FAQ

BAMOE v9 no longer includes the KIE Server, so you cannot deploy a KJAR directly to a server as in v8.

The recommended approach to make your BAMOE v8 KJAR compatible with BAMOE v9 is to duplicate your BAMOE v8 project (to preserve a backup) and follow the steps outlined in the Upgrading Projects section.

In BAMOE v9, a Business Service is a standalone, containerized application that encapsulates domain-specific logic, such as Workflows, Decisions, Rules, or Decision Tables, and is built using Quarkus or Spring Boot. Each Business Service can be versioned, monitored, and managed independently, aligning with modern microservices best practices.

This represents a shift from BAMOE v8, where multiple business assets were typically bundled into a single KJAR and deployed to a centralized KIE Server.

With BAMOE v9, you define the granularity of your deployments. You have the flexibility to: - Bundle multiple business assets (e.g., BPMN, DMN, DRL) into a single Business Service - Deploy multiple Business Services within the same Kubernetes pod for tighter coupling or resource efficiency - Separate Business Services into distinct deployments to improve modularity, scalability, and maintainability

This flexibility allows you to tailor your deployment strategy to your organization’s architecture, performance, and operational requirements. For additional information, see Deploying Business Services.

Since Smart Router is no longer available in BAMOE v9, you can achieve similar load balancing using any solution compatible with cloud environments.

BAMOE v9 does not provide its own Operator. Instead, it offers Helm charts to simplify deployment. The BAMOE Management Console Helm Chart is available for installing the related components on Kubernetes or OpenShift clusters. These charts support flexible configuration and align with infrastructure-as-code practices. For more details, see Deploying to Kubernetes or OpenShift with the Helm Chart.