4 Testing and Troubleshooting

After you deploy and configure the connector, you must test it to ensure that it functions as expected. This chapter discusses the following topics related to connector testing:

• Testing the Connector

• Troubleshooting Connector Problems

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

To use the testing utility:

1. Specify values for the parameters in the config.properties file. This file is in the OIM_HOME/xellerate/XLIntegrations/BMC/test/config directory.

   Note:

   The parameters in the config.properties file are the same as the IT resource parameters.

2. Run one of the following files:

   For UNIX:

   OIM_HOME/xellerate/XLIntegrations/tests/scripts/BMCRemedy.sh
   

   For Microsoft Windows

   OIM_HOME\xellerate\XLIntegrations\tests\scripts\BMCRemedy.bat
   

4.1.1 Testing Partial and Batched Reconciliation

You can test both partial and batched reconciliation, in either trusted source or target resource mode, by specifying values for the following user reconciliation attributes:

• BatchSize

• NoOfBatches

• First Name

• Last Name

• Notification Method

• Status

• Operator

These attributes are described in the "User Reconciliation Scheduled Tasks" section.

The following is a sample set of values for these attributes:

• BatchSize: 4

• NoOfBatches: 2

• First Name: John

• Last Name: Doe

• Notification Method: Nodata

• Status: 1

• Operator: AND

Suppose you specify these values in the target resource user reconciliation scheduled task. After that task is run, all target system records for which the first name and last name values are John and Doe, respectively, are divided into batches of four records each. Of these batches, the first two are reconciled during the current reconciliation run.

4.2 Troubleshooting Connector Problems

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 BMC server.	Ensure that the BMC Remedy User Management server is running. Ensure that Oracle Identity Manager is running. Ensure that all the adapters have been compiled. Use the IT Resources form to examine the Oracle Identity Manager record. Ensure that values for all the IT resource parameters have been correctly specified.
The Operation Failed message is displayed on the Oracle Identity Manager Administrative and User Console.	Ensure that the values for the various attributes do not contain delimiter characters (white space). Ensure that the attribute values do not exceed the allowable length.
The following error is encountered: java.lang.UnsatisfiedLinkErrorwrong ELF data format:ELFDATA2MSB	Ensure that you are using the specified shared object (.so) files. These files are platform dependent. For example, .so files for SPARC systems cannot work on x86 systems. See "Copying the External Code Files" for more information.