Installing an Interim Fix

Update your Sterling B2B Integrator V5.2.6 clustered or non-clustered installation with an interim fix.

Complete the following tasks before you apply an interim fix to V5.2.6 installation:
  • Download the latest interim fix image from IBM Fix Central.
  • Extract the package to a folder, go to the media directory and locate the following files:
    • IM_<operating system>.zip in the InstallationManager folder
    • Common_Repo.zip
  • Extract the files to a common directory. After you extract the files, the directory has b2bifixrepo and gmfixrepo as the sub directories.
  • For Linux servers, set the ulimit and language as follows:
    • ulimit -n 4096
    • ulimit -u 16000
    • export LANG=en_US
You can install the interim fix to one node at a time or bring down the entire cluster. Installing the interim fix to one node at a time, does not impact the functioning of the cluster, thereby avoiding any interruption to the transactions and trading partners. Whereas, if you stop the complete cluster, there will be some downtime during which the transactions cannot be processed. You must decide the type of update based on your requirement and considering the update in the interim fix. For example, if the interim fix contains updates to the database or database schema, then you must bring down all the nodes (the complete cluster), apply the fix, and restart the cluster.
Important: If the interim fix contains updates to the database schema, then you must create a backup of the current database before applying the interim fix. If for some reason the update is interrupted or stopped midway, you must manually revert the database changes by using the backup, and then restart interim fix installation. Refer to the download document for details of fixes included in the interim fix.

If Global Mailbox is installed, refer to the following information: Installing an interim fix.

To install an interim fix to Sterling B2B Integrator V5.2.6 and higher by using the user interface:

Important: For information to install a fix pack with a response file, see Installing or updating with a response file (V5.2.6 or later).
  1. Verify that the Sterling B2B Integrator database is up and ready to accept connections.
  2. Based on whether you are stopping a single node or all the nodes (cluster), do one of the following tasks:
    • To stop a single node, go to the \<install_dir>\install\bin (Windows) or /<install_dir>/install/bin (UNIX or Linux) directory, open a command prompt and enter the StopWindowsService.cmd (Windows) or ./hardstop.sh (UNIX or Linux) command. Wait until the perimeter server of the node is completely down before installing the interim fix.
    • To stop the cluster, open the Sterling B2B Integrator user interface (dashboard), and complete the following tasks:
      • From the Administration menu, select Operations > System > Troubleshooting.
      • Click Stop the System.
  3. Perform a full backup of the Sterling B2B Integrator installation directory, including all subdirectories.
    Important: If for some reason the update is interrupted or stopped midway, you must manually revert the changes by using the backed up files, and then restart interim fix installation.
  4. Perform a back up of the database.
  5. If you edited any property files, ensure that the associated properties.in files have the most current changes. Property files are overwritten with the contents of the associated properties.in files during the interim fix installation.
  6. Is the database password encrypted? If Yes, decrypt the password.
  7. Close all command prompt windows.
  8. To start the Installation Manager and provide the path to the input file, type <IIMInstallationDirectory>/eclipse/launcher -input <pathToExtractedFixMedia>/fixInput.xml on the command line for Linux servers or type <IIMInstallationDirectory>\eclipse\launcher -input <pathToExtractedFixMedia>\fixInput.xml for Windows servers.
    Important: You must install an interim fix by using an installed instance of Installation Manager. Therefore, you must launch Installation Manager from the <IIMInstallationDirectory>/eclipse/launcher directory and not from the IM_<operatingsystem> directory.
  9. On the Installation Manager home page, click Update.
  10. On the Update Packages page all the installed packages are listed. Based on the information from the release notes or interim fix notification, select the package that must be updated and click Next. Alternatively, you can select Update all packages with recommended updates and recommended fixes and click Next.
    Wait for the installer to read the updates and resolve references. You can also see information about the installed packages and installation directory on the page.
  11. The packages to be updated are selected by default. Verify the selection, and click Next.

    If there are more than one updates in the repository, the latest update is displayed if you select the Show recommended only option. You can select the recommended repository by using the Select Recommended option.

  12. The features and applications (Sterling B2B Integrator) that must be updated are selected by default. Verify the selection and click Next.

    To see if the current installation or update has any dependencies or pre-requisites, select the Show dependencies check box.

  13. Review the summary information about the updates and click Update.
    Important: You cannot install or remove any of the features listed on this page. However, if you select any feature that was not part of the original installation, an appropriate error message is displayed indicating the same.
  14. Notice the progress of the update and click Finish after the update completes.
  15. Repeat the steps for other Sterling B2B Integrator nodes.
    Attention: For node 2 and higher, you must update the value of REINIT_DB to false. When REINIT_DB is false, database updates are not applied during each interim fix. The REINIT_DB attribute is in the \<install_dir>\install\properties\sandbox.cfg file.
  16. If you stopped the Sterling B2B Integrator cluster, restart the cluster.
    Important:
    • After you apply any Interim Fix to Sterling B2B Integrator, you must manually re-install the b2bAPIs.jar file if a new b2bAPIs.jar file is released with the Interim Fix.
    • If you use the REST APIs, then you must re-install the b2bAPIs.jar file.
To verify the interim fix installation, go to the Rollback panel and check that the appropriate version number is displayed.