1 About the Connector

Oracle Identity Manager automates access rights management, security, and provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications. This guide discusses the procedure to deploy the connector that is used to integrate Oracle Identity Manager with Microsoft Windows.

This chapter contains the following sections:

Provisioning Module
Supported Functionality
Multilanguage Support
Files and Directories on the Installation Media
Determining the Release Number of the Connector

Note:

In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.

At some places in this guide, Microsoft Windows has been referred to as the target system.

1.1 Provisioning Module

Provisioning involves creating or modifying a user's account information on the target system through Oracle Identity Manager. You use the Oracle Identity Manager Administrative and User Console to perform provisioning operations.

Note:

For a provisioning operation, the file server, Oracle Identity Manager, and the target system account used by Oracle Identity Manager to perform provisioning operations must be on the same domain.

See the "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about provisioning.

For this target system, the following fields are provisioned:

New Share Path
Full Control
Change
Read
Share Path
Write
None
Hidden

1.2 Supported Functionality

The following table lists the functions that are available with this connector.

Function	Type	Description
Create folder for a user	Provisioning	Creates a folder, shares it for the user, and adds the user to the shared folder. Note: The folder that the connector creates is not the home folder for the user. When the user is added to the shared folder, only the permissions selected on the process form are granted.
Create hidden folder for a user	Provisioning	Creates a hidden folder, shares it for the user, and adds the user to the shared hidden folder. Note: The folder that the connector creates is not the home folder for the user. When the user is added to the shared folder, only the permissions selected on the process form are granted.
Delete share attribute	Provisioning	Stops sharing a folder.
Update access permissions for user	Provisioning	Updates the permissions granted to a user on the shared folder.
Revoke access permissions from user	Provisioning	Revokes the permissions granted to a user on a shared folder.
Add new share name	Provisioning	Assigns a new share name to an existing shared folder.

1.3 Multilanguage Support

The connector supports the following languages:

Arabic
Chinese Simplified
Chinese Traditional
Danish
English
French
German
Italian
Japanese
Korean
Portuguese (Brazilian)
Spanish

1.4 Files and Directories on the Installation Media

The files and directories on the installation media are listed and described in Table 1-1.

Table 1-1 Files and Directories on the Installation Media

File in the Installation Media Directory	Description
configuration/MS Windows-CI.xml	This XML file contains configuration information that is used during connector installation.
config\debug.properties	This file contains the debug parameter that you use to specify whether or not the connector must run in debug mode.
lib\tcWindowsNT40.dll	This DLL file contains the native code required for provisioning directories on a Microsoft Windows 2003 server.
lib\xliWindows2000.jar	This JAR file contains the class files required for provisioning. During connector deployment, this file is copied into the following directory: OIM_HOME/xellerate/JavaTasks
Files in the `resources` directory	Each of these resource bundles contains language-specific information that is used by the connector. During connector deployment, these resource bundles are copied into the following directory: OIM_HOME/xellerate/connectorResources Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the Administrative and User Console. These text strings include GUI element labels and messages.
test\config\config.properties	This file contains the attributes for Oracle Identity Manager to connect to the target system and perform provisioning operations.
test\scripts\runWindowsTest.bat	This file is used to start the testing utility.
xml\Windows2000Object_DM.xml	This XML file contains definitions for the following components of the connector: IT resource type Process form Process task and adapters (along with their mappings) Resource object Provisioning process Pre-populate rules Lookup definitions

Note:

The files in the test directory are used only to run tests on the connector.

1.5 Determining the Release Number of the Connector

You might have a deployment of an earlier release of the connector. While deploying the latest release, you might want to know the release number of the earlier release. To determine the release number of the connector that has already been deployed:

In a temporary directory, extract the contents of the following JAR file:
```
OIM_HOME/xellerate/JavaTasks/xliWindows2000.jar
```
Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the xliWindows2000.jar file.

In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.