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

Create a service account to be used for Realtime Decision Server for OpenShift deployment:

$ oc create serviceaccount <service-account-name>

Add the view role to the service account. This enables the service account to view all the resources in the application namespace in OpenShift, which is necessary for managing the cluster.

$ oc policy add-role-to-user view system:serviceaccount:<project-name>:<service-account-name>

Add the secret created for the project to the service account:

$ oc secret add sa/<service-account-name> secret/<secret-name>

The pom.xml must be configured to use a remote repository so that OpenShift can access it.

...
<distributionManagement>
  <repository>
    <id>deployment</id>
    <name>OpenShift Maven repo</name>
    <url>http://maven.example/deployment/filepath/</url>
  </repository>

  <snapshotRepository>
    <id>deployment</id>
    <name>OpenShift Maven repo</name>
    <url>http://maven.example/snapshots/filepath/</url>
  </snapshotRepository>
</distributionManagement>
...

For more information, see the Red Hat JBoss BRMS Administration and Configuration Guide.

The configuration/settings.xml file must have the remote repository defined so that OpenShift can download the application artifacts.

...
<profiles>
  <profile>
    <id>openshift-mirror-repositories</id>
    <repositories>
      <repository>
        <id>openshift-mirror</id>
        <url>http://maven.example/public/filepath/</url>
      </repository>
    </repositories>

    <pluginRepositories>
      <pluginRepository>
        <id>openshift-mirror</id>
        <url>http://maven.example/public/filepath/</url>
      </pluginRepository>
    </pluginRepositories>
  </profile>
</profiles>
...

For more information, see the Red Hat JBoss BRMS Installation Guide.

The hidden .s2i/environment file defines the KIE container deployment, including which KIE jars to use and the location from which to retrieve them. When OpenShift deploys the built image, the pod name is derived from the deployment alias defined in this file:

KIE_CONTAINER_DEPLOYMENT=<alias>=<group_id>:<artifact_id>:<version>

For example:

KIE_CONTAINER_DEPLOYMENT=RulesTest=com.example.openshift:example_workflow:1.0

If there is a pom.xml file in the source repository, a Maven build is triggered with the contents of $MAVEN_ARGS environment variable.

The results of a successful Maven build are installed into the local Maven repository, /home/jboss/.m2/repository/, along with all dependencies for offline usage. Realtime Decision Server for OpenShift will load the created kjars from this local repository.

All files in the configuration source repository directory are copied to EAP_HOME/standalone/configuration.

Get the application archive or build the application locally.

The following example uses both the hellorules and hellorules-client quickstarts.

Prepare the directory structure on the local file system.

Application archives in the deployments/ subdirectory of the main binary build directory are copied directly to the standard deployments folder of the image being built on OpenShift. For the application to deploy, the directory hierarchy containing the web application data must be correctly structured.

Create main directory for the binary build on the local file system and deployments/ subdirectory within it. Copy both the previously built JAR archive for the hellorules quickstart, and WAR archive for the hellorules-client quickstart to the deployments/ subdirectory:

decisionserver]$ ls
hellorules  hellorules-client  pom.xml

$ mkdir -p ocp/deployments

$ cp hellorules/target/decisionserver-hellorules-1.4.0.Final.jar ocp/deployments/

$ cp hellorules-client/target/decisionserver-hellorules-client-1.4.0.Final.war ocp/deployments/

Login into OpenShift instance.

$ oc login

Create a new project.

$ oc new-project ds-bin-demo

(Optional) Identify the image stream for the particular image.

$ oc get is -n openshift | grep ^jboss-decisionserver | cut -f1 -d ' '
jboss-decisionserver62-openshift
jboss-decisionserver63-openshift

Create new binary build, specifying image stream and application name.

