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 installer. For more information, see Installation overview.
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
- Log in as root on the console. Go to the directory where the installation file is located and
run the following command:
sh ./SaferPayments.bin
The installer starts in console mode:
- Select a language, press the enter key, and follow the installation steps. Note: Do not use Starter packs for major releases.
- The installer continues and finishes.
The following folders are updated:
- /usr/bin
- The IBM Safer Payments and the keygen binary files are installed in this folder.
- /usr/lib64
- The AES and SQL libraries of IBM Safer Payments are located in this folder.
- /installationPath/
- The IBM Safer Payments installation directory. The default is /opt/ibm/safer_payments/install
- /installationPath/inc
- The JavaScript files of IBM Safer Payments are located in this folder.
- /installationPath/factory_reset
- This folder contains an initial configuration to start IBM Safer Payments for the first time. Never change the files in this folder and always use a copy with other user privileges for your initial configuration.
- If you have a previous rpm installation, you must update all symbolic links (readme file and
swidtag, license, inc folder) of all configurations after the installation. Go to the instance path,
log in as
SPUser
on the console, and 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 .