| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSeries Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| loudcfla |
 Posted: Fri Sep 09, 2005 6:24 am Post subject: MQSeries Client |
 |
|
Acolyte
Joined: 05 May 2002
Posts: 58
|
Hello,
I have a simple point to point topography. A QMGR on SUN and a QMGR on Z/OS connected by sender and reciever channles. So currenlty our web app sends a message to the SUN and that message is sent to the Mainframe/CICS and a reply is sent back.
If I wanted to bypass the QMGR on the SUN, from what I have read I would need an MQ Client and that Client could talk directly to the Mainframe. But I don't understand where would the Client do an MQPUT to build the message and how would the message get to the Mainframe?
Could someone explain this to me? |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Fri Sep 09, 2005 6:33 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
Right now, your application is using server bindings to connect to the solaris queue manager.
Once you install the MQClient on your app server, and install and configure the Client Attachment Facility on the mainframe, and resolve the security problems on the mainframe, then your app will make an Client connection to the mainframe queue manager.
The only part of your code that will change is the connection logic - and that may not change at all either - and what library you are linked against (unless you're using java).
Your app will do the MQPut directly to the queue on the mainframe qmgr, that is currently the destination of the remote queue def/alias/cluster queue on the SUN Qmgr.
Your app will need a local queue on the mainframe queue manager to receive it's replies, or you will need to (and this is silly!) make another client connection to the SUN qmgr and issue your MQGet from the queue there.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| wschutz |
| Posted: Fri Sep 09, 2005 6:35 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
| Quote: |
| If I wanted to bypass the QMGR on the SUN, from what I have read I would need an MQ Client and that Client could talk directly to the Mainframe. |
Your understanding is correct. You need a MQ feature on the mainframe (called the client attach feature), so check with your m/f guys that they have it (it's an extra charge above based mq fee).
| Quote: |
But I don't understand where would the Client do an MQPUT to build the message and how would the message get to the Mainframe?
|
You need to make definitions on the client side (and mainframe side) which tells the client how to attach to the mainframe (channel name, ip address ...). The application does MQPUTs and GETs as before, there's no change (except for speed, perhaps, since the MQPUts to the MF are now synchronious and might take longer than local puts). Be aware, that if you are doing 2 phase (XA) commits, the out of box client doesn't do that; you need the extended transaction client (which has some limitationd on how it works and is also a chargable offering).
I suggest browsing the MQ Clients manual .....
_________________
-wayne |
|
| 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
|
|
|
|
