You can define a BOM in one of three ways:
-
Bottom-up:
- All your BOM classes map directly to the execution classes and the corresponding Java objects, XML Schemas, and Web services have already been developed. In this case, the quickest way for you to create a BOM is by importing execution classes into it, see Importing Classes into the BOM and Importing Classes from the XOM into the BOM.
-
Bottom-up with some virtual classes:
- Some of your classes are virtual, and some are imported from the execution classes. In this situation you can use the editors provided in the Rule Builder: the BOM Explorer (see Working With the BOM Explorer) and the BOM Graphical Editor (see Working With the BOM Graphical Editor). However, you must be careful not to edit classes that map in a one-to-one manner with execution classes. This is because, if any element of an imported class you have edited in the Rule Builder is different from its corresponding execution class, the BOM class is no longer recognized and is taken to be a virtual class with no
translation
property. You can still add members to an imported class, provided you set up a translation
property for these class members too. -
Top-down BOM prototyping:
- It is possible to set up a BOM that contains only virtual classes and methods using the BOM editors provided in the Rule Builder. You can create virtual BOM classes without necessarily considering the way that the execution classes are going to be implemented. At a later date when the execution classes are implemented, you can import them into the BOM, or use the
translation
property to map virtual BOM classes to execution classes.
For more information about the translation
property, see the Business Action Language User's Manual.
See Also
Virtual BOM Classes | Using the BOM Date and Time Classes | Adding Elements to a BOM | Adding and Editing Attributes | Adding and Editing Methods | Working With the Property Sheet | Setting Up the Execution Object Model
|