Converting Sterling B2B Integrator .txt silent file to XML (V5.2.6 or later)
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.
You must have the silent file that was used to install your current Sterling B2B Integrator.
You can install or upgrade to Sterling B2B Integrator V5.2.6 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 file, 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:
java -jar SilentFileToXml.jar silent525install.txt silent526install.xml
java -jar SilentFileToXml.jar /home/user/installationFiles/silent5242install.properties
/home/user/installDirectory/silent526install.xml
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.
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 left blank.
- Data keys
cic.selector.os
,cic.selector.arch
, andcic.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 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,
financial.feature,ebics.feature,meigIntegration.feature'
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 (V5.2.6 or later).
user.sb.DB_PASS
user.sb.APSERVER_PASS
user.confirmPassphrase
user.dbconfirmPassword
-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.