AS2 Setup Guide

Prerequisites

• Partner AS2 IDs, URLs, and encryption/signing requirements.
• X.509 certificates (PEM or PFX). Datasync can also generate certificates on your behalf.
• Outbound network access allowed to the partner endpoint (Datasync publishes IP ranges per region).

1. Create an AS2 transport

1. Navigate to Connectivity → AS2 and click Create Transport.
2. Choose Managed (Datasync hosts the endpoint) or Hybrid (you host, Datasync manages certs/monitoring).
3. Provide:
   • Partner AS2 ID and Datasync AS2 ID.
   • Encryption/signature algorithms (recommended: AES-256 + SHA-256).
   • Preferred MDN mode (synchronous or asynchronous).

2. Upload certificates

• Upload partner public certificates and optional intermediate chains.
• Generate Datasync private/public key pairs or import existing ones.
• Enable automatic rotation reminders (30, 15, and 5 days before expiry).

3. Configure MDN & retries

• Choose retry policy (default: 3 attempts, exponential backoff).
• Define MDN breach alerts to notify operators if acknowledgements exceed SLA.
• Enable auto-resend after certificate rotation so you never lose transactions.

4. Testing

Use the built-in AS2 sandbox to validate connectivity:

datasync transports as2 test --partner target --document sample-invoice.edi

• Datasync compares headers, content, and MDN signatures, then stores the transcript for audit purposes.

5. Promote to production

• Switch the endpoint status to Live.
• Provide partners with Datasync endpoint details (URL, AS2 ID, certificates) directly from the console.
• Monitor traffic in Live Visibility to ensure MDNs, retries, and SLAs look healthy.

Troubleshooting tips

• Use the Replay action to resend failed payloads without regenerating data from your ERP.
• Download AS2 logs and full payload copies when coordinating with partner support teams.
• Reach the Datasync NOC anytime at noc@datasync.com for urgent AS2 incidents.