Upgrade Interchange to B2Bi

This guide is for B2Bi administrators who are responsible for upgrading an existing Interchange installation to B2Bi 2.3.2.

Upgrade paths

If you are upgrading from Interchange 5.10.1 or later, you can upgrade directly to B2Bi 2.3.2 using the B2Bi installer.

IMPORTANT: If you use pluggable transports, prior to the B2Bi 2.3.1 upgrade, B2Bi 2.3.0 must be installed, started, and fully upgraded. You can then upgrade to B2Bi 2.3.1. Failure to do so will cause the 2.3.1 upgrade to fail.

If you have a version of Interchange installed that is earlier than 5.10.1, you must first upgrade to the latest version of Interchange. See Upgrade Interchange to version 5.10.1 or later.

Validated upgrade paths

The following table lists validated upgrades.

Upgrade target Upgrades validated from Interchange version:
Interchange 5.7.1 5.5.1, 5.5.2 and 5.7.0
Interchange 5.8.0 5.5.2, 5.7.0 and 5.7.1
Interchange 5.9.0 5.7.0, 5.7.1 and 5.8.0
Interchange 5.10.0 5.7.1, 5.8.0 and 5.9.0
Interchange 5.10.1 5.8.0, 5.9.0 and 5.10.0
Interchange 5.12.0 5.10 (latest SP), 5.10.1 (latest SP)
B2Bi 2.1.0 5.12.0 (latest SP)
B2Bi 2.2.1 5.10.0 (latest SP), 5.10.1 (latest SP), 5.12.0 (latest SP)
B2Bi 2.3.0 5.10.0 (latest SP), 5.10.1 (latest SP), 5.12.0 (latest SP)
B2Bi 2.3.1 5.10.1 (latest SP), 5.12.0 (latest SP)

About the upgrade process

When upgrading from Interchange to B2Bi, the upgrade process auto-detects and configures settings and prepares the upgraded installation for trading without any additional configuration. This includes the upgrading of clustered Interchange implementations.

B2Bi license requirement

During the upgrade from Interchange to B2Bi, you must specify the path to a valid B2Bi license.

Note   You cannot reuse your existing Interchange license and you must have an updated B2Bi license.

Handling of the common directory

By default, the B2Bi installer uses the directory above the Interchange common directory. During the installation process you can modify the B2Bi common path.

About the "Upgrade from Interchange 5.10.1 or later" option

From B2Bi 2.2.1, during the B2Bi installation process you can select the option: Upgrade from Interchange 5.10.1 or later

  • If you select this option – there is no need for any additional manual actions for the installation phase of the upgrade.
  • If you do not select this option – you must locate the data of your Interchange implementation (\common folder content).
    • If the source install is Interchange 5.10.1 – use the folder that contains the common folder as your share folder location. For example, if your Interchange common is /users/axway/share/common, the share folder for the installer should be /users/axway/share. If a new location is specified, you should copy the contents of the old common into the new one.

    • If the source is an earlier installation of B2Bi – use the same share folder location where the previous B2Bi version is installed. For example, if the common folder is /users/axway/share/common, the share folder should be /users/axway/share. If a new location is specified, you should copy the contents of the old common folder to the new one.

      Tip   To locate the common folder, see the B2Bi installation's filereg.xml.

Handling of trading and application pickups

If an existing Interchange standalone schema is upgraded to B2Bi 2.3.2, the upgrade processing automatically selects the Message processing option of "Limited - only use message handler and community delivery settings" for all trading pickups and "Limited - only use message handler and collaboration settings" for all application pickups.

This ensures that flows continue to work as they did before the upgrade.

Installation of the integration engine

The B2Bi integration engine is automatically installed and does not require an additional license. During the upgrade process you have a certain number of integration engine settings to select. These settings can be modified after upgrade by running the installer in "configure" mode.

Transaction Director

B2Bi does not support Transaction Director. If the existing Interchange installation runs Transaction Director, this feature is removed when upgrading.


The Sentinel Tracked Objects that specify which data is collected for monitoring purposes have been modified in B2Bi 2.3.2 to streamline and improve performance. Be sure to check in Sentinel for any changes in your graph and dashboard reporting outputs. Adjust as necessary.

If you have created any Sentinel filtering plug ins for Interchange, you will need to rebuild them in B2Bi. For information on creating and deploying Sentinel filtering plugins, see the B2Bi Trading Engine Developer Guide.

For details about B2Bi Tracked Object changes for B2Bi 2.3.2, see Sentinel Tracked Objects for B2Bi 2.3.1.

Do you use Integrator?

If you upgrade to B2Bi from an installation in which Interchange operates with Integrator, your existing application integration with the Integrator product will continue to work without any changes after upgrading to B2Bi.

What was called the "integration interface" in previous Interchange versions has now been renamed the "application interface" in B2Bi. This reflects the broader selection of application connectors offered in B2Bi compared to Interchange. The application pickup and delivery exchanges for communication with your existing Integrator environment will still be available, along with many new back-end application connection options.

The B2Bi architecture includes both trading engine (Interchange) and integration engine (Integrator) sub-servers which together provide full embedded trading and application integration processing. You may eventually choose to move your integration logic into the embedded B2Bi integration engine agreement and services model, but you are not required to do this immediately.


  • B2Bi does not support 32-bit platforms.
  • B2Bi does not support the Interchange Secure Web Mailbox. Replacement is SMTP through DMZ (Secure Relay). This replaces the mailbox feature with a DMZ-isolated SMTP connection routing solution.
  • B2Bi does not support Interchange Provisioning Services. To replace these services, use the client REST API interface to replace the Provisions Services UI with the API creation of the equivalent partner objects.
  • The upgrade procedures described in this guide do not apply to existing implementations of:
    • ePedigree
    • EBICS

Related Links