The Realtime Decision Server accepts a number of bootstrap switches (system properties) to configure the behaviour of the server. The following is a table of all the supported switches.

Note that some properties are marked as required when using a controller. Thus, you need to set these properties when you handle Realtime Decision Server, container creation, and removal in Business Central. If you use the Realtime Decision Server separately, without any interaction with Business Central, you do not have to set these properties.

A managed instance requires an available controller to start up the Realtime Decision Server.

A Controller is a component that keeps and manages a Realtime 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 Realtime Decision Server can be configured with a list of controllers, but will only connect to one at a time.

When the Realtime 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 for some reason 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 register a new managed Realtime Decision Server instance, set the following properties in standalone.xml:

<property name="org.kie.server.user" value="anton"></property>
<property name="org.kie.server.pwd" value="password1!"></property>
<property name="org.kie.server.location" value="http://localhost:8080/kie-server/services/rest/server"></property>
<property name="org.kie.server.controller" value="http://localhost:8080/business-central/rest/controller"></property>
<property name="org.kie.server.controller.user" value="kieserver"></property>
<property name="org.kie.server.controller.pwd" value="kieserver1!"></property>
<property name="org.kie.server.id" value="local-server-123"></property>

The standalone.xml file is located in the $SERVER_HOME/standalone/configuration/ directory.

org.kie.server.user must have the kie-server role assigned.

To create the kieserver user:

To verify successful start of the Realtime Decision Server, send a GET request to http://SERVER:PORT/kie-server/services/rest/server/. Once authenticated, you will see the following XML response:

<response type="SUCCESS" msg="Kie Server info">
	<kie-server-info>
		<capabilities>KieServer</capabilities>
		<capabilities>BRM</capabilities>
		<capabilities>BPM</capabilities>
		<location>
		http://localhost:8080/kie-server/services/rest/server
		</location>
		<name>local-server-123</name>
		<id>local-server-123</id>
		<version>6.3.0.Final-redhat-5</version>
	</kie-server-info>
</response>

To verify successful registration, log into the Business Central and select Deploy → Rule Deployments. If successful, you will see the registered server ID.

An unmanaged Realtime Decision Server is a standalone instance, and therefore must be configured individually using REST/JMS API from the Realtime 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: