Recommended Free Tools
Red Hat Process Automation Manager (PAM) is an enterprise middleware platform for designing, deploying, and operating business automation applications. jBPM is the process engine inside PAM—not a separate name for the whole product. In the usual architecture, Business Central is the authoring and administration interface, while KIE Server runs the deployed processes, rules, and other business assets.
What Red Hat Process Automation Manager does
Red Hat describes Process Automation Manager as a middleware platform for creating business automation applications and microservices. It helps business and IT teams document, simulate, manage, automate, and monitor business processes and policies.
The scope is broader than workflow alone. A PAM application can combine BPMN-based processes with business rules, decisions, and planning services. For example, a loan process might collect an application, apply eligibility rules, route exceptions to staff, and record each decision for later monitoring.
jBPM, Business Central, and KIE Server: the roles are different
| Part | Role |
|---|---|
| Business Central | Web-based authoring and management interface for creating rules, processes, and related assets; managing connected KIE Servers and KIE containers; and performing runtime operations on processes and tasks. |
| KIE Server | Runtime server that executes rules and other assets, starts and advances process instances, and solves planning problems. Deployments run in KIE containers. |
| jBPM | The process engine integrated into Process Automation Manager. It provides the execution capabilities for business processes. |
This means “jBPM versus Process Automation Manager” is usually the wrong comparison. jBPM is a core engine; PAM is the packaged platform and operating model around that engine.
#1 Best Overall
How a typical PAM installation works
Authoring in Business Central
Teams use Business Central to model BPMN processes, define rules and decisions, configure projects, and review process and task activity. It can also connect to multiple KIE Server instances and manage their deployed containers.
Execution on KIE Server
When a project is deployed, KIE Server executes its processes and rules. A deployment unit is a KIE container, which represents a particular version of a project. Applications and integrations call the server to start processes, complete tasks, evaluate rules, or inspect runtime state.
Using PAM without Business Central
Business Central is not mandatory in every runtime topology. Red Hat documents a headless controller and the REST API or KIE Server Java Client API for managing and interacting with KIE Server when the web authoring environment is not installed. This arrangement is useful when source control, build pipelines, and operational tooling are maintained outside PAM.
Managed and unmanaged KIE Server
KIE Server can operate in two modes:
- Managed mode: a Process Automation Manager controller manages server configuration and KIE containers.
- Unmanaged mode: operators create and maintain KIE containers manually.
The choice is an operations decision, not a feature ranking. Managed mode centralizes controller responsibilities; unmanaged mode can fit teams that already control deployments through scripts or an external release system.
Rank #2
- Loose-leaf Edition
Packaging and deployment
PAM projects are packaged as Knowledge JARs (KJARs). A KJAR contains business assets and project configuration, including Maven project information and KIE module configuration. KJARs are deployed to KIE Server, where a KIE container exposes the runtime services for that version.
Maven GroupId, ArtifactId, and Version identify the artifact. Every version intended for deployment must have a unique version value; reusing coordinates for different content makes release management and rollback ambiguous.
Red Hat documentation describes several supported deployment environments across releases, including JBoss EAP and OpenShift. KIE Server is also documented for Spring Boot, WebLogic, and WebSphere in relevant contexts. Support is release-specific, so verify the supported-configuration matrix for the exact PAM version, patch level, application server, and OpenShift release before installing.
Architecture choices to make before implementation
There is no single PAM topology that is best for every organization. Evaluate these decisions together:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Rank #3
| Decision | Questions to answer |
|---|---|
| Authoring | Will analysts and developers work in Business Central, an external IDE, or both? |
| Source control | Will projects use built-in Git storage, an external Git repository, or a synchronized workflow? |
| Execution | Will processes run on KIE Server or in an embedded engine inside an application? |
| Operations | Should a controller manage containers, or will operators and pipelines manage them directly? |
| Deployment environment | Which documented runtime—such as OpenShift or JBoss EAP—matches the target release and operational standards? |
| Migration | What existing BPMN models, rules, APIs, monitoring integrations, and support obligations must remain compatible? |
Version details and lifecycle cautions
Red Hat’s 7.13 component details list jBPM 7.67 and KIE Server 7.67. These are component versions for Process Automation Manager 7.13, not a claim that jBPM 7.67 is the newest jBPM release generally.
The 7.13 release documentation describes configurations involving JBoss EAP 7.4.x, Spring Boot 2.5.12, Red Hat JBoss Web Server 5.6, and OpenShift 4.12, with patch-specific qualifications. Check the official supported-configuration table for the precise 7.13 patch you plan to run.
Version changes can affect design and upgrades. Red Hat states that the legacy process designer was removed in Process Automation Manager 7.13.5 and recommends migration to the new designer. The 7.13 release notes also identify deprecated components or APIs and discuss maintenance support for included OptaPlanner components. A statement about 7.13 should not be generalized to every PAM release or to every customer’s support entitlement.
Red Hat’s documentation establishes 7.13 materials and component mappings, but it does not by itself establish a current lifecycle phase or definitive end-of-support date. Confirm those details in Red Hat’s lifecycle record for the exact product version.
Where Kogito fits
Kogito appears in the PAM 7.13 documentation and supported-configuration ecosystem, including constraints for Kogito decision services, runtimes, and interaction routes. The available documentation does not establish Kogito as a drop-in replacement for every jBPM or PAM application.
Any migration assessment should check process features, runtime model, APIs, monitoring, support conditions, and the available migration path for the specific application. Treat “successor” language as a starting point for evaluation rather than a compatibility guarantee.
Is jBPM included in Red Hat Process Automation Manager?
Yes. Red Hat identifies jBPM as the integrated process engine in Process Automation Manager. PAM adds the surrounding authoring, project, deployment, controller, runtime, and management capabilities. The exact jBPM version depends on the PAM release; for PAM 7.13, Red Hat lists jBPM 7.67.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
What is KIE Server?
KIE Server is the runtime component that executes deployed processes, rules, and other business assets. Deployments are represented by versioned KIE containers.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteCan Process Automation Manager run without Business Central?
Yes. Red Hat documents headless-controller options and REST or KIE Server Java Client APIs for managing and using KIE Server without the Business Central interface.
Is jBPM the same product as Process Automation Manager?
No. jBPM is the process engine integrated into the broader Process Automation Manager platform.
The Bottom Line
Think of the product as a layered platform: Business Central designs and manages assets, KIE Server runs versioned deployments, and jBPM supplies the process engine. Choose the topology, runtime, and migration path against the exact PAM release and its supported-configuration documentation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →
