How to write a message to queue from C samples?

For sending a message to queue from C samples under mq instalation we need to do the following steps:

export MQSERVER=SVRCONN.CHANNEL/TCP/'127.0.0.1(1416)'
export MQSAMP_USER_ID=user
./opt/mqm/samp/bin/amqsputc QUEUE.NAME QMGR.NAME

On Windows it is necessary to add enviroment variable:
MQNOREMPOOL=1


Important links:

• https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.con.doc/q017020_.htm
• https://www.ibm.com/support/knowledgecenter/es/SSFKSJ_8.0.0/com.ibm.mq.con.doc/q016990_.htm

How to create a IBM MQ Client Library using SSL for transmision? (PART II-II)

1. Emitir un certificado para una aplicación cliente en C

Cada aplicación debe tener su propio certificado con un nombre distinguido. Cada nombre distinguido debe ser único en la red del Websphere MQ.

1.1. Crear la llave del repositorio para la aplicación

Cambiar el directorio donde se encuentra localizado la llave del repositorio donde será creado /application:

user@user-vbox:~/code/ssl$ mkdir applicationuser@user-vbox:~/code/ssl$ cd application/user@user-vbox:~/code/ssl/application$  

Y emitir el siguiente comando para crear la llave de la base de datos de la aplicación:

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqckm -keydb -create -db myapp.kdb -type cms -stash
A password is required to access the source key database.
Please enter a password:

1.2. Crear el certificado de solicitud

Introduce el siguiente comando:

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqckm -certreq -create -db myapp.kdb -type cms -dn "CN=myAppName,O=sysEnterprise,OU=sysDeparment,L=Mexico,C=MX" -label "ibmwebspheremquser" -file myapp.req

A password is required to access the source key database.

Please enter a password:

1.3. Transferir la solicitud

Transferir el archivo de solicitud del certificado myapp.req para el directorio dodne se encuentra localizado los archivos CA.

user@user-vbox:~/code/ssl/application$ cp myapp.req /home/user/code/ssl/appCAdir/

1.4. Firmar la aplicación con el certificado

Ejecutar siguiente comando:

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -cert -sign -db appCA.kdb -label "appCAcertificate" -expire 365 -format ascii -file myapp.req -target myapp.cer

1.5 Transferir el certificado firmado

Transferir el certificado firmado, myapp.cer y el certificado publico de CA de regreso /application

user@user-vbox:~/code/ssl/appCAdir$ cp myapp.cer /home/user/code/ssl/application/user@user-vbox:~/code/ssl/appCAdir$ cp appCAcertfile.cer /home/user/code/ssl/application/

1.6. Agregar el certificado CA

Agregar el certificado a un repositorio llave de la aplicación:

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqckm -cert -add -db myapp.kdb -type cms -file appCAcertfile.cer -label "theCAcert"
A password is required to access the source key database.
Please enter a password:

1.7. Recibir el certificado firmado

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqckm -cert -receive -db myapp.kdb -type cms -file myapp.cer

A password is required to access the source key database.

Please enter a password:

1.8. Ejecutar una aplicación ejemplo

1.8.1. Crear el canal SVRCONN que use SSL

Iniciar el gestor de colas si no esta ya ejecutándose:

user@user-vbox:~/code/ssl/application$ strmqm appqmgr01

Una definición apropiada del canal SVRCONN debe de crearse. Esto se puede lograr en cualquier directorio: 

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqsc appqmgr01

DEFINE CHANNEL(MY.SEC.SVRCONN.CHL) CHLTYPE(SVRCONN) TRPTYPE(TCP) SSLCAUTH(REQUIRED) SSLCIPH(RC4_MD5_US)

END

1.8.2. Iniciar el listener

Si el listener no esta activo en el gestor de colas:

user@user-vbox:~/code/ssl/application$ /opt/mqm/bin/runmqsc appqmgr01

DEFINE CHANNEL(MY.SEC.SVRCONN.CHL) CHLTYPE(SVRCONN) TRPTYPE(TCP) SSLCAUTH(REQUIRED) SSLCIPH(RC4_MD5_US)

END

1.8.2. Agregar variable de entorno

