| Oracle® Identity Manager Connector Guide for Database Application Tables Release 9.1.0 Part Number E11194-04 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for Database Application Tables Release 9.1.0 Part Number E11194-04 |
|
|
View PDF |
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.2.
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 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 Deployment Configurations" 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" 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 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 RAC implementation, and Sybase Adaptive Server Enterprise 15.0.2 as target systems.
These target systems are mentioned in the "Certified Deployment Configurations" 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" datatype.
This information has been mentioned in the "Known Issues" 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 documentation-specific updates have been made in the guide:
The following sections discuss documentation-specific updates:
In the "Known Issues" chapter, 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 the "Certified Deployment Configurations" section, changes have been made in the "Target systems" and "JDBC drivers" rows.
The following are documentation-specific updates in release 9.1.0.2:
In the "Known Issues" chapter:
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.
The "Modifying Field Lengths of the Provider Parameters" section has been added.
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
