| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Trigger Fileinput node in message broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Thu Nov 01, 2012 6:43 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| kimbert wrote: |
| @Vitor: I expect you were lulled into a false sense of security by the reassuring-looking XML declaration at the start of the file. I was. |
You can't believe everything you read.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| wbi_telecom |
| Posted: Thu Nov 01, 2012 11:15 am Post subject: |
|
|
Disciple
Joined: 15 Feb 2006
Posts: 188
Location: Harrisburg, PA
|
I would go with what kimbert suggested. That seems to me a much cleaner approach than my design. But if I were to implement my design on your message the custom delimiter would be the end tag of Catalog. Keep in mind that if there is a header before the repeating elements, your very first message would have it. Also you have to append the hex value of the end tag to the BLOB message in the next compute before you change the parser back to XMLNSC (which is why I prefer kimbert's design). Given the time and choice (both very hard to get where I work) I will go back and refactor my flows.
Cheers, |
|
| Back to top |
|
|
| jrsdm |
| Posted: Fri Nov 02, 2012 6:45 am Post subject: |
|
|
Apprentice
Joined: 24 Oct 2012
Posts: 27
|
Hi Kimbert,
Thanks for the suggestion.
I have already tried this but as my xml structure is somthing like this below the parsed record sequence not work for me.
It will read this as one whole message.
As the file in concern is 4 GB and what I understood from the documentation that fileinput node read the file and put into the mqsitransit and then read the record one by one or as whole depending on this setting of the node , In this case so memory is required.
Now I am confuse about that memeory is required when it process the message or when the file is read into the mqsitransit directory .
I have tried to match my structure with the salelist example of Large messaging sample.
My structure is
-saleEnvelope
-Salelist
-<Header>
</Header>
-<department1>
</department1>
-<department2>
</department2>
-<department3>
</department3>
-<department4>
</department4>
-<department5>
</department5>
</Salelist>
</SaleEnvelope>
Thanks |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Nov 02, 2012 8:05 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| I have already tried this but as my xml structure is somthing like this below the parsed record sequence not work for me. |
That is a completely different structure from the one that you posted earlier in this thread. Before I reply again, I want a clear statement of your project's requirements.
| Quote: |
As the file in concern is 4 GB and what I understood from the documentation that fileinput node read the file and put into the mqsitransit and then read the record one by one or as whole depending on this setting of the node , In this case so memory is required.
Now I am confuse about that memeory is required when it process the message or when the file is read into the mqsitransit directory . |
Did you actually read what I posted in my last post?
| Quote: |
| I have tried to match my structure with the salelist example of Large messaging sample. |
What does that mean? Do you actually have control over the format of the XML input file? If not, then what do you gain by experimenting with the SalesList example?
Finally, don't bother using -- to indent your XML. Use code tags - it's not hard. |
|
| Back to top |
|
|
| jrsdm |
| Posted: Fri Nov 02, 2012 9:14 am Post subject: |
|
|
Apprentice
Joined: 24 Oct 2012
Posts: 27
|
My bad, the client have gave me the exact xml as mentioned in the previous post which I need to parsed.
The Project requirement is :
1. Parsed the record on by one
2. Create different file for different departments
The XML file is apporx of 4GB.
Thanks |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Nov 02, 2012 2:34 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
In that case we are back in the same situation as before, and everything that I said remains true. Post again when you have tried what I suggested.
Last edited by kimbert on Sat Nov 03, 2012 2:14 pm; edited 1 time in total |
|
| Back to top |
|
|
| jrsdm |
| Posted: Sat Nov 03, 2012 4:48 am Post subject: |
|
|
Apprentice
Joined: 24 Oct 2012
Posts: 27
|
As suggested I have modified the flow and still it not parsed the record one by one it is parsed the whole file and then end.
I need to parse the record one by one .
I have tested with 10 MB file . |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Nov 03, 2012 7:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jrsdm wrote: |
| still it not parsed the record one by one it is parsed the whole file and then end. |
How do you know this? Because of the amount of memory being used? Because you can see the whole file in the debug window? Because you see only a single message being propagated in the user trace?
Not all of those are evidence. And I would want to see a user trace segment before I could offer more help.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| kimbert |
| Posted: Sat Nov 03, 2012 2:19 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
| Quote: |
| I have modified the flow and still it not parsed the record one by one it is parsed the whole file and then end. |
Like Vitor, I would like to know *how* you know these things. The WMB test team have tested exactly this scenario, and it works for them.
Please can you describe what tests you carried out, and what results you saw? |
|
| Back to top |
|
|
| jrsdm |
| Posted: Sat Nov 03, 2012 4:33 pm Post subject: |
|
|
Apprentice
Joined: 24 Oct 2012
Posts: 27
|
hi,
My flow for test was
Fileinputnode -> Mqoutput node
When I have done the settings as mentioned in the previous post then file is picked up and in the MQoutput there is only message (whole XML file)
My means of record by record->The mqoutput node contain the individual message of each department number(As mentioned in the XML)
If you say parsed record sequence what exactly it mean by you?
Thanks |
|
| Back to top |
|
|
| Vitor |
| Posted: Sat Nov 03, 2012 7:03 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jrsdm wrote: |
| If you say parsed record sequence what exactly it mean by you? |
At the risk of putting words in the mouth of my most worthy associate, I suspect he means the "parsed record sequence" record detection he recommended you use to parse the pseudo-XML you're using. If you're having to ask what it is, then I put it to you that your assertion:
| jrsdm wrote: |
| As suggested I have modified the flow |
is rather odd; if you don't know what it is how can you have modified to use it? If you do know what it is, why are you asking?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| jrsdm |
| Posted: Sun Nov 04, 2012 2:44 pm Post subject: |
|
|
Apprentice
Joined: 24 Oct 2012
Posts: 27
|
Here is the user trace:
Timestamps are formatted in local time, 300 minutes before GMT.
Trace written by version ; formatter version 7001 (build S700-FP01)
2012-11-04 17:37:27.128358 1908 UserTrace BIP4040I: The Execution Group ''Test'' has processed a configuration message successfully.
A configuration message has been processed successfully. Any configuration changes have been made and stored persistently.
No user action required.
2012-11-04 17:37:27.128705 1908 UserTrace BIP2638I: The MQ output node '.outputNode' attempted to write a message to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' connected to queue manager ''MB7QMGR''. The MQCC was '0' and the MQRC was '0'.
2012-11-04 17:37:27.128725 1908 UserTrace BIP2622I: Message successfully output by output node '.outputNode' to queue ''SYSTEM.BROKER.EXECUTIONGROUP.REPLY'' on queue manager ''MB7QMGR''.
2012-11-04 17:37:27.128898 1908 Information BIP2154I: Execution group finished with Configuration message.
A command response will be sent to the broker.
No user action required.
2012-11-04 17:38:35.219009 5820 UserTrace BIP3336I: ''FileInput'' node ''File Input'' in message flow ''Test'' is moving file ''C:\Jre\PayData (11).xml'' to directory ''C:\Jre\mqsitransitin''.
The ''FileInput'' node is about to move a file to a different directory. The node will not change the file's name.
No user action is necessary.
2012-11-04 17:38:35.219909 5820 UserTrace BIP3351I: File node ''File Input'' in message flow ''Test'' is opening file ''C:\Jre\mqsitransitin\0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml''.
The FileInput node opens the file to read input records.
No action is required.
2012-11-04 17:38:35.225353 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8cb0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.225421 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.225475 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '16777216'.
Element ''Type'' has been changed to '16777216'.
No user action required.
2012-11-04 17:38:35.225509 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''File''.
Element ''Name'' has been changed to ''File''.
No user action required.
2012-11-04 17:38:35.225593 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.225753 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.225776 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:35.225799 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''LastModified''.
Element ''Name'' has been changed to ''LastModified''.
No user action required.
2012-11-04 17:38:35.225898 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.225917 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.225936 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:35.225959 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Offset''.
Element ''Name'' has been changed to ''Offset''.
No user action required.
2012-11-04 17:38:35.225994 5820 UserTrace BIP4142I: Evaluating cniElementSet'IntegerValue'. Changing value from ''NULL'' to '0'.
Element ''IntegerValue'' has been changed to '0'.
No user action required.
2012-11-04 17:38:35.226020 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.226039 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.226058 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:35.226078 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Record''.
Element ''Name'' has been changed to ''Record''.
No user action required.
2012-11-04 17:38:35.226097 5820 UserTrace BIP4142I: Evaluating cniElementSet'IntegerValue'. Changing value from ''NULL'' to '1'.
Element ''IntegerValue'' has been changed to '1'.
No user action required.
2012-11-04 17:38:35.226123 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.226142 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.226161 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:35.226181 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Delimiter''.
Element ''Name'' has been changed to ''Delimiter''.
No user action required.
2012-11-04 17:38:35.226203 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.226222 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.226242 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:35.226261 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''IsEmpty''.
Element ''Name'' has been changed to ''IsEmpty''.
No user action required.
2012-11-04 17:38:35.226284 5820 UserTrace BIP4142I: Evaluating cniElementSet'BooleanValue'. Changing value from ''NULL'' to ''false''.
Element ''BooleanValue'' has been changed to ''false''.
No user action required.
2012-11-04 17:38:35.226314 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8cb0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:35.226333 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:35.226352 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '16777216'.
Element ''Type'' has been changed to '16777216'.
No user action required.
2012-11-04 17:38:35.226371 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Wildcard''.
Element ''Name'' has been changed to ''Wildcard''.
No user action required.
2012-11-04 17:38:35.227157 5820 UserTrace BIP3352I: ''FileInput'' node ''File Input'' in message flow ''Test'' is propagating record ''1'' obtained from file ''C:\Jre\mqsitransitin\0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml'' at offset ''0'' to terminal ''out''.
The FileInput node read a record from the file, and will propagate it to the named terminal.
No action is required.
2012-11-04 17:38:35.227203 5820 UserTrace BIP3907I: Message received and propagated to 'out' terminal of input node 'Test.File Input'.
2012-11-04 17:38:35.227474 5820 UserTrace BIP6063I: A parser of type ''Properties'' was created on behalf of node 'Test.File Input' to handle the input stream, beginning at offset '0'.
2012-11-04 17:38:35.228145 5820 UserTrace BIP6064I: A parser of type ''XMLNSC'' was created on behalf of node 'Test.File Input' to handle the input stream, beginning at offset '0'. The parser type was selected based on value ''XMLNSC'' from the previous parser.
2012-11-04 17:38:45.507217 5820 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Test.Trace'.
The trace node 'Test.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2012-11-04 17:38:45.509117 5820 UserTrace BIP2638I: The MQ output node 'Test.MQ Output' attempted to write a message to queue ''Q1'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2012-11-04 17:38:45.509128 5820 UserTrace BIP2622I: Message successfully output by output node 'Test.MQ Output' to queue ''Q1'' on queue manager ''''.
2012-11-04 17:38:45.519786 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8cb0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.519805 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.519813 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '16777216'.
Element ''Type'' has been changed to '16777216'.
No user action required.
2012-11-04 17:38:45.519821 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''File''.
Element ''Name'' has been changed to ''File''.
No user action required.
2012-11-04 17:38:45.520038 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520050 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520057 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:45.520065 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''LastModified''.
Element ''Name'' has been changed to ''LastModified''.
No user action required.
2012-11-04 17:38:45.520092 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520095 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520103 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:45.520107 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Offset''.
Element ''Name'' has been changed to ''Offset''.
No user action required.
2012-11-04 17:38:45.520114 5820 UserTrace BIP4142I: Evaluating cniElementSet'IntegerValue'. Changing value from ''NULL integer'' to '68296'.
Element ''IntegerValue'' has been changed to '68296'.
No user action required.
2012-11-04 17:38:45.520122 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520130 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520133 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:45.520141 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Record''.
Element ''Name'' has been changed to ''Record''.
No user action required.
2012-11-04 17:38:45.520149 5820 UserTrace BIP4142I: Evaluating cniElementSet'IntegerValue'. Changing value from ''NULL integer'' to '1'.
Element ''IntegerValue'' has been changed to '1'.
No user action required.
2012-11-04 17:38:45.520153 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520160 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520164 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:45.520168 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Delimiter''.
Element ''Name'' has been changed to ''Delimiter''.
No user action required.
2012-11-04 17:38:45.520175 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8d10, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520183 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520187 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '50331648'.
Element ''Type'' has been changed to '50331648'.
No user action required.
2012-11-04 17:38:45.520191 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''IsEmpty''.
Element ''Name'' has been changed to ''IsEmpty''.
No user action required.
2012-11-04 17:38:45.520198 5820 UserTrace BIP4142I: Evaluating cniElementSet'BooleanValue'. Changing value from ''unknown'' to ''true''.
Element ''BooleanValue'' has been changed to ''true''.
No user action required.
2012-11-04 17:38:45.520210 5820 UserTrace BIP4144I: Entered function 'cniCreateElementAsLastChild'(1969f0c0, ca8cb0, 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A', 'N/A').
Entered the specified function with the specified parameters.
No user action required.
2012-11-04 17:38:45.520214 5820 UserTrace BIP4145I: Exiting function 'cniCreateElementAsLastChild' with result: 'CCI_SUCCESS'(0).
About to exit the specified the function with the specified result.
No user action required.
2012-11-04 17:38:45.520221 5820 UserTrace BIP4142I: Evaluating cniElementSet'Type'. Changing value from '0' to '16777216'.
Element ''Type'' has been changed to '16777216'.
No user action required.
2012-11-04 17:38:45.520225 5820 UserTrace BIP4142I: Evaluating cniElementSet'Name'. Changing value from '''' to ''Wildcard''.
Element ''Name'' has been changed to ''Wildcard''.
No user action required.
2012-11-04 17:38:45.520481 5820 UserTrace BIP3356I: ''FileInput'' node ''File Input'' in message flow ''Test'' has reached the end of file ''C:\Jre\mqsitransitin\0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml'' at record number ''1'', file length ''68296'' and is propagating record an empty BLOB record to terminal ''EOD''.
The FileInput node has processed all the records from the file. It will propagate an empty record to the named terminal to indicate end of data.
No action is required.
2012-11-04 17:38:45.520500 5820 UserTrace BIP3907I: Message received and propagated to 'End Of Data' terminal of input node 'Test.File Input'.
2012-11-04 17:38:45.520610 5820 UserTrace BIP6063I: A parser of type ''Properties'' was created on behalf of node 'Test.File Input' to handle the input stream, beginning at offset '0'.
2012-11-04 17:38:45.520641 5820 UserTrace BIP6064I: A parser of type ''BLOB'' was created on behalf of node 'Test.File Input' to handle the input stream, beginning at offset '0'. The parser type was selected based on value ''NONE'' from the previous parser.
2012-11-04 17:38:46.183902 5820 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Test.Trace'.
The trace node 'Test.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2012-11-04 17:38:46.184322 5820 UserTrace BIP2638I: The MQ output node 'Test.MQ Output' attempted to write a message to queue ''Q1'' connected to queue manager ''''. The MQCC was '0' and the MQRC was '0'.
2012-11-04 17:38:46.184368 5820 UserTrace BIP2622I: Message successfully output by output node 'Test.MQ Output' to queue ''Q1'' on queue manager ''''.
2012-11-04 17:38:46.196384 5820 UserTrace BIP3350I: File node ''File Input'' in message flow ''Test'' is closing file ''C:\Jre\mqsitransitin\0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml''.
The FileInput node is closing the input file.
No action is required.
2012-11-04 17:38:46.196685 5820 UserTrace BIP3337I: The node ''File Input'' in message flow ''Test'' is deleting file ''0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml'' from directory ''C:\Jre\mqsitransitin''.
The node is about to delete an existing file.
No user action is necessary.
2012-11-04 17:39:00.335081 1908 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node '.InputNode'.
2012-11-04 17:39:00.335150 1908 UserTrace BIP6060I: Parser type ''Properties'' created on behalf of node '.InputNode' to handle portion of incoming message of length 0 bytes beginning at offset '0'.
2012-11-04 17:39:00.335166 1908 UserTrace BIP6061I: Parser type ''MQMD'' created on behalf of node '.InputNode' to handle portion of incoming message of length '364' bytes beginning at offset '0'. Parser type selected based on value ''MQHMD'' from previous parser.
2012-11-04 17:39:00.335198 1908 UserTrace BIP6061I: Parser type ''XMLS'' created on behalf of node '.InputNode' to handle portion of incoming message of length '229' bytes beginning at offset '364'. Parser type selected based on value ''XMLS'' from previous parser.
Threads encountered in this trace:
1908 5820
Last edited by jrsdm on Mon Nov 05, 2012 5:52 pm; edited 1 time in total |
|
| Back to top |
|
|
| kimbert |
| Posted: Mon Nov 05, 2012 1:53 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5543
Location: Southampton
|
|
| Back to top |
|
|
| mayheminMQ |
| Posted: Mon Nov 05, 2012 8:56 am Post subject: |
|
|
Voyager
Joined: 04 Sep 2012
Posts: 77
Location: UK beyond the meadows of RocknRoll
|
@jrsdm: There will be one msg in MQOutput node, though FileInput Node specified Record detection was set as Parsed Record Sequence, I suspect that the message model did not have the structure defined for MB to actually pick the message in blocks.
If nothing is specified, it will end up reading the whole thing and will send it out as one message which is what your user trace shows.
To create different files for different departments, you will have first create a base message model that will allow you to read the BIG message in blocks.. Do your parsing and propagate.. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Nov 05, 2012 9:50 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| jrsdm wrote: |
| Here is the user trace: |
And this shows one thing very clearly:
2012-11-04 17:38:45.507217 5820 UserTrace BIP4067I: Message propagated to output terminal for trace node 'Test.Trace'.
The trace node 'Test.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
...
2012-11-04 17:38:45.520481 5820 UserTrace BIP3356I: ''FileInput'' node ''File Input'' in message flow ''Test'' has reached the end of file ''C:\Harish\mqsitransitin\0e77cba9-3a01-0000-0080-f53f676aa8d7-PayData (11).xml'' at record number ''1'', file length ''68296'' and is propagating record an empty BLOB record to terminal ''EOD''.
The FileInput node has processed all the records from the file. It will propagate an empty record to the named terminal to indicate end of data.
No action is required.
[/quote]
So you have not modified the flow to use Parsed Record Sequence because it thinks there's only 1 record in the file.
Or you've made the modification and done it wrong.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
|
|
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
|
|
|
|
