Skip Headers
Oracle® Identity Manager Connector Guide for Database Application Tables
Release 9.1.0

E11194-13
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

What's New in Oracle Identity Manager Connector for Database Application Tables?

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:

Software Updates

The following sections discuss software updates:

Software Updates in Release 9.1.0.5

The following is the software update in release 9.1.0.5:

Support for New Oracle Identity Manager Release

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.

Support for New Target System Versions

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.

Software Updates in Release 9.1.0.4

The following are software updates in release 9.1.0.4:

Support for New Target Systems

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.

Resolved Issues in Release 9.1.0.4

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.


Software Updates in Release 9.1.0.3

The following are software updates in release 9.1.0.3:

Change in Requirement for Oracle Identity Manager

The minimum Oracle Identity Manager requirement for the current release of the connector is Oracle Identity Manager release 9.1.0.1 BP03.

Resolved Issues in Release 9.1.0.3

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.


Software Updates in Release 9.1.0.2

The following are software updates in release 9.1.0.2:

Support for New Target System Versions

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.

Support for Creating a Connector for a Target System with the Autoincrement Option Set on the Primary Key Column

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.

Reconciliation Is Not Specific to the Type of Target System Database

From this release onward, implementation of the reconciliation functionality is independent of the type of target system database.

Resolved Issues in Release 9.1.0.2

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.


Software Updates in Release 9.1.0.1

The following are software updates in release 9.1.0.1:

Support for IBM DB2/UDB Version 9.x on Microsoft Windows, UNIX, and IBM z/OS Platforms

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.

Resolved Issues in Release 9.1.0.1

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.


Documentation-Specific Updates

The following sections discuss documentation-specific updates:

Documentation-Specific Updates in Release 9.1.0.5

The following documentation-specific updates have been made in the revision "13" of the release 9.1.0.5:

The following documentation-specific updates have been made in the revision "12" of the release 9.1.0.5:

The following documentation-specific updates have been made in the revision "11" of the release 9.1.0.5:

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.

Documentation-Specific Updates in Release 9.1.0.4

The following are documentation-specific updates in release 9.1.0.4:

Documentation-Specific Updates in Release 9.1.0.3

The following are documentation-specific updates in release 9.1.0.3:

Documentation-Specific Updates in Release 9.1.0.2

The following are documentation-specific updates in release 9.1.0.2:

Documentation-Specific Updates in Release 9.1.0.1

The following sections discuss documentation-specific updates: