Red Hat Training
A Red Hat training course is available for Red Hat Decision Manager
Chapter 8. Managed Decision Server
A managed instance requires an available controller to start the Decision Server.
A controller manages the Decision Server configuration in a centralized way. Each controller can manage multiple configurations at once, and there can be multiple controllers in the environment. Managed Decision Server can be configured with a list of controllers, but will only connect to one at a time.
Controllers should be synchronized to ensure that the same set of configuration is provided to the server, regardless of the controller to which it connects.
When the Decision Server is configured with a list of controllers, it will attempt to connect to each of them at startup until a connection is successfully established with one of them. If a connection cannot be established, the server will not start, even if there is a local storage available with configuration. This ensures consistence and prevents the server from running with redundant configuration.
To run the Decision Server in standalone mode without connecting to controllers, see Section 8.2, “Unmanaged Decision Server”.
8.1. Configuring Decision Server Managed by Decision Central
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.
Use this procedure to configure Decision Central to manage a Decision Server instance.
Prerequisite
Users with the following roles exist:
-
In Decision Central, a user with the role
rest-all
. -
On the Decision Server, a user with the role
kie-server
.
In production environments, use two distinct users, each with one role. In this sample situation, we use only one user named controllerUser
that has both the rest-all
and the kie-server
roles.
Procedure
Set the following JVM properties.
The location of Decision Central and the Decision Server may be different. In such case, ensure you set the properties on the correct server instances.
On Red Hat JBoss EAP, modify the
<system-properties>
section in:-
EAP_HOME/standalone/configuration/standalone*.xml
for standalone mode. -
EAP_HOME/domain/configuration/domain.xml
for domain mode.
-
Table 8.1. JVM Properties for Managed Decision Server Instance
Property Value Note org.kie.server.id
default-kie-server
The Decision Server ID.
org.kie.server.controller
The location of Decision Central.
org.kie.server.controller.user
controllerUser
The user name with the role
rest-all
as mentioned in the previous step.org.kie.server.controller.pwd
controllerUser1234;
The password of the user mentioned in the previous step.
org.kie.server.location
The location of the Decision Server.
Table 8.2. JVM Properties for Decision Central Instance
Property Value Note org.kie.server.user
controllerUser
The user name with the role
kie-server
as mentioned in the previous step.org.kie.server.pwd
controllerUser1234;
The password of the user mentioned in the previous step.
Verify the successful start of the Decision Server by sending a GET request to
http://SERVER:PORT/kie-server/services/rest/server/
. Once authenticated, you get an XML response similar to this:<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:
- Log in to Decision Central.
Click Menu → Deploy → Execution Servers.
If registration is successful, you can see the registered server ID.
8.2. Unmanaged Decision Server
An unmanaged Decision Server is a standalone instance, and therefore must be configured individually using REST/JMS API from the Decision Server itself. There is no controller involved. The configuration is automatically persisted by the server into a file and that is used as the internal server state, in case of restarts.
The configuration is updated during the following operations:
- Deploy KIE Container
- Undeploy KIE Container
- Start KIE Container
- Stop KIE Container
If the Decision Server is restarted, it will attempt to re-establish the same state that was persisted before shutdown. Therefore, KIE Containers that were running will be started, but the ones that were stopped will not.