Glossary of Terms for SOA Manager
Below is an overview of specific terms used in connection with SOA Manager:
|
abstract IBC (Identifiable Business Context) |
A modeled communication partner in the integration scenario definition that acts as a placeholder for IBC references. More information: Semantic Addressing Using Identifiable Business Contexts (IBCs) |
|
actor |
A party in a business process interaction. An actor is defined in the semantic contract and reused in the contract and the contract implementation. A semantic contract always contains two actors. More information: |
|
authentication determination |
A mechanism that uses rules to determine the correct authentication data based on the receiver, the sender, and the business context. Authentication determination is only needed if receiver and sender determination allow more than one possible combination. The business context is provided using a filter structure within the consumer factory by the application developer. The rules, on the other hand, are defined by the business administrator in SOA Manager. Logical Determination of Receiver, Sender, and Authentication |
|
binding |
A binding determines which protocol is used for processing Web service messages. 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. More information: |
|
configuration profile |
A configuration profile comprises a set of technical settings for bindings. 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 factory |
An SAP development object that defines a link between the source service consumer, the semantic contract, and one of its actors. It can also include filter structures and modes for sender, receiver, and authentication determination. Based on these entities, the business administrator can define rules in SOA Manager. As a result, a generated class can be used in the application for sender, receiver, and authentication determination and for the instantiation of the source service consumer. |
|
consumer proxy |
A consumer proxy is used in an application to call (consume) a Web service. More information: |
|
contract |
An SAP development object derived from a semantic contract. As well as the constituents of the semantic contract, a contract includes signatures of the operations. The contract is the technical basis for the communication between two systems. More information: For information about the configuration of contract-based connection, see Configuring Integration Scenarios. |
|
contract implementation |
An SAP development object that implements a contract for one of its actors. This is done by referencing the appropriate service providers and service consumers. More information: Creating Contract Implementations For the configuration of integration scenarios, contract definitions must exist in the design time cache of the central system. You can also create them directly in SOA Manager. For more information, see Creating Contract Implementations in SOA Manager |
|
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 binding. To access a service endpoint, a service consumer with a runtime configuration sends a call through a logical port. More information: |
|
Identifiable Business Context |
A representation of a business application entity (for example a business partner, a factory, a tenant) that can act as a party in a business process interaction (for example sales order processing, purchase order processing, billing). The Identifiable Business Context (IBC) is used for the configuration of integration scenarios and is a prerequisite for logical and technical receiver determination, logical and technical sender determination, and authentication determination. More information: Semantic Addressing Using Identifiable Business Contexts (IBCs) |
|
Identifiable Business Context reference |
A reference to an Identifiable Business Context (IBC) that another business application entity has to use to address this IBC. The IBC reference is used for the configuration of integration scenarios. More information: Semantic Addressing Using Identifiable Business Contexts (IBCs) |
|
integration scenario definition |
An SAP development object that groups interactions on a logical level. The integration scenario definition bundles a list of related semantic contracts and it contains assignments between the actors of these semantic contracts and abstract IBCs. At configuration time, landscape-specific integration scenarios are derived from integration scenario definitions. |
|
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, if they have used service groups. 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: Web Service Providers |
|
proxy |
More information: |
|
publication rule |
Services can be published to a 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: |
|
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: |
|
Single-target consumer mapping |
A type of consumer mapping in which all assigned operation mappings share one target consumer. A single-target consumer mapping (STCM) always includes mappings for each operation. Direct mapping from the source consumer to the target consumer without operation mapping is not allowed. More information: |