| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Client connect to 2 MQ Servers |
« View previous topic :: View next topic » |
| Author |
Message
|
| gbaddeley |
 Posted: Wed Oct 15, 2008 4:35 pm Post subject: |
 |
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| dkeister wrote: |
I realize the jenchao is a first time poster so hope this won't confuse the issue.
I have the scenario where I want to be able to connect to a queue manager without having defined either entries in the AMQCLCHL.TAB or supplied MQSERVER settings.
I use MQCONNX call and specify the relevant information in the MQCNO structure. That way, my application prompts the user for:
- Server Channel Connection Name (SYSTEM.AUTO.SVRCONN is a convenient default but may require a specific, named SVRCONN)
- Connection Name which takes the format
{server machine name or IP address}(Port#) with localhost often a good default.
I can prompt for these parameters and establish a client connection to any host that will allow it without needing to have to predefine settings.
As I said, this is probably not what you would want for the average user, but might be useful for cases where you never know who you may need to connect to.
Also, this allows simultaneous connection to multiple queue managers if you are careful. |
You will also need to set the Transport Type attribute in the MQCD structure pointed to by MQCNO.
It is not a good idea to use SYSTEM.xxx SVRCONN channels. These should be set with MCAUSER('nobody') anyway, making them unusable.
Define your own SVRCONN channel with a specfic name and set the MCAUSER to a local userid that is in a group that has the minimum required authorities in OAM to use MQ.
_________________
Glenn |
|
| Back to top |
|
 |
| dkeister |
| Posted: Thu Oct 16, 2008 5:49 am Post subject: |
|
|
Disciple
Joined: 25 Mar 2002
Posts: 184
Location: Purchase, New York
|
Good points gbaddeley.
I hope that people writing MQ applications understand and appreciate the value of default objects (for easily getting started) and the implications of using them (security is one).
I value this forum for getting sound practice information like what you provided.
_________________
Dean Keister |
|
| Back to top |
|
|
| gbaddeley |
| Posted: Thu Oct 16, 2008 3:02 pm Post subject: |
|
|
Jedi Knight
Joined: 25 Mar 2003
Posts: 2538
Location: Melbourne, Australia
|
| dkeister wrote: |
Good points gbaddeley.
I hope that people writing MQ applications understand and appreciate the value of default objects (for easily getting started) and the implications of using them (security is one).
I value this forum for getting sound practice information like what you provided. |
Default objects should *never* be used by applications, eg. SYSTEM.DEFAULT.LOCAL.QUEUE. They are merely templates (ie. set default values) for defining properly named application specific objects.
_________________
Glenn |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
