5 Testing and Troubleshooting

After you deploy the connector, you must test it to ensure that it functions as expected.

Note:

Using the testing utility, you can test connectivity and perform sanity tests on basic connector operations.The testing utility does not support functions such as validation, transformation, resource exclusion, multiple-version support, and remote connector server.

This chapter discusses the topics related to connector testing.

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 for reconciliation:

  1. Open and edit the test/config/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 HRMS
    

    v) Enter the name of the message for which you run the testing utility.

    For example:

    MessageName=PERSON_BASIC_SYNC
    
  2. If you are using Oracle Identity Manager release 11.1.2.x or later, then include the jrf.jar, jrf-api.jar, and jrf-client.jar files to the classpath.

    These JAR files are located in the $ORACLE_COMMON/modules/oracle.jrf_11.1.1 directory.

  3. Open a command window, and navigate to the scripts directory.

    You must run the testing utility from the OIM_HOME/server/ConnectorDefaultDirectory/CONN_HOME/test/scripts directory, where CONN_HOME is the connector directory.

    For example:

    OIM_HOME/server/ConnectorDefaultDirectory/PSFT_ER-11.1.1.5.0/test/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.HRMS.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.
Workforce incremental reconciliation fails or the updates on the target system are not transmitted to Oracle Identity Manager. You must update the Lookup.PSFT.HRMS.Configuration lookup definition on the Design Console.

To update, modify the WORKFORCE_SYNC.VERSION_3 value to WORKFORCE_SYNC.INTERNAL.