KIE deployments

The jBPM 6 platform introduced a brand new deployment process; the previous proprietary mechanism that leveraged the Guvnor packages (backed by a Java Content Repository (JCR) and the Drools KnowledgeAgent (changeset.xml) was replaced with the widely adopted Apache Maven tool. This greatly improved the development process both in terms of tool configuration (more convention/configuration oriented) and support, standardization, and deployment flexibility.

When you deploy your project, you physically create a KIE deployment unit (KJAR); this module is a Maven-enabled project and is a compressed standard Java archive that contains all the project's business assets (processes, workitem handlers, business rules, forms, and so on) as well as its knowledge session and runtime declarative metadata descriptor (META-INF/kmodule.xml).

Note

The kmodule.xml file is extensively covered in the official jBPM and Drools documentation.

The unique ID of a KIE module is built starting from its...