| Author |
Message
|
| ruimadaleno |
 Posted: Tue May 20, 2014 8:30 am Post subject: Monitoring terminal events on soap reply node |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
i've read the documentation and made some tests in my environment but i just can't get it working 
I have a simple message flow
Soap Input ----> Route to Label ---> Operation Subflow (only one dummy compute node) --> Soap Reply
Requirement: i want to monitor messages that go in and out from the message flow
i've enabled the following events:
Soap Input: Transaction Start Event , default event filter, $Root on event payload , include bitstream data in payload checked default correlation properties, default Transaction properties
Soap Reply: Terminal Out Event , default event filter, $Root on event payload , include bitstream data in payload checked default correlation properties, default Transaction properties
Message flow is deployed to broker via BAR file. Monitoring is enabled after deploy by running mqsichangeflowmonitoring command.
I can see monitoring events from the Soap Input but no events from the soap reply node, why ? 
My Environment
WMB 8.0.0.4
Windows Server 2008R2 Standard
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue May 20, 2014 12:32 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
No idea why the SOAPReply is not emitting events.
As a workaround, you could try putting a Passthrough node just before the SOAPReply and monitoring its Out terminal.
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| Esa |
| Posted: Tue May 20, 2014 10:40 pm Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
'out' terminals emit events only when a message is propagated through them. I have a habit of wiring a Passthrough node after all out terminals that I want to monitor, if they are not wired to some processing node.
For SOAP Reply node, it's possible to monitor the 'in' terminal, too, if you don't like Passthough nodes. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed May 21, 2014 3:16 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
i've changed the monitoring configuration in SOAP Reply node.
Instead of using the "Terminal Out" event i'm capturing the "Terminal In" event.
I've deployed the message flow, send some messages to it with SOAPUI and start getting events in monitoring 
For some reason the "Terminal Out" event is not being captured  i'm sure that message flow run's till the end , passing a message throughout the SOAP Reply out terminal (tested with SOAPUI and getting response)
Any ideias why i'm getting this behaviour ? 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| Esa |
| Posted: Wed May 21, 2014 3:20 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| ruimadaleno wrote: |
For some reason the "Terminal Out" event is not being captured i'm sure that message flow run's till the end , passing a message throughout the SOAP Reply out terminal (tested with SOAPUI and getting response)
Any ideias why i'm getting this behaviour ? |
So you did wire a passthrough node from SOAP Reply.out? |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed May 21, 2014 3:38 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| Esa wrote: |
| ruimadaleno wrote: |
For some reason the "Terminal Out" event is not being captured i'm sure that message flow run's till the end , passing a message throughout the SOAP Reply out terminal (tested with SOAPUI and getting response)
Any ideias why i'm getting this behaviour ? |
So you did wire a passthrough node from SOAP Reply.out? |
Hi Esa,
no extra nodes were added to message flow. I changed the "Event source" property of the monitoring configuration for node SOAP Reply from "Terminal Out" to "Terminal In".
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| Esa |
| Posted: Wed May 21, 2014 3:52 am Post subject: |
|
|
Grand Master
Joined: 22 May 2008
Posts: 1387
Location: Finland
|
| As I said earlier, an 'out' terminal won't emit events if the messages don't pass it. And messages are not propagated to a terminal that is not wired anywhere. To make the SOAP Reply nodes 'out' terminal send events you need to wire a Passthrough node from it. |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Wed May 21, 2014 5:05 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
| Esa wrote: |
| As I said earlier, an 'out' terminal won't emit events if the messages don't pass it. And messages are not propagated to a terminal that is not wired anywhere. To make the SOAP Reply nodes 'out' terminal send events you need to wire a Passthrough node from it. |
It makes perfect sense ! thank you so much for your explanation 
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
|
|
