8.7. Manifest

8.7.1. Manifest

The Manifest is where you specify from where the "intelligence" of the component is to come. For the BPM component, you need to specify, at the minimum, the location of the BPMN 2 process definition file. For the Rules component, you can specify the location of DRL, DSL, DSLR or XLS files.

8.7.2. Ways of Configuring the Manifest

Note
The following code examples assume there is a DRL file located on the classpath at com/example/MyRules.drl.
There are two ways to to configure the Manifest:
  • with a KIE Container. (This relies upon the existence of a META-INF/kmodule.xml configuration file.)
    Here is the sample META-INF/kmodule.xml file: 
    <kmodule xmlns="http://jboss.org/kie/6.0.0/kmodule">
    <kbase name="com.example">
        <ksession name="my-session"/>
    </kbase>
</kmodule>
    Here is the sample XML file: 
    <manifest>
    <container sessionName="my-session"/>
</manifest>
    In addition to the sessionName attribute, you can also specify baseName and releaseId, if you desire.
    To enable it to scan for updates, simply set scan="true" and, optionally, 
     scanInterval=<# of milliseconds>
  • with a manually defined list of resources.
    Here is the sample XML file: 
    <manifest>
    <resources>
        <resource location="com/example/MyProcess.bpmn" type="BPMN2"/>
        <resource location="com/example/MyRules.drl" type="DRL"/>
    </resources>
</manifest>
Important
These two options are mutually exclusive: You have to choose one or the other.