Configuring

You must configure Operational Decision Manager for z/OS® before you can send requests to the rule engine from your applications. If your execution environment is on WebSphere® Application Server for z/OS you must deploy and configure the provided archives for Rule Execution Server and the event runtime. You can also deploy the Decision Center consoles on WebSphere Application Server for z/OS to allow users to author and test rule projects.

To set up a Decision Server execution environment or Decision Center, you must customize the data sets, z/OS configuration variables, and z/OS jobs provided, and then use them to configure new environments. Depending on your requirement, you could use identical environments to maximize execution throughput or you could use one type of environment for legacy rules and another type for rules authored in Decision Center. The configuration process consists of initial steps that are common to all execution environments, followed by steps that are specific to your environment.

Decision Server supports the following execution environments:

• zRule Execution Server group with a shared console
• One or many CICS® rule-owning regions
• CICS rule-owning and application-owning regions
• Operational Decision Manager on WebSphere Application Server for z/OS
• Embedding an execution server with your batch execution
• Operational Decision Manager on the Liberty server

Decision Center provides a single repository, which can be deployed to production mainframe applications. Decision Center for z/OS works in the same way as Decision Center does, except that it runs on WebSphere Application Server for z/OS.