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 on the installation media. See Section 2.1.1.1, "Files and Directories on the Installation Media" for more information.

To run the testing utility:

Copy the testing utility files to the following directories:
- If you are using Oracle Identity Manager release 9.1.0.x, then:
  
  Copy files from the test/config directory on the installation media to the OIM_HOME/xellerate/XLIntegrations/PSFTER/config directory.
  
  Copy files from the test/scripts directory on the installation media to the OIM_HOME/xellerate/XLIntegrations/PSFTER/scripts directory.
- If you are using Oracle Identity Manager release 11.1.1, then:
  
  Copy files from the test/config directory on the installation media to the OIM_HOME/server/XLIntegrations/PSFTER/config directory.
  
  Copy files from the test/scripts directory on the installation media to the OIM_HOME/server/XLIntegrations/PSFTER/scripts directory.
  
  Note:
  
  You must create the destination directories on the Oracle Identity Manager host computer if they are not present.
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
- If you are using Oracle Identity Manager release 9.1.0.x, then copy the log4j.jar file into the following directory:
  
  OIM_HOME/xellerate/ThirdParty
- If you are using Oracle Identity Manager release 11.1.1, then copy the lib/PSFTCommon.jar and lib/Common.jar files from installation media into the following directory:
  
  OIM_HOME/server/JavaTasks
Modify the files that you copy into the config directory as follows:
1. If you are using Oracle Identity Manager release 9.1.0.x, then 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) Enter the PeopleSoftOIMListener servlet URL as the value of ListenerURL in following syntax:
```
http://HOSTNAME:PORT/PeopleSoftOIMListener
```
  For example:
```
ListenerURL=http://10.1.6.83:8080/PeopleSoftOIMListener
```
  ii) Enter the absolute XML message file path as the value of XMLFilePath as shown in the following example:
```
XMLFilePath=c:/xmlmessages/person_basic_sync.xml
```
  Note:
  
  Ensure that there is no blank or white-space character in the directory path and file name that you specify.
  
  iii) Enter a value for the MessageType. For a ping message, specify Ping, None, or otherwise as shown in the following example:
```
MessageType=None
```
  iv) Enter a value for ITResourceName. This value must match the active IT resource in Oracle Identity Manager.
  
  For example:
```
ITResourceName=PSFT Server
```
  v) Enter the name of the message for which you run the testing utility.
  
  For example:
```
MessageName=PERSON_BASIC_SYNC
```
3. Open a command window, and navigate to the following directory:
  
  If you are using Oracle Identity Manager release 9.1.0.x, then:
  
  OIM_HOME/xellerate/XLIntegrations/PSFTER/scripts
  
  If you are using Oracle Identity Manager release 11.1.1, then:
  
  OIM_HOME/server/XLIntegrations/PSFTER/scripts
4. Run the following script:
  
  For Microsoft Windows:
```
InvokeListener.bat
```
  For UNIX:
```
InvokeListener.sh
```

Verify that a reconciliation event is created in Oracle Identity Manager and that the event contains the data 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.