Kbase 20310: How Does SonicMQ Explorer Use the Connect ID?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/28/2001 |
|
SUMMARY:
This solution applies to Progress SonicMQ Version 2000.x and 3.x. It
explains how SonicMQ Explorer uses the connect ID entered by the user
when connecting to a broker.
EXPLANATION:
A connection to a SonicMQ broker from an administrative client
(in Explorer or the Admin shell) uses an automatically generated and
assigned connect ID such as $ISYS-Admin1, $ISYS-Admin2, etc. The
value you enter in the ConnectID field when you connect to a broker
in Explorer is used for the Topic and Queue Connections created when
you create JMS client sessions connected to that broker in Explorer,
as you might do for test purposes.
For example, if you enter the connect ID "explr" when connecting to a
broker in Explorer, when you create a QueueSession under the same
Message Broker node in the tree structure on the left hand pane of
Explorer, the new connection will have connectID "Queueexplr".
Similarly, a TopicSession created under the same broker node uses
connect ID "Topicexplr".
Additional Queue Sessions created under the same broker node share the
single QueueConnection, and additional Topic Sessions created under
the same broker node share the single TopicConnection. To create a
session that uses a separate connection to the broker in SonicMQ
Explorer, create a new administrative connection to the same broker
using a different connect ID, and create the session under the
resulting new broker node.
References to Written Documentation:
SonicMQ Installation and Administration Guide, Chapter 3,
"Graphical Installation Tool"