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

6.1 Testing the Connector

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. This section describes the following testing procedures:

6.1.1 Testing Provisioning

To use the testing utility:

  1. Copy the contents of the test directory on the installation media, to the OIM_HOME/xellerate/sapcua/test directory.

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

    This file is in the OIM_HOME/Xellerate/sapcua/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 CUA connection parameters Connection parameters required to connect to the target system

    These parameters are the same as the parameters of the IT resource.
    User information Field information required to create, modify, and delete a user profile
    Reconciliation information The From Date time stamp

    The To Date is set to the current date and time by default.

  3. Add the following to the CLASSPATH environment variable:

    OIM_HOME/xellerate/ext/log4j-1.2.8.jar

    OIM_HOME/Xellerate/JavaTasks/SAPCUA.jar

    OIM_HOME/Xellerate/ScheduleTask/SAPCommon.jar

    OIM_HOME/xellerate/lib/xlUtils.jar

    OIM_HOME/Xellerate/ThirdParty/sapjco.jar

    OIM_HOME/xellerate/lib/xlLogger.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/sapcua/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.

  5. Perform the following tests:

    • Enter the following command to create a user:

      java -DTproperties=OIM_HOME/Xellerate/sapcua/test/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/Xellerate/sapcua/test/Troubleshoot/log.properties TroubleShootingUtility C

    • Enter the following command to modify a user:

      java -DTproperties=OIM_HOME/Xellerate/sapcua/test/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/Xellerate/sapcua/test/Troubleshoot/log.properties TroubleShootingUtility M

    • Enter the following command to delete a user:

      java -DTproperties=OIM_HOME/Xellerate/sapcua/test/Troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_HOME/Xellerate/sapcua/test/Troubleshoot/log.properties TroubleShootingUtility D

    • Enter the following command to test reconciliation:

      java -DTproperties=OIM_HOME/Xellerate/sapcua/test/Troubleshoot/troubleShoot.properties -Dlog4j.configuration=file:/OIM_HOME/Xellerate/sapcua/test/Troubleshoot/log.properties TroubleShootingUtility R

6.1.2 Testing Limited Reconciliation

To test limited 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 assigned to the CustomizedReconQuery parameter: firstname=John&lastname=Doe

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

    • Value assigned to the CustomizedReconQuery parameter: firstname=John&userrole=ASAP_AUTORENUMGEBUNG

      Only the users with first name John and whose code key for user role is ASAP_AUTORENUMGEBUNG are reconciled.

      Note:

      The code key for user role is used to get the exact value of each role or profile.

  • 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 match 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.

6.1.3 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 at 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.

6.2 Troubleshooting

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

6.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 CUA.

Returned Error Message:

Error encountered while connecting to target server

Returned Error Code:

INVALID_CONNECTION_ERROR
  • Ensure that SAP CUA 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.
Target not available

Returned Error Message:

Target Server is not available

Returned Error Code:

TARGET_UNAVAILABLE_ERROR
  • Ensure that SAP CUA is running

  • Ensure that the specified SAP connection values 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.

6.2.2 Common SNC Errors

The following table provides a solution to an SNC error.

Problem Description 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

6.2.3 Create User Errors

The following table provides solutions to common Create User errors.

Problem Description Solution
Oracle Identity Manager cannot create a user.

Returned Error Message:

Required information missing

Returned Error Code:

SAP.INSUFFICIENT_INFORMATION

 Ensure that the following information is specified:

  • User ID

  • User first name

  • User last name

  • User password

  • User group

  • Profile option

  • Role or profile
Oracle Identity Manager cannot create a user.

Returned Error Message:

User already exists

Returned Error Code:

USER_ALREADY_EXIST

 User with the assigned ID already exists in SAP. Assign a new ID to this user, and try again.
Oracle Identity Manager cannot create a user.

Returned Error Message:

Could not create user

Returned Error Code:

USER_CREATION_FAILED

 User may not have been created because of one of the following errors:

  • The Change Password operation failed.

  • Role/profile assignment failed.

6.2.4 Delete User Errors

The following table provides solutions to common Delete User errors.

Problem Description Solution
Oracle Identity Manager cannot delete a user.

Returned Error Message:

Require information missing

Returned Error Code:

SAP.INSUFFICIENT_INFORMATION

 Ensure that the user ID has been correctly specified.
Oracle Identity Manager cannot delete a user.

Returned Error Message:

User does not exist

Returned Error Code:

SAP.USER_NOT_EXIST

 The specified user does not exist in SAP CUA.

6.2.5 Modify User Errors

The following table provides solutions to common Modify User errors.

Problem Description Solution
Oracle Identity Manager cannot update new information about a user.

Returned Error Message:

Could not modify user

Returned Error Code:

USER_MODIFICATION_FAILED

 Generic error. Refer to the log file for more details.
Oracle Identity Manager cannot update a user.

Returned Error Message:

User does not exist in target

Returned Error Code:

SAP.USER_NOT_EXIST

 The specified user does not exist in SAP CUA.

6.2.6 Child Data Errors

The following table provides solutions to common Child Data errors.

Problem Description Solution
Oracle Identity Manager cannot add a user to a profile.

Returned Error Message:

Profile does not exist

Returned Error Code:

SAP.PROFILE_NOT_MEMBER_OF_TARGET_SYSTEM

 The specified profile does not exist in SAP CUA. Check the profile name.
Oracle Identity Manager cannot assign a role to a user.

Returned Error Message:

Role is not a member of the target system

Returned Error Code:

ROLE_NOT_MEMBER_OF_TARGET_SYSTEM

 The specified role for the user in Oracle Identity Manager does not exist in SAP CUA. Check the role name.
The operation failed because a duplicate value was being added to a profile or role.

Returned Error Message:

User has already been assigned this role

Returned Error Code:

ROLE_ALREADY_EXISTS

PROFILE_ALREADY_EXISTS

 The user has already been added to the specified profile or role.