|
Using bTalk for XML
The diagram above shows all components built using bTalk to facilitate an XML request and response into SAP. bTalk generates the following:
- The Java Proxy Bean (handles the transaction between app server and SAP R/3 through the BAPI/RFC.
- The Java Parser Beans (handlers the parsing of the XML)
- The Java Server Page (which acts as a handler / servlet to accept the XML request)
- The XML Request (the actual XML file which holds the request information for the function)
- The DTD (the data definition for the XML packet)
Demonstration
This demonstration is to show how to retrieve information from SAP R/3 using XML.
The basic architecture is as follows:
- Send "Request" XML to bTalk (e.g. asking for Customer list)
- bTalk makes request to SAP via the BAPI/RFC (e.g. BAPI_Customer_GetList)
- bTalk sends "Results" back as XML.
Note: This process can be triggered by a user action or scheduled.
Here are the main components of the process:
- The Request Packet - The XML packet that Compusoft would send to bTalk requesting information.
- The Response Packet - The XML packet that Compusoft would get back from bTalk.
- The DTD used by bTalk to validate the XML packets
Run the Demo
Note: Sometime this demo is not operable due to our SAP system being down. If you would like to see this demo, please register for a web seminar.
|
