Installing and configuring Red Hat Decision Manager

Red Hat Decision Manager 7.10

Abstract

This document describes how to install Red Hat Decision Manager components on Red Hat JBoss EAP, in an Red Hat JBoss EAP clustered environment, on JBoss Web Server, and in other supported environments.

Preface

As a developer or system administrator, you can install Red Hat Decision Manager components on Red Hat JBoss EAP, in an Red Hat JBoss EAP clustered environment, on JBoss Web Server, and in other supported environments.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.

Part I. Planning a Red Hat Decision Manager installation

As a system administrator, you have several options for installing Red Hat Decision Manager.

Chapter 1. Red Hat Decision Manager versioning

Red Hat Decision Manager versions are designated with a numerical Major.Minor.Patch format, such as 7.5.1. In this example, the major release is 7.x.x, the minor release is 7.5.x, and the patch release is 7.5.1. Major releases often require data migration, while minor release upgrades and patch updates are typically managed with update tools provided with the Red Hat Decision Manager release artifacts.

The following are the general types of releases for Red Hat Decision Manager:

Major release migrations

Major releases of Red Hat Decision Manager include substantial enhancements, security updates, bug fixes, and possibly redesigned features and functions. Data migration is typically required when an application is moved from one major release to another major release, such as from Red Hat JBoss BRMS 6.4.x to Red Hat Decision Manager 7.0. Automated migration tools are often provided with new major versions of Red Hat Decision Manager to facilitate migration, but some manual effort is likely required for certain data and configurations. The supported migration paths are specified in product announcements and documentation.

For example migration instructions, see Migrating from Red Hat JBoss BRMS 6.4 to Red Hat Decision Manager 7.0.

Minor release upgrades

Minor releases of Red Hat Decision Manager include enhancements, security updates, and bug fixes. Data migration may be required when an application is moved from one minor release to another minor release, such as from Red Hat Decision Manager 7.5.x to 7.6. Automated update tools are often provided with both patch updates and new minor versions of Red Hat Decision Manager to facilitate updating certain components of Red Hat Decision Manager, such as Business Central, KIE Server, and the headless Decision Manager controller. Other Red Hat Decision Manager artifacts, such as the decision engine and standalone Business Central, are released as new artifacts with each minor release and you must re-install them to apply the update.

Before you upgrade to a new minor release, apply the latest patch update to your current version of Red Hat Decision Manager to ensure that the minor release upgrade is successful.

Patch updates

Patch updates of Red Hat Decision Manager include the latest security updates and bug fixes. Scheduled patch updates contain all previously released patch updates for that minor version of the product, so you do not need to apply each patch update incrementally in order to apply the latest update. For example, you can update Red Hat Decision Manager 7.5.0 or 7.5.1 to Red Hat Decision Manager 7.5.2. However, for optimal Red Hat Decision Manager performance, apply product updates as they become available. Occasionally, unscheduled patch updates may be released outside the normal update cycle of the existing product. These may include security or other updates provided by Red Hat Global Support Services (GSS) to fix specific issues, and may not be cumulative updates.

Automated update tools are often provided with both patch updates and new minor versions of Red Hat Decision Manager to facilitate updating certain components of Red Hat Decision Manager, such as Business Central, KIE Server, and the headless Decision Manager controller. Other Red Hat Decision Manager artifacts, such as the decision engine and standalone Business Central, are released as new artifacts with each minor release and you must re-install them to apply the update.

To ensure optimal transition between releases and to keep your Red Hat Decision Manager distribution current with the latest enhancements and fixes, apply new product releases and updates to Red Hat Decision Manager as they become available in the Red Hat Customer Portal. Consider also enabling product notifications in the Red Hat Customer Portal.

Chapter 2. Red Hat Decision Manager components

Red Hat Decision Manager is made up of Business Central and KIE Server.

Business Central is the graphical user interface where you create and manage business rules. You can install Business Central in a Red Hat JBoss EAP instance or on the Red Hat OpenShift Container Platform (OpenShift).
Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server.
KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. You can install KIE Server in a Red Hat JBoss EAP instance, in a Red Hat JBoss EAP cluster, on OpenShift, in an Oracle WebLogic server instance, in an IBM WebSphere Application Server instance, or as a part of Spring Boot application.
You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). A KIE container is a specific version of a project. If KIE Server is managed, the Decision Manager controller manages the KIE Server configuration and you interact with the Decision Manager controller to create and maintain KIE containers.
The Decision Manager controller is integrated with Business Central. If you install Business Central on Red Hat JBoss EAP, use the Execution Server page to create and maintain KIE containers. However, if you do not install Business Central, you can install the headless Decision Manager controller and use the REST API or the KIE Server Java Client API to interact with it.
Red Hat Business Optimizer is integrated in Business Central and KIE Server. It is a lightweight, embeddable planning engine that optimizes planning problems. Red Hat Business Optimizer helps Java programmers solve planning problems efficiently, and it combines optimization heuristics and metaheuristics with efficient score calculations.

Chapter 3. Red Hat Decision Manager installation platforms

Every Red Hat Decision Manager release is certified on a variety of operating systems, JVMs, web browsers, and database combinations. Red Hat provides both production and development support for supported and tested configurations in both physical and virtual environments, according to your subscription agreement. See the following pages for information about supported configurations and version numbers:

Red Hat Decision Manager 7.10 is available for the following application platforms:

Red Hat JBoss EAP
Red Hat JBoss Web Server
Red Hat OpenShift Container Platform
Oracle WebLogic Server
IBM WebSphere Application Server

3.1. Red Hat JBoss EAP

Red Hat JBoss Enterprise Application Platform (Red Hat JBoss EAP) is a certified implementation of the Java Enterprise Edition 7 (Java EE 7) full and web profile specifications. Red Hat JBoss EAP provides preconfigured options for features such as high availability, clustering, messaging, and distributed caching. It also enables users to write, deploy, and run applications using the various APIs and services that Red Hat JBoss EAP provides.

You can install both Business Central and KIE Server in a single Red Hat JBoss EAP instance. However, in production environments you should install them in separate instances.

3.2. Red Hat JBoss Web Server

Red Hat JBoss Web Server is an enterprise-ready web server designed for medium and large applications, based on Tomcat. Red Hat JBoss Web Server provides organizations with a single deployment platform for Java Server Pages (JSP) and Java Servlet technologies, PHP, and CGI.

You can install KIE Server and the headless Decision Manager controller on Red Hat JBoss Web Server.

3.3. Red Hat OpenShift Container Platform

Red Hat OpenShift Container Platform (OpenShift) uses Kubernetes and provides an API to manage these services. OpenShift enables you to create and manage containers.

In this solution, components of Red Hat Decision 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.

You can install both Business Central and KIE Server on OpenShift.

3.4. Oracle WebLogic Server

Oracle WebLogic Server is a Java EE application server that provides a standard set of APIs for creating distributed Java applications that can access a wide variety of services, such as databases, messaging services, and connections to external enterprise systems. Users access these applications using web browser clients or Java clients.

You can install KIE Server in an Oracle WebLogic Server instance and then use the headless Decision Manager controller and the REST API or the KIE Server Java Client API to interact with KIE Server. You can also use standalone Business Central to interact with KIE Server.

3.5. IBM WebSphere Application Server

IBM WebSphere Application Server is a flexible and secure web application server that hosts Java-based web applications and provides Java EE-certified run time environments. IBM WebSphere 9.0 supports Java SE 8 and is fully compliant with Java EE 7 since version 8.5.5.6.

You can install KIE Server in an IBM WebSphere Application Server instance and then use the headless Decision Manager controller to interact with KIE Server. You can also use standalone Business Central to interact with KIE Server.

Chapter 4. Red Hat Decision Manager supported repositories

You can use Git repositories and Apache Maven with Red Hat Decision Manager.

4.1. Git repositories

Git repositories are used internally within Business Central to store all processes, rules, and other artifacts that are created in the authoring environment. Git is a distributed version control system. It implements revisions as commit objects. When you commit your changes into a repository, a new commit object in the Git repository is created. When you create a project in Business Central, it is added to the Git repository that is connected to Business Central.

If you have projects in other Git repositories, you can import them into Business Central spaces. You can use Git hooks to synchronize the internal Git repositories with external repositories.

4.2. Apache Maven

Apache Maven is a distributed build automation tool used in Java application development to build and manage software projects. You can use Maven to build, publish, and deploy your Red Hat Decision Manager projects. Maven provides the following benefits:

The build process is easy and a uniform build system is implemented across projects.
All of the required JAR files for a project are made available at compile time.
A proper project structure is configured.
Dependencies and versions are well managed.
There is no need for additional build processing because Maven builds output into a number of predefined types, such as JAR and WAR.

Maven uses repositories to store Java libraries, plug-ins, and other build artifacts. These repositories can be local or remote. Red Hat Decision Manager maintains local and remote maven repositories that you can add to your project for accessing the rules, processes, events, and other project dependencies. When building projects and archetypes, Maven dynamically retrieves Java libraries and Maven plug-ins from local or remote repositories. Doing this promotes sharing and reuse of dependencies across projects.

Chapter 5. Installation environment options for Red Hat Decision Manager

With Red Hat Decision Manager, you can set up a development environment to develop business applications, a runtime environment to run those applications to support decisions, or both.

Development environment: Typically consists of one Business Central installation and at least one KIE Server installation. You can use Business Central to design decisions and other artifacts, and you can use KIE Server to execute and test the artifacts that you created.
Runtime environment: Consists of one or more KIE Server instances with or without Business Central. Business Central has an embedded Decision Manager controller. If you install Business Central, use the Menu → Deploy → Execution servers page to create and maintain containers. If you want to automate KIE Server management without Business Central, you can use the headless Decision Manager controller.

You can also cluster both development and runtime environments. A clustered development or runtime environment consists of a unified group or cluster of two or more servers. The primary benefit of clustering Red Hat Decision Manager development environments is high availability and enhanced collaboration, while the primary benefit of clustering Red Hat Decision Manager runtime environments is high availability and load balancing. High availability decreases the chance of data loss when a single server fails. When a server fails, another server fills the gap by providing a copy of the data that was on the failed server. When the failed server comes online again, it resumes its place in the cluster.

Note

Clustering of the runtime environment is currently supported on Red Hat JBoss EAP 7.3 and Red Hat OpenShift Container Platform only.

Chapter 6. Red Hat Decision Manager roles and users

To access Business Central or KIE Server, you must create users and assign them appropriate roles before the servers are started. You can create users and roles when you install Business Central or KIE Server.

Business Central and KIE Server use the Java Authentication and Authorization Service (JAAS) login module to authenticate users. If both Business Central and KIE Server are running on a single instance, then they share the same JAAS subject and security domain. Therefore, a user who is authenticated for Business Central can also access KIE Server.

However, if Business Central and KIE Server are running on different instances, then the JAAS login module is triggered for both individually. Therefore, a user who is authenticated for Business Central must be authenticated separately to access KIE Server. For example, if a user who is authenticated on Business Central but not authenticated on KIE Server tries to view or manage process definitions in Business Central, a 401 error is logged in the log file and the Invalid credentials to load data from remote server. Contact your system administrator. message appears in Business Central.

This section describes Red Hat Decision Manager user roles.

Note

The admin, analyst, and rest-all roles are reserved for Business Central. The kie-server role is reserved for KIE Server. For this reason, the available roles can differ depending on whether Business Central, KIE Server, or both are installed.

admin: Users with the admin role are the Business Central administrators. They can manage users and create, clone, and manage repositories. They have full access to make required changes in the application. Users with the admin role have access to all areas within Red Hat Decision Manager.
analyst: Users with the analyst role have access to all high-level features. They can model projects. However, these users cannot add contributors to spaces or delete spaces in the Design → Projects view. Access to the Deploy → Execution Servers view, which is intended for administrators, is not available to users with the analyst role. However, the Deploy button is available to these users when they access the Library perspective.
rest-all: Users with the rest-all role can access Business Central REST capabilities.
kie-server: Users with the kie-server role can access KIE Server REST capabilities.

Chapter 7. Red Hat Decision Manager reference implementations

Red Hat Decision Manager provides reference implementations that you can use as starter applications. They are included in the Red Hat Decision Manager 7.10.0 Reference Implementations download, available on the Red Hat Decision Manager Software Downloads page in the Red Hat Customer Portal.

Employee Rostering reference implementation

The employee rostering reference implementation enables you to create an application that assigns employees to shifts on various positions in an organization. For example, you can use the application to distribute shifts in a hospital between nurses, guard duty shifts across a number of locations, or shifts on an assembly line between workers.

Vehicle route planning reference implementation

The vehicle route planning reference implementation enables you to create an application that solves a vehicle route planning problem with real-world maps, roads, and vehicles delivering goods to locations, each with a specific capacity. For more information, see the README file in the vehicle routing ZIP file, included in the reference implementation download.

School timetable reference implementation

The school timetable reference implementation enables you to build a REST application on Spring Boot that associates lessons with rooms and time slots and avoids conflicts by considering student and teacher constraints.

High available event-driven decisioning reference implementation

The high available event-driven decisioning reference implementation enables you to deploy Drools engine code that requires stateful processing, including rules developed with complex event processing, in an OpenShift environment. Doing this enables the decision engine to process complex event series with high availability.

Chapter 8. Integrating with Red Hat Decision Manager

You can integrate Red Hat Decision Manager with other products and components, such as Spring Boot, Red Hat Fuse, and Red Hat Single Sign-On.

8.1. Red Hat Decision Manager Spring Boot business applications

Spring Framework is a Java platform that provides comprehensive infrastructure support for developing Java applications. Spring Boot is a lightweight framework based on Spring Boot starters. Spring Boot starters are pom.xml files that contain a set of dependency descriptors that you can include in your Spring Boot project. Red Hat offers support and maintenance for Red Hat Decision Manager Spring Boot projects as part of Red Hat Runtimes.

Red Hat Decision Manager Spring Boot business applications are flexible, UI-agnostic logical groupings of individual services that provide certain business capabilities. Business applications are based on Spring Boot starters. They are usually deployed separately and can be versioned individually. A complete business application enables a domain to achieve specific business goals, for example order management or accommodation management.

On the business application website you can create a Process Automation Manager, Decision Manager, or Business Optimizer business application. After you create and configure your business application, you can deploy it to an existing service or to the cloud, through OpenShift.

8.2. Integrating Red Hat Fuse

Fuse is a distributed, cloud-native integration platform that is part of an agile integration solution. Its distributed approach enables teams to deploy integrated services where required.

You can install Red Hat Fuse on the Apache Karaf container platform or Red Hat JBoss Enterprise Application Platform and then install and configure Red Hat Decision Manager in that container.

8.3. Integrating Red Hat Single Sign-On

Red Hat Single Sign-On (RH-SSO) is a single sign-on solution that you can use to secure your browser applications with your REST web services and Git access.

When you integrate Red Hat Decision Manager with RH-SSO, you create an SSO and identity management (IDM) environment for Red Hat Decision Manager. The session management feature of RH-SSO enables you to use a single authentication for different Red Hat Decision Manager environments on the internet.

RH-SSO 7.3 is supported with Red Hat Decision Manager on Red Hat JBoss EAP 7.3.

Chapter 9. Additional resources

Installation

Integration

Reference Implementations

OpenShift

Part II. Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.3

This document describes how to install Red Hat Decision Manager on a Red Hat JBoss Enterprise Application Platform 7.3 instance.

Prerequisites

You have reviewed the information in Planning a Red Hat Decision Manager installation.
You have installed the latest patch release of Red Hat JBoss Enterprise Application Platform 7.3. For information about installing Red Hat JBoss EAP, see the Red Hat JBoss Enterprise Application Platform installaton guide.

Chapter 10. About Red Hat Decision Manager

Red Hat Decision Manager is an open source decision management platform that combines business rules management, complex event processing, Decision Model & Notation (DMN) execution, and Business Optimizer for solving planning problems. It automates business decisions and makes that logic available to the entire business.

Business assets such as rules, decision tables, and DMN models are organized in projects and stored in the Business Central repository. This ensures consistency, transparency, and the ability to audit across the business. Business users can modify business logic without requiring assistance from IT personnel.

Red Hat Process Automation Manager is made up of Business Central and KIE Server.

KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. KIE Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store).
Business Central is the graphical user interface where you create and manage business rules that KIE Server executes.

Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without needing to deploy it to an application server.

Red Hat JBoss Enterprise Application Platform (Red Hat JBoss EAP) 7.3 is a certified implementation of the Java Enterprise Edition 8 (Java EE 8) full and web profile specifications. Red Hat JBoss EAP provides preconfigured options for features such as high availability, clustering, messaging, and distributed caching. It also enables users to write, deploy, and run applications using the various APIs and services that Red Hat JBoss EAP provides.

The instructions in this document explain how to install Red Hat Decision Manager in a Red Hat JBoss EAP 7.3 server instance.

For instructions on how to install Red Hat Decision Manager in other environments, see the following documents:

For information about supported components, see the following documents:

Chapter 11. Red Hat Decision Manager roles and users

This section describes Red Hat Decision Manager user roles.

Note

admin: Users with the admin role are the Business Central administrators. They can manage users and create, clone, and manage repositories. They have full access to make required changes in the application. Users with the admin role have access to all areas within Red Hat Decision Manager.
analyst: Users with the analyst role have access to all high-level features. They can model projects. However, these users cannot add contributors to spaces or delete spaces in the Design → Projects view. Access to the Deploy → Execution Servers view, which is intended for administrators, is not available to users with the analyst role. However, the Deploy button is available to these users when they access the Library perspective.
rest-all: Users with the rest-all role can access Business Central REST capabilities.
kie-server: Users with the kie-server role can access KIE Server REST capabilities.

Chapter 12. Downloading the Red Hat Decision Manager installation files

You can use the installer JAR file or deployable ZIP files to install Red Hat Decision Manager. You can run the installer in interactive or command line interface (CLI) mode. Alternatively, you can extract and configure the Business Central and KIE Server deployable ZIP files. If you want to run Business Central without deploying it to an application server, download the Business Central Standalone JAR file.

Download a Red Hat Decision Manager distribution that meets your environment and installation requirements.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download one of the following product distributions, depending on your preferred installation method:
Note
You only need to download one of these distributions.
- If you want to use the installer to install Red Hat Decision Manager on Red Hat JBoss EAP 7.3, download Red Hat Decision Manager 7.10.0 Installer (rhdm-installer-7.10.0.jar). The installer graphical user interface guides you through the installation process.
- If you want to install Red Hat Decision Manager on Red Hat JBoss EAP 7.3 using the deployable ZIP files, download the following files:
  - Red Hat Decision Manager 7.10.0 KIE Server for All Supported EE8 Containers (rhdm-7.10.0-kie-server-ee8.zip)
  - Red Hat Decision Manager 7.10.0 KIE Server Deployable for EAP 7 (rhdm-7.10.0-decision-central-eap7-deployable.zip)
- To run Business Central without needing to deploy it to an application server, download Red Hat Decision Manager 7.10.0 Business Central Standalone (rhdm-7.10.0-decision-central-standalone.jar).

Chapter 13. Using the Red Hat Decision Manager installer

This section describes how to install Business Central and the KIE Server using the installer JAR file. The JAR file is an executable file that installs Red Hat Decision Manager in an existing Red Hat JBoss EAP 7.3 server installation. You can run the installer in interactive or command line interface (CLI) mode.

Note

The Red Hat Decision Manager JAR file installer does not support the Red Hat JBoss EAP distribution installed by yum or RPM Package Manager. If you want to install Red Hat Decision Manager in this type of Red Hat JBoss EAP installation, download the Red Hat Decision Manager 7.10 Deployable for Red Hat JBoss EAP 7.3 file and follow the steps in Chapter 14, Installing Red Hat Decision Manager from ZIP files.

Note

Because IBM JDK cannot use keystores generated on other JDKs, you cannot install Red Hat Decision Manager into an existing Red Hat JBoss EAP installation running on IBM JDK with a keystore generated on another JDK.

Next steps:

Follow the instructions in one of the following sections:

Section 13.1, “Using the installer in interactive mode”
Section 13.2, “Using the installer in CLI mode”

13.1. Using the installer in interactive mode

The installer for Red Hat Decision Manager is an executable JAR file. You can use it to install Red Hat Decision Manager in an existing Red Hat JBoss EAP 7.3 server installation.

Note

For security reasons, you should run the installer as a non-root user.

Prerequisites

The Red Hat Decision Manager 7.10.0 Installer has been downloaded. For instructions, see Chapter 12, Downloading the Red Hat Decision Manager installation files.
A supported JDK is installed. For a list of supported JDKs, see Red Hat Decision Manager 7 Supported Configurations.
A backed-up Red Hat JBoss EAP 7.3 server installation is available.
Sufficient user permissions to complete the installation are granted.
The JAR binary is included in $PATH environment variable. On Red Hat Enterprise Linux, it is included in the java-$JAVA_VERSION-openjdk-devel package.
Note
Red Hat Decision Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix A, Business Central system properties.

Procedure

In a terminal window, navigate to the directory where you downloaded the installer JAR file and enter the following command:
```
java -jar rhdm-installer-7.10.0.jar
```
Note
When running the installer on Windows, you may be prompted to provide administrator credentials during the installation. To prevent this requirement, add the izpack.mode=privileged option to the installation command:
```
java -Dizpack.mode=privileged -jar
rhdm-installer-7.10.0.jar
```
Furthermore, when running the installer on a 32-bit Java virtual machine, you might encounter memory limitations. To prevent this issue, run this command:
```
java -XX:MaxHeapSize=4g -jar
rhdm-installer-7.10.0.jar
```
The graphical installer displays a splash screen and a license agreement page.
Click I accept the terms of this license agreement and click Next.
Specify the Red Hat JBoss EAP 7.3 server home where you want to install Red Hat Decision Manager and click Next.
Select the components that you want to install and click Next.
Note
You can install Business Central and KIE Server on the same server. However, you should install Business Central and KIE Server on different servers in production environments. To do this, run the installer twice.
Create a user and click Next. By default, if you install both Business Central and KIE Server in the same container the new user is given the admin, kie-server, and rest-all roles. If you install only KIE Server, the user is given the kie-server role. To select another role, deselect admin. For information about roles, see Chapter 11, Red Hat Decision Manager roles and users.
Note
Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).
Make a note of the user name and password. You will need them to access Business Central and KIE Server.
On the Installation Overview page, review the components that you will install and click Next to start the installation.
When the installation has completed, click Next.
When Processing finished appears at the top of the screen, click Next to complete the installation.
Optional: Click Generate Installation Script and Properties File to save the installation data in XML files, and then click Done.
The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file to repeat the Red Hat Decision Manager installation on multiple systems with the same type of server and the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command:
```
java -jar rhdm-installer-7.10.0.jar <path-to-auto.xml-file>
```

You have successfully installed Red Hat Decision Manager using the installer.

13.2. Using the installer in CLI mode

You can use the command-line interface (CLI) to run the Red Hat Decision Manager installer.

Note

For security reasons, you should run the installer as a non-root user.

Prerequisites

The Red Hat Decision Manager 7.10.0 Installer has been downloaded. For instructions, see Chapter 12, Downloading the Red Hat Decision Manager installation files.
A supported JDK is installed. For a list of supported JDKs, see Red Hat Decision Manager 7 Supported Configurations.
A backed-up Red Hat JBoss EAP 7.3 server installation is available.
Sufficient user permissions to complete the installation are granted.
The JAR binary is included in the $PATH environment variable. On Red Hat Enterprise Linux, it is included in the java-$JAVA_VERSION-openjdk-devel package.
Note
Red Hat Decision Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix A, Business Central system properties.

Procedure

In a terminal window, navigate to the directory where you downloaded the installer file and enter the following command:
```
java -jar rhdm-installer-7.10.0.jar -console
```
The command-line interactive process will start and display the End-User License Agreement.
```
press 1 to continue, 2 to quit, 3 to redisplay.
```

Read the license agreement, enter 1, and press Enter to continue:

