B2Bi prerequisites

The following information describes the B2Bi installation prerequisites.

Tip   It is strongly recommended that you close all other programs before proceeding with the installation.


The B2Bi installer automatically installs JRE V1.8.0. You do not have to install a JRE before the solution is installed. B2Bi does not use a shared JVM.



You can only install the B2Bi Client on 64 bit versions of Windows 7, 8.1, and 10.
IMPORTANT: Do not install the B2Bi Client on the same host as the Server.


The following table lists the shared file systems and databases that are supported for each B2Bi-supported operating system:

Operating System Shared file system Databases
Linux 64 bit
  • Oracle Linux 6 and 7
  • Red Hat Linux 6.x and 7.x
  • SUSE Linux Enterprise Server (SLES) 11 and 12

NAS/NFS v4 (Linux ext4)

See NFS requirements and options


SAN: Symantec Storage Foundation Cluster File System (High Availability) 6.0.3

See SAN hotfix requirement







  • IBM DB2 9.7, 10.5
  • Oracle 11g, 12c
  • Microsoft SQL Server 2012, 2014, 2016
  • MySQL 5.6


Windows 64 bit

  • 2008 R2
  • 2012 R1 and R2
  • 2016 R1


  • SMB2 (Windows 2008 R2)
  • SMB3 (Windows 2012 R1 and R2)


See SMB2 / SMB3 client and server configuration requirements

IBM AIX 64 bit

  • 7.x

NAS/NFS v4 (Linux ext4)


See AIX prerequisites and configuration settings

Solaris Sparc 64 bit

  • 11.2

(see prerequisites below)

NAS/NFS v4 (Linux ext4)


See Solaris prerequisites and configuration settings

Windows limitation

For Windows installations, you can install only one instance of B2Bi Server on the same machine with the same Windows user. For multiple installations of B2Bi Server you must install each instance on a different machine.

MS SQL database cluster support

MS SQL Server database clusters (mirroring and failover) are supported from B2Bi 2.2.1 (and later versions). B2Bi supports Failover Clustering. B2Bi has not been officially tested and certified for AlwaysOn Availability Groups.

RedHat Enterprise Linux 7 prerequisite

Installation of B2Bi on Red Hat Enterprise Linux 7.x requires the installation of libXtst.x86_64 and dependencies.

Red Hat Enterprise Linux version recommendation

  • RHEL version 7.x is validated for both performance and failover.
  • The best performance results for RHEL 7.x are obtained using Linux ext4 local file system, rather than xfs (the default local file system).
  • Axway does not recommend installing B2Bi on RHEL 7.0.

Solaris prerequisites and configuration details

  • Variable requirement
  • On Solaris platforms, to deploy maps from the client environment to B2Bi you must unset the environment variable LC_ALL LC_CTYPE using this command:
  • unset LC_ALL LC_CTYPE.
  • Trading Engine node handling
  • On Solaris platforms, you must always add B2Bi trading engine nodes manually. When you import a configuration file that already includes trading engine nodes, after you import the configuration, you must first remove all trading engine nodes and then manually add them again in the user interface System Management page, or use the manageNode tool.
  • NFS with ZFS
  • If NFS is used on top of ZFS, the ZFS mode of the shares must be set to “Latency”. If they are set to “Throughput” performed is seriously degraded.
  • Node time synchronization
  • NTP only allows a step larger than the panic value of 17 minutes once. B2Bi requires all nodes in the cluster to be synchronized to the same time. To ensure proper failover recovery, it is recommended that you set the NTP client’s “wait_for_sync” property to "true" on each node in the cluster, for example:

AIX prerequisites and configuration details

  • Set environment variable
  • To run B2Bi on AIX when an NAS/NFS v4 (Linux ext4) is used as the shared file system, set the following environment variable after you update to B2Bi 2.3.1:
    1. Open $CORE_LOCAL/config/environment.dat.
    2. Add the following line:
    3. Restart the trading engine.
  • Set NFS share mount options
  • If NFS share is used, use the following recommended mount options:
  • rw,bg,hard,intr,vers=4

In AIX, if the installer is executed from a shared file system, set the environment variable INSTALL4J_TEMP to an existing temp directory before the installation. After the installation, that temp directory is deleted.

SAN File System hotfix requirement

In order to run B2Bi on SAN 6.2, you must obtain the VxFS HotFix from Symantec Support and apply the HotFix to each Veritas cluster node.

Windows installation drive and directory access

You must have "Full Control" access permission to the drive and directory where you install B2Bi.

Windows cluster re-synchronization issues

In some cases, B2Bi installations on Windows may experience degraded failover times in the event of a power outage on a node, or a node that never recovers. This can be due to Windows systems failing to resynchronize when rebooting after a hard power failure.

If you experience these issues, Axway recommends that you add a batch file for Windows startup, to run the NET TIME command. The purpose of this command is to synchronize each of the node server times with a network time server.

For example, assume you have a server named TIMESRV that has a reliable system clock. An example batch file would look like this:


