Show TOC

Background documentationTasks Locate this document in the navigation structure

 

Using the SAP NetWeaver Developer Studio you can simplify or compose services in your composite applications.

Simplifying Services

Using the Service Composer perspective, you can easily reduce the complexity of an existing back-end service. Using the Service Composer, you can create a new composed service that will be used to represent only the section of functionality and data provided from the back-end service that you need. In addition, all data mappings of the data in the service interface are performed automatically. Once you are ready with the simplification of the complex service interface, you can consume the simplified service in other layers of your composite application. You have a ready to deploy-and-run executable service interface.

For more information about simplifying a complex service interface, see Simplifying Services.

Composing Services

You can compose a service which aggregates operations defined in several back-end services. Composing the service means that you define the flow of service interfaces used by your composed service and the data transformation. You can use this composed service to orchestrate the data that comes from different sources such as RFCs, Web services, or simplified service interfaces.

This graphic is explained in the accompanying text.

Service Composition Process

  1. Create a new service interface to use as a composed service. For more information, see Creating Service Interfaces or Services and Composing Services.

  2. Once the service interface is created, you continue with importing back-end services operations in the service flow and design and develop the specifics for your needs. For more information, see Modeling the Service Flow.

    You can define which data fields from the consumed service interfaces correspond to which data inside the composed service. For more information, see Mapping Service Operations Input and Output. You can also use built-in functions or create your own mapping functions. For more information, see Performing Complex Data Transformation with Functions.

  3. Generate, build, and deploy your project, and test the behavior of the service. You are ready with exposing the service as a Web service with the data from the multiple sources to your consuming objects or with the simple structure of the simplified service.

    Caution Caution

    Before each build, or after a change in your composed service, you have to trigger generation of the composed service.

    End of the caution.

    For more information, see Generating the Composed Service.

  4. Configure the composed service behavior at runtime.

    After you have deployed the service to an Application Server Java (AS Java), you need to configure all service groups and/or all logical destinations used by the consumed services.

    For more information about configuring the Service Registry consumer proxy, see Configuring a Central Services Registry.

    For more information about creating a provider system connection, see Creating Connections to Provider Systems.

    For more information about configuring a service group, see Configuring Groups of Web Service Clients.

    (Deprecated) If you have to configure the logical destination, see Creating Web Service Physical Destinations.

Recommended Developer Studio Settings

We recommend that you change the default preference settings of the Developer Studio when working with composed services. From the menu path of the Developer Studio, choose   Window   Preferences   Development Infrastructure   Design Time Repository   Eclipse Workspace Monitor   and change the option When detecting a new resource to Add to DTR. Then specify a default activity to be used when adding resources to the version repository (that is, to the Design Time Repository (DTR)).

More Information

Reimporting a Modified Service Definition

Securing Composed Services

Creating Mock Services