user@user-vbox:~/code/ssl/application$ MQSSLKEYR=/home/user/code/ssl/applicationuser@user-vbox:~/code/ssl/application$ export MQSSLKEYRuser@user-vbox:~/code/ssl/application$ echo $MQSSLKEYR

/home/user/code/ssl/application

user@user-vbox:~/code/ssl/application$

1.8.3. Codigo de programa en C para enviar un mensaje

   

1.8.3. Compilación del programa en GCC

gcc -m64 -o PutSample PutSample.c -I/opt/mqm/inc -L/opt/mqm/lib64 -Wl,-rpath=/opt/mqm/lib64 -Wl,-rpath=/usr/lib64 -lmqic

(EN REVISION)

Otros enlaces:

• https://github.com/osanchezh/mqclientssl-app
• https://docs.oracle.com/cd/E19909-01/817-3729/examples.html
• https://docs.oracle.com/cd/E19509-01/820-3503/ggfai/index.html

Best regards,

How to create a IBM MQ Client Library using SSL for transmision? (PART I-II)

1. Ambiente de desarrollo 

• Ubuntu 16.04 
• IBM Message Queue 7.5 

2. Aplicación empleando SSL, creación de una Autoridad de Certificación. 
2.1. Crear una llave para el repositorio CA 
Crear un directorio, y dentro del directorio crear el archivo con la llave del repositorio:
user@user-vbox:~/code/ssl$ mkdir appCAdir
user@user-vbox:~/code/ssl$ cd appCAdir/
user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -keydb -create -db appCA.kdb -type cms

Ingresando los comandos se solicitara crear una contraseña y deberá ingresar para usar la llave CA del repositorio.

2.2. Crear un certificado personal CA certificado

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -cert -create -db appCA.kdb -type cms -label "appCAcertificate" -dn "CN=appSysCAName,O=sysEnterprise,OU=sysDeparment,L=Mexico,C=MX" -expire 1000 -size 1024

-expires: define la cantidad de dias de expiracion del certificado

2.3 Extraer el certificado CA

Extraer el certificado CA en un archivo llamado appCAcertfile.cer, el cual transferiremos después a los repositorios del gestor de colas y cliente de la aplicación.

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -cert -extract -db appCA.kdb -type cms -label "appCAcertificate" -target appCAcertfile.cer -format ascii

2.4 Emisor de un certificado para un gestor de colas

Cada gestor de colas en la infraestructura debe tener su propio certificado, con su propio nombre distinguido (DN), El DN debe ser único con la red del Websphere MQ.

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/crtmqm appqmgr01
There are 89 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager created.
Directory '/var/mqm/qmgrs/appqmgr01' created.
The queue manager is associated with installation 'Installation1'.
Creating or replacing default objects for queue manager 'appqmgr01'.
Default objects statistics : 74 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/strmqm appqmgr01
There are 89 days left in the trial period for this copy of WebSphere MQ.
WebSphere MQ queue manager 'appqmgr01' starting.
The queue manager is associated with installation 'Installation1'.
5 log records accessed on queue manager 'appqmgr01' during the log replay phase.
Log replay for queue manager 'appqmgr01' complete.
Transaction manager state recovered for queue manager 'appqmgr01'.
WebSphere MQ queue manager 'appqmgr01' started using V7.5.0.2.

2.4.2 Crear la llave del repositorio para el gestor de colas

Cambiar la localización del directorio donde el archivo con la llave del repositorio es creado: /repository

user@user-vbox:~/code/ssl$ mkdir repositoryuser@user-vbox:~/code/ssl$ cd repository/

Y es seguido del siguiente comando para crear con la llave de la base de datos para el gestor colas:

user@user-vbox:~/code/ssl/repository$ /opt/mqm/bin/runmqckm -keydb -create -db appqmgr.kdb -type cms -stash

Después de ingresar el comando se solicitara ingresar la contraseña.

2.4.3 Crear el certificado de respuesta para solicitud

Generar el certificado de solicitud para el gestor de colas, a partir de llave privada.

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -certreq -create -db appqmgr.kdb -type cms -dn "CN=appqmgr01,O=sysEnterprise,OU=sysDeparment,L=Mexico,C=MX" -label "ibmwebspheremqappqmgr" -file appqmgr.req

  

