Troubleshooting agreements
Agreements can either be a transport-level agreement, such as AS2, or a protocol-level agreement, such as X12 or EDIFACT. In B2B scenarios with X12 and EDIFACT agreements, it can happen that the transport status returned to the client sending the message is an HTTP 200 OK, but the message landed in the suspend endpoint. This can happen if there are protocol-level errors. Such errors would be indicated by the acknowledgment message.
Some sample scenarios are shown in the following table:
|
Configuration |
Scenario |
Outcome |
|---|---|---|
|
AS2 standalone receive with sync MDN |
Incorrect configuration, for example, certificate incorrect |
HTTP 400 with error MDN |
|
AS2 standalone receive with async MDN |
Incorrect configuration, for example, certificate incorrect |
HTTP 200 OK for async and MDN with error |
|
AS2 standalone send |
Incorrect configuration, for example, certificate incorrect |
HTTP 500, AS2 Message Sender Activity error |
|
X12 or EDIFACT standalone receive |
Identities mismatch in... |
