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 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 Configuring user access 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) 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 Operational Decision Manager installation to emit events to IBM Business Automation Insights . Configuring the Decision Center Business console Decision Server Business console to use your customized dynamic domains, custom value editors, or custom ruleset extractors. Customizing the Decision Server Runtime Decision Server Runtime behavior through a configmap that references a properties file with context parameters. Customizing Decision Center Decision Server behavior through a configmap that references a properties file with context parameters.Customizing Decision Runner Configuring multi-zone support nodeAffinity parameter.Scheduling Operational Decision Manager pods onto tainted nodes