Después de ingresar el comando se solicitara ingresar la contraseña.

2.4.4 Transferir la solicitud

Para transferir el archivo de solicitud del certificado appqmgr.req, APRA el directorio donde el archivo CA se encuentra localizado. Es necesario cambiar al directorio:

user@user-vbox:~/code/ssl/repository$ ls
appqmgr.kdb  appqmgr.rdb  appqmgr.req  appqmgr.sth
user@user-vbox:~/code/ssl/repository$ pwd
/home/user/code/ssl/repository
user@user-vbox:~/code/ssl/repository$ mv appqmgr.req /home/user/code/ssl/appCAdir/

2.4.5 Firmar el certificado del gestor colas

Ejecutando el siguiente comando:

user@user-vbox:~/code/ssl/appCAdir$ /opt/mqm/bin/runmqckm -cert -sign -db appCA.kdb -label "appCAcertificate" -expire 365 -format ascii -file appqmgr.req -target appqmgr.cer

2.4.6 Transferir el certificado firmado CA

Transferir el certificado firmado appqmgr.cer y el certifcado public appCAcertfile.cer, a /repository.

user@user-vbox:~/code/ssl/appCAdir$ mv appqmgr.cer /home/user/code/ssl/repository/

user@user-vbox:~/code/ssl/appCAdir$ cp appCAcertfile.cer /home/user/code/ssl/repository/

2.4.7 Agregar el certificado CA

Agregar el certificado publico de CA al repositoriod e llaves del gestor de colas:

user@user-vbox:~/code/ssl/repository$ /opt/mqm/bin/runmqckm  -cert -add -db appqmgr.kdb -type cms -file appCAcertfile.cer -label "theCAcert"  

 

2.4.8 Repositorio del certificado firmado

Recibir el certificado en la llave del repositorio del gestor de colas.

 user @user-vbox:~/code/ssl/repository$ /opt/mqm/bin/runmqckm -cert -receive -db appqmgr.kdb -type cms -file appqmgr.cer

2.5 Agregar la locación de la llave del queuemanager

user@user-vbox:~/code/ssl/repository$ /opt/mqm/bin/runmqsc appqmgr01
5724-H72 (C) Copyright IBM Corp. 1994, 2011.  ALL RIGHTS RESERVED.
Starting MQSC for queue manager appqmgr01.

ALTER QMGR SSLKEYR('/home/user/code/ssl/repository/appqmgr')
     1 : ALTER QMGR SSLKEYR('/home/user/code/ssl/repository/appqmgr')
AMQ8005: WebSphere MQ queue manager changed.
END
     2 : END
One MQSC command read.
No commands have a syntax error.
All valid MQSC commands were processed.

Aqui termina la parte uno de 2 articulos de creación de certificados en IBM MQ.

Best regards,

Useful MQSC scripts for IBM Message Queue (Part I)

I have been caught by the time, after some years ago, my knowledge of configuration of IBM Message Queue is not being in practice because spending 2 hours trying to configure Channel Security the remembrance of how doing it stuck me.

I have decided to conserve some memories of script of configuration and this is the first part.

1. Backup and recovery script:

	dmpmqcfg -m [QUEUE_MANAGER] > BACKUP_FILE.mqsc
	runmqsc [QMNAME] < BACKUP_FILE.mqsc > logfile.txt 2>&1

view raw BACKUP_RESTORE_QMGR.sh hosted with ❤ by GitHub

2. Remove security to the channel

	RUNMQSC <QUEUEMANAGER>
	ALTER QMGR CHLAUTH(DISABLED)
	REFRESH SECURITY TYPE(CONNAUTH)
	END

view raw REMOVE_SECURITY_CHANNNELMQ.sh hosted with ❤ by GitHub

Important Links:

• https://www.ibm.com/support/knowledgecenter/en/SSFKSJ_8.0.0/com.ibm.mq.adm.doc/q117770_.htm

Best regards,

Missing libraries on installation of IBM Message Broker and Message Queue (Part I)

