Configuring Operational Decision Manager

Edit online

The installation of Operational Decision Manager can be customized 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 deployment.

About this task

ODM for production includes four containers corresponding to the following services:

  • Decision Center Business console
  • Decision Server console
  • Decision Server Runtime
  • Decision Runner

Choose which containers you want to install and which customizations you want to apply. Nonproduction deployments might include all of the four containers, whereas production deployments might have only runtime containers and a Decision Server console container.

Note: The Decision Server console cannot be installed on its own. It is automatically installed when you install the Decision Server Runtime or the Decision Runner components.

To gain insights into the decision-making process of your applications, add Business Automation Insights to your Operational Decision Manager instance to emit events from the execution of rulesets. The generated events are sent to Business Automation Insights to be processed.

Operational Decision Manager runs on Liberty, which has a server.xml file for the configuration. ODM authorization is managed with a webSecurity.xml file that provides a binding between Operational Decision Manager roles and Identity Management (IM) groups.

For more information, see the following topics.

Make a note of the different customization parameter names and values. Keep these names and values close to hand for when you edit the custom resource (CR) YAML file.

Procedure

  1. Open the CR file that you created in Option 1a: (Recommended) Generating the custom resource with the deployment script, or go to the YAML tab in the OpenShift console.
  2. Check the values to make sure they are the values that you want to deploy.

    If you selected the decisions pattern, you see this value in the sc_deployment_patterns parameter.

    You can also see in all cases the options to enable the ODM containers in the odm_configuration section.

    # To enable ODM runtime.
    decisionServerRuntime:
      enabled: true
# To enable the authoring part.
    decisionRunner:
      enabled: true
    decisionCenter:
      enabled: true
  3. If you need to configure more parameters, then use the fully customizable decisions template, ibm_cp4a_cr_production_FC_decisions.yaml, to copy lines from and paste them into your CR file.
    Go to the relevant folder in cert-kubernetes/descriptors/patterns to find all of the templates. For more information about downloading cert-kubernetes, see Preparing a client to connect to the cluster.
    Note: If you selected to use EDB Postgres as your deployment database and you want to use EDB Postgres for ODM, check that the datasource_configuration.dc_odm_datasource.dc_use_postgres parameter is set to true. If you do not want to use EDB Postgres for ODM, set the values to false. Then, check the values of the external database parameters that you generated when you ran the cp4a-prerequisites.sh script.

What to do next

Continue to configure the other capabilities that are in your CR file, and make sure that you complete the last step Validating the YAML in your custom resource file before you apply the CR to the operator.