| Oracle® Identity Manager Connector Guide for Siebel User Management Release 9.0.4 Part Number E10445-06 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for Siebel User Management Release 9.0.4 Part Number E10445-06 |
|
|
View PDF |
This chapter provides an overview of the updates made to the software and documentation for the Siebel User Management connector in release 9.0.4.8.
The updates discussed in this chapter are divided into the following categories:
This section describes updates made to the connector software.
Documentation-Specific Updates
This section describes major changes made to this guide. These changes are not related to software updates.
The following sections discuss updates made from release 9.0.4 to the current release of the connector:
The following is a software update in release 9.0.4.1:
The xlSiebel.jar file has been split into two files, xlSiebel.jar and SiebelRecon.jar. Corresponding changes have been made in the following sections:
The following are issues resolved in release 9.0.4.1_6713023:
| Bug Number | Issue | Resolution |
|---|---|---|
| 6713023 | User reconciliation and provisioning did not work due to connection failure. | The issue has been resolved. |
The following are issues resolved in release 9.0.4.2:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7014401 | Time zone values that you set during provisioning was not displayed on the target system. | This issue has been resolved. The time zone value is correctly stored during provisioning. |
The following are software updates implemented in release 9.0.4.3:
From Oracle Identity Manager release 9.1.0 onward, the Administrative and User Console provides the Connector Installer feature. This feature can be used to automate the connector installation procedure.
See "Installing the Connector on Oracle Identity Manager Release 9.1.0 or Later" for details.
The following are issues resolved in release 9.0.4.4:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7308907 | Incremental reconciliation failed if the target system database was set to any time zone other than GMT. For example, if the time zone of the target system database was set to GMT+08:00, then incremental reconciliation would fail. | This issue has been resolved. The SiebelDatabaseTimeZone attribute has been added to the Siebel Recon scheduled task. You can use this attribute to specify the time zone of the target system database.
See "User Reconciliation Scheduled Task" for more information about the |
The following are issues resolved in release 9.0.4.5:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7308907 | The connector uses the time stamp stored in the TimeStamp IT resource parameter to identify target system records that must be reconciled. However, daylight savings time was not taken into account. | This issue has been resolved. The DayLightSaving attribute has been added to the SiebelRecon task. You use this attribute to specify the time (in minutes) that must be added to the time stamp.
Sample value: With this sample value, 60 minutes are added to the time stamp stored in the TimeStamp parameter, and the new time stamp is used to identify records that have been created or modified after the last reconciliation run. Default value: Note: The SiebelDatabaseTimeZone attribute of the SiebelRecon scheduled task has been renamed to SiebelServerTimeZone. |
| 7163582 | The following issue was observed when the target system was Siebel 8.0:
In a provisioning operation, if you tried to assign a responsibility to a user who had no responsibilities, then the connection exception was encountered. |
This issue has been resolved. In a provisioning operation, you can now assign responsibilities to a user who does not have any responsibilities. |
| 7561587 | You could not set a primary responsibility to a user through a provisioning operation. | This issue has been resolved. You can now use the PrimaryResponsibility lookup field to set a primary responsibility during provisioning.
See Also: Bug 7703095 in the "Known Issues" chapter for information about an issue related to this feature. |
| 6847114 | On the target system, if a position name was used across more than one division, then only one occurrence of the position name was reconciled into the Lookup.Siebel.Position lookup definition. | This issue has been resolved. Position names are reconciled according to their unique IDs on the target system. The following are sample entries from the Lookup.Siebel.Position lookup definition:
Code Key1: Decode1: Code Key2: Decode2: |
| 7668306 | If a responsibility name reconciled from the target system contained a special character, then that responsibility could not be assigned to a user through a provisioning operation. | This issue has been resolved. Responsibilities whose names contain special characters, except the single quotation mark character ('), can now be assigned to user through provisioning.
Note: A responsibility whose name contains the single quotation mark (') character cannot be assigned to a user through provisioning. This is because the target system cannot search for a responsibility name if it contains a single quotation mark. |
| 7667566 | An exception was encountered if you deleted a user's position through a provisioning operation. | This issue has been resolved. You can delete a user's responsibility through provisioning. |
| 7673332 | A user's status was Inactive even when one or more responsibilities were assigned to the user through provisioning. | This issue has been resolved. If a user has no responsibilities assigned, then the status of the user is set to Inactive. If you assign responsibilities to the user through provisioning, then the status is changed to Active. |
The following are software updates implemented in release 9.0.4.6:
From this release onward, the connector supports Siebel 8.1.1. This is mentioned in the "Verifying Deployment Requirements" section.
The following table describes issues resolved in release 9.0.4.6:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8223113 | When you assign a primary position to an employee through a provisioning operation on Oracle Identity Manager, the change is correctly reflected in the Administration – User module on the target system. However, in the Administration – Group module, the check box designating that the position is primary for that particular employee remains deselected. | This issue has been resolved. The relationship between an employee and a primary position is correctly shown in the Administration – Group module.
The "Assigning a Position to Users" section has been removed from the connector guide. |
The following table describes issues resolved in release 9.0.4.7:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7579522 | When you assigned a primary position to an employee through a provisioning operation on Oracle Identity Manager, the employee became the primary user for the position. When you assigned the same primary position to another employee, this employee became the new primary user for the position. In this way, the primary user of the position kept changing with each assignment of the position. | This issue has been resolved. The first employee to whom the position is assigned remains the primary user of the position. |
The following table describes issues resolved in release 9.0.4.8:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8362522 | The connector did not work correctly if Oracle Identity Manager and Oracle Access Manager both used the same object manager (CommunicationsObjMgr_enu). The following error was encountered during password operations:
|
This issue has been resolved. The connector functions as expected even if Oracle Identity Manager and Oracle Access Manager are using the same object manager.
The |
The following sections discuss documentation-specific updates in the guide:
The following documentation-specific updates have been made in the guide from release 9.0.4.1 through 9.0.4.6:
The external code files for Siebel 7.6, 7.7, and 7.9 have been documented in the following sections:
Copying the Connector Files section
In the "Reconciled Resource Object Fields" section, the following fields have been added:
Extension
HomePhone
WorkPhone
MPosition
Title
The Phone and PersonalTitle fields have been removed from the list.
In the "Importing the Connector XML Files" section, the SiebelServerPort parameter has been renamed to GatewayServerPort.
In the "Partial Reconciliation" section:
All occurrences of givenname have been replaced with First Name.
All occurrences of sn have been replaced with Last Name.
In the "Known Issues" chapter, limitations of the target system have been separated from the known issues of the connector.
The "Creating the Target System User Account for Connector Operations" has been added.
In the "Configuring the Connector" chapter, the "Configuring the Connector for Multiple Installations of the Target System" section has been removed. This feature is not supported by default.
The following documentation-specific updates have been made in the guide for release 9.0.4.8:
The following sections have been added:
In the "Multilanguage Support" section, Arabic has been added to the list of languages that the connector supports.
In the "Verifying Deployment Requirements" section, changes have been made in the "Target systems" row.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