I am going back to IBM Message Queue and Message Broker, after some years, returning to old school, I have decided to publish this time some memories of working around and by now the following libraries are required to install the ibm middleware on a Centos 7 Machine:

	#!/bin/sh
	# List of libraries in Centos machine
	sudo yum install system-config-users
	sudo yum install ld-linux.so.2
	sudo yum install libgcc_s.so.1
	sudo yum install libstdc++.so.6
	sudo yum install libXtst.i686
	sudo yum install xulrunner.i686
	sudo yum install ld-linux.so.2
	sudo yum install libgcc_s.so.1
	sudo yum install libcanberra-gtk2.i686
	sudo yum install libcanberra-gtk3.i686
	sudo yum install libcanberra-gtk3.i686
	sudo yum install libcanberra-devel.i686
	#add 17102016
	sudo yum install packagekit-gtk3-module
	sudo yum install packagekit-gtk3-module
	sudo yum install PackageKit-gtk3-module
	#add
	sudo yum install ksh
	sudo yum install libstdc++.so.5
	sudo yum install compat-libstdc++*

view raw centos7_install_ibm.sh hosted with ❤ by GitHub

  Best regards,

How I do implement Request/Response pattern using SpringFramework and Weblogic?

Spring Framework has a lot of modules that could be implemented on several projects, On common questions in any projects is how to used it, The first factor that I could see is to Application Server well know, obviously your web application has to be deployed on an Web Application Server, we have to check the version and supporting jars to run your application, If your Application Server run up 1.5 JEE, a good choice will be Spring Framework, This small article try to getting started to first used spring jms module.

First you have to configure your Application Context:

	<?xml version="1.0" encoding="UTF-8" ?>
	<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xmlns:context="http://www.springframework.org/schema/context" xmlns:p="http://www.springframework.org/schema/p"
	xmlns:tx="http://www.springframework.org/schema/tx"
	xmlns:jms="http://www.springframework.org/schema/jms"
	xmlns:util="http://www.springframework.org/schema/util"
	xmlns:int="http://www.springframework.org/schema/integration"
	xmlns:int-jms="http://www.springframework.org/schema/integration/jms"
	xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.2.xsd
	http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx-3.2.xsd
	http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.2.xsd
	http://www.springframework.org/schema/integration http://www.springframework.org/schema/integration/spring-integration-2.2.xsd
	http://www.springframework.org/schema/util http://www.springframework.org/schema/util/spring-util-3.2.xsd
	http://www.springframework.org/schema/jms http://www.springframework.org/schema/jms/spring-jms-3.2.xsd
	http://www.springframework.org/schema/integration/jms http://www.springframework.org/schema/integration/jms/spring-integration-jms.xsd">
	<beans profile="DEV,TEST,PROD">
	<util:properties id="jndi_prop" location="file:///system/config/app-jndi.properties"/>
	<context:property-placeholder properties-ref="jndi_prop"/>
	<context:annotation-config/>
	<bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
	<property name="connectionFactory" ref="connectionFactory" />
	<property name="destinationResolver" ref="jmsDestinationResolver" />
	<property name="pubSubNoLocal" value="true" />
	<property name="pubSubDomain" value="false" />
	<property name="defaultDestination" ref="xmlMarshallerRequestQueue" />
	<property name="explicitQosEnabled" value="true" />
	</bean>
	<bean id="jndiTemplate" class="org.springframework.jndi.JndiTemplate">
	<property name="environment">
	<props>
	<prop key="java.naming.factory.initial">#{jndi_prop['java.naming.factory.initial']}</prop>
	<prop key="java.naming.factory.url.pkgs">#{jndi_prop['java.naming.factory.url.pkgs']}</prop>
	<prop key="java.naming.provider.url">#{jndi_prop['java.naming.provider.url']}</prop>
	<prop key="java.naming.security.principal">#{jndi_prop['java.naming.security.principal']}</prop>
	<prop key="java.naming.security.credentials">#{jndi_prop['java.naming.security.credentials']}</prop>
	</props>
	</property>
	</bean>
	<bean id="connectionFactory" class="org.springframework.jndi.JndiObjectFactoryBean">
	<property name="jndiTemplate">
	<ref bean="jndiTemplate" />
	</property>
	<property name="jndiName" value="#{jms_prop['jms.connection.factory.jndi.name']}" />
	</bean>
	<bean id="cachingConnectionFactory"
	class="org.springframework.jms.connection.CachingConnectionFactory">
	<property name="targetConnectionFactory" ref="connectionFactory" />
	<property name="sessionCacheSize" value="10" />
	</bean>
	<bean id="jmsTransactionManager" class="org.springframework.jms.connection.JmsTransactionManager">
	<property name="connectionFactory" ref="cachingConnectionFactory" />
	</bean>
	<bean id="jmsDestinationResolver"
	class="org.springframework.jms.support.destination.JndiDestinationResolver">
	<property name="jndiTemplate">
	<ref bean="jndiTemplate" />
	</property>
	<property name="cache" value="true" />
	<property name="fallbackToDynamicDestination" value="false" />
	</bean>
	<bean id="lineBusinessReplyQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
	<property name="jndiTemplate">
	<ref bean="jndiTemplate" />
	</property>
	<property name="jndiName" value="#{jms_prop['jms.queue.jndi.name.lineBusinessreply']}" />
	</bean>
	<bean id="lineBusinessRequestQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
	<property name="jndiTemplate">
	<ref bean="jndiTemplate" />
	</property>
	<property name="jndiName" value="#{jms_prop['jms.queue.jndi.name.lineBusinessrequest']}" />
	</bean>
	<bean id="lineBusinessErrorQueue" class="org.springframework.jndi.JndiObjectFactoryBean">
	<property name="jndiTemplate">
	<ref bean="jndiTemplate" />
	</property>
	<property name="jndiName" value="#{jms_prop['jms.queue.jndi.name.lineBusinesserror']}" />
	</bean>
	<bean id="lineBusinessMessageErrorBrowser" class="mx.com.company.jms.ErrorMessageBrowser">
	<property name="queue" ref="lineBusinessErrorQueue" />
	<property name="jmsTemplate" ref="jmsTemplate" />
	<property name="transactionManager" ref="jmsTransactionManager" />
	</bean>
	</beans>
	</beans>

