| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Using dynamic subscription queues in JMS Pub/Sub through WAS |
« View previous topic :: View next topic » |
| Author |
Message
|
| hilltops |
 Posted: Thu Jan 15, 2009 9:26 am Post subject: Using dynamic subscription queues in JMS Pub/Sub through WAS |
 |
|
Centurion
Joined: 01 Mar 2006
Posts: 112
|
I am trying to configure an Websphere Application Server (WAS) to use an MQ Pub/Sub broker (V6.0) using dynamic subscription queues. The manual suggests that this can be done in one of two ways:
1) Programmatically using setBrokerSubQueue() and specifying and argument ending in the asterisk character, such as SYSTEM.JMS.ND.TRADER.*. Thus,
setBrokerSubQueue(SYSTEM.JMS.ND.TRADER.*)
OR
2) Administratively using JMS Admin tool and specifying a value for BROKERSUBQ that ends in a * on the Topic Connection Factory.
Here is the manual description:
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzaw.doc/uj24850_.htm
| Quote: |
Configuring non-durable subscribers
You can set the non-durable subscriber queue name property in either of the following ways:
Use the WebSphere MQ JMS administration tool (for JNDI retrieved objects) to set the BROKERSUBQ property
Use the setBrokerSubQueue() method in your program
For non-durable subscriptions, the queue name you provide should start with the following characters:
SYSTEM.JMS.ND.
To select a shared queue approach, specify an explicit queue name, where the named queue is the one to use for the shared queue. The queue that you specify must already physically exist before you create the subscription.
To select the multiple queue approach, specify a queue name that ends with the * character. Subsequently, each subscriber that is created with this queue name creates an appropriate dynamic queue, for exclusive use by that particular subscriber. MQ JMS uses its own internal model queue to create such queues. Therefore, with the multiple queue approach, all required queues are created dynamically.
When you use the multiple queue approach, you cannot specify an explicit queue name. However, you can specify the queue prefix. This enables you to create different subscriber queue domains. For example, you could use:
SYSTEM.JMS.ND.MYDOMAIN.*
The characters that precede the * character are used as the prefix, so that all dynamic queues that are associated with this subscription have queue names that start with SYSTEM.JMS.ND.MYDOMAIN. |
Presumably if one can use the JMS admin tool to configure the TCF for dynamic queues, it also be possible to configure the same on the WAS interface and specifying a string of the format SYSTEM.JMS.ND.MYDOMAIN.*. Unfortunately, the WAS validation routine does not like strings ending in * and such a value cannot be specified for the Broker Subscription Queue field.
Has anybody encountered this problem?
Thankx |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Thu Jan 15, 2009 3:55 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
The other way you could do this for non durable subscriptions would be by using a little bit of coding.
First have your session create a dynamic queue that you prefix with SYSTEM.JMS.ND.MYDOMAIN.* This should return a Destination/queue name to your app. You can now build the topic uri using the information to have the messages for the subscription sent to that queue....
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
