Red Hat Process Automation Manager 7.5 …...With Red Hat Process Automation Manager, you can set up a development environment to develop business applications, a runtime environment

Red Hat Process Automation Manager7.5

Designing your decision managementarchitecture for Red Hat Process Automation

Manager

Last Updated: 2020-05-22

Red Hat Process Automation Manager 7.5 Designing your decisionmanagement architecture for Red Hat Process Automation Manager

Red Hat Customer Content [email protected]

Legal Notice

Copyright © 2020 Red Hat, Inc.

The text of and illustrations in this document are licensed by Red Hat under a Creative CommonsAttribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA isavailable athttp://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you mustprovide the URL for the original version.

Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert,Section 4d of CC-BY-SA to the fullest extent permitted by applicable law.

Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift,Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United Statesand other countries.

Linux ® is the registered trademark of Linus Torvalds in the United States and other countries.

Java ® is a registered trademark of Oracle and/or its affiliates.

XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United Statesand/or other countries.

MySQL ® is a registered trademark of MySQL AB in the United States, the European Union andother countries.

Node.js ® is an official trademark of Joyent. Red Hat is not formally related to or endorsed by theofficial Joyent Node.js open source or commercial project.

The OpenStack ® Word Mark and OpenStack logo are either registered trademarks/service marksor trademarks/service marks of the OpenStack Foundation, in the United States and othercountries and are used with the OpenStack Foundation's permission. We are not affiliated with,endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.

All other trademarks are the property of their respective owners.

Abstract

This document describes basic concepts and options for a Red Hat Process Automation Managerimplementation to consider when designing your decision management architecture. To verify themost suitable implementation for your environment, contact your Red Hat Technical AccountManager or Solutions Architect.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Table of Contents

PREFACE

CHAPTER 1. INSTALLATION ENVIRONMENT OPTIONS FOR RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 2. DECISION-AUTHORING ASSETS IN RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 3. PROJECT STORAGE AND BUILD OPTIONS WITH RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 4. PROJECT DEPLOYMENT OPTIONS WITH RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 5. ASSET EXECUTION OPTIONS WITH RED HAT PROCESS AUTOMATION MANAGER

CHAPTER 6. EXAMPLE DECISION MANAGEMENT ARCHITECTURES WITH RED HAT PROCESSAUTOMATION MANAGER

CHAPTER 7. ADDITIONAL RESOURCES

APPENDIX A. VERSIONING INFORMATION

3

4

5

9

12

15

16

21

22

Table of Contents

1

Red Hat Process Automation Manager 7.5 Designing your decision management architecture for Red Hat Process Automation Manager

2

PREFACEAs a business analyst, systems administrator, or business rules developer, the types of Red Hat ProcessAutomation Manager business assets that you create and the way in which you develop, store, execute,and deploy those assets varies based on the needs of your business automation environment. You candesign a decision management architecture that uses Business Central or an external integrateddevelopment environment (IDE) for asset development, a built-in or external Git repository for storageand version control, a Process Server or embedded application for deployment, or other implementationcombinations. You can also deploy Red Hat Process Automation Manager into a Red Hat OpenShiftContainer Platform environment for an enhanced containerized implementation.

This document describes basic concepts and options for a Red Hat Process Automation Managerimplementation to consider when designing your decision management architecture. To verify the mostsuitable implementation for your environment, contact your Red Hat Technical Account Manager orSolutions Architect.

PREFACE

3

CHAPTER 1. INSTALLATION ENVIRONMENT OPTIONS FORRED HAT PROCESS AUTOMATION MANAGER

With Red Hat Process Automation Manager, you can set up a development environment to developbusiness applications, a runtime environment to run those applications to support decisions, or both.

Development environment: Typically consists of one Business Central installation and at leastone Process Server installation. You can use Business Central to design decisions and otherartifacts, and you can use Process Server to execute and test the artifacts that you created.

Runtime environment: Consists of one or more Process Server instances with or withoutBusiness Central. Business Central has an embedded Process Automation Manager controller. Ifyou install Business Central, use the Menu → Deploy → Execution servers page to create andmaintain containers. If you want to automate Process Server management without BusinessCentral, you can use the headless Process Automation Manager controller.

You can also cluster both development and runtime environments. A clustered development or runtimeenvironment consists of a unified group or "cluster" of two or more servers. The primary benefit ofclustering Red Hat Process Automation Manager development environments is high availability andenhanced collaboration, while the primary benefit of clustering Red Hat Process Automation Managerruntime environments is high availability and load balancing. High availability decreases the chance of aloss of data when a single server fails. When a server fails, another server fills the gap by providing a copyof the data that was on the failed server. When the failed server comes online again, it resumes its placein the cluster. Load balancing shares the computing load across the nodes of the cluster to improve theoverall performance.

