B2Bi 2.1.0 Release Notes

Axway B2Bi 2.1.0 Release Notes

Product version requirements

B2Bi 2.1.0 includes the following product versions. Each product is available as a separate installation download:

Axway product Version
B2Bi Server 2.1.0
B2Bi Client 2.1.0
Mapping Services 3.0.1

The following updated Standards Libraries are released with B2Bi 2.1.0:

Standards Library Version
Core EDI 1.3.0
Extended B2B 1.2.0
Financial 3.1.0

Implementations with Axway Database, Sentinel and PassPort require the following versions for compatibility with B2Bi 2.1.0:

Axway product Version
Axway Database 4.6.0
PassPort 4.6.0



Each of the listed service packs is available as an individual download which can be obtained at support.axway.com.

New features and enhancements

New message format / version support

This release of B2Bi provides support for the creation and exchange of the following additional message formats:

  • EDIG@S XML 4.0
  • NACHA 2013
  • X12 7010

New database / version support

This release of B2Bi supports:

  • DB2 10.5
  • DB2 HADR in cluster environments
  • Oracle 12c

For a complete list of supported databases see the B2Bi 2.1 Support Reference Catalog.

Solaris 11.2 validation

This release of B2Bi has been validated for installation on Solaris 11.2. For installation prerequisites and configuration details specific to this platform, see the B2Bi 2.1.0 Installation Guide.

Custom integration support

The B2Bi Integration Manager now extends B2Bi document-processing capabilities to include customized and specialized complex processing patterns. The integrations you build or import and edit in Integration Manager can be seamlessly integrated in the processing flows in B2Bi. In addition to providing more document processing versatility, this tool facilitates the migration of configurations from Integrator V2.

Selective backup and restore of objects

Users can now export and import selected objects from the UI. This is useful if you want to create backups of individual objects or backups of collections of the same type of object. It is also a useful tool for moving selected objects between B2Bi environments of the same version.

FTP message processing in order of consumption

You can now configure FTP external pickups to use the timestamp of the consumed file to determine the message processing order.

HeartBeat node monitoring

B2Bi now delivers the HeartBeat Tracked Object to provide B2Bi node and Secure Relay (DMZ) node status reporting in Sentinel.

Extended processing of inbound documents with errors

The acceptance of inbound documents with errors is now extended to include EDIFACT and XML documents.

Logging of changes made in the user interface by users

You can now generate CVS and XML formatted logs of the changes that users perform in the user interface.

Enhanced overload and failure management

The B2Bi system throttle now automatically engages in situations of integration engine node overload or failure. This automatically suspends the consumption of new messages and the exchange of messages between the trading engine and integration engine, and prevents hard crashes. The throttle remains engaged until the situation has normalized. This suspension of message consumption can also be manually engaged to enable the system to complete the processing of all currently active messages before shutting it down.

Interoperation with WebEDI

You can now configure WebEDI Portal to send and receive EDIFACT messages with B2Bi through a standard interface.

Improved installation of migration transports

Migration transports are now automatically available when selected during installation.

Mapping Services enhancements

The B2Bi Mapping Services development tool now features the following enhancements:

  • 64 bit support - Mapping Services 3.0 is now only available as a 64-bit edition
  • Advanced versioning support (based on SVN)
  • Development team collaboration features
  • Datamapper map support
  • Datamapper support is particularly useful to customers migrating from AMTrix or Integrator. It facilitates the maintenance of all existing maps in a modern mapping tool, including all the new and existing features (versioning, team collaboration support).

New documentation

This release of B2Bi includes the following new documents:

  • B2Bi Getting Started Guide
  • B2Bi / WebEDI Interoperability Guide

Discontinued functionality

The following features have been discontinued in B2Bi 2.1.0:

NFS3 – B2Bi 2.1 supports configurations with an NFS4-mounted shared file system only. Existing customers must update their NFS share to be NFS4 based (instead of NFS3).

B2Bi Server 32-bit support – B2Bi 2.1 is installed only in 64-bit mode.

B2Bi Client (Mapping Services) 32-bit support – From the B2Bi 2.1 release, Mapping Services is installed only in 64-bit mode.

Integration engine JMS adapter – B2Bi 2.1 only supports JMS connectivity when provided through the trading engine. Existing connection configurations based on the integration engine must be updated manually after the upgrade. For more details see the upgrade chapters of the B2Bi Installation and Prerequisites Guide.

Transaction Director - In B2Bi 2.1, Transaction Director is no longer delivered. End-to- end visibility is now provided by Sentinel.

M3/Movex - The M3 Movex connector is not supported in 64-bit environments so is no longer supported in this release.