Specify the home directory of one of the following servers:  Red Hat JBoss EAP 7 or Red Hat JBoss Web Server 5. For more information, see https://access.redhat.com/articles/3354301[Red Hat Decision Manager 7 Supported Configurations].

Enter the parent directory of an existing Red Hat JBoss EAP 7.3 installation.
The installer will verify the location of the installation at the location provided. Enter 1 to confirm and continue.
Note
You can install Business Central and KIE Server on the same server. However, you should install Business Central and KIE Server on different servers in production environments.
Follow the instructions in the installer to complete the installation.
Note
When you create the user name and password, make sure that the specified user name does not conflict with any known title of a role or a group. For example, if there is a role called admin, you should not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character (not including the character &).
Make a note of the user name and password. You will need them to access Business Central and KIE Server.

When the installation has completed, you will see this message:

Would you like to generate an automatic installation script and properties file?

Enter y to create XML files that contain the installation data, or n to complete the installation. If you enter y, you are prompted to specify a path for the XML files.
Enter a path or press the Enter key to accept the suggested path.
The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file on multiple systems to easily repeat a Red Hat Decision Manager installation on the same type of server with the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command:
```
java -jar rhdm-installer-7.10.0.jar <path-to-auto.xml-file>
```
If you installed only Business Central, repeat these steps to install KIE Server on a separate server.

Chapter 14. Installing Red Hat Decision Manager from ZIP files

You can use the Red Hat Decision Manager ZIP files (one for Business Central and one for KIE Server) to install Red Hat Decision Manager without using the installer.

Note

You should install Business Central and the KIE Server on different servers in production environments.

For information about installing the headless Decision Manager controller, see Chapter 19, Installing and running the headless Decision Manager controller.

14.1. Installing Business Central from the ZIP file

Business Central is the graphical user interface where you create and manage business rules that KIE Server executes. You can use a deployable ZIP file to install and configure Business Central.

Prerequisites

A backed-up Red Hat JBoss EAP installation version 7.3 is available. The base directory of the Red Hat JBoss EAP installation is referred to as EAP_HOME.
Sufficient user permissions to complete the installation are granted.
The following file is downloaded as described in Chapter 12, Downloading the Red Hat Decision Manager installation files:
rhdm-7.10.0-decision-central-eap7-deployable.zip

Procedure

Extract the rhdm-7.10.0-decision-central-eap7-deployable.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-decision-central-eap7-deployable/jboss-eap-7.3 directory to EAP_HOME. When prompted, merge or replace files.
Warning
Ensure that the names of the Red Hat Decision Manager deployments that you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.

14.2. Installing KIE Server from the ZIP file

KIE Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store). You can use a deployable ZIP file to install and configure KIE Server.

Prerequisites

A backed-up Red Hat JBoss EAP installation version 7.3 is available. The base directory of the Red Hat JBoss EAP installation is referred to as EAP_HOME.
Sufficient user permissions to complete the installation are granted.
The following file is downloaded as described in Chapter 12, Downloading the Red Hat Decision Manager installation files:
rhdm-7.10.0-kie-server-ee8.zip

Procedure

Extract the rhdm-7.10.0-kie-server-ee8.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the TEMP_DIR/rhdm-7.10.0-kie-server-ee8/kie-server.war directory to EAP_HOME/standalone/deployments/.
Warning
Ensure the names of the Red Hat Decision Manager deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-kie-server-ee8/rhdm-7.10.0-kie-server-ee8/SecurityPolicy/ to EAP_HOME/bin.
When prompted to overwrite files, click Replace.
In the EAP_HOME/standalone/deployments/ directory, create an empty file named kie-server.war.dodeploy. This file ensures that KIE Server is automatically deployed when the server starts.

14.3. Creating users

If you used the deployable ZIP files to install Red Hat Decision Manager, before you can log in to Business Central or KIE Server, you must create users. This section shows you how to create a Business Central user with the admin, rest-all, and kie-server roles and a KIE Server user that has the kie-server role. For information about roles, see Chapter 11, Red Hat Decision Manager roles and users.

Note

If you used the installer to install Red Hat Decision Manager, you created at least one user during that process. The EAP_HOME/standalone/configuration/application-users.properties file contains application users and their passwords.

Prerequisites

Red Hat Decision Manager is installed in the base directory of the Red Hat JBoss EAP installation (EAP_HOME).

Procedure

In a terminal application, navigate to the EAP_HOME/bin directory.
Create a user with the admin, rest-all, and kie-server roles.
Note
Users with the admin role are Business Central administrators. Users with rest-all role can access Business Central REST capabilities. Users with the kie-server role can access KIE Server (KIE Server) REST capabilities.
In the following command, replace <USERNAME> and <PASSWORD> with the user name and password of your choice:
```
$ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role admin,rest-all,kie-server
```
Note
Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).
Create a user with the kie-server role that you will use to log in to KIE Server.
```
$ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role kie-server
```
Make a note of your user names and passwords.
Note
If you installed Business Central and KIE Server in the same server instance, you can create a single user that has both of these roles:
```
$ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role admin,rest-all,kie-server
```
You should install Business Central and KIE Server on different servers in production environments.

14.4. Configuring KIE Server to connect to Business Central

Warning

This section provides a sample setup that you can use for testing purposes. Some of the values are unsuitable for a production environment, and are marked as such.

If a KIE Server is not configured in your Red Hat Decision Manager environment, or if you require additional KIE Servers in your Red Hat Decision Manager environment, you must configure a KIE Server to connect to Business Central.

Note

If you are deploying KIE Server on Red Hat OpenShift Container Platform, see the Deploying a Red Hat Decision Manager environment on Red Hat OpenShift Container Platform using Operators document for instructions about configuring it to connect to Business Central.

Prerequisites

Business Central and KIE Server are installed in the base directory of the Red Hat JBoss EAP installation (EAP_HOME) as described in the following sections:
- Section 14.1, “Installing Business Central from the ZIP file”
- Section 14.2, “Installing KIE Server from the ZIP file”
Users with the following roles exist:
- In Business Central, a user with the role rest-all
- On the KIE Server, a user with the role kie-server
  For more information, see Section 14.3, “Creating users”.

Procedure

In your Red Hat Decision Manager installation directory, navigate to the standalone-full.xml file. For example, if you use a Red Hat JBoss EAP installation for Red Hat Decision Manager, go to $EAP_HOME/standalone/configuration/standalone-full.xml.

Open the standalone-full.xml file and under the <system-properties> tag, set the following JVM properties:

Table 14.1. JVM Properties for the managed KIE Server instance
Property	Value	Note
`org.kie.server.id`	`default-kie-server`	The KIE Server ID.
`org.kie.server.controller`	`http://localhost:8080/decision-central/rest/controller`	The location of Business Central. The URL for connecting to the API of Business Central.
`org.kie.server.controller.user`	`controllerUser`	The user name with the role `rest-all` who can log in to the Business Central.
`org.kie.server.controller.pwd`	`controllerUser1234;`	The password of the user who can log in to the Business Central.
`org.kie.server.location`	`http://localhost:8080/kie-server/services/rest/server`	The location of the KIE Server. The URL for connecting to the API of KIE Server.

Table 14.2. JVM Properties for the Business Central instance
Property	Value	Note
`org.kie.server.user`	`controllerUser`	The user name with the role `kie-server`.
`org.kie.server.pwd`	`controllerUser1234;`	The password of the user.

The following example shows how to configure a KIE Server instance:

<property name="org.kie.server.id" value="default-kie-server"/>
<property name="org.kie.server.controller" value="http://localhost:8080/decision-central/rest/controller"/>
<property name="org.kie.server.controller.user" value="controllerUser"/>
<property name="org.kie.server.controller.pwd" value="controllerUser1234;"/>
<property name="org.kie.server.location" value="http://localhost:8080/kie-server/services/rest/server"/>

The following example shows how to configure a for Business Central instance:

<property name="org.kie.server.user" value="controllerUser"/>
<property name="org.kie.server.pwd" value="controllerUser1234;"/>

Send a GET request to http://SERVER:PORT/kie-server/services/rest/server/ to verify that KIE Server started successfully. After authentication, you receive an XML response similar to the following example:

<response type="SUCCESS" msg="Kie Server info">
    <kie-server-info>
        <capabilities>KieServer</capabilities>
        <capabilities>BRM</capabilities>
        <capabilities>BPM</capabilities>
        <capabilities>CaseMgmt</capabilities>
        <capabilities>BPM-UI</capabilities>
        <capabilities>BRP</capabilities>
        <capabilities>DMN</capabilities>
        <capabilities>Swagger</capabilities>
        <location>http://localhost:8230/kie-server/services/rest/server</location>
        <messages>
            <content>Server KieServerInfo{serverId='first-kie-server', version='7.5.1.Final-redhat-1', location='http://localhost:8230/kie-server/services/rest/server', capabilities=[KieServer, BRM, BPM, CaseMgmt, BPM-UI, BRP, DMN, Swagger]}started successfully at Mon Feb 05 15:44:35 AEST 2018</content>
            <severity>INFO</severity>
            <timestamp>2018-02-05T15:44:35.355+10:00</timestamp>
        </messages>
        <name>first-kie-server</name>
        <id>first-kie-server</id>
        <version>7.5.1.Final-redhat-1</version>
    </kie-server-info>
</response>

Verify successful registration:
1. Log in to Business Central.
2. Click Menu → Deploy → Execution Servers.
  If registration is successful, you will see the registered server ID.

Chapter 15. Securing passwords with a keystore

You can use a keystore to encrypt passwords that are used for communication between Business Central and KIE Server. You should encrypt both controller and KIE Server passwords. If Business Central and KIE Server are deployed to different application servers, then both application servers should use the keystore.

Use Java Cryptography Extension KeyStore (JCEKS) for your keystore because it supports symmetric keys. Use KeyTool, which is part of the JDK installation, to create a new JCEKS.

Note

If KIE Server is not configured with JCEKS, KIE Server passwords are stored in system properties in plain text form.

Prerequisites

KIE Server is installed in Red Hat JBoss EAP.
Java 8 or higher is installed.

Procedure

In the Red Hat JBoss EAP home directory, enter the following command to create a KIE Server user with the kie-server role and specify a password. In the following example, replace <USER_NAME> and <PASSWORD> with the user name and password of your choice.
```
$<EAP_HOME>/bin/add-user.sh -a -e -u <USER_NAME> -p <PASSWORD> -g kie-server
```
To use KeyTool to create a JCEKS, enter the following command in the Java 8 home directory:
```
$<JAVA_HOME>/bin/keytool -importpassword -keystore <KEYSTORE_PATH> -keypass <ALIAS_KEY_PASSWORD> -alias <PASSWORD_ALIAS> -storepass <KEYSTORE_PASSWORD> -storetype JCEKS
```
In this example, replace the following variables:
- <KEYSTORE_PATH>: The path where the keystore will be stored
- <KEYSTORE_PASSWORD>: The keystore password
- <ALIAS_KEY_PASSWORD>: The password used to access values stored with the alias
- <PASSWORD_ALIAS>: The alias of the entry to the process
When prompted, enter the password for the KIE Server user that you created.

Set the following system properties in the EAP_HOME/standalone/configuration/standalone-full.xml file and replace the placeholders as listed in the following table:

    <system-properties>
        <property name="kie.keystore.keyStoreURL" value="<KEYSTORE_URL>"/>
        <property name="kie.keystore.keyStorePwd" value="<KEYSTORE_PWD>"/>
        <property name="kie.keystore.key.server.alias" value="<KEY_SERVER_ALIAS>"/>
        <property name="kie.keystore.key.server.pwd" value="<KEY_SERVER_PWD>"/>
        <property name="kie.keystore.key.ctrl.alias" value="<KEY_CONTROL_ALIAS>"/>
        <property name="kie.keystore.key.ctrl.pwd" value="<KEY_CONTROL_PWD>"/>
    </system-properties>

Table 15.1. System properties used to load a KIE Server JCEKS
System property	Placeholder	Description
`kie.keystore.keyStoreURL`	`<KEYSTORE_URL>`	URL for the JCEKS that you want to use, for example `file:///home/kie/keystores/keystore.jceks`
`kie.keystore.keyStorePwd`	`<KEYSTORE_PWD>`	Password for the JCEKS
`kie.keystore.key.server.alias`	`<KEY_SERVER_ALIAS>`	Alias of the key for REST services where the password is stored
`kie.keystore.key.server.pwd`	`<KEY_SERVER_PWD>`	Password of the alias for REST services with the stored password
`kie.keystore.key.ctrl.alias`	`<KEY_CONTROL_ALIAS>`	Alias of the key for default REST Process Automation Controller where the password is stored
`kie.keystore.key.ctrl.pwd`	`<KEY_CONTROL_PWD>`	Password of the alias for default REST Process Automation Controller with the stored password

Start KIE Server to verify the configuration.

Chapter 16. Configuring SSH to use RSA

SSH is used to clone Git repositories. By default, the DSA encryption algorithm is provided by Business Central. However, some SSH clients, for example SSH clients in the Fedora 23 environment, use the RSA algorithm instead of the DSA algorithm. Business Central contains a system property that you can use to switch from DSA to RSA if required.

Note

SSH clients on supported configurations, for example Red Hat Enterprise Linux 7, are not affected by this issue. For a list of supported configurations, see Red Hat Decision Manager 7 Supported Configurations.

Procedure

Complete one of the following tasks to enable this system property:

Modify the ~/.ssh/config file on the client side as follows to force the SSH client to accept the deprecated DSA algorithm:
```
Host <SERVER_IP>
       HostKeyAlgorithms +ssh-dss
```
Include the -Dorg.uberfire.nio.git.ssh.algorithm=RSA parameter when you start Business Central, for example:
```
$ ./standalone.sh -c standalone-full.xml
-Dorg.uberfire.nio.git.ssh.algorithm=RSA
```

Chapter 17. Verifying the Red Hat Decision Manager installation

After you have installed Red Hat Decision Manager, create an asset to verify that the installation is working.

Procedure

In a terminal window, navigate to the EAP_HOME/bin directory and enter the following command to start Red Hat Decision Manager:
```
./standalone.sh -c standalone-full.xml
```
Note
If you deployed Business Central without KIE Server, you can start Business Central with the standalone.sh script without specifying the standalone-full.xml file. In this case, ensure that you make any configuration changes to the standalone.xml file before starting Business Central.
In a web browser, enter localhost:8080/decision-central.
- If you configured Red Hat Decision Manager to run from a domain name, replace localhost with the domain name, for example:
  http://www.example.com:8080/decision-central
- If you configured Red Hat Decision Manager to run in a cluster, replace localhost with the IP address of a particular node, for example:
  http://<node_IP_address>:8080/decision-central
Enter the admin user credentials that you created during installation. The Business Central home page appears.
Select Menu → Deploy → Execution Servers.
Confirm that default-kieserver is listed under Server Configurations.
Select Menu → Design → Projects.
Open the MySpace space.
Click Try Samples → Mortgages → OK. The Assets window appears.
Click Add Asset → Data Object.
Enter MyDataObject in the Data Object field and click OK.
Click Spaces → MySpace → Mortgages and confirm that MyDataObject is in the list of assets.
Delete the Mortgages project.

Chapter 18. Running Red Hat Decision Manager

Use this procedure to run the Red Hat Decision Manager on Red Hat JBoss EAP in standalone mode.

Prerequisites

Red Hat Decision Manager is installed and configured.

Note

If you changed the default host (localhost) or the default port (9990), then before you run Red Hat Decision Manager, you must edit the business-central.war/WEB-INF/classes/datasource-management.properties and business-central.war/WEB-INF/classes/security-management.properties files as described in Solution 3519551.

Procedure

In a terminal application, navigate to EAP_HOME/bin.
Run the standalone configuration:
- On Linux or UNIX-based systems:
```
$ ./standalone.sh -c standalone-full.xml
```
- On Windows:
```
standalone.bat -c standalone-full.xml
```
  Note
  If you deployed Business Central without KIE Server, you can start Business Central with the standalone.sh script without specifying the standalone-full.xml file. In this case, ensure that you make any configuration changes to the standalone.xml file before starting Business Central.
  On Linux or UNIX-based systems:
  $ ./standalone.sh
  On Windows:
  standalone.bat
In a web browser, open the URL localhost:8080/decision-central.
If you configured Red Hat Decision Manager to run from a domain name, replace localhost with the domain name, for example:
http://www.example.com:8080/decision-central
Log in using the credentials of the user that you created for Business Central in Section 14.3, “Creating users”.

Chapter 19. Installing and running the headless Decision Manager controller

You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). If KIE Server is managed, the Decision Manager controller manages the KIE Server configuration and you interact with the Decision Manager controller to create and maintain KIE containers.

Business Central has an embedded Decision Manager controller. If you install Business Central, use the Execution Server page to create and maintain KIE containers. If you want to automate KIE Server management without Business Central, you can use the headless Decision Manager controller.

19.1. Installing the headless Decision Manager controller

You can install the headless Decision Manager controller and use the REST API or the KIE Server Java Client API to interact with it.

Prerequisites

A backed-up Red Hat JBoss EAP installation version 7.3 is available. The base directory of the Red Hat JBoss EAP installation is referred to as EAP_HOME.
Sufficient user permissions to complete the installation are granted.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 Add Ons (the rhdm-7.10.0-add-ons.zip file).
Extract the rhdm-7.10.0-add-ons.zip file. The rhdm-7.10.0-controller-ee7.zip file is in the extracted directory.
Extract the rhdm-7.10.0-controller-ee7 archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the TEMP_DIR/rhdm-7.10.0-controller-ee7/controller.war directory to EAP_HOME/standalone/deployments/.
Warning
Ensure that the names of the headless Decision Manager controller deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-controller-ee7/SecurityPolicy/ directory to EAP_HOME/bin.
When prompted to overwrite files, select Yes.
In the EAP_HOME/standalone/deployments/ directory, create an empty file named controller.war.dodeploy. This file ensures that the headless Decision Manager controller is automatically deployed when the server starts.

19.1.1. Creating a headless Decision Manager controller user

Before you can use the headless Decision Manager controller, you must create a user that has the kie-server role.

Prerequisites

The headless Decision Manager controller is installed in the base directory of the Red Hat JBoss EAP installation (EAP_HOME).

Procedure

In a terminal application, navigate to the EAP_HOME/bin directory.
Enter the following command and replace <USER_NAME> and <PASSWORD> with the user name and password of your choice.
```
$ ./add-user.sh -a --user <username> --password <password> --role kie-server
```
Note
Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).
Make a note of your user name and password.

19.1.2. Configuring KIE Server and the headless Decision Manager controller

If KIE Server will be managed by the headless Decision Manager controller, you must edit the standalone-full.xml file in KIE Server installation and the standalone.xml file in the headless Decision Manager controller installation.

Prerequisites

KIE Server is installed in an EAP_HOME.
The headless Decision Manager controller is installed in an EAP_HOME.
Note
You should install KIE Server and the headless Decision Manager controller on different servers in production environments. However, if you install KIE Server and the headless Decision Manager controller on the same server, for example in a development environment, make these changes in the shared standalone-full.xml file.
On KIE Server nodes, a user with the kie-server role exists.
On the server nodes, a user with the kie-server role exists.
For more information, see Section 14.3, “Creating users”.

Procedure

In the EAP_HOME/standalone/configuration/standalone-full.xml file, add the following properties to the <system-properties> section and replace <USERNAME> and <USER_PWD> with the credentials of a user with the kie-server role:
```
   <property name="org.kie.server.user" value="<USERNAME>"/>
   <property name="org.kie.server.pwd" value="<USER_PWD>"/>
```

In the KIE Server EAP_HOME/standalone/configuration/standalone-full.xml file, add the following properties to the <system-properties> section:

  <property name="org.kie.server.controller.user" value="<CONTROLLER_USER>"/>
  <property name="org.kie.server.controller.pwd" value="<CONTROLLER_PWD>"/>
  <property name="org.kie.server.id" value="<KIE_SERVER_ID>"/>
  <property name="org.kie.server.location" value="http://<HOST>:<PORT>/kie-server/services/rest/server"/>
  <property name="org.kie.server.controller" value="<CONTROLLER_URL>"/>

In this file, replace the following values:
- Replace <CONTROLLER_USER> and <CONTROLLER_PWD> with the credentials of a user with the kie-server role.
- Replace <KIE_SERVER_ID> with the ID or name of the KIE Server installation, for example, rhdm-7.10.0-kie-server-1.
- Replace <HOST> with the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.
- Replace <PORT> with the port of the KIE Server host, for example, 8080.
  Note
  The org.kie.server.location property specifies the location of KIE Server.
- Replace <CONTROLLER_URL> with the URL of the headless Decision Manager controller. KIE Server connects to this URL during startup.

19.2. Running the headless Decision Manager controller

After you have installed the headless Decision Manager controller on Red Hat JBoss EAP, use this procedure to run the headless Decision Manager controller.

Prerequisites

The headless Decision Manager controller is installed and configured in the base directory of the Red Hat JBoss EAP installation (EAP_HOME).

Procedure

In a terminal application, navigate to EAP_HOME/bin.
If you installed the headless Decision Manager controller on the same Red Hat JBoss EAP instance as the Red Hat JBoss EAP instance where you installed the KIE Server, enter one of the following commands:
- On Linux or UNIX-based systems:
```
$ ./standalone.sh -c standalone-full.xml
```
- On Windows:
```
standalone.bat -c standalone-full.xml
```
If you installed the headless Decision Manager controller on a separate Red Hat JBoss EAP instance from the Red Hat JBoss EAP instance where you installed the KIE Server, start the headless Decision Manager controller with the standalone.sh script:
Note
In this case, ensure that you made all required configuration changes to the standalone.xml file.
- On Linux or UNIX-based systems:
```
$ ./standalone.sh
```
- On Windows:
```
standalone.bat
```
To verify that the headless Decision Manager controller is working on Red Hat JBoss EAP, enter the following command where <CONTROLLER> and <CONTROLLER_PWD> is the user name and password combination that you created in Section 19.1.1, “Creating a headless Decision Manager controller user”. The output of this command provides information about the KIE Server instance.
```
curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H  "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'
```

Note

Alternatively, you can use the KIE Server Java API Client to access the headless Decision Manager controller.

Chapter 20. Configuring and running standalone Business Central

You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server. You can use sample configuration files to run the Business Central standalone JAR file out of the box or you can customize the sampfiles for your requirements.

Note

This JAR file is supported only when it is run on Red Hat Enterprise Linux.

Prerequisites

The Red Hat Decision Manager 7.10.0 Business Central Standalone (rhdm-7.10.0-decision-central-standalone.jar) and the Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) files have been downloaded from the Software Downloads page for Red Hat Decision Manager 7.10, as described in Chapter 12, Downloading the Red Hat Decision Manager installation files.

Procedure

Extract the downloaded rhdm-7.10.0-addons.zip to a temporary directory. This archive includes the rhdm-7.10.0-standalone-sample-configuration.zip file.
Extract the rhdm-7.10.0-standalone-sample-configuration.zip file to the directory that contains the rhdm-7.10.0-decision-central-standalone.jar file. The rhdm-7.10.0-standalone-sample-configuration.zip file contains the following sample configuration files:
- application-roles.properties
- application-users.properties
- sample-standalone-config.yml
  You can run the rhdm-7.10.0-decision-central-standalone.jar files with the sample data provided in the configuration files or you can customize the data for your requirements.
To customize the configuration data, complete the following steps:
1. Edit the application-users.properties file. Include an administrative user and if this Business Central instance will be a Decision Manager controller for KIE Server, include a Decision Manager controller user, for example:
```
rhdmAdmin=password1
```
2. Edit the application-roles.properties file to assign roles to the users that you included in the application-users.properties file, for example:
```
rhdmAdmin=admin
controllerUser=kie-server
```
  For more information, see Chapter 11, Red Hat Decision Manager roles and users.
3. Review the contents of the the sample-standalone-config.yml configuration file and update as required.

To run the Business Central standalone JAR file, enter the following command:

