MQSeries.net :: View topic

skysurfer · Posted: Mon Jun 10, 2002 4:22 pm Post subject:

JMS specifies that topic generally should be got via JNDI lookup and programmatically only temporaryTopic be created. However, JMS also has createTopic(String str) method in the TopicSession class and states that implementation be provider-specific.

Question 1--> I want to know how MQseries handle this. Is that MQseries createTopic(String str) only creates a temporary topic that will go away after this connection is closed?

Question 2 --> If answer to question 1 is yes (temporary), then does MQseries provide programmatic creation of topic that persists?

Question 3 --> Any tools or utility exists to see what topics a broker currently has?

Here are some of the information I read from Jguru but I don't know how MQseries works
--------------------------------------------------------------------------
How does a client create a topic (or a queue)?
Location: http://www.jguru.com/faq/view.jsp?EID=1188
Created: Nov 21, 1999
Author: Jerry Smith (http://www.jguru.com/guru/viewbio.jsp?EID=9)

In the section "Topic Management" the JMS specification states: "JMS does not define facilities for creating, administering, or deleting topics." In the JMS API, however, the QueueSession and TopicSession interfaces include createQueue() and createTopic(), respectively.

For now, it's likely that JMS implementations will vary with respect to static versus dynamic topic creation, as well as external topic administration and manipulation. It's possible that some implementations will require static topic creation in advance using external functionality, for example, a utility. Some JMS implementations include a complete system administration tool for topic and queue management. Some implementations will provide administrative APIs for programmatic control of resource management. Other implementations may provide basic facilities for, say, topic or queue creation on the fly, plus an administrative console for creation, deletion, and other management tasks, plus security management.

For example, some environments support dynamic look-up using JNDI, plus dynamic destination creation, if necessary:

...
try {
queue = (Queue) c.lookup(QUEUE);
}
catch (NamingException ne) {
try {
queue = session.createQueue(QUEUE);
c.bind(QUEUE, queue);
}
catch (Exception e) {
readyToSend = false;
closeConnection();
return;
}
}
...
In the previous code segment, c is a JNDI InitialContext object.