5 Testing and Troubleshooting

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

• Section 5.1, "Testing Reconciliation"

• Section 5.2, "Testing Provisioning"

• Section 5.3, "Troubleshooting"

5.1 Testing Reconciliation

After you deploy the connector, you must test it to ensure that it functions as expected. 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 contains the following directories:

• config: Contains configuration-related information

• scripts: Contains the scripts to run

To run the testing utility:

1. Copy the testing utility files in the following folders:

   config: OIM_HOME/xellerate/XLIntegrations/PSFT/config

   scripts: OIM_HOME/xellerate/XLIntegrations/PSFT/scripts

2. Copy the log4j.jar file in the following directory:

   OIM_HOME/xellerate/ThirdParty

3. Modify the files present in the OIM_HOME/xellerate/XLIntegrations/PSFT/config directory as follows:

   1. Modify the log.properties file as described in Section 2.3.1.2, "Enabling Logging."

   2. Open and edit the reconConfig.properties file as follows:

      i) Provide the PeopleSoftOIMListener servlet URL for ListenerURL in the following syntax:

      http://HOST_NAME: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/user_profile.xml
      

      
      

      Note: There should not be any space in the directory path.

      
      

      iii) Provide the value for 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 are run the testing utility.

      For example:

      MessageName=USER_PROFILE
      

   3. Open the command prompt.

   4. Navigate to the following location:

      OIM_HOME/xellerate/XLIntegrations/PSFT/scripts

   5. Run the following file:

      For Microsoft Windows:

      OIM_HOME/xellerate/XLIntegrations/PSFT/Test/scripts/InvokeListener.bat
      

      For UNIX:

      OIM_HOME/xellerate/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 Testing Provisioning

You can use the testing utility to identify the cause of problems associated with connecting to the target system and performing basic operations on the target system.

When you run the testing utility, it reads the connectivity information from the IT Resource, lookup definitions from Oracle Identity Manager, and process form data is read from the config.properties file.

While running the testing utility, you must ensure that the connector should be deployed and Oracle Identity Manager should be running.

Note: The testing utility might not work for IBM WebSphere Application Server and Oracle WebLogic Server.

1. Copy the following files to OIM_HOME/xellerate/ThirdParty directory:

   For IBM WebSphere Application Server:

   com.ibm.ws.admin.client_6.1.0.jar from WAS_HOME/AppServer/runtimes

   ibmorb.jar from WAS_HOME/AppServer/java/jre/lib

   xlDataObjectBeans.jar from OIM_CLIENT/xlclient/lib

   For JBoss Application Server:

   jbossall-client.jar from OIM_CLIENT/xlclient/ext

   log4j.jar from JBOSS_HOME/server/default/lib

   xlGenericUtils.jar from OIM_HOME/xellerate/lib

   For Oracle WebLogic Server:

   weblogic.jar from BEA_HOME/weblogic81/server/lib

2. Modify the attributes of the config.properties file using the values specified in the following table. This file is located in the OIM_HOME/xellerate/XLIntegrations/PSFTUM/config directory.

   Name	Description	Default Value
   ACTION	The value of this attribute defines the operation to be performed. It can have any value from the following set: CONNECT,CREATE, DELETE, ENABLE, DISABLE, UPDATEUSER, UPDATEEMAIL, UPDATEROLE,ADDORDELETEEMAIL, ADDORDELETEROLE,UPDATEPASSWORD, UPDATEIDTYPE	CONNECT
   IT_RESOURCE_NAME	The name of the IT resource instance from where the connectivity information is read.	PSFT Server
   UD_PSFT_BAS_SYMBOLICID UD_PSFT_BAS_EMPLID UD_PSFT_BAS_SERVER UD_PSFT_BAS_MULTILANG_CD UD_PSFT_BAS_LANGUAGE_CD UD_PSFT_BAS_CURRENCYCODE UD_PSFT_BAS_OPRID UD_PSFT_BAS_OPRDEFNDESC UD_PSFT_BAS_PRIEMAILADDRESS UD_PSFT_BAS_PRIEMAILTYPE UD_PSFT_BAS_OPERPSWD UD_PSFT_BAS_PRPERMISSIONLIST UD_PSFT_BAS_ROWPERMISSIONLIST UD_PSFT_BAS_PROCESSPROFILELIST UD_PSFT_BAS_NAVIGATORHOMELIST UD_PSFT_BAS_USERIDALIAS UD_PSFT_BAS_CUSTID UD_PSFT_BAS_CUSTSETID UD_PSFT_BAS_VNDID UD_PSFT_BAS_VNDSETID	Create user and update user data. Provide the value for the columns that have to be provisioned.	NA
   DELETE_USER_ID	Specify the user ID to be deleted.	NA
   ENABLE_USER_ID	Specify the user ID to be enables.	NA
   DISABLE_USER_ID	Specify the user ID to be disabled.	NA
   MODIFY_EMAIL_USER_ID EMAIL_ACTION EMAIL_TYPE EMAIL_ADDRESS	These attributes are used for adding or deleting an e-mail record. MODIFY_EMAIL_USER_ID: Specify the user ID whose e-mail record is to be modified. EMAIL_ACTION: This could be ADD or DELETE. EMAIL_TYPE: Specify the Type of Email Note: EMAIL_TYPE should be supplied in the following format 1~BB EMAIL_ADDRESS: Email Address	NA
   MODIFY_ROLE_USER_ID ROLE_ACTION ROLE_NAME	These attributes are used for adding or deleting a Role. MODIFY_ROLE_USER_ID: Specify the user ID whose Role is to be modified. ROLE_ACTION: This could be ADD or DELETE ROLE_NAME: Name of the role to be added or deleted Note: ROLE_NAME should be supplied in the following format 1~CE User.	NA
   UPDATE_PASSWORD_USER_ID	Specify the user ID whose password is to be updated
   UPDATE_ID_TYPE_USER_ID IDTYPE_COLUMNNAME_TO_BE_UPDATED	These attributes are used to update the ID type associated with a user profile. UPDATE_ID_TYPE_USER_ID: Specify the User ID whose ID Type is to be modified IDTYPE_COLUMNNAME_TO_BE_UPDATED: Specify the column name of the ID Type attribute For example, if employee ID is to be updated then specify UD_PSFT_BAS_EMPLID	UD_PSFT_BAS_EMPLID
   UPDATE_ROLE_USER_ID OLD_ROLE_NAME NEW_ROLE_NAME	These attributes are used to update the role assigned to a user profile UPDATE_ROLE_USER_ID: Specify the user ID whose role is to be updated OLD_ROLE_NAME: Role Name that has been assigned NEW_ROLE_NAME: New Role Name Note: OLD_ROLE_NAME assigned to the user ROLE NAME should be supplied in the following format: 1~Role Name. For example, 1~CE User.
   UPDATE_EMAIL_USER_ID NEW_EMAIL_TYPE OLD_EMAIL_TYPE NEW_EMAIL_ADDRESS	These attributes are used to update the e-mail messages assigned to a user profile NEW_EMAIL_TYPE: New Email Type to be updated OLD_EMAIL_TYPE: Existing Email Type of the email NEW_EMAIL_ADDRESS: New Email Address Note: OLD_EMAIL_TYPE should be already assigned to the user Note: EMAIL TYPE Should be supplied in the following format: 1~EMAILTYPE. For example, 1~BB.
   UPDATE_USER_ID COLUMN_TO_BE_UPDATED	These attributes are used to update the user attributes. UPDATE_USER_ID: User ID of the user profile whose attribute is to be updated COLUMN_TO_BE_UPDATED: Specify the column name of the attribute to be updated Note: The updated data would be fetched from create user and update user data.
   XL_HOME_DIR JAVA_SECURITY_POLICY JAVA_SECURITY_AUTH_LOGIN_CONFIG JAVA_NAMING_PROVIDER_URL	These are system properties, which have to be set for a signature-based login in Oracle Identity Manager. XL_HOME_DIR: Specify the path of Oracle Identity Manager home directory, for example path till the xellerate directory. For example: C:\OIM_JBOSS_9102\OimServer\xellerate JAVA_SECURITY_POLICY: Specify the path of xl.policy file. It is present in the config directory. For example: C:\OIM_JBOSS_9102\OimServer\xellerate\config\xl.policy JAVA_SECURITY_AUTH_LOGIN_CONFIG: Specify the path of auth.conf file. It is present in the config directory. For example: C:\OIM_JBOSS_9102\OimServer\xellerate\config\auth.conf For JBoss Application Server: Specify the path of aut.conf For Oracle WebLogic Server: Specify the path of authwl.conf file For IBM WebSphere Application Server: Specify the path of authws.conf JAVA_NAMING_PROVIDER_URL: Specify the value of "java.naming.provider.url" attribute present in the Discovery settings in OIM_HOME/xellerate/config/xlconfig.xml	NA

   
   