NOTE

Clustering of the runtime environment is currently supported on Red Hat JBoss EAP 7.2and Red Hat OpenShift Container Platform only. Clustering of Business Central iscurrently a Technology Preview feature that is not yet intended for production use. Formore information about Red Hat Technology Preview support, see Technology PreviewFeatures Support Scope.

Additional resources

Planning a Red Hat Process Automation Manager installation

Red Hat Process Automation Manager 7 Supported Configurations

Red Hat Process Automation Manager 7 Component Details


4

https://access.redhat.com/support/offerings/techpreview/

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/planning_a_red_hat_process_automation_manager_installation

https://access.redhat.com/articles/3405381

https://access.redhat.com/articles/3463751

CHAPTER 2. DECISION-AUTHORING ASSETS IN RED HATPROCESS AUTOMATION MANAGER

Red Hat Process Automation Manager supports several assets that you can use to define businessdecisions for your decision service. Each decision-authoring asset has different advantages, and youmight prefer to use one or a combination of multiple assets depending on your goals and needs.

The following table highlights the main decision-authoring assets supported in Red Hat ProcessAutomation Manager projects to help you decide or confirm the best method for defining decisions inyour decision service.

Table 2.1. Decision-authoring assets supported in Red Hat Process Automation Manager

Asset Highlights Authoring tools Documentation

Decision Modeland Notation(DMN) models

Are decision models based on anotation standard defined by theObject Management Group(OMG)

Use graphical decisionrequirements diagrams (DRDs)with one or more decisionrequirements graphs (DRGs) totrace business decision flows

Use an XML schema that allowsthe DMN models to be sharedbetween DMN-compliantplatforms

Support Friendly EnoughExpression Language (FEEL) todefine decision logic in DMNdecision tables and other DMNboxed expressions

Can be integrated efficientlywith Business Process Model andNotation (BPMN) processmodels

Are optimal for creatingcomprehensive, illustrative, andstable decision flows

Business Centralor other DMN-compliant editor

Designing adecision serviceusing DMN models


5

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_dmn_models

Guided decisiontables Are tables of rules that you

create in a UI-based tabledesigner in Business Central

Are a wizard-led alternative tospreadsheet decision tables

Provide fields and options foracceptable input

Support template keys andvalues for creating ruletemplates

Support hit policies, real-timevalidation, and other additionalfeatures not supported in otherassets

Are optimal for creating rules ina controlled tabular format tominimize compilation errors

Business Central Designing adecision serviceusing guideddecision tables

Spreadsheetdecision tables Are XLS or XLSX spreadsheet

decision tables that you canupload into Business Central

Support template keys andvalues for creating ruletemplates

Are optimal for creating rules indecision tables already managedoutside of Business Central

Have strict syntax requirementsfor rules to be compiled properlywhen uploaded

Spreadsheeteditor

Designing adecision serviceusing spreadsheetdecision tables

Guided rulesAre individual rules that youcreate in a UI-based ruledesigner in Business Central


Are optimal for creating singlerules in a controlled format tominimize compilation errors

Business Central Designing adecision serviceusing guided rules



6

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_guided_decision_tables

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_spreadsheet_decision_tables

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_guided_rules

Guided ruletemplates Are reusable rule structures that

you create in a UI-basedtemplate designer in BusinessCentral


Support template keys andvalues for creating ruletemplates (fundamental to thepurpose of this asset)

Are optimal for creating manyrules with the same rule structurebut with different defined fieldvalues

Business Central Designing adecision serviceusing guided ruletemplates

DRL rulesAre individual rules that youdefine directly in .drl text files

Provide the most flexibility fordefining rules and othertechnicalities of rule behavior

Can be created in certainstandalone environments andintegrated with Red Hat ProcessAutomation Manager

Are optimal for creating rulesthat require advanced DRLoptions

Have strict syntax requirementsfor rules to be compiled properly

Business Centralor integrateddevelopmentenvironment (IDE)

Designing adecision serviceusing DRL rules



7

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_guided_rule_templates

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_drl_rules

Predictive ModelMarkup Language(PMML) models

Are predictive data-analyticmodels based on a notationstandard defined by the DataMining Group (DMG)

