AS4 conformance profiles

The AS4 specification defines three basic conformance profiles: ebHandler, Light and Minimal Client. These basic profiles can be extended with the AS4 Multi-Hop Endpoint Conformance Clause to add support for multi-hop messaging. For each profile it is defined which P-Mode parameters must be supported to claim conformance to the profile. The table below lists these P-Mode parameters and shows whether Holodeck B2B supports them.  P-Mode parameters are only included in this table if support for a parameter is required by any of the AS4 profiles or if Holodeck B2B offers support for it.

This table applies to Holodeck B2B version 2.1.

Legend
✓ = required / supported in Holodeck B2B
O = optional
N = not required / not supported in Holodeck B2B

P-Mode parameterHolodeck B2BAS4 ebHandlerAS4 Light ClientAS4 Minimal Client
General P-Mode parameters
PMode.ID
PMode.Agreement
PMode.MEPOne-WayOne-WayOne-WayOne-Way
PMode.MEPBindingOne-Way/Push
One-Way/Pull both as Initiator and Responder
One-Way/Push
One-Way/Pull both as Initiator and Responder
One-Way/Push
One-Way/Pull as Initiator
One-Way/Push
PMode.Initiator.Party
PMode.Initiator.Role
PMode.Initiator.Authorization.usernameN
PMode.Initiator.Authorization.password N
PMode.Initiator.Authorization.Digest (*1)---
PMode.Initiator.Authorization.Nonce (*1)---
PMode.Initiator.Authorization.Created (*1)---
PMode.Responder.Party
PMode.Responder.Role
PMode.Responder.Authorization.usernameNN
PMode.Responder.Authorization.passwordNN
PMode.Responder.Authorization.Digest (*1)---
PMode.Responder.Authorization.Nonce (*1)---
PMode.Responder.Authorization.Created (*1)---
PMode[1].Protocol
PMode[1].Protocol.Addresshttp and https (*2)http and httpshttphttp
PMode[1].Protocol.AddActorOrRoleAttributeC (*3)C (*3)C (*3)
PMode[1].Protocol.SOAPVersion1.1 and 1.21.21.21.2
PMode[1].BusinessInfo
PMode[1].BusinessInfo.MPCN
PMode[1].BusinessInfo.subMPCextOON
PMode[1].BusinessInfo.Service
PMode[1].BusinessInfo.Action
PMode[1].BusinessInfo.Properties[]N
PMode[1].BusinessInfo.PayloadProfile[]NOON
PMode[1].ErrorHandling
PMode[1].ErrorHandling.Report.SenderErrorsToNNNN
PMode[1].ErrorHandling.Report.ReceiverErrorsToNN
PMode[1].ErrorHandling.Report.AsResponse
PMode[1].ErrorHandling.Report.ProcessErrorNotifyConsumerNNNN
PMode[1].ErrorHandling.Report.ProcessErrorNotifyProducerN
PMode[1].ErrorHandling.Report.DeliveryFailuresNotifyProducerNN (*4)N (*4)N
PMode[1].ReceptionAwareness
PMode[1].ReceptionAwarenessN
PMode[1].ReceptionAwareness.RetryN
PMode[1].ReceptionAwareness.Retry.ParametersMax. number of retries
Interval
N
PMode[1].ReceptionAwareness.DuplicateDetectionN
PMode[1].ReceptionAwareness.DetectDuplicates.ParametersFixed, complete message log is checked for duplicatesOON
PMode[1].Security
PMode[1].Security.WSSVersion1.1.11.11.1N
PMode[1].Security.X509.SignN
PMode[1].Security.X509.Signature.CertificateN
PMode[1].Security.X509.Signature.HashFunctionN
PMode[1].Security.X509.Signature.AlgorithmN
PMode[1].Security. X509.Encryption.EncryptNN
PMode[1].Security.X509.Encryption.CertificateNN
PMode[1].Security.X509.Encryption.AlgorithmNN
PMode[1].Security.X509.Encryption.MinimumStrengthNNNN
PMode[1].Security.UsernameToken.usernameN
PMode[1].Security.UsernameToken.passwordN
PMode[1].Security.UsernameToken.DigestN
PMode[1].Security.UsernameToken.NonceNNN
PMode[1].Security.UsernameToken.CreatedN
PMode[1].Security.PModeAuthorizeImplicit. Derived from PMode.[Initiator|Responder]. Authorization.N
PMode[1].Security.SendReceiptN
PMode[1].Security.SendReceipt.NonRepudiation (*5)✓ (*6)N
Pmode[1].Security.SendReceipt.ReplyPatternN
Pmode[1].Security.SendReceipt.ReplyTo (*7)N
AS4 Compression Feature
PMode[1].PayloadService.CompressionTypeN

(*1) These parameters are not mentioned in either AS4 Profile and ebMS V3 Core Specification for the UsernameToken included in the WS-Security header targeted to “ebms”.
(*2) https support only as client.
(*3) Support for this parameter is required when the AS4 Multi-Hop Endpoint Conformance Clause is used.
(*4) The AS4 profile version 1.0 erroneously states that support is required for this parameter. See issue 59 on the ebXML Messaging TC’s issue list.
(*5) This parameter is defined in (non-normative) section 5.2.1 of the AS4 profile. See also issue 30 in the issuetracker of the OASIS TC.
(*6) Holodeck B2B supports sending NRR Receipts, but determination of receipt type is currently based on whether the acknowledged user message is signed or not. When signed Holodeck B2B will create a NRR Receipt, otherwise a Reception Awareness Receipt will be created.
(*7) This parameter is defined in (non-normative) section 6.7.1 of ebMS V3 Part 2. Support for this parameter is required if the ReplyPattern value is “callback”. See also issue 33 in the issuetracker of the OASIS TC.