Skip Headers
Oracle® Identity Manager Connector Guide for SAP User Management
Release 9.0.4

E10444-10
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

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:

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. Specify the required values in the global.properties file.

    This file is in the OIM_home/Xellerate/SAP/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 User Management connection parameters Connection parameters required to connect to the target system

    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.

    User information Field information required to create, modify, and delete a user profile
    Reconciliation information The From Date timestamp

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


  2. Add the following to the CLASSPATH environment variable:

    OIM_home/xellerate/ext/log4j-1.2.8.jar
    OIM_home/Xellerate/JavaTasks/SAPAdapter.jar
    OIM_home/Xellerate/ScheduleTask/SAPAdapterRecon.jar
    OIM_home/xellerate/lib/xlLogger.jar
    OIM_home/xellerate/lib/xlUtils.jar
    OIM_home/xellerate/lib/xlAPI.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/sap/test/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.

  4. Perform the following tests:

    • Enter the following command to create a user:

      java -DTproperties=OIM_home/Xellerate/SAP/test/troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_home/Xellerate/SAP/test/troubleshoot/log.properties TroubleShootingUtility C
      
    • Enter the following command to modify a user:

      java -DTproperties=OIM_home/Xellerate/SAP/test/troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_home/Xellerate/SAP/test/troubleshoot/log.properties TroubleShootingUtility M
      
    • Delete a user as follows:

      java -DTproperties=OIM_home/Xellerate/SAP/test/troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_home/Xellerate/SAP/test/troubleshoot/log.properties TroubleShootingUtility D
      
    • Enter the following command to test reconciliation from the timestamp specified to the current time:

      java -DTproperties=OIM_home/Xellerate/SAP/test/troubleshoot/troubleshoot.properties -Dlog4j.configuration=file:/OIM_home/Xellerate/SAP/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 assigned to the CustomizedReconQuery parameter: firstname=John&lastname=Doe

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

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

      Only the users with first name John and who belong to the ASAP_AUTORENUMGEBUNG role 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 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 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 log 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 table lists solutions to a commonly encountered problem associated with this connector.

Problem Description Solution
Oracle Identity Manager cannot establish a connection to SAP User Management.

Returned Error Messages

Connection error encountered

Returned Error Code

CONNECTION_ERROR

  • Ensure that SAP User Management is running.
  • Ensure that the connection parameters for the SAP User Management server have been correctly specified.

  • Check that information in the IT resource, such as the user name and password, are correct.

  • If required, restart SAP User Management.