You create a service interface depending on the following use cases:
Inbound (Provider Role): You want to implement a service in an application system that can be called by a user.
Outbound (Consumer Role): You want to call a service of a provider. To do so, you require the outbound service interface that matches your inbound service interface.
Abstract : In enhanced communication using the Integration Server, you want to exchange messages with a buffered integration process .
Define the security profile of the service interface.
To define a business event that can be consumed by other applications as Web services, select the Event Interface check box.
If you want to enable the encryption at run time for a service interface, then select the check box for Sensitive Data
Depending on the interface pattern, you require one or more operations. Use the operation list to create new operations. You can continue to change the name of the operation until you save the service interface for the first time.
Define the operation pattern and mode for each operation. Depending on the interface pattern, the service interface editor provides you with different operation patterns and modes to select from (see above).
For inbound category, synchronous mode, and any interface pattern other than TU&C/C, an option called Idempotent is available.
Using the input help, assign each operation a message schema for the request message and, if applicable, response and fault messages. The corresponding interface objects must be in the same software component version as the service interface, or in an underlying software component version .
In enhanced communication, you can simply access the message payload by using context objects for logical routing. In the service interface editor, you can assign a request message context object from the same software component version or from an underlying software component version.