$ oc new-build --binary=true \
--name=ds-hr-app \
--image-stream=jboss-decisionserver63-openshift \
-e KIE_SERVER_USER=kieserveruser \
-e KIE_SERVER_PASSWORD=kieserverPwd1!
--> Found image 4a6c0ce (5 weeks old) in image stream "jboss-decisionserver63-openshift" in project "openshift" under tag "latest" for "jboss-decisionserver63-openshift"

    JBoss BRMS Realtime Decision Server 6.3
    ---------------------------------------
    Platform for executing business rules on JBoss BRMS Realtime Decision Server 6.3.

    Tags: builder, decisionserver, decisionserver6

    * A source build using binary input will be created
      * The resulting image will be pushed to image stream "ds-hr-app:latest"
      * Use 'start-build --from-dir=DIR|--from-repo=DIR|--from-file=FILE' to trigger a new build
      * WARNING: a binary build was created, you must specify one of --from-dir|--from-file|--from-repo when starting builds

--> Creating resources with label build=ds-hr-app ...
    imagestream "ds-hr-app" created
    buildconfig "ds-hr-app" created
--> Success

Start the binary build. Instruct oc executable to use main directory of the binary build we created in previous step as the directory containing binary input for the OpenShift build.

$ oc start-build ds-hr-app --from-dir=./ocp/ --follow
Uploading directory "ocp" as binary input for the build ...
build "ds-hr-app-1" started
Receiving source from STDIN as archive ...

Copying all war artifacts from /home/jboss/source/. directory into /opt/eap/standalone/deployments for later deployment...
Copying all ear artifacts from /home/jboss/source/. directory into /opt/eap/standalone/deployments for later deployment...
Copying all rar artifacts from /home/jboss/source/. directory into /opt/eap/standalone/deployments for later deployment...
Copying all jar artifacts from /home/jboss/source/. directory into /opt/eap/standalone/deployments for later deployment...
Copying all war artifacts from /home/jboss/source/deployments directory into /opt/eap/standalone/deployments for later deployment...
'/home/jboss/source/deployments/decisionserver-hellorules-client-1.4.0.Final.war' -> '/opt/eap/standalone/deployments/decisionserver-hellorules-client-1.4.0.Final.war'
Copying all ear artifacts from /home/jboss/source/deployments directory into /opt/eap/standalone/deployments for later deployment...
Copying all rar artifacts from /home/jboss/source/deployments directory into /opt/eap/standalone/deployments for later deployment...
Copying all jar artifacts from /home/jboss/source/deployments directory into /opt/eap/standalone/deployments for later deployment...
'/home/jboss/source/deployments/decisionserver-hellorules-1.4.0.Final.jar' -> '/opt/eap/standalone/deployments/decisionserver-hellorules-1.4.0.Final.jar'
/opt/eap/standalone/deployments/decisionserver-hellorules-1.4.0.Final.jar is a kjar
...
INFO: org.openshift.quickstarts:decisionserver-hellorules:1.4.0.Final verified.


Pushing image 172.30.202.111:5000/ds-bin-demo/ds-hr-app:latest ...
Pushed 6/9 layers, 67% complete
Pushed 7/9 layers, 78% complete
Pushed 8/9 layers, 89% complete
Pushed 9/9 layers, 100% complete
Push successful

Create a new OpenShift application based on the build.

$ oc new-app ds-hr-app
--> Found image c2c182e (48 seconds old) in image stream ds-hr-app under tag "latest" for "ds-hr-app"

    ds-bin-demo/ds-hr-app-2:ea504dd7
    --------------------------------
    Platform for executing business rules on JBoss BRMS Realtime Decision Server 6.3.

    Tags: builder, decisionserver, decisionserver6

    * This image will be deployed in deployment config "ds-hr-app"
    * Ports 8080/tcp, 8443/tcp, 8778/tcp will be load balanced by service "ds-hr-app"
      * Other containers can access this service through the hostname "ds-hr-app"

--> Creating resources with label app=ds-hr-app ...
    deploymentconfig "ds-hr-app" created
    service "ds-hr-app" created
--> Success
    Run 'oc status' to view your app.

Expose the service as route.

$ oc get svc -o name
service/ds-hr-app

$ oc expose svc/ds-hr-app
route "ds-hr-app" exposed

Access the application.

You can get the list of available query string arguments of the hellorules application by accessing the URL http://ds-hr-app-ds-bin-demo.openshift.example.com/hellorules/.

Run the hellorules-client servlet using the URL http://ds-hr-app-ds-bin-demo.openshift.example.com/hellorules?command=runLocal.

Create a new project:

