Share via

2     Demonstration Scenarios Overview

2.1    General Remarks

SAP speaks of Web service providers and Web service consumers. Microsoft generally uses the terms services and clients.

In this document, Microsoft terminology uses accessing services, whereas in SAP terminology, the term consuming services is used.

2.2    PO/Confirmation Scenario

The description of how to set up Web services-based communication between AS ABAP and .NET Framework 4 is based on the delivered demonstration scenario purchase order/confirmation service (PO/Confirmation). The SAP Enterprise Procurement Model (EPM) system provides two asynchronous Web services for this. The communication pattern used in this scenario is one-way reliable messaging with anonymous (non-addressable) client.

This demonstration scenario is derived from an SAP Enterprise Service. The detailed description in Chapter 4is based on this scenario.

Figure 1 PO/Confirmation scenario

In scenario PO (Send Purchase Order Request), AS ABAP (SAP) acts as the Web service provider and WCF (Microsoft) as the Web service consumer/client. The purchaser sends a purchase order request to the supplier. All descriptions in section 4.3.1refer to this scenario.

In a production implementation of a PO/Confirmation scenario the application layer would send out the confirmation after processing the PO request. In this demo scenario however, a simulation is implemented instead (Simulate Purchase Order Processing). It processes the purchase order request and sends back a purchase order confirmation to the purchaser. In the simulation, no data is stored in the database.

In the Confirmation (Send Purchase Order Confirmation) scenario, WCF (Microsoft) acts as the Web service provider and AS ABAP (SAP) as the Web service consumer/client. The supplier sends back a purchase order confirmation to the purchaser. All descriptions in section 4.3.2are based on this scenario.

Note   The contract between the Web service provider and the consumer is based on one interface. Figure 1, EMP_PurchaseOrderRequest_Out and EPM_PurchaseOrderRequest_In illustrates the distinction in this contract. This distinction is made in case that you want to set up Web services connectivity using SAP NetWeaver Process Integration. In the following scenario description, Web services connectivity is set up directly between an SAP and a Microsoft system. The distinction between In and Out is not required in the scenarios described in this guide. The message types are identical in both cases.

To secure the exchanged messages, SSL over HTTP is used and user ID/password authentication either on transport level or on message level.

2.3    Ping/Echo Scenarios

The Ping/Echo scenarios are technical scenarios that Microsoft and SAP used for interoperability testing. All descriptions in Chapter 5 refer to Ping/Echo.

To secure the exchanged messages, various alternatives have been tested:

  • On transport level you can use either SSL over HTTP or message encryption. For authentication, user name/password is available either on transport or on message level.
  • Alternatively, you can use an X.509 certificate on message level for authentication or SAML based Single Sign-On by involving a security token service.
  • Other tests included Web Services Reliable Messaging, data type testing, including how XSD elements are mapped to ABAP types. Tests also used different WSDL document types.
  • Message Transmission Optimization Mechanism (MTOM) combined with message signature and encryption and WS-Addressing scenarios were tested.

In Chapter 5, references to the delivered scenarios in.NET Framework 4 and in the AS ABAP implementation can be found.

2.4    Demonstration Scenarios Delivery

2.4.1      SAP

SAP delivers the PO/Confirmation as ES Repository content in the software component SAP Basis, software component version SAP Basis 7.20, and namespace http://sap.com/xi/NWDemo, folder EPM.

SAP has implemented PO/Confirmation in AS ABAP. The implementation is in the ABAP Workbench (transaction SE80) in package S_EPM_PI.

SAP does not deliver endpoints or logical ports. For the configuration of endpoints or logical ports, go to SOA Management (transaction SOAMANAGER) and search for EPM*.

There is no ES Repository content available for Ping/Echo.

The Ping/Echo scenarios are implemented in AS ABAP in package SOAP_RT_TESTS_BIZTALK. For the configuration of endpoints, go to SOA Management (transaction SOAMANAGER). Search for I*, Echo or Notify.

For the configuration of logical ports, go to SOA Management (transaction SOAMANAGER). Search by Internal Name for CO_*.

To access the provider WSDLs for configuration, use user ID Alice_ and password _ecilA. Some .NET clients need this information at runtime. The exact credentials could be anything you chose.

Note    To simplify the WSDL access, you can add the user ID and password to the WSDL URL in the following way: Add &sap-user=Alice_&sap-password=_ecilA at the end of the URL. This is NOT recommended for production scenarios!

2.4.2      Microsoft

Microsoft delivers the PO/Confirmation and the Ping/Echo scenarios as downloads.

You can download the latest .NET PO/Confirmation implementation, SAPBusinessScenario.zip, from the following location: https://code.msdn.microsoft.com/WCFandSAP

You can download the latest .NET Ping/Echo implementations, InteropSourcesAndBinaries_SecurityPolicy12.zip, from the following location: https://code.msdn.microsoft.com/WCFInterop

Download

Source code

Document Sections

Additional Resources
  • Last updated on