What's New in Oracle Identity Manager Connector for Siebel User Management?

This chapter provides an overview of the updates made to the software and documentation for the Siebel User Management connector in release 11.1.1.6.0.

The updates discussed in this chapter are divided into the following categories:

Software Updates

The following sections discuss software updates:

Software Updates in Release 11.1.1.6.0

The following are issues resolved in this release of the connector:

Bug Number Issue

16482094

Entitlement, IT resource, Account Name, and Account ID tagging were missing in the process form fields in Oracle Identity Manager 11.1.2.

16483473

When an access policy was created with DNLA flags for the connector, the policy did not work as expected.

Software Updates in Release 11.1.1.5.0

This is the first release of the Oracle Identity Manager Connector for Siebel User Management based on Identity Connector Framework (ICF). The following are the software updates in release 11.1.1.5.0:

Support for Identity Connector Framework

The Oracle Identity Manager Connector for Siebel User Management is an ICF-based connector.

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 Siebel User Management connector to co-exist with legacy versions of the connector.

See Connector Architecture for more information.

Support for Deployment Using Connector Server

In the earlier releases, the Siebel User Management connector could be deployed in the machine on which Oracle Identity Manager was running. This release onward, you can deploy this connector either locally in Oracle Identity Manager or remotely in the Connector Server.

See the following sections for more information:

Support for Dependent Lookup Fields

In earlier releases, if you had multiple installations of the target system, then entries in a lookup definition were not linked with the target system installation from which the entries were copied. During a provisioning operation, you could not select lookup field values that were specific to the target system installation on which the provisioning operation was to be performed.

From this release onward, entries in lookup definitions are linked to the target system installation from which they are copied.

See Lookup Definitions Synchronized with the Target System for more information.

Transformation and Validation of Account Data

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:

Reconciliation of Deleted User Records

You can configure the connector for reconciliation of deleted user records. In target resource mode, if a record is deleted on the target system, then the corresponding Siebel resource is revoked from the OIM User. In trusted source mode, if a record is deleted on the target system, then the corresponding OIM User is deleted.

See Scheduled Job for Reconciliation of Deleted Users Records for more information about scheduled jobs used for reconciling deleted user records.

Independent Scheduled Jobs for User Records and Deleted User Records Reconciliation

In the earlier releases, you had one scheduled task for configuring your connector for user record and deleted user record reconciliation in both the target resource and trusted source mode.

From this release onward, you have independent scheduled jobs as follows:

  • Siebel Target User Recon

  • Siebel Trusted User Reconciliation

  • Siebel Target Resource User Delete Reconciliation

  • Siebel Trusted User Delete Reconciliation

See Reconciliation Scheduled Jobs for more information about each of the scheduled jobs.

Support for Adding New Siebel Business Objects and Business Components

Depending upon the requirement in your environment, you can add new Siebel Business Objects and Business Components for reconciliation and provisioning. See the following sections for more information:

Support for Configuring the Connector for Multiple Target System Versions

From this release onward, you can configure the connector for target system installations of different versions. See Configuring the Connector for Multiple Versions of the Target System for more information.

Documentation-Specific Updates

The following section discusses documentation-specific updates:

Documentation-Specific Updates in Release 11.1.1.6.0

The following documentation-specific updates have been made in revision "24" of this guide:

The following documentation-specific update has been made in revision "23" of this guide:

Few editorial changes and minor updates to the document structure have been made for better readability.

The following documentation-specific updates have been made in revision "22" of this guide:

The following documentation-specific updates have been made in revision "21" of this guide:

The following documentation-specific update has been made in revision "20" of this guide:

The "Oracle Identity Manager" row of Table 1-1 has been renamed as "Oracle Identity Governance or Oracle Identity Manager" and also updated for Oracle Identity Governance 12c (12.2.1.3.0) certification.

The following documentation-specific updates have been made in revision "19" of this guide:

  • The "Target systems" and "External code" rows of Table 1-1 have been updated to include support for Siebel Innovation Pack 2016.

  • Updated the support for Siebel Innovation Pack 2016 throughout the document.

The following documentation-specific updates have been made in revision "18" of this guide:

The following documentation-specific updates have been made in revision "17" of this guide:

  • The "Connector Server" row has been added to Table 1-1.

  • The "JDK and JRE" row of Table 1-1 has been renamed to "Connector Server JDK and JRE".

The following documentation-specific update has been made in revision "16" of this guide:

A "Note" regarding trusted source IT resource has been added at the beginning of Configuring the IT Resource for the Target System.

The following documentation-specific update has been made in revision "15" of this guide:

Postcloning Steps has been added.

The following documentation-specific updates have been made in revision "14" of this guide:

  • The "Oracle Identity Manager" row of Table 1-1 has been updated.

  • Information specific to Oracle Identity Manager 11g Release 2 PS3 (11.1.2.3.0) has been added to Usage Recommendation.

The following documentation-specific update has been made in revision "13" of this guide:

A "Note" has been added at the beginning of Extending the Functionality of the Connector.

The following documentation-specific update has been made in revision "12" of this guide:

Configuring the Connector to Remove Old Primary Position or Responsibility has been added.

The following documentation-specific updates have been made in revision "11" of this guide:

The following documentation-specific updates have been made upto revision "10" of this guide:

Documentation-Specific Updates in Release 11.1.1.5.0

The following documentation-specific updates have been made in the revision "8" of this guide:

The following documentation-specific update has been made in the revision "7" of this guide:

In Adding New Siebel Business Objects and Business Components for Reconciliation, and Adding New Siebel Business Objects and Business Components for Provisioning, a note has been included on the support of non-account Siebel object in the connector guide.

The following documentation-specific update has been made in the revision "6" of this guide:

Installation includes connector installation scenarios depending on where you want to run the connector code (bundle), either locally in Oracle Identity Manager or remotely in a Connector Server.

The following documentation-specific updates have been made in the revision "5" of this guide: