Configuring a Service Provider 
To configure a service provider, you need to create and configure a binding. The binding 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. These development objects are either shipped by SAP or are custom-created objects shipped as part of an application. Service definitions are automatically created during proxy generation.
You can create more than one binding for the same service. In this way, you can provide the same service with several different runtime configurations.
Note
If you do not create a binding, it will not be possible to call the service.
When to Configure a Single Service Provider
You will normally configure a single service provider in the following situations:
Communication between two applications takes place in one direction.
The consumer proxies need to be configured for only one of the two applications. For the unconfigured application, only the services need to be configured.
The consumer side is connected to exactly one provider system or to a mediator (hub).
The consumer system offers receiver determination not using service groups, but instead through application-specific configuration in which logical port names are stored and accessed directly at runtime.
There is only a small number of consumer proxies or services.
Procedure
From the main screen of the SOA Manager, go to the Service Administration tab.
Select Web Service Configuration.
Specify a service.
You can locate a service from the Search or Browse tab.
Search
You can search for service definitions, consumer proxies, or Service Groups, using either the internal or external name, or both.
Show 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).
To display more information about the service definition, select a row and choose Apply Selection.
The information includes the namespace for the port type, the package name, and links to the WSDL documents for the binding(s).
Go to the Configurations tab.
Choose Create.
A dialog box is displayed proposing the name and the description of the service you selected.
Specify a unique name for the binding.
A binding contains a single runtime configuration for a service. To define different runtime behaviors, you can create multiple bindings for the same service. This allows you to provide the same service with a different runtime behavior to different consumers.
Choose Apply Settings.
The configuration settings for the binding are displayed.
Check that the configuration settings meet your requirements.
To make changes, choose Edit.
You have the following configuration options for bindings:
Security
Transport Security 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: 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.
Save.
The service can now be called and the WSDL document for the service is available.