Converting Sterling B2B Integrator .txt silent file to XML

You must convert your .txt silent file to XML file in a format that can be used for installing with Installation Manager, to install or upgrade to Sterling B2B Integrator using the response file method if you want to reuse the contents of the .txt silent file.

Before you begin

You must have the silent file that was used to install your current Sterling B2B Integrator.

About this task

You can install or upgrade to Sterling B2B Integrator 6.0 using the user interface or the response file method. To install using a response file, the file must be in an XML format that can be used for installing with Installation Manager. You cannot use the .txt silent files, as the Installation Manager does not support it. Instead of re-creating the silent file in XML format, you can convert your existing .txt silent file to XML file, by using the SilentFileToXml utility. The utility is packaged with Sterling B2B Integrator.


To convert a .txt silent file to an XML file by using the SilentFileToXml utility, complete the following steps:

  1. Go to the folder where you downloaded the latest version of Sterling B2B Integrator.
  2. Extract the compressed media file.
  3. Open the ResponseFiles\SilentInstallationFileConverter folder and extract the file.
    The following contents are extracted:
    • plugins - A folder which contains libraries that are required by the utility.
    • SilentFileToXml.jar - The utility JAR file.
    • SilentFileToXml_README.txt - A readme file with information and details about the utility.
    Important: The plugins folder and the JAR file must be in the same directory, at the same level.
  4. Open a command prompt.
  5. Type the following command to run the JAR file in the following format:
    java -jar SilentFileToXml.jar <input-properties-file> <output-xml-file>
    • <input-properties-file> is the file to be converted from the .txt format to XML.
    • <output-xml-file> is the new file in the XML format


java -jar SilentFileToXml.jar silent525install.txt silent526install.xml

java -jar SilentFileToXml.jar /home/user/installationFiles/ /home/user/installDirectory/silent526install.xml

What to do next

After running the utility, the XML file that is created might not have all the entries that are required to upgrade Sterling B2B Integrator to the latest version. Therefore, you must manually add the new entries to the XML file.

Following is a list of the entries that must be added or modified in the XML file:
Table 1. Entries to be modified
Parameter Description
repository location Set this to the absolute path of the Sterling B2B Integrator repository that is extracted from
Variable sharedLocation Set this to the absolute path of the IBMIMShared directory. It typically is in a path of the following form: /home/your-username/IBM/IBMIMShared/
Data key user.CLUSTER_NODE_NUM If you are installing node 2 or higher of a clustered Sterling B2B Integrator system, enter in the cluster node number to this property. If you are not, this value can be left blank.
Data keys cic.selector.os, cic.selector.arch, and For information to determine correct values for these entries, see Command-line arguments for the imcl command.

It is not required to modify the properties that are given by <preference name=...>, nor any <data key=...> property not given in the above list.

To include additional features such as Sterling File Gateway, EBICS, and B2B Advanced Communications integration module, add the features to the list of features to install in the <offering profile=..."> section. For example, features='main.feature,filegateway.feature,fips.feature,as2.feature,

Important: The meigIntegration.feature corresponds to B2B Advanced Communications bridge component for Sterling B2B Integrator.

For more information about the standard response files, file format, and additional features, see Sample response files.

The following parameters must be encrypted (and their original values are encrypted by the utility by default):
  • user.confirmPassphrase
  • user.dbconfirmPassword
If you modify the passphrase in the new file, password encryption can be done with the following command:
-bash-3.2$ ./imutilsc encryptString Password
-bash-3.2$ pwd
For more information about passphrase encryption, see Installation Manager command-line arguments for silent mode.