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 BMC Remedy User Management.

This chapter contains the following sections:

Connector Architecture
Reconciliation Module
Provisioning Module
Supported Functionality
Multilanguage Support
Files and Directories That Comprise the Connector
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, BMC Remedy System has been referred to as the target system. It is used interchangeably with BMC Remedy User Management.

The BMC Remedy User Management connector is also referred to as the user management connector.

1.1 Connector Architecture

The architecture of the connector is the blueprint for the functionality of the connector.

The primary function of a connector is to create Users on the target system through Oracle Identity Manager. The BMC Remedy System (target system) can be configured to run in either the identity reconciliation (trusted source) mode or the provisioning (target resource) mode.

In the identity reconciliation mode, BMC Remedy System is used as the trusted source and users are directly created and modified on it. During reconciliation from the trusted source, the user management connector fetches data about these target system users into Oracle Identity Manager. This data is used to create or update the corresponding OIM Users.

In the account management or provisioning mode, BMC Remedy System is used as a target resource. During reconciliation, the user management connector fetches data about users created or modified directly on the target system into Oracle Identity Manager. This data is used to add or modify resources allocated to OIM Users. In addition, the connector enables provisioning operations through which user data changes are propagated from Oracle Identity Manager to BMC Remedy System.

Figure 1-1 provides the architecture of the BMC Remedy User Management connector.

Figure 1-1 Architecture of the BMC Remedy User Management Connector

Description of "Figure 1-1 Architecture of the BMC Remedy User Management Connector"

Users are created during provisioning in the People form of the BMC Remedy target system. The connector makes use of the Remedy APIs to connect to the Remedy Server, and in turn provision the account.

During Reconciliation, user records are retrieved from the People form.

1.2 Reconciliation Module

Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. It is an automated process initiated by a scheduled task that you configure.

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about reconciliation configurations

Based on the type of data reconciled from the target system, reconciliation can be divided into the following types:

Lookup Fields Reconciliation
User Reconciliation

1.2.1 Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the following lookup fields:

Company
Organization
Department
Region
Site
Site ID
Site Group
Support Group ID
Support Relationship Role
Support Group Company
Support Group Organization
Support Group Name
Primary Cost Center Code

1.2.2 User Reconciliation

User reconciliation involves reconciling the following fields.

1.2.2.1 Reconciled Resource Object Fields

The following target system fields are reconciled:

Profile Status
ARLicenseType
Department
Site
Region
LastName
FirstName
LoginName
SupportStaff
HourlyRate
Vip
Client Type
Client Sensitivity
NotificationMethod
EmailAddress
PrimaryCenterCode
Company
Organization
Site ID
Person ID
Business Phone Number

The following multivalued fields are reconciled:

Support Group Company
Support Group Organization
Support Group Name
Support Group Relationship Role
Support Group Association ID
Support Group ID

1.2.2.2 Reconciled Xellerate User Fields

The following target system fields are reconciled only if trusted source reconciliation is implemented:

User ID
First Name
Last Name
Organization
User Type
Employee Type

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

See Also:

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:

Profile Status
ARLicenseType
Department
Site
Region
LastName
FirstName
LoginName
HourlyRate
Vip
Client Type
Client Sensitivity
NotificationMethod
EmailAddress
PrimaryCenterCode
Password
Company
Organization
Site Group

The following multivalued fields are provisioned:

Support Group Company
Support Group Organization
Support Group Name
Support Group Relationship Role
Support Group ID

Note:

If a support group is added, then the SupportStaff field on the parent form is updated to Yes.

1.4 Supported Functionality

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

Function	Type	Description
Add User	Provisioning	Creates a user
Delete User	Provisioning	Deletes a user
Update User Last Name	Provisioning	Updates the last name of a user
Update User Password	Provisioning	Updates the password of a user
Update User First Name	Provisioning	Updates the first name of a user
Update User Client Sensitivity	Provisioning	Updates the Client Sensitivity field of a user
Update User Email	Provisioning	Updates the e-mail address of a user
Update User Support Staff	Provisioning	Updates the support staff of a user
Update User Profile Status	Provisioning	Updates the profile status of a user
Update User Client Type	Provisioning	Updates the client type of a user
Update User VIP Field	Provisioning	Updates the VIP status of a user
Update User Business Phone	Provisioning	Updates the business phone number of a user
Update User Notification Method Field	Provisioning	Updates the notification method of a user
Update User Region	Provisioning	Updates the region of a user
Update User Site	Provisioning	Updates the site of a user
Update User Department	Provisioning	Updates the department of a user
Update User Company	Provisioning	Updates the company of a user
Update User Organization	Provisioning	Updates the organization of a user
Update User Hourly Rate	Provisioning	Updates the hourly rate of a user
Update User CostCentercode	Provisioning	Updates the cost center code of a user
Update User ARLicenseType	Provisioning	Updates the ARLicense type of a user
Update User Site Group	Provisioning	Updates the User Site group of a user
Reconcile Lookup Field	Reconciliation	Reconciles the lookup fields
Reconcile User Data	Reconciliation	Trusted source reconciliation: Reconciles user data from BMC Remedy User Management to Oracle Identity Manager. A corresponding user is created in Oracle Identity Manager. If the user already exists in Oracle Identity Manager, then this user is updated. Target resource reconciliation: Reconciles user data from BMC Remedy User Management to Oracle Identity Manager. A user is not created in Oracle Identity Manager.

1.5 Multilanguage Support

The connector supports the following languages:

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

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

1.6 Files and Directories That Comprise the Connector

The files and directories that comprise this connector are in the following directory on the installation media:

Help Desk/BMC Remedy/BMC Remedy User Management

These files and directories are listed in Table 1-1.

Table 1-1 Files and Directories On the Installation Media

File in the Installation Media Directory	Description
configuration/BMC RemedyUser Reconciliation-CI.xml	This XML file contains configuration information that is used during connector installation.
config/attributemapping_prov.properties	This file contains the attributes required for provisioning.
config/attributemapping_recon.properties	This file contains the attributes required for reconciliation.
lib/JavaTask/xlBMCRemedy.jar	This file contains the class files that are required for provisioning.
Files in the `resources` directory	Each of these resource bundles contains language-specific information that is used by the connector. Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.
test/config/config.properties	This file contains the parameters required to connect to and perform provisioning on the target system.
test/config/log.properties	This file is used to store log information.
test/scripts/BMCRemedy.bat test/scripts/BMCRemedy.sh	This file is used to run the test utility.
xml/BMCConnector_DM.xml	This file contains definitions for the following components of the connector: IT resource type IT resource Resource object Process form Process definition Process tasks Adapter tasks Scheduled tasks
xml/BMCXellerateUser_DM.xml	This XML file contains the configuration for the Xellerate User. You must import this file only if you plan to use the connector for trusted source reconciliation.

1.7 Determining the Release Number of the Connector

You can use the following method to determine the release number of the connector:

Extract the contents of the xlBMCRemedy.jar file. This file is in the following directory on the installation media:
```
OIM_HOME/xellerate/JavaTasks/xlBMCRemedy.jar
```
Open the Manifest.mf file in a text editor. The Manifest.mf file is one of the files bundled inside the xlBMCRemedy.jar file.

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