Standalone mode allows you to run BAMOE projects as self-contained Java applications without requiring a full server environment. BAMOE v9 provides two templates that include the minimal setup required to run a Business Service project in a functionality equivalent Embedded mode for more information see Decisions and Rules Services in Embedded Java mode. Both templates include a pom.xml file with the minimal set of dependencies needed to run the project independently.

Decisions template

Is available decisions-embedded-mode-example GitHub repository. It contains executable java class DecisionsEmbeddedModeExample.java. You will need to update DecisionsEmbeddedModeExample.java code accordingly:

  • namespace: change "https://kie.org/dmn/_C83DFD16-A42A-46BE-A843-370444580E0F" to your model namespace value

  • modelName: change "loan-application-age-limit" to your model name value

  • dmnContext: change to dmnContext.set(key, value) according to your model Input Data nodes

After applying the updates, run one of the following commands depending on the desired outcome:

  • To run a full build lifecycle, including tests, and install the generated artifacts into the user’s local repository, use the following command:

mvn clean install
./gradlew clean build publishToMavenLocal

  • To build the project and run tests, but not install the generated artifacts into the local repository, use the following command:

mvn clean verify
./gradlew clean check

  • To build the project without running tests or installing artifacts into the local repository, use the following command:

mvn clean package
gradle clean build
Note
 Maven places all build artifacts in the /target directory, while Gradle places them in the build/ directory.

Rules template

Is available here. It contains executable java class RulesEmbeddedModeExample.java. You will need to update RulesEmbeddedModeExample.java code accordingly:

  • CommandFactory.newInsert(new Applicant("#0001", 20), "applicant"): replace Applicant according to your domain data objects

After applying the updates, run one of the following commands depending on the desired outcome:

  • To run a full build lifecycle, including tests, and install the generated artifacts into the user’s local repository, use the following command:

mvn clean install
./gradlew clean build publishToMavenLocal

  • To build the project and run tests, but not install the generated artifacts into the local repository, use the following command:

mvn clean verify
./gradlew clean check

  • To build the project without running tests or installing artifacts into the local repository, use the following command:

mvn clean package
gradle clean build
Note
 Maven places all build artifacts in the /target directory, while Gradle places them in the build/ directory.

Other assets

Your project may contain multiple types of assets. Each asset type may require a different migration approach. For more information, see Upgrading Individual Assets topic.