What's New in the Oracle Identity Manager Connector for Siebel Enterprise Applications?

This chapter provides an overview of the updates made to the software and documentation for the Siebel Enterprise Applications connector in release 9.0.4 of the Oracle Identity Manager connector pack.

See Also:

The 9.0.3 release of this guide for information about updates that were new for the 9.0.3 release

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

• Software Updates

  These include updates made to the connector software.

• Documentation-Specific Updates

  These include major changes made to the connector documentation. These changes are not related to software updates.

See Also:

Oracle Identity Manager Release Notes

Software Updates

This section discusses the following software updates implemented in this release of the connector.

Modifying the Primary Position of Users

You can add a position to a Siebel user through provisioning on Oracle Identity Manager. In earlier releases of the connector, the first Position value assigned to a Siebel user would become the primary position of that user. If you were to add another position to the user, then you could not designate the second position as the primary position of the user. This limitation applied to all positions assigned after the first one to the user.

In this release, you can change the primary position of a user through a provisioning operation. This is achieved through the introduction of the Primary Position lookup field in the Siebel Resource form. You use this lookup field to select the primary position from among the positions assigned to a user.

If you have configured trusted source reconciliation with the target system, then changes in the Primary Position value in Siebel are reconciled into Oracle Identity Manager.

In the "Supported Functionality" section, the Primary Position Updated function has been added.

Reconciliation Based on User Type

In this release of the connector, you can use the UserType scheduled task attribute to specify the user type for which reconciliation must be performed. This attribute is discussed in the following sections:

• Reconciliation Based on User Type section

• Specifying Values for the Scheduled Task Attributes section

Partial Reconciliation

The CustomizedReconQuery parameter has been added to the IT resource definition. You can use this parameter to customize the query that the reconciliation module uses to determine the records to be retrieved from the target system. The CustomizedReconQuery parameter is explained in the following sections:

• Defining IT Resources

• Partial Reconciliation

• Testing Partial Reconciliation

Enabling Logging

By following the instructions in the "Enabling Logging" section, you can configure the generation of log information that is specific to the target system.

Changes in the Known Issues List

In the Known Issues list in Chapter 5, the following item has been added:

• The batched reconciliation feature has not been implemented for this connector because Siebel does not support the JDB APIs that are required to implement this feature.

Documentation-Specific Updates

The following documentation-specific updates have been made in this release of the guide:

• Instructions in the "Determining the Release Number of the Connector" section have been revised.

• The "Multiple Trusted Reconciliation" section has been removed from the guide.

• Some of the content from the Chapter 2 of the earlier release of this guide has been moved to Chapter 3.