Converting Sterling B2B Integrator .txt silent file to XML

To install or update to Sterling B2B Integrator V5.2.6 using a silent .txt file from a previous version, you must convert the .txt silent file to the required IBM Installation Manager XML format.

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 update to Sterling B2B Integrator V5.2.6, using the user interface or the silent installation method. To install V5.2.6 by the silent installation method, the silent files must be in XML file in 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 file, you can convert your existing .txt silent file to XML file, by using the SilentFileToXml utility, and make necessary changes to include V5.2.6 specific features. The utility is packaged with V5.2.6 installable.

To convert .txt silent file to XML file by using the SilentFileToXml utility:

Procedure

  1. Go to the folder where you downloaded Sterling B2B IntegratorV5.2.6 package.
  2. Extract the compressed media file.
  3. Open the ResponseFiles > SilentInstallationFileConverter folder and the extract the SilentFileToXml.zip 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
    For more information, see the examples.

Example

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

java -jar SilentFileToXml.jar /home/user/installationFiles/silent5242install.properties /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 install Sterling B2B Integrator V5.2.6. 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:
repository location
Set this to the absolute path of the Sterling B2B Integrator repository that is extracted from Common_Repo.zip.
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 blank.
Data keys cic.selector.os, cic.selector.arch, and cic.selector.ws
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 preceding list.

To include additional features such as, Sterling File Gateway, EBICS, B2B Advanced Communications, 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,financial.feature,ebics.feature,meigIntegration.feature'
Important: The meigIntegration.feature corresponds to Sterling B2B Integrator bridge component, which is required for B2B Advanced Communications.

For more information about the standard response files, file format, and additional features, see Sample response files (V5.2.6.2 or later).

The following parameters must be encrypted (and their original values are encrypted by the utility by default):
  • user.sb.DB_PASS
  • user.sb.APSERVER_PASS
  • 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
NnO7aEXCW36ozr3feBXWTQ==
-bash-3.2$ pwd
/fullpath/IBM/InstallationManager/eclipse/tools
For more information about passphrase encryption, see Installation Manager command-line arguments for silent mode.
Related concepts:
FAQ for Sterling B2B Integrator (V5.2.6 or later)