Pre-installation tasks

This checklist will help you to gather all the information that is needed for a successful installation. You need to provide the values during the installation process.

To obtain files required for upgrading IBM Financial Services Workbench:

• go to Passport Advantage Online

• search for IBM Financial Services Workbench for Cloud Pak for Data

• download the presented file, e.g. ssob-3.0.0-ibm-openshift-4.6-cpd-installations.tgz (search for latest version). This file contains all container images and accompanying resource files needed for installation on OpenShift 4.8

Unpack the installation file on the computer from which the installation commands are to be executed:

INSTALLDIR=~/install/
mkdir ${INSTALLDIR}
cd ${INSTALLDIR}
tar xzvf ssob-3.0.0-ibm-openshift-4.6-cpd-installations.tgz
mv ssob-3.0.0-ibm-openshift-4.6-cpd-installations ssob_3.0.0
cd ${INSTALLDIR}/ssob_3.0.0

Keep OpenShift details available:

• host_domain: The external hostname for the OpenShift cluster, which will be used as a base path for serving components, e.g. apps.openshift-cluster.mydomain.cloud

• external_address_image_registry: The external address of the internal docker registry. If the OpenShift image registry is used, this address can be found via the route image-registry in namespace openshift-image-registry

• internal_address_image_registry: The address of the internal docker registry, e.g. image-registry.openshift-image-registry.svc:5000

Keep Cloud Pak for Data (CPD) installation details available:

• cpd_namespace: The name of the namespace, where CPD is installed, commonly zen

• helm-tls-ca-cert: The filename of the Helm TLS CA certificate, which was created by the CPD installation, e.g. /path/to/my/ca.cert.pem

• helm-tls-cert: The filename of the Helm TLS certificate, which was created by the CPD installation, e.g. /path/to/my/helm.cert.pem

• helm-tls-key: The filename of the Helm TLS key, which was created by the CPD installation, e.g. path/to/my/helm.key.pem

The IBM Financial Services Workbench requires that you synchronize the clocks on each node in the cluster. The clocks must be within one second of each other. It is recommended that you use chrony to synchronize your clocks. For more information about setting up chrony, see the user documentation for your operating system.

It is recommended to NOT use self-signed certificates. As a feasible solution it might be sufficient to use certificates that are signed by Let's encrypt.