This chapter provides an overview of the updates made to the software and documentation for release 11.1.1.6.0 of the BMC User Management connector.
The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software. This section also points out the sections of this guide that have been changed in response to each software update.
Documentation-Specific Updates
This section describes major changes made to this guide. For example, the relocation of a section from the second chapter to the third chapter is a documentation-specific update. These changes are not related to software updates.
The following sections discuss software updates:
The following are the software updates in release 11.1.1.6.0:
Support for Performing Reconciliation and Provisioning Operations on Custom Forms
Support for Performing Lookup Field Synchronization Against Custom Forms
By default, this connector provisions to and reconciles data from the CTM:People form. From this release onward, the connector can be configured to perform reconciliation and provisioning operations on custom forms in the target system. See Section 4.6, "Configuring the Connector for Performing Reconciliation and Provisioning Operations on Custom Forms".
The connector performs lookup field synchronization against the default forms (available in the target system) associated with each lookup field. From this release onward, you can specify target system form names against which lookup field synchronization must be performed. See Section 4.7, "Configuring the Connector for Performing Lookup Field Synchronization on Custom Forms".
The following are issues resolved in release 11.1.1.6.0:
Bug Number | Issue | Resolution |
---|---|---|
17388344 | The following error was encountered when you tried creating a new version of the UD_BMC process form on Oracle Identity Manager release 11.1.1.x:
|
This issue is encountered if the UD_BMC_PWD process form field has the AccountPassword property set to true, which is not supported in Oracle Identity Manager release 11.1.1.x. This issue has been resolved.
Note: This issue exists if you are using release 11.1.1.5.0 of this connector with Oracle Identity Manager release 11.1.1.x. Therefore, as a workaround, perform the following steps:
See Oracle Fusion Middleware Administering Oracle Identity Manager for release 11.1.1.x for detailed instructions about the procedure. |
17388395 | When two or more support groups are assigned to a user, the Delete Support Group provisioning operation always removed the support group that was first assigned to the user, irrespective of the support group that was intended to be deleted. | This issue has been resolved. |
The following are the software updates in release 11.1.1.5.0:
The Identity Connector Framework (ICF) is a component that provides basic provisioning, reconciliation, and other functions that all Oracle Identity Manager and Oracle Waveset connectors require. The ICF also uses classpath isolation, which allows the BMC Remedy User Management connector to co-exist with legacy versions of the connector. See Section 1.1, "Certified Components".
As this connector is ICF-based:
you can deploy the connector in a Connector Server. See Section 2.2.2, "Deploying the Connector in a Connector Server".
the connector supports connector pooling. See Section 1.5.8, "Connection Pooling".
separate scheduled jobs for performing lookup field synchronization are available. See Section 3.2, "Scheduled Job for Lookup Field Synchronization".
From this release onward, the connector adds support for all target system releases from 7.1 through 8.1.
These target system versions are mentioned in Section 1.1, "Certified Components."
For target system releases prior to the BMC Remedy AR System 7.1, the connector used native APIs to connect to the target system. These native APIs were platform dependent. Therefore, the native libraries from the target system had to be placed in the classpath of Oracle Identity Manager.
From BMC Remedy AR System 7.1 onwards, the target supports the use of pure Java APIs for the connector to establish a connection with the target system. Therefore, this connector (which supports AR System versions 7.1 through 8.1) has no dependency on the native libraries of the target system.
From this release onward, the connector can be installed and used on Oracle Identity Manager 11g Release 2 BP04 (11.1.2.0.4) or later. This Oracle Identity Manager version is mentioned in Section 1.1, "Certified Components."
You can configure transformation of account data that is brought into Oracle Identity Manager during reconciliation. In addition, you can configure validation of account data that is brought into or sent from Oracle Identity Manager during reconciliation and provisioning. See the following sections for more information:
The following sections discuss documentation-specific updates:
The following is a documentation-specific update in revision "7" of release 11.1.1.6.0:
The "Target system" row of Table 1-1, "Certified Components" has been updated to include support to BMC Remedy target system 9.1.
The following is a documentation-specific update in revision "6" of release 11.1.1.6.0:
The "JDK" row of Table 1-1, "Certified Components" has been renamed to "Connector Server JDK".
The following are documentation-specific updates in revision "5" of release 11.1.1.6.0:
The "Oracle Identity Manager" row of Table 1-1, "Certified Components" has been updated.
Information specific to Oracle Identity Manager 11g Release 2 PS3 (11.1.2.3.0) has been added to Section 1.2, "Usage Recommendation."
The following is a documentation-specific update in revision "4" of release 11.1.1.6.0:
A "Note" regarding lookup queries has been added at the beginning of Chapter 4, "Extending the Functionality of the Connector."
The following is a documentation-specific update in revision "3" of release 11.1.1.6.0:
Information about limited reconciliation has been modified in Section 3.3.2, "Limited Reconciliation."
The following are documentation-specific updates in release 11.1.1.6.0:
An example has been added in Step 1 of Section 2.1.1.2, "Copying the External Code Files."
Section 2.3.1.1.6, "Configuring the Password Form Field" has been added.