This example shows how to use Camel in the Java Container using CDI to connect to the A-MQ xPaaS message broker on OpenShift. The Red Hat JBoss A-MQ xPaaS product should already be installed and running on your OpenShift installation - see the documentation

This example is implemented using Java code with CDI injected resources. The source code uses the CDI Annotation @ServiceName to lookup the ActiveMQ broker Service name.

The broker service name can be changed here and defaults to @ServiceName("broker")

This example will connect to the A_MQ message broker and send messages to a queue TEST.FOO

The example can be built with

mvn clean install

It is assumed that OpenShift platform is already running. If not you can find details how to Install OpenShift at your site.

The example can be built and deployed using a single goal:

mvn -Pf8-deploy

When the example runs in OpenShift, you can use the OpenShift client tool to inspect the status

To list all the running pods:

oc get pods

Then find the name of the pod that runs this quickstart, and output the logs from the running pods with:

oc logs <name of pod>

You can also use the openshift web console to manage the running pods, and view logs and much more.

The example can also be built and run using the included S2I template quickstart-template.json.

The application can be run directly by first editing the template file and populating S2I build parameters, including the required parameter GIT_REPO and then executing the command:

oc new-app -f quickstart-template.json

Alternatively the template file can be used to create an OpenShift application template by executing the command:

oc create -f quickstart-template.json

You can find more details about running this quickstart on the website. This also includes instructions how to change the Docker image user and registry.