Chapter 10. Configuring Process Server Managed by Business 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 Business Central to manage a Process Server instance.
Prerequisites
Users with the following roles exist:
-
In Business Central, a user with the role
rest-all
-
On the Process Server, a user with the role
kie-server
-
In Business Central, a user with the role
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 Business Central and the Process 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 10.1. JVM Properties for Process Server Instance
Property Value Note org.kie.server.id
default-kie-server
The Process Server ID.
org.kie.server.controller
http://localhost:8080/business-central/rest/controller
The location of Business 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
http://localhost:8080/kie-server/services/rest/server
The location of the Process Server.
Table 10.2. JVM Properties for Business 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 Process 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 Business Central.
Click Menu → Deploy → Execution Servers.
If registration is successful, you can see the registered server ID.
10.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.jar
Replace
PATH_TO_YOUR_KEYSTORE
,YOUR_KEYSTORE_PASSWD
,YOUR_KEYSTORE_ALIAS
, andYOUR_VERSION
with the relevant data.