Chapter 4. Preparing a Red Hat JBoss BRMS Project Repository for OpenShift

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