Chapter 8. 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*.xmlfor standalone mode. -
EAP_HOME/domain/configuration/domain.xmlfor domain mode.
-
Table 8.1. JVM Properties for Managed Decision Server Instance Property Value Note org.kie.server.iddefault-kie-serverThe Decision Server ID.
org.kie.server.controllerhttp://localhost:8080/decision-central/rest/controllerThe location of Decision Central.
org.kie.server.controller.usercontrollerUserThe user name with the role
rest-allas mentioned in the previous step.org.kie.server.controller.pwdcontrollerUser1234;The password of the user mentioned in the previous step.
org.kie.server.locationhttp://localhost:8080/kie-server/services/rest/serverThe location of the Decision Server.
Table 8.2. JVM Properties for Decision Central Instance Property Value Note org.kie.server.usercontrollerUserThe user name with the role
kie-serveras mentioned in the previous step.org.kie.server.pwdcontrollerUser1234;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.1. Configuring Smart Router for TLS support
You can now configure Smart Router (previously, KIE Server Router) for TLS support to allow HTTPS traffic.
Procedure
Open a terminal and enter the following command to start the smart router with TLS support:
java -Dorg.kie.server.router.tls.keystore=PATH_TO_YOUR_KEYSTORE -Dorg.kie.server.router.tls.keystore.password=YOUR_KEYSTORE_PASSWD -Dorg.kie.server.router.tls.keystore.keyalias=YOUR_KEYSTORE_ALIAS -jar kie-server-router-proxy-YOUR_VERSION.jarReplace
PATH_TO_YOUR_KEYSTORE,YOUR_KEYSTORE_PASSWD,YOUR_KEYSTORE_ALIAS, andYOUR_VERSIONwith the relevant data.
