Show TOC

Creating Shared Service GroupsLocate this document in the navigation structure

Prerequisites

  • One of the following DCs is created in SAP NetWeaver Development Infrastructure:

    • WEB Module DC.

      The WEB Module DC in the project is version 2.5.

    • EJB Module DC.

      The EJB Module DC in the project is version 3.

  • An enterprise application project DC is created in the SAP NetWeaver Development Infrastructure.

  • A Service Group Configuration DC is created in the SAP NetWeaver Development Infrastructure.

    More information:

    Creating Development Components

    Development Component Types

  • DC dependency from the WEB Module DC or the EJB Module DC to the Service Group Configuration DC is set.

  • A dependency from the EAR project DC to the Web Module DC or the EJB Module DC is set.

    More information: Defining Development Component Dependencies

  • The AS Java settings are configured in Start of the navigation path Window Next navigation step Preferences Next navigation step SAP AS Java End of the navigation path

  • The application server and Web service runtime are set in the SAP NetWeaver Developer Studio from Start of the navigation path Window Next navigation step Preferences Next navigation step Web Services Next navigation step Server and Runtime End of the navigation path. In the Server field, choose SAP Server, and in the Web service runtime, choose SAP NetWeaver.

  • Import the WSDL document of the Web service you want to consume in the Web Module DC or the EJB Module DC.

    More information: Importing WSDL Documents in the SAP NetWeaver Developer Studio

Context

To be able to reuse Service Groups in multiple consumer applications, you have to share these Service Groups in a uniform location. You create and share Service Groups in Service Group Configuration development components (DCs). Referring to the shared Service Groups, you ensure that service references in different client applications are grouped together and will be configured to use the same provider at runtime.

Procedure

  1. Open the Java EE perspective; choose Start of the navigation path Window Next navigation step Open Perspective Next navigation step Other Next navigation step Java EE Next navigation step OK End of the navigation path
  2. Right click the imported WSDL document and then choose Start of the navigation path Web Services Next navigation step Create Service Reference End of the navigation path
  3. Depending on the existing Service Groups in the Service Group Configuration DC, proceed as follows:

    • If the system discovers an existing Service Group whose name matches the name of the Service Group you are about to create, you can use the existing Service Group as a storage.

      1. Choose the Choose Existing radio button.

      2. From the dropdown menu, choose the existing Service Group.

    • If you want to create a Service Group in the Service Group Configuration DC, proceed as follows.

      1. Choose Create new .

      2. In the Package field, enter the package in which you want to create the Service Group files.

      3. Enter Service Group name and description.

      4. In the Create in project field, choose the Service Group DC in which you want to create the Service Group.

  4. Choose Finish .

Results

The tools create the Service Group in the Service Group Configuration DC, and service references in the Web Module DC or the EJB Module DC.

Next Steps

As a next step, you can proceed with the following tasks:

  1. Create a Web service proxy

    More information: Creating Web Service Proxies

  2. Create the Web service client application.

    More information: Creating Web Service Client Applications

  3. Deploy the Web service client on the application server (for deployable proxies only).

    More information: Building, Publishing and Removing Published Java EE Applications

  4. Configure the Web service client in the SAP NetWeaver Administrator.

    More information: Configuring Web Services and Web Service Clients in the SAP NetWeaverSAP NetWeaver Administrator

    Note

    When you deploy the application on the consumer system and there is an established connection from the consumer system to the Services Registry (SR), SOA configuration for connectivity checks the provider systems listed in the SR. If there is a system providing the Web services that you want to consume and a connection to this system is established, SOA configuration for connectivity automatically creates assignment to this system and creates configuration entities (logical ports).

    Note that SOA configuration for connectivity checks only the names of the provider system and the consumed services. The connectivity settings in the communication profiles and the policies in the service endpoints are not taken into account at this stage. Even if the names of the provider system and the consumed services match, the automatic assignment may still fail if the policies in the profiles and service endpoints do not match.

    In addition, the following entities may not be configured properly if the policies in the profiles and service endpoints do not match, even though the system displays them as successfully configured.

    • Callable objects that are created with Guided Procedures framework.

    • Automated activities and events that are created with Business Process Management framework.

    • Adaptive Web service models that are created with Web Dynpro framework.

    • Web service operations that are created with Visual Composer framework.