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 for testing reconciliation:

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

   This file is in the OIM_home/xellerate/XLIntegrations/saphrms/test/troubleshoot directory. The following table describes the sections of this file in which you must provide information for running the tests.

   Section	Information
   SAP HRMS Server Parameters	Parameters required to connect to SAP Employee Reconciliation For information about the values that you must provide, refer to the description of the IT resource parameters. This is covered earlier in this guide.
   Reconciliation Parameters	Date from which modified data is to be reconciled The To Date value is taken as the current date and time.

   
   

2. Add the following to the CLASSPATH environment variable:

   OIM_home/xellerate/ext/log4j-1.2.8.jar
   OIM_home/Xellerate/ScheduleTask/xliSAPHR.jar
   OIM_home/xellerate/lib/xlLogger.jar
   OIM_home/xellerate/lib/xlUtils.jar
   OIM_home/Xellerate/ThirdParty/sapjco.jar
   

3. 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/XLIntegrations/saphrms/test/troubleshoot
      

   2. Enter the following command:

      native2ascii global.properties troubleshoot.properties
      

      The troubleshoot.properties file 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.

4. Enter the following command to test reconciliation:

   java -DTproperties=OIM_home/xellerate/XLIntegrations/saphrms/test/troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_home/xellerate/XLIntegrations/saphrms/test/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 queries with user attributes

  Value assigned to the CustomizedReconQuery parameter: firstname=John

  The users with first name John are reconciled.

• Queries with '&' and '|' logical operators

  • Value assigend to the CustomizedReconQuery parameter: employeeid=E001|firstname=John

    The users with employee id E001 and users with first name John are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: firstname=John&lastname=Doe

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

• Queries with time stamps

  • Value assigned to the CustomizedReconQuery parameter: None

    Value of the TimeStamp parameter: Nov 3, 2006 at 10:00:00 GMT+05:30

    The users that matches the time stamp value are reconciled.

  • Value assigned to the CustomizedReconQuery parameter: firstname=John

    Value of the TimeStamp parameter: Nov 3, 2006 at 10:00:00 GMT+05:30

    The users with first name John and who matches the time stamp value are reconciled.

4.1.2 Testing Batched Reconciliation

You can test reconciliation based on batching and data paging of user records by specifying values for the following user reconciliation scheduled task attributes:

• If you set the value of StartRecord to 1, BatchSize to 0, and NumberOfBatches to All Available, then all the users are reconciled.

• If you set the value of StartRecord to 1, BatchSize to 5, and NumberOfBatches to 50, then all the users starting from record 1 are reconciled in 50 batches, with 5 records in each batch.

• If you set the value of StartRecord to 200, BatchSize to 5, and NumberOfBatches to 50, then all the users starting from record 200 are reconciled in 50 batches, with 5 records in each batch.

The results of batching are displayed in the logger file, which is located in the following path:

JBOSS_HOME/server/default/log/server.log

In this file, you can view the batch numbers, the user ids of the users that are reconciled, and whether the reconciliation is successful or not.

4.2 Troubleshooting

The following sections provide solutions to some commonly encountered problems associated with the connector:

• Connection Errors

• Common SNC Errors

4.2.1 Connection Errors

The following table provides solutions to common connection errors.

Problem Description	Solution
Oracle Identity Manager cannot establish a connection to SAP Employee Reconciliation. Returned Error Message: Connection error encountered Returned Error Code: INVALID_CONNECTION_ERROR	Ensure that SAP Employee Reconciliation is running. Ensure that Oracle Identity Manager is running (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 the IP address, admin ID, and admin password are correct.
Authentication error Returned Error Message: Invalid or incorrect password Returned Error Code: AUTHENTICATION_ERROR	Ensure that the specified SAP connection user ID and password are correct.

4.2.2 Common SNC Errors

The following table provides a solution to an SNC error.

Problem Descriptions	Solution
Trying to connect to SAP through SNC. Returned Error Message: SAP Connection JCO Exception Returned Error Code: SNC required for this connection	Ensure that values for the following IT resource parameters are correctly specified as shown in the following example: SAPsnc_mode: 1 SAPsnc_myname: p:CN=win2003, OU=SAP, O=ORA, C=IN SAPsnc_qop: 3 SAPsnc_partnername: p:CN=I47, OU=SAP, O=ORA, C=IN SAPsnc_lib: C://usr//sap//sapcrypto.dll