| Oracle® Identity Manager Connector Guide for BMC Remedy User Management Release 9.0.1 Part Number B31111-01 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for BMC Remedy User Management Release 9.0.1 Part Number B31111-01 |
|
|
View PDF |
Deploying the connector involves the following steps:
The following table lists the deployment requirements for the connector.
Perform the following steps to configure the target system:
Use the User form to create a user with License Type=Fixed. This user account is used to create new (custom) forms.
The SHR:DeletePeople form is used to store the details of deleted users. This information is required during reconciliation.
To create the SHR:DeletePeople form:
Open the ArAdmin tool.
Connect to the BMC Remedy User Management server by using the Demo user ID. The password can be left blank.
Click Forms.
Select Save As from the File menu, and save this form as SHR:DeletePeople.
A database trigger is used in the database to move all deleted users from the SHR:People form to the SHR:DeletePeople form.
Note:
The table for the SHR:People form is
t57, and the table for the SHR:DeletePeople form is t608. You can retrieve the table name by running the following SELECT statement on the database:
SELECT name,schemaid FROM arschema WHERE name LIKE 'SHR:People';
Instructions to create this database trigger in the BMC database are given in Appendix A.
This section discusses the following topics related to Remedy encryption:
To enable Remedy encryption:
Exit or stop all AR System processes that are running. To do this, open Control Panel, Administrator Tools, and Services. Examine the status of each AR System process and, if it is running, then stop it.
In the ar.conf file (for UNIX) or the ar.cfg file (for Microsoft Windows), add the Encrypt-Security-Policy option with a setting of 0 (encryption is allowed) or 1 (encryption is required). Add other options in the file as required.
The default UNIX directory for the ar.conf file is ar_install_dir/conf. In Microsoft Windows, the ar.cfg file is stored in the ar_install_dir\conf directory. Here ar_install_dir is the installation directory for ARSystem on the AR server.
Caution:
If you set theEncrypt-Security-Policy option to 1 (encryption is required), then communication is not allowed for any server or client that has not been upgraded to use encryption.Restart the AR System server.
To enable encryption and set encryption options, you must include server encryption options in the ar.conf file (UNIX) or the ar.cfg file (Microsoft Windows). You can do this by using a text editor.
You can set the Encrypt-Security-Policy encryption option. This is an integer value that indicates whether or not encryption is enabled. If encryption is enabled, then you can set encryption to required or allowed. If this option is not in the ar.cfg (or ar.conf) file, then encryption is disabled by default. You can assign any one of the following values to this option:
0: Encryption is allowed. Clients and servers with or without encryption enabled on them can connect to this AR System server.
1: Encryption is required. Only clients and servers that have encryption enabled on them can connect to this AR System server.
2: Encryption is disallowed. Regardless of whether or not encryption is enabled, clients and servers can communicate without encryption.
Sample Encryption Product Settings in the Configuration File
The following table explains sample settings for the options that you can add in the ar.conf (or ar.cfg) file.
| Option Settings | Significance |
|---|---|
| Encrypt-Security-Policy: 1 | Encryption is required. |
| Encrypt-Public-Key-Expire: 86400 | Public key duration is 1 day (86400 seconds). |
| Encrypt-Symmetric-Data-Key-Expire: 2700 | Symmetric data encryption key duration is 45 minutes (2700 seconds). |
| Encrypt-Public-Key-Algorithm: 5 | Public key encryption key strength is RSA-1024 (Performance Security). |
| Encrypt-Data-Encryption-Algorithm: 2 | Symmetric data encryption key strength is RC4 128-bit (Performance Security). |
If you do not set these options, then the default values are used. Defaults for the level of encryption depend on the encryption product that you are using.
When the AR System server is started, it checks encryption licensing and encryption configuration settings, if encryption is enabled. If the appropriate Remedy Encryption product licenses are not detected or if invalid configuration settings are detected, then one or more of the following error messages are displayed.
If encryption is disabled, then encryption error checking does not occur and encryption errors are bypassed. Error messages are listed in the order in which they are detected.
The connector files to be copied and the directories to which you must copy them are given in the following table.
Note:
The directory paths given in the first column of this table correspond to the location of the connector files in the following ZIP file on the installation media:Help Desk\BMC Remedy User Management\BMC Remedy User Management Rev 1.0.0.zip
Refer to "Files and Directories That Comprise the Connector" for more information about these files.
After you copy the connector files:
Copy the following files from the BMC Remedy Admin Client installation directory (for example, C:\Program Files\AR System) to the xellerate_home\xellerate\ThirdParty directory:
arapi60.jar arutil60.jar arapi60.dll arjni60.dll arrpc60.dll arutl60.dll
Include the path of the following files in the PATH environment variable:
arapi60.dll arjni60.dll arrpc60.dll arutl60.dll
Include the path of the following files in the CLASSPATH environment variable:
arapi60.jar arutil60.jar
To import the connector XML file into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for locating files is displayed.
Locate and open the BMCConnector_DM.xml file, which is in the xellerate_home\xlclient\ directory. Details of this XML file are shown on the File Preview page.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the BMC IT resource is displayed.
Specify values for the parameters of the BMC IT resource. Refer to the table in the "Defining IT Resources" section for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the BMCRemedy IT resource type is displayed.
Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.
See Also:
If you want to define another IT resource, then refer to Oracle Identity Manager Tools Reference Guide for instructions.Click View Selections.
The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. You must remove these nodes. To do this, right-click each such node, and then select Remove.
Click Import. The connector XML file is imported into Oracle Identity Manager.
After you import the connector XML file, proceed to the "Step 5: Configuring Reconciliation" section.
You must specify values for the BMC IT resource parameters listed in the following table.
| Parameter Name | Parameter Description |
|---|---|
UserName |
User ID that is used to connect to the target system
The default value is |
Password |
Password for the user ID that is used to connect to the target system |
ServerName |
IP address or computer name of the BMC Remedy User Management server |
Port |
TCP/IP port at which the BMC Remedy User Management server is listening
The default value is |
TrustedField |
Unique identification key for searching user records
The default value is |
IsDebug |
Specifies whether or not debugging statements must be displayed
The value can be |
TimeStamp |
For the first reconciliation run, specify the value None for this parameter. From the next reconciliation run time onward, this parameter stores the time at which the last reconciliation run was completed.
The default value is |
IsSecure |
Specifies whether or not the encryption feature is enabled
The value can be |
DeleteUserFormName |
Name of the form in the target system from which details of deleted users can be obtained
The value is |
FormName |
Name of the form in the target system from which details of newly created and updated users can be obtained
The value is |
After you specify values for these IT resource parameters, go to Step 9 of the procedure to import connector XML files.
Configuring reconciliation involves creating scheduled tasks for lookup fields and user reconciliations. To create these scheduled tasks:
Expand the Xellerate Administration folder.
Select Task Scheduler.
Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.
Enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager should attempt to complete the task before assigning the ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are cleared.
In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.
In the Interval region, set the following schedule parameters:
To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option.
If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.
To set the task to run only once, select the Once option.
Provide values for the attributes of the scheduled task. Refer to the appropriate table in the "Specifying Values for the Scheduled Task Attributes"section for information about the values to be specified.
See Also:
Oracle Identity Manager Design Console Guide for information about adding and removing task attributesClick Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.
Repeat Steps 5 through 10 to define the second scheduled task.
After you define both scheduled tasks, proceed to the "Step 6: Compiling Adapters" section.
This section provides information about the attribute values to be specified for the following scheduled tasks:
You must specify values for the following attributes of the lookup fields reconciliation scheduled task.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.After you specify values for these scheduled task attributes, go to Step 10 of the procedure to create scheduled tasks.
You must specify values for the following attributes of the user reconciliation scheduled task.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.| Attribute Name | Description | Value |
|---|---|---|
ServerName |
Name of the IT resource instance | BMC |
IsTrusted |
Specifies whether or not reconciliation is to be carried out in trusted mode | YES or NO
The default is |
TargetRO |
Name of the resource object | BMCRO |
XellerateOrganisation |
Default value for the Oracle Identity Manager Organization name
This value is used to create the Xellerate User in trusted mode. |
Xellerate Users |
After you specify values for these scheduled task attributes, go to Step 10 of the procedure to create scheduled tasks.
The following adapters are imported into Oracle Identity Manager when you import the connector XML file. You must compile these adapters before you can use them to provision accounts on the target system.
adpBMC
adpBMCUPDATEUSER
adpBMCUPDATEPASSWORD
adpBMCDELETEUSER
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
To compile all the adapters that you import into the current database, select the Compile All option.
To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select the Compile Selected option.
Click Start. Oracle Identity Manager compiles the adapters that you specify.
To view detailed information about an adapter:
Highlight the adapter in the Adapter Manager form.
Double-click the row header of the adapter, or right-click the adapter.
Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.
