This chapter provides an overview of the updates made to the software and documentation for the SAP CUA connector in release 9.0.4.8.
See Also:
The earlier release of this guide for information about updates that were new for that releaseThe 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 software updates:
The following are software updates in release 9.0.4.1:
There are some changes in the directory structure of the testing utility files. These changes have been made in the "Files and Directories on the Installation Media" section.
In this release, the connector supports Oracle Application Server. Changes related to this software update have been made in the following sections:
Installing the Security Package section
Enabling Logging section
From Chapter 5, "Known Issues", the following item has been removed:
"The connector uses the JCO API that supports JDK 1.4 to communicate with SAP CUA. Oracle Identity Manager supports the Oracle Containers for J2EE (OC4J) release that works on JDK 1.5. Therefore, the connector does not support OC4J."
The following are software updates in release 9.0.4.1_6742861:
In the "Lookup Data Reconciliation" section, the Lookup.SAP.CUA.ChildSystem has been added to the list of lookup definitions.
In the "Reconciled SAP CUA Resource Object Fields" section, the following fields have been added to the list of User Role fields that are reconciled:
StartDate
EndDate
The following are issues resolved in release 9.0.4.1_6742861:
| Bug Number | Issue | Resolution |
|---|---|---|
| 6366964 | An error was thrown if you did not specify values for the User Role or Profile field on the process form. | This issue has been resolved. The User Role and Profile fields have been mandatory fields on the process form. |
| 6409766 | A start date and end date could not be set for an SAP role during a provisioning operation. | This issue has been resolved. During a provisioning operation, you can set a start date and end date for an SAP role. |
| 6359766 | Reconciliation and provisioning failed if you did not specify a value for the User Group attribute. | This issue has been resolved. The User Group attribute is not a mandatory attribute. |
There are no software updates in releases 9.0.4.2 through 9.0.4.3.
The following is a software update in release 9.0.4.4:
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" for details.
The following are issues resolved in release 9.0.4.5:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7644485 | During reconciliation, the time stamp of the Oracle Identity Manager host computer is used to set the time stamp value in the TimeStamp IT resource parameter. This time stamp is used to determine which records must be fetched from the target system during the next reconciliation run.
If the time zone of the Oracle Identity Manager host computer was different from the time zone of the target system host computer, then some records that should have been fetched for reconciliation were not fetched. |
This issue has been resolved. The OIMServerTimeZone attribute has been added in the scheduled task. You use this attribute to specify the time zone of the Oracle Identity Manager host computer.
See "User Reconciliation Scheduled Task" for more information about this attribute. |
| 7418360 | The java.lang.OutOfMemoryError exception was encountered if a provisioning operation involved a large number of users. |
This issue has been resolved. The connector now supports SAP JCo 3.0. The issue is not encountered when you use SAP custom code files provided along with this version of the SAP JCo.
Note: SAP JCo 3.0 replaces SAP JCo 2.0 and SAP JCo 2.1. It requires JVM version 1.5 or later, and it is incompatible with earlier versions of SAP JCo. See "Verifying Deployment Requirements" for information about the required external files. |
The following are issues resolved in release 9.0.4.6:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7652537 | If a single role assigned to a target system user was deleted and the user was then reconciled, the deletion of the role was not reflected on the process form. | This issue has been resolved. If a target system user has been assigned only one role and if you delete that role, then the deletion of the role is reflected on the process form after reconciliation. |
| 6409766 | During provisioning, a start date and end date could not be set for a role assigned to a user. | This issue has been resolved. During provisioning, you can assign a start date and end date to a role assigned to a user. If you do not specify a start date and end date, then the following default values are used:
Start Date: End Date: |
There are no software updates in release 9.0.4.7.
The following are issues resolved in release 9.0.4.8:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7558078 | An error was encountered when you tried to provision the SAP CUA resource to multiple users at the same time | The TimeoutRetryCount and TimeoutCount parameters have been added in the IT resource definition. You use these parameters to specify the delay between consecutive retries of the Add User Role process task. |
| 8398133 | Blank values provided for "from" and "to" date fields while adding/removing roles displays wrong values in SAP. These wrong values are displayed for the machines having (GMT-x) or (GMT+x) timezones. | This issue has been resolved for any timezone. The default dates are set in the target system, if blank values are provided during provisioning of roles. |
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made in releases 9.0.4.1 through 9.0.4.7:
The connector cannot be used with an Oracle Identity Manager installation on OC4J. This point is mentioned in the "Known Issues" chapter. Instructions to enable logging on OC4J have been removed from the "Enabling Logging" section.
The following changes have been made in the "Verifying Deployment Requirements" section:
This section provides information about the permissions to be assigned to the target system user account that Oracle Identity Manager uses to connect to and communicate with the target system. This information has been modified.
Information about the certified Oracle Identity Manager releases has been modified.
The JDK requirement has been added.
The following is a documentation-specific update that has been made in release 9.0.4.8:
In the "Multilanguage Support" section, Arabic has been added to the list of languages that the connector supports.
From this release onward:
The minimum certified release of Oracle Identity Manager is release 9.1.0.1.
The minimum certified release of JDK is release 1.4.2.
See "Verifying Deployment Requirements" section for the complete listing of certified components.