Synchrony Database 4.4 - Synchrony Database 4.4.0 is not supported with B2Bi 2.1. Users must upgrade to Axway Database 4.6.0.

Persistable event queue – The persistable event queue for Sentinel is no longer supported.

Virtualization support for x86/x64 based systems

Axway generally supports product installation and operation on VMware virtual machine platforms. For B2Bi support cases, Axway will investigate and troubleshoot a problem until it is determined that the problem is due to virtualization. If Axway suspects that a specific defect occurs because the system is virtualized and we cannot reproduce the problem in a non-virtualized environment, we will request you to either reproduce the defect on a non-virtualized environment and to contact the virtualization vendor for a resolution, or to switch to a non-virtualized platform.

Important note for FIPs implementations

This announcement applies to all B2Bi implementations that adhere to the Federal Information Processing Standards (FIPS). In B2Bi, FIPS is a license key-enabled option that turns on FIPS-compliant implementations of certain cryptographic algorithms.

The security provider libraries for FIPS have been updated in B2Bi 2.x. There is now stricter enforcement of the allowable key lengths in RSA Key Pair Generation, aligned with the following excerpt of the requirement. Full NIST requirements are available at:


“This Standard specifies three choices for the length of the modulus (i.e., nlen): 1024, 2048 and 3072 bits. Federal Government entities shall generate digital signatures using one or more of these choices.”

As a result, cryptographic functions that use alternate key lengths (for example 512 or 4096) are blocked while in FIPS mode. This can render trading with existing certificates inoperable, including certificates imported from trading partners. Administrators of existing B2Bi installations or Interchange installations who upgrade to B2Bi 2.x, and who have keys of alternate lengths (512 and 4096 are most common) must do one of the following:

  • Update (import new, or re-generate) any certificates that are not compatible (those not of a 1024, 2048, or 3072 length)
  • Disable the key length enforcement. See Override FIPS key length validation.
  • Caution: Disabling key length validation makes your environment non-FIPS compliant, and non-compliant with the Federal standard. It should only be used as a temporary measure.

Known issues and limitations

Axway Database support

Axway Database is ONLY supported on Linux, Windows and Solaris. For all other operating systems you must use another supported database or change to another operating system when upgrading to B2Bi 2.x.

To enable recovery from possible uninstall issues, make a backup of the system and the database prior to the update to 2.1.

General upgrade limitation

The step from B2Bi 1.5 to B2Bi 2.x represents a major change in the B2Bi product. To ensure a successful B2Bi 1.5-to-2.x transition, Axway recommends that customers follow a well-defined upgrade process managed by the Axway B2Bi Upgrade Team. B2Bi 1.5 customers who wish to upgrade to B2Bi 2.x should contact their Sales Account Representative.

For detailed information about upgrade procedures, download the latest version of the B2Bi 2.1.0 Installation Guide from https://support.axway.com.

Upgrade connector and format limitations

  • MQ connectors – If you are upgrading from B2Bi 1.x and using the integration engine JMS connector, you must replace your pickups and deliveries to trading engine based ones. For detailed information about upgrade procedures, download the latest version of the B2Bi 2.1 Installation and Prerequisites Guide from Axway Sphere at https://support.axway.com
  • CargoIMP – CargoIMP message handling is not supported in B2Bi 2.x.

Upgrade limitation: Message Tracker fails to display message details

After upgrading a B2Bi 1.5 implementation to B2Bi 2.1, Message Tracker no longer displays message-processing details of messages that were processed prior to the B2Bi 2.1.0 upgrade.

Upgrade limitation: Use of trading engine transports on the application side through Message Handler re-routing

If you had a B2Bi 1.5 implementation in which a "U-turn construct" was employed to enable the use the Trading Engine transports on the application side, this logic must be manually reconfigured after the upgrade.

Upgrade limitation: Alternate party in an agreement is used even when an outbound agreement for enveloping is specified

Issue: After upgrading from B2Bi 1.5 to B2Bi 2.x, in some cases trading fails due to the way partner routing ID’s are selected by the upgrade logic.

This occurs when the upgrade logic creates a document agreement inside an inbound agreement, and where the output in the document agreement refers to an outbound agreement for enveloping and also has the “Use alternate delivery partner” option selected. In this case, the Routing ID that is selected is the one that matches with the Messaging ID of the agreement, which leads to errors. The correct Routing ID should be one that reflects the identity that is used by the communication partner.

Resolution: In the B2Bi UI, manually edit each inbound agreement and document agreement, setting the Partner Routing ID to one that belongs to the community on the remote system.

Upgrade limitation: Recreate Secure Relay DMZ nodes

