| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| OTMA Primary/Secondary transactio processing issues |
« View previous topic :: View next topic » |
| Author |
Message
|
| smeunier |
 Posted: Mon Dec 19, 2005 10:32 am Post subject: OTMA Primary/Secondary transactio processing issues |
 |
|
Partisan
Joined: 19 Aug 2002
Posts: 305
Location: Green Mountains of Vermont
|
We are trying to us the MQ to IMS bridge(OTMA) to send IMS transaction to IMS and receive a reply. We have this working with a Primary IMS transaction sending a reply back through MQ. This works great. We are now trying to uses this facility again, where a Primary transaction is being sent to IMS(verified it gets there and executes). The Primary IMS transaction cuts a Secondary IMS transaction, which would be the sender of the reply. This reply never comes back through the OTMA bridge. Is there a procedure that needs to be followed when using Primary/Secondary transaction processing in order for the Secondary to reply back through OTMA? Any help is greatly appreciated.
I will post to another forum as well to make sure it get to the right exposure. |
|
| Back to top |
|
 |
| DryHeatDave |
| Posted: Thu Mar 23, 2006 3:06 pm Post subject: |
|
|
Apprentice
Joined: 21 Mar 2006
Posts: 28
Location: Phoenix, AZ
|
I know that's a pain. My solution was to NOT respond via OTMA. I have Requests coming in via OTMA & Responses going back directly (MQPUT) into remote queues.
_________________
SCJP2
IBM Cert. Solutions Designer for Websphere MQ 5.3
Not a certified mainframer - just been doing it a real long time. |
|
| Back to top |
|
|
| JT |
| Posted: Fri Mar 24, 2006 9:45 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| So you obviously aren't concerned with maintaining any of the MQMD values (correlid, expiry, etc.) for the reply messages. |
|
| Back to top |
|
|
| DryHeatDave |
| Posted: Mon Mar 27, 2006 12:43 pm Post subject: |
|
|
Apprentice
Joined: 21 Mar 2006
Posts: 28
Location: Phoenix, AZ
|
We use (almost) SOAP-compatible MQ messages, including an envelope, that contains the data we need, in order to maintain msg id etc.
Either -
1. Send requests via a hub & perform enrichment/transformation in the hub, to populate the relevant envelope fields.
2. prepopulate the envelope, pre-assigning a message id (rather than letting MQ do it).
_________________
SCJP2
IBM Cert. Solutions Designer for Websphere MQ 5.3
Not a certified mainframer - just been doing it a real long time. |
|
| 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
|
|
|
|
