Skip to main content

Red Hat JBoss Fuse - Connecting to A-MQ in EAP with Camel

JBoss EAP has a built-in Messaging solution, HornetQ. Sometimes we need A-MQ for more protocol support, reliable messaging and HA capability. By connecting through the resource adaptor in EAP, we will be able to connect EAP to A-MQ.

First install the A-MQ library into EAP.

You can find it in the A-MQ zip file, under /jboss-a-mq-6.2.x.redhat-xxx/extras/,
in there you can find a apache-activemq-5.11.x.redhat-62xxxx-bin.zip file, unzip it, there you can locate the library we need in apache-activemq-5.11.x.redhat-62xxxx/lib/optional. 

  • activemq-rar-5.11.x.redhat-62xxxx.rar

Make sure you start up both the JBoss A-MQ(with ID/PWD: admin/admin) and JBoss EAP, go to the JBoss Admin Console located at http://localhost:9990 and logon with the ID/PWD previously set by you when installing. There are several options here,
  1. Install the libraries through deployment
  2. Install as module

So I am going to do the easy way, which is deploy the libraries. This is not recommended in production (since anyone with admin right and remove, disable the library..).  In the admin console, go to Runtime/Manage Deployments, and click on "Add" button to add the rar file.



After successful deployment, enable the rar file.


And we are now ready to start setting the resource adaptor. Go to Configuration -> Under Connector, click on Resource Adapters, and it will display the configuration page. Click on Add to add our new Resource, which A-MQ.


A screen will then pop-up, enter
activemq-rar-5.11.x.redhat-62xxxx.rar
which is the name when you deploy the library on EAP. And select XATransaction.


Under Properties tab, enter the following settings,

  • UserName: admin
  • Password: admin
  • UseInboundSession: true
  • ServerUrl: tcp://localhost:61616?jms.rmIdFromConnectionId=true



We can now setup the ConnectionFactory for the broker, first click on view in activemq-rar-5.11.x.redhat-6.2.xxx.rar. In the Connection Definition configuration page, click on add, a popup will appear, enter following information.

  • Name: localhostConnectionFactory
  • JNDI Name: java:jboss/jms/activemq/ConnectionFactory
  • Connection Class: org.apache.activemq.ra.ActiveMQManagedConnectionFactory



Under Properties, please enter the following config. 
  • UserName: admin
  • Password: admin
  • UseInboundSession: true
  • ServerUrl: tcp://localhost:61616?jms.rmIdFromConnectionId=true
And lastly, enable the connection factory.


This is what it looks like.



Normally, that is all we need for Camel application. BUT! If you would like to map to your messaging queue or topics via Message Driven Bean, we need to go for an extra step to create the adapter for Queue and Topics as well. Here I am going to use queue as an example.

Go to Admin Objects unser Resource Adapter,


Click on Add to add an admin object, enter:

  • Name:testQueue
  • JNDI Name:java:jboss/jms/amq/queue/testQueue
  • Class Name: org.apache.activemq.command.ActiveMQQueue

In Properties tab add

  • PhysicalName:TEST.QUEUE

And enable the testQueue.
And to add resource mapping to Message driven bean, we need to map the resource adapter to our message driven bean in the container, go to standalone.xml or domain.xml (depends on if you are in standalone or domain mode). Here I am starting using standalone mode, so I will open my standalone.xml under standalone/configuration folder in JBoss EAP. 

Under ejb3 subsystem, add mdb mapping. 

<subsystem xmlns="urn:jboss:domain:ejb3:1.5">
    .....
    <mdb>
      <resource-adapter-ref resource-adapter-name="activemq-rar-5.11.0.redhat-620133.rar"/>
      <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>
    </mdb>
    ......
</subsystem>

That's it for the setting. You have successfully created a Resource Adaptor from JBoss EAP to JBoss A-MQ. 

To do a little testing, I created a small MDB project, 
we can map the destination queue to "queue/testQueue" 

package com.redhat.mdb;

import java.util.logging.Logger;

import javax.ejb.ActivationConfigProperty;
import javax.ejb.MessageDriven;
import javax.jms.JMSException;
import javax.jms.Message;
import javax.jms.MessageListener;
import javax.jms.TextMessage;

