JBoss With MQ

How to configure JBoss with MQ

Introduction This document describes the integration with Web Sphere MQ Series from any J2EE 1.4 compliant application server without custom integration code with the help of JCA 1.5 compliant resource adapter provided by IBM. Web Sphere MQ implements the industry standard java Message Service (JMS) interface.

Assumptions This document describes many concepts and prerequisite knowledge of the following is considered essential: l

jBoss Application Server 4 or later

l

IBM Web Sphere MQ Server 7

l

Java Standard Edition

l

Java Enterprise Edition l

JCA

l

MDB

l

J2EE application servers

l

JMS

jBoss Application Server setup usually comes as ‘jboss-VERSION. packages which can be easily extracted to any desired location.

Configurations to Use WebSphere MQ Server as JMS Resource Provider Step 1: Installing and Configuring WebSphere MQ Server Install WebSphere MQ Server 7 using custom option. During the product selection phase we need to make sure ‘Java Extended Transaction’ option under ‘Java and Web Services ’ section is also selected to install XA-Transaction support for MQ Server which will be required later. Upon successful installation of MQ Server we will see

icon in our system tray which indicates that MQ Server up and running.

Step 2: Creating Queue Manager As a first step of our configuration we need to create a Queue Manager. Open a command prompt and navigate to the ‘bin’ directory which can be found under ‘WebSphere_MQ_Install_Dir’. We can create queue manager by executing following command;

Description: Above command will create a queue manager called ‘T24QM’. Step 3: Starting Queue manager To start the queue manager issue the following command;

Step 4: Creating Queues

Quick Guide to Jboss with MQ- Release R13.00 -Page 2 of 10 - (c) Temenos Systems 2013 05/07/2013

Once the queue manager is up and running User needs to create some local queue (physical destinations) where messages will get stored. To create queues issue the following command;

Description: First we have to enter into ‘MQSC’ shell (where we can manipulate our queue manager settings) then we create our queues. Above two ‘define’ statement will create ‘t24OFSQueue’ and ‘t24OFSReplyQueue’ destinations into queue manager ‘T24QM’. While defining queues if the queen names are not given inside quotes (‘) then it will be created in Uppercase. To exit from ‘MQSC’ shell just type ‘end’ and hit return. Step 5: Starting MQ Listener Finally we need to start a MQ listener for the queue manager to communicate with outside world, MQ listener can be started by executing following command;

Description: Above command will start MQ listener for queue manager (-m) ‘T24QM’, on port (-p) ‘1415’ and transport protocol will be used (t) ‘TCP’. After creating Queue manager, Queues and starting listener, following components need to be deployed in jboss Application server. 1) wmq.jmsra.rar 2) tocfT24ra-ra.rar 3) tocfOFSmessage-ejb.jar 4) mq-ds.xml 5) t24-ds.xml 6) ibmmq-destinations-service.xml 7) BrowserWeb.War 8) netty-3.2.4.jar

Configuration of Jboss Application server Step 1: Deploying WebSphere MQ JCA Adaptor To configure jBoss Application Server to communicate with the WebSphere MQ Server deploy a ‘WebSphere MQ JMS Adaptor’ called ‘wmq.jmsra.rar’ from ‘WebSphere_MQ_HOME/java/lib/jca’ directory to ‘[JbossInstallDirectory]\server\default\deploy]’directory.


Step 2: Deploying WebSphere MQ Connection Factory Jboss application server will use the WMQ connection factory to connect to WebSphere MQ Server so we need to copy following file into ‘[JbossInstallDirectory]\server\default\deploy]directory; mq-ds.xml

?xml version="1.0" encoding="utf-8"?> wmq/myFC true wmq.jmsra.rar javax.jms.ConnectionFactory 127.0.0.1 1415 T24QM 20

Step 3: Deploying ibmmq-destinations-service.xml As soon as we have deployed the above connection factory successfully, we can now reference WebSphere MQ Server local queues for our application. Copy ibmmq-destinations-service.xml file into ‘[JbossInstallDirectory]\server\default\deploy]’directory which should look similar to the one below;

Ibmmq-destinations-service.xml

name="jboss.jca:-

jboss.jca:service=RARDeployment,name='wmq.jmsra.rar' queue/t24OFSQueue javax.jms.Queue baseQueueManagerName=T24QM baseQueueName=t24OFSQueue < mbean code="org.jboss.resource.deployment.AdminObject" service=WASDestination,name=t24OFSReplyQueue">
name="jboss.jca:-

optional-attribute-name="RARName"> jboss.jca:service=RARDeployment,name='wmq.jmsra.rar'


queue/t24OFSReplyQueue javax.jms.Queue baseQueueManagerName=T24QM baseQueueName=t24OFSReplyQueue

