4.1 Upgrading While Installing Identity Manager 3.5.1

During an Identity Manager 3.5.1 installation, you can install the Driver for JDBC (along with other Identity Manager drivers) at the same time that Identity Manager 3.5.1 is installed. You can upgrade from DirXML 1.1a, Identity Manager 2, or Identity Manager 3 to Identity Manager 3.5.1.

The Identity Manager Driver for JDBC 3.5.1 won’t run on Identity Manager earlier than Identity Manager 3.0.

The Identity Manager Driver for JDBC 2.1 won’t run on Identity Manager earlier than Identity Manager 3.0. To use the Driver for JDBC 2.1, you must upgrade to Identity Manager 3.x.

The Identity Manager Driver for JDBC 2.0 runs on Identity Manager 2.

To upgrade from the Identity Manager Driver for JDBC 1.5 or later to 3.5.1, install the Driver for JDBC 3.5.1. This task replaces only binaries.

You can upgrade from DirXML 1.1a or Identity Manager 2 to Identity Manager 3.

The following tables summarize upgrade paths:

Table 4-1 Upgrading to the Identity Manager Driver for JDBC 3.5.1

If You Are Running This Version

Upgrade to This Version

Before Upgrading to This Version

Driver for JDBC earlier than 1.5

Driver for JDBC 1.51

Driver for JDBC 2.0

Driver for JDBC 1.5 or later

None

Driver for JDBC 2.0

Table 4-2 Upgrading to the Identity Manager Driver for JDBC 2.1 or later

If You Are Running This Version

Upgrade to This Version

Before Upgrading to This Version

Driver for JDBC earlier than 1.5

Driver for JDBC 1.51

Driver for JDBC 2.1

Driver for JDBC 1.5 or later

None

Driver for JDBC 3.5.1

For Identity Manager Driver for JDBC versions earlier than 1.5, you must first upgrade to version 1.5. Refer to the DirXML Driver 1.5 for JDBC Implementation Guide. Be sure to use the 2.1 Association Utility. It supersedes all previous versions.

4.1.1 Backward Incompatibilities

  • The driver now requires a minimum of two database connections for bidirectional synchronization. For additional information, refer to Use Minimal Number of Connections?.

  • The driver now returns schema qualifiers (when available) for logical database class names (parent table or view names). This change doesn’t affect existing configurations unless class names are remapped in Schema Mapping policies. If class names are remapped, all references to class names in existing policy need to be schema-qualified.

  • Slightly alter existing configurations that use views. Set the parameter Enable Meta-Identifier Support to Boolean False. See Enable Meta-Identifier Support?.

  • Slightly alter existing configurations that reference the com.novell.nds.dirxml.driver.jdbc.util.MappingPolicy class. Methods in this class no longer edit the source document. Instead, they return node sets that must be copied into the destination document. The example .xml driver configuration file includes examples of how to do this.

  • Slightly alter existing configurations deployed against DB2/AS400 or other legacy databases that do not implement or support column position. Add and set the Sort Column Names By parameter. To sort column names by string collation order, see Sort Column Names By. The default behavior has been changed to sort column names by hexadecimal value.