Upgrade B2Bi 2.3.1 Server from previous versions

The following information describes how to upgrade from previous versions of the B2Bi Server.

Are you upgrading from Interchange

For upgrades from an Interchange implementation to B2Bi 2.3.1, refer to the B2Bi 2.3.1 Interchange Upgrade Guide.

Do you require assistance

Before starting an upgrade, best practice is determining whether you need help from Axway. Answer the following:

  • Did Axway professional services help in the initial deployment or a previous upgrade?
  • Are you upgrading to a version that is two or more versions later than your current version?
  • Are you upgrading two or more products simultaneously?
  • Have you implemented changes that make your environment atypical or unique?
  • Are you unsure whether in-house resources have the necessary technical expertise?

If you answer "yes" to one or more of these questions, or are unsure, contact your Axway account executive or technical support to discuss options.

Warning on conserving the integrity of B2Bi 2.3.1 after upgrade or migration

After you upgrade to B2Bi 2.3.1, do not attempt to customize the upgraded product by importing binaries or environment variable settings from previous Axway B2Bi or Interchange installations. This type of product modification is very likely to induce product failures.

Upgrades between operating systems / databases / file systems

The lists of operating systems, file systems and databases that are supported for Interchange and B2Bi installations have evolved significantly over the past several years. If your upgrade involves a migration between operating systems, file systems and/or databases, you may require extra steps to adapt the upgrade to the new environment.

URL used for HTTP pickups

When you upgrade B2Bi from one maching to another, the URL used for the partner in the HTTP pickup is not automatically updated to the new hostname. This prevents issues if the load balancer is already set up or if the DMZ in the URL is utilized.

Synchrony Database / Axway Database no longer supported

Neither the Synchrony Database nor the Axway Database are supported for B2Bi 2.3.1. If you are upgrading from an installation that uses either of these databases, you must select an alternative database, for example, MySQL (on which the Synchrony Database and Axway Database are built).

Oracle Database

To support clustered configurations with an Oracle Database, you must configure your Oracle user with the CREATE SEQUENCE permission before you start the server. To do this, execute a command similar to:

GRANT CREATE SEQUENCE TO <my_oracle_b2biUser>

Upgrade paths

For all upgrades, we recommend the assistance of Axway support services.

You can upgrade directly from the following B2Bi versions to B2Bi 2.3.1 using methods described in this document.The following upgrade paths are supported:

  • B2Bi 1.5 to B2Bi 2.3.1
  • B2Bi 2.0 to B2Bi 2.3.1
  • B2Bi 2.1.0 to B2Bi 2.3.1
  • B2Bi 2.2.1 to B2Bi 2.3.1
  • B2Bi 2.3.0 to B2Bi 2.3.1

Scope and impact of the upgrade

To determine if an upgrade is appropriate for your B2Bi implementation and production requirements:

  • Review the B2Bi Release Notes for:
    • New Features
    • Fixed Issues
    • Known Limitations
  • Review information about the new data model introduced in B2Bi 2.0.0, see Changes in data model from B2Bi 1.x to 2.x.
  • Evaluate the effort required for this upgrade. Consider the following:
    • Basic upgrade effort
    • Basic upgrade validation and non-regression testing
    • Particular effort resulting from limitations
    • Particular effort for extended validation and non-regression testing

Warning on upgrade process failures

When you complete an upgrade and then start B2Bi for the first time after upgrade, B2Bi applies an upgrade logic to the database structure. If the database upgrade logic fails at this first product startup, you must restore the previous B2Bi version database content before trying to start the product again (re-triggering the database upgrade logic).

Upgrade B2Bi with Secure Relay

If you are upgrading from a B2Bi implementation in which a Secure Relay DMZ node is used, you must perform the following steps:

  1. Before the upgrade procedure, stop all Secure Relay Router Agent nodes in the DMZ.
  2. After completing the upgrade procedure:
    1. Create new DMZ certificates.
    2. Delete the pre-upgrade DMZ nodes.
    3. Re-create the DMZ.
    4. Export the updated SR node packages from B2Bi.
  3. Deploy and start new Secure Relay Router Agent nodes in the DMZ.
Note   Secure Relay Router Agent nodes now require that Java 1.8 be installed on the supporting DMZ machines.

