| Author |
Message
|
| GAKD |
 Posted: Tue Jun 30, 2015 9:15 am Post subject: FileOutputNode is not able to save the $ExceptionList |
 |
|
Novice
Joined: 25 Jun 2015
Posts: 14
|
I am not sure If I am wrong with this concept . Please correct me.
In the Error Handling functionality I am reading the exception list and manipulating something and storing some data in the Environment but at the end I am just sending the outputRoot = InputRoot as such so that I can save the ExceptionList into a log file which is handled using FileOutputNode.
-> In the 'basic' properties I have given Directory and Filename, Mode is set to write directly to output file and append if the same file existis.
->In the 'Request' property I have given the 'Data location' as $ExceptionList so that the incoming InputExceptionList gets saved to the log file which is not happening.
The ExceptionList is not getting saved in the fileOutputNode. Am I doing something wrong is the configuration wrong ? |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Jun 30, 2015 9:23 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| ExceptionList doesn't have a parser. |
|
| Back to top |
|
|
| GAKD |
| Posted: Tue Jun 30, 2015 10:17 am Post subject: Ok . Its the Datalocation that the FileOutputNode supposed |
|
|
Novice
Joined: 25 Jun 2015
Posts: 14
|
| "ExceptionList doesn't have a parser" - How does this matter ? Its part of the incoming tree and if you check the FileOutNode 'datalocation' property you have options to point any part of the tree . |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jun 30, 2015 10:30 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The job of a parser is to read a bitstream and turn it into a logical message tree.
It is also to read a logical message tree and turn it into a bitstream. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jun 30, 2015 3:08 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
To put it in different words: Without a parser attached your tree is not serializable and the system can't write it to the file... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Wed Jul 01, 2015 4:46 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
You need to navigate through the exception list, get the information you want and put it in a way a parser can serialize it. For example, you can populate a XML message with the exception information.
This is an example of a plugin that makes it easy to summarize the exception list tree into a variable in the Environment tree, then you can do whatever you want with it. |
|
| Back to top |
|
|
|
|