Use an XML schema that allowsthe PMML models to be sharedbetween PMML-compliantplatforms

Support Regression, Scorecard,Tree, Mining, and other modeltypes

Can be included with astandalone Red Hat ProcessAutomation Manager project orimported into a project inBusiness Central

Are optimal for incorporatingpredictive data into decisionservices in Red Hat ProcessAutomation Manager

PMML or XMLeditor

Designing adecision serviceusing PMMLmodels



8

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_pmml_models

CHAPTER 3. PROJECT STORAGE AND BUILD OPTIONS WITHRED HAT PROCESS AUTOMATION MANAGER

As you develop a Red Hat Process Automation Manager project, you need to be able to track theversions of your project with a version-controlled repository, manage your project assets in a stableenvironment, and build your project for testing and deployment. You can use Business Central for all ofthese tasks, or use a combination of Business Central and external tools and repositories. Red HatProcess Automation Manager supports Git repositories for project version control, Apache Maven forproject management, and a variety of Maven-based, Java-based, or custom-tool-based build options.

The following options are the main methods for Red Hat Process Automation Manager projectversioning, storage, and building:

Table 3.1. Project version control options (Git)

Versioning option Description Documentation

Business Central GitVFS

Business Central contains a built-in Git Virtual FileSystem (VFS) that stores all processes, rules, andother artifacts that you create in the authoringenvironment. Git is a distributed version controlsystem that implements revisions as commit objects.When you commit your changes into a repository, anew commit object in the Git repository is created.When you create a project in Business Central, theproject is added to the Git repository connected toBusiness Central.

NA

External Git repository If you have Red Hat Process Automation Managerprojects in Git repositories outside of BusinessCentral, you can import them into Red Hat ProcessAutomation Manager spaces and use Git hooks tosynchronize the internal and external Git repositories.

Managing projects inBusiness Central

Table 3.2. Project management options (Maven)

Management option Description Documentation


9

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/managing_projects_in_business_central#git-import-project

Business Central Mavenrepository

Business Central contains a built-in Maven repositorythat organizes and builds project assets that youcreate in the authoring environment. Maven is adistributed build-automation tool that usesrepositories to store Java libraries, plug-ins, andother build artifacts. When building projects andarchetypes, Maven dynamically retrieves Javalibraries and Maven plug-ins from local or remoterepositories to promote shared dependencies acrossprojects.

NOTE

For a production environment,consider using an external Mavenrepository configured with BusinessCentral.

NA

External Mavenrepository

If you have Red Hat Process Automation Managerprojects in an external Maven repository, such asNexus or Artifactory, you can create a settings.xmlfile with connection details and add that file path tothe kie.maven.settings.custom property in yourproject standalone-full.xml file.

Maven SettingsReference

Packaging and deployinga Red Hat ProcessAutomation Managerproject

Management option Description Documentation

Table 3.3. Project build options

Build option Description Documentation

Business Central (KJAR) Business Central builds Red Hat Process AutomationManager projects stored in either the built-in Mavenrepository or a configured external Maven repository.Projects in Business Central are packagedautomatically as knowledge JAR (KJAR) files with allcomponents needed for deployment when you buildthe projects.


Standalone Mavenproject (KJAR)

If you have a standalone Red Hat ProcessAutomation Manager Maven project outside ofBusiness Central, you can edit the project pom.xmlfile to package your project as a KJAR file, and thenadd a kmodule.xml file with the KIE base and KIEsession configurations needed to build the project.



10

https://maven.apache.org/settings.html

https://maven.apache.org/settings.html

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/packaging_and_deploying_a_red_hat_process_automation_manager_project#maven-external-configure-proc_packaging-deploying

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/packaging_and_deploying_a_red_hat_process_automation_manager_project

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/packaging_and_deploying_a_red_hat_process_automation_manager_project#project-build-deploy-maven-proc_packaging-deploying

Embedded Javaapplication (KJAR)

If you have an embedded Java application fromwhich you want to build your Red Hat ProcessAutomation Manager project, you can use a KieModuleModel instance to programaticallycreate a kmodule.xml file with the KIE base and KIEsession configurations, and then add all resources inyour project to the KIE virtual file system KieFileSystem to build the project.


CI/CD tool (KJAR) If you use a tool for continuous integration andcontinuous delivery (CI/CD), you can configure thetool set to integrate with your Red Hat ProcessAutomation Manager Git repositories to build aspecified project. Ensure that your projects arepackaged and built as KJAR files to ensure optimaldeployment.

NA

S2I in OpenShift(container image)

