Installing a fix pack update

A fix pack update can be run without downtime of the online message interfaces (MCI, IBM MQ, and Kafka). If possible, reduce API activity to case investigation during the update procedure until at least two instances are updated to the new version. Doing so prevents complications during model changes, go-lives, and simulation that are caused by instances that are running on different versions. If postponing model operations is not feasible, you can choose to run model operations all the time but at your own risk.

Before you begin:

1. Go to the Release Notes for the fix pack and read the Update information.
2. Follow the installation instructions up to running the RPM installation package. For more information, see Installation overview.
3. Find out the directories and folders where IBM® Safer Payments is currently installed. You need to know the /binaryPath, /librarypath, and /installationPath/. For more information, see the prerequisites in Running the RPM installation package.

Suggested workflow to install a fix pack update:

1. Disable the online message interfaces (MCI, MQI, and KMI) and incoming FLI on instance (A) that will be updated first. Move API to another instance if API is active on instance (A)
2. Ensure that the outgoing FLI buffer of instance (A) to all other instances is empty.
3. If possible, minimize the API activity from that point on to case investigation on any remote instance during the update of instance (A).
4. Shut down instance (A).
5. Back up at least one instance. Use the backup to restore other instances if you need to revert the update. For more information, see:

   https://www.ibm.com/support/pages/performing-backup-ibm-safer-payments

6. If the existing application was installed by using InstallAnywhere, uninstall it by using InstallAnywhere. For more information, see Uninstalling IBM Safer Payments (InstallAnywhere). If the existing application was installed by using the RPM installation package, go to the next step.
7. Log in as root on the console.
8. Go to the directory where the RPM installation package file is located.
9. Run the installation command that applies to your situation:

   To install all files in the default directories and folders, run the following command:

   rpm -Uvh ibm-safer-payments-6_7_x_x.x86_64.rpm

   Example:

   rpm -Uvh ibm-safer-payments-6_7_0_0.x86_64.rpm

   To install files in custom directories and folders, run the following command:

   rpm -Uvh --relocate [prefix]=[custom_dir] ibm-safer-payments-6_7_x_x.x86_64.rpm 

   Where, up to three --relocate parameters are allowed. The allowed prefixes are:

   • /usr/bin
   • /usr/lib64
   • /opt/ibm/safer_payments/install

   Example 1: Install binary files in a custom folder and all other files in default directories and folders:

   rpm -Uvh --relocate /usr/bin=/usr/saferpayments/bin ibm-safer-payments-6_7_0_0.x86_64.rpm

   Example 2: Install binary and library files in custom folders and all other files in default directories and folders:

   rpm -Uvh --relocate /usr/bin=/usr/saferpayments/bin --relocate /usr/lib64=/usr/saferpayments/libs ibm-safer-payments-6_7_0_0.x86_64.rpm

   Example 3: Install binary, library, and configuration files in custom directories and folders and all other files in default folders:

   rpm -Uvh --relocate /usr/bin=/usr/saferpayments/bin --relocate /usr/lib64=/usr/saferpayments/libs --relocate /opt/ibm/safer_payments/install=/usr/saferpayments/configs ibm-safer-payments-6_7_0_0.x86_64.rpm

10. The RPM installation package finishes.

    The following directories and folders are updated:

    • /usr/bin or custom folder
    • /usr/lib64 or custom folder
    • /opt/ibm/safer_payments/install or custom directory
    • /installationPath/inc
    • /installationPath/factory_reset
11. If you changed /opt/ibm/safer_payments/install to a different directory than it was before, you must update symbolic links.
    1. Go to the instance path.
    2. Log in as SPUser on the console.
    3. Run the following commands:

       ln -f -s /installationPath/readme readme
       ln -f -s /installationPath/swidtag swidtag
       ln -f -s /installationPath/license license
       ln -f -s /installationPath/inc inc

12. Start instance (A) and monitor logs during startup. Contact support if unexpected errors or warnings occur that were not in the log before.
13. Clear browser cache before you log in to instance (A) (Ctrl+shift+F5 on most browsers).
14. Activate FLI on instance (A) and wait for instance (A) to receive all buffered FLI messages.
15. Disable FLI on all instances except for (A).
16. Enable API and the online message interfaces on instance (A).
17. If the update was successful, continue to the next step and update the other instances. If something went wrong, back out the update. For more information, see Backing out a fix pack update.
18. Disable the online message interfaces on all other instances.
19. Shut down instance (B).
20. Perform an update on instance (B) as described in step 6.
21. Start instance (B).
22. Enable FLI on instance (B) and wait for synchronization.
23. Enable the online message interfaces on instance (B) after synchronization is complete.
24. If required, you can now perform configuration and model changes on the updated instances again.
25. Shut down, update, and start instance (C) and all other instances (X).
26. Enable FLI on instances (C) and (X).
27. Enable the online message interfaces on instances (C) and (X) after synchronization is complete.
28. Verify the version number. Log in and go to Cluster > System monitoring > System internals.