| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Sysplex and shared inbound channels with MQ clients |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Wed Apr 09, 2008 5:39 am Post subject: Sysplex and shared inbound channels with MQ clients |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I have never used a Parallel Sysplex, let alone with MQ V6, however it has been suggested that we might use one.
I understand the basics of shared queues and how the messages can be picked up on either side of the sysplex.
What I can't work out is the impact on MQ client connections. Most of our applications hosted on Windows or Unix connect directly to a given (mainframe) queue manager name.
The IP address and port comes from the amqclchl.tab file, or is explicitly configured in the case of our Java or JMS clients.
With a Sysplex, the two sides run queue managers with different names, so surely if a generic port was used then the connections would not always arrive at the expected queue manager?
How could we balance the client connections over a Sysplex when they specify a particular queue manager name?
Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Wed Apr 09, 2008 6:41 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
The application program MQCONNects to either a queue manager or a queue-sharing group name.
This is fairly well explained in the WMQ V6 Application Programming Reference. Take a look at MQCONN. Look for the the queue manager name (which can be a queue-sharing group name).
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Toronto_MQ |
| Posted: Wed Apr 09, 2008 8:16 am Post subject: |
|
|
Master
Joined: 10 Jul 2002
Posts: 263
Location: read my name
|
As Bruce points out, you use the QSG name instead of the queue manager name, in situations where you cannot leave it blank to pick up the default queue manager.
We use sysplex distributor (think sophisticated vIP) to route the connections.
Hope this helps,
Steve |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Apr 09, 2008 10:32 pm Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
OK thanks. I'll look into QSG names.
If we share queues, are there any constraints on message size, queue size and so on which might need consideration? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Apr 10, 2008 2:28 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| zpat wrote: |
OK thanks. I'll look into QSG names.
If we share queues, are there any constraints on message size, queue size and so on which might need consideration? |
Depending on which version you are.... IIRC On 5.3.1  messages over 64K were written to DB2 and you'd take a performance hit.
You might want to look up that corresponding section for V6. 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Apr 10, 2008 2:36 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| fjb_saper wrote: |
| IIRC On 5.3.1 messages over 64K were written to DB2 and you'd take a performance hit. |
Uhm. I think in v5.3 you couldn't put messages bigger than 64k onto a shared queue.
And in v6 you can, because they're written to DB2.
But maybe I'm entirely wrong here.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Apr 10, 2008 6:23 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
V5 limited msgs on shared queues to 63k, and non-persistent only. V6 allows 100meg messages, persistent and non-persistent.
Msgs bigger than 63k are stored as blobs in DB2 structures, with pointers in the shared queue. All this is invisible to the application. As with most things mainframe, there is little overhead. Shared queues live in a coupling-facility (CF). CF's are fiber chanel attached, so light-speed data transfer.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| 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
|
|
|
|
