Customizing ODM for production
Before you install the Helm chart, customize some settings, for example, to protect your
containers or define the users and groups that access Decision Center and Decision Server .
Defining the security certificate
By default, IBM Operational Decision Manager is delivered with self-signed certificates. You can replace the default certificates with your own certificates, either CA signed or self-signed. You do so with certificate tools such as OCP native certificate management capabilities or cert-manager , or with the Java keytool.
Importing the certificate of an external service
To integrate with an external service, you must first import its Transport Layer Security (TLS) certificate into the containers trusted list.
Configuring user access
By default, IBM Operational Decision Manager is provided with a set of predefined users. To provide customized user access through an LDAP directory, you must configure the Liberty server and Decision Center by using Kubernetes secrets.
Configuring the database
Operational Decision Manager must persist data in a database.
Optimizing the execution unit (XU)
The Decision Server execution unit (XU) can be configured at installation time and also applied to an existing Operational Decision Manager instance. You can avoid deadlocks by adjusting the predetermined length of timeouts, restricting the number of rule instances to evaluate, and limiting the number of rules that can fire.
Configuring the ODM event emitter
To gain insights into the decision-making process of your applications, configure your Operational Decision Manager installation to emit events to IBM Business Automation Insights .
Configuring the Decision Center Business console
You can configure the Decision Server Business console to use your customized dynamic domains, custom value editors, or custom ruleset extractors.
Customizing the Decision Server Runtime
You can customize the Decision Server Runtime behavior through a configmap that references a properties file with context parameters.
Customizing Decision Center
You can customize the Decision Server behavior through a configmap that references a properties file with context parameters.
Customizing Decision Runner
In a topology where ODM is deployed in several namespaces inside a cluster or on several clusters, you might want to design decision services in a development environment (in a given namespace), to do tests and simulations in a staging environment (in another namespace), and finally to deploy the decision services to production on another cluster.
Configuring multi-zone support
You configure multi-zone support by setting the nodeAffinity
parameter.
Scheduling Operational Decision Manager pods onto tainted nodes
Taints and tolerations are used to ensure that pods are not scheduled on inappropriate nodes.