|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQIPT routing designs |
« View previous topic :: View next topic » |
Author |
Message
|
rconn2 |
Posted: Thu Apr 30, 2015 12:19 pm Post subject: MQIPT routing designs |
|
|
Voyager
Joined: 09 Aug 2007 Posts: 79 Location: MD, USA
|
I have a few general questions about best practices or trade-offs regarding setting up routes using the MQIPT pass-through server.
For Source Queue Managers A1, A2.. An; Destination Queue Managers B1, B2... Bn; all on different servers(IP's).
1. Many to One. Let's say A1, A2, A3 send messages to B1. Is it better to use a single route (a single port, say 20000) that routes to B1 such that A1, A2, A3 all connect to the MQIPT using port 20000? Or, is it better to set aside different ports for each so that A1 uses port 20000, A2, 20001, A3 20003?
2. One to Many. Is there a downside to using the exit whereby a single port can route to multiple queue managers depending on the channel name (there's a sample exit that uses the channel name string to map to a destination queue manager)?
So, A1 uses port 20000 and is routed to B1 or B2 or B3 etc. based on the channel name (for example, channels: B1.A1, B2.A2, B3.A3 -- the example has the best practice of source.destination backwards)? |
|
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
|
|
|
|