Installing a major release

A major release is indicated by a change of the first or second revision number position.

In a major release, file formats might be changed so that you cannot change back to an earlier release. Also, you might not be able to install such an update immediately, that is, on a running IBM® Safer Payments cluster that still fully runs during the update.

Depending on your specific application needs, it might be advisable to contact IBM support for assistance with a major release.

Before you begin:

Go to the Release Notes for the major release and read the Update information.
Follow the installation instructions up to running the RPM installation package. For more information, see Installation overview.
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 major release:

Shut down all IBM Safer Payments instances in a cluster.
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
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.
Log in as root on the console.
Go to the directory where the RPM installation package file is located.
Run the installation command that applies to your situation:
To install all files in the default directories and folders, run the following command:
```
rpm -ivh ibm-safer-payments-6_7_x_x.x86_64.rpm
```
Example:
```
rpm -ivh ibm-safer-payments-6_7_0_0.x86_64.rpm
```
To install files in custom directories and folders, run the following command:
```
rpm -ivh --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 -ivh --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 -ivh --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 -ivh --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
```
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
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
```
Read the Release Notes to find out whether any other files must be exchanged.
Start all updated IBM Safer Payments instances.
Verify the version number. Log in and go to Cluster > System monitoring > System internals.