Show TOC

Procedure documentationConfiguring a Service Provider Locate this document in the navigation structure

 

To configure a service provider, you need to create and configure an endpoint. The endpoint contains a runtime configuration, which is needed to implement the service. A runtime configuration is generated using the service definition. A service definition consists of development objects - either from SAP or custom-created objects delivered as part of an application. Service definitions are automatically created during proxy generation.

You can create more than one endpoint for the same service. In this way, you can provide the same service with several different runtime configurations.

Note Note

If you do not create an endpoint, it will not be possible to call the service.

End of the note.

Procedure

  1. From the main screen of the SOA Manager, go to the Application and Scenario Communication tab.

  2. Select Single Service Administration.

  3. Specify a service.

    You can locate a service from the Search or Browse tab.

    Search

    You can search for service definitions, consumer proxies, or ServiceGroups, using either the internal or external name, or both.

    Advanced search allows you to search by classification.

    You can display the objects for selected classifications and subclassifications sorted either by DPB (deployment unit, process component, business object) or SPB (software component, process component, business object).

    Browse

    Display all the services or consumer proxies for a classification (DPB Group or SPB Group).

    Objects are displayed with their internal and external names, namespace, and type (deployment unit, process component, or business object).

  4. Select a row and choose Apply Selection to display more information about the service definition.

    The information includes the namespace for the port type, the package name, and links to the WSDL documents for the endpoint(s).

    Note Note

    An endpoint is also referred to as a binding.

    A binding determines which protocol is actually used for processing Web service messages. A binding has a one-to-one relationship to an endpoint.

    End of the note.
  5. Select the service and choose Apply Selection.

    An overview of design-time information is displayed for the service definition.

  6. Go to the Configurations tab.

  7. Choose Create Endpoint.

    A dialog box is displayed.

  8. Specify a unique name for the endpoint.

    An endpoint contains a single runtime configuration for a service. To define different runtime behaviors, you can create multiple endpoints for the same service. This allows you to provide the same service with a different runtime behavior to different consumers.

  9. Choose Apply Settings.

    The configuration settings for the endpoint are displayed.

  10. Check that the configuration settings meet your requirements.

    To make changes, choose Edit.

    You have the following configuration options for endpoints:

    Provider Security

    Transport Guarantee Here, you determine whether and how messages are signed or encrypted.

    Using a signature confirms to the recipient that a message was not changed in transit.

    Encryption prevents a message from being seen in transit.

    Authentication Settings: Here, you determine how the consumer and the provider authenticate themselves to each other.

    Transport Settings

    Define an alternative URL for messages.

    The path that you set here overrides the path defined in the URL.

    You need to specify an alternative path, for example, if the service is not local if it is behind a firewall, .

    If the target Web service can only be accessed through a proxy server, you can also specify some proxy information here.

    Operation specific

    You can specify the SOAP action for the operation. In this field, you can enter a URI that identifies the intent of the call. The SOAP action is set as an HTTP header when the Web service call is made through HTTP.

  11. Save.

    The service can now be called and the WSDL document for the service is available.