Generic/Specific Definition of Receiver
Agreements
Use
You can create a receiver agreement generically for the following key attributes:
· Sender party
· Sender service
· Inbound interface (name and namespace)
In the following instances, it is recommended that you (partly) define a receiver agreement generically:
Typical Usage
Unspecified Key Attribute (Wildcard Character *) |
Use |
Receiver interface |
The same communication channel should be valid for all interfaces in a business system (for example, in internal business processes). |
Sender party and sender service |
The sender must only authenticate itself in the receiver system, regardless of where the message was sent from. This is recommended for internal company processes, for example. |