Designing business object models
The way you design a business object model (BOM) depends on the nature of the data you use as its basis. You can design a BOM for a Java™ model or for an XML model.
- Overview: BOM and execution object model (XOM)
The XOM is the model used to execute the rules. You can build the XOM from different data sources: Java, XML, COBOL, PL/I, or .NET. - Sharing a BOM between Java, COBOL, and PL/I applications
A BOM can be shared in Java, COBOL, and PL/I applications. Rules that are created from the BOM can be deployed and executed in the distributed and z/OS® environments. - Creating BOM entries
BOM entries are files that describe a part of a Business Object Model (BOM). - Designing a BOM for a Java model
You design a BOM for a Java model by building a XOM from compiled Java classes or from an XML schema, mapping BOM elements to XOM elements, and configuring BOM updates. - Designing a BOM for an XML model
You can use data other than Java as the basis for your XOM. - Designing a BOM for a COBOL model
You generate a BOM for a COBOL model from a COBOL XOM. You generate the COBOL XOM from a COBOL copybook. - Designing a BOM for a PL/I model
You generate a BOM for a PL/I model from a PL/I XOM. You generate the PL/I XOM from a PL/I include file. - Updating the BOM when the XOM changes
How you manage XOM changes in the BOM depends on whether your rule project references a Java project as a XOM. - Preserving your changes to the Java XOM when the z/OS data model is updated
You can add code to a generated Java XOM and keep the changes when the z/OS data model (COBOL copybook or PL/I include file) is updated by enclosing that code inside user code tags.
Parent topic: Designing projects for rule authoring