Creating a BOM entry from a XOM

If you create a BOM entry from a XOM, you can subsequently extend the BOM without modifying the XOM.

About this task

You can create BOM entries from an existing XOM. You can later extend the BOM without modifying the original XOM.

Procedure

To create a BOM entry from a XOM:

  1. In the Rule Explorer view, select the bom folder and then, on the File menu, click New  > BOM Entry.
  2. In the New BOM Entry wizard, in the Name field, type a name for the BOM entry, and select the option Create a BOM entry from a XOM.
  3. Click Next.
    In the BOM Entry step, you select the XOM entries that you have defined in your rule project to be used as a basis for the BOM entry. These XOM entries can be in your current rule project or in a referenced rule project.
    Important:

    You can also select the Java™ Runtime Environment (JRE) or Java Development Kit (JDK) system libraries as a XOM. However, it can make the BOM entry creation fail because some classes cannot be loaded directly. You can click Browse XOM again to reload the XOM types. The second time, the failing classes are ignored.

  4. In the Choose a XOM entry field, type a path with the format xom:/myRuleProject/myXOM, or click Browse XOM to select a XOM entry.

    The classes in the XOM entry you selected are now shown in the Select classes field.

  5. In the Select classes field, select the classes that you want to have in the BOM entry.

    Any classes that you do not select are not available from any of the rule project items. When you select a package or a class, all its members are automatically included in the selection. You can redefine the list of selected classes later on.

    BOM types that are derived from XML simple types are filtered out because they do not have a binding at run time. To prevent runtime errors that are caused by a BOM created in a previous release, do any of the following:
    • Manually delete BOM types that are derived from XML simple types.
    • Regenerate your BOM to ensure that the XML simple types are no longer generated into the BOM.
    Important: The rule compilation might fail if the Logger class (java.util.logging.Logger) is defined in the BOM.
  6. Click Next.

    In the BOM Verbalization step, you define which BOM elements you want to be verbalized. BOM elements that you do not verbalize are not available in business rule artifacts, but you can still use them in technical rule artifacts. You can redefine the elements to be verbalized later on.

    Note: The package java.util is already included in the default BOM. It should never be included in a new BOM entry. The package com.ibm.rules.engine represents the engine classes and should not be included in a BOM entry. Including these packages in a BOM can prevent a successful build.
  7. Click Finish.

    In the Rule Explorer view, the bom folder displays a new BOM entry.

Results

You can now edit the verbalization of business elements in the BOM Editor, and use them in your rule artifacts.