For details about deployment and configuration of Secure Relay, see the B2Bi Administrator Guide.

Upgrade B2Bi for WebTrader

To upgrade to B2Bi 2.3.1 version and to continue to run in WebTrader standard mode (direct upload) you must obtain a new B2Bi license key. For details on how to use WebTrader, see the Axway B2Bi Administrator Guide.

  • Standard WebTrader (direct upload) mode is enabled based on the following option settings:
    • Option Webtrader = true
    • Option webtraderAppletForLargeFiles = false
    • Option signingUploadApplet = false

Upgrade B2Bi for GDHA WebTrader

To upgrade to B2Bi 2.3.1version and to continue to run in GDHA WebTrader you must obtain a new B2Bi license key. See the Axway GDHA WebTrader Installation Guide for details.

The new B2Bi license key supports two modes, direct upload and user services:

  • GDHA WebTrader Direct (direct upload) mode is enabled based on the following option settings:
    • Option Webtrader = true
    • Option webtraderAppletForLargeFiles = true
    • Option signingUploadApplet = false
  • GDHA Client (User Services) mode is enabled based on the following option settings:
    • Option Webtrader = true
    • Option webtraderAppletForLargeFiles = false
    • Option signingUploadApplet = true

Prepare your upgrade

Inline processor JRE version

All inline processors that you redeploy after upgrading to B2Bi 2.3.1 must be compliant with JRE7 or later.

Upgrade your shared file system mounts to NFS v4

B2Bi 2.3.1 supports configurations with an NFS v4-mounted shared file system only. Existing customers must update their NFS share to be NFS v4 based (instead of NFS v3).

This NFS3 limitation is not a new limitation introduced in 2.3.1. Extensive testing of B2Bi has shown that the use of NFS3 can result in potential recovery issues in case of failover situations.

Custom programs using proprietary data structures

If your pre-upgrade implementation uses any custom programs that depend on access to proprietary data structures, you must modify the programs to conform to the B2Bi 2.x data model. Access to internal proprietary data structures is not supported in B2Bi. Attempts to upgrade with this type of data structure access will likely provoke upgrade failure.

B2Bi 1.5 upgrades: Integration-engine owned application connectors

In B2Bi 2.3.1, integration pickups and deliveries (which were trading-engine owned in 1.5) have been merged with the application pickups and deliveries (which were integration-engine owned in 1.5). After upgrading from B2Bi 1.5 to B2Bi 2.3.1, pickups and deliveries are presented in a single list views of application pickups and deliveries. The integration-engine owned application pickups and deliveries are disabled in B2Bi 2.3.1 by default. Axway recommends that you migrate integration-engine owned pickups and deliveries to trading-engine owned after the upgrade. See B2Bi 1.5 upgrades: Manually reconfigure integration engine exchanges.

B2Bi 1.5 upgrades: Unused processing steps

If your B2Bi 1.5 implementation includes any unused Processing Steps, these objects may be lost during the upgrade project. Make sure that you create a comprehensive configuration backup of your 1.5 implementation before upgrading. This will enable you to manually recover missing objects.

B2Bi 1.5 upgrades: EDIFACT routing ID references in Metadata profiles

If you upgrade from an earlier version of B2Bi, and in that version you had one or more Metadata Profiles that refer to EDIFACT routing ID attributes, after implementing the upgrade you must check your Metadata Profiles to confirm that the EDIFACT routing ID is correctly referenced. See B2Bi 1.5 upgrades: Check Metadata Profile routing ID references based on EDIFACT message parsing.

B2Bi 1.5 upgrades:  TRADACOMS document version T93 is not available in B2Bi 2.3.1

After upgrading from B2Bi 1.5 to B2Bi 2.3.1, the TRADACOMS document version T93 is no longer available for message exchanges. As a result, native TRADACOMS single digit numeric document version values are used by default.

Sentinel Tracked Objects

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

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

Integrator core MBCs

If your B2Bi 1.5 implementation includes any Services that are configured to use "internal" Integrator Message Builder Components in Processing Steps, remove these MBCs from the component registry before applying the upgrade.

Transaction Director

Transaction Director is no longer delivered with B2Bi 2.0 or later.

See Post-upgrade procedures for additional tasks and restrictions.

Related Links