The installation of Operational Decision Manager 8.10.1 uses the ibm-odm-prod-2.1.0 Helm chart, also known as the ODM for production Helm chart. The chart is a package of preconfigured Kubernetes resources that bootstraps an ODM for production deployment on a Kubernetes cluster. You customize the deployment by changing and adding configuration parameters. The default values are appropriate to a production environment, but it is likely that you want to configure at least the security of your kubernetes deployment.
The following architectures are supported for Operational Decision Manager 8.10.1 on Certified Kubernetes:
- AMD64 (or x86_64), which is the 64-bit edition for Linux x86.
The ibm-odm-prod-2.1.0 Helm chart includes five containers corresponding to the following services.
- Decision Center Business Console and Enterprise Console
- Decision Server Console
- Decision Server Runtime
- Decision Server Runner
- (Optional) Internal PostgreSQL DB
The services require CPU and memory resources. The following table lists the minimum requirements that are used as default values.
| Service | CPU Minimum (m) | Memory Minimum (Mi) |
|---|---|---|
| Decision Center | 500 | 512 |
| Decision Runner | 500 | 512 |
| Decision Server Console | 500 | 512 |
| Decision Server Runtime | 500 | 512 |
| Total | 2000 (2CPU) | 2048 (2Gb) |
| (Optional) Internal DB | 500 | 512 |
Go to the IBM Digital Business Automation for MultiCloud 18.0.x Knowledge Center and choose which customizations you want to apply to your installation.
- Configuring PVUs
- Defining the security certificate
- Configuring the LDAP and user registry
- Configuring a custom external database
- Configuring the ODM event emitter
After you noted the values for all of the configuration parameters that you need to customize Operational Decision Manager, choose one of the following options to help you complete the installation.
Note: The configuration folder provides sample configuration files that you might find useful. Download the files and edit them for your own customizations.
A Helm chart is a Package Manager for Kubernetes to help you manage (install/upgrade/update) your Kubernetes deployment. If you are using Helm on a cluster that you completely control, like Minikube or a cluster on a private network in which sharing is not a concern, the default installation that applies no security configuration is the easiest option.
However, if your cluster is exposed to a larger network or if you share your cluster with others – production clusters fall into this category – you must secure your installation to prevent careless or malicious actors from damaging the cluster or its data. To secure Helm for use in a production environment and other multi-tenant scenarios, see Securing a Helm installation.
Refer to helm-charts/README.md
If you prefer to use a simpler deployment process that uses a native Kubernetes authorization mechanism (RBAC) instead of Helm and Tiller, use the Helm command line interface (CLI) to generate a Kubernetes manifest. If you choose to use Kubernetes YAML you cannot use certain capabilities of Helm to manage your deployment.
Refer to k8s-yaml/README.md
The following instructions are for specific offerings:
You can check the status of the pods by using the following command:
$ kubectl get podsWhen all of the pods are Running and Ready, retrieve the cluster-info-ip name and port numbers with the following commands:
$ kubectl cluster-info Kubernetes master is running at https://cluster-info-ip:8443 CoreDNS is running at https://cluster-info-ip:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy $ kubectl get services NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP **** none 443/TCP 9m my-odm-prod-release-dbserver ClusterIP **** none 5432/TCP 3m my-odm-prod-release-odm-decisioncenter NodePort **** none 9453:dcs-port/TCP 3m my-odm-prod-release-odm-decisionrunner NodePort **** none 9443:dr-port/TCP 3m my-odm-prod-release-odm-decisionserverconsole NodePort **** none 9443:dsc-port/TCP 3m my-odm-prod-release-odm-decisionserverconsole-notif ClusterIP **** none 1883/TCP 3m my-odm-prod-release-odm-decisionserverruntime NodePort **** none 9443:dsr-port/TCP 3m
With the cluster-info-ip name and port numbers, you have access to the applications with the following URLs:
| Component | URL | Username | Password |
|---|---|---|---|
| Decision Server Console | https://cluster-info-ip:dsc-port/res | resAdmin | resAdmin |
| Decision Server Runtime | https://cluster-info-ip:dsr-port/DecisionService | N/A | N/A |
| Decision Center Business Console | https://cluster-info-ip:dcs-port/decisioncenter | rtsAdmin | rtsAdmin |
| Decision Center Enterprise Console | https://cluster-info-ip:dcs-port/teamserver | rtsAdmin | rtsAdmin |
| Decision Runner | https://cluster-info-ip:dr-port/DecisionRunner | resDeployer | resDeployer |
To further debug and diagnose deployment problems in the Kubernetes cluster, use the kubectl cluster-info dump command.
For more information about how to check the state and recent events of your pods, see Troubleshooting.
If you customized the default user registry, you must synchronize the registry with the Decision Center database. For more information, see Synchronizing users and groups in Decision Center.
It is possible to update a deployment after it is installed. Use the following tasks in IBM Knowledge Center to update a deployment whenever you need, and as many times as you need.