If you use Red Hat Process Automation Manager onRed Hat OpenShift Container Platform, you canbuild your Red Hat Process Automation Managerprojects as KJAR files in the typical way or useSource-to-Image (S2I) to build your projects ascontainer images. S2I is a framework and a tool thatallows you to write images that use the applicationsource code as an input and produce a new imagethat runs the assembled application as an output. Themain advantage of using the S2I tool for buildingreproducible container images is the ease of use fordevelopers.

Creating Images inOpenShift

Build option Description Documentation


11

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/packaging_and_deploying_a_red_hat_process_automation_manager_project#project-build-deploy-java-proc_packaging-deploying

https://access.redhat.com/documentation/en-us/openshift_container_platform/3.3/html/creating_images/creating-images-s2i

CHAPTER 4. PROJECT DEPLOYMENT OPTIONS WITH REDHAT PROCESS AUTOMATION MANAGER

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

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

Table 4.1. Project deployment options

Deployment option Description Documentation


12

Deployment to anOpenShift environment

Red Hat OpenShift Container Platform combinesDocker and Kubernetes and enables you to createand manage containers. You can install both BusinessCentral and Process Server on OpenShift. Red HatProcess Automation Manager provides templatesthat you can use to deploy a Red Hat ProcessAutomation Manager authoring environment,managed server environment, immutable serverenvironment, or trial environment on OpenShift. WithOpenShift, components of Red Hat ProcessAutomation Manager are deployed as separateOpenShift pods. You can scale each of the pods upand down individually, providing as few or as manycontainers as necessary for a particular component.You can use standard OpenShift methods to managethe pods and balance the load.

Deploying a Red HatProcess AutomationManager immutableserver environment onRed Hat OpenShiftContainer Platform

Deploying a Red HatProcess AutomationManager authoringenvironment on Red HatOpenShift ContainerPlatform

Deploying a Red HatProcess AutomationManager freeformmanaged serverenvironment on Red HatOpenShift ContainerPlatform

Deploying a Red HatProcess AutomationManager environment onRed Hat OpenShiftContainer Platform usingAutomation Broker

Deploying a Red HatProcess AutomationManager environment onRed Hat OpenShiftContainer Platform usingOperators

Deploying a Red HatProcess AutomationManager trialenvironment on Red HatOpenShift ContainerPlatform


CHAPTER 4. PROJECT DEPLOYMENT OPTIONS WITH RED HAT PROCESS AUTOMATION MANAGER

13

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_immutable_server_environment_on_red_hat_openshift_container_platform

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_authoring_environment_on_red_hat_openshift_container_platform

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_freeform_managed_server_environment_on_red_hat_openshift_container_platform

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_environment_on_red_hat_openshift_container_platform_using_automation_broker

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_environment_on_red_hat_openshift_container_platform_using_operators

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/deploying_a_red_hat_process_automation_manager_trial_environment_on_red_hat_openshift_container_platform

Deployment to ProcessServer

Process Server is the server provided with Red HatProcess Automation Manager that runs the decisionservices, process applications, and other deployableassets from a packaged and deployed Red HatProcess Automation Manager project (KJAR file).These services are consumed at run time through aninstantiated KIE container, or deployment unit. Youcan deploy and maintain deployment units in ProcessServer using Business Central or using a headlessProcess Automation Manager controller with itsassociated REST API (considered a managedProcess Server instance). You can also deploy andmaintain deployment units using the Process ServerREST API or Java client API from a standaloneMaven project, an embedded Java application, orother custom environment (considered anunmanaged Process Server instance).


Interacting with Red HatProcess AutomationManager using KIE APIs

Managing andmonitoring ProcessServer

Deployment to anembedded Javaapplication

If you want to deploy Red Hat Process AutomationManager projects to your own Java virtual machine(JVM) environment, microservice, or applicationserver, you can bundle the application resources inthe project WAR files to create a deployment unitsimilar to a KIE container. You can also use the coreKIE APIs (not Process Server APIs) to configure a KIEscanner to periodically update KIE containers.

KIE Public API



14


https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/interacting_with_red_hat_process_automation_manager_using_kie_apis

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/managing_and_monitoring_process_server

http://docs.jboss.org/drools/release/latestFinal/kie-api-javadoc/

CHAPTER 5. ASSET EXECUTION OPTIONS WITH RED HATPROCESS AUTOMATION MANAGER

After you build and deploy your Red Hat Process Automation Manager project to Process Server orother environment, you can execute the deployed assets for testing or for runtime consumption. Youcan also execute assets locally in addition to or instead of executing them after deployment.

