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:

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

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 Phone	Provisioning	Updates the phone number of a user
Update User Fax	Provisioning	Updates the fax number of a user
Update User Office Number	Provisioning	Updates the office number of a user
Update User Pager Fields	Provisioning	Updates the pager fields of a user
Update User Web Page	Provisioning	Updates the URL of the Web page of a user
Update User Street	Provisioning	Updates the street name of a user's address
Update User City	Provisioning	Updates the city of a user's address
Update User Postal Code	Provisioning	Updates the postal code of a user's address
Update User Accounting Code	Provisioning	Updates the accounting code of a user
Update User ID	Provisioning	Updates the ID 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

In addition to English, this release of the connector supports the following languages:

French
Japanese

Reconciliation Module

This section discusses the elements that the reconciliation module extracts from the target system to construct reconciliation event records.

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:

Status
ARLicenseType
Department
Site
Region
FullName
LastName
FirstName
LoginName
Id
PhoneNumber
FaxNumber
PagerSoftware
PagerPin
OfficeNo
PagerProvider
Manager
SupportStaff
HourlyRate
Vip
AccountingCode
Type
NotificationMethod
EmailAddress
PagerEmail
OptionalParameter1
WebPage
ManagerName
OptionalParameter2
PagerPhone
Street
PostalCode
City
Country
State
PrimaryCenterCode

Provisioning Module

The following fields are provisioned:

Status
ARLicenseType
Department
Site
Region
FullName
LastName
FirstName
LoginName
Id
PhoneNumber
FaxNumber
PagerSoftware
PagerPin
OfficeNo
PagerProvider
Manager
SupportStaff
HourlyRate
Vip
AccountingCode
Type
NotificationMethod
EmailAddress
PagerEmail
OptionalParameter1
WebPage
ManagerName
OptionalParameter2
PagerPhone
Street
PostalCode
City
Country
State
PrimaryCenterCode
Password

Files and Directories That Comprise the Connector

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

Help Desk\BMC Remedy User Management\BMC Remedy User Management Rev 1.1.0.zip

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
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
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.
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.
Files in the `resources` directory	Each of these files contains locale-specific information that is used by the connector.
docs\B32150_01.pdf	This guide, which provides instructions to deploy the connector.

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

Determining the Release Number of the Connector

To determine the release number of the connector:

Extract the contents of the xlBMCRemedy.jar file. This file is in the lib\JavaTask directory inside the installation media directory.
Open the manifest.mf file in a text editor, which 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.