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, "Running Test Cases"

• Section 5.2, "Troubleshooting"

5.1 Running Test Cases

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.

The testing utility is located in the /test directory of the installation media.

To use the testing utility:

1. Open one of the following files:

   • For Oracle Identity Manager release 9.1.0.x:

     OIM_HOME/xellerate/XLintegrations/EBSUM/config/config_um_prov.properties

   • For Oracle Identity Manager releases 11.1.x and 11.1.2.x:

     OIM_HOME/server/XLintegrations/EBSUM/config/config_um_prov.properties

2. Specify values for the attributes in this file. These attributes are described in the following table.

   Attribute	Description	Sample Value
   MODE	Specifies the mode to run the testing utility Note: For this release of the connector, only the FILE mode is supported.	FILE
   PROPERTIES_FILE_NAME	Specifies the name of the properties file that contains data for the testing utility	config_um_prov_fileOption.properties
   ACTION	Specifies the provisioning action to be performed by the testing utility	The required action can be CONNECT,CREATE_USER, UPDATE_USER, DISABLE_USER, ENABLE_USER, ADD_RESPONSIBILITY, or REMOVE_RESPONSIBILITY.

   
   

3. Open one of the following files:

   • For Oracle Identity Manager release 9.1.0.x:

     OIM_HOME/xellerate/XLIntegrations/EBSUM/config/config_um_prov_fileOption.properties

   • For Oracle Identity Manager releases 11.1.x and 11.1.2.x:

     OIM_HOME/server/XLIntegrations/EBSUM/config/config_um_prov_fileOption.properties

4. Specify values for the following parameters listed in the file:

   Parameter	Description
   ITR.CONNECTION_RETRIES	Enter the number of consecutive attempts to be made to establish a connection with the target system. Sample value: 3
   ITR.RETRY_INTERVAL	Enter the interval in milliseconds between consecutive attempts to establish a connection with the target system. Sample value: 120000
   ITR.ADMIN_ID	Use Login ID of the Oracle E-Business User Management server administrator Sample value: apps
   ITR.ADMIN_PASSWORD	Password of the Oracle E-Business User Management server administrator Sample value: passw0rd1
   ITR.STATEMENT_TIMEOUT	Enter the time in milliseconds within which a query run on the target system is expected to return results. If the results of a query are not returned within the specified time, then it is assumed that the connection with the target system has failed. The connector then attempts to reestablish a connection with the target system. Sample value: 120000
   ITR.CONNECTION_TIMEOUT	Enter the time in milliseconds within which the target system is expected to respond to a connection attempt.For a particular connection attempt, if the target system does not respond within the time interval specified by the Connection Timeout parameter, then it is assumed that the connection attempt has failed. Sample value: 120000
   ITR.EBSCONTEXT_USER_ID	This parameter is used only by the Oracle E-Business User Management connector. Sample value: 0
   ITR.EBSCONTEXT_APPLICATIONNAME	This parameter is used only by the Oracle E-Business User Management connector. Sample value: 0
   ITR.EBSCONTEXT_RESPONSIBILITY_NAME	This parameter is used only by the Oracle E-Business User Management connector. Sample value: 0
   ITR.JDBC_URL	Specify the JDBC URL for the target system database. Sample value: jdbc:oracle:thin:@172.21.176.18:1521:vis
   ITR.CONNECTION_PROPERTIES	Specify the connection properties for the target system database.
   ITR.IS_SSL_ENABLED	To configure SSL to secure communication between Oracle Identity Manager and the target system. Sample value: No
   UD_EBS_USER_USRNAME	User Login ID Sample value: ORATEST
   UD_EBS_USER_PASSWORD	Password of the user Sample value: passw0rd1
   UD_EBS_USER_PSWD_EXP_TYPE	Password Expiration type of the user Sample value: Days, Accesses, None
   UD_EBS_USER_PSWD_EXP_INTV	Password Expiration value of the user This value depends on the value assigned to the Password expiration Type attribute.
   UD_EBS_USER_DESCR	Description of the user Sample value: Test description
   UD_EBS_USER_EMAIL	E-mail address of the user Sample value: [e-mail]
   UD_EBS_USER_FAX	Fax number of the user Sample value: 657895421
   UD_EBS_USER_EFFDATEFROM	Start date of the user Sample value: 2009-03-11
   UD_EBS_USER_EFFDATETO	End date of the user Sample value: 2009-04-12
   UD_EBS_USER_USERID	User ID of the user Sample value: 1051274
   UPDATE_FIELDNAME	Name of the process form field to be updated Sample value: UD_EBS_USER_PASSWORD
   APPLICATION_NAME	Application short name Sample value: 1~160
   RESPONSIBILITY_NAME	Responsibility name Sample value: 1~160~20456
   RESP_START_DATE	Start date of the responsibility Sample value: 2006-11-11
   RESP_END_DATE	End date of the responsibility Sample value: 2006-11-11
   SECURITY_GROUP_NAME	Security group name Sample value: 1~1

   
   

5. Run the testing utility file.

   Note:

   Before running the testing utility, in Oracle Identity Manager 11g, extract EBSUM.jar file for MANIFEST.MF file and set Class-Path to correct path of jars, include Jdbc driver jar file and repackage EBSUM.jar with these settings.

   • On Microsoft Windows, run the following file:

     • For Oracle Identity Manager release 9.1.0.x:

       OIM_HOME\xellerate\XLIntegrations\EBSUM\scripts\OracleEBiz.bat

     • For Oracle Identity Manager releases 11.1.x and 11.1.2.x:

       OIM_HOME\server\XLIntegrations\EBSUM\scripts\OracleEBiz.bat

   • On UNIX, run the following file:

     • For Oracle Identity Manager release 9.1.0.x:

       OIM_HOME/xellerate/XLIntegrations/EBSUM/scripts/OracleEBiz.sh

     • For Oracle Identity Manager releases 11.1.x and 11.1.2.x:

       OIM_HOME/server/XLIntegrations/EBSUM/scripts/OracleEBiz.sh

6. If the script runs without any error, then verify that the required provisioning action has been carried out on the target system.

5.2 Troubleshooting

The following table lists solutions to some commonly encountered errors associated with the connector.

Problem Description	Solution
Oracle Identity Manager cannot establish a connection with the Oracle E-Business User Management server.	Ensure that the Oracle E-Business User Management server is running. Check if the user exists in Oracle E-Business User Management. Ensure that Oracle Identity Manager is running. Use the IT Resources form to examine the Oracle Identity Manager record. Ensure that the IP address, administrator ID, and administrator password are correct.
The Operation Failed message is displayed on the Oracle Identity Manager Administrative and User Console	Ensure that the values for the attributes do not contain delimiter characters (white space). Ensure that the attribute values do not exceed the specified length.
One of the following error messages is thrown when Oracle Identity Manager tries to exchange data with the target system: table or view does not exist insufficient privileges	This error message is thrown because the target system account for connector operations does not have the required privileges. See Section 2.1.2.1, "Creating a Target System User Account for Connector Operations" for information about creating this account and assigning the required privileges to it.
Reinstallation of the connector is unsuccessful.	Perform the following steps to resolve the issue: In a text editor, open the OIM_HOME/ConnectorDefaultDirectory/ORCL_EBS_UM_RELEASE_NUMBER/xml/Oracle-eBusiness Suite-HRMS-Main-ConnectorConfig.xml for editing. Search for all resource forms and remove the <Form name> entries to prevent them from being reimported. For example, search for and remove the entry: <Form name = "UD_EBSX_XXXX" subtype = "Resource Form"> Save and close the file. Retry installing the connector.