The following options are the main methods for Red Hat Process Automation Manager asset execution:

Table 5.1. Asset execution options

Execution option Description Documentation

Execution in ProcessServer

If you deployed Red Hat Process AutomationManager project assets to Process Server, you canuse the Process Server REST API or Java client APIto execute and interact with the deployed assets.You can also use Business Central or the headlessProcess Automation Manager controller outside ofBusiness Central to manage the configurations andKIE containers in the Process Server instancesassociated with your deployed assets. For processdefinitions, you can use Business Central directly toexecute process instances.

Interacting with Red HatProcess AutomationManager using KIE APIs

Execution in anembedded Javaapplication

If you deployed Red Hat Process AutomationManager project assets in your own Java virtualmachine (JVM) environment, microservice, orapplication server, you can use custom APIs orapplication interactions with core KIE APIs (notProcess Server APIs) to execute assets in theembedded engine.

KIE Public API

Execution in a localenvironment forextended testing

As part of your development cycle, you can executeassets locally to ensure that the assets you havecreated in Red Hat Process Automation Managerfunction as intended. You can use local execution inaddition to or instead of executing assets afterdeployment.

"Executing rules" inDesigning a decisionservice using DRL rules

SMART ROUTER (PROCESS SERVER ROUTER)

Depending on your deployment and execution environment, you can use a Smart Routerto aggregate multiple independent Process Server instances as though they are a singleserver. Smart Router is a single endpoint that can receive calls from client applications toany of your services and route each call automatically to the Process Server that runs theservice. For more information about Smart Router, see Installing and configuring Red HatProcess Automation Manager in a Red Hat JBoss EAP clustered environment.

CHAPTER 5. ASSET EXECUTION OPTIONS WITH RED HAT PROCESS AUTOMATION MANAGER

15

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/interacting_with_red_hat_process_automation_manager_using_kie_apis

http://docs.jboss.org/drools/release/latestFinal/kie-api-javadoc/

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/designing_a_decision_service_using_drl_rules#assets-executing-proc_drl-rules

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/installing_and_configuring_red_hat_process_automation_manager_in_a_red_hat_jboss_eap_clustered_environment#clustering-smartrouter-install-proc

CHAPTER 6. EXAMPLE DECISION MANAGEMENTARCHITECTURES WITH RED HAT PROCESS AUTOMATION

MANAGERThe following scenarios illustrate common variations of Red Hat Process Automation Managerinstallation, asset authoring, project storage, project deployment, and asset execution in a decisionmanagement architecture. Each section summarizes the methods and tools used and the advantagesfor the given architecture. The examples are basic and are only a few of the many combinations youmight consider, depending on your specific goals and needs with Red Hat Process Automation Manager.

Red Hat Process Automation Manager authoring and managed server environments on OpenShiftwith Business Central and Process Server

Installation environment: Red Hat Process Automation Manager on Red Hat OpenShiftContainer Platform, using the rhpam75-authoring.yaml and rhpam75-kieserver.yamltemplate files

Project storage and build environment: External Git repository for project versioningsynchronized with the Business Central Git repository using Git hooks, and external Mavenrepository for project management and building configured with Process Server

Asset-authoring tool: Business Central

Main asset types: Decision Model and Notation (DMN) models for decisions and BusinessProcess Model and Notation (BPMN) models for processes

Project deployment and execution environment: Process Server on Red Hat OpenShiftContainer Platform

Scenario advantages:

Containerized implementation of Red Hat Process Automation Manager in a cloud-based development environment. Components of Red Hat Process AutomationManager are deployed as separate OpenShift pods that you can scale up and downindividually, providing as few or as many containers as necessary for a particularcomponent. You can use standard OpenShift methods to manage the pods and balancethe load.

Access to the repositories, assets, asset designers, and project build options in BusinessCentral.

Standardized asset-authoring approach using DMN and BPMN for optimal integrationand stability.

Access to Process Server functionality and KIE APIs for asset deployment andexecution.

Figure 6.1. Red Hat Process Automation Manager on OpenShift with Business Central and


16

Figure 6.1. Red Hat Process Automation Manager on OpenShift with Business Central andProcess Server

Red Hat Process Automation Manager on Red Hat JBoss EAP with Business Central and ProcessServer

Installation environment: Red Hat Process Automation Manager on Red Hat JBossEnterprise Application Platform

Project storage and build environment: External Git repository for project versioningsynchronized with the Business Central Git repository using Git hooks, and external Mavenrepository for project management and building configured with Process Server

