| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Windows client communicating with Linux server |
« View previous topic :: View next topic » |
| Author |
Message
|
| wschutz |
 Posted: Thu Nov 17, 2005 8:13 am Post subject: |
 |
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Keith --
you'll remember that in a client MQCONN, if you specify "*QMGR1", this means:
search the channel table for a QMNAME of QMGR1, but ignore the actual name of the queue manager you get connected to (ie, they don't need to match).
As compared to "QMGR1", which would need to match BOTH the QMNAME in the channel table AND the actual qmanager you get connected to....
_________________
-wayne |
|
| Back to top |
|
 |
| KeeferG |
| Posted: Thu Nov 17, 2005 8:17 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
See, I knew it would come to me 
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| pranav_kavi |
| Posted: Thu Nov 17, 2005 7:15 pm Post subject: Windows client communicating with Linux server |
|
|
Novice
Joined: 15 Nov 2005
Posts: 16
Location: Bangalore
|
Answering to Wayne's q,I have checked in the .TAB file and the reqd q manager name is present.
One more q is tat,isnt .TAB method a bit tedious, as the there needs to be a copy of the .TAB file on the client machines tat needs to communicate with the server????
Thanx...
_________________
kavitha r |
|
| Back to top |
|
|
| KeeferG |
| Posted: Fri Nov 18, 2005 2:30 am Post subject: |
|
|
Master
Joined: 15 Oct 2004
Posts: 215
Location: Basingstoke, UK
|
I guess it depends on how many client systems you have and how you roll out the client applications. Its not normally too much of an issue.
MQCONNX - Coded in application. Usually gets the appropriate config from user defined file that needs to be deployed with application. Application can connect to multiple queue managers. My personal favourite for production code.
MQCONN - A little simpler to code as normal connection. Requires channel table file generated by MQ to be deployed with application and appropriate registry/environment variables set. Application can connect to multiple queue managers. Most widely used solution for production ready applications in my experience.
MQSERVER - Uses identicle application as the MQCONN solution. Application can connect to single queue manager. Overides the channel table file. Most widely used in light client applications and intitial development.
Any body else have thoughts on this.
_________________
Keith Guttridge
-----------------
Using MQ since 1995 |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Nov 18, 2005 2:47 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
MQSERVER - simple, but no ability to change "defaults", ie max message size, specify channel exits, etc ...
if you have a reliable file server, you can have a channel table mounted on a shared drive and point to that.
Also, now with the new (v6) java client, you can specify the channel table as an ftp destination:
| Code: |
java.net.URL chanTab2 = new URL("ftp://ftp.server/admdata/ccdt2.tab");
factory.setCCDTURL(chanTab2); |
_________________
-wayne |
|
| 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
|
|
|
|