java -jar rhdm-7.10.0-decision-central-standalone.jar -s sample-standalone-config.yml

To set application properties when you run the JAR file, include the -D<PROPERTY>=<VALUE> parameter in the command, where <PROPERTY> is the name of a supported application property and <VALUE> is the property value:
```
java -jar rhdm-7.10.0-decision-central-standalone.jar -s sample-standalone-config.yml -D<PROPERTY>=<VALUE> -D<PROPERTY>=<VALUE>
```
For example, to run Business Central and connect to KIE Server as the user controllerUser, enter:
```
java -jar {PRODUCT_FILE}-{URL_COMPONENT_CENTRAL}-standalone.jar \
-s sample-standalone-config.yml \
-Dorg.kie.server.user=controllerUser
-Dorg.kie.server.pwd=controllerUser1234
```
Doing this enables you to deploy containers to KIE Server. See Appendix A, Business Central system properties for more information.

Chapter 21. Maven settings and repositories for Red Hat Decision Manager

When you create a Red Hat Decision Manager project, Business Central uses the Maven repositories that are configured for Business Central. You can use the Maven global or user settings to direct all Red Hat Decision Manager projects to retrieve dependencies from the public Red Hat Decision Manager repository by modifying the Maven project object model (POM) file (pom.xml). You can also configure Business Central and KIE Server to use an external Maven repository or prepare a Maven mirror for offline use.

For more information about Red Hat Decision Manager packaging and deployment options, see Packaging and deploying a Red Hat Decision Manager project.

21.1. Adding Maven dependencies for Red Hat Decision Manager

To use the correct Maven dependencies in your Red Hat Decision Manager project, add the Red Hat Business Automation bill of materials (BOM) files to the project’s pom.xml file. The Red Hat Business Automation BOM applies to both Red Hat Decision Manager and Red Hat Process Automation Manager. When you add the BOM files, the correct versions of transitive dependencies from the provided Maven repositories are included in the project.

For more information about the Red Hat Business Automation BOM, see What is the mapping between Red Hat Decision Manager and the Maven library version?.

Procedure

Declare the Red Hat Business Automation BOM in the pom.xml file:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>com.redhat.ba</groupId>
   <artifactId>ba-platform-bom</artifactId>
   <version>7.10.0.redhat-00004</version>
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>
<dependencies>
<!-- Your dependencies -->
</dependencies>

Declare dependencies required for your project in the <dependencies> tag. After you import the product BOM into your project, the versions of the user-facing product dependencies are defined so you do not need to specify the <version> sub-element of these <dependency> elements. However, you must use the <dependency> element to declare dependencies which you want to use in your project.

For standalone projects that are not authored in Business Central, specify all dependencies required for your projects. In projects that you author in Business Central, the basic decision engine dependencies are provided automatically by Business Central.

For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:

For a basic Red Hat Decision Manager project, declare the following dependencies:

Embedded decision engine dependencies

<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-compiler</artifactId>
</dependency>

<!-- Dependency for persistence support. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-persistence-jpa</artifactId>
</dependency>

<!-- Dependencies for decision tables, templates, and scorecards.
For other assets, declare org.drools:business-central-models-* dependencies. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-decisiontables</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-templates</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-scorecards</artifactId>
</dependency>

<!-- Dependency for loading KJARs from a Maven repository using KieScanner. -->
<dependency>
  <groupId>org.kie</groupId>
  <artifactId>kie-ci</artifactId>
</dependency>

To use the KIE Server, declare the following dependencies:

Client application KIE Server dependencies

<dependency>
  <groupId>org.kie.server</groupId>
  <artifactId>kie-server-client</artifactId>
</dependency>

To create a remote client for Red Hat Decision Manager, declare the following dependency:

Client dependency

<dependency>
  <groupId>org.uberfire</groupId>
  <artifactId>uberfire-rest-client</artifactId>
</dependency>

When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as kjar and use org.kie:kie-maven-plugin to process the kjar packaging type located under the <project> element. In the following example, ${kie.version} is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:
```
<packaging>kjar</packaging>
<build>
 <plugins>
  <plugin>
   <groupId>org.kie</groupId>
   <artifactId>kie-maven-plugin</artifactId>
   <version>${kie.version}</version>
   <extensions>true</extensions>
  </plugin>
 </plugins>
</build>
```

21.2. Configuring an external Maven repository for Business Central and KIE Server

You can configure Business Central and KIE Server to use an external Maven repository, such as Nexus or Artifactory, instead of the built-in repository. This enables Business Central and KIE Server to access and download artifacts that are maintained in the external Maven repository.

Important

Artifacts in the repository do not receive automated security patches because Maven requires that artifacts be immutable. As a result, artifacts that are missing patches for known security flaws will remain in the repository to avoid breaking builds that depend on them. The version numbers of patched artifacts are incremented. For more information, see JBoss Enterprise Maven Repository.

Note

For information about configuring an external Maven repository for an authoring environment on Red Hat OpenShift Container Platform, see the following documents:

Prerequisites

Business Central and KIE Server are installed. For installation options, see Planning a Red Hat Decision Manager installation.

Procedure

Create a Maven settings.xml file with connection and access details for your external repository. For details about the settings.xml file, see the Maven Settings Reference.
Save the file in a known location, for example, /opt/custom-config/settings.xml.
In your Red Hat Decision Manager installation directory, navigate to the standalone-full.xml file. For example, if you use a Red Hat JBoss EAP installation for Red Hat Decision Manager, go to $EAP_HOME/standalone/configuration/standalone-full.xml.
Open standalone-full.xml and under the <system-properties> tag, set the kie.maven.settings.custom property to the full path name of the settings.xml file.
For example:
```
<property name="kie.maven.settings.custom" value="/opt/custom-config/settings.xml"/>
```
Start or restart Business Central and KIE Server.

Next steps

For each Business Central project that you want to export or push as a KJAR artifact to the external Maven repository, you must add the repository information in the project pom.xml file. For instructions, see Packaging and deploying a Red Hat Decision Manager project.

21.3. Preparing a Maven mirror repository for offline use

If your Red Hat Decision Manager deployment does not have outgoing access to the public Internet, you must prepare a Maven repository with a mirror of all the necessary artifacts and make this repository available to your environment.

Note

You do not need to complete this procedure if your Red Hat Decision Manager deployment is connected to the Internet.

Prerequisites

A computer that has outgoing access to the public Internet is available.

Procedure

On the computer that has an outgoing connection to the public Internet, complete the following steps:
Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Red Hat Decision Manager
- Version: 7.10
  1. Download and extract the Red Hat Process Automation Manager 7.10.0 Offliner Content List (rhdm-7.10.0-offliner.zip) product deliverable file.
  2. Extract the contents of the rhdm-7.10.0-offliner.zip file into any directory.
  3. Change to the directory and enter the following command:
    ./offline-repo-builder.sh offliner.txt
    This command creates the repository subdirectory and downloads the necessary artifacts into this subdirectory. This is the mirror repository.
    If a message reports that some downloads have failed, run the same command again. If downloads fail again, contact Red Hat support.
If you developed services outside of Business Central and they have additional dependencies, add the dependencies to the mirror repository. If you developed the services as Maven projects, you can use the following steps to prepare these dependencies automatically. Complete the steps on the computer that has an outgoing connection to the public Internet.
1. Create a backup of the local Maven cache directory (~/.m2/repository) and then clear the directory.
2. Build the source of your projects using the mvn clean install command.
3. For every project, enter the following command to ensure that Maven downloads all runtime dependencies for all the artifacts generated by the project:
```
mvn -e -DskipTests dependency:go-offline -f /path/to/project/pom.xml --batch-mode -Djava.net.preferIPv4Stack=true
```
  Replace /path/to/project/pom.xml with the path of the pom.xml file of the project.
4. Copy the contents of the local Maven cache directory (~/.m2/repository) to the repository subdirectory that was created.
Copy the contents of the repository subdirectory to a directory on the computer on which you deployed Red Hat Decision Manager. This directory becomes the offline Maven mirror repository.
Create and configure a settings.xml file for your Red Hat Decision Manager deployment as described in Section 21.2, “Configuring an external Maven repository for Business Central and KIE Server”.
Make the following changes in the settings.xml file:
- Under the <profile> tag, if a <repositories> or <pluginRepositores> tag is missing, add the missing tags.
- Under <repositories> add the following content:
```
<repository>
  <id>offline-repository</id>
  <url>file:///path/to/repo</url>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
</repository>
```
  Replace /path/to/repo with the full path to the local Maven mirror repository directory.
- Under <pluginRepositories> add the following content:
```
<repository>
  <id>offline-plugin-repository</id>
  <url>file:///path/to/repo</url>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
</repository>
```
  Replace /path/to/repo with the full path to the local Maven mirror repository directory.
Set the kie.maven.offline.force property for Business Central to true. For instructions about setting properties for Business Central, see Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.3.

Chapter 22. Importing projects from Git repositories

Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created.

Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is embedded in Business Central. If you have projects in other Git repositories, you can import those projects into the Business Central Git repository through Business Central spaces.

Prerequisites

Red Hat Decision Manager projects exist in an external Git repository.
You have the credentials required for read access to that external Git repository.

Procedure

In Business Central, click Menu → Design → Projects.
Select or create the space into which you want to import the projects. The default space is MySpace.
To import a project, do one of the following:
- Click Import Project.
- Select Import Project from the drop-down list.
In the Import Project window, enter the URL and credentials for the Git repository that contains the projects that you want to import and click Import. The projects are added to the Business Central Git repository and are available from the current space.

Chapter 23. Customizing the branding of Business Central

You can customize the branding of the Business Central login page and application header by replacing the images with your own.

23.1. Customizing the Business Central login page

You can customize the company logo and the project logo on the Business Central login page.

Procedure

Start Red Hat JBoss EAP and open Business Central in a web browser.
Copy an SVG format image to the EAP_HOME/standalone/deployments/decision-central.war/img/ directory in your Red Hat Decision Manager installation.
In the EAP_HOME/standalone/deployments/decision-central.war/img/ directory, either move or rename the existing redhat_logo.png file.
Rename your PNG file redhat_logo.png.
To change the project logo that appears above the User name and Password fields, replace the default image BC_Logo.png with a new SVG file.
Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.

23.2. Customizing Business Central application header

You can customize the Business Central application header.

Procedure

Start Red Hat JBoss EAP, open Business Central in a web browser, and log in with your user credentials.
Copy your new application header image in the SVG format to the EAP_HOME/standalone/deployments/decision-central.war/banner/ directory in your Red Hat Decision Manager installation.
Open the EAP_HOME/standalone/deployments/decision-central.war/banner/banner.html file in a text editor.
Replace logo.png in the <img> tag with the file name of your new image:admin-and-config/
```
<img src="banner/logo.png"/>
```
Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.

Chapter 24. Integrating LDAP and SSL

With Red Hat Decision Manager you can integrate LDAP and SSL through RH-SSO. For more information, see the Red Hat Single Sign-On Server Administration Guide.

Appendix A. Business Central system properties

The Business Central system properties listed in this section are passed to standalone*.xml files.

Git directory

Use the following properties to set the location and name for the Business Central Git directory:

org.uberfire.nio.git.dir: Location of the Business Central Git directory.
org.uberfire.nio.git.dirname: Name of the Business Central Git directory. Default value: .niogit.
org.uberfire.nio.git.ketch: Enables or disables Git ketch.
org.uberfire.nio.git.hooks: Location of the Git hooks directory.

Git over HTTP

Use the following properties to configure access to the Git repository over HTTP:

org.uberfire.nio.git.proxy.ssh.over.http: Specifies whether SSH should use an HTTP proxy. Default value: false.
http.proxyHost: Defines the host name of the HTTP proxy. Default value: null.
http.proxyPort: Defines the host port (integer value) of the HTTP proxy. Default value: null.
http.proxyUser: Defines the user name of the HTTP proxy.
http.proxyPassword: Defines the user password of the HTTP proxy.
org.uberfire.nio.git.http.enabled: Enables or disables the HTTP daemon. Default value: true.
org.uberfire.nio.git.http.host: If the HTTP daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.http.hostname: If the HTTP daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.http.port: If the HTTP daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: 8080.

Git over HTTPS

Use the following properties to configure access to the Git repository over HTTPS:

org.uberfire.nio.git.proxy.ssh.over.https: Specifies whether SSH uses an HTTPS proxy. Default value: false.
https.proxyHost: Defines the host name of the HTTPS proxy. Default value: null.
https.proxyPort: Defines the host port (integer value) of the HTTPS proxy. Default value: null.
https.proxyUser: Defines the user name of the HTTPS proxy.
https.proxyPassword: Defines the user password of the HTTPS proxy.
user.dir: Location of the user directory.
org.uberfire.nio.git.https.enabled: Enables or disables the HTTPS daemon. Default value: false
org.uberfire.nio.git.https.host: If the HTTPS daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.https.hostname: If the HTTPS daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.https.port: If the HTTPS daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: 8080.

JGit

org.uberfire.nio.jgit.cache.instances: Defines the JGit cache size.
org.uberfire.nio.jgit.cache.overflow.cleanup.size: Defines the JGit cache overflow cleanup size.
org.uberfire.nio.jgit.remove.eldest.iterations: Enables or disables whether to remove eldest JGit iterations.
org.uberfire.nio.jgit.cache.evict.threshold.duration: Defines the JGit evict threshold duration.
org.uberfire.nio.jgit.cache.evict.threshold.time.unit: Defines the JGit evict threshold time unit.

Git daemon

Use the following properties to enable and configure the Git daemon:

org.uberfire.nio.git.daemon.enabled: Enables or disables the Git daemon. Default value: true.
org.uberfire.nio.git.daemon.host: If the Git daemon is enabled, it uses this property as the local host identifier. Default value: localhost.
org.uberfire.nio.git.daemon.hostname: If the Git daemon is enabled, it uses this property as the local host name identifier. Default value: localhost
org.uberfire.nio.git.daemon.port: If the Git daemon is enabled, it uses this property as the port number. Default value: 9418.
org.uberfire.nio.git.http.sslVerify: Enables or disables SSL certificate checking for Git repositories. Default value: true.
Note
If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.

Git SSH

Use the following properties to enable and configure the Git SSH daemon:

org.uberfire.nio.git.ssh.enabled: Enables or disables the SSH daemon. Default value: true.
org.uberfire.nio.git.ssh.host: If the SSH daemon enabled, it uses this property as the local host identifier. Default value: localhost.
org.uberfire.nio.git.ssh.hostname: If the SSH daemon is enabled, it uses this property as local host name identifier. Default value: localhost.
org.uberfire.nio.git.ssh.port: If the SSH daemon is enabled, it uses this property as the port number. Default value: 8001.
Note
If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.
org.uberfire.nio.git.ssh.cert.dir: Location of the .security directory where local certificates are stored. Default value: Working directory.
org.uberfire.nio.git.ssh.idle.timeout: Sets the SSH idle timeout.
org.uberfire.nio.git.ssh.passphrase: Pass phrase used to access the public key store of your operating system when cloning git repositories with SCP style URLs. Example: git@github.com:user/repository.git.
org.uberfire.nio.git.ssh.algorithm: Algorithm used by SSH. Default value: RSA.
org.uberfire.nio.git.gc.limit: Sets the GC limit.
org.uberfire.nio.git.ssh.ciphers: A comma-separated string of ciphers. The available ciphers are aes128-ctr, aes192-ctr, aes256-ctr, arcfour128, arcfour256, aes192-cbc, aes256-cbc. If the property is not used, all available ciphers are loaded.
org.uberfire.nio.git.ssh.macs: A comma-separated string of message authentication codes (MACs). The available MACs are hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512. If the property is not used, all available MACs are loaded.
Note
If you plan to use RSA or any algorithm other than DSA, make sure you set up your application server to use the Bouncy Castle JCE library.

KIE Server nodes and Decision Manager controller

Use the following properties to configure the connections with the KIE Server nodes from the Decision Manager controller:

org.kie.server.controller: The URL is used to connect to the Decision Manager controller. For example, ws://localhost:8080/decision-central/websocket/controller.
org.kie.server.user: User name used to connect to the KIE Server nodes from the Decision Manager controller. This property is only required when using this Business Central installation as a Decision Manager controller.
org.kie.server.pwd: Password used to connect to the KIE Server nodes from the Decision Manager controller. This property is only required when using this Business Central installation as a Decision Manager controller.

Maven and miscellaneous

Use the following properties to configure Maven and other miscellaneous functions:

kie.maven.offline.force: Forces Maven to behave as if offline. If true, disables online dependency resolution. Default value: false.
Note
Use this property for Business Central only. If you share a runtime environment with any other component, isolate the configuration and apply it only to Business Central.
org.uberfire.gzip.enable: Enables or disables Gzip compression on the GzipFilter compression filter. Default value: true.
org.kie.workbench.profile: Selects the Business Central profile. Possible values are FULL or PLANNER_AND_RULES. A prefix FULL_ sets the profile and hides the profile preferences from the administrator preferences. Default value: FULL
org.appformer.m2repo.url: Business Central uses the default location of the Maven repository when looking for dependencies. It directs to the Maven repository inside Business Central, for example, http://localhost:8080/business-central/maven2. Set this property before starting Business Central. Default value: File path to the inner m2 repository.
appformer.ssh.keystore: Defines the custom SSH keystore to be used with Business Central by specifying a class name. If the property is not available, the default SSH keystore is used.
appformer.ssh.keys.storage.folder: When using the default SSH keystore, this property defines the storage folder for the user’s SSH public keys. If the property is not available, the keys are stored in the Business Central .security folder.
appformer.experimental.features: Enables the experimental features framework. Default value: false.
org.kie.demo: Enables an external clone of a demo application from GitHub.
org.uberfire.metadata.index.dir: Place where the Lucene .index directory is stored. Default value: Working directory.
org.uberfire.ldap.regex.role_mapper: Regex pattern used to map LDAP principal names to the application role name. Note that the variable role must be a part of the pattern as the application role name substitutes the variable role when matching a principle value and role name.
org.uberfire.sys.repo.monitor.disabled: Disables the configuration monitor. Do not disable unless you are sure. Default value: false.
org.uberfire.secure.key: Password used by password encryption. Default value: org.uberfire.admin.
org.uberfire.secure.alg: Crypto algorithm used by password encryption. Default value: PBEWithMD5AndDES.
org.uberfire.domain: Security-domain name used by uberfire. Default value: ApplicationRealm.
org.guvnor.m2repo.dir: Place where the Maven repository folder is stored. Default value: <working-directory>/repositories/kie.
org.guvnor.project.gav.check.disabled: Disables group ID, artifact ID, and version (GAV) checks. Default value: false.
org.kie.build.disable-project-explorer: Disables automatic build of a selected project in Project Explorer. Default value: false.
org.kie.builder.cache.size: Defines the cache size of the project builder. Default value: 20.
org.kie.library.assets_per_page: You can customize the number of assets per page in the project screen. Default value: 15.
org.kie.verification.disable-dtable-realtime-verification: Disables the real-time validation and verification of decision tables. Default value: false.

Decision Manager controller

Use the following properties to configure how to connect to the Decision Manager controller:

org.kie.workbench.controller: The URL used to connect to the Decision Manager controller, for example, ws://localhost:8080/kie-server-controller/websocket/controller.
org.kie.workbench.controller.user: The Decision Manager controller user. Default value: kieserver.
org.kie.workbench.controller.pwd: The Decision Manager controller password. Default value: kieserver1!.
org.kie.workbench.controller.token: The token string used to connect to the Decision Manager controller.

Java Cryptography Extension KeyStore (JCEKS)

Use the following properties to configure JCEKS:

kie.keystore.keyStoreURL: The URL used to load a Java Cryptography Extension KeyStore (JCEKS). For example, file:///home/kie/keystores/keystore.jceks.
kie.keystore.keyStorePwd: The password used for the JCEKS.
kie.keystore.key.ctrl.alias: The alias of the key for the default REST Decision Manager controller.
kie.keystore.key.ctrl.pwd: The password of the alias for the default REST Decision Manager controller.

Rendering

Use the following properties to switch between Business Central and KIE Server rendered forms:

org.jbpm.wb.forms.renderer.ext: Switches the form rendering between Business Central and KIE Server. By default, the form rendering is performed by Business Central. Default value: false.
org.jbpm.wb.forms.renderer.name: Enables you to switch between Business Central and KIE Server rendered forms. Default value: workbench.

Chapter 25. Additional resources

Installing and configuring Red Hat Decision Manager in a Red Hat JBoss EAP clustered environment

Chapter 26. Next steps

Part III. Installing and configuring Red Hat Decision Manager in a Red Hat JBoss EAP clustered environment

As a system engineer, you can create a Red Hat Decision Manager clustered environment to provide high availability and load balancing for your development and runtime environments.

Prerequisites

You have reviewed the information in Planning a Red Hat Decision Manager installation.

Chapter 27. Red Hat Decision Manager clusters

By clustering two or more computers, you have the benefits of high availability, enhanced collaboration, and load balancing. High availability decreases the chance of data loss when a single computer fails. When a computer fails, another computer fills the gap by providing a copy of the data that was on the failed computer. When the failed computer comes online again, it resumes its place in the cluster.

There are several ways that you can cluster Red Hat Decision Manager components. This document describes how to cluster the following scenarios:

Chapter 28, Red Hat Decision Manager clusters in a development (authoring) environment
Chapter 29, KIE Server clusters in a runtime environment

Chapter 28. Red Hat Decision Manager clusters in a development (authoring) environment

You can configure Red Hat Decision Manager as a clustered development environment to benefit from high availability. With a clustered environment, if a developer is working on a node and that node fails, that developer’s work is preserved and visible on any other node of the cluster.

Most development environments consist of Business Central and at least one KIE Server .

To create a Red Hat Decision Manager clustered development environment, you must perform the following tasks:

Configure Red Hat JBoss EAP 7.3 with Red Hat Data Grid 7.3 on a machine.
Configure AMQ Broker, a Java messaging server (JMS) broker, on a machine.
Configure an NFS file server on a machine.
Download Red Hat JBoss EAP 7.3 and Red Hat Decision Manager 7.10, then install them on each machine that is to become a cluster node.
Configure and start Business Central on each cluster node to start the operation of the cluster.

Red Hat Data Grid is built from the Infinispan open-source software project. It is a distributed in-memory key/value data store that has indexing capabilities that enable you to store, search, and analyze high volumes of data quickly and in near-real time. In a Red Hat Decision Manager clustered environment, it enables you to perform complex and efficient searches across cluster nodes.

A JMS broker is a software component that receives messages, stores them locally, and forwards the messages to a recipient. AMQ Broker enables your applications to communicate with any messaging provider. It specifies how components such as message-driven beans, Enterprise JavaBeans, and servlets can send or receive messages.

28.1. Installing and configuring Red Hat Data Grid

Install and configure Red Hat Data Grid for the Red Hat Decision Manager clustered environment for more efficient searching across cluster nodes.

For information about advanced installation and configuration options, and Red Hat Data Grid modules for Red Hat JBoss EAP, see the Red Hat Data Grid User Guide.

Note

Do not install Red Hat Data Grid on the same node as Business Central.

Prerequisites

A Java Virtual Machine (JVM) environment compatible with Java 8.0 or later is installed.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Data Grid
- Version: 7.3
Download and extract the Red Hat JBoss Data Grid 7.3.0 Server (jboss-datagrid-7.3.0-1-server.zip) installation file to the preferred location on your system.
The extracted directory is referred to as JDG_HOME.
Update Red Hat Data Grid to the latest version. For more information, see Red Hat Data Grid Red Hat Data Grid User Guide.
To run Red Hat Data Grid, navigate to JDG_HOME/bin and enter the following command:
```
$ ./standalone.sh -c clustered.xml -b <HOST>
```
Replace <HOST> with the IP address or host name of the server where you installed Red Hat Data Grid.

28.2. Downloading and configuring AMQ Broker

