Integrations
/ Axway
Integrations · Middleware
TracePharma + Axway
Axway is middleware, not an L4 competitor. TracePharma interoperates when your partners or IT team routes EPCIS through an Axway gateway to your tenant AS2 endpoint or HTTPS webhook.
Preset:
axway
AS2
HTTPS
Pulse ecosystem vendor
Axway is a Pulse-listed integration platform used by manufacturers and wholesalers for AS2 and managed file transfer. TracePharma supports native AS2 and Axway-forwarded HTTPS patterns. Enterprise EDI teams keep their gateway while you run operator L4 workflows.
Inbound interoperability
- ✓ Native AS2 receive with partner certificates registered per connection.
- ✓ HTTPS webhook when Axway transforms and forwards EPCIS to TracePharma.
- ✓ Axway preset documents gateway URL and partner cert exchange checklist.
Outbound & compliance
- ✓ Outbound EPCIS returned via AS2 or partner-configured gateway paths.
- ✓ MDN and ACK tracking surfaced in integration health views.
- ✓ Same outbound generation engine as direct partner connections.
Typical cutover steps
- 1 Work with EDI team to map Axway partner profiles to TracePharma endpoints.
- 2 Exchange AS2 IDs, certificates, or webhook tokens per connection.
- 3 Run test messages through Axway staging before production promotion.
- 4 Monitor integration health for certificate expiry alerts.
Best for
- → Enterprises with existing Axway B2B infrastructure.
- → TraceLink paths that require Axway gateway in the middle.
- → IT teams that will not expose L4 directly but will forward EPCIS.
Axway interoperability FAQ
- Is Axway a TracePharma competitor?
- No. Axway moves messages; TracePharma is your L4 DSCSA application. You typically run both—Axway for transport, TracePharma for receiving, exceptions, VRS, and compliance.
Connect Axway in your tenant
We'll walk through inbound preset setup, test receiving, and ACK monitoring on a profile-tuned demo workspace.