此内容没有您所选择的语言版本。

Chapter 4. Project deployment options with Red Hat Process Automation Manager


After you develop, test, and build your Red Hat Process Automation Manager project, you can deploy the project to begin using the business assets you have created. You can deploy a Red Hat Process Automation Manager project to a configured Process Server, to an embedded Java application, or into a Red Hat OpenShift Container Platform environment for an enhanced containerized implementation.

The following options are the main methods for Red Hat Process Automation Manager project deployment:

Expand
Table 4.1. Project deployment options
Deployment optionDescriptionDocumentation

Deployment to an OpenShift environment

Red Hat OpenShift Container Platform combines Docker and Kubernetes and enables you to create and manage containers. You can install both Business Central and Process Server on OpenShift. Red Hat Process Automation Manager provides templates that you can use to deploy a Red Hat Process Automation Manager authoring environment, managed server environment, immutable server environment, or trial environment on OpenShift. With OpenShift, components of Red Hat Process Automation Manager are deployed as separate OpenShift pods. You can scale each of the pods up and down individually, providing as few or as many containers as necessary for a particular component. You can use standard OpenShift methods to manage the pods and balance the load.

Deploying a Red Hat Process Automation Manager authoring environment on Red Hat OpenShift Container Platform

Deploying a Red Hat Process Automation Manager managed server environment on Red Hat OpenShift Container Platform

Deploying a Red Hat Process Automation Manager immutable server environment on Red Hat OpenShift Container Platform

Deploying a Red Hat Process Automation Manager trial environment on Red Hat OpenShift Container Platform

Deployment to Process Server

Process Server is the server provided with Red Hat Process Automation Manager that runs the decision services, process applications, and other deployable assets from a packaged and deployed Red Hat Process Automation Manager project (KJAR file). These services are consumed at run time through an instantiated KIE container, or deployment unit. You can deploy and maintain deployment units in Process Server using Business Central or using a headless Process Automation Manager controller with its associated REST API (considered a managed Process Server instance). You can also deploy and maintain deployment units using the Process Server REST API or Java client API from a standalone Maven project, an embedded Java application, or other custom environment (considered an unmanaged Process Server instance).

Packaging and deploying a Red Hat Process Automation Manager project

Interacting with Red Hat Process Automation Manager using KIE APIs

Managing and monitoring Process Server

Deployment to an embedded Java application

If you want to deploy Red Hat Process Automation Manager projects to your own Java virtual machine (JVM) environment, microservice, or application server, you can bundle the application resources in the project WAR files to create a deployment unit similar to a KIE container. You can also use the core KIE APIs (not Process Server APIs) to configure a KIE scanner to periodically update KIE containers.

KIE Public API

返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat