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:

• Testing Full Reconciliation

• Testing Incremental Reconciliation

• Testing Provisioning

• Troubleshooting

5.1 Testing Full Reconciliation

The testing utility allows you to test the functionality of the connector without using Oracle Identity Manager. The testing utility takes as input a text file generated by the target system. This file contains comma-separated values.

To run the testing utility:

1. Open the OIM_HOME/XLIntegrations/PSFTUM/config/config_Recon.properties file, and specify values for the following properties:

   • FiltersToBeApplied

   • FiltersValues

   • IsFilterApplied

   • Operator

   • SearchCriteria

   • CaseSensitive

   • FilePath

   • RecordDelimiter

   • NoOfRecordsToBeReconciled

   • UserType

   • EmployeeType

   • OrganizationName

   • IndexOfLastReconciledRecord

   • AppendMode: If the value is yes, then the data is added to the end of the file. If the value is no, then the data is written from the beginning and the previous contents of the file are overwritten. The default value is no.

   • DestinationFileName: Specify the file name with path where the text file will be generated.

   • DelayBetweenRetries

   • NumberOfRetries

2. After you specify the values in the properties file, run the following file:

   For UNIX:

   OIM_HOME/XLIntegrations/PSFTUM/scripts/psftUM_Recon.sh
   

   For Microsoft Windows:

   OIM_HOME/XLIntegrations/PSFTUM/scripts/psftUM_Recon.bat
   

After the testing utility completes the run, a text file is created in the location specified in the DestinationFileName property. This file contains all the records that satisfy the filter condition, if required.

5.2 Testing Incremental Reconciliation

Testing incremental reconciliation involves verifying that the PeopleSoft listener can reconcile user profiles into Oracle Identity Manager. The following sections provide information about this procedure:

• Prerequisites for Testing the PeopleSoft Listener

• Testing the PeopleSoft Listener

5.2.1 Prerequisites for Testing the PeopleSoft Listener

The following are prerequisites for testing the PeopleSoft listener:

• Ensure that the Microsoft Windows scripting engine is installed. This is required to run VBScript files.

• Ensure that the PeopleSoft XML message template is described in the USR_MGMT_MSG.xml file, which is in the OIM_HOME/XLIntegrations/PSFTUM/cbrecon directory.

5.2.2 Testing the PeopleSoft Listener

To test the PeopleSoft listener:

1. In the OIM_HOME/XLIntegrations/PSFTUM/cbrecon/psft-xel-test.vbs file:

   • Modify the value of the ps_server_url variable so that it points to the URL for the PeopleSoft listener.

   • Specify the required PeopleSoft attributes and user data values in the ExecuteATM function.

2. Run psft-xel-test.vbs. Ensure that the script runs without any errors.

When the script is 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 specify in the psft-xel-test.vbs file.

If the reconciliation event is successful, an event is displayed with the status as either Event Linked or No Match Found.

5.3 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.

There are two modes in which the testing utility runs:

• File Mode: In this mode, all the connectivity information will be read from the config file and it will prompt you to enter target credentials, which consist of the username and password.

• OIM Mode: While running in OIM mode, the testing utility will read only the connectivity information from the IT Resource and rest of the information will be read from the file. It will prompt you to enter Oracle Identity Manager credentials, which consist of the username and password to log in to Oracle Identity Manager.

  While running the testing utility in OIM mode, you must copy the following files to the OIM_HOME/ThirdParty directory:

  • For Oracle WebLogic Server:

    Copy weblogic.jar from BEA_HOME/weblogic81/server/lib

  • For IBM WebSphere Application Server, copy the following files:

    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:

    Copy jbossall-client.jar and ejb.jar from OIM_CLIENT/xlclient/ext

  • For Oracle Application Server:

    Copy oc4jclient.jar and ejb.jar from OIM_CLIENT/xlclient/ext, and javagroups-all.jar from OIM_HOME/ext.

For the connector with the Remote Manager, before the testing utility prompts you for either the target or Oracle Identity Manager credentials, it will prompt you for the Remote Manager credentials. You must provide the following details:

• service name

  Sample value: ServiceName= RManager