Red Hat AMQ Broker enables your applications to communicate with any messaging provider. It specifies how components such as message-driven beans, Enterprise JavaBeans, and servlets can send or receive messages.

For information about advanced installations and configuration options, see Getting started with AMQ Broker.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: AMQ Broker
- Version: 7.8.0
Click Download next to Red Hat AMQ Broker 7.8.0 (amq-broker-7.8.0-bin.zip).
Extract the amq-broker-7.8.0-bin.zip file.
Change directory to amq-broker-7.8.0-bin/amq-broker-7.8.0/bin.
Enter the following command and replace the following placeholders to create the broker and broker user:
- <HOST> is the IP address or host name of the server where you installed AMQ Broker.
- <AMQ_USER> and <AMQ_PASSWORD> is a user name and password combination of your choice.
- <BROKER_NAME> is a name for the broker that you are creating.
```
./artemis create --host <HOST> --user <AMQ_USER> --password <AMQ_PASSWORD> --require-login <BROKER_NAME>
```
To run AMQ Broker, enter the following command in the amq-broker-7.8.0-bin/amq-broker-7.8.0/bin directory:
```
<BROKER_NAME>/bin/artemis run
```

28.3. Configuring an NFS server

A shared file system is required for a Business Central clustered environment and each client node must have access to the shared file system.

You must deploy and configure an NFS version 4 server.

Procedure

Configure a server to export NFS version 4 shares. For instructions about exporting NFS shares on Red Hat Enterprise Linux, see Exporting NFS shares in Managing file systems. For more information about creating the NFS server, see How to configure NFS in RHEL 7.
On the server, create an /opt/kie/data share with the rw,sync,no_root_squash options by adding the following line to the /etc/exports file:
```
/opt/kie/data *(rw,sync,no_root_squash)
```
In this example, /opt/kie/data is the shared folder, * are the IP addresses allowed to connect to the NFS server, and (rw,sync,no_root_squash) are the minimum options required for NFS. For example:
```
/opt/kie/data 192.268.1.0/24(rw,sync,no_root_squash)
```
Note
You can use another share name instead of '/opt/kie/data'. In this case, you must use this name when configuring all nodes that run Business Central.

28.4. Downloading and extracting Red Hat JBoss EAP 7.3 and Red Hat Decision Manager

Download and install Red Hat JBoss EAP 7.3 and Red Hat Decision Manager 7.10 on each node of the cluster.

Procedure

Download Red Hat JBoss EAP 7.3 on each node of the cluster:
1. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
  - Product: Enterprise Application Platform
  - Version: 7.3
2. Click Download next to Red Hat JBoss Enterprise Application Platform 7.3.4. (JBEAP-7.3.4/jboss-eap-7.3.4.zip).
Extract the jboss-eap-7.3.4.zip file. In the following steps, EAP_HOME is the jboss-eap-7.3/jboss-eap-7.3 directory.
Download and apply the latest Red Hat JBoss EAP patch, if available.
Download Red Hat Decision Manager on each node of the cluster:
1. Navigate to the Software Downloads page in the Red Hat Customer Portal, and select the product and version from the drop-down options:
  - Product: Decision Manager
  - Version: 7.10
2. Download Red Hat Decision Manager 7.10.0 Business Central Deployable for Red Hat JBoss EAP 7 (rhdm-7.10.0-decision-central-eap7-deployable.zip).
Extract the rhdm-7.10.0-decision-central-eap7-deployable.zip file to a temporary directory. In the following commands this directory is called TEMP_DIR.
Copy the contents of TEMP_DIR/rhdm-7.10.0-decision-central-eap7-deployable/jboss-eap-7.3 to EAP_HOME.
Download and apply the latest Red Hat Decision Manager patch, if available.
Configure Red Hat Single Sign-On for your high availability environment. For more information, see Integrating Red Hat Decision Manager with Red Hat Single Sign-On and the Red Hat Single Sign-On Server Administration Guide.

28.5. Configuring and running Business Central in a cluster

After you install Red Hat JBoss EAP and Business Central you can use Red Hat Data Grid and the AMQ Broker to configure the cluster. Complete these steps on each node of the cluster.

Note

These steps describe a basic cluster configuration. For more complex configurations, see the Red Hat JBoss EAP 7.3 Configuration Guide.

Note

Do not connect KIE Server to Business Central in high availability (HA) on premise environments.

Business Central instances are not able to keep in sync with the status of each KIE Server. For example, if a KIE Server is up but not in sync, Business Central will not be able to deploy through that instance.

Prerequisites

Red Hat Data Grid 7.3 is installed as described in Section 28.1, “Installing and configuring Red Hat Data Grid”.
AMQ Broker is installed and configured, as described in Section 28.2, “Downloading and configuring AMQ Broker”.
Red Hat JBoss EAP and Red Hat Decision Manager are installed on each node of the cluster as described in Section 28.4, “Downloading and extracting Red Hat JBoss EAP 7.3 and Red Hat Decision Manager”.
An NFS server with a shared folder is available as described in Section 28.3, “Configuring an NFS server”.

Procedure

Mount the directory shared over NFS as /data. Enter the following commands as the root user:
```
mkdir /data
mount <NFS_SERVER_IP>:<DATA_SHARE> /data
```
Replace <NFS_SERVER_IP> with the IP address or hostname of the NFS server machine. Replace <DATA_SHARE> with the share name that you configured (for example, /opt/kie/data).
Create a kie-wb-playground directory in the /data NFS directory:
```
mkdir /kie-wb-playground
```

Create a kie-wb-playground directory in the EAP_HOME/bin directory and mount the directory:

mount -o rw,sync,actimeo=1 <NFS_SERVER_IP>:<DATA_SHARE>/kie-wb-playground kie-wb-playground

Open the EAP_HOME/standalone/configuration/standalone-full.xml file in a text editor.

Edit or add the properties under the <system-properties> element and replace the following placeholders:

<AMQ_USER> and <AMQ_PASSWORD> are the credentials that you defined when creating the AMQ Broker.
<AMQ_BROKER_IP_ADDRESS> is the IP address of the AMQ Broker.

<DATA_GRID_NODE_IP> is the IP address where Red Hat Data Grid is installed.

<system-properties>
  <property name="appformer-jms-connection-mode" value="REMOTE"/>
  <property name="appformer-jms-username" value="<AMQ_USER>"/>
  <property name="appformer-jms-password" value="<AMQ_USER_PASSWORD>"/>
  <property name="appformer-jms-url"
     value="tcp://<AMQ_BROKER_IP_ADDRESS>:61616?ha=true&amp;retryInterval=1000&amp;retryIntervalMultiplier=1.0&amp;reconnectAttempts=-1"/>
  <property name="org.appformer.ext.metadata.infinispan.port"
     value="11222"/>
  <property name="org.appformer.ext.metadata.infinispan.host"
     value="<DATA_GRID_NODE_IP>"/>
  <property name="org.appformer.ext.metadata.infinispan.realm"
     value="ApplicationRealm"/>
  <property name="org.appformer.ext.metadata.infinispan.cluster"
     value="kie-cluster"/>
  <property name="org.appformer.ext.metadata.index"
     value="infinispan"/>
  <property name="org.uberfire.nio.git.dir"
     value="/data"/>
  <property name="es.set.netty.runtime.available.processors"
     value="false"/>
</system-properties>

Optional: If the Red Hat Data Grid deployment requires authentication, edit or add the properties under the <system-properties> element and replace the following placeholders:
- <SERVER_NAME> is the server name specified in your Red Hat Data Grid server configuration.
- <SASL_QOP> is the combination of auth, auth-int and auth-conf values for your Red Hat Data Grid server configuration.
```
<property name="org.appformer.ext.metadata.infinispan.server.name"
   value="<SERVER_NAME>"/>
<property name="org.appformer.ext.metadata.infinispan.sasl.qop"
   value="<SASL_QOP>"/>
<property name="org.appformer.ext.metadata.infinispan.username"
   value=""/>
<property name="org.appformer.ext.metadata.infinispan.password"
   value=""/>
```
Save the standalone-full.xml file.
To start the cluster, navigate to EAP_HOME/bin and enter the following command:
```
$ ./standalone.sh -c standalone-full.xml -b <HOST>
```
Replace <HOST> with the IP address or host name of the server where you installed Red Hat Decision Manager.

28.6. Testing your high availability (HA) on-premise infrastructure

When you create a production-ready high availability (HA) on-premises infrastructure for Business Central, you must ensure that it meets the minimum hardware and performance requirements for a viable HA environment. An HA on-premise infrastructure consists of the following four main components: Business Central, the message system (AMQ), the indexing server (Red Hat Data Grid), and a shared file system (NFS/GlusterFS/Ceph).

Prerequisites

A network environment of at least 3 nodes is configured with the following layout:
Node 1: Business Central
Node 2: Business Central
Node 3: AMQ, Red Hat Data Grid, and NFS

Procedure

Test the network speed by following these steps:

In the command terminal of each server node, install iPerf3:
```
$ dnf install iperf3
```
In the command terminal of the NFS server node (server node 3), start iPerf3 in server mode:
```
$ iperf3 -s
```
In the command terminal of each Business Central server node, start iPerf3 in client mode with the NFS server node set as the host:
```
$ iperf3 -c <NFS_SERVER_IP>
```

Compare the results from each server node with the following example of minimum values:

iperf3 -c 172.31.47.103
Connecting to host 172.31.47.103, port 5201
[  5] local 172.31.39.4 port 44820 connected to 172.31.47.103 port 5201
[ ID] Interval           Transfer     Bitrate         Retr  Cwnd
[  5]   0.00-1.00   sec   143 MBytes  1.20 Gbits/sec    0    419 KBytes
[  5]   1.00-2.00   sec   111 MBytes   928 Mbits/sec    6    848 KBytes
[  5]   2.00-3.00   sec  53.8 MBytes   451 Mbits/sec    0   1.08 MBytes
[  5]   3.00-4.00   sec  52.5 MBytes   440 Mbits/sec    1   1022 KBytes
[  5]   4.00-5.00   sec  53.8 MBytes   451 Mbits/sec    1    935 KBytes
[  5]   5.00-6.00   sec  53.8 MBytes   451 Mbits/sec    1    848 KBytes
[  5]   6.00-7.00   sec  52.5 MBytes   440 Mbits/sec    0   1.08 MBytes
[  5]   7.00-8.00   sec  53.8 MBytes   451 Mbits/sec    1   1.01 MBytes
[  5]   8.00-9.00   sec  53.8 MBytes   451 Mbits/sec    1    953 KBytes
[  5]   9.00-10.00  sec  52.5 MBytes   440 Mbits/sec    1    856 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval           Transfer     Bitrate         Retr
[  5]   0.00-10.00  sec   680 MBytes   570 Mbits/sec   12             sender
[  5]   0.00-10.04  sec   677 MBytes   566 Mbits/sec                  receiver

iperf Done.

Verify the NFS information by following these steps:

In the command terminal of each Business Central server node, mount the NFS node:
```
$ mount -o actimeo=1 <NFS_SERVER_IP>:/opt/nfs/kie /opt/kie/niogit
```
In the command terminal of each mounted node, enter nfsiostat:
```
$ nfsiostat
```

Compare the results from each server node with the following example of minimum values:

nfsiostat
ops/s	rpc bklog
6.415	0.000

read:
ops/s	kB/s	kB/op	retrans	avg RTT (ms)	avg exe (ms)	avg queue (ms)	errors
0.031	0.045	1.452	0 (0.0%)	0.129		0.166		0.019		0 (0.0%)

write:
ops/s	kB/s	kB/op	retrans	avg RTT (ms)	avg exe (ms)	avg queue (ms)	errors
0.517	0.467	0.903	0 (0.0%)	1.235		1.269		0.01 8		0 (0.0%)

Verify that the disk is an SSD by following these steps:

In the command terminal of the NFS server, enter df -h to identify the disk as shown in the following example:

$ df -h
Filesystem               Size  Used Avail Use% Mounted on
devtmpfs                 3.8G     0  3.8G   0% /dev
tmpfs                    3.9G     0  3.9G   0% /dev/shm
tmpfs                    3.9G   33M  3.8G   1% /run
tmpfs                    3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/xvda2                25G  3.2G   22G  13% /
tmpfs                    781M     0  781M   0% /run/user/1000
172.31.47.103:/root/nfs   25G  2.1G   23G   9% /root/nfs

Enter lsblk -d to verify that the disk is an SSD:
```
$ lsblk -d
```
Enter hdparm -Tt to test the disk:
```
$ hdparm -Tt /dev/xvda2
```

Compare the results from each server node with the following example of minimum values:

$ hdparm -Tt /dev/xvda2

/dev/xvda2:
 Timing cached reads:   18670 MB in  1.99 seconds = 9389.01 MB/sec
 Timing buffered disk reads: 216 MB in  3.03 seconds =  71.40 MB/sec

28.7. Verifying the Red Hat Decision Manager cluster

After configuring the cluster for Red Hat Decision Manager, create an asset to verify that the installation is working.

Procedure

In a web browser, enter <node-IP-address>:8080/decision-central. Replace <node-IP-address> with the IP address of a particular node.
Enter the admin user credentials that you created during installation. The Business Central home page appears.
Select Menu → Design → Projects.
Open the MySpace space.
Click Try Samples → Mortgages → OK. The Assets window appears.
Click Add Asset → Data Object.
Enter MyDataObject in the Data Object field and click OK.
Click Spaces → MySpace → Mortgages and confirm that MyDataObject is in the list of assets.
Enter the following URL in a web browser, where <node_IP_address> is the address of a different node of the cluster:
http://<node_IP_address>:8080/decision-central
Enter the same credentials that you used to log in to Business Central on the first node, where you created the MyDataObject asset.
Select Menu→ Design → Projects.
Open the MySpace space.
Select the Mortgages project.
Verify that MyDataObject is in the asset list.
Delete the Mortgages project.

Chapter 29. KIE Server clusters in a runtime environment

The primary benefit of clustering a KIE Server runtime environment is load balancing. If activity on one node of the cluster increases, that activity can be shared among the other nodes of the cluster to improve performance.

To create a KIE Server clustered runtime environment, you download and extract Red Hat JBoss EAP 7.3 and KIE Server. Then, you configure Red Hat JBoss EAP 7.3 for a cluster, start the cluster, and install KIE Server on each cluster node.

Optionally, you can then cluster the headless Decision Manager controller.

Note

Do not connect KIE Server to Business Central in high availability (HA) on premise environments.

29.1. Downloading and extracting Red Hat JBoss EAP 7.3 and KIE Server

Complete the steps in this section to download and install Red Hat JBoss EAP 7.3 and KIE Server for installation in a clustered environment.

Procedure

Download Red Hat JBoss EAP 7.3 on each node of the cluster:
1. Navigate to the Software Downloads page in the Red Hat Customer Portal (login required) and select the product and version from the drop-down options:
  - Product: Red Hat JBoss EAP
  - Version: 7.3
2. Click Download next to Red Hat JBoss Enterprise Application Platform 7.3.4. (jboss-eap-7.3.4.zip).
Extract the jboss-eap-7.3.4.zip file. The jboss-eap-7.3/jboss-eap-7.3 directory is referred to as EAP_HOME.
Download and apply the latest Red Hat JBoss EAP patch, if available.
Download KIE Server:
1. Navigate to the Software Downloads page in the Red Hat Customer Portal and select the product and version from the drop-down options:
  - Product: Decision Manager
  - Version: 7.10
2. Download Red Hat Decision Manager 7.10.0 KIE Server for All Supported EE8 Containers (rhdm-7.10.0-kie-server-ee8.zip).
Extract the rhdm-7.10.0-kie-server-ee8.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the TEMP_DIR/rhdm-7.10.0-kie-server-ee8/rhdm-7.10.0-kie-server-ee8/kie-server.war directory to EAP_HOME/standalone/deployments/.
Warning
Ensure the names of the Red Hat Decision Manager deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-kie-server-ee8/rhdm-7.10.0-kie-server-ee8/SecurityPolicy/ to EAP_HOME/bin.
When prompted to overwrite files, click Replace.
In the EAP_HOME/standalone/deployments/ directory, create an empty file named kie-server.war.dodeploy. This file ensures that KIE Server is automatically deployed when the server starts.
Download and apply the latest Red Hat Decision Manager patch, if available.
Navigate to the EAP_HOME/bin directory.
Create a user with the kie-server role that you will use to log in to KIE Server.
```
$ ./add-user.sh -a --user <USERNAME>  --password <PASSWORD> --role kie-server
```
Make a note of your user names and passwords.
To start the cluster, navigate to EAP_HOME/bin and enter one of the following commands:
- On Linux or UNIX-based systems:
```
$ ./standalone.sh -c standalone-full.xml
```
- On Windows:
```
standalone.bat -c standalone-full.xml
```

29.2. Clustering KIE Servers with the headless Decision Manager controller

The Decision Manager controller is integrated with Business Central. However, if you do not install Business Central, you can install the headless Decision Manager controller and use the REST API or the KIE Server Java Client API to interact with it.

Prerequisites

A backed-up Red Hat JBoss EAP installation version 7.3 or later is available. The base directory of the Red Hat JBoss EAP installation is referred to as EAP_HOME.
Sufficient user permissions to complete the installation are granted.
An NFS server with a shared folder is available as described in Section 28.3, “Configuring an NFS server”.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 Add Ons (the rhdm-7.10.0-add-ons.zip file).
Extract the rhdm-7.10.0-add-ons.zip file. The rhdm-7.10.0-controller-ee7.zip file is in the extracted directory.
Extract the rhdm-7.10.0-controller-ee7 archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the TEMP_DIR/rhdm-7.10.0-controller-ee7/controller.war directory to EAP_HOME/standalone/deployments/.
Warning
Ensure that the names of the headless Decision Manager controller deployments you copy do not conflict with your existing deployments in the Red Hat JBoss EAP instance.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-controller-ee7/SecurityPolicy/ directory to EAP_HOME/bin.
When prompted to overwrite files, click Yes.
In the EAP_HOME/standalone/deployments/ directory, create an empty file named controller.war.dodeploy. This file ensures that the headless Decision Manager controller is automatically deployed when the server starts.
Open the EAP_HOME/standalone/configuration/standalone.xml file in a text editor.
Add the following properties to the <system-properties> element and replace <NFS_STORAGE> with the absolute path to the NFS storage where the template configuration is stored:
```
<system-properties>
  <property name="org.kie.server.controller.templatefile.watcher.enabled" value="true"/>
  <property name="org.kie.server.controller.templatefile" value="<NFS_STORAGE>"/>
</system-properties>
```
Template files contain default configurations for specific deployment scenarios.
If the value of the org.kie.server.controller.templatefile.watcher.enabled property is set to true, a separate thread is started to watch for modifications of the template file. The default interval for these checks is 30000 milliseconds and can be further controlled by the org.kie.server.controller.templatefile.watcher.interval system property. If the value of this property is set to false, changes to the template file are detected only when the server restarts.
To start the headless Decision Manager controller, navigate to EAP_HOME/bin and enter the following command:
- On Linux or UNIX-based systems:
```
$ ./standalone.sh
```
- On Windows:
```
standalone.bat
```

Chapter 30. Additional resources

Part IV. Installing and configuring Red Hat Decision Manager on Red Hat JBoss Web Server

This document describes how to install Red Hat Decision Manager 7.10 on JBoss Web Server.

Prerequisites

You have reviewed the information in Planning a Red Hat Decision Manager installation.
You have installed Red Hat JBoss Web Server 5.4.0. For information about installing Red Hat JBoss Web Server, see the Red Hat JBoss Web Server Installation Guide.

Chapter 31. About Red Hat Decision Manager

Red Hat Process Automation Manager is made up of Business Central and KIE Server.

KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. KIE Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store).
Business Central is the graphical user interface where you create and manage business rules that KIE Server executes.

Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without needing to deploy it to an application server.

Red Hat JBoss Web Server is an enterprise ready web server designed for medium and large applications, based on Tomcat. Red Hat JBoss Web Server provides organizations with a single deployment platform for Java Server Pages (JSP) and Java Servlet technologies, PHP, and CGI.

On a Red Hat JBoss Web Server installation, you can install KIE Server and the headless Decision Manager controller. Alternatively, you can run the standalone Business Central JAR file.

The instructions in this document explain how to install Red Hat Decision Manager in a Red Hat JBoss Web Server instance.

For instructions on how to install Red Hat Decision Manager in other environments, see the following documents:

For information about supported components, see the following documents:

31.1. Red Hat Decision Manager components

Red Hat Decision Manager is made up of Business Central and KIE Server.

Business Central is the graphical user interface where you create and manage business rules. You can install Business Central in a Red Hat JBoss EAP instance or on the Red Hat OpenShift Container Platform (OpenShift).
Business Central is also available as a standalone JAR file. You can use the Business Central standalone JAR file to run Business Central without deploying it to an application server.
KIE Server is the server where rules and other artifacts are executed. It is used to instantiate and execute rules and solve planning problems. You can install KIE Server in a Red Hat JBoss EAP instance, in a Red Hat JBoss EAP cluster, on OpenShift, in an Oracle WebLogic server instance, in an IBM WebSphere Application Server instance, or as a part of Spring Boot application.
You can configure KIE Server to run in managed or unmanaged mode. If KIE Server is unmanaged, you must manually create and maintain KIE containers (deployment units). A KIE container is a specific version of a project. If KIE Server is managed, the Decision Manager controller manages the KIE Server configuration and you interact with the Decision Manager controller to create and maintain KIE containers.
On a Red Hat JBoss Web Server installation, you can install KIE Server and the headless Decision Manager controller. Alternatively, you can run the standalone Business Central JAR file.

31.2. Red Hat Decision Manager roles and users

This section describes Red Hat Decision Manager user roles.

Note

admin: Users with the admin role are the Business Central administrators. They can manage users and create, clone, and manage repositories. They have full access to make required changes in the application. Users with the admin role have access to all areas within Red Hat Decision Manager.
analyst: Users with the analyst role have access to all high-level features. They can model projects. However, these users cannot add contributors to spaces or delete spaces in the Design → Projects view. Access to the Deploy → Execution Servers view, which is intended for administrators, is not available to users with the analyst role. However, the Deploy button is available to these users when they access the Library perspective.
rest-all: Users with the rest-all role can access Business Central REST capabilities.
kie-server: Users with the kie-server role can access KIE Server REST capabilities.

Chapter 32. Downloading the Red Hat Decision Manager installation files

Download a Red Hat Decision Manager distribution that meets your environment and installation requirements.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download one of the following product distributions, depending on your preferred installation method:
Note
You only need to download one of these distributions.
- If you want to use the installer to install Red Hat Decision Manager on Red Hat JBoss Web Server, download Red Hat Decision Manager 7.10.0 Installer (rhdm-installer-7.10.0.jar). The installer graphical user interface guides you through the installation process.
- To install KIE Server on Red Hat JBoss Web Server using the deployable ZIP file, download the Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) file.
  The ZIP file does not require a graphical user interface.
- To run Business Central without needing to deploy it to an application server, download Red Hat Decision Manager 7.10.0 Business Central Standalone (rhdm-7.10.0-decision-central-standalone.jar).

Chapter 33. Using the Red Hat Decision Manager installer

This section describes how to install Business Central and the KIE Server using the installer JAR file. The JAR file is an executable file that installs Red Hat Decision Manager in an existing Red Hat JBoss Web Server 5.4.0 server installation. You can run the installer in interactive or command line interface (CLI) mode.

Next steps:

Follow the instructions in one of the following sections:

Section 33.1, “Using the installer in interactive mode”
Section 33.2, “Using the installer in CLI mode”

33.1. Using the installer in interactive mode

The installer for Red Hat Decision Manager is an executable JAR file. You can use it to install Red Hat Decision Manager in an existing Red Hat JBoss Web Server 5.4.0 server installation.

Note

For security reasons, you should run the installer as a non-root user.

Prerequisites