$ oc new-project rds-app-demo

Create a service account to be used for the deployment of the Decision Server application:

$ oc create serviceaccount rds-service-account

Add the view role to the service account. This enables the service account to view all the resources in the rds-app-demo namespace, which is necessary for managing the cluster.

$ oc policy add-role-to-user view system:serviceaccount:rds-app-demo:rds-service-account

The Decision Server template requires an SSL keystore and a JGroups keystore.
These keystores are expected even if the application will not use https.
This example uses ‘keytool’, a package included with the Java Development Kit, to generate self-signed certificates for these keystores. The following commands will prompt for passwords.

Use the SSL and JGroup keystore files to create the secret for the project:

$ oc create secret generic rds-app-secret --from-file=jgroups.jceks --from-file=keystore.jks

Add the secret to the service account created earlier:

$ oc secret add sa/rds-service-account secret/rds-app-secret

Fork the repository.

You are redirected to your new fork.

Click Clone.

Once cloned, the repository displays the commit history.

From the command line, navigate into the /.niogit directory in the project you forked earlier:

$ cd EAPHOME/bin/.niogit/decision-services.git

The path above is the default, which may differ depending on where the workbench has been configured to store its data. This location is set using the org.uberfire.nio.git.dir system property.

Set the remote URL for this project:

$ git remote set-url origin git@github.com:/decisionserver

Navigate into the hooks directory:

$ cd hooks

Create a simple post-commit file:

$ touch post-commit

Edit the file and type the following:

#!/bin/sh

git push origin master

Change the permissions on the file to allow Red Hat JBoss BRMS the access it requires:

$ chmod 777 post-commit

The hook is now configured, meaning that any change to the files in this Red Hat JBoss BRMS project will automatically update your forked decisionserver GitHub repository.

Under DRL, click to load the HelloRules.drl file:

package org.openshift.quickstarts.decisionserver.hellorules

query "get greeting"()
    greeting : Greeting()
end

rule "greet master"
    when
        person : Person( name == "john")
    then
        String salutation = "Hello " + person.getName() + "! What can I help you with today?";
        insert(new Greeting(salutation));
end
rule "greet strangers"
    when
        person : Person(name != "john")
    then
        String salutation = "Hey there " + person.getName() + ". I don't think I know you yet!";
        insert(new Greeting (salutation));
end

Click Save, type a check in comment, and click Save again.

The hook you created earlier will automatically update your forked GitHub repository with these saved changes.

Click Create.

The web console’s welcome screen loads.

Change the SOURCE_REPOSITORY_URL to the Git source URI for your forked repository. For example:

https://github.com/<your_github_username>/decisionserver.git

Add the MAVEN_MIRROR_URL environment variable below the KIE_CONTAINER_DEPLOYMENT variable:

strategy
 sourceStrategy:
  env:
   -
    name: KIE_CONTAINER_DEPLOYMENT
    value: 'HelloRulesContainer=org.openshift.quickstarts:decisionserver-hellorules:1.2.0.Final'
   -
    name: MAVEN_MIRROR_URL
    value: 'http://nexus-ci.cloudapps.bos.openshift3roadshow.com/content/groups/public/'

The value for MAVEN_MIRROR_URL can be found in Maven by viewing the repositories, then copying the path for the Public Repositories group.

Verify that the new build is using the new Maven proxy to download locally by finding the line in the log that references Downloading. For example:

I0130 12:32:25.664594     1 sti.go:492] Downloading: http://nexus-ci.cloudapps.openshift.com/content/groups/public/org/kie/kie-maven-plugin/6.3.0.Final-redhat-5/kie-maven-plugin-6.3.0.Final-redhat-5.pom

Load the HelloRules.drl file:

package org.openshift.quickstarts.decisionserver.hellorules

query "get greeting"()
    greeting : Greeting()
end

rule "greet master"
    when
        person : Person( name == "john")
    then
        String salutation = "Hello " + person.getName() + "! What can I help you with today?";
        insert(new Greeting(salutation));
end
rule "greet strangers"
    when
        person : Person(name != "john")
    then
        String salutation = "Hey there " + person.getName() + ". I don't think I know you yet!";
        insert(new Greeting (salutation));
end