Protocols, APIs and security, in depth
How each protocol works, when a trading partner requires it, and how Archr.Hermod configures it; how the papiNet REST API is served, called and connected to your back end; and developer guides to the SDK for C#, Java, TypeScript and Python. For implementation-level detail beyond this reference, see the project's own documentation and source.
-
ebMS 2.0
The ebXML Messaging Service — SOAP-based, CPA-driven, with built-in reliable delivery.
-
AS2 (RFC 4130)
MIME-based messaging over HTTP/HTTPS with S/MIME security and MDN receipts.
-
SFRM
Large files cut into segments, each checked with a checksum, optionally signed and encrypted, and acknowledged when the whole file has arrived.
-
Security & Certificate Management
How signing keys, partner certificates, and per-message cryptography are managed.
-
papiNet REST API
A secured HTTPS API for your trading partners, built from the papiNet specification and carried over your message queue to the system that holds the data.
-
papiNet outbound API hub
One place your applications use to call trading partners' papiNet APIs: endpoints, credentials and limits live in Archr.Hermod, not in every application.
-
Connecting your back-end system
Typed messages, .NET, TypeScript, Java and Python contracts, and ready-made adapters and clients for .NET Framework, Java, Node.js and Python applications.
-
SDK guide 1: A comprehensive overview of how to use Java, C#, TypeScript and Python with Archr.Hermod
Using the SDK with your back-end systems, SDK reference by language, and the handling the papiNet messages.
-
SDK guide 2: Handling inbound papiNet API calls and integrating with your business applications
Step by step, with code in Java, C#, TypeScript and Python: connect to the queue, write a handler for each operation, answer with the right status, and find out why a caller gets 502 or 504.
-
SDK guide 3: Making outbound API calls with trading partners from your business application
Step by step, with code in Java, C#, TypeScript and Python: set up a partner, make a call through the outbound hub, read the outcome, and what happens on the wire.
-
ebMS guide: setting up and running ebXML Messaging (ebMS 2.0)
What to agree with your partner, how a message travels, what each setting of an ebMS partnership does, how to send and receive, and how to follow a message to its acknowledgement.
-
AS2 guide: setting up and running AS2 (RFC 4130)
What to agree with your partner, how a message and its receipt (MDN) travel, what each setting of an AS2 partnership does, how to send and receive, and what to try when a partner rejects a message.
-
SFRM guide: sending and receiving large files in segments
How a file is split into segments, checked and put back together, what each setting of an SFRM partnership does, how to send and receive, and how a transfer is acknowledged and retried.