Sample response files (V5.2.6 only)

Sample response files are provided with Sterling B2B Integrator V5.2.6 package. The response files can be modified and used to install Sterling B2B Integrator, Global Mailbox, and its components through silent mode.

A response file is an XML file that contains the data to install the following components:

Sterling B2B Integrator
Global Mailbox
Cassandra
ZooKeeper

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, Global Mailbox, Cassandra, and Zookeeper nodes.

You can also record a response file 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 with Installation Manager.

The following sample response files are packaged with Global Mailbox:

responseFile_GM_Prereqs_V526.xml: Use the file to install Cassandra and ZooKeeper

responseFile_B2Bi_GM_V526.xml: Use the file to install Sterling B2B Integrator and Global Mailbox

responseFile_update_B2Bi.xml: Use the file to update Sterling B2B Integrator 5.2.x to 5.2.6 and also to apply fix packs.

You can use the files to complete the following Global Mailbox related installations, after modifying them to suit your requirements and environment details:

Install ZooKeeper and Cassandra nodes
Install ZooKeeper only or Cassandra only nodes
Install initial Sterling B2B Integrator and Global Mailbox nodes
Install additional Sterling B2B Integrator and Global Mailbox nodes
Install only Global Mailbox or only Sterling B2B Integrator nodes.

Important: The files can be used to apply fix pack (update) your Sterling B2B Integrator and Global Mailbox installation.

Additionally, the following sample response files that can be used to do silent installation of install interim fix (iFix) are also packaged with interim fix packages:

responseFile_iFix_GM.xml
responseFile_iFix_B2Bi_GM.xml
responseFile_iFix_B2Bi.xml

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

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 to the environment where Global Mailbox prerequisites are installed. In addition to that, you must modify values for some parameters based on the following criteria:

Installing initial or additional nodes
Installing nodes on a Global Mailbox topology covering only a single data center
Installing first node in the second or subsequent data centers
Installing Cassandra only or ZooKeeper only nodes

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

Installation scenario	Parameters that must be modified	Must be modified to what?	Why the parameter must be modified?
Installing only ZooKeeper node	`features` Sample response file - responseFile_GM_Prereqs_V526.xml	`features='main.feature,coord.only.feature'`	The default value is `features='main.feature,ds.only.feature,coord.only.feature'`. Modifying it to `features='main.feature,coord.only.feature'`, indicates that only the coordination node, which is ZooKeeper, must be installed.
Installing only Cassandra node	`features` Sample response file - responseFile_GM_Prereqs_V526.xml	`features='main.feature,ds.only.feature'`	The default value is `features='main.feature,ds.only.feature,coord.only.feature'`. Modifying it to `features='main.feature,ds.only.feature'`, indicates that only the data store node, which is Cassandra, must be installed.
Installing Cassandra and ZooKeeper nodes	`user.LocalZookeeperListenInfo` `user.LocalZookeeperListenPort` `user.CassandraListenAddress` Sample response file - responseFile_GM_Prereqs_V526.xml	NA	Specify the port address according to the planned topology.
Installing first Global Mailbox and Sterling B2B Integrator node. Important: The node can be the initial node in the Global Mailbox topology or first node in the second and subsequent data centers.	`user.sb.CLUSTER` `user.CLUSTER_NODE_NUM` Sample response file - responseFile_B2Bi_GM_V526.xml Important: The parameters are specific to Sterling B2B Integrator and are not related to Global Mailbox.	Set `user.sb.CLUSTER` to `false` and do not specify any value for `user.CLUSTER_NODE_NUM`.	Setting `user.sb.CLUSTER` to `false` indicates that the node is not yet clustered and not specifying value for `user.CLUSTER_NODE_NUM` indicates that the node is a single or first node.
Installing second and subsequent Sterling B2B Integrator and Global Mailbox nodes in a data center.	`user.sb.CLUSTER` `user.CLUSTER_NODE_NUM` `features` Sample response file - responseFile_B2Bi_GM_V526.xml Important: The parameters are specific to Sterling B2B Integrator and are not related to Global Mailbox.	Set the following values for the parameters: `user.sb.CLUSTER='true'` `user.CLUSTER_NODE_NUM` - Specify the node number in the cluster (2 or higher) `features='main.feature,additional.mbx.feature'`	Setting `user.sb.CLUSTER` to `true` indicates that the node is part of a cluster specifying value for `user.CLUSTER_NODE_NUM` indicates the node number in the cluster.
Installing Global Mailbox and Sterling B2B Integrator separately Important: If installing separately, you must install Sterling B2B Integrator first, followed by Global Mailbox.	`user.RestAuthUser` `user.RestAuthPass` `user.RestAuthoPassConfirm` Sample response file - responseFile_B2Bi_GM_V526.xml	NA	If you are not installing Global Mailbox and Sterling B2B Integrator together, ensure that values for the parameters match the user name and password of the Sterling B2B Integrator node administrator account. This is applicable when installing initial and additional nodes.
Installing additional Global Mailbox nodes	`features` Sample response file - responseFile_B2Bi_GM_V526.xml	`features='main.feature,additional.mbx.feature'`	The default value is `features='main.feature,initial.external.ds.feature'`. Modifying it to `features='main.feature,additional.mbx.feature'`, indicates that additional Global Mailbox node must be installed. When you change the value of the `features` parameter to replace `initial.external.ds.feature` with `additional.mbx.feature`, the Installation Manager ignores parameters that are not required for installing additional nodes. Therefore, it is not required to comment out parameters that are not applicable to the installation type you are proceeding with. However, when installing second and subsequent nodes in a data center, you must comment out or remove the `user.data.center.aspera.connections` parameter, because Installation Manager does not ignore the parameter if it is present. Important: The `user.data.center.aspera.connections` parameter must not be commented out for the initial node and the first nodes in a data center.
Installing the following optional Sterling B2B Integrator features: Sterling File Gateway FIPS Module AS2 Edition Module Financial Services Module EBICS Banking Server Module B2B Advanced Communications Integration Module	`features` Sample response file - responseFile_B2Bi_GM_V526.xml	You must add the feature name to the `features` parameter. For example, with the following values, you can install the initial Global Mailbox and Sterling B2B Integrator nodes with all the optional features: `features='main.feature,initial.external.ds.feature, filegateway.feature, fips.feature, as2.feature, financial.feature, ebics.features, meigIntegration.feature'`	To install optional Sterling B2B Integrator features.
Installing two nodes of a cluster installation on the same server.	`user.sb.PORT1` Sample response file - responseFile_B2Bi_GM_V526.xml	NA	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.
Database connection information in different data centers when installing initial and additional Sterling B2B Integrator nodes.	`user.sb.DB_CREATE_SCHEMA` `user.sb.DB_USER` `user.sb.DB_PASS` `user.dbconfirmPassword` `user.sb.DB_DATA` `user.sb.DB_HOST` `user.sb.DB_PORT` `user.sb.DB_DRIVERS` Sample response file - responseFile_B2Bi_GM_V526.xml	NA	Modify database connection information to point to the database specific to the data center, where you are installing Global Mailbox and Sterling B2B Integrator nodes. Set the `user.sb.DB_CREATE_SCHEMA` parameter to `true` for the first node in a cluster. For subsequent nodes, set it to `false`.
Installing on different data centers	`user.DataCenterName` `user.StorageBasePath` `user.StoragePassphrase` `user.StoragePassphraseConfirm` Sample response file - responseFile_B2Bi_GM_V526.xml		Specify the correct data center name and storage related information for each data center.
Installing on different local systems with different paths to the system Java location	`user.CassandraZookeeperJavaLoc` `user.sb.JVM_LOC` Sample response file - responseFile_GM_Prereqs_V526.xml	NA	Specify the appropriate Java path

Installing Global Mailbox and Sterling B2B Integrator nodes

Initial Global Mailbox and Sterling B2B Integrator nodes are installed only once in a particular Global Mailbox topology. Installation parameters specific to initial nodes do not differ between data centers or Global Mailbox instances. You must modify the sample response file responseFile_B2Bi_GM_V526.xml with values specific to server where you are installing the initial nodes and also must specify correct values for prerequisite parameters. For information about other parameters that must be modified, see the preceding table.

Upgrading from Sterling B2B Integrator V5.2.x to V5.2.6

When you are upgrading from Sterling B2B Integrator V5.2.x to V5.2.6, 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.

Commenting out Aspera Enterprise Server details

You must comment out or remove Aspera Enterprise Server connection details for the following scenarios:

When installing a single node (non-clustered) Sterling B2B Integrator and Global Mailbox. If it is not commented out or removed, the installation fails because the Aspera Enterprise Server parameter is not ignored for non-clustered installations.
When installing first Global Mailbox and Sterling B2B Integrator nodes in second and subsequent data centers.

Encrypting passwords

You must encrypt values for the following properties by using the imutilsc utility in the <IIM install_dir>/eclipse/tools directory:

user.StoragePassphrase
user.StoragePassphraseConfirm
user.RestAuthPass
user.RestAuthPassConfirm

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>.