Glossary of Terms for SOA Manager 
Below is an overview of specific terms used in connection with SOA Manager:
binding |
A binding determines which protocol is used for processing Web service messages.
A binding is also referred to as an endpoint. End of the note. More information: |
|
configuration profile |
A configuration profile comprises a set of technical settings for endpoints. More information: |
configuration scenario |
A configuration scenario consists of multiple service definitions, to which you can assign a configuration profile. You can create multiple configuration scenarios for your system infrastructure. More information: |
consumer proxy |
A consumer proxy is used in an application to call (consume) a Web service. More information: |
endpoint |
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.
An endpoint is also referred to as a binding. A binding determines which protocol is used for processing Web service messages End of the note. More information: |
event-enabled |
Operations for specially created event proxies can be service enabled to allow applications in a landscape to communicate with each other using business events. More information: |
logical port |
The consumer proxy's logical port communicates with the provider proxy’s endpoint. To access a service endpoint, a service consumer with a runtime configuration sends a call through a logical port. More information: |
technical receiver determination |
The ABAP stack of SAP NetWeaver offers an API for technical receiver determination (TRD-API), which allows developers of web service consumer applications to dynamically instantiate consumer proxies at runtime. More information: |
provider proxy |
A provider proxy needs to be created to provide a Web service. Provider proxies are created and implemented in the ABAP back-end system, in which the service is provided. More information: |
proxies |
More information: |
publication rule |
Services can be published to the Services Registry in accordance with publication rules. More information: Setting Up the Connection to the Services Registry Creating and Changing Publication Rules in the Back-end System |
reverse proxy |
More information: |
runtime configuration |
A runtime configuration is needed to implement a service. A runtime configuration is generated using the service definition. More information: |
service classification |
You can search the Services Registry using service classifications. More information: Finding Information About Services in the Services Registry A publication rule can consist of a set of service definitions and classifications. More information: Creating and Changing Publication Rules in the Back-end System |
service definition |
A service definition consists of development objects. These objects can be either from SAP or custom-created objects delivered as part of an application. Service definitions are automatically created during proxy generation. A service definition is used to generate a runtime configuration. More information: |
Service Group |
Service Groups allow you to configure multiple consumer proxies at the same time. Service Groups are used to define which services a consumer application needs to run. This ensures that all the services in a Service Group are available on the same provider system. More information: |
service metering |
The service metering feature allows SAP NetWeaver components involved in the provisioning and consumption of Web services to collect information about which consumer components are consuming which Web services. The information collected in the SOA back-end systems can be read by SAP EarlyWatch and analyzed to optimize SOA scenarios and the enterprise services. More information: |
Services Registry |
More information: |
Note