Point-to-Point Service-Based Integration 

This variant is about creating and binding ABAP and Java Web Services.

So far, the combination of different uses in heterogeneous system landscapes has been based, for the most part, on manually declared interfaces, message formats, and agreements between business partners. This process has been simplified with Web Services. Web Services form the technological basis of Enterprise Service Architecture. By being implemented, IT infrastructures can be converted – step by step – into service-oriented architectures.  

SAP applications consist of BAPIs, RFMs, EJBs, and so on. These modules can be included as Web Services either within a company or on a cross-company basis. They can also be included in other applications. Web services that are based on “non-SAP“ modules can also be integrated into existing applications within the framework of the Enterprise Services Architecture.  

In this variant, a Web service is called in point-to-point mode.

 

In this case, the Integration Broker is not used as a negotiator between the Web service client and the Web service provider (see the variant: Brokered Service-Based Integration). 

To be able to implement this scenario variant, use the tools provided by the Web Service Framework.

·        The Web Service Toolset of the ABAP Workbench

·        The Web Service Toolset of the SAP NetWeaver Developer Studio

·        Tools that support UDDI registration

Required SAP NetWeaver Usage Types

To use this scenario variant, you require the following technical usage types of SAP NetWeaver:

·        AS Java

·        AS ABAP

IT Processes of the Scenario Variant

This scenario variant comprises the following IT processes:

Process	What you should know…
Service Consuming	To execute a service of another system, the application calls a proxy in the application system. The result of the call is that the application system sends a message to the Integration Broker.
Service Providing	The service provider receives the message and calls the service. If you have synchronous calling, the receiver sends the response message to the Web service client.