5 Testing and Troubleshooting

After you deploy the connector, you must test it to ensure that it functions as expected. This chapter discusses the topics related to connector testing.

Section 5.1, "Testing Reconciliation"
Section 5.2, "Troubleshooting"

5.1 Testing Reconciliation

The testing utility enables you to test the functionality of the connector. The testing utility takes as input the XML file or message generated by the target system. It can be used for testing full and incremental reconciliation.

The testing utility is located in the /test directory of the installation media.

It has the following directories:

config: Contains configuration-related information
scripts: Contains the scripts to run

To run the testing utility:

Copy the testing utility files in the following folders:

config: OIM_HOME/XLIntegrations/PSFT/config

scripts: OIM_HOME/XLIntegrations/PSFT/scripts
Copy the log4j.jar file in the following directory:

OIM_HOME/Xellerate/ThirdParty
Modify the files present in the OIM_HOME/XLIntegrations/PSFT/config directory as follows:
1. Modify the log.properties file as described in Section 2.3.1.1, "Enabling Logging."
2. Open and edit the reconConfig.properties file as follows:
  
  i) Provide the PeopleSoftOIMListener servlet URL for ListenerURL in following syntax:
```
http://HOSTNAME:PORT/PeopleSoftOIMListener
```
  For example:
```
ListenerURL=http://10.1.6.83:8080/PeopleSoftOIMListener
```
  ii) Provide the absolute XML message file path for XMLFilePath as follows:
```
XMLFilePath=c:/xmlmessages/person_basic_sync.xml
```
  Note:
  There should not be any space in the directory path.
  
  iii) Provide the value for the MessageType. In case of the ping message, specify Ping, None, or otherwise as follows:
```
MessageType=None
```
  iv) Specify the value for ITResourceName. This value should match the active IT resource in Oracle Identity Manager.
  
  For example:
```
ITResourceName=PSFT Server
```
  v) Provide the name of the message for which you run the testing utility.
  
  For example:
```
MessageName=PERSON_BASIC_SYNC
```
3. Open a command window, and switch to the following directory:
  
  OIM_HOME/XLIntegrations/PSFT/scripts
4. Run the following file:
  
  For Microsoft Windows:
```
OIM_HOME/XLIntegrations/PSFT/Test/scripts/InvokeListener.bat
```
  For UNIX:
```
OIM_HOME/XLIntegrations/PSFT/Test/scripts/InvokeListener.sh
```

After the testing utility completes the run, it creates a reconciliation event. Verify that the reconciliation event is created in Oracle Identity Manager and that the event contains the data that you specified in the message-specific XML file.

5.2 Troubleshooting

The following table lists solutions to some commonly encountered issues associated with the PeopleSoft Employee Reconciliation connector:

Problem Description	Solution
You might receive the following error message while reconciling job data: ERROR [PSFTCOMMON] =============================== ERROR [PSFTCOMMON] oracle.iam.connectors.psft.common.handler.HandlerFactory: getMessageHandler: No Lookup defined for message WORKFORCE_SYNC.VERSION_2 ERROR [PSFTCOMMON] =============================== ERROR [PSFTCOMMON] =============================== ERROR [PSFTCOMMON] oracle.iam.connectors.psft.common.listener.PeopleSoftOIMListener: process: Message specific handler couldn'tbe initialized. Please check if lookup definition has been specified for the message "WORKFORCE_SYNC.VERSION_2". ERROR [PSFTCOMMON] ================================ This indicates that the target system is sending the WORKFORCE_SYNC message with the name WORKFORCE_SYNC.VERSION_2.	You must modify the Code Key value of the WORKFORCE_SYNC attribute in the Lookup.PSFT.Configuration lookup definition as follows: Code Key: WORKFORCE_SYNC.VERSION_2 Decode: Lookup.PSFT.Message.WorkForceSync.Configuration
If the WORKFORCE_FULLSYNC message is processed before the PERSON_BASIC_FULLSYNC message, then the Oracle Identity Manager stores the data for all those events in the Event Received state. You might receive an event in the Event Received state with an empty Status field.	You must check the value of the Action applicable for the Person in the Lookup.PSFT.HRMS.WorkForceSync.EmpStatus lookup definition. This lookup definition stores the mapping between the Action applicable for a Person and the OIM User status.

Problem Description

Solution

You might receive the following error message while reconciling job data:

ERROR [PSFTCOMMON] 
===============================
ERROR [PSFTCOMMON] 
oracle.iam.connectors.psft.common.handler.HandlerFactory:
getMessageHandler: 
No Lookup defined for 
message WORKFORCE_SYNC.VERSION_2 
ERROR [PSFTCOMMON] 
===============================

ERROR [PSFTCOMMON] 
===============================
ERROR [PSFTCOMMON] 
oracle.iam.connectors.psft.common.listener.PeopleSoftOIMListener:
process: Message specific handler couldn'tbe initialized. 
Please check if lookup definition has been 
specified for the message "WORKFORCE_SYNC.VERSION_2".
ERROR [PSFTCOMMON] 
================================

This indicates that the target system is sending the WORKFORCE_SYNC message with the name WORKFORCE_SYNC.VERSION_2.

You must modify the Code Key value of the WORKFORCE_SYNC attribute in the Lookup.PSFT.Configuration lookup definition as follows:

Code Key: WORKFORCE_SYNC.VERSION_2

Decode: Lookup.PSFT.Message.WorkForceSync.Configuration

If the WORKFORCE_FULLSYNC message is processed before the PERSON_BASIC_FULLSYNC message, then the Oracle Identity Manager stores the data for all those events in the Event Received state. You might receive an event in the Event Received state with an empty Status field.

You must check the value of the Action applicable for the Person in the Lookup.PSFT.HRMS.WorkForceSync.EmpStatus lookup definition. This lookup definition stores the mapping between the Action applicable for a Person and the OIM User status.