Show TOC

Procedure documentationTasks Locate this document in the navigation structure

 

To keep the description in this guide as clear as possible, it is based on the following use case: A business would like to expose its business functions as services so that external business partners can call them. To take advantage of all the possibilities for connecting own protocols and formats, the integration takes place using the Integration Server or Advanced Adapter Engine.

Note Note

This documentation describes all the tasks covering the following areas:

  • Modelling and Design of ESR Content

  • Configuration in the Integration Directory

  • Publishing Services for Calling the Integration Server of the Advanced Adapter Engine to the Services Registry

In addition, you will find references to other tasks that are related to administering and monitoring the process that is running.

Tasks connected with implementing application logic at the consumer or provider side are not included in this documentation.

End of the note.

SAP NetWeaver Process Integration also supports the integration of Web service providers and Web service consumers. The complete procedure for configuring such scenarios depends on which backend systems the provider and consumer are implemented. You cna find an overview of the tools and procedures for configuring such scenarios in a separate guide in the SAP Developer Network (SDN) under https://www.sdn.sap.com/irj/sdn/soa-management. In the Knowledge Center on the SOA Management page, choose the Configuration and Monitoring service and on the following pages of the document, SAP NetWeaver Process Integration 7.1 - Configuring Web Service Scenarios (Guide).

Procedure

Basic Procedure
Tasks on the Provider Side

The tasks described below must be executed on the provider side.

  1. Installing and Configuring SAP NetWeaver PI

    You can find all the information on installing and technically configuring SAP NetWeaver PI on the SAP Service Marketplace under http://service.sap.com/instguidesnwpi71. Under Installation you can access the detailed installation guide.

  2. Importing and Searching ESR Content

    SAP delivers pre-defined ESR content that deals with a broad range of applications. By using pre-defined content, you can save a lot of your own developing effort and complete your integration project much more quickly.

    For more information on the steps required for using pre-defined ESR content, see Working with Enterprise Service Definitions of SAP.

  3. Defining Development Packages

    To be able to develop objects in the Enterprise Services Repository, you must first define software components. The project development manager normally has the necessary authorization. Software components have the role of development packages which you can use to structure the content in ES Repository. If you want to create objects purely for testing, you can create a local software component version for this purpose.

    1. Defining Software Components in the System Landscape Directory

    2. Importing Software Components into the ES Repository

    For more information, see: Development Cycle in the Enterprise Services Repository

  4. Modelling and Specifying ESR Content

    In the Enterprise Services Repository you can describe details for the business process at different levels. You can create very different content to do this: From process models that describe the process flow of the process and message exchange using interface descriptions and data types through to mappings and communication templates. The Enterprise Services Repository is the central development environment with which you can model, specify, and manage content.

    For more information, see: Modelling and Specifying ESR Content

  5. Generating Callable Proxies for Service Providers

    To create callable interfaces (proxies) of the interface descriptions in the ES Repository in each of the backend systems, execute the proxy generation.

    For more information, see: Proxy Generation

  6. Implementing a Service Provider

    Based on the proxy, complete the functions on the provider side in program code.

  7. Configuring Security Settings

    Depending on the security standards for communication between the consumer and the provider, you have to make the corresponding settings.

    How you proceed from here and which tools you use depends on the security settings that you require.

    You can find an overview of the recommended security settings for Web service provider and Web service consumer communication under Recommended WS Security Scenarios

  8. Configuring Message Processing

    When configuring message processing, you define how messages are to be exchanges in your system landscape (routing), which mapping is to be applied, and how the messages are to be processed at the inbound and outbound channels of the Integration Broker. If you want to define specific security settings for transferring messages, specify them when configuring the adapter that is used. Note that, depending on the use case, there may be additional tasks required for the configuring security settings in the backend systems connected with each other.

    For more information, see: Configuring Message Processing

  9. Publishing Sender Agreements or Integrated Configurations to the Services Registry

    When configuring the message processing you also define the details for the inbound processing of a message at the Integration Server or Advanced Adapter Engine. You can publish the configuration objects that are relevant for this (sender agreement or integrated configuration) to the Services Registry. This alleviates the consumer systems involved of the need to call the Integration Server or Advanced Adapter Engine.

The figure below illustrates the important tasks at the provider side and the relevant tools.

This graphic is explained in the accompanying text.

Note Note

Note that, depending on the actual use case, some steps may not be required.

End of the note.
Tasks on the Consumer Side

The following tasks must be executed by the integration expoerts and developers involved at the consumer side so that the provider application can be called.

  1. Finding a Service for Calling the Provider in the Services Registry

    With this step you find the sender agreement or integration configuration published in the Services Registry that specifies the call of the Integration Server of the Advanced Adapter Engine,

  2. Implementing the consumer application.

Monitoring Cross-Component Processes

If you have modelled, specified, and configured a cross-component process, you can execute and monitor it at runtime. SAP NetWeaver Process Integration provides different tools for monitoring such processes.

For more information, see: Process Integration Monitoring