Creating a response file

Before you can silently install or upgrade Sterling B2B Integrator, you must create a response file. You can create a response file by using one of the sample response files or by modifying a recorded response file.

Note: A response file is only required for silent installation. Skip this step if you are using the IBM Installation Manager GUI for installation.

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.

For more information, see Sample response files and Recording a response file.

Considerations

When you modify the sample response files or files that you might have recorded, consider the following points:
  • Parameters specific to your installation environment.
  • Whether it is a non-clustered or clustered environment.
  • Whether you are installing initial or additional Sterling B2B Integrator nodes.
  • Whether you are updating Sterling B2B Integrator.
  • Server and the environment changes for systems where you install the additional nodes.

Using the response file to upgrade

To upgrade Sterling B2B Integrator, set user.sb.UPGRADE to true and provide the details for the existing database. You must also provide the user.sb.HOME_DIR which is the path for the home directory for the Sterling B2B Integrator installation based on the upgrade scenario that is applicable for your setup.
Table 1. Upgrade scenarios
Upgrade type Options to select during upgrade process
Upgrading from v5.2.6.x and using a new application server user.sb.HOME_DIR is the path for the home directory on the new application server for the Sterling B2B Integrator upgrade.
Upgrading from v5.2.6.x on the same application server but in a different directory user.sb.HOME_DIR is the path for the home directory on the application server for the Sterling B2B Integrator upgrade.

This directory must be different from the directory that was used for the previous installation.
Upgrading from v5.2.6.x on the same application server and the same directory user.sb.HOME_DIR is the path for the home directory on the application server for the Sterling B2B Integrator upgrade.

This directory must be the same as the directory that was used for the previous installation.
Upgrading from v5.2.5.x or earlier and using a new application server user.sb.HOME_DIR is the path for the home directory on the new application server for the Sterling B2B Integrator upgrade.
Upgrading from v5.2.5.x or earlier on the same application server but in a different directory user.sb.HOME_DIR is the path for the home directory on the application server for the Sterling B2B Integrator upgrade.

This directory must be different from the directory that was used for the previous installation.
Upgrading from v5.2.5.x or earlier on the same application server and the same directory user.sb.HOME_DIR is the path for the home directory on the application server for the Sterling B2B Integrator upgrade.

This directory must be the same as the directory that was used for the previous installation.

Response file parameters

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

Important: You must also modify the variables that are enclosed in $$<variable>$$ within the response file. Remember to remove the $$ after you modify the variables.
Table 2. 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