Post-upgrade procedures

After you upgrade to B2Bi 2.3.1, check your B2Bi installation and perform the procedures that are detailed in this chapter, as required.

This topic is divided into two main sections:

Procedures for all upgrades

View install logs

After you run the installer:

Check the <B2Bi_install_directory>\install.log (UNIX: /opt/axway/install.log) for ERROR and WARN entries. For critical errors that cannot be solved, contact Axway Support for assistance.

After you start B2Bi:

When you start B2Bi, detailed information about the update processing is written to the file <machine_name>_cn.log. This file is located in <B2Bi_installation_name>\Interchange\logs\.

Validate the B2Bi engines

Recommended: Activate the Tail command so that you can monitor log entries in real time.

  • For UNIX: tail -f Interchange/logs/<hostname>_cn.log
  • For Windows download tail.exe from:
  • http://www.microsoft.com/en-us/download/confirmation.aspx?id=17657
  1. Start B2Bi:
    • UNIX: ./B2Bi start
    • Windows: B2Bi start
  2. Wait for the database upgrade to finish completely. When the database is built, a completion message is displayed.
  3. Validate the Integration Engine.
    • Inspect logs located in the directories:
    • <B2Bi_install_directory>/Interchange/data/log/*
    • <B2Bi_install_directory>/Interchange/data/trace/<8 or 9>/t*
    • Connect to the B2Bi System Manager: All Programs > Axway Software > [B2Bi_client_installation_name] > B2Bi Tools > B2Bi System Manager
  4. Connect to the B2Bi Server UI.
  5. Navigate to the System Management page. The first time you start B2Bi, you will see that no processing nodes (Trading Engine or Integration Engine nodes) exist. At this point, no unexpected pickup and processing can occur.
  6. Make a backup copy of <hostname>_cn.log to conserve the upgrade execution details. The <hostname>_cn.log is recycled automatically so the initial build information will eventually be overwritten.
  7. Navigate through the configuration and do a cursory inspection. For example, check pages such as Agreements, Services, Components, Delivery and Pickup exchanges, and so on.
  8. Click Start all nodes. Confirm that all nodes start. The displayed status for the Trading Engine nodes should be “Running”. The displayed status of Integration Engine nodes should be “Started”.
  9. Process some test messages to validate the upgraded configuration. Monitor logs and traces.

Set the output option for components

B2Bi 2.3.1 provides the following new message processing features:

Post-detection processing step

Post detection is a type of processing step that you can add to a service. The post-detection step enables you to apply processing after message detection but before any mapping is applied.

As for other types of processing steps, the actual processing code for a post-detection step is provided by a component resource.

Post upgrade procedure:

When you apply the B2Bi 2.3.1 upgrade, the upgrade logic does not analyze and correctly set the new option for components that use an MBC modifier or a JMC modifier resource. For this reason you must execute the following procedure after you upgrade:

  1. Open a session in the B2Bi user interface.
  2. Go to Processing configuration > Manage components to open the Manage components page.
  3. Open a component that uses an MBC modifier or a JMC modifier resource.
  4. If the component resource is not of the Map type, select the option Copy input message if no output created.
  5. Click Save changes.
  6. Repeat this procedure for each component that uses an MBC modifier or a JMC modifier resource.

Redeploy DML maps

If you migrated DML maps from a previous B2Bi version to B2Bi 2.3.1, the *_cnlog file will contain error entries that indicate missing maps. To correct these errors, you must redeploy all DML maps from Mapping Services to the B2Bi server.

Recompile Datamapper maps

If you migrated Datamapper maps from any of the following products to B2Bi 2.3.1, you must recompile the maps after completing the upgrade or migration procedure:

  • B2Bi 1.5
  • B2Bi 2.0
  • AMTrix
  • Integrator

Manually update JMS connectors

The integration engine JMS connector which existed in earlier versions B2Bi no longer exists in B2Bi 2.3.1.

If you migrate from an earlier version of B2Bi, and in that version you had an Integration Pickup of the type Synchrony Messaging, when you open the same pickup in version 2.3.1 a warning is displayed indicating the application does not exist on integration engine.

The following entries related to the JMS connector migration failure are written to the trace log on server startup:

To correct the JMS connector configuration:

  1. Open a session in the B2Bi 2.3.1 user interface.
  2. From the lists of Community Application Pickups and Application Deliveries, locate any migrated integration JMS Pickups or Deliveries. You can confirm non-migrated Pickups and Deliveries by opening them and viewing any error messages.
  3. Delete the JMS Pickups or Deliveries that have failed migration.
  4. Create a new application JMS Pickup or Delivery, selecting the JMS option in the wizard.
  5. The JMS option in the Exchange Wizard.
  6. Repeat the preceding steps for each migrated integration engine JMS Pickup or Delivery exchange.

Verify JRE compliance of inline processors

All inline processors that you redeploy after upgrading to B2Bi 2.3.1 must be compliant with JRE7 (or later version if installed).

Update user-defined criteria in Metadata Profiles

During the upgrade process, the upgrade logic does not update the user-defined criteria of Metadata Profiles. After you complete the upgrade:

  1. Go to B2BI_SHARED_LOCAL/config/b2bx/server.
  2. Open the file metadata_attributes.cfg in a text editor.
  3. Manually change the criteria in each affected Metadata Profile.
  4. Save the file.

Edit jvmArgumentsments.xml file

If in version B2Bi 1.5 (trading engine version 5.10.x) you updated the jvmArguments.xml file, located in “<B2BI_install_directory>/conf/, after upgrading the product you must repeat any changes you made in the file before the upgrade.

Update Message Builder database interface settings

After upgrading, if you used, or intend to use, a database interface through Message Builder code, you must move any unused database interfaces that are located in CORE_ROOT/4edi/dbload/ to the subfolder disabled/.

Update SAP JCO libraries

If you upgrade from a B2Bi 1.5 configuration that includes an ALE connector, it is recommended that you update the SAP JCO libraries to version 3.0.9.

Procedures for upgrades from B2Bi 1.5

The following procedures are required only following upgrades from B2Bi 1.5.

B2Bi 1.5 upgrades: Manually reconfigure integration engine exchanges

In B2Bi 2.3.1, integration pickups and deliveries have been merged with application pickups and deliveries. After upgrading from B2Bi 1.5 to B2Bi 2.3.1, pickup and delivery exchanges are presented in single list views. When you open migrated integration-engine owned application pickups and deliveries, a warning is displayed indicating the application does not exist on integration engine.

It is recommended that you migrate the pickups and deliveries based on the protocols in the integration engine to pickups and deliveries based on the trading engine using the following procedures:

Step 1 - Activate the integration engine protocols through the installer

  1. Start the B2Bi 2.3.1 Installer in Configure mode. Go to the B2Bi installation directory, and launch:
    • Unix: ./configure.sh
    • Windows: ConfigureB2Bi.exe.
  2. Click or select Next
  3. Click Next (Select products).
  4. Select the Integrator product.
  5. Click Next (PassPort AM Configuration). The installer displays a message warning you to stop all products before the update.
  6. Click OK to continue.
  7. Click Next (B2Bi Core Server Configuration).
  8. Select the communication adapters(s) you need to enable (by selecting the number) and set the value to 1 to enable.
  9. Click Next.
  10. Click Next.
  11. Click Configure.
  12. The Installer enables the selected (and licensed) integration communication adapters.

Step 2: Validate and confirm the integration engine application pickups and deliveries

  1. Open a session in the B2Bi 2.3.1 user interface.
  2. From the lists of Community Application Pickups and Application Deliveries, locate any migrated Integration Pickups or Deliveries. You can confirm non-migrated (erroneous) Pickups and Deliveries by opening them and viewing any error messages.
  3. Delete each integration engine Pickup or Delivery that has failed migration.
  4. Create a new Application Pickup or Delivery, selecting the correct application transport type in the wizard.
  5. Save the Application Pickup or Delivery.
  6. Repeat the preceding steps for each migrated integration engine Pickup or Delivery exchange.

Step 3 (optional): Replace the integration engine Application Pickups and Deliveries with trading engine Pickups and Deliveries

It is recommended to use the trading engine communication adapters whenever possible.

  1. Delete the "old" integration engine application Pickup or Delivery.
  2. Create a new Application Pickup or Delivery, selecting the correct application transport type in the wizard.
  3. This creates trading engine type exchanges in place of the obsolete integration engine type exchanges.

This method does not apply to JMS connector configurations. The integration engine JMS connector which existed in earlier versions B2Bi no longer exists in B2Bi 2.2.x. See the following procedure for details.

B2Bi 1.5 upgrades: Recreate MQ Series application pickups

After the upgrade from B2Bi 1.5 to B2Bi 2.3.1, the MQ pickups in the export and database dump are missing values for the "Coded character set ID". B2Bi cannot create MQ pickups without this data. The defect in the MQ pickups blocks all pickups from being broadcast to the B2Bi integration engine.

B2Bi supports MQ only from versions 2.1.0 SP3 and later.

  1. After upgrading to 2.3.1 , start the B2Bi trading engine. This also starts the B2Bi integration engine. Starting these engines enables the broadcasting of pickups to the integration engine.
  2. Delete the MQ pickups.
  3. Re-add the MQ pickups. You can either add them through the B2Bi UI, or import them from a backup.
  4. The pickups are automatically broadcast to the integration engine when they are added or imported, along with all other missing pickups.

B2Bi 1.5 upgrades: Confirm X12 and EDIFACT message handling

After upgrading from B2Bi 1.5 to B2Bi 2.3.1, the X12 and EDIFACT messages that are received through application pickups are handled as X12 and EDIFACT (and no longer handled as INHOUSE formats). Be sure to adjust your configuration to adapt to this behavioral change.

B2Bi 1.5 upgrades: Check Routing IDs

During upgrades, B2Bi 2.3.1 Community Messaging IDs (and their associated Routing IDs) are derived from B2Bi 1.5 Messaging Profile Routing IDs.

The data model has changed for B2Bi 2.3.1. During the upgrade process Agreements are now automatically created to represent the relationships between Communities and Partners.

After the upgrade review all Routing IDs in your Agreements for possible errors, and verify the correct exchange partner is referenced.

B2Bi 1.5 upgrades: Check Metadata Profile routing ID references based on EDIFACT message parsing

B2Bi 1.5 does not distinguish between EDIFACT syntax versions and related routing IDs. This distinction is now made in B2Bi 2.3.1. During upgrade from B2Bi 1.5 to B2Bi 2.3.1, the upgrade logic detects the EDIFACT syntax version and applies a routing ID representation based on the syntax version: V3-based IDs contain two colons (example: 1234::), V4-based IDs contain three colons (example: 1234:::).

In the case where the B2Bi 1.5 EDIFACT routing ID is modified during the upgrade, any Metadata Profiles that formerly referred to the old routing ID notation will no longer be correct after upgrading. Working in the UI, you must manually correct all Metadata Profile EDIFACT routing ID references, using the updated EDIFACT-based routing ID as it appears in the Partner or Community configuration.

B2Bi 1.5 upgrades: Recreate VDA document agreements

In B2Bi 1.5 when you create a VDA document profile for a messaging profile, B2Bi does not provide a field for indicating the document version to use. It automatically assumes the document version to be "VDA". "VDA" is not a valid document version for 2.3.1. As a result, after migration to 2.3.1, all of the generated VDA document agreements are in a disabled status.

To enable VDA trading after migration, recreate the VDA document agreements, assigning a valid document version (01, 02, 03, 04).

B2Bi 1.5 upgrades: Reset VDA previous transaction number

VDA message headers contain two transmission numbers:

  • Current number
  • Old transmission number – transmission number used in the previous message to the partner

In 1.5, B2Bi keeps track of the old transmission number, and increments this number by 1 to obtain the current transmission number.

In B2Bi 2.3.1, the new transmission number field is populated by a generator, with a value that can be edited. This generator field for the new transmission number did not exist in B2Bi 1.5.

In general, you should only modify the old transmission number in the UI if it is incorrect for some reason.

When you upgrade, if you want to conserve a VDA transmission number sequence, manually verify the number that is displayed in the UI, and modify as required.

For details on setting the transmission number generator fields, see the B2Bi Administrator Guide, VDA agreements configuration topics.

B2Bi 1.5 upgrades: Correct FTP pluggable exchange spelling

If you have configured migration FTP pluggable transports in B2Bi 1.5 and then upgrade to B2Bi 2.3.1, B2Bi fails to start. This is due to a difference in spelling of the FTP migration transports in the pluggabletransports.xml file.To fix this issue:

  1. Go to <B2Bi_install_directory>/Interchange/conf and open pluggabletransports.xml in an editor.
  2. Change the spelling of the following two entries:
    • Migration FTP Delivery -> Migration FTP delivery
    • Migration FTP Pickup -> Migration FTP pickup
  3. Save the file.
  4. Start B2Bi.
  5. Stop B2Bi.
  6. Open pluggabletransports.xml again in an editor.
  7. Reverse the changes you made in step 2 above:
    • Migration FTP delivery -> Migration FTP Delivery
    • Migration FTP pickup -> Migration FTP Pickup
  8. Save the file.
  9. Start B2Bi.

B2Bi 1.5 upgrades: Manually reconfigure "u-turn" communication between integration exchanges and the integration engine

In B2Bi 1.5 it is possible to use a "U-turn construct" to enable the use of Trading Engine transports on the application side. This involves using the Message Handler to reroute messages between integration pickups and deliveries and the integration engine. If you used this configuration construct in 1.5, you must manually reconfigure the exchanges after the upgrade to B2Bi 2.3.1.

B2Bi 1.5 upgrades: Identify obsolete elements in the user interface

Due to structural changes in the B2Bi data model, certain B2Bi 1.5 configuration elements will be obsolete [duplicated] in B2Bi 2.3.1. After upgrading, these objects appear in disabled status in the 2.2.1 UI.

For details of the changes in the data structure in the user interface, see Changes in data model from B2Bi 1.x to 2.x.

B2Bi 1.5 upgrades: Delete B2Bi 1.5 trading data

The trading data that you collected before upgrading (this data was searchable from the Message Tracker in the

  • For UNIX: tail -f Interchange/logs/<hostname>_cn.log
  • For Windows download tail.exe from:
  • http://www.microsoft.com/en-us/download/confirmation.aspx?id=17657

Related Links