Chapter 10. Realtime Decision Server

The Realtime Decision Server is a standalone, out-of-the-box component that can be used to instantiate and execute rules through interfaces available for REST, JMS or a Java client side application. Created as a web deployable WAR file, this server can be deployed on any web container. The current version of the Realtime Decision Server ships with default extensions for both JBoss BRMS and JBoss BPM Suite.

This 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 KIE Containers which allows you to execute multiple rule services in parallel.

You can provision the Realtime Decision Server instances through Business Central. In this chapter, you will go through the steps required to setup the Realtime Decision Server, provision and connect to this server through Business Central, control what rule artifacts go in each instance and go through its lifecycle.

10.1. Deploying the Realtime Decision Server

The Realtime Decision Server is distributed as a web application archive (WAR) file with the name of kie-server.war. When you install Red Hat JBoss BRMS, this WAR file is installed and deployed in your web container by default.

You can copy this WAR file and deploy it in any other web container (Red Hat JBoss Web Server or another Red Hat JBoss EAP install, for example) and have this server available from other web containers. Note that you must deploy the WAR file that is compatible for your web container.

  1. Once you have deployed the WAR file (or if you have it deployed on the same web container where Red Hat JBoss BRMS is deployed), create a user with the role of kie-server in this web container.
  2. Test that you can access the decision engine by navigating to the endpoint in a browser window: http://SERVER:PORT/kie-server/services/rest/server/ with the web container running. You will be prompted for your username/password that you created in the previous step.
  3. Once authenticated, you will see an XML response in the form of engine status, similar to this:

    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <response type="SUCCESS" msg="Kie Server info">