| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Pattern "MQ one-way (for IDoc)" doesn't work for m |
View previous topic :: View next topic |
| Author |
Message
|
| mwe |
 Posted: Wed Mar 23, 2011 6:59 am Post subject: Pattern "MQ one-way (for IDoc)" doesn't work for m |
 |
|
Newbie
Joined: 23 Mar 2011
Posts: 1
|
Hey folks,
I tried to use the “MQ one-way (for IDoc)” SAP Pattern with the standard BOMMAT03 IDoc and couldn't get it to work. The IDoc was not parsed successfully by an MQInput-Node. 
First, my environment:
Broker Version 7.0.0.2 running on SuSE Linux Enterprise Server 11. My Toolkit is on Version: 7.0.0.2 (Build id: 7.0.0.2-20101130_1524).
The Websphere Adapter for SAP Version is 7.0.0.3 .
Here's what I have done:
First I’ve created the pattern, just giving the connection details for my SAP Testsystem and the place of my sapjca3 JAR and DLL file and everything else as default.
Then I created the configurable service with the idocpassthrough.inadapter.configurableservice file in my MQ Explorer and set up the credentials with mqsisetdbparms.
To see the pattern in action I ran the Adapter Connection Wizard to discover an IDoc (BOMMAT03) in my SAP Testsystem. I let the wizard create a fresh Message Set just for that adapter. (leaving all settings to default as mentioned in the other thread.)
To see if the IDoc could be parsed I created a new flow with just one MQInput node and a pass through node just for debugging.
I set all the parsing properties as advised in the pattern description:
Message domain: Data Object
Message set: the one with the BOMMAT03 Message Set
Message type: SapBommat03
Message format: SAP ALE IDoc
Finally I created the BAR file with the INADAPTER file, the two message flows, two XSDZIP files (one for each message set) and one JAR files. (the code of the java compute node)
When I sent an IDoc to my Broker I could see the message in my IDOCPassThroughFlow message flow correctly parsed into the generic message set.
After the java compute the message was correctly put into OutputRoot.BLOB.BLOB and the destination was set to BOMMAT03 (MQ Queue name depending on the IDocType-field). After receiving the message in the other flow the DataObject is empty.
The was no exception or error message during debugging. I couldn't find anything helping or suspicious in the user trace.
Where did I make the mistake?
Did anyone else had the same problem and found a solution to this?
Or do you use the pattern but made any steps in a different way?
Please tell me if more information or traces are needed. Thank you for any help!
If you are interested in a project interchange zip please contact me.
Regards,
Matthias |
|
| Back to top |
|
 |
| cc-77 |
| Posted: Thu Aug 04, 2011 2:38 am Post subject: Did your problem has been resolved? |
|
|
Newbie
Joined: 23 Jun 2009
Posts: 1
|
| Hi Did your problem has been resolved? I encounter the same problem now. |
|
| Back to top |
|
|
| whydieanut |
| Posted: Thu Sep 22, 2011 2:02 am Post subject: |
|
|
Disciple
Joined: 02 Apr 2010
Posts: 186
|
I have the same sample working fine for me.
But I did notice one thing;
When I tried to parse the Generic Object in the first flow itself, using CREATE with PARSE and specifying the specific IDOC Message Set, the debugger kept showing the Message tree's DataObject element as blank. But the messages did come through, nonetheless...
Try putting the message into a queue and browse it later... |
|
| Back to top |
|
|
| marko.pitkanen |
| Posted: Thu Sep 22, 2011 4:14 am Post subject: |
|
|
Chevalier
Joined: 23 Jul 2008
Posts: 440
Location: Jamsa, Finland
|
Hi,
At generic Inbound flow you should remove generic message set's envelope from your iDocs you are passing to appropriate application flow so that them can be parsed with specific iDoc message set.
| Code: |
SET OutputRoot.BLOB.BLOB = CAST(InputBody.*:SapGenericIDocObject.*:IDocStreamData AS BLOB);
SET OutputRoot.Properties.MessageSet = '';
SET OutputRoot.Properties.MessageType = '';
SET OutputRoot.Properties.MessageFormat = '';
|
--
Marko |
|
| 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
|
|
|
|
