Server installer configure mode

After you install a B2Bi Server environment, you can modify many parameters of the installation by running the installer in configure mode.

When you run the installer in configure mode you have access to the original installation pages as well as to additional pages that you can use to fine-tune the B2Bi performance and behavior.

Before you make modifications in configure mode

Stop the B2Bi Server.

Start the installer in configure mode

Windows

  1. In Windows Explorer, go to the root of the B2Bi Server installation directory and right-click ConfigureB2Bi.exe.
  2. Select Run as administrator.

Alternatively, you can:

  1. Go to Start > All Programs > Axway Software > Configure B2Bi.
  2. Right-click Configure and select Run as administrator.

UNIX/Linux

Go to the root of the B2Bi Server installation directory and launch configure.sh.

Safely configure a clustered B2Bi server installation

When you configure your installation, the installer stops and starts the integration engine in the background to perform configuration actions. These starts and stops can potentially create some inconsistencies between the nodes of a multi-node cluster installation.

To safely configure a multi-node B2Bi cluster:

  1. Shutdown node1 and node2.
  2. Configure node1 completely.
  3. Configure node2 completely.
  4. Start node1.
  5. Wait until B2Bi is started and the database is completely updated.
  6. Start node2.

Configure

After you start an installer in configure mode, you use it much as you do in installation mode.

You can work in either in a console display or a graphic interface display (Windows only) to view your current installation settings and modify fields to meet your operating requirements.

Select the elements to configure

You do not need to view all configuration parameters. An initial configuration page enables you to select the product elements that you want to view and optionally configure. Options are:

  • Change database credentials
  • Change server configuration

You can select one or both options.

View and modify parameters

You can configure the following B2Bi Server parameters in configure mode.

Database

  • Change database credentials

Port Range Allocation

  • Minimum value
  • Maximum value

PassPort

  • Use PassPort AM
    • PassPort host
    • PassPort port
    • Shared secret

Farm Client

  • Farm server enabled
  • Farm server host
  • Farm server port

B2Bi Server

  • Number of CPU's – Select the number CPUs of your host machine (2,4,6 or 8). Default = 2.
  • Message size limit for caching message content in memory – Accept displayed value or enter a new cache size value.
  • Use Sentinel – Indicate if you are using Sentinel for B2Bi monitoring.
  • Enable online archive – Select this option if you want to create an online archiving task in the trading engine. This task enables you to view and manage message archives from the Document Tracker tool of the B2Bi System Manager.
  • B2Bi Server SAP connector – Select this option to specify the location of the SAP libraries on your network so that they can be copied by the installer to the B2Bi installation. In most cases your SAP libraries are located here:
  • <SAP_installation_directory>/lib
  • B2Bi SAP exchanges require SAP version 3.0.9 libraries.

B2Bi Core Server Configuration – Select the connectors to activate in your environment.

  • MQ
  • WebEDI
  • SAP ALE
  • FTP
  • File system
  • HTTP
  • Email
  • Secure Transport
  • Enable migration
  • JMS
  • Execute Map as a Service

B2Bi Server SAP connector – Select this option to specify the location of the SAP libraries on your network so that they can be copied by the installer to the B2Bi installation. In most cases your SAP libraries are located here:

<SAP_installation_directory>/lib

B2Bi SAP exchanges require SAP version 3.0.9 libraries.

B2Bi Core Server Configuration – These parameters can only be viewed and modified in configure mode.

  • Use failsafe mode – The fail-safe operation configuration controls how files are written to disk. The files can be written in synchronized or unsynchronized mode:
  • Option selected = Synchronized write to ensure data persistence in case of a system crash. The program that writes to a file on the disk has to wait until the disk acknowledges the physical disk writes. (This involves physically spinning the disk and moving the arm, which is time consuming.)
  • Option not selected = Unsynchronized write, to improve performance: The program that writes to a file on the disk, writes to an O/S buffer. This buffer is emptied/synchronized at intervals, and the overall disk I/O performance is very good. In case of a system crash, there is a risk of losing the contents of the buffer.
  • The recommended setup is to configure the B2Bi integration engine to run with fail-safe operation enabled (synchronized write mode). This guarantees maximum message integrity and overall system consistency.
  • Enable EDIFACT batch file splitter – Enables the use of EDIFACT batches.
  • Enable X12 batch file splitter – Enables the use of X12 batches.
  • Use DML Maps – Enable the use of of DML maps within B2Bi. Enabled by default. You should only clear this option in exceptional cases (for example when migrating environments).
  • Generate acknowledgements for undefined X12 transaction sets – Enables the generation of acknowledgements for non-defined transaction sets for specified partners within your system. Disabled by default.
  • Stop possible duplicates from being reprocessed flag – Messages that transit in B2Bi can potentially be duplicated when the B2Bi system is unexpectedly halted before it can notify a partner system that the communication is completed / confirmed. Use this option to control B2Bi handling of possible duplicates.
  • Option not selected = The integration engine automatically reprocesses completed (but uncommitted) transfers when the system restarts.
  • Option selected = The Integration Engine does not automatically reprocess messages which potentially have been processed already. Instead, it marks these messages as possible duplicates. The system administrator must decide whether or not to retransmit flagged messages manually.

Apply the configuration

When you are satisfied with the configuration settings, click Next to apply changes and update the configuration.

When the installer has finished the configuration cycle, you can close the installer and restart B2Bi.

Related Links