Installing or updating with a response file (V5.2.6 or later)

You can use the response files that are recorded when installing or updating Sterling B2B Integrator. You can also use the sample response files that are provided with Sterling B2B Integrator V5.2.6.

Ensure that you have the appropriate response file to use for installing or updating (applying fix pack or interim fix) Sterling B2B Integrator and the databases installed and configured.

Ensure that IBM® Installation Manager is installed. If the userinstc command is run without IBM Installation Manager installed, it does not install or update Sterling B2B Integrator, but installs IBM Installation Manager instead.

A response file is an XML file with configuration information that can be used for installing or updating Sterling B2B Integrator. Most of the configuration details and other information that is required for installing and updating Sterling B2B Integrator nodes are recorded in the response file. However, you must modify values for some parameters based on whether you are installing or updating initial or additional nodes or clustered and non-clustered environments. For more information about parameters that must be modified, see Sample response files (V5.2.6 or later).

Silent installations minimize the requirement to reenter the same information or potential errors while keying in the configuration information. Nevertheless, you must change values of some parameters because the server and the environment where you install the additional nodes might differ.

Upgrade Compatibility (v5.2.6.5 or later)

The system displays an alert message on the console. For more information on the supported upgrade paths, see the Upgrade Compatibility matrix.

When you upgrade to a higher version from a lower version, you cannot use that instance as all the defect fixes from the lower version are not available in the higher version.

For an in-place upgrade, the system displays an alert message on the console and prompts you to proceed with or cancel the installation.

Note: To skip the alert message, you can add a flag, displayVersionCompatibilityAlert in the response file and set it to false. By default, the alert message is displayed.
Important: Because the silent mode allows reuse of most of the configuration and reduces mistakes when manually keying in information on the user interface, using the appropriate response file to install Sterling B2B Integrator is the preferred method, over using the user interface.
To install or update (fix pack or interim fix) Sterling B2B Integrator node using a response file:
Tip: You can record a response file when updating your current installation and use the file to update additional nodes.
  1. Start the 64-bit Installation Manager and provide the command to install using a response file.
  2. Go to the IM_<operating_system> folder and use one of the following commands, if Installation Manager is not installed and you are using the Installation Manager agent provided with V5.2.6, if you installed a 64-bit Installation Manager, or if you have the Installation Manager installed on a platform that has only one download available for Installation Manager. For example, AIX®, Solaris, HP, zLinux, or Windows:
    • ./userinstc input <response_file> -acceptLicense -log <log_file> (AIX, Solaris, HP, zLinux)
    • userinstc.exe input <response_file> -acceptLicense -log <log_file> (Windows)

    For example, on an AIX system, if the response file is located at /response_files and if you want to save the log file in /mylog, type ./userinstc input /response_files/install.xml -acceptLicense -log /mylog/install_log.xml

    Note: If you have installed Sterling B2B Integrator using 32-bit Installation Manager, then:
    • Take a back up of 32-bit installation directory along with the shared folders.
    • Install Sterling B2B Integrator using 64-bit Installation Manager.
    If you have already installed other products, such as DB2, using 32-bit Installation Manager and if you want to update these products, then:
    • Back up using 64-bit Installation Manager.
    • Restore using 32-bit Installation Manager.