Open Edition

 View Only

 Understanding BAMOE, DMOE, and PAMOE: Differences and Uses

Viswa Teja Challa's profile image
Viswa Teja Challa posted Mon February 10, 2025 04:00 PM

Hello Everyone,

I'm new to this community and also to Business Rules Engine/Automation.

I have a requirement to build a business rules engine with a dashboard. I learned that Red Hat Decision Manager is a good fit for OpenShift Container Platform (OCP), but I understand it has been renamed to Business Automation Manager Open Edition (BAMOE). Please correct me if I'm wrong.

I see multiple business tools such as BAMOE, Decision Manager Open Edition (DMOE), and Process Automation Manager Open Edition (PAMOE). Why are there so many tools, and what are their specific uses? While I found several resources for implementing BAMOE, I couldn't find much for DMOE. Where can I find resources on how to install DMOE in OCP?

BAMOE and DMOE. Could someone explain how these tools differ in their uses and functionalities? Specifically, what are the unique features and ideal use cases for each?

Additionally, is DMOE the open-source version of Operational Decision Manager? If anyone has the best resources or guidance, please share them here.

Thank you!

Barry Lulas's profile image
Barry Lulas posted Thu April 17, 2025 12:58 PM

There are two business automation offerings that came from Red Hat, but have been further refined for the hybrid cloud at IBM under the product suite name of BAMOE:

  • Red Hat Decision Manager (RHDM), now referred to as IBM Decision Manager Open Edition (DMOE)
  • Red Hat Process Automation Manager (RHPAM), now referred to as IBM Product Automation Manager Open Edition (PAMOE)

DMOE is focused on business rules and decisions, plus stateless workflow (STP).  PAMOE includes all the decision automation capabilities of DMOE but adds stateful business process management via BPMN.  So you can think of PAMOE as a superset offering.  If your workflow needs persistence, such as having a human task or a timer, then you need PAMOE.  If your workflow is stateless and is simply orchestrating rule tasks, then all you need is DMOE.

There are two product version streams for BAMOE, v8 and v9.  While v8 is basically the legacy product we inherited from Red Hat, based on application server technology, it's mostly a maintenance and migration path release for former Red Hat customers.  v9 is the next generation business automation, based on the community project known as Kogito, which essentially moves the architecture to a cloud-native, micro-service architecture, based on Quarkus or Spring Boot.  

DMOE v8 is based on upstream Drools 7, PAMOE v8 is based on upstream jBPM v7.  DMOE v9 is based on Kogito-Drools 10.x, PAMOE v9 is based on Kogito-jBPM 10.x.

The latest release of BAMOE is 9.2.0, and both the DMOE as well as the PAMOE offerings are now fully powered by Kogito, which means it has been written and optimized for Kubernetes, including OpenShift.  


FYI: There is no relationship between any BAMOE component (DMOE or PAMOE), with other IBM business automation products such as ODM, ADS, or BAW.

Related Content