Step 4: Deploying TOCF (EE) [ofsmessage-ejb.jar] As we know that TOCF (EE) is composed of four modules i.e. ‘OFSListener’, ‘OFSMessage’, ‘OFSDelivery’ and ‘TOCFPLUGIN’. If we deploy complete package it will result in many exceptions and errors on application server as each module require some specific configurations. For this example we only require ‘OFSMessage’ module. So we only extract ‘ofsmessage-ejb.jar’ and ‘tocfcommon.jar’ from package. Copy ‘tocfcommon.jar and netty-4.2.3.jar’ file on [JbossInstallDirectory]\server\default \lib’ directory. Then copy ‘ofsmessage-ejb.jar’ in file into ‘[JbossInstallDirectory]\server\default\deploy directory with following contents in ‘ejb.jar.xml’ and ‘jboss.xml’. ejb-jar.xml

OFSMessage OFSMessage Bean OFSMessageMDB com.temenos.tocf.ofsmessage.mdb.OFSMessageMDB javax.jms.MessageListener Bean javax.jms.Queue destination t24OFSQueue destinationType javax.jms.Queue useJNDI false


hostName 127.0.0.1 port 1415 queueManager T24QM T24 Queue Connection Factory jms/jmsConnectionFactory javax.jms.QueueConnectionFactory Container T24 JCA Connection Factory eis/t24ConnectionFactory com.temenos.tocf.t24ra.T24ConnectionFactory Container OFS reply queue queue/t24OFSReplyQueue javax.jms.Queue Container OFSMessageMDB * Required

Jboss.xml


wmq.jmsra.rar OFSMessageMDB Standard Message Inflow Driven Bean queue/t24OFSQueue jms/jmsConnectionFactory java:wmq/myFC queue/t24OFSReplyQueue queue/t24OFSReplyQueue eis/t24ConnectionFactory java:jca/t24ConnectionFactory Note: Above jboss.xml will map the activation specification defined in ejb-jar.xml to a jBoss Application Server. As we are using WMQ resource adapter we need to make sure that we use correct JNDI name in ‘jms/jmsConnectionFactory’ i.e. ‘java:wmq/myFC’.

Step 5: Deploying TAFC JCA Adaptor To configure jBoss Application Server to communicate with the T24 Application Server copy a ‘TAFC Adaptor’ called ‘tocfT24ra.rar’ to ‘[JbossInstallDirectory]\server\default\deploy]’directory.

Step 6: Deploying TAFC JCA Connection Factory Jboss application server will use the TAFC JCA connection factory to connect to T24 Application Server so we need to copy following file into ‘[JbossInstallDirectory]\server\default\deploy]’directory; t24-ds.xml:-

jca/t24ConnectionFactory tocfT24ra-ra.rar com.temenos.tocf.t24ra.T24ConnectionFactory 127.0.0.1


51164 true OFS_SOURCE=BROWSERTC 9087

Test Configurations We can verify configurations up to this point by putting messages on our ‘t24OFSQueue’ and check whether ‘OFSMessageMDB’ gets activated and pos t message to T24 and see the response in ‘t24OFSReplyQueue’. We need to open a command prompt on system where MQ server is installed and navigate to ‘bin’ directory of ‘Websphere_MQ_Install_Dir’ and apply following command but Ensure that jboss is in running state and jbase_agent listening to port number 51164.

We can verify the response by this command ‘amqsget.exe t24OFSReplyQueue’ from ‘WebSphere_MQ_Install_Dir/bin’ directory. Or follow the below steps 1) Navigate to WebSphere MQ Explorer. 2) Expand IBM Web sphere option in left pane . 3) Click on Queue Manager (T24QM) under that click on Queues option. 4) In right side pane select t24OFSReplyQueue and you can see the response in that. You can also notice output on T24 jbase_agent screen if it is running in debug mode; For Eg: Jbase_agent –p 51164 –L2

Important Note:


If this test passes we can simply deploy BrowserWeb.war defined in next step. If any exceptions occurred on this stage, we need to rectify the problem before we move onto next step.

Step 7: Deploying BrowserWeb.war To deploy T24 Browser copy the BrowserWeb.war file into ‘jboss\server\default \server’ directory including the below changes to ‘WEBINF/jboss-web.xml’.

Jboss-web.xml jca/t24ConnectionFactory com.temenos.tocf.t24ra.T24ConnectionFactory java:jca/t24ConnectionFactory jms/jmsConnectionFactory javax.jms.ConnectionFactory java:wmq/myFC queue/t24OFSQueue javax.jms.Queue queue/t24OFSQueue queue/t24OFSReplyQueue javax.jms.Queue queue/t24OFSReplyQueue

After configuring above component Start jboss (by clicking run.bat) and start jbase_ agent listening to port number specified in t24ds.xml (jbase_agent –p 51164) login to T24.


Resources Using WebSphere MQ Server with jBoss Application Server 4.. http://www.jboss.org/community/wiki/UsingWebSphereMQSeriesWithJBossASPart4


JBoss With MQ

Recommend Documents