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 the service account:

$ echo '{"kind": "ServiceAccount", "apiVersion": "v1", "metadata": {"name": "<service-account-name>"}}' | oc create -f -

OpenShift 3.2 users can use the following command to create the service account:

$ oc create serviceaccount <service-account-name>

Add the view role to the service account:

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

Create a service account to be used for the Intelligent Process Server 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/<ips-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 BPM Suite 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 BPM Suite 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=ApplicationTest=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. The Intelligent Process Server xPaaS Image will load the created kjars from this local repository.

Get the application archive or build the application locally.

The following example uses both the library and library-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 library quickstart (processserver-library-1.4.0.Final.jar), and WAR archive for the library-client quickstart (processserver-library-client-1.4.0.Final.war) to the deployments/ subdirectory:

$ ls
library  library-client  pom.xml  timerprocess

$ mkdir -p ps-bin-demo/deployments

$ cp library/target/processserver-library-1.4.0.Final.jar ps-bin-demo/deployments/

$ cp library-client/target/processserver-library-client-1.4.0.Final.war ps-bin-demo/deployments/

Login into OpenShift instance.

$ oc login

Create a new project.

$ oc new-project ps-bin-demo

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

$ oc get is -n openshift | grep ^jboss-process | cut -f1 -d ' '
jboss-processserver63-openshift

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

$ oc new-build --binary=true \
--name=ps-l-app \
--image-stream=jboss-processserver63-openshift \
-e KIE_SERVER_USER=kieserveruser \
-e KIE_SERVER_PASSWORD=kieserverPwd1!
--> Found image 78c88f3 (2 months old) in image stream "openshift/jboss-processserver63-openshift" under tag "latest" for "jboss-processserver63-openshift"

    JBoss BPMS Intelligent Process Server 6.3
    -----------------------------------------
    Platform for executing business rules on JBoss BPMS Intelligent Process Server 6.3.

    Tags: builder, processserver, processserver6

    * A source build using binary input will be created
      * The resulting image will be pushed to image stream "ps-l-app:latest"
      * A binary build was created, use 'start-build --from-dir' to trigger a new build

--> Creating resources with label build=ps-l-app ...
    imagestream "ps-l-app" created
    buildconfig "ps-l-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 ps-l-app \
--from-dir=./ps-bin-demo/ \
--follow
Uploading directory "ps-bin-demo" as binary input for the build ...
build "ps-l-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/processserver-library-client-1.4.0.Final.war' -> '/opt/eap/standalone/deployments/processserver-library-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/processserver-library-1.4.0.Final.jar' -> '/opt/eap/standalone/deployments/processserver-library-1.4.0.Final.jar'
/opt/eap/standalone/deployments/processserver-library-1.4.0.Final.jar is a kjar
...
INFO: org.openshift.quickstarts:processserver-library:1.4.0.Final verified.
Pushing image 172.30.82.129:5000/ps-bin-demo/ps-l-app:latest ...
Pushed 0/9 layers, 0% complete
Pushed 1/9 layers, 12% complete
Pushed 2/9 layers, 33% complete
Pushed 3/9 layers, 45% complete
Pushed 4/9 layers, 64% complete
Pushed 5/9 layers, 71% complete
Pushed 6/9 layers, 80% complete
Pushed 7/9 layers, 88% complete
Pushed 8/9 layers, 100% complete
Pushed 9/9 layers, 100% complete
Push successful

Create a new OpenShift application based on the build.

$ oc new-app ps-l-app
--> Found image 65a8367 (About a minute old) in image stream "ps-bin-demo/ps-l-app" under tag "latest" for "ps-l-app"

    ps-bin-demo/ps-l-app-1:0af8685b
    -------------------------------
    Platform for executing business rules on JBoss BPMS Intelligent Process Server 6.3.

    Tags: builder, processserver, processserver6

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

--> Creating resources ...
    deploymentconfig "ps-l-app" created
    service "ps-l-app" created
--> Success
    Run 'oc status' to view your app.

Expose the service as route.

$ oc get svc -o name
service/ps-l-app

$ oc expose svc/ps-l-app
route "ps-l-app" exposed

$ oc get route
NAME       HOST/PORT                                    PATH      SERVICES   PORT       TERMINATION   WILDCARD
ps-l-app   ps-l-app-ps-bin-demo.openshift.example.com             ps-l-app   8080-tcp                 None

Access the application.

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

Run the library-client servlet using the URL http://ps-l-app-ps-bin-demo.openshift.example.com/library?command=runLocal.

Clone the existing repository to ensure it is up-to-date.

Using Repository View, ensure the pom.xml is configured to use a remote repository by containing xml similar to the following:

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

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

In the application repository, ensure the configuration/settings.xml and the .s2i/environment files define the Maven repository and the KIE container deployment respectively:

Create a new project:

$ oc new-project ips-app-demo

Create a service account to be used for the IPS deployment:

$ oc create serviceaccount ips-service-account

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

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

The Intelligent Process 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 ips-app-secret --from-file=jgroups.jceks --from-file=keystore.jks

Add the secret to the service account created earlier:

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