Object model and deployment options

You can choose which type of object model to use for your rule project, and which deployment option suits your execution requirements.

When you create a rule project to execute rules in a COBOL application on z/OS®, you must know what type of object model you are starting from, and where you want to execute your rules.

You have a choice of object models and a number of execution options:

  • You can define an execution object model (XOM) from Java™ classes or a COBOL copybook.

  • You can share rule projects between Java and COBOL platforms, so that you can execute the same rules in both environments.

  • You can deploy your rules in the following ways:

    • Deploy to zRule Execution Server for z/OS and call the rules from a COBOL application (batch or CICS®).

    • Generate a COBOL rule execution program, compile and build it, and then call it from a COBOL calling program (batch, CICS, or IMS).

You can start from a Java or a COBOL model, choose where to deploy, and execute your rules in any of the supported environments. The following diagram shows the different pathways you can take to define the XOM and the BOM for the required execution option.

COBOL management source and execution options

The choices you make determine how you design your rule project and configure the BOM, and might limit some of the rule authoring features you can use.

For example, to execute your rules in Enterprise COBOL, you follow this path:

  • You base your XOM on a COBOL copybook, or create a copybook from an existing Java BOM.

  • You implement BOM to XOM mapping, and implement BOM methods in COBOL.

  • You create ruleflows and use the BAL to write your business rules, but at all times observe COBOL compatibility.

  • You generate a COBOL program for rule execution and integrate it into your COBOL calling program. You must have a copybook to be able to do this.