This chapter provides an overview of the updates made to the software and documentation for the Database Application Tables connector in release 9.1.0.5.
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 software updates:
The following is the software update in release 9.1.0.5:
From this release onward, the connector can be installed and used on Oracle Identity Manager 11g release 1 (11.1.1). Where applicable, instructions specific to this Oracle Identity Manager release have been added in the guide.
See Section 1.1, "Certified Components" for the full list of certified Oracle Identity Manager releases.
From this release onward, MySQL 5.3 and Oracle Database 11g Release 2 (11.2) have been added to the list of supported target systems.
See Section 1.1, "Certified Components" for the full list of supported target systems.
The following are software updates in release 9.1.0.4:
From this release onward, MySQL 5.1.30 has been added to the list of certified target systems.
This target system is mentioned in the "Certified Components" section.
The following are issues resolved in release 9.1.0.4:
| Bug Number | Issue | Resolution |
|---|---|---|
| 9563242 | In the earlier release, JDK 1.6 was required to run the connector. This JDK version was not the same as the JDK version required for Oracle Identity Manager release 9.1.0.1, which was the minimum Oracle Identity Manager requirement for the connector. | This issue has been resolved. From this release onward, the JDK requirement is JDK 1.5. |
The following are software updates in release 9.1.0.3:
The minimum Oracle Identity Manager requirement for the current release of the connector is Oracle Identity Manager release 9.1.0.1 BP03.
The following are issues resolved in release 9.1.0.3:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8843835 | If you were using Sybase Adaptive Server Enterprise as the target system, then the connector did not support child table views. | This issue has been resolved. The connector now supports child table views on the Sybase Adaptive Server Enterprise target system. |
| 8666410 | On the Step 3: Modify Connector Configuration page of the Administrative and User Console, data types of all target database columns were set to String by default. The actual data types of these columns were ignored. | This issue has been resolved. The actual data types of the columns are now displayed on the Step 3: Modify Connector Configuration page. |
The following are software updates in release 9.1.0.2:
From this release onward, the connector adds support for Microsoft SQL Server 2008, Oracle Database 10g, 11g as Oracle RAC implementation, and Sybase Adaptive Server Enterprise 15.x as target systems.
These target systems are mentioned in the "Certified Components" section. In addition, the JDBC drivers required for the new target systems are also mentioned in this section.
Note:
If you are using Sybase Adaptive Server Enterprise as the target system, then this connector does not support child table views.If you are using Microsoft SQL Server 2008 as the target system, then this connector does not support the Date data type.
This information has been mentioned in the "Known Issues, Workarounds, and Troubleshooting" chapter.
For information about the JDBC drivers that need to be used for the newly supported target system versions, see the "Copying the JDBC Drivers" section of the connector guide.
For information about the Database URL and Connection Properties parameters for Oracle RAC and Sybase Adaptive Server Enterprise, see the "Database URL and Connection Properties for Oracle RAC" and "Database URL and Connection Properties for Sybase Adaptive Server Enterprise" sections, respectively.
For information about configuring secure communication between Sybase Adpative Server Enterprise and Oracle Identity Manager, see "Configuring Secure Communication Between Sybase Adaptive Server Enterprise and Oracle Identity Manager" section.
From this release onward, you can create a connector for a target system that has the primary key column defined with the autoincrement option. During a Create User provisioning operation, the process form field corresponding to the primary key field is updated after the account is created on the target system. In other words, you need not specify this value on the process form.
The Is Primary Key Auto Incremented parameter has been added to implement this feature. For information about this parameter, see the "Step 2: Specify Parameter Values Page" section.
Note:
If you are using IBM DB2/UDB as the target system and the autoincrement option has been set on the primary key column, then you must install db2jcc4.jar and jdk 1.6.This information has been mentioned in the "Copying the JDBC Drivers" section of the connector guide.
For information about creating a connector for a target system that has a primary key column defined with the autoincrement option, see the "Step 3: Modify Connector Configuration Page" section.
If you are using Oracle Database as the target system, then see the "Configuring Oracle Database" section for information about configuring the target system for this feature.
From this release onward, implementation of the reconciliation functionality is independent of the type of target system database.
The following are issues resolved in release 9.1.0.2:
| Bug Number | Issue | Resolution |
|---|---|---|
| 8282035 | While updating a provisioned resource, an error was encountered if the column names of the target database tables were in lowercase. | This issue has been resolved. No error is encountered while updating a provisioned resource if the target database column names are in lowercase. |
| 8314294 | After the Create User provisioning operation, the account status value for a target system was Null. |
This issue has been resolved. The appropriate account status value is being displayed after a provisioning operation. |
The following are software updates in release 9.1.0.1:
In addition to the databases supported by the earlier release, this release supports IBM DB2/UDB version 9.x running on Microsoft Windows, UNIX, and IBM z/OS platforms.
See "Certified Components" in the connector guide for information about the other target systems. Information specific to IBM DB2/UDB has been added at various places in this guide.
Note:
SSL communication is not supported if IBM DB2/UDB is running on IBM z/OS. This has been mentioned in the "Known Issues, Workarounds, and Troubleshooting" chapter.The following is an issue resolved in release 9.1.0.1:
| Bug Number | Issue | Resolution |
|---|---|---|
| 7622061 | While a connector was being created, the names of target database tables that you specified were changed to uppercase by the generic technology connector framework. If the database was configured to be case-sensitive to table names, then these tables were not found in the database during the connector creation process and the process failed. | This issue has been resolved. During the connector creation process, the table names are not modified. |
The following sections discuss documentation-specific updates:
The following documentation-specific updates have been made in revision "14" of release 9.1.0.5:
The "Oracle Identity Manager" row has been modified in Table 1-1, "Certified Components".
An issue related to running the Evaluate User Policy scheduled job has been added to Section 4.1, "Known Issues and Workarounds".
The following documentation-specific updates have been made in the revision "13" of the release 9.1.0.5:
The name of the "Known Issues and Workarounds" chapter has been changed to "Known Issues, Workarounds, and Troubleshooting." In addition, Chapter 4, "Known Issues, Workarounds, and Troubleshooting" has been restructured.
A problem related to database column type has been added to Section 4.2, "Troubleshooting."
The following documentation-specific updates have been made in the revision "12" of the release 9.1.0.5:
The "Usage Recommendations" section has been removed as the information in that section is not valid.
MySQL 5.5 has been added to the "Target System" row of Section 1.1, "Certified Components."
Section 2.1.7, "Prerequisites for Creating the Connector" has been added.
The "Configuring IBM DB2/UDB Running on IBM z/OS" section has been removed as the connector does not support the use of stored procedures to perform CRUD operations.
Section 2.1.4, "Copying the JDBC Drivers" has been modified.
In Section 2.1.4, "Copying the JDBC Drivers," information about Oracle Database 11g release 2 (11.2) drivers has been added under the "For Oracle Database" list item.
Section 3.6, "Localizing Field Lables in UI Forms" has been added.
The procedure to modify the field length of provider parameters in Oracle Identity Manager release 11.1.1 and 11.1.2.x has been deleted from the Section 3.3, "Modifying Field Lengths of the Provider Parameters."
Section 2.2.4, "Creating Target System User Accounts for Connector Operations" has been added.
The following documentation-specific updates have been made in the revision "11" of the release 9.1.0.5:
The "Oracle Identity Manager" and JDK rows in Table 1-1, "Certified Components" has been modified.
The following sections have been added:
Instructions specific to Oracle Identity Manager release 11.1.2.x have been added as required throughout the guide.
The following documentation-specific update has been made in the revision "10" of the release 9.1.0.5:
In Chapter 4, "Known Issues, Workarounds, and Troubleshooting," the following item has been added:
Bug 10206089
Suppose a target system table has a primary key defined. While configuring a connector, if you designate a column as Unique, then the connector fails.
The following are documentation-specific updates in release 9.1.0.4:
Section 1.4, "Supported Data Types" has been modified.
In Section 4, "Known Issues, Workarounds, and Troubleshooting":
The following items have been removed:
Bugs 6689376, 8841689
The number of characters in the Provider definition fields cannot be more than 200.
The following item has been moved to the limitations section because this issue is a limitation of the target system:
Bug 8854612
If you are using Microsoft SQL Server 2008 as the target system, then this connector does not support the Date data type. A workaround for this issue is to use the DateTime data type.
The following are documentation-specific updates in release 9.1.0.3:
In Section 1.1, "Certified Components," the JDK requirement has been added.
Section 1.4, "Supported Data Types" has been added.
In Section 4, "Known Issues, Workarounds, and Troubleshooting":
The following item has been removed:
Bug 8843835
If you are using Sybase Adaptive Server Enterprise as the target system, then the Database Application Tables connector does not support child table views.
Issues tracked by Bug 8843835 and Bug 8805516 have been added.
The following are documentation-specific updates in release 9.1.0.2:
In Section 4, "Known Issues, Workarounds, and Troubleshooting":
The following item has been removed:
Bug 8282035
If the data type of the primary key column of the target database table is not VARCHAR, then an error is encountered if you try to update a provisioned resource whose data is stored in that target database table.
Issues tracked by bug numbers 8843835 and 8805516 have been added.
Section 3.3, "Modifying Field Lengths of the Provider Parameters" has been added.
The following sections discuss documentation-specific updates:
In Section 4, "Known Issues, Workarounds, and Troubleshooting," the following item has been added:
Bug 8282035
If the data type of the primary key column of the target database table is not VARCHAR, then an error is encountered if you try to update a provisioned resource whose data is stored in that target database table.
In Section 1.1, "Certified Components," changes have been made in the "Target System" and "JDBC drivers" rows.