With the project space now available, let's create the broker instance.

Inspect the ActiveMQArtermis custom resource

Click the link below to open the custom resource (CR) definition for the cluster:

• amq-broker.yaml

As you can see, we are enabling just one single acceptor and configuring it to accept incomming AMQP connections in the default 5672 port.

We are also enabling the console and exposing the endpoints for external access too.

Creating an AMQ broker

Switch to the application directory in the command line by issuing the following command:

cd /root/projects/amq-examples/amq-js-demo

Create a new broker using the OpenShift command:

oc -n messaging apply -f amq-broker.yaml

This command will create a broker customer resource, the operator then will take notice of the desired state and will create the required deployment and resources missing to run a new instance.

You should see the output:

activemqartemis.broker.amq.io/broker created

Check broker deployment

Follow up the AMQ broker deployment to validate it is running.

To watch the pods status run the following command:

oc -n messaging get pods -w

You will see the pod for the broker StatefulSet changing the status to running. It should look similar to the following:

NAME                                  READY   STATUS              RESTARTS   AGE
amq-broker-operator-6c76986f9-brl67   1/1     Running             0          15m
broker-ss-0                           0/1     ContainerCreating   0          5s
broker-ss-0                           0/1     ContainerCreating   0          6s
broker-ss-0                           0/1     Running             0          25s
broker-ss-0                           1/1     Running             0          57s

Hit Ctrl+C to stop the process.

^C

When the provisioning of the broker finishes, you will be set to start using the service. In the next step you will deploy a simple messging application.

The sample project in the upper right part side of the screen, shows the components of your sample Node.js project. This project uses Red Hat Runtimes, a set of open source cloud native application runtimes for modern applications.

The app implements a simple messaging greeting service that simply sends a Hello World! to a queue and the same application listens in the same queue for greeting messages. We use the Red Hat AMQ JavaScript Client to create a connection to the messaging broker to send and receive messages.

The AMQ Clients is a suite of AMQP 1.0 messaging APIs that allow you to make any application a messaging application. It includes both industry-standard APIs such as JMS and new event-driven APIs that make it easy to integrate messaging anywhere. The AMQ Javascript Client is based on the AMQP Rhea Project.

Inspect the application code

Click the links below to open each file and inspect its contents:

• package.json - Metadata about the project: name, version, dependencies, and other information needed to build and maintain the project.
• app.js - Main logic of the sample application.

Install Dependencies

Dependencies are listed in the package.json file and declare which external projects this sample app requires. To download and install them, run the following command:

npm install

It will take a few seconds to download, and you should see a final report such as

added 140 packages in 2.937s

Deploy

Build and deploy the project using the following command:

npm run openshift

This uses NPM and the Nodeshift project to build and deploy the sample application to OpenShift using the containerized Node.js runtime.

The build and deploy may take a minute or two. Wait for it to complete.

You should see INFO complete at the end of the build output, and you should not see any obvious errors or failures.

Check application deployment

Follow up the application deployment to validate it is running.

To watch the pods status run the following command:

oc -n messaging get pods -w

You will see the pod for the application changing the status to running. It should look similar to the following:

NAME                                  READY   STATUS      RESTARTS   AGE
amq-broker-operator-6c76986f9-6vjhj   1/1     Running     0          6m5s
amq-js-demo-1-deploy                  0/1     Completed   0          32s
amq-js-demo-1-dftm4                   1/1     Running     0          26s
amq-js-demo-s2i-1-build               0/1     Completed   0          90s
broker-ss-0                           1/1     Running     0          4m46s

Hit Ctrl+C to stop the process.

^C

In the next step you will check your application is running.

After the previous step build finishes, it will take less than a minute for the application to become available.

Check the application logs

Now that the application is up and running you can check the logs to check how is everything going on.

Let's use the OpenShift CLI tool to connect with the deployment and view the pod's log.

Use the following command to retrieve the logs:

oc -n messaging logs -f dc/amq-js-demo

You will see a message every 10 seconds with the following text:

Message received: {"id":1,"text":"Hello World!","timestamp":1605814628546}

This message is been sent and received to the example queue by the application you just deployed.