• url

  The syntax of the url is: rmi://REMOTE_MANGER_HOST:BINDING_PORT

  Sample value: url = rmi://172.21.109.95:12346

  The service name and the binding port of the url are available in the RM_HOME/config/xlconfig.xml file.

Before you use the testing utility, you must set the required values in the config.properties file. This file is located in the OIM_HOME/XLIntegrations/PSFTUM/config directory.

Use the information in the following table to modify the default attributes of the config.properties file.

Name	Description	Sample Value
Mode	Specifies the mode (File/OIM) in which the testing utility will run.	FILE
ITResourceType	The IT resource type of the IT resource instance, which is used to fetch the connectivity information when running in OIM mode.	PSFTUM_RM
ITResourceName	The name of the IT resource instance which is used to fetch the connectivity information when running in OIM mode.	PSFTUM_RM_849
serverName	IP address or host name of the PeopleSoft Enterprise Applications server	172.21.109.95
serverPort	Port at which the PeopleSoft Enterprise Applications server is listening	9000
ciName	Component interface used to load user data in PeopleSoft Enterprise Applications	USER_PROFILE
NumberOfRetries	Number of times the connection to the target system must be retried before the InvocationTargetException is thrown	2
DelayBetweenRetries	Time difference between subsequent retries (in milliseconds)	10000
action	Action to be performed	You can specify one of the following values: CONNECT CREATE DELETE UPDATEUSERINFO UPDATEUSER_EMPID UPDATEPASSWORD
userId	User login ID	PSFTTEST
userDescription	Description of the user	PSFTTEST
primaryEmailAddress	Primary e-mail address	[e-mail]
primaryEmailType	E-mail type of the primary e-mail account	BUS
password	Password of the user	password
languageCode	Language code for the user	ENG
currencyCode	Currency code for the user	USD
recName	Used to validate the employee ID during user provisioning in PeopleSoft Enterprise Applications	PERSONAL_DATA
empId	Employee ID for the user	A10000
primaryPermissionList	Primary permission list for the user	HCCPAM1
userIdAlias	User ID alias	PSFTTEST1
symbId	Specifies the AccessId associated with the user profile The AccessId specifies whether or not the user has sufficient privileges on the PeopleSoft Enterprise Applications database.	PS89
attrName	Name of the attribute to be updated	You can specify one of the following values. These are the column names of the fields to be updated. UD_PSFT_BAS_EMPLID UD_PSFT_BAS_OPRDEFNDESC UD_PSFT_BAS_OPERPSWD
attrValue	Value of the attribute to be updated	The value that you provide must correspond to the attribute name that you specify as the value of the attrName parameter.

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

For UNIX:

OIM_HOME/XLIntegrations/PSFTUM/scripts/PSFTUM.sh

For Microsoft Windows

OIM_HOME/XLIntegrations/PSFTUM/scripts/PSFTUM.bat

For the connector with the Remote Manager:

For UNIX:

OIM_HOME/XLIntegrations/PSFTUM/scripts/PSFTUM_RM.sh

For Microsoft Windows

OIM_HOME/XLIntegrations/PSFTUM/scripts/PSFTUM_RM.bat

If your Oracle Identity Manager installation is running on IBM WebSphere Application Server, then run the following file:

For UNIX:

OIM_HOME/XLIntegrations/PSFTUM/scripts/was_psftUM_RM.sh

For Microsoft Windows

OIM_HOME/XLIntegrations/PSFTUM/scripts/was_PSFTUM_RM.bat

5.4 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 port has been specified. See Table 2-4, "Parameters of the IT Resource for the Target System" for information about locating and determining a JOLT port. Ensure that the server on which Oracle Identity Manager is running can communicate with the JOLT listener over the JOLT port.
The Operation Fail message is displayed on the Oracle Identity Manager Administrative and User Console.	Ensure that the values for the attributes do not contain delimiter characters, such as white space and commas. Ensure that the attribute values do not exceed allowable length.
The Create User adapter is triggered even when the pre-populate adapter is run successfully.	Set the property associated with the user ID attribute in the process form as required.