| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| TimeOuts & using CorrelationID |
« View previous topic :: View next topic » |
| Author |
Message
|
| Mirage |
 Posted: Tue Nov 30, 2004 7:41 am Post subject: TimeOuts & using CorrelationID |
 |
|
Apprentice
Joined: 30 Nov 2004
Posts: 44
Location: IL
|
Hello,
I'm working on a message flow which uses a WBI JText Adapter to FTP the files to mainframe. The Requirement for the flow is to handle exceptions that occur in the process, say for example if there was an error in FTP'ing the file to Mainframe the error generated by JText Adapter should be caught in the flow and logged to DB.
If we give the ReplyToQueue name and queue manager name, JText Adapter will write the response(whether its a success or failure) setting the correlation id to message id of request.
Here are some of the details of the design we thought about.
1. In message flow, write the request message to JText adapter's request queue.
2. Store the MessageID.
[[Outside the Flow JText Adapter picks the message, processe's it and puts a success/failure message on the response queue.]]
3. Set a Timeout & within this timeout, use the MessageID to read a message out of response queue whose correlation id is matching. [[MQGET with correlation ID & Timeout]]
4. If there was a message then get the message, parse its contents to find success or failure. If there was no message there should have been a Time out exception thrown in the flow. Log the response.
Question: Is there a predefined node/ custom node available to perform this(MQGet-correlId&Timeout) task ?. If not can you suggest on how to achieve it.
Should I use Aggregate Nodes to achieve the Timeout functionality or Write a custom node with MQ Java API to use the MQ's inbuilt Timeout functionality.
Note: This functionality is actually provided by WBI MQ Adapter, so I'm wondering why it isnt provided in MessageBroker.
Thanks for the help and Please let me know your questions.
Cheers,
Raghu. |
|
| Back to top |
|
 |
| tej |
| Posted: Thu Dec 02, 2004 8:28 am Post subject: |
|
|
Novice
Joined: 18 Nov 2002
Posts: 20
|
The simplest way is to include the request and response in the message and keep the request portion unlatered in the reply. and compre the time stamp from that header. This should agreed by both ends
Tej |
|
| Back to top |
|
|
| JT |
| Posted: Thu Dec 02, 2004 11:17 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
| Quote: |
JText Adapter will write the response(whether its a success or failure) setting the correlation id to message
id of request. |
Is this true for all conditions? Are there situations where the adapter doesn't reply?
If the adapter always replies, can you wait to log your time-out event until you eventually receive the reply?
| Quote: |
| Is there a predefined node/ custom node available to perform this(MQGet-correlId&Timeout) task ?. |
Not one that's available "off the shelf". The MQGet plug-in (IA07 supportpac) does not have wait logic built in.
| Quote: |
| If not can you suggest on how to achieve it. |
I know there's been discussion/dis-agreement in the past amongst this site's members regarding the implementation of latency into a message flow, but like yourself we had a scenario where we had a need to create a MQGet plug-in with a configurable wait interval. Although it's been working without incident, we're prudent with it's use.
| Quote: |
Should I use Aggregate Nodes to achieve the Timeout functionality or Write a custom node with
MQ Java API to use the MQ's inbuilt Timeout functionality. |
I would suggest against using the Aggregate nodes for this purpose (although you certainly can accomplish what you want with them). As I'm sure you're aware, the objective of the Aggregate nodes is to merge the replies from multiple requests into a single message. Using the Aggregates's time-out feature, should a reply not return in time, is a ancillary benefit. I would go with developing a custom node. |
|
| Back to top |
|
|
| Mirage |
| Posted: Fri Dec 03, 2004 10:33 am Post subject: |
|
|
Apprentice
Joined: 30 Nov 2004
Posts: 44
Location: IL
|
Hi JT,
Thanks for your input on this. We've decided to go with a Custom node just like you said.
This is what we are planning to do.
By using the MQ's Java API we are building(coding is almost done) a custom node, which will take the MessageID, MQ response queue connection details and Timeout interval as input parameters. It'll monitor the queue for a message whose correlation id is matching the message id, if there is a message(success/failure) it'll be picked up and an XML message is build to pass to the next node. If there was no message, we catch the timeout exception and build an error XML message.
Do you think of anything that we are missing here ? any suggestions ?
I'm not sure about how to set the input parameters to the CustomNode dynamically in the messageflow. Can you give some info on this. ?
Thanks - Raghu.
| Quote: |
Is this true for all conditions? Are there situations where the adapter doesn't reply?
If the adapter always replies, can you wait to log your time-out event until you eventually receive the reply?
|
Yes, as long as the Adapter is up it'll write the response to the response queue. |
|
| Back to top |
|
|
| kalyanMD |
| Posted: Fri Jun 01, 2007 2:03 am Post subject: Re: TimeOuts & using CorrelationID |
|
|
Novice
Joined: 03 Feb 2005
Posts: 14
Location: London UK
|
| Mirage wrote: |
Hello,
I'm working on a message flow which uses a WBI JText Adapter to FTP the files to mainframe. The Requirement for the flow is to handle exceptions that occur in the process, say for example if there was an error in FTP'ing the file to Mainframe the error generated by JText Adapter should be caught in the flow and logged to DB.
If we give the ReplyToQueue name and queue manager name, JText Adapter will write the response(whether its a success or failure) setting the correlation id to message id of request.
Here are some of the details of the design we thought about.
1. In message flow, write the request message to JText adapter's request queue.
2. Store the MessageID.
[[Outside the Flow JText Adapter picks the message, processe's it and puts a success/failure message on the response queue.]]
3. Set a Timeout & within this timeout, use the MessageID to read a message out of response queue whose correlation id is matching. [[MQGET with correlation ID & Timeout]]
4. If there was a message then get the message, parse its contents to find success or failure. If there was no message there should have been a Time out exception thrown in the flow. Log the response.
Question: Is there a predefined node/ custom node available to perform this(MQGet-correlId&Timeout) task ?. If not can you suggest on how to achieve it.
Should I use Aggregate Nodes to achieve the Timeout functionality or Write a custom node with MQ Java API to use the MQ's inbuilt Timeout functionality.
Note: This functionality is actually provided by WBI MQ Adapter, so I'm wondering why it isnt provided in MessageBroker.
Thanks for the help and Please let me know your questions.
Cheers,
Raghu. |
Hi Raghu,
Can I please get that bit of esql code that you are using for code page conversion for mainframe and the configuration file and business objects file that u r using to do an ftp thru JText adapter. As we are trying to convert code page on our message broker and Jtext is sending FTP files to AS400 but, at AS400 end files are not getting processed.
Regards,
Kalyan |
|
| 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
|
|
|
|