The Red Hat Decision Manager 7.10.0 Installer has been downloaded. For instructions, see Chapter 32, Downloading the Red Hat Decision Manager installation files.
A supported JDK is installed. For a list of supported JDKs, see Red Hat Decision Manager 7 Supported Configurations.
A backed-up Red Hat JBoss Web Server 5.4.0 server installation is available.
Sufficient user permissions to complete the installation are granted.
Note
Ensure that you are logged in with a user that has write permission for Tomcat.
The JAR binary is included in $PATH environment variable. On Red Hat Enterprise Linux, it is included in the java-$JAVA_VERSION-openjdk-devel package.
Note
Red Hat Decision Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix B, Business Central system properties.

Procedure

In a terminal window, navigate to the directory where you downloaded the installer JAR file and enter the following command:
```
java -jar rhdm-installer-7.10.0.jar
```
Note
When running the installer on Windows, you may be prompted to provide administrator credentials during the installation. To prevent this requirement, add the izpack.mode=privileged option to the installation command:
```
java -Dizpack.mode=privileged -jar
rhdm-installer-7.10.0.jar
```
Furthermore, when running the installer on a 32-bit Java virtual machine, you might encounter memory limitations. To prevent this issue, run this command:
```
java -XX:MaxHeapSize=4g -jar
rhdm-installer-7.10.0.jar
```
The graphical installer displays a splash screen and a license agreement page.
Click I accept the terms of this license agreement and click Next.
Specify the Red Hat JBoss Web Server 5.4.0 server home where you want to install Red Hat Decision Manager and click Next.
Select the components that you want to install and click Next.
You cannot install Business Central on Red Hat JBoss Web Server. You can only install it on Red Hat JBoss EAP. However, you can install KIE Server and the headless Decision Manager controller on Red Hat JBoss Web Server. The headless Decision Manager controller is used to manage KIE Server. Install the headless Decision Manager controller if you plan to manage multiple KIE Server instances.
Create a user and click Next. By default, if you install both Business Central and KIE Server in the same container the new user is given the admin, kie-server, and rest-all roles. If you install only KIE Server, the user is given the kie-server role. The kie-server role is required to access KIE Server REST capabilities.
Note
Make sure that the specified user name is not the same as an existing user, role, or group. For example, do not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character, but not & (ampersand).
Make a note of the user name and password. You will need them to access Business Central and KIE Server.
On the Installation Overview page, review the components that you will install and click Next to start the installation.
When the installation has completed, click Next.
When Processing finished appears at the top of the screen, click Next to complete the installation.
Optional: Click Generate Installation Script and Properties File to save the installation data in XML files, and then click Done.
The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file to repeat the Red Hat Decision Manager installation on multiple systems with the same type of server and the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command:
```
java -jar rhdm-installer-7.10.0.jar <path-to-auto.xml-file>
```

You have successfully installed Red Hat Decision Manager using the installer.

33.2. Using the installer in CLI mode

You can use the command-line interface (CLI) to run the Red Hat Decision Manager installer.

Note

For security reasons, you should run the installer as a non-root user.

Prerequisites

The Red Hat Decision Manager 7.10.0 Installer has been downloaded. For instructions, see Chapter 32, Downloading the Red Hat Decision Manager installation files.
A supported JDK is installed. For a list of supported JDKs, see Red Hat Decision Manager 7 Supported Configurations.
A backed-up Red Hat JBoss Web Server 5.4.0 server installation is available.
Sufficient user permissions to complete the installation are granted.
Note
Ensure that you are logged in with a user that has write permission for Tomcat.
The JAR binary is included in the $PATH environment variable. On Red Hat Enterprise Linux, it is included in the java-$JAVA_VERSION-openjdk-devel package.
Note
Red Hat Decision Manager is designed to work with UTF-8 encoding. If a different encoding system is used by the underlying JVM, unexpected errors might occur. To ensure UTF-8 is used by the JVM, use the "-Dfile.encoding=UTF-8" system property. For a list of system properties, see Appendix B, Business Central system properties.

Procedure

In a terminal window, navigate to the directory where you downloaded the installer file and enter the following command:
```
java -jar rhdm-installer-7.10.0.jar -console
```
The command-line interactive process will start and display the End-User License Agreement.
```
press 1 to continue, 2 to quit, 3 to redisplay.
```

Read the license agreement, enter 1, and press Enter to continue:

Specify the home directory of one of the following servers:  Red Hat JBoss EAP 7 or Red Hat JBoss Web Server 5. For more information, see https://access.redhat.com/articles/3354301[Red Hat Decision Manager 7 Supported Configurations].

Enter the parent directory of an existing Red Hat JBoss Web Server 5.4.0 installation.
The installer will verify the location of the installation at the location provided. Enter 1 to confirm and continue.
Follow the instructions in the installer to complete the installation.
Note
When you create the user name and password, make sure that the specified user name does not conflict with any known title of a role or a group. For example, if there is a role called admin, you should not create a user with the user name admin.
The password must have at least eight characters and must contain at least one number and one non-alphanumeric character (not including the character &).
Make a note of the user name and password. You will need them to access Business Central and KIE Server.

When the installation has completed, you will see this message:

Would you like to generate an automatic installation script and properties file?

Enter y to create XML files that contain the installation data, or n to complete the installation. If you enter y, you are prompted to specify a path for the XML files.
Enter a path or press the Enter key to accept the suggested path.
The installer generates two files. The auto.xml file automates future installations and the auto.xml.variables file stores user passwords and other sensitive variables. Use the auto.xml file on multiple systems to easily repeat a Red Hat Decision Manager installation on the same type of server with the same configuration as the original installation. If necessary, update the installpath parameter in the auto.xml file. To perform an installation using the XML file, enter the following command:
```
java -jar rhdm-installer-7.10.0.jar <path-to-auto.xml-file>
```
If you installed only KIE Server, repeat these steps to install the headless Decision Manager controller on a separate server.

Chapter 34. KIE Server ZIP file installation and configuration

You can install KIE Server using the rhdm-7.10.0-kie-server-jws.zip file available from the Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) file on the Customer Portal .

34.1. Installing KIE Server from ZIP files

KIE Server provides the runtime environment for business assets and accesses the data stored in the assets repository (knowledge store). You can use ZIP files to install KIE Server on an existing Red Hat JBoss Web Server 5.4.0 server instance.

Note

To use the installer JAR file to install KIE Server, see Chapter 33, Using the Red Hat Decision Manager installer.

The Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) file has been downloaded, as described in Chapter 32, Downloading the Red Hat Decision Manager installation files.
A backed-up Red Hat JBoss Web Server 5.4.0 server installation is available. The base directory of the Red Hat JBoss Web Server installation is referred to as JWS_HOME.
Sufficient user permissions to complete the installation are granted.

Procedure

Extract the rhdm-7.10.0-add-ons.zip file.
From the extracted rhdm-7.10.0-add-ons.zip file, extract the following files:
- rhdm-7.10.0-kie-server-jws.zip
- rhdm-7.10.0-decision-engine.zip
In the following instructions, the directory that contains the extracted rhdm-7.10.0-kie-server-jws.zip file is called JWS_TEMP_DIR and the directory that contains the extracted rhdm-7.10.0-decision-engine.zip file is called ENGINE_TEMP_DIR.
Copy the JWS_TEMP_DIR/rhdm-7.10.0-kie-server-jws/kie-server.war directory to the JWS_HOME/tomcat/webapps directory.
Note
Ensure the names of the Red Hat Decision Manager deployments you copy do not conflict with your existing deployments in the Red Hat JBoss Web Server instance.
Remove the .war extensions from the kie-server.war folder.
Move the kie-tomcat-integration-7.48.0.Final-redhat-00004.jar file from the ENGINE_TEMP_DIR directory to the JWS_HOME/tomcat/lib directory.
Move the jboss-jacc-api-<VERSION>.jar, slf4j-api-<VERSION>.jar, and slf4j-jdk14-<VERSION>.jar files from the ENGINE_TEMP_DIR/lib directory to the JWS_HOME/tomcat/lib directory, where <VERSION> is the version artifact file name, in the lib directory.
Add the following line to the <host> element in the JWS_HOME/tomcat/conf/server.xml file after the last Valve definition:
```
<Valve className="org.kie.integration.tomcat.JACCValve" />
```
Open the JWS_HOME/tomcat/conf/tomcat-users.xml file in a text editor.
Add users and roles to the JWS_HOME/tomcat/conf/tomcat-users.xml file. In the following example, <ROLE_NAME> is a role supported by Red Hat Decision Manager. <USER_NAME> and <USER_PWD> are the user name and password of your choice:
```
<role rolename="<ROLE_NAME>"/>
<user username="<USER_NAME>" password="<USER_PWD>" roles="<ROLE_NAME>"/>
```
If a user has more than one role, as shown in the following example, separate the roles with a comma:
```
<role rolename="admin"/>
<role rolename="kie-server"/>
<user username="rhdmUser" password="user1234" roles="admin,kie-server"/>
```

Complete one of the following steps in the JWS_HOME/tomcat/bin directory:

On Linux or UNIX, create the setenv.sh file with the following content:

CATALINA_OPTS="-Xmx1024m
 -Dorg.jboss.logging.provider=jdk
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true"

On Windows, add the following content to the setenv.bat file:

set CATALINA_OPTS="-Xmx1024m -Dorg.jboss.logging.provider=jdk -Dorg.jbpm.server.ext.disabled=true -Dorg.jbpm.ui.server.ext.disabled=true -Dorg.jbpm.case.server.ext.disabled=true

Chapter 35. Securing passwords with a keystore

Use Java Cryptography Extension KeyStore (JCEKS) for your keystore because it supports symmetric keys. Use KeyTool, which is part of the JDK installation, to create a new JCEKS.

Note

If KIE Server is not configured with JCEKS, KIE Server passwords are stored in system properties in plain text form.

Prerequisites

KIE Server is installed in Red Hat JBoss Web Server.
Java 8 or higher is installed.

Procedure

Open the JWS_HOME/tomcat/conf/tomcat-users.xml file in a text editor.
Add a KIE Server user with the kie-server role to the JWS_HOME/tomcat/conf/tomcat-users.xml file. In the following example, replace <USER_NAME> and <PASSWORD> with the user name and password of your choice.
```
<role rolename="kie-server"/>
<user username="<USER_NAME>" password="<PASSWORD>" roles="kie-server"/>
```
To use KeyTool to create a JCEKS, enter the following command in the Java 8 home directory:
```
$<JAVA_HOME>/bin/keytool -importpassword -keystore <KEYSTORE_PATH> -keypass <ALIAS_KEY_PASSWORD> -alias <PASSWORD_ALIAS> -storepass <KEYSTORE_PASSWORD> -storetype JCEKS
```
In this example, replace the following variables:
- <KEYSTORE_PATH>: The path where the keystore will be stored
- <KEYSTORE_PASSWORD>: The keystore password
- <ALIAS_KEY_PASSWORD>: The password used to access values stored with the alias
- <PASSWORD_ALIAS>: The alias of the entry to the process
When prompted, enter the password for the KIE Server user that you created.

To set the system properties, complete one of these steps in the JWS_HOME/tomcat/bin directory and replace the variables as described in the following table:

Note

If Business Central or the standalone controller are installed in separate instances from Red Hat JBoss Web Server, do not add the kie.keystore.key.server.alias and kie.keystore.key.server.pwd properties to CATALINA_OPTS.

On Linux or UNIX, create the setenv.sh file with the following content:

set CATALINA_OPTS="
-Dkie.keystore.keyStoreURL=<KEYSTORE_URL>
-Dkie.keystore.keyStorePwd=<KEYSTORE_PWD>
-Dkie.keystore.key.server.alias=<KEY_SERVER_ALIAS>
-Dkie.keystore.key.server.pwd=<KEY_SERVER_PWD>
-Dkie.keystore.key.ctrl.alias=<KEY_CONTROL_ALIAS>
-Dkie.keystore.key.ctrl.pwd=<KEY_CONTROL_PWD>

On Windows, add the following content to the setenv.bat file:

set CATALINA_OPTS="
-Dkie.keystore.keyStoreURL=<KEYSTORE_URL>
-Dkie.keystore.keyStorePwd=<KEYSTORE_PWD>
-Dkie.keystore.key.server.alias=<KEY_SERVER_ALIAS>
-Dkie.keystore.key.server.pwd=<KEY_SERVER_PWD>
-Dkie.keystore.key.ctrl.alias=<KEY_CONTROL_ALIAS>
-Dkie.keystore.key.ctrl.pwd=<KEY_CONTROL_PWD>

Table 35.1. System properties used to load a KIE Server JCEKS
System property	Placeholder	Description
`kie.keystore.keyStoreURL`	`<KEYSTORE_URL>`	URL for the JCEKS that you want to use, for example `file:///home/kie/keystores/keystore.jceks`
`kie.keystore.keyStorePwd`	`<KEYSTORE_PWD>`	Password for the JCEKS
`kie.keystore.key.server.alias`	`<KEY_SERVER_ALIAS>`	Alias of the key for REST services where the password is stored
`kie.keystore.key.server.pwd`	`<KEY_SERVER_PWD>`	Password of the alias for REST services with the stored password
`kie.keystore.key.ctrl.alias`	`<KEY_CONTROL_ALIAS>`	Alias of the key for default REST Process Automation Controller where the password is stored
`kie.keystore.key.ctrl.pwd`	`<KEY_CONTROL_PWD>`	Password of the alias for default REST Process Automation Controller with the stored password

Start KIE Server to verify the configuration.

Chapter 36. Verifying the KIE Server installation

Verify that KIE Server is installed correctly.

Prerequisites

KIE Server is installed and configured.

Procedure

To start KIE Server, enter one of the following commands in the JWS_HOME/tomcat/bin directory:
- On Linux or UNIX-based systems:
```
$ ./startup.sh
```
- On Windows:
```
startup.bat
```
After a few minutes, review the files in the JWS_HOME/tomcat/logs directory and correct any errors.
To verify that KIE Server is working correctly, enter http://localhost:8080/kie-server/services/rest/server in a web browser.
Enter the user name and password stored in the tomcat-users.xml file.

Chapter 37. Downloading and installing the headless Decision Manager controller

The Decision Manager controller is integrated with Business Central. If you install Business Central, use the Execution Server page to create and maintain KIE containers. However, if you do not install Business Central, you can install the headless Decision Manager controller and use the REST API or the KIE Server Java Client API to interact with it.

Prerequisites

The Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) file has been downloaded, as described in Chapter 32, Downloading the Red Hat Decision Manager installation files.
A Red Hat JBoss Web Server 5.4.0 server installation is available. The base directory of the Red Hat JBoss Web Server installation is referred to as JWS_HOME.
Sufficient user permissions to complete the installation are granted.

Procedure

Extract the rhdm-7.10.0-add-ons.zip file. The rhdm-7.10.0-controller-jws.zip file is in the extracted directory.
Extract the rhdm-7.10.0-controller-jws.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Copy the TEMP_DIR/rhdm-7.10.0-controller-jws.zip/controller.war directory to the JWS_HOME/tomcat/webapps directory.
Note
Ensure the names of the Red Hat Decision Manager deployments you copy do not conflict with your existing deployments in the Red Hat JBoss Web Server instance.
Remove the .war extensions from the controller.war folder.
Copy the contents of the TEMP_DIR/rhdm-7.10.0-controller-jws/SecurityPolicy/ directory to JWS_HOME/bin
When prompted to overwrite files, select Yes.
Add the kie-server role and user to the JWS_HOME/tomcat/conf/tomcat-users.xml file. In the following example, <USER_NAME> and <PASSWORD> are the user name and password of your choice:
```
<role rolename="kie-server"/>
<user username="<USER_NAME>" password="<PASSWORD>" roles="kie-server"/>
```

Complete one of the following tasks in the JWS_HOME/tomcat/bin directory of the instance running KIE Server:

On Linux or UNIX, create the setenv.sh file with the following content:

CATALINA_OPTS="-Xmx1024m
 -Dorg.jboss.logging.provider=jdk
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true
 -Dorg.kie.server.controller.user=<CONTROLLER_USER>
 -Dorg.kie.server.controller.pwd=<CONTROLLER_PWD>
 -Dorg.kie.server.id=<KIE_SERVER_ID>
 -Dorg.kie.server.location=http://<HOST>:<PORT>/kie-server/services/rest/server
 -Dorg.kie.server.controller=http://<HOST>:<PORT>/controller/rest/controller"

On Windows, add the following content to the setenv.bat file:

set CATALINA_OPTS= -Xmx1024m
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true
 -Dorg.kie.server.controller.user=<CONTROLLER_USER>
 -Dorg.kie.server.controller.pwd=<CONTROLLER_PWD>
 -Dorg.kie.server.id=<KIE_SERVER_ID>
 -Dorg.kie.server.location=http://<HOST>:<PORT>/kie-server/services/rest/server
 -Dorg.kie.server.controller=http://<CONTROLLER_HOST>:<CONTROLLER_PORT>/controller/rest/controller

In the preceding examples, replace the following variables:

Replace <CONTROLLER_USER> and <CONTROLLER_PWD> with the user name and password for the kie-server role that you defined earlier in this procedure.
Replace <KIE_SERVER_ID> with a unique identifier.
Replace <CONTROLLER_HOST>:<CONTROLLER_PORT> with the IP address (host and port) of the controller. If you use the same server for KIE Server and the controller, <CONTROLLER_HOST>:<CONTROLLER_PORT> is localhost:8080.

In the JWS_HOME/tomcat/bin directory of the instance running the headless Decision Manager controller, create a readable setenv.sh file with the following content, where <USERNAME> is the KIE Server user and <USER_PWD> is the password for that user:
CATALINA_OPTS="-Dorg.kie.server.user=<USERNAME> -Dorg.kie.server.pwd=<USER_PWD>"
To start the headless Decision Manager controller, enter one of the following commands in the JWS_HOME/tomcat/bin directory:
- On Linux or UNIX-based systems:
```
$ ./startup.sh
```
- On Windows:
```
startup.bat
```
After a few minutes, review the JWS_HOME/tomcat/logs directory and correct any errors.
To verify that the headless Decision Manager controller is working correctly, enter http://<CONTROLLER_HOST>:<CONTROLLER_PORT>/controller/rest/controller/management/servers in a web browser. If you use the same server for KIE Server and the controller, <CONTROLLER_HOST>:<CONTROLLER_PORT> is localhost:8080.
Enter the user name and password stored in the tomcat-users.xml file.

Chapter 38. Configuring and running standalone Business Central

Note

This JAR file is supported only when it is run on Red Hat Enterprise Linux.

Prerequisites

The Red Hat Decision Manager 7.10.0 Business Central Standalone (rhdm-7.10.0-decision-central-standalone.jar) and the Red Hat Decision Manager 7.10.0 Add Ons (rhdm-7.10.0-add-ons.zip) files have been downloaded from the Software Downloads page for Red Hat Decision Manager 7.10, as described in Chapter 32, Downloading the Red Hat Decision Manager installation files.

Procedure

Extract the downloaded rhdm-7.10.0-addons.zip to a temporary directory. This archive includes the rhdm-7.10.0-standalone-sample-configuration.zip file.
Extract the rhdm-7.10.0-standalone-sample-configuration.zip file to the directory that contains the rhdm-7.10.0-decision-central-standalone.jar file. The rhdm-7.10.0-standalone-sample-configuration.zip file contains the following sample configuration files:
- application-roles.properties
- application-users.properties
- sample-standalone-config.yml
  You can run the rhdm-7.10.0-decision-central-standalone.jar files with the sample data provided in the configuration files or you can customize the data for your requirements.
To customize the configuration data, complete the following steps:
1. Edit the application-users.properties file. Include an administrative user and if this Business Central instance will be a Decision Manager controller for KIE Server, include a Decision Manager controller user, for example:
```
rhdmAdmin=password1
```
2. Edit the application-roles.properties file to assign roles to the users that you included in the application-users.properties file, for example:
```
rhdmAdmin=admin
controllerUser=kie-server
```
  For more information, see Section 31.2, “Red Hat Decision Manager roles and users”.
3. Review the contents of the the sample-standalone-config.yml configuration file and update as required.

To run the Business Central standalone JAR file, enter the following command:

java -jar rhdm-7.10.0-decision-central-standalone.jar -s sample-standalone-config.yml

To set application properties when you run the JAR file, include the -D<PROPERTY>=<VALUE> parameter in the command, where <PROPERTY> is the name of a supported application property and <VALUE> is the property value:
```
java -jar rhdm-7.10.0-decision-central-standalone.jar -s sample-standalone-config.yml -D<PROPERTY>=<VALUE> -D<PROPERTY>=<VALUE>
```
For example, to run Business Central and connect to KIE Server as the user controllerUser, enter:
```
java -jar {PRODUCT_FILE}-{URL_COMPONENT_CENTRAL}-standalone.jar \
-s sample-standalone-config.yml \
-Dorg.kie.server.user=controllerUser
-Dorg.kie.server.pwd=controllerUser1234
```
Doing this enables you to deploy containers to KIE Server. See Appendix A, Business Central system properties for more information.

Chapter 39. Maven settings and repositories for Red Hat Decision Manager

For more information about Red Hat Decision Manager packaging and deployment options, see Packaging and deploying a Red Hat Decision Manager project.

39.1. Configuring Maven using the project configuration file (`pom.xml`)

To use Maven for building and managing your Red Hat Decision Manager projects, you must create and configure the POM file (pom.xml). This file holds configuration information for your project. For more information, see Apache Maven Project.

Procedure

Generate a Maven project. A pom.xml file is automatically generated when you create a Maven project.
Edit the pom.xml file to add more dependencies and new repositories.
Maven downloads all of the JAR files and the dependent JAR files from the Maven repository when you compile and package your project.

Find the schema for the pom.xml file at http://maven.apache.org/maven-v4_0_0.xsd. For more information about POM files, see Apache Maven Project POM.

39.2. Modifying the Maven settings file

Red Hat Decision Manager uses Maven settings.xml file to configure it’s Maven execution. You must create and activate a profile in the settings.xml file and declare the Maven repositories used by your Red Hat Decision Manager projects.

For information about the Maven settings.xml file, see the Apache Maven Project Setting Reference.

Procedure

In the settings.xml file, declare the repositories that your Red Hat Decision Manager projects use. Usually, this is either the online Red Hat Decision Manager Maven repository or the Red Hat Decision Manager Maven repository that you download from the Red Hat Customer Portal and any repositories for custom artifacts that you want to use.
Ensure that Business Central or KIE Server is configured to use the settings.xml file. For example, specify the kie.maven.settings.custom=<SETTINGS_FILE_PATH> property where <SETTINGS_FILE_PATH> is the path to the settings.xml file.
On Red Hat JBoss Web Server, for KIE Server add -Dkie.maven.settings.custom=<SETTINGS_FILE_PATH> to the CATALINA_OPTS section of the setenv.sh (Linux) or setenv.bat (Windows) file. For standalone Business Central, enter the following command:
```
java -jar rhpam-7.10.0-business-central-standalone.jar -s application-config.yaml -Dkie.maven.settings.custom=<SETTINGS_FILE_PATH>
```

39.3. Adding Maven dependencies for Red Hat Decision Manager

For more information about the Red Hat Business Automation BOM, see What is the mapping between Red Hat Decision Manager and the Maven library version?.

Procedure

Declare the Red Hat Business Automation BOM in the pom.xml file:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>com.redhat.ba</groupId>
   <artifactId>ba-platform-bom</artifactId>
   <version>7.10.0.redhat-00004</version>
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>
<dependencies>
<!-- Your dependencies -->
</dependencies>

Declare dependencies required for your project in the <dependencies> tag. After you import the product BOM into your project, the versions of the user-facing product dependencies are defined so you do not need to specify the <version> sub-element of these <dependency> elements. However, you must use the <dependency> element to declare dependencies which you want to use in your project.

For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:

For a basic Red Hat Decision Manager project, declare the following dependencies:

Embedded decision engine dependencies

<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-compiler</artifactId>
</dependency>

<!-- Dependency for persistence support. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-persistence-jpa</artifactId>
</dependency>

