第3章 Realtime Decision Server

1. Follow the steps described in section Installing Red Hat JBoss BRMS on Red Hat JBoss Web Server of Red Hat JBoss BRMS Installation Guide to download and extract the generic deployable archive containing kie-server.war.

2. Configure users and roles. Make sure that the TOMCAT_HOME/conf/tomcat-users.xml file contains the following role and user definition. The user name and password should be unique, however, the role must be defined as kie-server:

   <role rolename="kie-server"/>
   <user username="serveruser" password="my.s3cr3t.pass" roles="kie-server"/>

3. Start the server: run TOMCAT_HOME/bin/startup.sh or in a Windows system TOMCAT_HOME/bin/startup.bat. To make sure that the application was deployed successfully, see Tomcat logs in the TOMCAT_HOME/logs directory. See 「Bootstrap Switches」 for the list of bootstrap switches that can be used to properly configure the instance. For example:

   $ ./startup.sh -Dorg.kie.server.id=first-kie-server -Dorg.kie.server.location=http://localhost:8080/kie-server/services/rest/server

4. To verify that the server is running, open http://SERVER:PORT/kie-server/services/rest/server/ in a web browser and enter the user name and the password specified before. You should see a simple XML message with basic information about the server.

Configuring Realtime Decision Server Managed by Business Central

1. Make sure users with the following roles exist:

   • In Business Central, a user with the role rest-all.
   • On the Realtime 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.

   If such users do not exist, create them.

   • On Red Hat JBoss EAP, go to EAP_HOME/bin/ and execute:

     $ ./add-user.sh -a --user controllerUser --password controllerUser1234; --role kie-server,rest-all

     警告

     Plain-text passwords are not secure. For production environments, use a password vault. For more information, see the Password Vault chapter of the Red Hat JBoss Enterprise Application Platform 6.4 How To Configure Server Security guide.

   • On Red Hat JBoss Web Server, see 「Red Hat JBoss Web Server 2.X/3.X, Tomcat 8.X/9.X」.
   • On IBM WebSphere Application Server, see the Creating Users and Groups section of the Red Hat JBoss BRMS IBM WebSphere Installation and Configuration Guide.
   • On Oracle WebLogic Server, see the Configuring Security Settings section of the Red Hat JBoss BRMS Oracle Weblogic Installation and Configuration Guide.

2. Set the following JVM properties. The location of Business Central and the Realtime 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.
   • On Red Hat JBoss Web Server, see 「Red Hat JBoss Web Server 2.X/3.X, Tomcat 8.X/9.X」.
   • On IBM WebSphere Application Server, see section Adding Custom JVM Properties of the Red Hat JBoss BRMS IBM WebSphere Installation and Configuration Guide.
   • On Oracle WebLogic Server, see section Setting Environment Variables of the Red Hat JBoss BRMS Oracle WebLogic Installation and Configuration Guide.

   表3.5 JVM Properties for Managed Realtime Decision Server Instance

   Property	Value	Note
   org.kie.server.id	default-kie-server	The Realtime Decision 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 Realtime Decision Server.

   表3.6 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.

3. Verify the successful start of the Realtime 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:

   <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
   <response type="SUCCESS" msg="Kie Server info">
       <kie-server-info>
           <capabilities>BRM</capabilities>
           <capabilities>BPM-UI</capabilities>
           <capabilities>BPM</capabilities>
           <capabilities>BRP</capabilities>
           <capabilities>KieServer</capabilities>
           <location>http://localhost:8080/kie-server/services/rest/server</location>
           <messages>
               <content>Server KieServerInfo{serverId='local-server-123', version='6.4.0.Final-redhat-3', location='http://localhost:8080/kie-server/services/rest/server'}started successfully at Fri Jun 03 13:48:44 CEST 2016</content>
               <severity>INFO</severity>
               <timestamp>2016-06-03T13:48:44.606+02:00</timestamp>
           </messages>
           <name>local-server-123</name>
           <id>local-server-123</id>
           <version>6.4.0.Final-redhat-3</version>
       </kie-server-info>
   </response>

4. Verify successful registration by logging into Business Central and selecting Deploy → Execution Servers. If successful, you can see the registered server ID.

1. Log in to Business Central.
2. In the main menu on the top, click Deploy → Execution Servers.
3. Select your server from the SERVER TEMPLATES section on the left side of the page.
4. Find the container you want to start under the KIE CONTAINERS section on the left.

5. Click Start at the upper right hand corner.

   Alternatively, click Stop to stop a running container. Once a container is stopped, you can click Remove to remove it.

1. Log in to Business Central.
2. In the main menu on the top, click Deploy → Execution Servers.
3. Select your server from the SERVER TEMPLATES section on the left side of the page.
4. Find the container you want to upgrade under the KIE CONTAINERS section on the left.
5. Click on the Version Configuration tab at the top.

6. Enter a new version and click Upgrade.

   Optionally, if you want a deployed container to always have the latest version of your deployment without manually editing it, set the Version value to LATEST and click Scan Now. If a newer version of a container deployment is found in the repository during the scanning, the container is automatically upgraded to this newer version. To start the scanner in the background, click Start Scanner and specify a scan interval in milliseconds.

   The Version value can be set to LATEST if you are creating a deployment for the first time.