3. After you specify values in the config.properties file, run one of the following files:

   For UNIX:

   OIM_HOME/xellerate/XLIntegrations/PSFTUM/scripts/PeoplsoftTestingUtility.sh
   

   For Microsoft Windows:

   OIM_HOME/xellerate/XLIntegrations/PSFTUM/scripts/PeoplsoftTestingUtility.bat
   

   The following table lists the column names or attributes for create and update user in the config.properties and their labels:

   Attributes	Labels
   UD_PSFT_BAS_SYMBOLICID	Symbolic ID
   UD_PSFT_BAS_EMPLID	Employee ID
   UD_PSFT_BAS_MULTILANG_CD	Multi Language Code
   UD_PSFT_BAS_LANGUAGE_CD	Language Code
   UD_PSFT_BAS_CURRENCYCODE	Currency Code
   UD_PSFT_BAS_OPRID	User ID
   UD_PSFT_BAS_OPRDEFNDESC	User Description
   UD_PSFT_BAS_PRIEMAILADDRESS	Primary Email Address
   UD_PSFT_BAS_PRIEMAILTYPE	Primary Email Type
   UD_PSFT_BAS_OPERPSWD	Password
   UD_PSFT_BAS_PRPERMISSIONLIST	Primary Permission List
   UD_PSFT_BAS_ROWPERMISSIONLIST	Row Security Permission List
   UD_PSFT_BAS_PROCESSPROFILELIST	Process Profile Permission List
   UD_PSFT_BAS_NAVIGATORHOMELIST	Navigator Home Permission List
   UD_PSFT_BAS_USERIDALIAS	User ID Alias
   UD_PSFT_BAS_CUSTID	Customer ID
   UD_PSFT_BAS_CUSTSETID	Customer Set ID
   UD_PSFT_BAS_VNDID	Vendor ID
   UD_PSFT_BAS_VNDSETID	Vendor Set ID

   
   

5.3 Troubleshooting

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

Problem Description	Solution
Oracle Identity Manager cannot establish a connection with the PeopleSoft Enterprise Applications server.	Ensure that the PeopleSoft Enterprise Applications server is running. Ensure that Oracle Identity Manager is running. Ensure that all the adapters have been compiled. Use the IT Resources form to examine the Oracle Identity Manager record. Ensure that the IP address, admin ID, and admin password are correct. Ensure that the correct Jolt URL has been specified. See Table 2-4, "IT Resource Parameters" for information about locating and determining a Jolt URL. Ensure that the server on which Oracle Identity Manager is running can communicate with the Jolt listener over the Jolt URL.
Class loading error Returned Error Message: ERROR [STDERR] Caused by: java.lang.NoClassDefFoundError: psft/pt8/joa/JOAException	Check the value of the Multiple Version Support parameter in the Lookup.PSFT.Configuration lookup definition. If the value is set to No, then ensure that the OIM_HOME/xellerate/ThirdParty directory contains the target system specific JAR files (psjoa.jar and peoplesoft.jar). If the value of the Multiple Version Support parameter in the lookup definition is set to Yes, then verify the directory path specified in the Jar File Location parameter of ITResource. It should contain target system specific JAR files (psjoa.jar and peoplesoft.jar).
Connection error Returned Error Message: Reason:NwHdlr: Cannot open socketINFO [STDOUT] Jolt Session Pool cannot provide a connection to the appsever. This appears to be because there is no available application server domain. ERROR [STDERR] [Thu Nov 12 19:36:16 IST 2009] bea.jolt.ServiceException: Invalid Session	Check the Jolt URL parameter defined in the ITResource. See Table 2-4, "IT Resource Parameters" for more information. It should contain the correct host name and port.
Class loading error Returned Error Message: ERROR [PSFTUM] Description : ADP ClassLoader failed to load: oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManagerERROR [PSFTUM] java.lang.ClassNotFoundException: ADP ClassLoader failed to load: oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager	Check the value of the Multiple Version Support parameter in the Lookup.PSFT.Configuration lookup definition. If the value is set to No, then ensure that the OIM_HOME/xellerate/JavaTasks directory contains the PSFTUM.jar file with the oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager class. If the value of the Multiple Version Support parameter in the lookup definition is set to Yes, then verify the directory path specified in the Jar File Location parameter of ITResource. It should contain PeopleSoftProxy.jar with oracle.iam.connectors.psft.usermgmt.integration.PSFTUMUserProxyProvisionManager class.
You might receive the following error message while reconciling user profile data: ERROR [PSFTCOMMON] ================================= ERROR [PSFTCOMMON] oracle.iam.connectors.psft.common.handler.HandlerFactory: getMessageHandler: No Lookup defined for message USER_PROFILE.VERSION_84 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 "USER_PROFILE.VERSION_84". ERROR [PSFTCOMMON] ================================= This indicates that the target system is sending the USER_PROFILE message with the name USER_PROFILE.VERSION_84.	You must modify the Code Key value of the USER_PROFILE attribute in the Lookup.PSFT.Configuration lookup definition as follows: Code Key: USER_PROFILE.VERSION_84 Decode: Lookup.PSFT.Message.UserProfile.Configuration