view raw app-context-jms.xml hosted with ❤ by GitHub

After configurate your xml file you will have to inject a browser of Message Queue:

	/* */ package mx.com.company.jms;
	/* */
	/* */ import java.io.PrintStream;
	/* */ import java.util.ArrayList;
	/* */ import java.util.Enumeration;
	/* */ import java.util.List;
	/* */ import javax.jms.JMSException;
	/* */ import javax.jms.Message;
	/* */ import javax.jms.ObjectMessage;
	/* */ import javax.jms.Queue;
	/* */ import javax.jms.QueueBrowser;
	/* */ import javax.jms.Session;
	/* */ import javax.jms.TextMessage;
	/* */ import org.springframework.jms.connection.JmsTransactionManager;
	/* */ import org.springframework.jms.core.BrowserCallback;
	/* */ import org.springframework.jms.core.JmsTemplate;
	/* */ import org.springframework.transaction.annotation.Isolation;
	/* */ import org.springframework.transaction.annotation.Propagation;
	/* */ import org.springframework.transaction.annotation.Transactional;
	/* */
	/* */ @Transactional
	/* */ public class ErrorMessageBrowser
	/* */ {
	/* */ private JmsTemplate jmsTemplate;
	/* */ private Queue queue;
	/* */ private JmsTransactionManager transactionManager;
	/* */
	/* */ @Transactional(isolation=Isolation.DEFAULT, propagation=Propagation.REQUIRED, rollbackFor={JMSException.class})
	/* */ public int contarMensajes()
	/* */ throws JMSException
	/* */ {
	/* 39 */ int count = ((Integer)this.jmsTemplate.browse(this.queue, new BrowserCallback()
	/* */ {
	/* */ public Integer doInJms(Session session, QueueBrowser browser) throws JMSException {
	/* 42 */ Enumeration enumeration = browser.getEnumeration();
	/* 43 */ int counter = 0;
	/* 44 */ while (enumeration.hasMoreElements()) {
	/* 45 */ Message msg = (Message)enumeration.nextElement();
	/* 46 */ System.out.println(String.format("\tFound : %s", new Object[] { msg }));
	/* 47 */ counter++;
	/* */ }
	/* 49 */ return Integer.valueOf(counter);
	/* */ }
	/* */ })).intValue();
	/* */
	/* 52 */ System.out.println(String.format("\tThere are %s messages", new Object[] { Integer.valueOf(count) }));
	/* 53 */ return count;
	/* */ }
	/* */ @Transactional(isolation=Isolation.DEFAULT, propagation=Propagation.REQUIRED, rollbackFor={JMSException.class})
	/* */ public List<String> obtenerTextMessages() throws JMSException {
	/* 57 */ List count = (List)this.jmsTemplate.browse(this.queue, new BrowserCallback()
	/* */ {
	/* */ public List<String> doInJms(Session session, QueueBrowser browser) throws JMSException {
	/* 60 */ Enumeration enumeration = browser.getEnumeration();
	/* 61 */ List lstText = new ArrayList();
	/* 62 */ while (enumeration.hasMoreElements()) {
	/* 63 */ Message msg = (Message)enumeration.nextElement();
	/* 64 */ if ((msg instanceof TextMessage))
	/* */ {
	/* 66 */ TextMessage tm = (TextMessage)msg;
	/* 67 */ String mensaje = tm.getText();
	/* 68 */ lstText.add(mensaje);
	/* */ }
	/* 70 */ System.out.println(String.format("\tFound : %s", new Object[] { msg }));
	/* */ }
	/* 72 */ return lstText;
	/* */ }
	/* */ });
	/* 75 */ System.out.println(String.format("\tThere are %s messages", new Object[] { count }));
	/* 76 */ return count;
	/* */ }
	/* */
	/* */ public List<Message> obtenerMessageException() throws JMSException {
	/* 80 */ List count = (List)this.jmsTemplate.browse(this.queue, new BrowserCallback()
	/* */ {
	/* */ public List<Message> doInJms(Session session, QueueBrowser browser) throws JMSException {
	/* 83 */ Enumeration enumeration = browser.getEnumeration();
	/* 84 */ List lstText = new ArrayList();
	/* 85 */ while (enumeration.hasMoreElements()) {
	/* 86 */ Message msg = (Message)enumeration.nextElement();
	/* */
	/* 88 */ if ((msg instanceof ObjectMessage))
	/* */ {
	/* 90 */ ObjectMessage om = (ObjectMessage)msg;
	/* 91 */ Object objeto = om.getObject();
	/* 92 */ if ((objeto instanceof MessageException))
	/* 93 */ lstText.add(msg);
	/* */ }
	/* 95 */ System.out.println(String.format("\tFound : %s", new Object[] { msg }));
	/* */ }
	/* 97 */ return lstText;
	/* */ }
	/* */ });
	/* 100 */ System.out.println(String.format("\tThere are %s messages", new Object[] { count }));
	/* 101 */ return count;
	/* */ }
	/* */
	/* */ public void setJmsTemplate(JmsTemplate jmsTemplate)
	/* */ {
	/* 108 */ this.jmsTemplate = jmsTemplate;
	/* */ }
	/* */
	/* */ public JmsTemplate getJmsTemplate() {
	/* 112 */ return this.jmsTemplate;
	/* */ }
	/* */
	/* */ public void setQueue(Queue queue) {
	/* 116 */ this.queue = queue;
	/* */ }
	/* */
	/* */ public Queue getQueue() {
	/* 120 */ return this.queue;
	/* */ }
	/* */
	/* */ public void setTransactionManager(JmsTransactionManager transactionManager) {
	/* 124 */ this.transactionManager = transactionManager;
	/* */ }
	/* */
	/* */ public JmsTransactionManager getTransactionManager() {
	/* 128 */ return this.transactionManager;
	/* */ }
	/* */ }

view raw queuebrowser.java hosted with ❤ by GitHub

Now you can Inject the Request/Response in any Service, this had getting easier a MQ Implementation.


Best Regards,