Defining BOM-to-XOM mapping

You can map different business elements to the XOM. These elements include business classes, attributes, method calls, and constructor calls. You can also implement synthetic objects, and access ruleset variables, parameters, and functions from rule language mapping code.

Rule language and extender mapping
Rule artifacts that are created from the BOM must be mapped to the XOM to run at run time. You can use the default mapping, or mappings based on rule language functions or Java extender classes.
Execution class mapping
You can map a business class to an execution class. By default, the elements of the business class are mapped to the elements of the execution class. Conversely, the BOM-to-XOM mapping also helps to deduce the business class from a particular class instance, such as for testing and simulation.
Rule language mapping
You can use the rule language mapping code to define the BOM-to-XOM mapping.
Extender mapping
Extender mapping is designed to use Java rather than rule language. In a Java extender class, you create static elements that have the same name as business class elements.
Accessing classic rule engine and related artifacts from IRL mapping code
You can access the classic rule engine and its related artifacts, by writing IRL mapping code in the BOM-to-XOM mapping section of the BOM Editor.
Accessing decision engine and related artifacts from ARL mapping code
You can access the decision engine and its related artifacts, by writing ARL mapping code in the BOM-to-XOM mapping section of the BOM Editor.

Parent topic: Designing a BOM for a Java model