| Author |
Message
|
| nelson |
 Posted: Sat Feb 09, 2013 9:52 pm Post subject: FileInput Node message identifier |
 |
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
Hi All,
Maybe this is a basic question, but I need to get a unique identifier after a file is read in a FileInput node, an equivalent to the MsgId of the MQ Header. I tried adding a MQ Header next to the FileInput node and set the property MsgId = MQMI_NONE, but it does not generate the MsgId (always get 0000..), (I don't know if this makes any sense). I have explored all the properties tree and the LocalEnvironment.File section but couldn't find any property for that purpose. I'm using WMB 8.0.0.1.
Does this property exist? or.. how can I get a unique message identifier?
Thanks in advance. |
|
| Back to top |
|
 |
| smdavies99 |
| Posted: Sun Feb 10, 2013 12:02 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I know this works for other nodes (like TCP & HTTP) so how about putting a TRace node after the file Input node and output the following
${Root}
${LocalEnvironment}
and see what you get.
_________________
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 |
|
|
| nelson |
| Posted: Sun Feb 10, 2013 1:53 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| smdavies99 wrote: |
I know this works for other nodes (like TCP & HTTP) so how about putting a TRace node after the file Input node and output the following
${Root}
${LocalEnvironment}
and see what you get. |
Thank you smdavies99, that's the way I did it, but can't figure out where the identifier is. Maybe the CreationTime? it's the only value that seems to work as an identifier. Am I missing some field? |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Sun Feb 10, 2013 2:41 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
One option that comes to my mind is that you will generate MsgId with ESQL UUIDAS* functions if you don't find one in our message tree after FileInput - node.
And if I'm not totally wrong, many of the output -nodes will create identifier if it missing and if you need to store it somewhere you can perhaps find it from the message trees after the output -node. I think InfoCenter will tell you exactly path.
--
Marko |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun Feb 10, 2013 2:50 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You said you used an MQ output node. Did you also check New MessageId checkbox in the MQOutput node properties? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| nelson |
| Posted: Sun Feb 10, 2013 11:37 am Post subject: |
|
|
Partisan
Joined: 02 Oct 2012
Posts: 313
|
| marko.pitkanen wrote: |
One option that comes to my mind is that you will generate MsgId with ESQL UUIDAS* functions if you don't find one in our message tree after FileInput - node.
--
Marko |
Marko, thanks a lot! this information was very helpful. Finally I got a message identifier doing this:
| Code: |
DECLARE MsgId CHAR;
SET MsgId = UUIDASCHAR; |
Thanks all for your suggestions. |
|
| Back to top |
|
|
|
|
