| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Message Broker 6 connecting to SAP |
« View previous topic :: View next topic » |
| Author |
Message
|
| sebastian |
 Posted: Wed Aug 02, 2006 7:28 am Post subject: Message Broker 6 connecting to SAP |
 |
|
Centurion
Joined: 12 Nov 2003
Posts: 110
Location: Philadelphia
|
Our shop recently migrated from MQSIv2.1 to Message Broker 6.0. Since we were early adopters of IBM's integration tool, we are also using the Neon rules and formatter extentions for many legacy flows.
Our current method to develop flows, which have SAP as the target or source, has been to use the R/3 link to move the message between SAP and MB6. The message type coming from SAP first enters the neon rules engine and is routed to a message flow that contains a neon transform node. In, Neon, the SAP idoc comes in and is usually transformed to XML. This XML is manipulated using ESQL in a compute node and then routed to the application destination.
We would like very much to move away from using Neon and are exploring alternatives such as the mySAP.com adapter.
I am very interested in hearing from anyone using Message Broker with SAP. What interface tools, adapters are you using with SAP? Are you coding Message Sets manually for idocs or is there some more efficient method for this?
Any feedback is greatly appreciated.
thank you,
Sebastian 
_________________
sebastian signature |
|
| Back to top |
|
 |
| fjb_saper |
| Posted: Wed Aug 02, 2006 4:06 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
You can use MQ-Link for R3. You will get an Idoc format. You can then use a java compute node to do some recursive programming that will transform the IDOC into XML and go on.
You can as well use the JCO and the SAP provided IDOC classes for the JCO (com.sap.mw.jco.idoc ??) and create directly (formatting in the JCO) an XML Idoc and drop that XML Idoc into a queue. (I have done that in point to point JMS).
Enjoy
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| anvanzyl |
| Posted: Sun Aug 06, 2006 7:24 pm Post subject: |
|
|
Novice
Joined: 03 Jan 2005
Posts: 19
Location: Melbourne, Australia
|
Hi,
I have used the R3Link to integrate applications via MQSI 2.1 to SAP before. My current customer uses WBIMB V5 and the WBI SAP Adapter to integrate with SAP. The following features make the WBI adapter for SAP much better (imho) to use - You can use the ODA (object discovery agent) to discover IDOC structures or BAPI function parameter structures. This will generate XML schemas (.xsd) which you then use as the business object in the adapter configuration and you can use this to quickly define a MRM XML message set.
The adapter can be used to call BAPI functions and receive responses, create inbound SAP IDOCs or receive SAP outbound IDOC messages all in XML format.
Sending requests to and receiving outbound data from SAP in the adapter via WBI MB uses XML format and this is much easier to work with in the message flow than the old fixed length R3Link format.
I haven't done much performance testing with the WBI SAP adapter yet, but the customer has been using it for both high volume and large messages and it performs adequitly in production.
_________________
Regards
Andre
IBM Certified System Administrator -- WMQ V5.3
IBM Certified Solution Designer -- WBIMB V5 |
|
| 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
|
|
|
|
