|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
[Solved] Using IDOC parser |
« View previous topic :: View next topic » |
Author |
Message
|
elvis_gn |
Posted: Sun Jul 31, 2005 10:21 pm Post subject: [Solved] Using IDOC parser |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi,
I am trying to make use of the IDOC parser and after a lot of trials and errors and help from previous posts on this site, i think i have got it working.
The problem now is that, I have two flat files, one which comes with the IBM support pack and one which I received from the client.
When i put the IBM sample the message is parsed but for my sample it is not done correctly.
I noticed that the message set,message type and message format are NULL in the Properties for my sample but for the IBM sample it is populated with the correct names.
When i removed the DC segments(data part) from the IBM sample it starts failing too. So it gives an impression that the data contained information of which message set to select..
Does anyone have any idea on which fields are effecting the proper parsing.
Last edited by elvis_gn on Tue Aug 02, 2005 7:54 pm; edited 1 time in total |
|
Back to top |
|
 |
Ramphart |
Posted: Tue Aug 02, 2005 2:14 am Post subject: |
|
|
 Disciple
Joined: 21 Jul 2004 Posts: 150 Location: South Africa, JHB
|
hi,
when I parse an INCOMING IDOC I do the following:
- InputNode (Message Domain = BLOB) I don't set anything else
- then I wire it to a ResetContentDescriptor and set the following:
1. Message Domain = IDOC (Click Resest Message Domain)
2. Message Set = E5A9J5S09I001 ---> your message set ID (Click Resest Message Set)
3. Message Type (Leave this Blank)
4. Message Format = CWF (Click Resest Message Format)
when creating an outgoing IDOC:
SET OutputRoot.Properties.MessageSet = 'E5A9J5S08C001';
SET OutputRoot.Properties.MessageType = '';
SET OutputRoot.Properties.MessageDomain = 'IDOC';
Hope this helps _________________ Applications Architect |
|
Back to top |
|
 |
elvis_gn |
Posted: Tue Aug 02, 2005 7:54 pm Post subject: |
|
|
 Padawan
Joined: 08 Oct 2004 Posts: 1905 Location: Dubai
|
Hi Ramphart,
Thanks for the reply. As i had stated the IBM sample was parsing, hence I had to ask the client to provide another sample and it turned out that the problem was with the data they had provided.
Anyway you are right as I tried what you said too, but eventually I used the MQInput Node with the same parameters filled in. I also noticed that the message set does not have the Custom wire format of CWF set, it is given a blank, even though CWF is available for selection.
Thanks a lot. |
|
Back to top |
|
 |
|
|
 |
|
Page 1 of 1 |
|
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
|
|
|
|