Asset-authoring tool: Business Central

Main asset types: Decision Model and Notation (DMN) models for decisions and BusinessProcess Model and Notation (BPMN) models for processes

Project deployment and execution environment: Process Server


Stable implementation of Red Hat Process Automation Manager in an on-premisedevelopment environment

Access to the repositories, assets, asset designers, and project build options in BusinessCentral

Standardized asset-authoring approach using DMN and BPMN for optimal integrationand stability

Access to Process Server functionality and KIE APIs for asset deployment and execution

Figure 6.2. Red Hat Process Automation Manager on Red Hat JBoss EAP with Business Central

CHAPTER 6. EXAMPLE DECISION MANAGEMENT ARCHITECTURES WITH RED HAT PROCESS AUTOMATION MANAGER

17

Figure 6.2. Red Hat Process Automation Manager on Red Hat JBoss EAP with Business Centraland Process Server

Red Hat Process Automation Manager on Red Hat JBoss EAP with an IDE and Process Server

Installation environment: Red Hat Process Automation Manager on Red Hat JBossEnterprise Application Platform

Project storage and build environment: External Git repository for project versioning (notsynchronized with Business Central) and external Maven repository for project managementand building configured with Process Server

Asset-authoring tools: Integrated development environment (IDE), such as Red HatCodeReady Studio, and a spreadsheet editor or a Decision Model and Notation (DMN)modeling tool for other decision formats

Main asset types: Drools Rule Language (DRL) rules, spreadsheet decision tables, andDecision Model and Notation (DMN) models for decisions, and Business Process Model andNotation (BPMN) models for processes

Project deployment and execution environment: Process Server


Flexible implementation of Red Hat Process Automation Manager in an on-premisedevelopment environment

Ability to define business assets using an external IDE and other asset-authoring tools ofyour choice

Access to Process Server functionality and KIE APIs for asset deployment and execution

Figure 6.3. Red Hat Process Automation Manager on Red Hat JBoss EAP with an IDE and


18

Figure 6.3. Red Hat Process Automation Manager on Red Hat JBoss EAP with an IDE andProcess Server

Red Hat Process Automation Manager with an IDE and an embedded Java application

Installation environment: Red Hat Process Automation Manager libraries embedded withina custom application

Project storage and build environment: External Git repository for project versioning (notsynchronized with Business Central) and external Maven repository for project managementand building configured with your embedded Java application (not configured with ProcessServer)

Asset-authoring tools: Integrated development environment (IDE), such as Red HatCodeReady Studio, and a spreadsheet editor or a Decision Model and Notation (DMN)modeling tool for other decision formats

Main asset types: Drools Rule Language (DRL) rules, spreadsheet decision tables, andDecision Model and Notation (DMN) models for decisions, and Business Process Model andNotation (BPMN) models for processes

Project deployment and execution environment: Embedded Java application, such as in aJava virtual machine (JVM) environment, microservice, or custom application server


Custom implementation of Red Hat Process Automation Manager in an on-premisedevelopment environment with an embedded Java application

Ability to define business assets using an external IDE and other asset-authoring tools ofyour choice

Use of custom APIs to interact with core KIE APIs (not Process Server APIs) and toexecute assets in the embedded engine

Figure 6.4. Red Hat Process Automation Manager with an IDE and an embedded Java

CHAPTER 6. EXAMPLE DECISION MANAGEMENT ARCHITECTURES WITH RED HAT PROCESS AUTOMATION MANAGER

19

Figure 6.4. Red Hat Process Automation Manager with an IDE and an embedded Javaapplication


20

CHAPTER 7. ADDITIONAL RESOURCESPlanning a Red Hat Process Automation Manager installation

Getting started with decision services

Getting started with Red Hat Business Optimizer

Getting started with business processes

Packaging and deploying a Red Hat Process Automation Manager project

CHAPTER 7. ADDITIONAL RESOURCES

21

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/planning_a_red_hat_process_automation_manager_installation

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/getting_started_with_decision_services

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/getting_started_with_red_hat_business_optimizer

https://access.redhat.com/documentation/en-us/red_hat_process_automation_manager/7.5/html-single/getting_started_with_business_processes


APPENDIX A. VERSIONING INFORMATIONDocumentation last updated on Thursday, October 31, 2019.


22

Documents

Red Hat Process Automation Manager 7.5 …...With Red Hat Process Automation Manager, you can set up a development environment to develop business applications, a runtime environment