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. The connector for BMC Remedy User Management is used to integrate Oracle Identity Manager with BMC Remedy User Management.

Note:

Oracle Identity Manager connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.

This chapter contains the following sections:

Reconciliation Module
Provisioning Module
Supported Functionality
Multilanguage Support
Files and Directories That Comprise the Connector
Determining the Release Number of the Connector

Note:

At some places in this guide, BMC Remedy User Management has been referred to as the target system.

Reconciliation Module

Reconciliation involves duplicating in Oracle Identity Manager additions 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 Framework 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

Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the following lookup fields:

Country
Department
ManagerName
PagerSw
PrimaryCenterCode
Region
Site
State

User Reconciliation

User reconciliation involves reconciling the following fields.

Reconciled Resource Object Fields

The following target system fields are reconciled:

Status
ARLicenseType
Department
Site
Region
FullName
LastName
FirstName
LoginName
PagerSoftware
Manager
SupportStaff
HourlyRate
Vip
Type
NotificationMethod
EmailAddress
ManagerName
Country
State
PrimaryCenterCode

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

Provisioning Module

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

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Framework Guide for conceptual information about provisioning

For this target system, the following fields are provisioned:

Status
ARLicenseType
Department
Site
Region
FullName
LastName
FirstName
LoginName
PagerSoftware
Manager
SupportStaff
HourlyRate
Vip
Type
NotificationMethod
EmailAddress
ManagerName
Country
State
PrimaryCenterCode
Password

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 Full Name	Provisioning	Updates the full name 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 Status	Provisioning	Updates the status of a user
Update User Type	Provisioning	Updates the type of a user
Update User VIP Field	Provisioning	Updates the VIP status of a user
Update User Manager Field	Provisioning	Updates the manager code of a user
Update User Notification Method Field	Provisioning	Updates the notification method of a user
Update User Manager Name Field	Provisioning	Updates the name of a user's manager
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 State	Provisioning	Updates the state of a user
Update User Country	Provisioning	Updates the country 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
Reconcile Lookup Field	Reconciliation	Reconciles the lookup fields
Reconcile User Data	Reconciliation	Trusted mode: 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. Nontrusted mode: Reconciles user data from BMC Remedy User Management to Oracle Identity Manager. A user is not created in Oracle Identity Manager.

Multilanguage Support

The connector supports the following languages:

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

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

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 User Management

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
BMCTrigger/Trigger.txt	This file contains the SQL code for the trigger that is run on the BMC Remedy database for moving the records of deleted users.
lib/JavaTask/xlBMCRemedy.jar	This file contains the class files that are required for provisioning.
lib/ScheduleTask/xlBMCRemedyRecon.jar	This file contains the class files that are required for reconciliation.
Files in the `resources` directory	Each of these resource bundle files 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.
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
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.

The "Step 3: Copying the Connector Files and External Code Files" section provides instructions to copy these files into the required directories.

Determining the Release Number of the Connector

You can use any one of the following methods to determine the release number of the connector.

Before Deployment

To determine the release number of a connector before you deploy it:

Extract the contents of the xlBMCRemedy.jar file. This file is in the following directory on the installation media:
```
Help Desk/BMC Remedy User Management/lib/JavaTask
```
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.

Note:

If you maintain a copy of the xlBMCRemedy.jar file after deployment, then you can use this method to determine the release number of the connector at any stage. After you deploy the connector, it is recommended that you use the "After Deployment" method, which is described in the following section.

After Deployment

To determine the release number of a connector that has already been deployed:

See Also:

Oracle Identity Manager Design Console Guide

Open the Oracle Identity Manager Design Console.
In the Form Designer, open the process form. The release number of the connector is the value of the Version field.