MQSeries.net :: View topic - Trouble with Remote Queue Concept and JMS

dant · Posted: Fri Apr 01, 2005 1:48 pm Post subject:

Hello all,

I am confused about the JMS abstraction of the MQ objects. From what I can tell, one creates one QCF (QueueConnectionFactory) for each QueueManager one has. Well, assuming this is true, and say I have a QueueManager with 2 local queues and one remote queue, I am not sure if you create 3 JMS Queues (Two for local, one for remote).

Essentially, I have two QueueManagers running on my local machine, one on port 1414, the other on 1415. This is being done for sandbox purposes and development. Eventually my application will have one QueueManager that is accessed via JMS, and the other QueueManager will belong to another non JMS system.

I have a script that I used to create the JMS administerd object with the JMSAdmin tool. It looks like this:

<script>
echo def qcf(xQCF) QMGR(QMX) > ivtsetup.scp
echo def q(xProductionQ) qu(X.PROD) QMGR(QMX) >> ivtsetup.scp
echo def q(xTrainingQ) qu(X.TRAIN) QMGR(QMX) >> ivtsetup.scp
echo def q(xRemoteQueue) qu(Y.PROD) QMGR(QMX) >> ivtsetup.scp

echo def qcf(yQCF) QMGR(QMY) >> ivtsetup.scp
echo def q(yQ) qu(Y.PROD) QMGR(QMY) >> ivtsetup.scp

</script>

In a program that has access to the JNDI namespace where these JMS administered objects reside, what JMS objects do I need to send a message to the remote defined queue, Y.PROD?

Essentially, I would imagine I need the xQCF to get the connection, session, etc, but can you use the connections gained from xQCF to write a message to yQ?

Is this right?

[edit] Or is it just as simple as using the yQCF to write to yQ? I wasn't sure if I was supposed to create a QCF and Q for an MQ Server that won't be accessed via JMS. Perhaps just keeping references to other MQServers in the JNDI namespace is totally legit. Again I am not sure if one creates only JMS Queues that are defined as local within MQ vs. also defining JMS Queues for remote queues as well.

TIA.