Author |
Message
|
mqlover |
Posted: Sun May 12, 2013 10:50 pm Post subject: Identify the source system that message was consumed by WMB |
|
|
Disciple
Joined: 25 Jul 2010 Posts: 176
|
Hi,
I have a front end from where the message ise sent and is consumed by WMB for further processing and is sent to AS400 m/c i.e backend.
I have DB logging which shows that the message reached WMB and was further passed down.
How do I make the front end know that WMB consumed the messages?
I initially thought of using COA or COD, but after searching through the forums found that its not a good practice.
In what other can I make the front end notify that the message was consumed by WMB?
Thanks |
|
Back to top |
|
 |
Esa |
Posted: Sun May 12, 2013 10:59 pm Post subject: Re: Identify the source system that message was consumed by |
|
|
 Grand Master
Joined: 22 May 2008 Posts: 1387 Location: Finland
|
mqlover wrote: |
How do I make the front end know that WMB consumed the messages?
I initially thought of using COA or COD, but after searching through the forums found that its not a good practice.
|
What is wrong with COD?
Or do you want to get notified only if the message was consumed successfully? Then you can send a PAN, but you must code it in the flow. After output terminal 2 of a FlowOrder node for example.
You may also want to edit the topic header and replace "Identify" with "Notify"... |
|
Back to top |
|
 |
smdavies99 |
Posted: Sun May 12, 2013 11:36 pm Post subject: Re: Identify the source system that message was consumed by |
|
|
 Jedi Council
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
|
Esa wrote: |
What is wrong with COD?
|
There is nothing wrong per-say with COD but will the sending system understand a COD message? That has always been the stumbling block when I've suggested this in the past. _________________ WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
Back to top |
|
 |
Vitor |
Posted: Mon May 13, 2013 5:23 am Post subject: Re: Identify the source system that message was consumed by |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
Esa wrote: |
What is wrong with COD? |
The problem where the original message turns up but the COD gets delayed on the back leg causing the original system to believe delivery has not taken place & initate some kind of retry. Duplicate messages and other tangles rapidly become possible.
If all you want is logging, i.e. the front end system is correctly reling on assured delivery, it's not a bad option. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|