Prerequisites for installing Sterling B2B Integrator Certified Container

Before you install the application, you must ensure the following prerequisites are in place.

The following sections provide the list of prerequisites for every version.

Prerequisites of v6.1.0

  • You must ensure the Kubernetes version >= 1.14.6 along with beta APIs enabled.
  • You must ensure the Helm version >= 3.1.0.
  • You must ensure that one of the supported database servers (Oracle/DB2/MSSQL) is installed and the database is accessible from inside the cluster.
  • You must ensure that the Docker images for Sterling B2B Integrator Software Enterprise Edition from Passport Advantage are loaded to an appropriate Docker registry.
  • You must ensure that a supported MQ Server version (IBM MQ or ActiveMQ Server) is installed and accessible from inside the cluster.
  • You must create a persistent volume with access mode as 'Read Only Many' and place the database driver jar, JCE policy file, key store and trust store files in case of an SSL connection to database or MQ server in the mapped volume location.
  • You must create secrets with requisite confidential credentials for system passphrase, database, MQ server and Liberty. You can use the given configuration files under pak_extensions/pre-install/secret directory.
  • You must ensure that dataSetup.enable parameter is set to true and dataSetup.upgrade parameter is set as false when installing the chart on a new database that does not have Sterling B2B Integrator software schema tables and metadata, This creates the required database tables and metadata in the database before installing the chart.
  • You must ensure that dataSetup.enable parameter is set to true and dataSetup.upgrade parameter is set as true when installing the chart on a database on an older release version. This upgrades the given database tables and metadata to the latest version.

Prerequisites of v6.1.0.1

  • You must ensure to use Kubernetes version >= 1.14.6 with beta APIs enabled.
    Note: You must use Kubernetes version >= 1.18 to use topologySpreadConstraints.
  • You must ensure to use Helm version >= 3.2.
  • You must ensure that one of the supported database server (Oracle/DB2/MSSQL) is installed and the database is accessible from inside the cluster.
  • You must ensure that the Docker images for Sterling B2B Integrator Software Enterprise Edition from Passport Advantage are loaded to an appropriate Docker registry.
  • You must ensure that a supported MQ Server version (IBM MQ or ActiveMQ Server) is installed and accessible from inside the cluster if required by an adapter service or Adapter Container server.
  • You must create a persistent volume for application resources with access mode as Read Only Many and place the database driver jar, JCE policy file, Key store and Trust store files in case of SSL connection to database or MQ server in the mapped volume location, when appResourcesPVC.enabled is true.
  • You must create a persistent volume for application logs with access mode as Read Write Many when logs.enableAppLogOnConsole is false.
  • You must create a persistent volume for application document storage with access mode as Read Write Many when appDocumentsPVC.enabled is true.
  • You must create secrets with requisite confidential credentials for system passphrase, database, MQ server and Liberty. You can use the supplied configuration files under the pak_extensions/pre-install/secret directory.
  • You can create a secret to pull the image from a private registry or repository using the following command.
    
kubectl create secret docker-registry <name of secret> --docker-server=<your-registry-server> 
--docker-username=<your-username> --docker-password=<your-password> --docker-email=<your-email>
  • You can create secrets with confidential certificates required by Database, MQ or Liberty for SSL connectivity using the below command.
    
kubectl create secret generic <secret-name> --from-file=/path/to/<certificate>
  • You must ensure that dataSetup.enable is set to true and dataSetup.upgrade to false when installing the chart on a new database, which does not have Sterling B2B Integrator software schema tables and metadata. This creates the required database tables and metadata in the database before installing the chart.
  • You must ensure that dataSetup.enable is set to true, dataSetup.upgrade to true, and env.upgradeCompatibilityVerified to true when installing the chart on a database on an older version. This upgrades the given database tables and metadata to the latest version.
  • You must use the automatic script to install License Service on any Kubernetes-orchestrated cloud to automatically install ibm-licensing-operator with a stand-alone IBM Containerized Software using Operator Lifecycle Manager (OLM). The script creates an instance and validates the steps.
    This is tested to work on OpenShift Container Platform >=v4.2, vanilla Kubernetes cluster and is available at the below location. 
    pre-install/license/ibm_licensing_operator_install.sh

    For more information, see IBM Licensing Operator.

Additionally, the prerequisites has the following steps: