Compatibility
This chapter provides information about compatibility to previous DirX releases.
DBAM database compatibility
Interplatform compatibility of DBAM databases
DBAM databases are not portable between different platforms per design. Also, databases created with an older 32-bit version of DirX Directory are not compatible with any 64 bit version of DirX Directory.
DBAM database compatibility with previous DirX version
The DBAM database structure starting from DirX 8.2B is fully upward compatible with that of DirX 9.1. An upgrade installation is possible without performing any DBAM database conversion procedures.
Due to functional changes, schema extensions and changes in the internal structure of shadowing status and journal files in the DirX server, additional migration steps may be required. Please refer to chapter Upgrade Installation and Database Migration and chapter Upgrade installation in a shadowing environment for necessary migration steps.
Other Compatibility Aspects
DirX V9.1 compatibility with previous DirX releases is detailed in the matrix below.
| DirX Version | X.500 Protocols DAP DSP DISP |
Protocol rpc(1) | Shadowing Agreements | Configuration | Scripts |
|---|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(1) rpc is used for the communication between dirxadm or DirX Manager and the DirX Servers and for signalling purposes between ldapserver and DSA.
The user password attribute is per default single-valued. It is possible to extend the schema in order to make it multi-valued.
PreferredDeliveryMethod Attribute in ldap protocol: According to RFC 4517 the output of PreferredDeliveryMethod attribute values as ldap strings contain the sequence " $ " to separate the elements of a delivery method attribute. Former versions used the '$' character only. As input DirX accept both forms.
The format of DSA audit and LDAP audit files has been changed. Evaluation of audit log files is only possible with the actual dirxauddecode or dirxaudstatistics tool.
In V9.0 automatic verification of binary backups was introduced. As it’s described in the new features list, in V9.0 and later versions, unverified backups, erroneous backups and backups verified by an older product version cannot be loaded. Before loading a binary backup, created by an older product version, it must be verified by the current version of dbamverify. As new checks are usually introduced in new product versions, a verification done with an older version is not considered fully verified. Due to this, if there is a backup created with an older product version, then it must be fully verified (including all components) with the new version, even if it was previously verified with the older version.