Using Web Services in SAP with Transaction SE80 & SOA Manager

 How Do You Make SAP Technically Fit for Modern Mobility Web Services? In Just a Few Steps Using SAP Transactions SE80 and SOA Manager.

If you want to give external systems access to SAP function modules, various ways offer themselves. A rather conventional path is via the RFC interface. SAP offers native libraries for this on various platforms, which can then in turn be called up by language-dependent libraries, e.g., for Java. Unfortunately, these libraries are not available for all platforms and programming languages. For example, access via mobile devices or browsers must take place via a server-side intermediate component.

Publishing SAP function modules as a web service provides a remedy. Since these are based on HTTP, they can be called up by almost any network-capable application. A further advantage is the more convenient integration of web services into existing heterogeneous service-oriented system landscapes, in which communication currently takes place largely via web services.

The following example illustrates how simply and conveniently SAP enables the provision of function modules as a SOAP web service with its tools. The usual path is described here, without going into the actually quite diverse configuration options in the individual steps.

The definition of the web service takes place in the Object Explorer. This can be opened via transaction SE80. After selecting a target package in the Repository Browser, the wizard for creating the web service can be started via the context menu "Create > Enterprise Service".

Fig. 1: Select Service Provider as object type Fig. 2: "Inside Out" publication; the type of Service Provider is an "Existing ABAP Object" Fig. 3: Specification of the name (Service Definition) as well as a description Fig. 4: Select "Function Module" as the endpoint type, for example Fig. 5: Selection of the function module to be published Fig. 6: Select required security profile depending on the respective security requirements Fig. 7: Select the development package to which the new Enterprise Service is assigned Fig. 8: Complete wizard via "Finish"

The service is now located in the selected package and can be activated in the menu bar via an existing or new workbench request.

After activation, the web service still requires a runtime release for final use. This is configured in the SOA Manager. This is accessible via the SAP transaction "SOA-Manager".

After selecting "Web Service Configuration," the service to be configured can be selected via a search for the object type "Service Definition" and the corresponding object name.

Selecting the service opens the wizard for configuring the web service release via the "Create Service" button.

In the wizard for configuring the release, which consists of four steps, SOAP-relevant settings, e.g., regarding security, are made:

Fig. 1: Entry of the service name and name of the binding (usually with the suffix "_binding") Fig. 2: Select option "User ID and Password" in the Transport Level Authentication area Fig. 3: Usually no adjustments to SOAP protocol settings necessary Fig. 4: To conclude the wizard, the released operation is displayed

The result of the wizard can be seen in the configuration list. There, the service can later be deactivated, edited, and deleted.

So that applications can access the web service, they now only need the URL of the WSDL of the web service. This information can be displayed via the corresponding symbol in the binding entry in the list.

Configuring SAP for web services requires only a few steps. With transactions SE80 and SOA Manager, a convenient solution for SAP Mobility connection is thus available, without having to take the path via the RFC interface or a middleware component.