Installing containerized ODM

After you have assessed your readiness and prepared your data for the move to a Certified Kubernetes platform, install Operational Decision Manager on Kubernetes.

Then, follow the instructions in Installing ODM charts on Certified Kubernetes. The following steps present a typical installation.

1. Migrate your LDAP connection and database, as described in the following subtopics.
   • Migrating your LDAP connection
   • Migrating your data source
2. Define the security certificate.

   For example, access the container images using the IBM® Entitled registry and your email.

   kubectl create secret docker-registry registry-secret --docker-server=cp.icr.io --docker-username=cp --docker-password="XXX...." --docker-email=Joe@ibm.com

   When you install the Helm chart, add the following parameter:

    --set image.pullSecrets=registry-secret

3. Obtain the Helm chart by running the following command.

   wget https://raw.githubusercontent.com/IBM/charts/master/repo/entitled/ibm-odm-prod-26.0.0.tgz

   When you install the Helm chart, add the following parameter:

    --set image.repository=cp.icr.io/cp/cp4a/odm

4. Install the Helm chart to create your instance of Operational Decision Manager.
   Create a my-values.yaml file with the following parameters:

   license: true 
   image: 
      repository: cp.icr.io/cp/cp4a/odm 
      pullSecrets: 
      - ibm-entitlement-key 
   externalCustomDatabase: 
      datasourceRef: customdatasource-secret 
   customization: 
      authSecretRef: my-auth-secret 
   decisionServerConsole: 
      extendRoleMapping: true 
   decisionCenter: 
      extendRoleMapping: true 
   decisionRunner: 
      extendRoleMapping: true 
   decisionServerRuntime 
      extendRoleMapping: true

   See detailed instructions here.
5. To install a release with the name my-odm-prod-release, use the following command:

   helm install my-odm-prod-release -f my-values.yaml ibm-helm/ibm-odm-prod

   Note: In OpenShift, you must set the following parameters:

   --set customization.runAsUser='' and you can also set the parameter --set service.enableRoute=true.

   Alternatively, you can set these parameters in my-values.yaml:

   customization: 
      runAsUser: "" 
   service: 
      enableRoute: true

   For more information, see Required Parameters .