Loading

AS2, OFTP2 and the Other Transports

A transport is how messages travel between you and a partner. Which one you use is usually the partner's choice. Transports are now set up on the EDI console's Transports tab, one form per kind, with every secret stored encrypted and masked on screen. Several partners can share one transport.

Where to find it

Admin Panel → ERP - Setup:

  • EDI — the Transports and AS2 certificates tabs

Architect Panel → ERP - Trading & Analytics:

  • EDI — the same console
  • EDI Transports and AS2 Certificates — the datastores behind them; edit on the console

The kinds

  • Shared folder (file drop): interchanges written to an Outbound folder and collected from an Inbound folder, with an optional Archive folder and Inbound file pattern (such as *.x12). Use it for a mounted VAN mailbox, a folder synced by another tool, or testing. One ships, switched off until a folder is set.
  • HTTPS POST: messages posted to the Partner endpoint URL (a public https address), with an optional Authorization header.
  • AS2: signed, encrypted, with a signed receipt (MDN). Settings: Partner AS2 URL, MIC algorithm (sha256 unless the partner says otherwise), Sign outbound messages, Encrypt outbound messages, MDN address, Asynchronous MDN URL (blank for a synchronous MDN), and an HTTP user and password if the partner needs one.
  • SFTP: Host, Port, Username, Password or Private key path, and remote outbound and inbound folders. The account must allow SCP and listing a folder; an account restricted to SFTP only is refused with that reason. It also needs the server's SSH extension, which the hosting administrator installs.
  • OFTP2: the automotive standard: host, port, your SSID identity and password, the virtual file name and certificate files. It is built but has not yet been run against a real OFTP2 partner, so test it thoroughly.
  • VAN mailbox: listed, but there is no direct VAN connection. Connect to your VAN through its SFTP or AS2 service, or a mounted folder, instead.

Who can set them up

Shared folder, SFTP and OFTP2 transports name folders and key files on the server, so only an architect can create or edit them, and every folder must sit inside the ERP drop-folder area that the hosting administrator configures for the installation. A folder outside it is refused. HTTPS and AS2 transports can be set up by ERP administrators.

Setting up an AS2 partner

  1. On Transports, add an AS2 transport with the partner's AS2 URL and agreed settings, and switch it on.
  2. On AS2 certificates, add a row for the partner: a Label, MIC algorithm, Our certificate (PEM), Their certificate (PEM), Our private key (PEM) and its Key passphrase. The key and passphrase are write-only: they are stored encrypted and never shown again.
  3. A partner's own certificate row overrides the transport's MIC algorithm and its sign and encrypt switches, and can Require a signed MDN: with that on, an unsigned or unverifiable receipt fails the send.
  4. Give the partner your AS2 address from the Partners tab (Issue URL).

Certificates expire

An expired certificate stops the exchange on a date known well in advance, and a swap needs both sides ready. Diary renewals at least 60 days ahead and agree the changeover date with the partner.

Switching a transport off

Switching off a transport that partners use asks first and names the partners it cuts off. Nothing is sent for, or acknowledged on behalf of, a partner that is disabled or deleted.

What goes wrong

  • A folder is refused: it is outside the drop-folder area. Ask the hosting administrator where that is.
  • SFTP fails: the server lacks the SSH extension, or the partner's account does not allow SCP and folder listing; the error says which.
  • The partner says messages are unsigned: check the partner's certificate row, which overrides the transport's switches.
  • Files are not picked up: the transport is off, the pattern does not match, or nobody has polled. Use Poll now on the Partners tab.

Worked example

A manufacturer trades with three retailers over AS2 and a dozen small customers through a VAN. The architect sets up a shared folder transport pointing at the folder the VAN's own software synchronises, and all twelve partners use it. The ERP administrator sets up one AS2 transport per retailer, loads each retailer's certificate and the company's key, and diaries the certificate expiry dates.

Recommendations

  • Enable only the transports you use.
  • Prefer a shared folder fed by your VAN's software for many small partners.
  • Diary certificate expiry 60 days ahead.
  • Test OFTP2 end to end with the partner before relying on it.