Working with Peppol TPA

Edit online

webMethods B2B Integration has a set of default TPA values according to the Peppol specification to help ensure the proper functioning of business documents in the Peppol network. You cannot delete or modify the Peppol-specific TPA. The agreement name for the default TPA is Peppol, and the value for the sender and the receiver is Unknown. You can make the TPA partner-specific by selecting the sender or receiver.

Peppol TPA variable Description
agreement URI of the location that contains the partner agreement. The default value is urn:fdc:peppol.eu:2017:agreements:tia:ap_provider.
mepBinding Messages exchange definition between two trading partners. The default MEP type is One-Way/Push. It sends a user message to a trading partner. For more information, see Message Exchange Patterns.
initiator Information that identifies the initiator of the message exchange. For more information about the variables, see initiator. The following list provides the default value for the sub fields of initiator:
  • type- urn:fdc:peppol.eu:2017:identifiers:ap.
  • role- http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/initiator.
  • host- false
responder Identifies the responder. For more information about the variables, see responder. The following list provides the default value for the sub fields of responder:
  • type- urn:fdc:peppol.eu:2017:identifiers:ap.
  • role- http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/responder.
  • host - false
legs Defines processing, transportation binding, and business information parameters. Click icon to add a leg before the current leg. For more information about the variables, see legs. The following list provides the default value for the sub fields of legs:
  • label - requestUM
  • businessInfo/mpc - http://docs.oasis-open.org/ebxml-msg/ebms/v3.0/ns/core/200704/defaultMPC.
  • errorHandling/report/asResponse - true
  • errorHandling/report/missingReceiptNotifyProducer - false
  • security/enableSecurity - true
  • security/includeTimeStamp - false
  • security/x509/sign/enableSign - true
  • security/x509/sign/attachments - true
  • security/x509/sign/signReceipt - true
  • security/x509/sign/signReceiptBody - true
  • security/x509/encrypt/enableEncrypt - true
  • security/x509/encrypt/attachments - true
  • security/x509/encrypt/encryptBody - false
  • security/x509/algorithmSuite - The available options are -
    • Advanced128Sha256GCM. This is the default value.
    • Advanced256Sha256GCM
    • Advanced128Sha256MGFSha1GCM
    • Advanced256Sha256MGFSha1GCM
  • security/usernameToken/policyStandard - PEPPOL
  • security/usernameToken/pmodeAuthorize - false
  • security/receipt/sendReceipt - true
  • security/receipt/replyPattern - response
  • security/receipt/nonRepudiation - true
  • receptionAwareness/enabled - false
  • receptionAwareness/retry/enabled - false
  • receptionAwareness/duplicateDetection/enabled - false
payloadService Configurable compression and decompression of application payloads. For more information about the variables, see payloadService. The following list provides the default value for the sub fields of payloadService:
  • compressionType - application/gzip
  • extractAttachment - false
  • validate - Validates the payload. The possible values are -
    • none. Validation is disabled.
    • inbound. Validates the inbound payload.
    • outbound. Validates the outbound payload.
    • both. Validates inbound and outbound payload The default value is both.
splitting The sending Messaging Service Handler (MSH) splits the message into multiple fragments during the sent operation of a large user message. For more information about the variables, see splitting. The following list provides the default value for the sub fields of splitting:
  • enabled - false.