Service
Use
You use a service to do the following:
● Implement a technical or business unit, which is to be addressed as the sender or receiver of messages.
An example of a business unit is Order Management.Services as business units can be used in B2B scenarios in particular.
● Group interfaces to exchange messages according to particular task areas
● Address business systems as senders or receivers of messages
Features
Object Key
The object key is produced when you create an object and it comprises the following:
● Party
● Service
Service Types
In the PCK, the service is of type Business Service. It represents an abstract, addressable unit. Business services are used in cross-company processes, for example, if the parties involved have only published their interfaces and not their system landscape, or it is only partly known.
Using a business service, you can define the technical or business subunits of the companies involved and then assign them the relevant interfaces.
Adapter-Specific Identifiers
In the case of particular message formats, the sender and receiver are addressed by special identifiers at service level (and not at communication party level). These identifiers are part of the message header. The following adapter-specific identifiers exist:
Adapter Type |
Identifier |
IDoc Adapter |
Logical system |
SAP system ID and client |
|
Marketplace Adapter |
DDID label |
● To display and edit adapter-specific identifiers for a service, in the object editor menu bar, choose Object ® Adapter-Specific Identifiers.
● If you want to edit the identifiers, switch to change mode.
● Specify the names for your adapter-specific identifiers and choose Apply.
Access Control Using Assigned Users
You can restrict access to the runtime environment to specific users for a particular sender service. An authorization check is then carried out at runtime prior to inbound processing of the message. This ensures that messages that have the particular service entered as the sender in the message header can only be executed in the Adapter Engine by the specified users.
In addition, you can restrict the access control to a particular interface of the sender. You specify the authorized users in the configuration of the sender agreement, which contains the interface in the object key.
This function was specially designed for the configuration of business-to-business processes. You and your external business partner agree on a special user to be used for communication with SAP Exchange Infrastructure. You assign this user all services that the external business partner uses to send messages to your PCK. The external business partner must include this user when configuring their receiver channels (or when configuring their HTTP destinations).
This function is supported by the following (sender) adapters:
- XI Adapter
- RFC Adapter
- SOAP Adapter
- SAP Business Connector Adapter
●
To assign
authorized users, in the editor Edit Service,
choose the Assigned Users tab page. Insert a new
line for the new user (Insert Line After Selection 
) and enter the user name manually.
If no users are specified, there are no access restrictions for this service.
If you use adapters from third-party vendors, refer to the relevant documentation for the adapters to check whether this function is supported.
● To specify authorized users for a particular interface of the sender, in the editor Edit Sender Agreement, choose the Assigned Users tab page and insert the users line by line.
Note that the users specified for the sender agreement must match those assigned for the service, or must at least be a subset of these.
For some adapter types, it is not absolutely necessary to configure a sender agreement (see Sender Agreement) unless you want to make additional security settings. If you want to make access to the runtime environment dependent on the sender interface, you must define a separate sender agreement that contains the list of authorized users.