Show TOC

Receiver AgreementLocate this document in the navigation structure

Use

You find the Web service description for a receiver agreement in the following data types. You find the data types in the Receiver Agreement folder.

Data Type

Description

MessageHeaderID (in Common folder)

Specifies object key

The same data structure is used for the object key for receiver determinations, interface determinations, sender agreements, receiver agreements, and direct connections.

For more information, see: Receiver Determination

Note that for a receiver agreement you must enter the name and namespace of the receiver interface.

ReceiverAgreement (or RestrictedReceiverAgreement)

Defines the receiver agreement with all attributes.

  • MasterLanguage , AdministrativeData , and Description ; more information: Cross-Object-Type Elements

  • ReceiverAgreementID : Object Key

  • CommunicationChannel : Specifies the assigned receiver communication channel.

  • AdapterSpecificAttribute : Adapter-specific attributes of the receiver determination.

    The adapter-specific attributes are dependent on the adapter type of the assigned communication channel.

  • AdapterSpecificTableAttribute

  • HeaderMapping : Specifies the header mapping.

    For more information, see below.

HeaderMapping

Defines the header mapping.

You enter the sender and receiver for the header mapping.

CommunicationPartnerExtractor

To be able to specify the sender or receiver in the header mapping, you must enter for both the sender or receiver party the name, identification schema, and the issuing agency and the name of the sender or receiver service.

Therefore you have four parameters each for both the sender and receiver.

  • CommunicationParty

  • CommunicationPartySchema

  • CommunicationPartyAgency

  • CommunicationComponent

    All parameters are based on type Extractor .

    For more information on defining an expression based on type Extractor , see Receiver Determination (Section Structure of Expressions ).