| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Generic IDoc routing into SAP using sapRequest node |
« View previous topic :: View next topic » |
| Author |
Message
|
| sunny_30 |
 Posted: Tue Jul 27, 2010 8:06 am Post subject: Generic IDoc routing into SAP using sapRequest node |
 |
|
Master
Joined: 03 Oct 2005
Posts: 258
|
HI
I would like to know if its feasible in WMBv7 to dynamically post different IDoc types into SAP using sapRequest node running in PassThrough mode (data sent as BitStream)
The plan is to use single MessageFlow instance deployed with a single Adapter connection but trying to be able to automatically route single/packet IDocs mixed with different IDoc message-types into SAP. There is no parsing required in Broker
Found the following URL in infocenter that only talks abt Outbound of SAP using sapInput node:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/bc22050_.htm
But Im not sure if its possible the other way around
Appreciate in advance any ideas on how this can be implemented..
Thanks |
|
| Back to top |
|
 |
| Gaya3 |
| Posted: Wed Jul 28, 2010 7:14 am Post subject: Re: Generic IDoc routing into SAP using sapRequest node |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| sunny_30 wrote: |
I would like to know if its feasible in WMBv7 to dynamically post different IDoc types into SAP using sapRequest node running in PassThrough mode (data sent as BitStream)
|
i have tried it with ALE mode and its working, we have posted different IDoc types to the SAP server using SAP Request node. [Tested and verified in MB V6.1]
if it is working for ALE, i believe it will work for the Pass through mode as well.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| sunny_30 |
| Posted: Thu Jul 29, 2010 11:11 am Post subject: |
|
|
Master
Joined: 03 Oct 2005
Posts: 258
|
Thank you for the information
Can you please confirm that you used a single Broker MessageFlow instance + single adapter instance to post different IDoc types into SAP? |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Thu Jul 29, 2010 11:48 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| sunny_30 wrote: |
Thank you for the information
Can you please confirm that you used a single Broker MessageFlow instance + single adapter instance to post different IDoc types into SAP? |
Main flow -> InboundAdapter Message flow [this comprises of the adapter which having different IDoc Types]
Single adapter - having multiple types
========================
this is good if you finalized on the SAP Side [this never going to happen], if any changes happened you have to re-discover all the Business object together and recreate the adapter again. tightly couple solution
Multiple adapter instances
====================
Easy to handle, if any changes happened, it is required to discover only that Business object and update the adapter. loosely coupled solution
I tried the above two scenarios, i feel the second is the best in my experience.
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| sunny_30 |
| Posted: Thu Jul 29, 2010 3:19 pm Post subject: |
|
|
Master
Joined: 03 Oct 2005
Posts: 258
|
HI Gayathri
Thank you for the explanation
Sorry, I have few more questions I need to clarify..
you said:
| Quote: |
| if any changes happened you have to re-discover all the Business object together and recreate the adapter again |
Why do we need to discover specific IDoc types when we are trying to build a generic flow to handle any type ? Cant we use "generic Idoc" feature in the Adapter connection for Inbound processing into SAP?
The idea here is to use PassThrough mode in the Adapter connection "into" SAP. I have a requirement where in different types of IDocs (in flat file format) land on a single MQ queue. My plan is to use a single flow to process these IDocs & post them into SAP instead of separating into different MessageFlows for each IDoc type (there are abt 20..). No parsing required. Everything pushed in BitStream as is.
There is an article in IBM-dW on the same topic:
http://www.ibm.com/developerworks/websphere/library/techarticles/1004_agarwal/1004_agarwal.html?ca=drs-#icomments
in the figure 17.esql code segment, its using Idoc type: sapmatmas05
The type is hard-coded in both namespace & also as the BO-XML tag
| Quote: |
DECLARE ns NAMESPACE
'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapmatmas05'; |
| Quote: |
OutputRoot.XMLNSC.ns:SapMatmas05.IDocStreamData =
InputRoot.BLOB.BLOB; |
Instead of a single hardcoded Idoc type (as in this example), I could just dynamically read the type from input message into a variable and substitute it in the above code (I havent explored the exact syntax on how to do it, but Im pretty sure it can be done..)
My question is will it work if I code in ESQL to process different input Idocs dynamically as different BO-XMLs to output inside a single flow?
Im trying to test this on sandbox but still waiting on SAP test system availability & broker to be upgraded to v7.
In the meantime, all im looking is to confirm in 'theory' so I can put out the design proposal.
Appreciate your help on this..
Thanks! |
|
| Back to top |
|
|
| Gaya3 |
| Posted: Fri Jul 30, 2010 5:58 am Post subject: |
|
|
Jedi
Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US
|
| sunny_30 wrote: |
HI Gayathri
Thank you for the explanation
Sorry, I have few more questions I need to clarify..
you said:
| Quote: |
| if any changes happened you have to re-discover all the Business object together and recreate the adapter again |
Why do we need to discover specific IDoc types when we are trying to build a generic flow to handle any type ? Cant we use "generic Idoc" feature in the Adapter connection for Inbound processing into SAP?
|
I agree with you, but SAP makes changes, i didnt see they finalize it very soon. they always changes the segments name some or the other way
| sunny_30 wrote: |
The idea here is to use PassThrough mode in the Adapter connection "into" SAP. I have a requirement where in different types of IDocs (in flat file format) land on a single MQ queue. My plan is to use a single flow to process these IDocs & post them into SAP instead of separating into different MessageFlows for each IDoc type (there are abt 20..). No parsing required. Everything pushed in BitStream as is.
There is an article in IBM-dW on the same topic:
http://www.ibm.com/developerworks/websphere/library/techarticles/1004_agarwal/1004_agarwal.html?ca=drs-#icomments
in the figure 17.esql code segment, its using Idoc type: sapmatmas05
The type is hard-coded in both namespace & also as the BO-XML tag
| Quote: |
DECLARE ns NAMESPACE
'http://www.ibm.com/xmlns/prod/websphere/j2ca/sap/sapmatmas05'; |
| Quote: |
OutputRoot.XMLNSC.ns:SapMatmas05.IDocStreamData =
InputRoot.BLOB.BLOB; |
Instead of a single hardcoded Idoc type (as in this example), I could just dynamically read the type from input message into a variable and substitute it in the above code (I havent explored the exact syntax on how to do it, but Im pretty sure it can be done..)
My question is will it work if I code in ESQL to process different input Idocs dynamically as different BO-XMLs to output inside a single flow?
Im trying to test this on sandbox but still waiting on SAP test system availability & broker to be upgraded to v7.
In the meantime, all im looking is to confirm in 'theory' so I can put out the design proposal.
Appreciate your help on this..
Thanks! |
this will work, i tested y'day, my worry is about SAP, they wont finalize the BO as easily what you think
and when you said its just passthrough and no validation is going to happen, it will help you pass over to the target
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die |
|
| Back to top |
|
|
| sunny_30 |
| Posted: Fri Jul 30, 2010 9:21 am Post subject: |
|
|
Master
Joined: 03 Oct 2005
Posts: 258
|
|
| 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
|
|
|
|
