Adding the execution object model (XOM)
To execute your rules in Java™ you need an execution object model (XOM). After creating the XOM, you must attach it the rule project, and associate your BOM entry to the XOM by setting the origin.
About this task
During the migration process, the business object model (BOM) is converted. However the .NET class library project on which the initial BOM was based is not converted. Therefore, you must re-write the classes from your .NET class library project, in Java.
The Java project containing the execution classes, is called the execution object model (XOM). The XOM is a model that references implementation objects used in rules. Through the XOM, the rule engine can access application objects and methods. At run time, rules that are written against the BOM are run against the XOM.
The classes in the XOM must map the classes that you have in the migrated BOM. Every BOM element (business element) must have a corresponding XOM element (execution element). The mapping between execution elements and business elements does not need to be one-to-one. When a business element is not attached to an execution element, you must specify a BOM to XOM mapping.
After creating the Java project for the XOM, you must reference it in the rule project. Then, you link the XOM to the BOM entry.
Procedure
Results
What to do next
To synchronize changes between the BOM and the XOM, you can use the BOM update view.