After upgrading from B2Bi 1.5 or 2.0 to B2Bi 2.1 you must remove all DMZ nodes and then recreate and redeploy them in your DMZ. DMZ zones do not need to be recreated.

For a detailed description of how to add Secure Relay Router Agent nodes, see the B2Bi Administrator Guide.

Upgrade limitation: TRADACOMS document version T93 is not available in B2Bi 2.1

After upgrading from B2Bi 1.5 to B2Bi 2.x, 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.

Upgrade limitation: Failure of upgrade from B2Bi 1.5 to B2Bi 2.1.0 with migration pickups/deliveries configured

When migrating from B2Bi 1.5 with migration pickups/deliveries configured, to B2Bi 2.1.0, the server fails to start and an error is thrown to cn.log.

This issue is fixed with Service Pack 4 and later.

EDIFACT rejection rules not applied

When an inbound EDIFACT interchange contains the optional Functional Group level, any configured rejection rules are not applied to the inbound document.

This issue is fixed with Service Pack 4 and later.

Cipher suites fail with secure protocols (FTPS, HTTPS, ...)

The following cipher suites do not function in support of secure protocol connections in B2Bi 2.1: ◦TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384


This issue is fixed with Service Pack 4 and later.

RHEL 6 requirement for X.400 support

By default, the Red Hat Enterprise Linux 6 x86_64 operating system installs without installing a 32-bit library (/lib/ld-linux.so.2) needed by the trading engine X.400 subsystem. To enable B2Bi with X.400 installed on RHEL 6, install the package glibc.i686 from the RHEL installation media.

Passive FTP data connections directed by Secure Relay to wrong trading engine

This issue can be due to the following reasons:

  • A trading engine starts on an existing cluster, after trading engines have been added or removed from the UI configuration. In this case, the sub-range of passive ports defined for the new trading engine's embedded FTP server may not be available on the Secure Relay Router Agent.
  • The workaround is to restart all running trading engine nodes that host the embedded FTP server, on each machine in the cluster. This forces removal of listen ports, and frees the ports in the passive FTP range on the Secure Relay Router Agent machine.
  • The embedded FTP server port ranges of two trading engine nodes overlap.
  • Important: Do not overlap port ranges on more than one embedded server.

Queries for attributes in custom components fail due to attribute name format change

In B2Bi 2.x, the attribute name logic has changed to make the system more versatile and to make the attributes associated to different object types easier to distinguish.

This has a potential negative impact for B2Bi 2. users who rely on the attribute structure implemented in B2Bi 2.0 before SP1.

After upgrading to 2.1, when using custom components that run on the integration engine, and running queries to access the available attributes associated to the message, the queries will fail to return a value if you base the query on the previous naming convention.

In B2Bi 2.x, attribute names conform to the following syntax:



Direction = Inbound or Outbound

Domain = Community, Sender, Receiver, Service, MetadataService, Agreement or DocumentAgreement

Example: Suppose you add an attribute to an inbound agreement with the name Customattribute1 and with value “1”. Before upgrading to B2Bi 2.x, you can retrieve the value of this attribute by referring to the attribute name Customattribute1. After upgrading to B2Bi 2.x, you must change this query to Inbound.Agreement.Customattribute1.

System import limitation: Processing fails on messages that were in "Retry Scheduled" state

In cases where you stop the trading engine node and import a system backup and then restart the node, any messages that were in "Retry Scheduled" state will fail on send attempts after restart. This is because the system import logic modifies the outbound ID of the target exchange partner. These in-process messages that are failed and any existing messages already in a “Failed” or “Delivered” state are now not possible to Resend or Reprocess.

System import limitation: Directory path folders of SFTP/FTP missing after system import in update mode

Issue: If you have any application pickups or community-owned trading pickups that are of the type FTP or SFTP, and you create a system export, when you import the system profile in "update mode" the directory paths are deleted and are not recreated.

Resolution: After system import, manually recreate directory paths. FTP and SFTP paths have the following structures:

FTP trading -


SFTP trading -


FTP application -


SFTP application -


MQSeries 7.x server access

B2Bi 2.x installs updated MQ Series jars. You may need to modify the MQSeries configuration in order to enable an existing MQ 7.x configuration to work after upgrading to B2Bi 2.x.

In some cases, the MQ jars that are updated in SP1 enable additional MQ 7.x security features. Depending on your configuration, you may need to do one or more of the following:

  • Update channel authentication records
  • Add or update authentication or object authorities
  • Add an MQ user to an Interchange MQ exchange point that formerly worked anonymously

Axway recommends that you contact your MQ administrator if problems are noted.

