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 .
Customizing your Liberty configuration WebSphere Liberty installation to use your own parameters. Creating dedicated runtime pods for specific rulesets Defining scripts for container starts and stops Operational Decision Manager (ODM) containers support Kubernetes lifecycle hooks, which allow users to inject scripts that are executed at key points in the lifecycle of a container.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.Collecting and sending usage metrics Operational Decision Manager usage metrics to IBM Software Central .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. Emitting runtime events Decision Server can send Kafka events to Business Automation Insights for use in dashboards as key performance indicators or to an Apache Kafka service for flexible integration with various other systems. Configuring the Decision Center Business console Decision Center Business console to use your customized dynamic domains, custom value editors, or custom ruleset extractor.Customizing Decision Server Decision Server components through configuration maps.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.Configuring topology spread constraints on Operational Decision Manager pods Configuring custom pod anti-affinity on Operational Decision Manager pods Operational Decision Manager deployments (except the Decision Server console), a default pod anti-affinity setting is applied to spread the pods across the nodes by using preferredDuringSchedulingIgnoredDuringExecution . You can use the customPodAntiAffinity parameter to override this default setting.Scheduling Operational Decision Manager pods onto tainted nodes Configuring pod disruption budget on ODM deployments