@MessageDriven(name = "TestMDB", activationConfig = {
@ActivationConfigProperty(propertyName = "destinationType", propertyValue = "javax.jms.Queue"),
@ActivationConfigProperty(propertyName = "destination", propertyValue = "queue/testQueue"),
@ActivationConfigProperty(propertyName = "acknowledgeMode", propertyValue = "Auto-acknowledge") })
public class TestMDB implements MessageListener {

  private final static Logger LOGGER = Logger.getLogger(TestMDB.class.toString());
  @Override
  public void onMessage(Message recmsg) {
    TextMessage msg = null;
    try {
      if (recmsg instanceof TextMessage) {
        msg = (TextMessage) recmsg;
        LOGGER.info("Received Message from queue: " + msg.getText());
      } else {
        LOGGER.warning("Message of wrong type: " recmsg.getClass().getName());
      }
    } catch (JMSException e) {
      throw new RuntimeException(e);
    }
  }

}

Click here to download for the source code, if you would like to run it, please run
  • mvn clean install 

under the mdb project directory.

And then deploy the WAR file onto EAP. 


It will start printing our messages if we send message in to the queue, so, go to A-MQ admin console at http://localhost:8181, login with admin/admin, click on  ActiveMQ -> amq -> queue -> queue/testQueue, and then on the righthand side, click on the Send Tab. 
Here you can send data and messages into queue. 





And the result will appear in the log.


That's it. :)





Comments

Popular posts from this blog

Red Hat JBoss Fuse - Getting Started with Fuse Integration Service 2.0 Tech preview

I just realized that I did not do a getting started for Fuse Integration Service 2.0 Tech preview before I did the pipeline demo, thanks for those of you who reminded me! :)

To get started with FIS 2.0, for people who has just getting to know the technology, here is how I interpret it. Basically, it's divide into two aspect,

1. Integration development, FIS uses Apache Camel as the core technology that creates, orchestrate, compose microservices into a super lightweight thin integration layer, and become the API provider and service orchestrator through exposing RESTful or messaging service endpoints. And you can choose to either package and run it with Spring-Boot or Karaf.


2. Application Deployment and Management, FIS takes advantages of OpenShift platform, and allows you to separately deploy the micro-integration service among distributed environment, at the same time takes care of the failover, high availability, load balancing and service lookup problem for you.


So, now we know …

Red Hat JBoss Fuse/A-MQ - Fuse and A-MQ Version 6.3 GA is released!

Fuse and A-MQ 6.3 GA has just went out. Maybe, you would think this is just only a minor version release why should I care? Hold your thoughts on that! Because they have done a lot of improvements and also added many new features into this release.

Besides various bug fixes and making sure Fuse Fabric is much more stable. There are two major change in this version update:

New Tooling in JBoss Developer Studio (JBDS) 9.1 GA. Newer Apache Camel version – Camel v2.17. I was really impressed by the work put in to make developing Camel application much simpler. First is the installation of tooling itself. Now it has a all-in-one installer so you don't need to worry about which plugins you need to check. See the videos below to see the new "Getting Started" of Fuse 6.3.



And If you notice from the above video, the presentation of camel route in JBDS has also updated. It fixed some of the miss representation of logic and making it easier to read.

Old Camel Route
New Camel Route
On …

Fuse Integration Service - Setup JBDS and create first quickstart application

Before we go and start creating our first application, I want to show you how to setup your JBoss Developer Studio, create a small application from the quickstart example and then running it on Fuse Integration Service.

I am using JBoss Developer Studio version 9, you can find it here.
After download the

jboss-devstudio-9.0.0.GA-installer-eap.jar
double-click it, and start installing with default values.

After successful installation, we will need install the plugins for Fuse, on JBoss Central view, select software update, select enable early access.


And select JBoss Fuse Development for the plugin,


Click on install, and we are all set to go!

First thing first, we want to create a Fuse project to deploy on the base of Fuse Integration Service, which is OpenShift. If you have not installed it, please go back to my previous post for instructions. So on your JBDS, right click and start creating the project. Select new, maven project, if you have installed the plugin correctly, you should …