Windows SMB2 / SMB3 client configuration requirements for clustered environments

Security rights on the shared directory must be set to "Full Control".

To avoid file locking errors on SMB2 (Windows 2008 R2) and SMB3 (Windows 2012 R1 and R2) platforms, set the following registry values:

  • On the client machine, set the SessTimeout parameter to the recommended value of 240 seconds.
  • Registry path: HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
  • On the server machine, set the SessionKeepAlive registry parameter to the recommended value of 30000 milliseconds (30 seconds).
  • Registry path: HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters
Note   On Windows upgrades to Windows 2012 R1/R2 SMB3: When you upgrade from an earlier Windows OS to Windows 2012 (which uplifts SMB2 to SMB3), double-check these registry settings (even if they were correctly set before the upgrade). The platform upgrade may have reset platform defaults, which can lead to B2Bi restart issues.

RHEL 6 requirement for X.400 support

By default, the Red Hat Enterprise Linux 6 x86_64 operating systems install 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.

NFS v4 requirement

B2Bi supports configurations with an NFS v4-mounted shared file system only. You must update your NFS share to be NFS v4 based (instead of NFS v3) when you use the full B2Bi functionality (including the integration functionality).

If you run B2Bi in communication only mode, it is not necessary to update the NFS v3 share to NFS v4. To avoid issues in particular failover situations, configure the system to not check the availability of the Integration Engine by adjusting the following system property (ui/core/SystemProperties):


Set the value of this property to a couple of years (expressed in seconds, for example, 315360000). This will prevent the trading engines from throttling or shutting down when the system is not running.

NFS4 recommended options

The following are recommended options for configuring NFS4.

Export options:

  • rw
  • insecure
  • no_root_squash
  • no_subtree_check
  • sec=sys
  • no_all_squash

Mount options:

  • rw
  • realtime
  • vers=4.0
  • rsize=1048576
  • wsize=1048576
  • namlen=255
  • hard
  • proto=tcp
  • port=0
  • timeo=600
  • retrans=2
  • sec=sys
  • local_lock=none
Note   Some of these options are NFS defaults, which may differ between Linux versions.

NFS read lease bug - workaround for Linux distributions running kernel version 2.x (2012/11/14)

NFS uses a read lease to guarantee that a client can perform local read opens without informing the server. Axway tests show that under some circumstances this read lease is not updated correctly and causes inconsistency on what the different nodes see on the shared file system. This can cause the nodes in a cluster to stop and restart unexpectedly and repeatedly.

Because this issue is not currently resolved in the 2.x Linux kernel, Axway recommends that you turn off the read lease function on the NFS server. This is done by setting a flag in the /proc/sys file system to tell the kernel to not allow any use of this feature.

The following procedure provides an example of how to set the flag on a Red Hat machine that acts as an NFS server. Similar procedures can be adapted for other distributions.

  1. Important: Stop B2Bi before you perform this procedure.
  2. As root, execute the command:
  3. echo 0 > /proc/sys/fs/leases-enable
  4. Restart the nfs daemon:
  5. /etc/init.d/nfs restart
  6. After you complete the previous steps, unmount and re-mount from the NFS client.
Note   The change implemented by this procedure disappears when you reboot the server. To make this change persistent over machine restarts, add the following lines to a start-up script that is executed before the NFS daemon is started. A good place for this is in /etc/init.d/nfs in the "start" section, after the check for root UID but before the nfsd is started (insertion in bold):

# Only root can start the service

[ $uid -ne 0 ] && exit 4

# Hotfix for the read-leases problem

echo 0 > /proc/sys/fs/leases-enable

SMB 2.x and Windows Server 2008 cache lifetime issue

This issue only applies to the following:

  • Windows 2008 / SMB 2.0
  • Windows 2008 R2 / SMB 2.1

With the releases of SMB 2.0 in Windows Server 2008, and SMB 2.1 in Windows Server 2008 R2, three file metadata caches were implemented to speed up the return of the most recently accessed file and directory information. These caches also reduce the number of interactions a client requires with a SMB server for common file-browsing operations. Axway tests show that this behavior causes inconsistency on what the different nodes see on the shared file system, affecting the stability of the system.

When either SMB 2.0 or SMB 2.1 is the negotiated protocol, the client SMB network redirector uses three different caches.

Cache name, type, ID Description Registry key that controls the cache Default setting
(in seconds)

File Information Cache



File attribute information contained in the File_Network_Open_Information structure


System\ CurrentControlSet\Services\


Details: Use this to conserve network IO when retrieving common file metadata information. To disable (turn off) the caching behavior, set the value of this registry key to 0. It is not recommended to disable the file information cache as it may double the number of network transactions required to execute a given scenario.

File Not Found Cache



Cache of files that the client failed to open because the file was not present on the server


System\ CurrentControlSet\Services\


