Sample response files (V5.2.6 or later)

Sample response files are provided with Sterling B2B Integrator. The response file is an XML file that can be modified and used to install Sterling B2B Integrator and its features.

You must edit the provided sample response files with information specific to your installation environment. Follow the instructions in the sample response file to replace values that are designated within $$<variable>$$. You can then use the file to install initial and additional Sterling B2B Integrator nodes.

You can also record a response file using the GUI install mode and use the file to install initial and additional nodes. While recording the response file, you can use the skipInstall option to skip actual installation and record the file. For more information, see Recording a response file (V5.2.6 or later).

Response files can be used in either silent or GUI installation modes. In GUI mode, the user interface is prepopulated with the data from the response file.

The following sample response files are packaged with Sterling B2B Integrator:
responseFile_GM_Prereqs_V526.xml
This file is Global Mailbox specific and must be used to install Cassandra and ZooKeeper.
responseFile_B2Bi_GM_V526.xml

Use this file to install Sterling B2B Integrator. It can also be used to install Global Mailbox.

responseFile_update_B2Bi.xml
Use this file to upgrade from Sterling B2B Integrator V5.2.x and to apply fix packs.
Additionally, the following sample response files can be used to install an interim fix:
  • responseFile_iFix_GM.xml
  • responseFile_iFix_B2Bi_GM.xml
  • responseFile_iFix_B2Bi.xml

Sample response files for interim fix installation are located in the ResponseFiles/SampleResponseFiles directory of the interim fix package.

Upgrading from Sterling B2B Integrator V5.2.x

When you upgrade from Sterling B2B Integrator V5.2.x, you can use the sample response file, responseFile_update_B2Bi.xml for reference. You can also use the sample file for reference when installing fix packs.

You must begin by changing your current installation properties file to the XML format response file. For more information about changing your installation properties file to XML format response file, see Converting Sterling B2B Integrator .txt silent file to XML (V5.2.6 or later).

Encrypting passwords

You must encrypt values for the following properties by using the imutilsc utility in the <IIM install_dir>/eclipse/tools directory:
  • user.RestAuthPass
  • user.RestAuthPassConfirm
  • user.sb.DB_PASS
  • user.dbconfirmPassword
To encrypt you must go to the <IIM install_dir>/eclipse/tools directory, type the imutilsc encryptString <string to encrypt> command, and then paste the output as the property value. For example, to encrypt storage passphrase type imutilsc encryptString <passphrase of storage>.

Response file parameters

When using the sample response files or files that you might have recorded, you must modify values for parameters specific to your installation environment and also based on whether you are installing initial or additional Sterling B2B Integrator nodes.

The following table provides details about parameters that must be modified based on your installation scenario:

Remember: You must also modify the variables enclosed in $$<variable>$$ within the response file. Remember to remove the $$ after you modify the variables.
Table 1. Java parameters
Parameters Values Description
user.sb.JVM_LOC   The full path to the location for the JDK.
user.sb.JDK64BIT Default value is true.  
user.sb.JCE_DIST_FILE   The full path for the JCE files.
user.sb.APSERVER_PASS

user.confirmPassphrase

   The system passphrase for Sterling B2B Integrator.
user.sb.DEBUG   Set to true to enable verbose logging.
user.sb.PROCESSORS Default value is 2. The number of processors. You can change this value after installation is completed by using the tuning.properties file.
user.sb.MEMORY Default value is 3072. The memory to allocate. You can change this value after installation is completed by using the tuning.properties file.
user.sb.UPGRADE Default value is false. Set to true to upgrade Sterling B2B Integrator and to use the existing database.
user.sb.LICENSE_FILE Default value is Core_License.xml. License file required for installation.
user.sb.FIPS_MODE Default value is false. Set to true to enable FIPS Module.
user.sb.NIST_MODE Default value is off. To enable NIST mode, set to transition or to strict depending on the required level.
user.sb.INSTALL_SPE_INTEGRATION Default value is false. Set to true to enable SPE integration.

If SPE integration is enabled, you must also provide the values for the user.sb.SPE_INSTALL_DIR, user.sb.SPE_UI_PORT, and user.sb.WTX_INSTALL_DIR.
user.sb.SPE_INSTALL_DIR   The path for the SPE directory. Required only if SPE integration is enabled.
user.sb.SPE_UI_PORT   The port for SPE. Required only if SPE integration is enabled.
user.sb.WTX_INSTALL_DIR   The WTX install directory. This is optional for SPE integration. Clear the value if you do not want to integrate Sterling B2B Integrator with WTX.
user.sb.SI_ADMIN_MAIL_ADDR   Email address to which Sterling B2B Integrator system level notifications should be sent.
user.sb.SI_ADMIN_SMTP_HOST   Port of the SMTP host for the notification email address.
user.sb.DB_VENDOR
  • DB2 (Default)
  • Oracle
  • MSSQL2005 (Use for both SQL Server 2005 and SQL Server 2008)
  • MSSQL2012
 Specify the type of database used by the Sterling B2B Integrator node.
user.sb.CLUSTER Default value is false. When installing the first node, set user.sb.CLUSTER to false and do not specify any value for user.CLUSTER_NODE_NUM.

For node 2 and higher, set to true.

You must also set the node number by using the user.CLUSTER_NODE_NUM parameter.

For node 2 and higher, set user.sb.CLUSTER to true. This indicates that the node is part of a cluster. The value set for user.CLUSTER_NODE_NUM indicates the node number in the cluster.

Important: Be consistent in specifying either IP addresses or fully qualified domain names between the first node and second and subsequent nodes.
user.CLUSTER_NODE_NUM   Specify the node number in the cluster (2 or higher).
user.sb.DB_CREATE_SCHEMA Default value is true. Create the database schema automatically.

Set to true for the first node in a cluster. For subsequent nodes, set to false.
user.sb.DB_USER,   The database user.
user.sb.DB_PASS

user.dbconfirmPassword

   The database password.
user.sb.DB_DATA   The database name.
user.sb.DB_HOST   The database host IP address.
user.sb.DB_PORT   The connection port for the database.
user.sb.USE_SERVICE_NAME Default value is false. The database service name. You must set the value to true to enable the service name for the database.
user.sb.DB_DRIVERS   The location of the database drivers.
user.sb.DB_DRIVERS_VERSION   The driver version of the database driver that is specified in user.sb.DB_DRIVERS.
user.sb.INSTALL_IP   The IP address or host name of the system on which you are installing Sterling B2B Integrator.
user.sb.PORT1   The initial port number for Sterling B2B Integrator. Each node requires a series of 200 port numbers. The difference between the value of user.sb.PORT1 on any two nodes of a cluster installation on the same machine must be at least 200.
user.sb.HOME_DIR   The path for the home directory for the Sterling B2B Integrator installation.
user.sb.REINIT_DB Default value is false. Set to true to refresh the installation after the node is installed. For example, node1=true, node2=false.
features Add the feature name to the features parameter.

For example, features='main.feature, filegateway.feature, fips.feature, as2.feature, financial.feature, ebics.features, meigIntegration.feature'

 Install the following optional features:
  • Sterling File Gateway
  • FIPS Module
  • AS2 Edition Module
  • Financial Services Module
  • EBICS Banking Server Module
  • B2B Advanced Communications Integration Module