Red Hat Process Automation Manager, formerly JBoss BPM Suite, packaged jBPM and Drools; its 7.x line is past end of life and IBM BAMOE succeeds it. Pages here cover moving to Apache KIE, Flowable or IBM's successor.
Red Hat Process Automation Manager 7.x is past end of life and its extended support has ended. This page compares the three ways forward: IBM's BAMOE subscription, self-supported Apache KIE, or a move to Flowable, by code changes, support and risk.
Moving Red Hat PAM 7 projects to the Apache KIE 10 line: which BPMN, DMN and rule assets to test first, moving from KIE Server and Business Central to the Kogito-based runtime on Quarkus or Spring Boot, and living with an incubating ASF project.
Moving jBPM processes from Red Hat PAM to Flowable: re-validating BPMN models on Flowable's engine, replacing work item handlers with Flowable service tasks, deciding where Drools rules go, and draining in-flight process instances.
Comparing what Red Hat PAM teams had, jBPM processes with Drools rules and Business Central, with Flowable's BPMN, CMMN and DMN engines and its commercial editions, to judge whether Flowable is a better long-term home than the jBPM lineage.
Red Hat Decision Manager reached end of life with PAM. For rule-heavy applications: running Drools and DMN from Apache KIE, IBM's Decision Manager Open Edition, or Flowable's DMN engine for simpler decision tables.
Cost of ownership by component: an IBM BAMOE subscription against running Apache KIE without a vendor, covering migration effort, the in-house or partner support you need for an incubating project, upgrades, and risk.
Tell us what you're working on, whether it's a deployment, an audit, a security test or a cyber range. You'll speak with an engineer who can help you scope it.