<!-- Dependencies for decision tables, templates, and scorecards.
For other assets, declare org.drools:business-central-models-* dependencies. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-decisiontables</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-templates</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-scorecards</artifactId>
</dependency>

<!-- Dependency for loading KJARs from a Maven repository using KieScanner. -->
<dependency>
  <groupId>org.kie</groupId>
  <artifactId>kie-ci</artifactId>
</dependency>

To use the KIE Server, declare the following dependencies:

Client application KIE Server dependencies

<dependency>
  <groupId>org.kie.server</groupId>
  <artifactId>kie-server-client</artifactId>
</dependency>

To create a remote client for Red Hat Decision Manager, declare the following dependency:

Client dependency

<dependency>
  <groupId>org.uberfire</groupId>
  <artifactId>uberfire-rest-client</artifactId>
</dependency>

When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as kjar and use org.kie:kie-maven-plugin to process the kjar packaging type located under the <project> element. In the following example, ${kie.version} is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:
```
<packaging>kjar</packaging>
<build>
 <plugins>
  <plugin>
   <groupId>org.kie</groupId>
   <artifactId>kie-maven-plugin</artifactId>
   <version>${kie.version}</version>
   <extensions>true</extensions>
  </plugin>
 </plugins>
</build>
```

39.4. Preparing a Maven mirror repository for offline use

Note

You do not need to complete this procedure if your Red Hat Decision Manager deployment is connected to the Internet.

Prerequisites

A computer that has outgoing access to the public Internet is available.

Procedure

On the computer that has an outgoing connection to the public Internet, complete the following steps:
Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Red Hat Decision Manager
- Version: 7.10
  1. Download and extract the Red Hat Process Automation Manager 7.10.0 Offliner Content List (rhdm-7.10.0-offliner.zip) product deliverable file.
  2. Extract the contents of the rhdm-7.10.0-offliner.zip file into any directory.
  3. Change to the directory and enter the following command:
    ./offline-repo-builder.sh offliner.txt
    This command creates the repository subdirectory and downloads the necessary artifacts into this subdirectory. This is the mirror repository.
    If a message reports that some downloads have failed, run the same command again. If downloads fail again, contact Red Hat support.
If you developed services outside of Business Central and they have additional dependencies, add the dependencies to the mirror repository. If you developed the services as Maven projects, you can use the following steps to prepare these dependencies automatically. Complete the steps on the computer that has an outgoing connection to the public Internet.
1. Create a backup of the local Maven cache directory (~/.m2/repository) and then clear the directory.
2. Build the source of your projects using the mvn clean install command.
3. For every project, enter the following command to ensure that Maven downloads all runtime dependencies for all the artifacts generated by the project:
```
mvn -e -DskipTests dependency:go-offline -f /path/to/project/pom.xml --batch-mode -Djava.net.preferIPv4Stack=true
```
  Replace /path/to/project/pom.xml with the path of the pom.xml file of the project.
4. Copy the contents of the local Maven cache directory (~/.m2/repository) to the repository subdirectory that was created.
Copy the contents of the repository subdirectory to a directory on the computer on which you deployed Red Hat Decision Manager. This directory becomes the offline Maven mirror repository.
Create and configure a settings.xml file for your Red Hat Decision Manager deployment as described in Section 39.2, “Modifying the Maven settings file”.
Make the following changes in the settings.xml file:
- Under the <profile> tag, if a <repositories> or <pluginRepositores> tag is missing, add the missing tags.
- Under <repositories> add the following content:
```
<repository>
  <id>offline-repository</id>
  <url>file:///path/to/repo</url>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
</repository>
```
  Replace /path/to/repo with the full path to the local Maven mirror repository directory.
- Under <pluginRepositories> add the following content:
```
<repository>
  <id>offline-plugin-repository</id>
  <url>file:///path/to/repo</url>
  <releases>
    <enabled>true</enabled>
  </releases>
  <snapshots>
    <enabled>false</enabled>
  </snapshots>
</repository>
```
  Replace /path/to/repo with the full path to the local Maven mirror repository directory.

Chapter 40. Importing projects from Git repositories

Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created.

Prerequisites

Red Hat Decision Manager projects exist in an external Git repository.
You have the credentials required for read access to that external Git repository.

Procedure

In Business Central, click Menu → Design → Projects.
Select or create the space into which you want to import the projects. The default space is MySpace.
To import a project, do one of the following:
- Click Import Project.
- Select Import Project from the drop-down list.
In the Import Project window, enter the URL and credentials for the Git repository that contains the projects that you want to import and click Import. The projects are added to the Business Central Git repository and are available from the current space.

Chapter 41. Integrating LDAP and SSL

With Red Hat Decision Manager you can integrate LDAP and SSL through RH-SSO. For more information, see the Red Hat Single Sign-On Server Administration Guide.

Appendix B. Business Central system properties

The Business Central system properties listed in this section are passed to standalone*.xml files.

Git directory

Use the following properties to set the location and name for the Business Central Git directory:

org.uberfire.nio.git.dir: Location of the Business Central Git directory.
org.uberfire.nio.git.dirname: Name of the Business Central Git directory. Default value: .niogit.
org.uberfire.nio.git.ketch: Enables or disables Git ketch.
org.uberfire.nio.git.hooks: Location of the Git hooks directory.

Git over HTTP

Use the following properties to configure access to the Git repository over HTTP:

org.uberfire.nio.git.proxy.ssh.over.http: Specifies whether SSH should use an HTTP proxy. Default value: false.
http.proxyHost: Defines the host name of the HTTP proxy. Default value: null.
http.proxyPort: Defines the host port (integer value) of the HTTP proxy. Default value: null.
http.proxyUser: Defines the user name of the HTTP proxy.
http.proxyPassword: Defines the user password of the HTTP proxy.
org.uberfire.nio.git.http.enabled: Enables or disables the HTTP daemon. Default value: true.
org.uberfire.nio.git.http.host: If the HTTP daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.http.hostname: If the HTTP daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.http.port: If the HTTP daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTP. The HTTP still relies on the servlet container. Default value: 8080.

Git over HTTPS

Use the following properties to configure access to the Git repository over HTTPS:

org.uberfire.nio.git.proxy.ssh.over.https: Specifies whether SSH uses an HTTPS proxy. Default value: false.
https.proxyHost: Defines the host name of the HTTPS proxy. Default value: null.
https.proxyPort: Defines the host port (integer value) of the HTTPS proxy. Default value: null.
https.proxyUser: Defines the user name of the HTTPS proxy.
https.proxyPassword: Defines the user password of the HTTPS proxy.
user.dir: Location of the user directory.
org.uberfire.nio.git.https.enabled: Enables or disables the HTTPS daemon. Default value: false
org.uberfire.nio.git.https.host: If the HTTPS daemon is enabled, it uses this property as the host identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.https.hostname: If the HTTPS daemon is enabled, it uses this property as the host name identifier. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: localhost.
org.uberfire.nio.git.https.port: If the HTTPS daemon is enabled, it uses this property as the port number. This is an informative property that is used to display how to access the Git repository over HTTPS. The HTTPS still relies on the servlet container. Default value: 8080.

JGit

org.uberfire.nio.jgit.cache.instances: Defines the JGit cache size.
org.uberfire.nio.jgit.cache.overflow.cleanup.size: Defines the JGit cache overflow cleanup size.
org.uberfire.nio.jgit.remove.eldest.iterations: Enables or disables whether to remove eldest JGit iterations.
org.uberfire.nio.jgit.cache.evict.threshold.duration: Defines the JGit evict threshold duration.
org.uberfire.nio.jgit.cache.evict.threshold.time.unit: Defines the JGit evict threshold time unit.

Git daemon

Use the following properties to enable and configure the Git daemon:

org.uberfire.nio.git.daemon.enabled: Enables or disables the Git daemon. Default value: true.
org.uberfire.nio.git.daemon.host: If the Git daemon is enabled, it uses this property as the local host identifier. Default value: localhost.
org.uberfire.nio.git.daemon.hostname: If the Git daemon is enabled, it uses this property as the local host name identifier. Default value: localhost
org.uberfire.nio.git.daemon.port: If the Git daemon is enabled, it uses this property as the port number. Default value: 9418.
org.uberfire.nio.git.http.sslVerify: Enables or disables SSL certificate checking for Git repositories. Default value: true.
Note
If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.

Git SSH

Use the following properties to enable and configure the Git SSH daemon:

org.uberfire.nio.git.ssh.enabled: Enables or disables the SSH daemon. Default value: true.
org.uberfire.nio.git.ssh.host: If the SSH daemon enabled, it uses this property as the local host identifier. Default value: localhost.
org.uberfire.nio.git.ssh.hostname: If the SSH daemon is enabled, it uses this property as local host name identifier. Default value: localhost.
org.uberfire.nio.git.ssh.port: If the SSH daemon is enabled, it uses this property as the port number. Default value: 8001.
Note
If the default or assigned port is already in use, a new port is automatically selected. Ensure that the ports are available and check the log for more information.
org.uberfire.nio.git.ssh.cert.dir: Location of the .security directory where local certificates are stored. Default value: Working directory.
org.uberfire.nio.git.ssh.idle.timeout: Sets the SSH idle timeout.
org.uberfire.nio.git.ssh.passphrase: Pass phrase used to access the public key store of your operating system when cloning git repositories with SCP style URLs. Example: git@github.com:user/repository.git.
org.uberfire.nio.git.ssh.algorithm: Algorithm used by SSH. Default value: RSA.
org.uberfire.nio.git.gc.limit: Sets the GC limit.
org.uberfire.nio.git.ssh.ciphers: A comma-separated string of ciphers. The available ciphers are aes128-ctr, aes192-ctr, aes256-ctr, arcfour128, arcfour256, aes192-cbc, aes256-cbc. If the property is not used, all available ciphers are loaded.
org.uberfire.nio.git.ssh.macs: A comma-separated string of message authentication codes (MACs). The available MACs are hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512. If the property is not used, all available MACs are loaded.
Note
If you plan to use RSA or any algorithm other than DSA, make sure you set up your application server to use the Bouncy Castle JCE library.

KIE Server nodes and Decision Manager controller

Use the following properties to configure the connections with the KIE Server nodes from the Decision Manager controller:

org.kie.server.controller: The URL is used to connect to the Decision Manager controller. For example, ws://localhost:8080/decision-central/websocket/controller.
org.kie.server.user: User name used to connect to the KIE Server nodes from the Decision Manager controller. This property is only required when using this Business Central installation as a Decision Manager controller.
org.kie.server.pwd: Password used to connect to the KIE Server nodes from the Decision Manager controller. This property is only required when using this Business Central installation as a Decision Manager controller.

Maven and miscellaneous

Use the following properties to configure Maven and other miscellaneous functions:

kie.maven.offline.force: Forces Maven to behave as if offline. If true, disables online dependency resolution. Default value: false.
Note
Use this property for Business Central only. If you share a runtime environment with any other component, isolate the configuration and apply it only to Business Central.
org.uberfire.gzip.enable: Enables or disables Gzip compression on the GzipFilter compression filter. Default value: true.
org.kie.workbench.profile: Selects the Business Central profile. Possible values are FULL or PLANNER_AND_RULES. A prefix FULL_ sets the profile and hides the profile preferences from the administrator preferences. Default value: FULL
org.appformer.m2repo.url: Business Central uses the default location of the Maven repository when looking for dependencies. It directs to the Maven repository inside Business Central, for example, http://localhost:8080/business-central/maven2. Set this property before starting Business Central. Default value: File path to the inner m2 repository.
appformer.ssh.keystore: Defines the custom SSH keystore to be used with Business Central by specifying a class name. If the property is not available, the default SSH keystore is used.
appformer.ssh.keys.storage.folder: When using the default SSH keystore, this property defines the storage folder for the user’s SSH public keys. If the property is not available, the keys are stored in the Business Central .security folder.
appformer.experimental.features: Enables the experimental features framework. Default value: false.
org.kie.demo: Enables an external clone of a demo application from GitHub.
org.uberfire.metadata.index.dir: Place where the Lucene .index directory is stored. Default value: Working directory.
org.uberfire.ldap.regex.role_mapper: Regex pattern used to map LDAP principal names to the application role name. Note that the variable role must be a part of the pattern as the application role name substitutes the variable role when matching a principle value and role name.
org.uberfire.sys.repo.monitor.disabled: Disables the configuration monitor. Do not disable unless you are sure. Default value: false.
org.uberfire.secure.key: Password used by password encryption. Default value: org.uberfire.admin.
org.uberfire.secure.alg: Crypto algorithm used by password encryption. Default value: PBEWithMD5AndDES.
org.uberfire.domain: Security-domain name used by uberfire. Default value: ApplicationRealm.
org.guvnor.m2repo.dir: Place where the Maven repository folder is stored. Default value: <working-directory>/repositories/kie.
org.guvnor.project.gav.check.disabled: Disables group ID, artifact ID, and version (GAV) checks. Default value: false.
org.kie.build.disable-project-explorer: Disables automatic build of a selected project in Project Explorer. Default value: false.
org.kie.builder.cache.size: Defines the cache size of the project builder. Default value: 20.
org.kie.library.assets_per_page: You can customize the number of assets per page in the project screen. Default value: 15.
org.kie.verification.disable-dtable-realtime-verification: Disables the real-time validation and verification of decision tables. Default value: false.

Decision Manager controller

Use the following properties to configure how to connect to the Decision Manager controller:

org.kie.workbench.controller: The URL used to connect to the Decision Manager controller, for example, ws://localhost:8080/kie-server-controller/websocket/controller.
org.kie.workbench.controller.user: The Decision Manager controller user. Default value: kieserver.
org.kie.workbench.controller.pwd: The Decision Manager controller password. Default value: kieserver1!.
org.kie.workbench.controller.token: The token string used to connect to the Decision Manager controller.

Java Cryptography Extension KeyStore (JCEKS)

Use the following properties to configure JCEKS:

kie.keystore.keyStoreURL: The URL used to load a Java Cryptography Extension KeyStore (JCEKS). For example, file:///home/kie/keystores/keystore.jceks.
kie.keystore.keyStorePwd: The password used for the JCEKS.
kie.keystore.key.ctrl.alias: The alias of the key for the default REST Decision Manager controller.
kie.keystore.key.ctrl.pwd: The password of the alias for the default REST Decision Manager controller.

Rendering

Use the following properties to switch between Business Central and KIE Server rendered forms:

org.jbpm.wb.forms.renderer.ext: Switches the form rendering between Business Central and KIE Server. By default, the form rendering is performed by Business Central. Default value: false.
org.jbpm.wb.forms.renderer.name: Enables you to switch between Business Central and KIE Server rendered forms. Default value: workbench.

Part V. Installing and configuring KIE Server on IBM WebSphere Application Server

As a system administrator, you can configure your IBM WebSphere Application Server for Red Hat KIE Server and install KIE Server on that IBM server instance.

Prerequisites

An IBM WebSphere Application Server instance version 9.0 or later is installed. For complete installation instructions, see the IBM WebSphere Application Server product page.
You have access to the WebSphere Integrated Solutions Console, usually at http://<HOST>:9060/ibm/console.

Chapter 42. KIE Server

KIE Server is the server where the rules and other artifacts for Red Hat Decision Manager are stored and run. KIE Server is a standalone built-in component that can be used to instantiate and execute rules through interfaces available for REST, Java Message Service (JMS), or Java client-side applications, and Red Hat Business Optimizer functionality through solvers.

Created as a web deployable WAR file, KIE Server can be deployed on any web container. The current version of the KIE Server is included with default extensions for both Red Hat Decision Manager and Red Hat Process Automation Manager.

KIE Server has a low footprint with minimal memory consumption and therefore can be deployed easily on a cloud instance. Each instance of this server can open and instantiate multiple containers, which enables you to execute multiple rule services in parallel.

KIE Server can be integrated with other application servers, such as Oracle WebLogic Server or IBM WebSphere Application Server, to streamline Red Hat Decision Manager application management.

Chapter 43. IBM WebSphere Application Server

Chapter 44. Installing and running IBM WebSphere Application Server

IBM WebSphere Application Server must be installed and running for you to apply many of the configurations that accommodate KIE Server. This section describes how to install and start IBM WebSphere.

For the most up-to-date and detailed installation instructions, see the IBM Knowledge Center.

Procedure

Download IBM Installation Manager version 1.8.5 or later from the IBM Installation Manager and Packaging Utility download links page. IBM Installation Manager is required for installing IBM WebSphere.
Extract the downloaded archive and run the following command as the root user in the new directory:
```
sudo ./install
```
The IBM Installation Manager opens.
Go to File → Preferences and click Add Repository.
In the Add Repository window, enter the repository URL for IBM WebSphere 9.0. You can find all the repository URLs in the Online product repositories for IBM WebSphere Application Server offerings page of the IBM Knowledge Center.
In your command terminal, navigate to the IBM WebSphere Application Server folder location that you specified during the installation.
Change to the /bin directory and run a command similar to the following example to create an IBM WebSphere profile, user name, and password. A profile defines the run time environment. The profile includes all the files that the server processes in the runtime environment and that you can change. The user is required for login.
```
sudo ./manageprofiles.sh -create -profileName testprofile -profilePath /profiles/testprofile  -adminUserName websphere -adminPassword password123
```
In your command terminal, navigate to the bin directory within the profile that you created (for example, /profiles/testprofile/bin) and run the following command to start the IBM WebSphere Application Server instance:
```
sudo ./startServer.sh <SERVER_NAME>
```
<SERVER_NAME> is the IBM WebSphere Application Server name defined in Servers → Server Types → IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console.
Open the following URL in a web browser:
```
http://<HOST>:9060/ibm/console
```
<HOST> is the system name or IP address of the target server.
For example, to start the WebSphere Integrated Solutions Console for a local instance of IBM WebSphere running on your system, enter the following URL in a web browser:
```
http://localhost:9060/ibm/console
```
When the login page of the WebSphere Integrated Solutions Console appears, enter your administrative credentials.

Chapter 45. Configuring IBM WebSphere Application Server for KIE Server

Before you deploy KIE Server with IBM WebSphere Application Server, you must configure system properties, security settings, JMS requirements, and other properties on IBM WebSphere. These configurations promote an optimal integration with KIE Server.

Prerequisites

IBM WebSphere Application Server is installed and running.
You are logged in to the WebSphere Integrated Solutions Console.

45.1. Enabling administrative security

You must enable administrative security in the WebSphere Integrated Solutions Console so that you have the required permissions to create users and groups.

Procedure

In the WebSphere Integrated Solutions Console, click Security → Global Security and ensure that the option Enable Application Security is selected. This may already be selected and overridden at the server level.
Click Security Configuration Wizard and click Next.
Select the repository that contains the user information. For example, select Federated repositories for local configurations.
Click Next
Enter the Primary administrative user name and Password.
Click Next and then click Finish.
Click Save in the Messages window to save your changes to the primary configuration.
Figure 45.1. Save security changes
In your command terminal, navigate to the IBM WebSphere Application Server /bin directory location that you specified during installation, and run the following commands to stop and restart IBM WebSphere to apply the security changes:
```
sudo ./stopServer.sh <SERVER_NAME>
```
```
sudo ./startServer.sh <SERVER_NAME>
```
<SERVER_NAME> is the IBM WebSphere Application Server name defined in Servers → Server Types → IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console.

45.2. Configuring Java Message Service (JMS)

The Java Message Service (JMS) is a Java API that KIE Server uses to exchange messages with other application servers such as Oracle WebLogic Server and IBM WebSphere Application Server. You must configure your application server to send and receive JMS messages through KIE Server to ensure proper collaboration between the two servers.

45.2.1. Create a service bus and add IBM WebSphere

You must create a service bus and add the IBM WebSphere Application Server as a member of it in order to use JMS.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Service Integration → Buses → New.
Enter a new bus name and clear the Bus Security option.
Click Next and then Finish to create the service bus.
Select the service bus that you have created.
Under Topology, click Bus Members → Add.
In the Add a New Bus Member wizard, choose the IBM WebSphere Application Server and the type of message store for persistence. You can also specify the properties of the message store.
Click Finish to add the new bus member.

45.2.2. Create JMS connection factories

To enable messaging with KIE Server, you must create certain JMS connection factories for sending and receiving messages.

Prerequisites

You have created a service bus for IBM WebSphere Application Server.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Resources → JMS → Connection Factories.
Select the correct scope and click New.
Select the Default Messaging Provider option and click OK.
For each of the following required connection factories, enter the name of the connection factory (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/cf/KIE.SERVER.REQUEST), and then select the service bus from the Bus Name drop-down list. Leave the default values for the remaining options.
Click Apply and Save to save the changes to the primary configuration, and repeat for each required factory.

45.2.2.1. JMS connection factories for KIE Server

The following are the required Java Message Service (JMS) connection factories that enable JMS messaging with KIE Server:

Table 45.1. Required JMS connection factories for KIE Server
Name	Default value	Used for
`KIE.SERVER.REQUEST`	`jms/cf/KIE.SERVER.REQUEST`	Sending all requests to KIE Server
`KIE.SERVER.RESPONSE`	`jms/cf/KIE.SERVER.RESPONSE`	Receiving all responses produced by KIE Server

45.2.3. Create JMS queues

JMS queues are the destination end points for point-to-point messaging. You must create certain JMS queues to enable JMS messaging with KIE Server.

Prerequisites

You have created a service bus for IBM WebSphere Application Server.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Resources → JMS → Queues.
Select the correct scope and click New.
Select the Default Messaging Provider option and click OK.
For each of the following required queues, enter the name of the queue (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/KIE.SERVER.REQUEST), and then select the service bus from the Bus Name drop-down list.
From the Queue Name drop-down list, select the Create Service Integration Bus Destination, enter a unique identifier, and select the bus member that you created previously.
Click Apply and Save to save the changes to the primary configuration, and repeat for each required queue.

45.2.3.1. JMS queues for KIE Server

The following are the required Java Message Service (JMS) queues that enable JMS messaging with KIE Server:

Table 45.2. Required JMS queues for KIE Server
Name	Default value	Used for
`KIE.SERVER.REQUEST`	`jms/KIE.SERVER.REQUEST`	Sending all requests to KIE Server
`KIE.SERVER.RESPONSE`	`jms/KIE.SERVER.RESPONSE`	Receiving all responses produced by KIE Server

45.2.4. Create JMS activation specifications

A JMS activation specification is required in order to bridge the queue and the message-driven bean that enables JMS.

Prerequisites

You have created a service bus for IBM WebSphere Application Server.
You have created JMS queues.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Resources → JMS → Activation Specifications.
Select the correct scope and click New.
Select the Default Messaging Provider option and click OK.
For each of the following required activation specifications, enter the name of the activation specification (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/activation/KIE.SERVER.REQUEST), and then select the service bus from the Bus Name drop-down list.
From the Destination Type drop-down list, select Queue and enter the name of the corresponding queue as a Destination lookup (for example, jms/KIE.SERVER.REQUEST).
Click Apply and Save to save the changes to the primary configuration, and repeat for each required activation specification.

45.2.4.1. JMS activation specifications for KIE Server

The following are the required Java Message Service (JMS) activation specifications that enable JMS messaging with KIE Server:

Table 45.3. Required JMS activation specifications for KIE Server
Name	Default value	Used for
`KIE.SERVER.REQUEST`	`jms/activation/KIE.SERVER.REQUEST`	Sending all requests to KIE Server
`KIE.SERVER.RESPONSE`	`jms/activation/KIE.SERVER.RESPONSE`	Receiving all responses produced by KIE Server

45.3. Setting system properties in IBM WebSphere Application Server

