Question
Hello,
I was running a test with two Domibus instances, sending a message from one to the other with the default test settings as found in the distribution files.
The default PayloadProfile ( called "MessageProfile" ) has two payloads defined:
- businessContentPayload with CID "cid:message"
- businessContentAttachment with CID "cid:attachment"
I noticed that the ResponderParty uses the PayloadProfile defined in the PMode to process the incoming message. If the message does not conform to the profile, it will be rejected.
My question: is the "MessageProfile" as found in the examples the standard way to send messages in the eDelivery AS4 setting? Or is there a specific way to configure the Responder to be able to accept unknown/foreign payload profiles??
Author: Marco DE TIEGE
Answer
Hello,
You are able to change the payload profile based on mime types as defined in the "Administration Guide". However, there needs to be an alignment between the sender and the receiver for the system to function without errors.
CEF Support
Answer from Marco DE TIEGE
Thank you for answering and explaining there needs to be an alignment between sender and receiver. What happens if the receiver is agnostic of what the sender is sending? How can the alignment be achieved if both parties are foreign to each other?
Answer from CEF Support
The best way for that is to remove the package/payload verification. To do that, you would modify the legConfiguration used for your particular use case. You would need to remove the payloadProfile definition in that particular legConfiguration.
Let me know how it goes. Note that It is always best to specify the nature of the message for the processing of the message, and as an extra layer of security. This is why we provide the payload profile in the PMode.
Answer from Marco DE TIEGE
Hello Alexander, for the receiving Domibus, I removed the payloadProfile attribute in the legConfiguration and I can now receive the messages, thank you for your help!