Java Development Kit (JDK) is not installed on IBM AIX operating systems. Install and configure JDK before you install B2B Data Exchange.

Java Cryptography Extension (JCE) is not installed on IBM AIX operating systems. If you use B2B Data Exchange with Managed File Transfer, install JCE before you install B2B Data Exchange.

The archive command line utility does not use the dx.event.status.category.success system property and the dx.event.status.category.failed system property to determine if an event reached a final or an error status. Instead, B2B Data Exchange stores the information in the event status. The archive command line utility determines which events to archive based on whether the event reached a final state, regardless of the error state.

Names and identifiers of custom attributes for partners and accounts are case-insensitive. During the upgrade process, the B2B Data Exchange installer removes all duplicate names or identifiers and the log describes the removal information. The installer does not remove attribute definitions. If you import partners or accounts from earlier versions that contain duplicates, the import process rejects all duplicates and throws an exception.

B2B Data Exchange does not create events for audit records, and does not convert audit trail events from previous versions to enhanced audit records. You can use the archive utility to archive and delete all of the legacy audit trail events before you upgrade. If you keep the legacy audit events from earlier versions, you can view the events after you upgrade in the Legacy Audit Events page. You can also archive the legacy audit events with the B2B Data Exchange Accelerator for Informatica Data Archive or the B2B Data Exchange archive utility after you upgrade.

When an event reconciliation completes successfully, B2B Data Exchange generates a single entry in the

Processing Information

tab of the event details instead of multiple entries for each stage of the reconciliation process.

To improve performance and reduce bottlenecks, B2B Data Exchange creates a temporary file for every incoming file that it processes through Managed File Transfer endpoints in the following folder:

<DXDocumentStore>\mft

. Each file name includes the prefix

dx_

, the name of the incoming file, and the extension

.tmp

. To conserve disk space, periodically delete temporary files that B2B Data Exchange created in the folder at least 24 hours earlier.

You cannot configure session replication for B2B Data Exchange in a cluster environment.

B2B Data Exchange uses the dx.endpoint.jms.provider.url system property to determine if the B2B Data Exchange JMS Broker service is running.

After you upgrade, you cannot view the

Properties

tab of the DX_Generate_Temporary_File transformation. To use this option, delete and re-add the transformation.

In the B2B Data Exchange repository on Microsoft SQL Server, the type of the CORRELATION_IDENTIFIER column in the DX_CORRELATION table is NVARCHAR(255) instead of VARCHAR(255).

In the B2B Data Exchange repository on Oracle and Microsoft SQL Server, the type of the CORRELATION_ID column in the DX_CORRELATION table is NUMERIC(19,0) instead of VARCHAR(255).