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:

• Testing the Connector

• Troubleshooting

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/DBAppTables/config directory.

   See Also:

   The "Defining IT Resources" section for information about the parameters in the config.properties file

2. Run one of the following files:

   For UNIX:

   OIM_home/xellerate/XLIntegrations/DBAppTables/scripts/DBTable.sh
   

   For Microsoft Windows

   OIM_home\xellerate\XLIntegrations\DBAppTables\scripts\DBTable.bat
   

4.2 Troubleshooting

The following table provides solutions to some commonly encountered issues associated with this connector.

Problem Description	Returned Error Code	Solution
Oracle Identity Manager cannot establish a connection with the target database.	DATABASE CONNECTION FAILED	Ensure that the drivers of the database are specified in the CLASSPATH environment variable of the Oracle Identity Manager server. 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 the IP address, administrator ID, and administrator password are correct.
	DATABASE DRIVER NOT LOADED	Ensure that the database driver is available in the CLASSPATH environment variable of the Oracle Identity Manager server.
A provisioning operation fails with an error code other than those described in the following rows.	CONFIGURATION ERROR	Ensure that the configuration XML file given in the IT resource definition exists at the specified file system path. Ensure that the XML schema file exists at the location specified in the configuration XML file. Ensure that the configuration XML file adheres to the XML schema specified inside the file itself.
	DATA SIZE MISMATCH	Ensure that the data size of the user profile attributes in the configuration XML file adheres to the process form limitations.
	MANDATORY FIELD MISSING	Ensure that values are provided for all user attributes specified as required in the configuration XML file. This error is thrown even if a blank string is provided. Ensure that the process form includes the fields marked as required in the configuration XML file.
	DATABASE OPERATION FAILED	Ensure that the maximum size of user profile attributes given in the configuration XML file matches the size defined in the actual database schema. Ensure that all the mandatory fields of the database table are marked as required in the configuration XML file.
Create User provisioning operation fails	USER ALREADY EXISTS	Check if the target database table already has a record with the same user ID (or a combination of whichever primary key fields exist for the table).
Create User or Reset Password provisioning operation fails	ENCRYPTION INTERFACE MISSING	Check if password encryption is set to true in the configuration XML file. Ensure that the encryption interface implementation class is available in the CLASSPATH environment variable of the Oracle Identity Manager server.
	ENCRYPT/DECRYPT ERROR	This error occurs if an exception is thrown from the encryption implementation class. Check if the encryption implementation class is working correctly. Check the logs for a description of the error and stack trace.
Update Any User Profile Attribute, Delete a User, or Revoke a Provisioned Resource Object from a User provisioning operation fails	USER DOES NOT EXIST	Check if the record for the user exists in the target database tables.