Details: Use this to prevent the client from repeatedly attempting to open files which are known not to exist on the server. This cache may affect distributed applications that run on multiple computers accessing a set of files on a server - where the applications use an out of band mechanism to signal each other about addition/deletion of files on the server.

Directory Cache



Cache of recent directory enumerations performed by the client


System\ CurrentControlSet\Services\


Details: Subsequent enumeration requests made by client applications, as well as metadata queries for files in the directory, can be satisfied from this cache. The client uses the directory cache to determine the presence or absence of a file in the directory and uses the information to prevent clients from repeatedly attempting to open files which are known not to exist on the server. This cache may affect distributed applications running on multiple computers that access a set of files on a server (where the applications use an out of band mechanism to signal each other about modification, addition, and deletion of files on the server).

Disable all three caches by adding (or changing) the registry keys:

  • Directory cache – Set DirectoryCacheLifetime to ZERO.
  • File Not Found cache – Set FileNotFoundCacheLifetime to ZERO.
  • File information cache – Set FileInfoCacheLifetime to ZERO.

For additional information about SMB redirector cache settings, see the website:

Linux library requirement

For Linux installations, before you install B2Bi, install the following libraries:

  • libXi.so.6
  • libXtst
  • libX11

Fully Qualified Domain Name support

From B2Bi release 2.2.1 forward, you can install the B2Bi Server and the B2Bi Farm Server on Linux/UNIX machines configured with FQDN used as the host name.

FQDNs are not supported on Windows platforms.

AIX / Secure Relay installation requirement

For installations on AIX platforms, both B2Bi Server and Secure Relay must use the same operating system.


For a list of B2Bi supported databases, see Platforms .

For detailed information about database prerequisites and setup for each database type, see Configure databases.

File systems for cluster installations

For additional information about cluster file system organization and requirements see File systems for clusters

Additional Server prerequisites

Product license

  • You must acquire a B2Bi license before you begin the installation procedure.
  • The license file provided for B2Bi 2.3.1 does not work on earlier releases of B2Bi.
  • Older license files do not work on B2Bi 2.3.1 and later versions of B2Bi.
  • Make sure you start the product with the correct license file.

Windows user rights

You must have Administrative privileges to the server to proceed with the installation. On Windows the user should have the "Log on as a Service" privilege for the server installation.

Assign the user that performs the server installation permission to log on to a service:

  1. From the Windows Start menu, select Administrative Tools > Local Security Policy > Local Policies > User Rights Assignment.
  2. Double-click Log on as a service.
  3. Select Add a user or Group.
  4. Type the name that you want to use.
  5. Click OK to validate.

Supported browsers and browser requirements

B2Bi has been tested and validated with the following browsers:

  • Internet Explorer 11.1593.14393.0
  • Internet Explorer 11.0.96
  • Opera 48.0.2685.32
  • Mozilla Firefox 33.0.3
  • Mozilla Firefox 55.0.3
  • Google Chrome:
  • Microsoft Edge: 38.14393.1066.0

Enable JavaScript

JavaScript must be enabled in your browser.

Hardware prerequisites

  • Two dual-core processors or better
  • Minimum 6 GB available RAM
  • Minimum 3 GB free hard drive space (for installation only)

Shared directory path for B2Bi Server

During the installation of the B2Bi Server, you are required to enter the path to a B2Bi shared directory location used for file sharing. You must enter a path to this shared directory using the Universal Naming Convention (UNC).

Tip   Do not use any special characters in directory paths.

MQ Server installation

If you install the B2Bi Server with WebSphere MQ and use the B2Bi connector, it is recommended that you install WebSphere MQ before you install the B2Bi Server. This enables B2Bi to correctly set the PATH variable that points to the IBM WebSphere MQ installation.

If you install WebSphere MQ after you install the B2Bi Server, you must correct the PATH in order to view the MQ connector in the B2Bi user interface, see the post-installation task Activate WebSphere MQ (MQ Series).

Additional Client prerequisites

Hardware Requirements

  • Minimum 1 GB available RAM
  • Minimum 2 GB free hard drive space - for installation only

B2Bi Sentinel prerequisites


Sentinel uses its own database to store tracking data. For a complete list of supported Sentinel data bases, see the Axway documentation site, docs.axway.com.

During the Sentinel installation, you are asked for database access information.

If you use MySQL, before you install Composer and Sentinel, make sure the user who will perform the installation has the MySQL user SUPER privilege.

To grant this privilege, the MySQL database administrator must use the following command:

GRANT SUPER on *.* to 'username'@'hostname';


  • username = the user
  • hostname = the host machine

PassPort hostname resolution

Before you install the optional PassPort product, make sure the hostname is resolved in the host file for the supporting OS.

Example host file entries for hostname resolution are: localhost mycomputer

For information about hostname resolution, refer to:

Server update prerequisite

In B2Bi, tasks on the integration engine (Integrator) are controlled by the trading engine ( Interchange). Before you update B2Bi with a new patch or service pack, stop B2Bi. See Start/stop script.

Related topics

Related Links