| Author |
Message
|
| kevinf2349 |
 Posted: Tue Jun 02, 2009 5:06 am Post subject: |
 |
|
Grand Master
Joined: 28 Feb 2003
Posts: 1311
Location: USA
|
If the messages are so important why do they expire anyway?
I smell auditors in this mix somewhere. 
What is the real requirement here? Why would you want to keep all the messages if the business doesn't think them important enough to keep them around? Is it so that 'managers' can see how many attempts were made to do something rather than how many were successful? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jun 02, 2009 5:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kevinf2349 wrote: |
| If the messages are so important why do they expire anyway? |
I think we've established they're only important until the testing's been signed off....
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jun 02, 2009 5:56 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| I think we've established they're only important until the testing's been signed off.... |
I would think testing should replicate production.
_________________
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 |
|
|
| Vitor |
| Posted: Tue Jun 02, 2009 6:16 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bruce2359 wrote: |
| Quote: |
| I think we've established they're only important until the testing's been signed off.... |
I would think testing should replicate production. |
It seems reasonable enough that, during early testing, you'd want to keep a copy of the input messages so as to see what went into your app / broker flow / other component and tie it up to the actual results and/or stack trace / dump.
I agree that later on through the cycle you'd use a set up more closely aligned with production.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jun 02, 2009 7:04 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
| It seems reasonable enough that, during early testing, you'd want to keep a copy of the input messages so as to see what went into your app / broker flow / other component and tie it up to the actual results and/or stack trace / dump. |
Does sound reasonable. The design should contemplate the same requirement in production if a problem subsequently occurs in production.
Good design requires that test=qa=production.
_________________
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 |
|
|
| jeevan |
| Posted: Tue Jun 02, 2009 8:02 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| Vitor wrote: |
| bruce2359 wrote: |
| Quote: |
| I think we've established they're only important until the testing's been signed off.... |
I would think testing should replicate production. |
It seems reasonable enough that, during early testing, you'd want to keep a copy of the input messages so as to see what went into your app / broker flow / other component and tie it up to the actual results and/or stack trace / dump.
I agree that later on through the cycle you'd use a set up more closely aligned with production. |
Vitor is right ( as usual). We are trying to be safe to keep the copy of real input message.
in fact, my colleague who is supposed to develop the Tibco webservices, to receive message from a third party product in xml, has been told that the message he has to put is in binary format as we are not changing message consumer. So, he needs to see the input message.
Actually, there are a few more issues associated with this project which I will be posting later in future. We are very early stage and are more concern about the message and do a little POC.
I really thanks for all for the valuable suggestions and hope the same in future
Last edited by jeevan on Tue Jun 02, 2009 8:15 pm; edited 2 times in total |
|
| Back to top |
|
|
| jeevan |
| Posted: Tue Jun 02, 2009 8:04 pm Post subject: |
|
|
Grand Master
Joined: 12 Nov 2005
Posts: 1432
|
| bruce2359 wrote: |
| Quote: |
| I think we've established they're only important until the testing's been signed off.... |
I would think testing should replicate production. |
it is being done first time. So, once we know the format in test, we will continue the same in production. |
|
| Back to top |
|
|
| aditya.aggarwal |
| Posted: Wed Jun 03, 2009 12:46 am Post subject: |
|
|
Master
Joined: 13 Jan 2009
Posts: 252
|
A Very simple solution...
I think you want to capture a reply message and trying to understand the reply message format.
If you want to browse the message temoprary from the queue... Follow the below steps.
Request-Reply: I.e. you are sending a request and getting a reply back and you want to capture the reply message to understand its format.
1. Stop RCVR Channel at your queue manager
2. Send 10-15 Request
3. Stop application
4. Start rcvr channel
5. Broswe the message after its arrival in reply queue.
But ensure that you have all the commands handy and involve 1-2 people to perform this task. otherwise the message will expire from the queue.
Cheers,
Aditya |
|
| Back to top |
|
|
|
|
