This sample shows how to use the business object model (BOM) to execution object model (XOM) mapping mechanism to isolate rules from the execution layer.
Time required
5 minutes
Prerequisites
You must have Rule Designer installed to import and run this sample.
Description
This sample shows how to use the business object model (BOM) to Execution Object Model (XOM) mapping mechanism to isolate rules from the “physical” execution layer.
You can apply the same rules on different execution applications and platforms. For example:
In this sample, you map a single BOM to two very different XOMs.
The BOM was designed for regular Java™ static classes and is re-mapped to a model made of generic objects (also called synthetic, or dynamic objects) made of key-value properties, such as hash maps. You can execute the same BAL rules on the two execution layers.
The sample is derived from the engine > patternmatching sample (the Java XOM is shared, and the rules are rewritten in BAL). The execution results are the same.
The key features of this sample include: