Setting up the cluster by running a script

To install the Cloud Pak capabilities with the Cloud Pak operator, a cluster administrator user can run a script to set up the cluster. The administrator must also provide information that they get from the script to a non-administrator user so they can run the deployment script.

1. Download the appropriate repository to a Linux® based machine (RHEL, CentOS, and so on) or a client to a linux-based machine or VM that runs podman natively, and go to the cert-kubernetes directory.

   For more information about downloading cert-kubernetes, see Preparing for a production deployment.

2. Log in to the target cluster as the <cluster-admin> user.

   Using the OpenShift CLI:

   oc login https://<cluster-ip>:<port> -u <cluster-admin> -p <password>

   On ROKS, if you are not already logged in:

   oc login --token=<token> --server=https://<cluster-ip>:<port>

3. Run the cluster setup script from where you downloaded the cert-kubernetes repository, and follow the prompts in the command window.

   cd scripts
   ./cp4a-clusteradmin-setup.sh 

   1. From 21.0.3-IF033 Select the CP4BA deployment environment: Online (1) / Offline or Airgap (2). Select Online.
   2. Select the platform type: ROKS (1) or OCP (2).
   3. Select the deployment type production.
   4. Select Yes if you want to install the CP4BA operator in 'All Namespaces'. The default is No.
   5. Enter the name for a new project or an existing project (cp4ba-project) for the target deployment namespace. For more information, see Preparing storage for the Cloud Pak operator.

      If an existing CP4BA operator is found in another project on your cluster, confirm that you want to deploy another CP4BA operator in the new project by entering Yes. You must install a CP4BA operator in each namespace where you want to install a CP4BA instance.

   6. Enter Yes or No to confirm whether you want to use the images in the IBM Entitlement Registry.
   7. If you replied Yes, enter your IBM Entitled Registry key and login credentials (user and password).

      If you want to load the container images to a local registry, then set up the cluster by mirroring the images instead of running the cp4a-clusteradmin-setup.sh script. For more information, see Setting up the cluster by mirroring the container images.

      Tip: If you ran the cp4a-clusteradmin-setup.sh script and you see one or more of the following messages, then make sure that you start Docker or Podman and run the script again.

      Error saving credentials: error storing credentials
      Error: unable to connect
      The Entitlement Registry key failed

   8. Enter a dynamic storage class name. On ROKS/ROKS VPC, use an appropriate storage class.
      Note: From 21.0.3-IF008, the script no longer creates the 3 storage classes: ibmc-file-bronze-gid, ibmc-file-silver-gid, and ibmc-file-gold-gid.

   Note: The following message appears on OCP 4.6, but the warning does not have any functional impact.

   Creating the custom resource definition (CRD) and a service account that has the permissions to manage the resources...
   W1102 26405 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
   

4. Monitor the operator pods until they show a STATUS of "Running".

   oc get pod -w

   Tip: If ibm-cp4a-operator is inactive for some time, you can delete the operator pod and let it reconcile.

   To confirm that the operator is stuck, check to see whether the log is providing an output.

   oc project <namespace of Cloud Pak for Business Automation operator>
   NAMESPACE=$(oc project -q)
   podname=$(oc get pod -n $NAMESPACE | grep ibm-cp4a-operator | awk '{print $1}')
   oc logs $podname -f

   You can also list the ClusterServiceVersion (CSV) to verify the version of the running operators on your cluster.

   oc get csv

5. Add JDBC drivers to the operator pod for Business Automation Navigator and all of the other patterns in your deployment that need them.

   Copy all of the JDBC drivers that are needed by the components to the operator pod. Depending on your storage configuration, you might not need all these drivers. For more information about compatible JDBC drivers, see Db2 JDBC information, Oracle JDBC information, SQL Server JDBC information, and PostgreSQL JDBC information. The following .jar files are examples.

   • Db2®
     • db2jcc4.jar
     • db2jcc_license_cu.jar

     The Db2 license file is included in all Db2 server editions and you must take the license file from the Db2 Activation CD or download it from Passport Advantage. For more information, see Db2 license files.

   • Oracle
     • ojdbc8.jar
     • orai18n.jar
   • Microsoft SQL Server
     • mssql-jdbc-8.2.2.jre8.jar
   • PostgreSQL
     • postgresql-42.2.9.jar

   The following structure shows an example remote file system. The jdbc directory and the subfolder name for the database must be created.

   /root/operator
      └── jdbc
           ├── db2
               ├── db2jcc4.jar
               └── db2jcc_license_cu.jar
           ├── oracle
               ├── ojdbc8.jar
               └── orai18n.jar
           ├── sqlserver
               └── mssql-jdbc-8.2.2.jre8.jar
           ├── postgresql
               └── postgresql-42.2.9.jar

   Copy the JDBC files to the operator pod.

   oc project <namespace of Cloud Pak for Business Automation operator>
   NAMESPACE=$(oc project -q)
   podname=$(oc get pod -n $NAMESPACE | grep ibm-cp4a-operator | awk '{print $1}')
   oc cp PATH_TO_JDBC/jdbc $NAMESPACE/$podname:/opt/ansible/share 

   The PATH_TO_JDBC is the path to the driver files on your system.

   To verify that the files are in the pod, run the following commands:

   oc exec -n $NAMESPACE $podname -- ls -lR /opt/ansible/share

6. Optional: If you intend to install Content Collector for SAP as an optional component of the Content Manager pattern, then you must download the necessary libraries, put them in a directory, and copy the files to the operator pod.
   1. Make a saplibs directory.
      Give read and write permissions to the directory by running the chmod command.
   2. Download the SAP Netweaver SDK 7.50 library from the SAP Service Marketplace.
      • https://launchpad.support.sap.com/#/softwarecenter/object/0020000000957442020 for libsapcrypto.so
      • https://launchpad.support.sap.com/#/softwarecenter/object/0020000001646522020 for libicudata.so.50, libicudecnumber.so, libicui18n.so.50, libicuuc.so.50, libsapnwrfc.so, and libsapucum.so
   3. Download the SAP JCo Release 3.0.x from the SAP Service Marketplace.
      • https://launchpad.support.sap.com/#/softwarecenter/object/0020000001721092019 for sapjco3.jar and libsapjco3.so
   4. Extract all of the content of the packages to the saplibs directory.
   5. Check you have all of the following libraries.

      saplibs/
      ├── libicudata.so.50
      ├── libicudecnumber.so
      ├── libicui18n.so.50
      ├── libicuuc.so.50
      ├── libsapcrypto.so
      ├── libsapjco3.so
      ├── libsapnwrfc.so
      └── sapjco3.jar

   6. Copy the SAP files to the operator pod.

      oc cp PATH_TO_SAPLIBS/saplibs $NAMESPACE/$podname:/opt/ansible/share

      The PATH_TO_SAPLIBS is the path to the driver files on your system.

      To verify that the files are in the pod, run the following command:

      oc exec -n $NAMESPACE $podname -- ls -lR /opt/ansible/share

oc get pods -n ibm-common-services

oc -n ibm-common-services get csv

- name: ibm-iam-operator
  spec:
    authentication:
      config:
        defaultAdminUser: <custom-username>