Extending the SAP call out to a synchronous system sample

You can extend the sample in two ways:

  1. The sample currently stores the customer information in a shared variable. This information is updated and stored when the appropriate BAPIs are run. The sample can be extended by replacing the shared variable with an external system which can be a Relational Database (for example, DB2 or Oracle), an IMS system, a WebSphere MQ application, a Web service, a JMS application, or any other system that can be accessed by using WebSphere Message Broker nodes. Other samples showing how to access all of these systems are supplied.
  2. This sample implements four BAPIs that are predefined in SAP. A more realistic scenario is that an SAP application developer wants to access an external system that cannot be accessed locally within SAP, such as IMS. The SAP application developer defines the interface inside SAP as a custom BAPI, then a WebSphere Message Broker Application developer discovers this interface and implements the BAPI inside WebSphere Message Broker. This extension follows on from the previous extension that explains how different external systems can replace the shared variable. To read about how to extend the sample in this way, see Implementing a custom BAPI.

Back to sample home