| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Client appl connecting with MQSERVER without Qmgr name |
« View previous topic :: View next topic » |
| Author |
Message
|
| KAKEZ |
 Posted: Thu Sep 25, 2003 12:57 am Post subject: Client appl connecting with MQSERVER without Qmgr name |
 |
|
Centurion
Joined: 10 Oct 2002
Posts: 117
|
Hi,
reference to the manual Websphere MQ Clients page 148 item 'Using MQSERVER' I understand that:
- if you define the client channel for instance by:
MQSERVER=svrconn-name/TCP/host-IP-adress(1415)
and
- if client appli call MQCONN with field QmgrName="" (blanc)
the connection is made to the QMGR for which the listener listening on port 1415 is running to
Is that right?
If yes, that's interesting because that's a mean to let the client appli connect to a qmgr without having to know the name of the Qmgr it is connecting to - this operation is made automatic - we only have to play with the listeners and the ports on which they are listening.
thanks for opinions about that
Jack |
|
| Back to top |
|
 |
| bower5932 |
| Posted: Thu Sep 25, 2003 9:49 am Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
| The blank queue manager name means to use the default queue manager. If your default qmgr is listening on port 1415, things work in your scenario. However, if you have another qmgr listening on port 1415, you'll end up with a 2058 error. |
|
| Back to top |
|
|
| KAKEZ |
| Posted: Thu Sep 25, 2003 11:26 pm Post subject: |
|
|
Centurion
Joined: 10 Oct 2002
Posts: 117
|
Hi bower,
thanks for replying,
- but in case where there is no default qmgr defined on the server?
are you sure the client connection is impossible even on the qmgr on which the listener is listening on port 1415?
- that would be a good solution for me: I would like to free the client application from having to know the qmgr name to connect to whithin the MQCONN call - and so make this connection automatic
Jack |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Sep 26, 2003 4:48 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| KAKEZ wrote: |
that would be a good solution for me: I would like to free the client application from having to know the qmgr name to connect to whithin the MQCONN call - and so make this connection automatic
|
If you don't to hard code a queue manager name inside your code, then use parameters from a configuration file, a command line option, an environment variable, or a database lookup.
But I think it's a bad idea to give the client application no way of specificing which particular queue manager to connect to. That is, hard coding an empty name is as bad as hardcoding any other name. If you use any of the techniques above, you can still do what you want by specifying an empty parameter.
_________________
I am *not* the model of the modern major general. |
|
| 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
|
|
|
|
