3 Testing the Connector

After you deploy the connector, you must test it to ensure that it functions as expected. You can conduct provisioning tests on the connector. This type of test involves using Oracle Identity Manager to provision one of its users or organizations with a target resource. In other words, Oracle Identity Manager is the starting point of the connector and the target resource is the end point.

A test from the connector to the target resource is known as an I-T provisioning testing.

Note:

In earlier releases of this guide, the connector was referred to as the integration.

I-T Provisioning Test

To perform an I-T provisioning test:

Update the following entry in the runADTest.bat script file. This file is in the xellerate_home\xellerate\test\scripts directory.
```
set XL_HOME = xellerate_home
```
Update the config.properties file in the xellerate_home\xellerate\test\config directory. In this file, specify the values of attributes for the AD user that would get created in Microsoft Active Directory as part of the I-T test.
Run the runADTest.bat script.

For example:
```
D:\eclipse\workspace\XLIntegrations\package\ActiveDirectory\test\scripts>runADTest
```
If the script runs without any error, then verify that the user has been created on the Microsoft Active Directory server.

Logging for Microsoft Active Directory Connectors

Logging can be enabled by making an appropriate entry in the log.properties file at the following location:

xellerate_home\xellerate\test\config

The following are the different log levels for which logging can be enabled:

DEBUG
INFO
WARN
ERROR
FATAL

Note:

The check for these values is case-sensitive. You must specify a value in uppercase only.

For example, if the log level for DEBUG is to be enabled, then you must add the following entry in the log.properties file:

log4j.logger.ADAPTERS.ACTIVEDIRECTORY=DEBUG