Skip Headers
Oracle® Identity Manager Connector Guide for Microsoft Active Directory
Release 9.0.2

Part Number B32157-01
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Index
Index

Go to previous page
Previous
Go to next page
Next
View PDF

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:

  1. Update the following entry in the runADTest.bat script file. This file is in the OIM_home\xellerate\test\scripts directory.

    set XL_HOME = OIM_home
    
    
  2. Update the config.properties file in the OIM_home\xellerate\test\config directory. In this file, specify values for the attributes of the AD user that is created in Microsoft Active Directory as part of the I-T provisioning test.

  3. Run the runADTest.bat script. This file is in the following directory:

    OIM_home\xellerate\test\scripts
    
    

    If the script runs without any error, then verify that the user has been created on the Microsoft Active Directory server.

Enabling Logging

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

OIM_home\xellerate\test\config

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


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