4 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:

• Running Test Cases

• Troubleshooting

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

To use the testing utility:

1. Copy the contents of the Troubleshoot directory on the installation media, to the OIM_HOME/xellerate/Siebel/Troubleshoot directory.

2. Specify the required values in the global.properties file.

   This file is in the OIM_HOME/xellerate/Siebel/Troubleshoot directory. The following table describes the sections of this file in which you must provide information for running the tests.

   Section	Information
   Siebel Server Parameters	Parameters required to connect to the target system These parameters are the same as the parameters of the IT resource.
   Create User Parameters	Values required to create a user
   Modify User Parameters	Values required to modify a user
   Delete User Parameters	User ID of the user to be deleted
   Recon Parameters	Date from which modified data is to be reconciled The To Date value is taken as the current date and time.

   
   

3. Add the following to the CLASSPATH environment variable:

   OIM_HOME/xellerate/lib/xlUtils.jar
   OIM_HOME/xellerate/JavaTasks/xlSiebel.jar
   OIM_HOME/xellerate/ScheduleTask/SiebelRecon.jar
   OIM_HOME/xellerate/lib/xlLogger.jar 
   OIM_HOME/xellerate/ext/log4j-1.2.8.jar
   

   For Siebel 7.5, the following files from the OIM_HOME/xellerate/ThirdParty directory

   SiebelJI_enu.jar
   SiebelJI_Common.jar
   SiebelJI.jar
   

   For Siebel 7.8, the following files from the OIM_HOME/xellerate/ThirdParty directory

   Siebel.jar
   SiebelJI_enu.jar
   

4. Create an ASCII-format copy of the global.properties file as follows:

   Note:

   You must perform this procedure every time you make a change in the contents of the global.properties file.

   1. In a command window, change to the following directory:

      OIM_HOME/Xellerate/Siebel/troubleshoot
      

   2. Enter the following command:

      native2ascii global.properties troubleshoot.properties
      

      The troubleshoot.properties is created when you run the native2ascii command. The contents of this file are an ASCII-format copy of the contents of the global.properties file.

5. Perform the following tests:

   • Enter the following command to create a user:

     java -DTproperties=OIM_HOME/xellerate/Siebel/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/xellerate/Siebel/Troubleshoot/log.properties TroubleShootingUtility C
     

   • Enter the following command to modify a user:

     java -DTproperties=OIM_HOME/xellerate/Siebel/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/xellerate/Siebel/Troubleshoot/log.properties TroubleShootingUtility M
     

   • Enter the following command to delete a user:

     java -DTproperties=OIM_HOME/xellerate/Siebel/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/xellerate/Siebel/Troubleshoot/log.properties TroubleShootingUtility D
     

   • Enter the following command to reconcile user information:

     java -DTproperties=OIM_HOME/xellerate/Siebel/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/xellerate/Siebel/Troubleshoot/log.properties TroubleShootingUtility R
     

4.1.1 Testing Partial Reconciliation

To test query-based reconciliation, you can specify the following types of query conditions as values for the CustomizedReconQuery parameter:

• Simple query with user attributes, for example:

  • Value assigned to the CustomizedReconQuery parameter: First Name=John

    The users with first name John are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: Login Name=JOHN

    The users with login name JOHN are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: First Name=John|First Name=Jane

    The users with first name John and Jane are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: First Name=John&Last Name=Doe

    The users with the first name John and last name Doe are reconciled.

• Query based on positions and responsibilities, for example:

  • Value assigned to the CustomizedReconQuery parameter: Position=Proxy Employee|Position=ERM AnonUser

    All users having positions as Proxy Employee or ERM AnonUser are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: Responsibility=CEO&Responsibility=Consultant

    All users having responsibilities as CEO and Consultant are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: Responsibility=CEO& Position=ERM AnonUser

    All users having responsibility CEO and position as ERM AnonUser are reconciled.

• Complex queries, for example:

  • Value assigned to the CustomizedReconQuery parameter: First Name=John&Position=Proxy Employee|Position=ERM AnonUser

    All users having first name as John and position as Proxy Employee, as well as all users with position as ERM AnonUser are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: Last Name=Doe|Position=Proxy Employee&Responsibility=CEO

    All users having last name as Doe plus all users having both Position as Proxy Employee and Responsibility as CEO are reconciled.

Note:

For queries with a combination of & and |, the name value pairs adjacent to the & operator are taken as if they are in parenthesis by Siebel.

4.1.2 Testing Reconciliation Based on User Type

You can test reconciliation based on the type of user by specifying the following values for the UserType scheduled task attribute:

• Employee

  All information about users belonging to the Employee type is reconciled.

• Partner User

  All information about users belonging to the Partner User type is reconciled.

• Customer

  All information about users belonging to the Customer type is reconciled. These users belonging to the Customer type have NONE as the value for the Position field.

4.2 Troubleshooting

The following sections list solutions to some commonly encountered errors of the following types:

• Connection Errors

• Create User Errors

• Delete User Errors

• Edit User Errors

4.2.1 Connection Errors

The following table lists the solution to a commonly encountered connection error.

Problem Description	Solution
Oracle Identity Manager cannot establish a connection to the target system. Returned Error Message: SIEBEL connection exception	Ensure that the target system is running. Ensure that Oracle Identity Manager is working (that is, the database is running). Ensure that all the adapters have been compiled. Examine the Oracle Identity Manager record (from the IT Resources form). Ensure that values for all the IT resource parameters have been correctly specified.

4.2.2 Create User Errors

The following table lists the solution to a commonly encountered Create User error.

Problem Description	Solution
Oracle Identity Manager cannot create a user. Returned Error Message: User already exists Returned Error Code: SIEBEL.USER_ALREADY_EXIST	A user with the assigned ID already exists in the target system.

4.2.3 Delete User Errors

The following table lists the solution to a commonly encountered Delete User error.

Problem Description	Solution
Oracle Identity Manager cannot delete a user. Returned Error Message: User does not exist in target system Returned Error Code: SIEBEL.USER_DOES_NOT_EXIST	The specified user does not exist in the target system.

4.2.4 Edit User Errors

The following table lists the solution to a commonly encountered Edit User error.

Problem Description	Solution
Oracle Identity Manager cannot update a user. Returned Error Message: User does not exist in target system Returned Error Code: SIEBEL.USER_DOES_NOT_EXIST	Review the log for more details.