Set the system properties listed in this section on your IBM WebSphere Application Server before you deploy KIE Server.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Servers → Server Types → IBM WebSphere Application Servers.
In the list of application servers, choose the server on which you are going to deploy KIE Server.
Under the Server Infrastructure, click Java and Process Management → Process Definition.
Figure 45.2. WebSphere configuration page
Under Additional Properties, click Java Virtual Machine.
Figure 45.3. Process definition configuration page
This opens the configuration properties for the JVM that is used to start IBM WebSphere.
Set both the Initial heap size and Maximum heap size to 2048 and click Apply to increase the Java Virtual Machine (JVM) memory size. KIE Server has been tested with these values. If you do not increase the JVM memory size, IBM WebSphere Application Server freezes or causes deployment errors when deploying KIE Server.
Under Additional Properties, click Custom Properties.

Click New → Custom JVM Properties and add the following properties to IBM WebSphere:

Table 45.4. System properties for KIE Server
Name	Value	Description
`kie.server.jms.queues.response`	`jms/KIE.SERVER.RESPONSE`	The JNDI name of JMS queue for responses used by KIE Server.
`org.kie.server.domain`	`WSLogin`	JAAS `LoginContext` domain used to authenticate users when using JMS.
`org.jbpm.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.
`org.jbpm.ui.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.
`org.jbpm.case.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.
`org.jboss.logging.provider`	`jdk`	This property is only required where a `CA SiteMinder TAI (SMTAI)` is installed in the environment. Using this property forces Hibernate to use `JDK` instead of `log4j` for logging within Dashbuilder. `CA SiteMinder TAI (SMTAI)` contains an old version of `log4j`, which causes conflicts.

Click Save to save the changes to the primary configuration.

45.4. Stopping and restarting IBM WebSphere Application Server

After you have configured all required system properties in IBM WebSphere Application Server, stop and restart the IBM server to ensure that the configurations are applied.

Procedure

In your command terminal, navigate to the IBM WebSphere Application Server /bin directory location that you specified during installation, and run the following commands to stop and restart IBM WebSphere to apply the configuration changes:

sudo ./stopServer.sh <SERVER_NAME>

sudo ./startServer.sh <SERVER_NAME>

<SERVER_NAME> is the IBM WebSphere Application Server name defined in Servers → Server Types → IBM WebSphere Application Servers of the WebSphere Integrated Solutions Console.

Chapter 46. Installing and running KIE Server with IBM WebSphere Application Server

After you have configured all required system properties in IBM WebSphere Application Server, you can install KIE Server with IBM WebSphere to streamline Red Hat Decision Manager application management.

Prerequisites

An IBM WebSphere Application Server instance is configured as described in Chapter 45, Configuring IBM WebSphere Application Server for KIE Server.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 KIE Server for All Supported EE7 Containers.
Extract the rhdm-7.10.0-kie-server-ee7.zip archive to a temporary directory. In the following examples this directory is called TEMP_DIR.
Repackage the kie-server.war directory:
1. Navigate to the TEMP_DIR/rhdm-7.10.0-kie-server-ee7/kie-server.war directory.
2. Select the contents of the TEMP_DIR/rhdm-7.10.0-kie-server-ee7/kie-server.war directory and create the kie-server.zip file.
3. Rename kie-server.zip to kie-server.war. This is the file that you will use to deploy KIE Server.
4. Optional: Copy the new kie-server.war file to a location that is more convenient to deploy from.
In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications.
Click InstCll.
Navigate to the kie-server.war file that you repackaged and select it to upload.
Select Fast Path and click Next.
The Install New Application wizard opens.
Change the Application Name to kie-server and click Next.
Map the KIE Server modules to servers according to your specific requirements and click Next.
For Bind Listeners for Message-Driven Beans, select Activation Specification for both beans, enter jms/activation/KIE.SERVER.REQUEST in the Target Resource JNDI Name field, and enter the jms/cf/KIE.SERVER.REQUEST JNDI name for the KIE.SERVER.REQUEST connection factory.
In the Map Virtual Hosts for Web Modules section, keep the default values and click Next.
Set the context root to kie-server.
In the Metadata for Modules section, keep the default values and click Next.
Click Finish to install KIE Server and click Save to save the changes to the primary configuration.

46.1. Creating the KIE Server group and role

After KIE Server is installed, you must create the kie-server group and a user.

Prerequisites

KIE Server is installed on the IBM WebSphere Application Server instance.

Procedure

In the WebSphere Integrated Solutions Console, click Users and Groups → Manage Groups.
In the Manage Groups screen, click Create.
In the Create a Group screen, enter kie-server in the Group name box, then click Create.
To create a user to add to the kie-server group, click Users and Groups → Manage Users.
In the Create a User screen, complete the required information.
Click Group Membership.
In the Group Membership screen, click kie-server, move it to Mapped To, and click Close.
On the Create a User screen click Create.

46.2. Mapping the KIE Server group and role

After KIE Server is installed, you must map the kie-server role to the kie-server group in the WebSphere Integrated Solutions Console to run KIE Server.

Prerequisites

KIE Server is installed on the IBM WebSphere Application Server instance.
IBM WebSphere Application Server has the kie-server group with at least one user.

Procedure

In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications and select the newly installed kie-server application.
Under Detail Properties, click Security Role to User/Group Mapping.
Select the kie-server role and click Map Groups to search for the kie-server group.
Move the kie-server group from the Available list to the Selected list and click OK.
This mapping gives users in the IBM WebSphere Application Server kie-server group access to KIE Server.
Click Save to complete the mapping.

46.3. Configuring class loading for KIE Server

After KIE Server is installed, you must configure class loading to set parent classes to load last.

Procedure

Navigate to Applications → Application Types → WebSphere Enterprise Applications and click kie-server.
Click Class Loading and Update Detection under the Detail Properties heading on the left.
In the properties, change Class Loader Order to Classes loaded with local class loader first (parent last) and WAR Class Loader Policy to Single class loader for application.
Save the changes to the primary configuration.

46.4. Verifying the installation

After you install KIE Server and define the KIE Server group mapping, verify that the server is running.

Prerequisites

KIE Server is installed on the IBM WebSphere Application Server instance.
You have set all required system properties for the headless Decision Manager controller.
You have defined the KIE Server group mapping in IBM WebSphere Application Server.

Procedure

Navigate to the KIE Server URL http://<HOST>:<PORT>/kie-server to verify that the server is running, or send a GET request to http://<HOST>:<PORT>/kie-server/services/rest/server to check whether the KIE Server REST API responds.

<HOST> is the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.

<PORT> is the port of the KIE Server host, for example, 9060.

If KIE Server is not running, stop and restart the IBM WebSphere Application Server instance and try again to access the KIE Server URL or API.

Chapter 47. Installing and running the headless Decision Manager controller with IBM WebSphere Application Server

To use the KIE Server REST API or Java Client API to interact with KIE Server, install the headless Decision Manager controller with IBM WebSphere Application Server. The headless Decision Manager controller manages KIE Server configuration in a centralized way so that you can use the headless Decision Manager controller to create and maintain containers and perform other server-level tasks.

Note

Prerequisites

The IBM WebSphere Application Server instance is configured as described in Chapter 45, Configuring IBM WebSphere Application Server for KIE Server.
KIE Server is installed on the IBM WebSphere Application Server instance.
You have sufficient user permissions to complete the installation.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 Add-Ons.
Extract the downloaded rhdm-7.10.0-add-ons.zip file to a temporary directory.
Extract the rhdm-7.10.0-add-ons.zip file to a temporary directory. In the following examples this directory is called TEMP_DIR.
Extract the rhdm-7.10.0-add-ons/rhdm-7.10.0-controller-ee7.zip file.
Repackage the controller.war directory:
1. Navigate to the TEMP_DIR/rhdm-7.10.0-add-ons/rhdm-7.10.0-controller-ee7/controller.war directory.
2. Select the contents of the TEMP_DIR/rhdm-7.10.0-add-ons/rhdm-7.10.0-controller-ee7/controller.war directory and create the controller.zip file.
3. Rename controller.zip to controller.war. This is the file that you will use to deploy the headless Decision Manager controller.
4. Optional: Copy the new controller.war file to a location that is more convenient to deploy from.
In the WebSphere Integrated Solutions Console, navigate to Applications → Application Types → WebSphere Enterprise Applications.
Click Install.
Navigate to the controller.war file that you repackaged and select it to upload.
Select Fast Path and click Next.
The Install New Application wizard opens.
Change the Application Name to controller and click Next.
Map the headless Decision Manager controller modules to servers according to your specific requirements and click Next.
For Bind Listeners for Message-Driven Beans, select Activation Specification for both beans, enter jms/activation/KIE.SERVER.REQUEST in the Target Resource JNDI Name field, and enter the jms/cf/KIE.SERVER.REQUEST JNDI name for the KIE.SERVER.REQUEST connection factory.
In the Map Virtual Hosts for Web Modules section, keep the default values and click Next.
Set the context root to controller.
In the Metadata for Modules section, keep the default values and click Next.
Click Finish to install the headless Decision Manager controller and click Save to save the changes to the primary configuration.

47.1. Configuring class loading for the headless Decision Manager controller

After the headless Decision Manager controller is installed, you must configure KIE Server class loading to set parent classes to load last.

Procedure

Navigate to Applications → Application Types → WebSphere Enterprise Applications and click kie-server.
Click Class Loading and Update Detection under the Detail Properties heading on the left.
In the properties, change Class Loader Order to Classes loaded with local class loader first (parent last) and WAR Class Loader Policy to Single class loader for application.
Save the changes to the primary configuration.

47.2. Setting system properties for the headless Decision Manager controller

After you install the headless Decision Manager controller, set the system properties listed in this section on your application server or servers to enable proper interaction with the headless Decision Manager controller.

Note

For optimal results, install KIE Server and the headless Decision Manager controller on different servers in production environments. In development environments, you can install KIE Server and the headless Decision Manager controller on the same server. In either case, be sure to make these property changes on all application servers where the headless Decision Manager controller is installed.

Prerequisites

KIE Server and the headless Decision Manager controller are installed on the application server instance.

Procedure

Specify the following JVM property values on the application server instance where the headless Decision Manager controller is installed:

Table 47.1. Required properties for the headless Decision Manager controller
Name	Requirement
`org.kie.server.user`	A user with the `kie-server` role
`org.kie.server.pwd`	The password for the user specified in the `org.kie.server.user` property

Specify the following JVM property values on the application server instance where KIE Server is installed:

Table 47.2. Required properties for KIE Server when headless Decision Manager controller is installed
Name	Requirement
`org.kie.server.controller.user`	A user with the `kie-server` role
`org.kie.server.controller.pwd`	The password for the user specified for the `org.kie.server.controller.user` property
`org.kie.server.id`	The ID or name of the KIE Server installation, such as `rhdm700-decision-server-1`
`org.kie.server.location`	The URL of the KIE Server, `http://<HOST>:<PORT>/kie-server/services/rest/server`
`org.kie.server.controller`	The URL of the headless Decision Manager controller, `http://<HOST>:<PORT>/controller/rest/controller`

<HOST> is the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.

<PORT> is the port of the KIE Server host, for example, 7001.

47.3. Mapping the headless Decision Manager controller group and role

After the headless Decision Manager controller is installed, in the WebSphere Integrated Solutions Console, you must create the kie-server group and then map the kie-server role to the kie-server group.

Prerequisites

The headless Decision Manager controller is installed on the IBM WebSphere Application Server instance.

Procedure

In the WebSphere Integrated Solutions Console, create the kie-server group and a user for that group, as described in Creating the KIE Server group and role.
Navigate to Applications → Application Types → WebSphere Enterprise Applications and select the newly installed headless Decision Manager controller.
Under Detail Properties, click Security Role to User/Group Mapping.
Select the kie-server role and click Map Groups to search for the kie-server group.
Move the kie-server group from the Available list to the Selected list and click OK.
This mapping gives the previously created administrator user access to Decision Manager.
Click Save to complete the mapping.

47.4. Verifying the installation

After you install the headless Decision Manager controller and define the required system properties and role requirements on the application server, verify that the headless Decision Manager controller works correctly.

Prerequisites

KIE Server and the headless Decision Manager controller are installed on the application server instance.
You have set all required system properties and role requirements for the headless Decision Manager controller on the application server.

Procedure

In your command terminal, enter the following command to verify that the headless Decision Manager controller is working:

curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H  "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'

<HOST> is the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.

<PORT> is the port of the KIE Server host, for example, 7001.

<CONTROLLER> and <CONTROLLER_PWD> are the user credentials that you created in this section.

The command should return information about the KIE Server instance.

Note

Alternatively, you can use the KIE Server Java API Client to access the headless Decision Manager controller.

If the headless Decision Manager controller is not running, stop and restart the application server instance and try again to access the headless Decision Manager controller URL or API.

Chapter 48. Configuring an embedded decision engine in IBM WebSphere Application Server

A decision engine is a light-weight rule engine that enables you to execute your decisions and business processes. A decision engine can be part of a Red Hat Decision Manager application or it can be deployed as a service through OpenShift, Kubernetes, and Docker. You can embed a decision engine in a Red Hat Decision Manager application through the API or as a set of contexts and dependency injection (CDI) services.

If you intend to use an embedded engine with your Red Hat Decision Manager application, you must add Maven dependencies to your project by adding the Red Hat Business Automation bill of materials (BOM) files to the project’s pom.xml file. The Red Hat Business Automation BOM applies to a Red Hat Decision Manager. For more information about the Red Hat Business Automation BOM, see What is the mapping between Red Hat Decision Manager and the Maven library version?.

Procedure

Declare the Red Hat Business Automation BOM in the pom.xml file:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>com.redhat.ba</groupId>
   <artifactId>ba-platform-bom</artifactId>
   <version>7.10.0.redhat-00004</version>
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>
<dependencies>
<!-- Your dependencies -->
</dependencies>

Declare dependencies required for your project in the <dependencies> tag. After you import the product BOM into your project, the versions of the user-facing product dependencies are defined so you do not need to specify the <version> sub-element of these <dependency> elements. However, you must use the <dependency> element to declare dependencies which you want to use in your project.

For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:

Embedded decision engine dependencies

<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-compiler</artifactId>
</dependency>

<!-- Dependency for persistence support. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-persistence-jpa</artifactId>
</dependency>

<!-- Dependencies for decision tables, templates, and scorecards.
For other assets, declare org.drools:business-central-models-* dependencies. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-decisiontables</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-templates</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-scorecards</artifactId>
</dependency>

<!-- Dependency for loading KJARs from a Maven repository using KieScanner. -->
<dependency>
  <groupId>org.kie</groupId>
  <artifactId>kie-ci</artifactId>
</dependency>

To use the KIE Server, declare the following dependencies:

Client application KIE Server dependencies

<dependency>
  <groupId>org.kie.server</groupId>
  <artifactId>kie-server-client</artifactId>
</dependency>

To create a remote client for Red Hat Decision Manager, declare the following dependency:

Client dependency

<dependency>
  <groupId>org.uberfire</groupId>
  <artifactId>uberfire-rest-client</artifactId>
</dependency>

When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as kjar and use org.kie:kie-maven-plugin to process the kjar packaging type located under the <project> element. In the following example, ${kie.version} is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:
```
<packaging>kjar</packaging>
<build>
 <plugins>
  <plugin>
   <groupId>org.kie</groupId>
   <artifactId>kie-maven-plugin</artifactId>
   <version>${kie.version}</version>
   <extensions>true</extensions>
  </plugin>
 </plugins>
</build>
```

If you use a decision engine with persistence support in your project, you must declare the following hibernate dependencies in the dependencyManagement section of your pom.xml file by copying the version.org.hibernate-4ee7 property from the Red Hat Business Automation BOM file:

Hibernate dependencies in decision engine with persistence

<!-- hibernate dependencies -->
<dependencyManagement>
  <dependencies>
    <dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-entitymanager</artifactId>
    <version>${version.org.hibernate-4ee7}</version>
    </dependency>

    <dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-core</artifactId>
    <version>${version.org.hibernate-4ee7}</version>
    </dependency>
  </dependencies>
</dependencyManagement>

Chapter 49. Securing passwords with a keystore

Use Java Cryptography Extension KeyStore (JCEKS) for your keystore because it supports symmetric keys.

Note

If KIE Server is not configured with JCEKS, KIE Server passwords are stored in system properties in plain text form.

Prerequisites

KIE Server is installed in IBM WebSphere Application Server.
A KIE Server user with the kie-server role has been created, as described in Section 46.1, “Creating the KIE Server group and role”.
Java 8 or higher is installed.

Procedure

Create a JCEKS keystore.
When prompted, enter the password for the KIE Server user that you created.

Set the system properties listed in the following table:

Table 49.1. System properties used to load a KIE Server JCEKS
System property	Placeholder	Description
`kie.keystore.keyStoreURL`	`<KEYSTORE_URL>`	URL for the JCEKS that you want to use, for example `file:///home/kie/keystores/keystore.jceks`
`kie.keystore.keyStorePwd`	`<KEYSTORE_PWD>`	Password for the JCEKS
`kie.keystore.key.server.alias`	`<KEY_SERVER_ALIAS>`	Alias of the key for REST services where the password is stored
`kie.keystore.key.server.pwd`	`<KEY_SERVER_PWD>`	Password of the alias for REST services with the stored password
`kie.keystore.key.ctrl.alias`	`<KEY_CONTROL_ALIAS>`	Alias of the key for default REST Process Automation Controller where the password is stored
`kie.keystore.key.ctrl.pwd`	`<KEY_CONTROL_PWD>`	Password of the alias for default REST Process Automation Controller with the stored password

Start KIE Server to verify the configuration.

Chapter 50. Next steps

Part VI. Installing and configuring KIE Server on Oracle WebLogic Server

As a system administrator, you can configure your Oracle WebLogic Server for Red Hat KIE Server and install KIE Server on that Oracle server instance.

Prerequisites

An Oracle WebLogic Server instance version 12.2.1.3.0 or later is installed. For complete installation instructions, see the Oracle WebLogic Server product page.
You have access to the Oracle WebLogic Server Administration Console, usually at http://<HOST>:7001/console.

Chapter 51. KIE Server

KIE Server can be integrated with other application servers, such as Oracle WebLogic Server or IBM WebSphere Application Server, to streamline Red Hat Decision Manager application management.

Chapter 52. Oracle WebLogic Server

Oracle WebLogic Server is a Java EE application server that provides a standard set of APIs for creating distributed Java applications that can access a wide variety of services, such as databases, messaging services, and connections to external enterprise systems. User clients access these applications using web browser clients or Java clients.

Chapter 53. Installing and running Oracle WebLogic Server

Oracle WebLogic Server must be installed and running for you to apply many of the configurations that accommodate KIE Server. This section describes how to install and start Oracle WebLogic Server in a standalone Oracle WebLogic Server domain.

For the most up-to-date and detailed installation instructions, see the Oracle WebLogic Server product page.

Note

If you are already running an instance of Oracle WebLogic Server that uses the same listener port as the one to be used by the server you are starting, you must stop the first server before starting the second server.

Procedure

Download Oracle WebLogic Server 12.2.1.3.0 or later from the Oracle WebLogic Server Downloads page.
Sign in to the target system and verify that a certified JDK already exists on your system. The installer requires a certified JDK. For system requirements, see Oracle Fusion Middleware Systems Requirements and Specifications. To download the JDK, see the 'About JDK Requirements for an Oracle Fusion Middleware Installation' section in the Planning an Installation of Oracle Fusion Middleware.
Go to the directory where you downloaded the installation program.
Launch the installation program by running java -jar from the JDK directory on your system. See the following examples:
On UNIX-based operating systems:
```
/home/Oracle/jdk/jdk1.8.0_131/bin/java -jar fmw_12.2.1.3.0_wls_generic.jar
```
On Windows operating systems:
```
C:\Program Files\Java\jdk1.8.0_131\bin\java -jar fmw_12.2.1.3.0_wls_generic.jar
```
Be sure to replace the JDK location in these examples with the actual JDK location on your system.
Follow the installation wizard prompts to complete the installation.
After the installation is complete, navigate to the domain directory in the command terminal, WLS_HOME/user_projects/<DOMAIN_NAME>. For example:
```
WLS\user_projects\mydomain
```
Enter one of the following commands to start Oracle WebLogic Server:
On UNIX-based operating systems:
```
startWebLogic.sh
```
On Windows operating systems:
```
startWebLogic.cmd
```
The startup script displays a series of messages, and finally displays a message similar to the following:
```
<Dec 8, 2017 3:50:42 PM PDT> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
```
Open the following URL in a web browser:
```
http://<HOST>:<PORT>/console
```
<HOST> is the system name or IP address of the host server.
<PORT> is the address of the port on which the host server is listening for requests (7001 by default).
For example, to start the Administration Console for a local instance of Oracle WebLogic Server running on your system, enter the following URL in a web browser:
```
http://localhost:7001/console/
```
If you started the Administration Console using secure socket layer (SSL), you must add s after http, as follows: https://<HOST>:<PORT>/console
When the login page of the WebLogic Administration Console appears, enter your administrative credentials.

Chapter 54. Configuring Oracle WebLogic Server for KIE Server

Before you deploy KIE Server with Oracle WebLogic Server, you must configure system properties, security settings, JMS requirements, and other properties on Oracle WebLogic Server. These configurations promote an optimal integration with KIE Server.

Prerequisites

Oracle WebLogic Server is installed and running.
You are logged in to the WebLogic Administration Console.

54.1. Configuring the KIE Server group and users

You must assign users to a kie-server group in the WebLogic Administration Console to enable the container-managed authentication mechanisms in Oracle WebLogic Server.

Procedure

In the WebLogic Administration Console, click Security Realms.
Choose your desired security realm or click New to create a new security realm.
Navigate to Users and Groups → Groups → New and create the kie-server group.
Navigate to Users → New and create a new user.
Enter a user, such as server-user, and a password for this new user and click OK.
Important
Make sure that the selected user name does not conflict with any known title of a role or a group. For example, if there is a role called kie-server, then do not create a user with the user name kie-server.
Click the newly created user, then return to the Groups tab.
Use the selection tool to move the kie-server group from the Available field to the Chosen field, and click Save.

54.2. Configuring Java Message Service (JMS)

54.2.1. Create a JMS server

You must create a JMS server in order to use JMS.

Procedure

In the WebLogic Administration Console, navigate to Services → Messaging → JMS Servers.
Click New to create a new JMS server.
Enter a name for your JMS server and click Next.
Select the target server chosen for the KIE Server deployment.
Click Finish.

54.2.2. Create a JMS module

You must create a JMS module to store your JMS resources, such as connection factories and queues.

Prerequisites

You have created a JMS server.

Procedure

In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules.
Click New to create a module.
Enter a module name and click Next.
Select the target server chosen for the KIE Server deployment and click Finish.
Click the newly created module name and then click Subdeployments.
Click New to create a subdeployment for your module.
Give your subdeployment a name and click Next.
Select the check box to choose the previously created JMS server.
Click Finish to complete the subdeployment configuration.

54.2.3. Create JMS connection factories

To enable messaging with KIE Server, you must create certain JMS connection factories for sending and receiving messages.

Prerequisites

You have created a JMS server.
You have created a JMS module.

Procedure

In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules to see a list of JMS modules.
Select your previously created module and click New to create a new JMS resource.
Select Connection Factory and click Next.
For each of the following required connection factories, enter the name of the connection factory (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/cf/KIE.SERVER.REQUEST) and click Next. The connection factory automatically selects the servers assigned to the JMS Module as the default.
Click Finish to add the connection factory, and repeat for each required factory.

54.2.3.1. JMS connection factories for KIE Server

The following are the required Java Message Service (JMS) connection factories that enable JMS messaging with KIE Server:

Table 54.1. Required JMS connection factories for KIE Server
Name	Default value	Used for
`KIE.SERVER.REQUEST`	`jms/cf/KIE.SERVER.REQUEST`	Sending all requests to KIE Server
`KIE.SERVER.RESPONSE`	`jms/cf/KIE.SERVER.RESPONSE`	Receiving all responses produced by KIE Server

54.2.4. Create JMS queues

JMS queues are the destination end points for point-to-point messaging. You must create certain JMS queues to enable JMS messaging with KIE Server.

Prerequisites

You have created a JMS server.
You have created a JMS module.

