Manage Connections for AS2 Transport with Common URL or Endpoint
Connections used for AS2 transports that share a common AS2 URL or endpoint are not directly linked to specific B2B transport integrations. Instead, these connections are dynamically selected at runtime based on the AS2-From header for transport identification.
Due to their unique behavior during runtime, AS2 connections with common URLs or endpoints require careful management.
Key considerations
- The connections will not appear as being used in the B2B transport integrations.
- The connection page does not prevent deletion of these connections. However, if such a connection is deleted, any inbound messages relying on it will fail at runtime when attempting to retrieve the connection details. Therefore, do not delete these connections unless you have confirmed they are not used by any common AS2 transports.
- Tip: To help identify these connections more easily, consider adopting clear naming conventions.
- After updating these connections, you must redeploy the corresponding transport. Failing to do so will cause inbound messages to fail at runtime when attempting to fetch the updated connection details.