Web Services provider flow: "check input attributes" and "check output attributes" not persisted on B2Bi server

Issue: In Mapping Services, when you create an enumeration in a BusinessDoc leaf (in the Attributes/Enumeration tab), and then use the BusinessDoc in a Flow in which the "check input attributes" and "check output attributes" options are selected, these options are not persisted when you deploy the map to a B2Bi server.

Resolution: You must manually select the "check input attributes" and "check output attributes" options in the B2Bi user interface (Service/Service details/Component details).

MQ/SSL cipher suite selection issues

In the B2Bi user interface, when configuring an IBM MQ Series pickup or delivery exchange with SSL, it is necessary to select the SSL cipher suite to use. The cipher suite that you select must correspond to a specific cipher specification that the IBM server supports. The following table indicates the correct relationship between specification and cipher suite. Additionally, cipher suites preceded by an asterisk (*) are used to connect to a FIPS provider and, although they are displayed, they are not currently supported in B2Bi:

Cipher specification (MQSeries name) B2Bi JSSE cipher suite

* Not currently supported. Do not select this cipher suite.

Failover and sequential delivery

The ability to deliver messages in sequence in the case of a failover is not always guaranteed. This issue will be resolved in a future release.

General Web Services limitations

  • B2Bi 2.x supports Web Services on the trading (partner side), but not on the application side.
  • By default, WS-Addressing must be used in provider mode. To disable the need for WS-addressing, refer to the alternate axis2NoWSAddressing.xml file in your WS pickup configuration.
  • The B2Bi WSDL wizard currently only supports the generation of WSDL definitions. These definitions cannot be edited afterwards. To change the WS interface, you must either regenerate a new WSDL using the wizard, or edit the WSDL manually.

Web Services provider mode HTTP connection fails to close

Issue – When configuring Web Services provider mode for one-way communication with faults returned to client, on the Web Service trading pickup you must normally select the option "Synchronous response generated in backend" in order to enable sending of the fault file to the requesting service consumer. However, if the incoming request message does not trigger a fault and is correctly delivered to the back end, the HTTP connection is kept open until timeout on the client side.

Workaround – For a one-way Web Service provider configuration, do not select the option "Synchronous response generated in backend". This prevents the provider from sending a fault message, but allows the connection to close normally after receiving the client request message.

XSD deployment for Web Services

If a project in Mapping Services contains multiple XSDs and you need to redeploy a single XSD from the project, then all XSDs in that project must be redeployed at the same time.

Web Services provider mode configuration using Mapping Services RouteTo blocks

When a Web Services provider flow with attachments is configured that uses a Mapping Services map with a RouteTo block, B2Bi copies the inbound request attachment attributes onto the output response. This results in the inbound attachments being forwarded back to the originator of the Web Service request.

Workaround – For a one-way Web Service provider configuration, do not select the option "Synchronous response generated in backend". This prevents the provider from sending a fault message, but allows the connection to close normally after receiving the client request message.

PassPort AM integration issue with integration engine tools

When configuring the integration engine with PassPort access management, the B2Bi integration engine client tools lose the ability to distinguish between different levels of user privileges(view/modify/execute). Access to individual tools can either be granted or not granted.

Uninstalling B2Bi in Windows non-service mode

All B2Bi servers must be stopped before B2Bi can be properly uninstalled. In Windows environments when B2Bi components are installed in Windows Service mode, the uninstaller automatically stops all servers before proceeding with the uninstall. However, if you installed the components in manual start mode, you must be sure to manually stop all components before uninstalling.


EBICS is not supported in B2Bi 2.x.


Axway B2Bi is accompanied by a complete set of documentation, covering all aspects of using the product. These documents include the following:

  • B2Bi 2.1.0 Installation Guide
  • B2Bi 2.1.0 Getting Started Guide
  • B2Bi 2.1.0 online help
  • B2Bi 2.1.0 Administrator Guide
  • B2Bi 2.1.0 Operations Guide
  • B2Bi 2.1.0 Support Reference Catalog
  • B2Bi 2.1.0 Security Guide
  • B2Bi 2.1.0 Interchange Upgrade Guide
  • B2Bi 2.1.0 Developer Guide package
  • Axway B2Bi Overview
  • Axway B2Bi Supported Platforms
  • Axway B2Bi Interoperability Matrix
  • Axway B2Bi Concepts Guide
  • Axway B2Bi B2B Reference Solution Implementation Guide

Support services

The Axway Global Support team provides worldwide 24/7 support for customers with active support agreements.
Email support@axway.com or visit support.axway.com.

Copyright © 2015 Axway. All rights reserved


Related Links