Procedure

In the WebLogic Administration Console, navigate to Services → Messaging → JMS Modules to see the list of JMS modules.
Select your previously created module, then click New to create a new JMS resource.
Select Queue and click Next.
For each of the following required queues, enter the name of the queue (for example, KIE.SERVER.REQUEST) and the JNDI name (for example, jms/KIE.SERVER.REQUEST) and then click Next.
Choose the JMS module subdeployment that connects to the JMS server.
Click Finish to add the queue, and repeat for each required queue.

54.2.4.1. JMS queues for KIE Server

The following are the required Java Message Service (JMS) queues that enable JMS messaging with KIE Server:

Table 54.2. Required JMS queues for KIE Server
Name	Default value	Used for
`KIE.SERVER.REQUEST`	`jms/KIE.SERVER.REQUEST`	Sending all requests to KIE Server
`KIE.SERVER.RESPONSE`	`jms/KIE.SERVER.RESPONSE`	Receiving all responses produced by KIE Server

54.3. Setting system properties in Oracle WebLogic Server

Set the system properties listed in this section on your Oracle WebLogic Server before you deploy KIE Server.

Procedure

Set the following system property to increase the Java Virtual Machine (JVM) memory size:
```
USER_MEM_ARGS=-Xms512m -Xmx1024m
```
If you do not increase the JVM memory size, Oracle WebLogic Server freezes or causes deployment errors when deploying KIE Server.

Specify the following system properties for KIE Server on the Oracle WebLogic Server instance:

Table 54.3. System properties for KIE Server
Name	Value	Description
`kie.server.jms.queues.response`	`jms/KIE.SERVER.RESPONSE`	The JNDI name of JMS queue for responses used by the KIE Server.
`org.kie.server.domain`	`OracleDefaultLoginConfiguration`	JAAS `LoginContext` domain used to authenticate users when using JMS.
`org.jbpm.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.
`org.jbpm.ui.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.
`org.jbpm.case.server.ext.disabled`	`true`	Disables Business Central features, which are not supported in RHDM. If not set, KIE Server will work, but will show error messages during start up.

Set the same property values in the JAVA_OPTIONS environment variable:

JAVA_OPTIONS="-Dkie.server.jms.queues.response=jms/KIE.SERVER.RESPONSE
 -Dorg.kie.server.domain=OracleDefaultLoginConfiguration
 -Dorg.jbpm.server.ext.disabled=true
 -Dorg.jbpm.ui.server.ext.disabled=true
 -Dorg.jbpm.case.server.ext.disabled=true"

54.4. Stopping and restarting Oracle WebLogic Server

After you have configured all required system properties in Oracle WebLogic Server, stop and restart the Oracle server to ensure that the configurations are applied.

Procedure

In the WebLogic Administration Console, navigate to Change Center → Lock & Edit.
Under Domain Structure, click Environment → Servers → Control.
Select the server that you want to stop and click Shutdown.
Select When Work Completes to gracefully shut down the server or select Force Shutdown Now to stop the server immediately without completing ongoing tasks.
On the Server Life Cycle Assistant pane, click Yes to complete the shutdown.
After the shutdown is complete, navigate to the domain directory in the command terminal, WLS_HOME/user_projects/<DOMAIN_NAME>. For example:
```
WLS\user_projects\mydomain
```
Enter one of the following commands to restart Oracle WebLogic Server to apply the new configurations:
On UNIX-based operating systems:
```
startWebLogic.sh
```
On Windows operating systems:
```
startWebLogic.cmd
```
Open the Administration Console in a web browser (for example, http://localhost:7001/console/) and log in with your credentials.

Chapter 55. Installing KIE Server with Oracle WebLogic Server

After you have configured all required system properties in Oracle WebLogic Server, you can install KIE Server with Oracle WebLogic Server to streamline Red Hat Decision Manager application management.

Prerequisites

An Oracle WebLogic Server instance is configured as described in Chapter 54, Configuring Oracle WebLogic Server for KIE Server.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 KIE Server for All Supported EE7 Containers.
Extract the downloaded rhdm-7.10.0-kie-server-ee7.zip file to a temporary directory.
In the WebLogic Administration Console, navigate to Deployments to view all existing applications.
Click Install.
Navigate to the temporary directory where you downloaded and extracted the rhdm-7.10.0-kie-server-ee7.zip file, and go to rhdm-7.10.0-kie-server-ee7/kie-server.war.
Select the kie-server.war file and click Next to continue.
Select Install this deployment as an application as the targeting style and click Next.
Set the application name to kie-server and set the security model to DD Only. Leave the remaining options as default and click Next to continue.
In the Additional Configuration section, choose No, I will review the configuration later and click Finish.

55.1. Verifying the KIE Server installation on Oracle WebLogic Server

After you have installed KIE Server on Oracle WebLogic Server, verify that the installation was successful.

Prerequisites

An Oracle WebLogic Server instance is configured as described in Chapter 54, Configuring Oracle WebLogic Server for KIE Server.
KIE Server is installed as described in Chapter 55, Installing KIE Server with Oracle WebLogic Server.

Procedure

Enter the KIE Server URL http://<HOST>:<PORT>/kie-server/services/rest/server in a web browser.
Verify that KIE Server is running.
If KIE Server is not running, stop and restart the Oracle WebLogic Server instance and try again to access the KIE Server URL.

Chapter 56. Installing and running the headless Decision Manager controller with Oracle WebLogic Server

To use the KIE Server REST API or Java Client API to interact with KIE Server, install the headless Decision Manager controller with Oracle WebLogic Server. The headless Decision Manager controller manages KIE Server configuration in a centralized way so that you can use the headless Decision Manager controller to create and maintain containers and perform other server-level tasks.

Prerequisites

The Oracle WebLogic Server instance is configured as described in Chapter 54, Configuring Oracle WebLogic Server for KIE Server.
KIE Server is installed on the Oracle WebLogic Server instance.
You have sufficient user permissions to complete the installation.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options:
- Product: Decision Manager
- Version: 7.10
Download Red Hat Decision Manager 7.10.0 Add-Ons.
Extract the downloaded rhdm-7.10.0-add-ons.zip file to a temporary directory.
In the WebLogic Administration Console, navigate to Security Realms → Users and Groups.
In the kie-server group that you created previously, create a user for the headless Decision Manager controller, such as controller, and a password for this new user and click OK. For more information about creating groups and users, see Section 54.1, “Configuring the KIE Server group and users”.
Navigate to Deployments to view all existing applications.
Click Install.
Navigate to the temporary directory where you downloaded and extracted the rhdm-7.10.0-add-ons.zip file, and go to rhdm-7.10.0-add-ons/rhdm-7.10.0-controller-ee7.zip/controller.war.
Select the controller.war file and click Next to continue.
Select Install this deployment as an application as the targeting style and click Next.
Keep the application name as controller and set the security model to DD Only. Leave the remaining options as default and click Next to continue.
In the Additional Configuration section, choose No, I will review the configuration later and click Finish.

56.1. Setting system properties for the headless Decision Manager controller

Note

Prerequisites

KIE Server and the headless Decision Manager controller are installed on the application server instance.

Procedure

Specify the following JVM property values on the application server instance where the headless Decision Manager controller is installed:

Table 56.1. Required properties for the headless Decision Manager controller
Name	Requirement
`org.kie.server.user`	A user with the `kie-server` role
`org.kie.server.pwd`	The password for the user specified in the `org.kie.server.user` property

Specify the following JVM property values on the application server instance where KIE Server is installed:

Table 56.2. Required properties for KIE Server when headless Decision Manager controller is installed
Name	Requirement
`org.kie.server.controller.user`	A user with the `kie-server` role
`org.kie.server.controller.pwd`	The password for the user specified for the `org.kie.server.controller.user` property
`org.kie.server.id`	The ID or name of the KIE Server installation, such as `rhdm700-decision-server-1`
`org.kie.server.location`	The URL of the KIE Server, `http://<HOST>:<PORT>/kie-server/services/rest/server`
`org.kie.server.controller`	The URL of the headless Decision Manager controller, `http://<HOST>:<PORT>/controller/rest/controller`

<HOST> is the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.

<PORT> is the port of the KIE Server host, for example, 7001.

56.2. Verifying the installation

Prerequisites

KIE Server and the headless Decision Manager controller are installed on the application server instance.
You have set all required system properties and role requirements for the headless Decision Manager controller on the application server.

Procedure

In your command terminal, enter the following command to verify that the headless Decision Manager controller is working:

curl -X GET "http://<HOST>:<PORT>/controller/rest/controller/management/servers" -H  "accept: application/xml" -u '<CONTROLLER>:<CONTROLLER_PWD>'

<HOST> is the ID or name of the KIE Server host, for example, localhost or 192.7.8.9.

<PORT> is the port of the KIE Server host, for example, 7001.

<CONTROLLER> and <CONTROLLER_PWD> are the user credentials that you created in this section.

The command should return information about the KIE Server instance.

Note

Alternatively, you can use the KIE Server Java API Client to access the headless Decision Manager controller.

If the headless Decision Manager controller is not running, stop and restart the application server instance and try again to access the headless Decision Manager controller URL or API.

Chapter 57. Configuring an embedded decision engine in Oracle WebLogic Server

Procedure

Declare the Red Hat Business Automation BOM in the pom.xml file:

<dependencyManagement>
 <dependencies>
  <dependency>
   <groupId>com.redhat.ba</groupId>
   <artifactId>ba-platform-bom</artifactId>
   <version>7.10.0.redhat-00004</version>
   <type>pom</type>
   <scope>import</scope>
  </dependency>
 </dependencies>
</dependencyManagement>
<dependencies>
<!-- Your dependencies -->
</dependencies>

For a basic Red Hat Decision Manager project, declare the following dependencies, depending on the features that you want to use:

Embedded decision engine dependencies

<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-compiler</artifactId>
</dependency>

<!-- Dependency for persistence support. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-persistence-jpa</artifactId>
</dependency>

<!-- Dependencies for decision tables, templates, and scorecards.
For other assets, declare org.drools:business-central-models-* dependencies. -->
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-decisiontables</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-templates</artifactId>
</dependency>
<dependency>
  <groupId>org.drools</groupId>
  <artifactId>drools-scorecards</artifactId>
</dependency>

<!-- Dependency for loading KJARs from a Maven repository using KieScanner. -->
<dependency>
  <groupId>org.kie</groupId>
  <artifactId>kie-ci</artifactId>
</dependency>

To use the KIE Server, declare the following dependencies:

Client application KIE Server dependencies

<dependency>
  <groupId>org.kie.server</groupId>
  <artifactId>kie-server-client</artifactId>
</dependency>

To create a remote client for Red Hat Decision Manager, declare the following dependency:

Client dependency

<dependency>
  <groupId>org.uberfire</groupId>
  <artifactId>uberfire-rest-client</artifactId>
</dependency>

When creating a JAR file that includes assets, such as rules and process definitions, specify the packaging type for your Maven project as kjar and use org.kie:kie-maven-plugin to process the kjar packaging type located under the <project> element. In the following example, ${kie.version} is the Maven library version listed in What is the mapping between Red Hat Decision Manager and the Maven library version?:
```
<packaging>kjar</packaging>
<build>
 <plugins>
  <plugin>
   <groupId>org.kie</groupId>
   <artifactId>kie-maven-plugin</artifactId>
   <version>${kie.version}</version>
   <extensions>true</extensions>
  </plugin>
 </plugins>
</build>
```

Hibernate dependencies in decision engine with persistence

<!-- hibernate dependencies -->
<dependencyManagement>
  <dependencies>
    <dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-entitymanager</artifactId>
    <version>${version.org.hibernate-4ee7}</version>
    </dependency>

    <dependency>
    <groupId>org.hibernate</groupId>
    <artifactId>hibernate-core</artifactId>
    <version>${version.org.hibernate-4ee7}</version>
    </dependency>
  </dependencies>
</dependencyManagement>

Chapter 58. Securing passwords with a keystore

Use Java Cryptography Extension KeyStore (JCEKS) for your keystore because it supports symmetric keys. Use KeyTool, which is part of the JDK installation, to create a new JCEKS.

Note

If KIE Server is not configured with JCEKS, KIE Server passwords are stored in system properties in plain text form.

Prerequisites

KIE Server is installed in Oracle WebLogic Server.
A KIE Server user with the kie-server role has been created, as described in Section 54.1, “Configuring the KIE Server group and users”.
Java 8 or higher is installed.

Procedure

To use KeyTool to create a JCEKS, enter the following command in the Java 8 home directory:
```
$<JAVA_HOME>/bin/keytool -importpassword -keystore <KEYSTORE_PATH> -keypass <ALIAS_KEY_PASSWORD> -alias <PASSWORD_ALIAS> -storepass <KEYSTORE_PASSWORD> -storetype JCEKS
```
In this example, replace the following variables:
- <KEYSTORE_PATH>: The path where the keystore will be stored
- <KEYSTORE_PASSWORD>: The keystore password
- <ALIAS_KEY_PASSWORD>: The password used to access values stored with the alias
- <PASSWORD_ALIAS>: The alias of the entry to the process
When prompted, enter the password for the KIE Server user that you created.

Set the system properties listed in the following table:

Table 58.1. System properties used to load a KIE Server JCEKS
System property	Placeholder	Description
`kie.keystore.keyStoreURL`	`<KEYSTORE_URL>`	URL for the JCEKS that you want to use, for example `file:///home/kie/keystores/keystore.jceks`
`kie.keystore.keyStorePwd`	`<KEYSTORE_PWD>`	Password for the JCEKS
`kie.keystore.key.server.alias`	`<KEY_SERVER_ALIAS>`	Alias of the key for REST services where the password is stored
`kie.keystore.key.server.pwd`	`<KEY_SERVER_PWD>`	Password of the alias for REST services with the stored password
`kie.keystore.key.ctrl.alias`	`<KEY_CONTROL_ALIAS>`	Alias of the key for default REST Process Automation Controller where the password is stored
`kie.keystore.key.ctrl.pwd`	`<KEY_CONTROL_PWD>`	Password of the alias for default REST Process Automation Controller with the stored password

Start KIE Server to verify the configuration.

Chapter 59. Next steps

Part VII. Patching and upgrading Red Hat Decision Manager 7.10

As a Red Hat Decision Manager user, you can apply updates to Red Hat Decision Manager as they become available in the Red Hat Customer Portal to keep your Red Hat Decision Manager distribution current with the latest enhancements and fixes. Red Hat provides update tools and product notifications for new product releases so you can more readily apply helpful updates to Red Hat Decision Manager and KIE Server.

Prerequisites

You have a Red Hat Customer Portal account.
Red Hat Decision Manager 7.10 is installed. For installation options, see Planning a Red Hat Decision Manager installation.
Note
If you are using Red Hat Decision Manager 7.9 and you want to upgrade to Red Hat Decision Manager 7.10, see Patching and upgrading Red Hat Decision Manager 7.9 .

Chapter 60. Red Hat Decision Manager versioning

Red Hat Decision Manager versions are designated with a numerical Major.Minor.Patch format, such as 7.10.1. In this example, the major release is 7.x.x, the minor release is 7.10.x, and the patch release is 7.10.1. Major releases often require data migration, while minor release upgrades and patch updates are typically managed with update tools provided with the Red Hat Decision Manager release artifacts.

The following are the general types of releases for Red Hat Decision Manager:

Major release migrations

For example migration instructions, see Migrating from Red Hat JBoss BRMS 6.4 to Red Hat Decision Manager 7.0.

Minor release upgrades

Minor releases of Red Hat Decision Manager include enhancements, security updates, and bug fixes. Data migration may be required when an application is moved from one minor release to another minor release, such as from Red Hat Decision Manager 7.9.x to 7.10. Automated update tools are often provided with both patch updates and new minor versions of Red Hat Decision Manager to facilitate updating certain components of Red Hat Decision Manager, such as Business Central, KIE Server, and the headless Decision Manager controller. Other Red Hat Decision Manager artifacts, such as the decision engine and standalone Business Central, are released as new artifacts with each minor release and you must re-install them to apply the update.

Before you upgrade to a new minor release, apply the latest patch update to your current version of Red Hat Decision Manager to ensure that the minor release upgrade is successful.

Patch updates

Patch updates of Red Hat Decision Manager include the latest security updates and bug fixes. Scheduled patch updates contain all previously released patch updates for that minor version of the product, so you do not need to apply each patch update incrementally in order to apply the latest update. For example, you can update Red Hat Decision Manager 7.9.0 or 7.9.1 to Red Hat Decision Manager 7.9.2. However, for optimal Red Hat Decision Manager performance, apply product updates as they become available. Occasionally, unscheduled patch updates may be released outside the normal update cycle of the existing product. These may include security or other updates provided by Red Hat Global Support Services (GSS) to fix specific issues, and may not be cumulative updates.

For information about enabling product notifications, see Chapter 61, Enabling Red Hat Decision Manager notifications in the Red Hat Customer Portal.

Chapter 61. Enabling Red Hat Decision Manager notifications in the Red Hat Customer Portal

You can enable notifications in the Red Hat Customer Portal to receive Red Hat Decision Manager updates and announcements. These notifications inform you of updated or added documentation, product releases, and patch updates related to Red Hat Decision Manager. With notifications enabled, you can more readily apply product updates to Red Hat Decision Manager as they become available in the Red Hat Customer Portal to keep your Red Hat Decision Manager distribution current with the latest enhancements and fixes.

Prerequisites

You have a Red Hat Customer Portal account and are logged in.

Procedure

In the top-right corner of the Red Hat Customer Portal window, click your profile name and click Notifications.
Select the Notifications tab and click Manage Notifications.
Next to Follow, select Products from the drop-down menu, and then select Red Hat Decision Manager from the next drop-down menu that appears.
Click Save Notification to finish.

You can add notifications for any other products as needed in the same way.

Chapter 62. Applying patch updates and minor release upgrades to Red Hat Decision Manager

You can use the same automated update tool to apply both patch updates and minor release upgrades to Red Hat Decision Manager 7.10. Patch updates of Red Hat Decision Manager, such as an update from version 7.10 to 7.10.1, include the latest security updates and bug fixes. Minor release upgrades of Red Hat Decision Manager, such as an upgrade from version 7.9.x to 7.10, include enhancements, security updates, and bug fixes.

Note

Only updates for Red Hat Decision Manager are included in Red Hat Decision Manager update tools. Updates to Red Hat JBoss EAP must be applied using Red Hat JBoss EAP patch distributions. For more information about Red Hat JBoss EAP patching, see the Red Hat JBoss EAP patching and upgrading guide.

Prerequisites

Your Red Hat Decision Manager and KIE Server instances are not running. Do not apply updates while you are running an instance of Red Hat Decision Manager or KIE Server.

Procedure

Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options.
If you are upgrading to a new minor release of Red Hat Decision Manager, such as an upgrade from version 7.9.x to 7.10, first apply the latest patch update to your current version of Red Hat Decision Manager and then follow this procedure again to upgrade to the new minor release.
Click Patches, download the Red Hat Decision Manager [VERSION] Update Tool, and extract the downloaded rhdm-$VERSION-update.zip file to a temporary directory.
This update tool automates the update of certain components of Red Hat Decision Manager, such as Business Central, KIE Server, and the headless Decision Manager controller. Use this update tool first to apply updates and then install any other updates or new release artifacts that are relevant to your Red Hat Decision Manager distribution.
If you want to preserve any files from being updated by the update tool, navigate to the extracted rhdm-$VERSION-update folder, open the blacklist.txt file, and add the relative paths to the files that you do not want to be updated.
When a file is listed in the blacklist.txt file, the update script does not replace the file with the new version but instead leaves the file in place and in the same location adds the new version with a .new suffix. If you block files that are no longer being distributed, the update tool creates an empty marker file with a .removed suffix. You can then choose to retain, merge, or delete these new files manually.
Example files to be excluded in blacklist.txt file:
```
WEB-INF/web.xml  // Custom file
styles/base.css  // Obsolete custom file kept for record
```
The contents of the blocked file directories after the update:
```
$ ls WEB-INF
web.xml web.xml.new
```
```
$ ls styles
base.css base.css.removed
```
In your command terminal, navigate to the temporary directory where you extracted the rhdm-$VERSION-update.zip file and run the apply-updates script in the following format:
Important
Make sure that your Red Hat Decision Manager and KIE Server instances are not running before you apply updates. Do not apply updates while you are running an instance of Red Hat Decision Manager or KIE Server.
On Linux or Unix-based systems:
```
$ ./apply-updates.sh $DISTRO_PATH $DISTRO_TYPE
```
On Windows:
```
$ .\apply-updates.bat $DISTRO_PATH $DISTRO_TYPE
```
The $DISTRO_PATH portion is the path to the relevant distribution directory and the $DISTRO_TYPE portion is the type of distribution that you are updating with this update.
The following distribution types are supported in Red Hat Decision Manager update tool:
- rhdm-decision-central-eap7-deployable: Updates Business Central (decision-central.war)
- rhdm-kie-server-ee8: Updates KIE Server (kie-server.war)
- rhdm-kie-server-jws: Updates KIE Server on Red Hat JBoss Web Server (kie-server.war)
- rhdm-controller-ee7: Updates the headless Decision Manager controller (controller.war)
- rhdm-controller-jws: Updates the headless Decision Manager controller on Red Hat JBoss Web Server (controller.war)
  Example update to Business Central and KIE Server for a full Red Hat Decision Manager distribution on Red Hat JBoss EAP:
```
./apply-updates.sh ~EAP_HOME/standalone/deployments/decision-central.war rhdm-decision-central-eap7-deployable

./apply-updates.sh ~EAP_HOME/standalone/deployments/kie-server.war rhdm-kie-server-ee8
```
  Example update to headless Decision Manager controller, if used:
```
./apply-updates.sh ~EAP_HOME/standalone/deployments/controller.war rhdm-controller-ee7
```
  The update script creates a backup folder in the extracted rhdm-$VERSION-update folder with a copy of the specified distribution, and then proceeds with the update.
After the update tool completes, return to the Software Downloads page of the Red Hat Customer Portal where you downloaded the update tool and install any other updates or new release artifacts that are relevant to your Red Hat Decision Manager distribution.
For files that already exist in your Red Hat Decision Manager distribution, such as .jar files for the decision engine or other add-ons, replace the existing version of the file with the new version from the Red Hat Customer Portal.
If you use the standalone Red Hat Decision Manager 7.10.0 Maven Repository artifact (rhdm-7.10.0-maven-repository.zip), such as in air-gap environments, download Red Hat Decision Manager 7.10.x Maven Repository and extract the downloaded rhdm-7.10.x-maven-repository.zip file to your existing ~/maven-repository directory to update the relevant contents.
Example Maven repository update:
```
$ unzip -o rhdm-7.10.x-maven-repository.zip 'rhba-7.10.1.GA-maven-repository/maven-repository/*' -d /tmp/rhbaMavenRepoUpdate

$ mv /tmp/rhbaMavenRepoUpdate/rhba-7.10.0.GA-maven-repository/maven-repository/ $REPO_PATH/
```
Note
You can remove the /tmp/rhbaMavenRepoUpdate folder after you complete the update.
After you finish applying all relevant updates, start Red Hat Decision Manager and KIE Server and log in to Business Central.
Verify that all project data is present and accurate in Business Central, and in the top-right corner of the Business Central window, click your profile name and click About to verify the updated product version number.
If you encounter errors or notice any missing data in Business Central, you can restore the contents in the backup folder within the rhdm-$VERSION-update folder to revert the update tool changes. You can also re-install the relevant release artifacts from your previous version of Red Hat Decision Manager in the Red Hat Customer Portal. After restoring your previous distribution, you can try again to run the update.

Chapter 63. Additional resources

Appendix C. Versioning information

Documentation last updated on Monday, March 01, 2021.

Appendix D. Contact information

Red Hat Decision Manager documentation team: brms-docs@redhat.com

Legal Notice

The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide 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 States and 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 States and/or other countries.

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

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

The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries 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.