5 Testing and Troubleshooting

This chapter discusses the topics related to connector 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.

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 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/scc_constituent_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 Campus

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

    For example:

    MessageName=SCC_CONSTITUENT_SYNC
  2. 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_CS-11.1.1.5.0/test/scripts

  3. 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 this connector:

Problem Description Solution

When you try to run an operation, you get an error similar to the following errors:

oracle.iam.connectors.psft.common.parser.impl.CampusMessageParser: processMessage: No data found in XML

MissingRequiredAttributeException: [Last Name]

Ensure that Decode entries of the Lookup.PSFT.Campus.SccConstituentFullSync.AttributeMapping lookup definition are based on the message structure shown in Message Structure.

If the message structure changes (if the node names in the XML file are different), then the Decode entries in the lookup definition need to be updated as per the modified message structure.

Note: If this problem is encountered during incremental reconciliation, then change the Decode entries in the Lookup.PSFT.Campus.SccConstituentSync.AttributeMapping lookup definition.

When you try to run a reconciliation operation, sometimes two CREATE user events will be created for a single entity.

Ensure that the reconciliation batchSize parameter is set to 0 in the reconciliation profile of the Resource Object.