Chapter 2. Comparison: Red Hat JBoss BRMS and Realtime Decision Server for OpenShift
This topic details the differences between Realtime Decision Server for OpenShift and the full, non-PaaS release of Red Hat JBoss BRMS, and provides instructions specific to running and configuring Realtime Decision Server for OpenShift. Documentation for other Red Hat JBoss BRMS functionality not specific to Realtime Decision Server for OpenShift can be found in the Red Hat JBoss BRMS documentation on the Red Hat Customer Portal.
EAP_HOME in this documentation, as in the Red Hat JBoss BRMS documentation, is used to refer to the JBoss EAP installation directory where the decision server is deployed. The location of EAP_HOME inside Realtime Decision Server for OpenShift is /opt/eap/, which the JBOSS_HOME environment variable is also set to by default.
2.1. Functionality Differences for Realtime Decision Server for OpenShift
There are several major functionality differences in Realtime Decision Server for OpenShift:
- Realtime Decision Server for OpenShift extends EAP for OpenShift, and any capabilities or limitations it has are also found in Realtime Decision Server for OpenShift.
- Only stateless scenarios are supported.
- To connect to the Decision Server web console, click the Connect button in the Decision Server pod of the OpenShift web console, or the Open Java Console button in OpenShift 3.2.
- There is no support for authoring any content through the BRMS Console or API.
2.2. Version Compatibility and Support
For more information on OpenShift image version compatibility, see the xPaaS part of the OpenShift and Atomic Platform Tested Integrations page.
2.3. Deprecated Image Streams and Application Templates for Realtime Decision Server for OpenShift
The Realtime Decision Server for OpenShift image version number 6.2 is deprecated and it will no longer receive updates of image and application templates.
The Realtime Decision Server for OpenShift image version number 6.3 is deprecated and it will no longer receive updates of image and application templates.
It is recommended to use the version 6.4 of Realtime Decision Server for OpenShift image and application templates to deploy new applications.
2.4. Managing Realtime Decision Server for OpenShift
As Realtime Decision Server for OpenShift is built off EAP for OpenShift, the JBoss EAP Management CLI is accessible from within the container for troubleshooting purposes.
First open a remote shell session to the running pod:
$ oc rsh <pod_name>
Then run the following from the remote shell session to launch the JBoss EAP Management CLI:
$ /opt/eap/bin/jboss-cli.sh
Any configuration changes made using the JBoss EAP Management CLI on a running container will be lost when the container restarts.
Making configuration changes to the JBoss EAP instance inside EAP for OpenShift is different from the process you may be used to for a regular release of JBoss EAP.
2.5. Security in Realtime Decision Server for OpenShift
Access is limited to users with the kie-server authorization role. A user with this role can be specified via the KIE_SERVER_USER and KIE_SERVER_PASSWORD environment variables.
The HTTP/REST endpoint is configured to only allow the execution of KIE containers and querying of KIE Server resources. Administrative functions like creating or disposing Containers, updating ReleaseIds or Scanners, etc. are restricted. The JMS endpoint currently does not support these restrictions. In the future, more fine-grained security configuration should be available for both endpoints.
2.6. Initial Setup
The Tutorials in this guide follow on from and assume an OpenShift instance similar to that created in the OpenShift Primer.
