FileRelayDocumentation
Try for Free

SAP ArchiveLink Setup

How the SAP ArchiveLink protocol works with FileRelay — supported systems, request types, and the end-to-end document flow.

SAP ArchiveLink Setup

ArchiveLink is SAP's HTTP-based protocol for talking to external content repositories. FileRelay implements the HTTP Content Server interface (BC-HCS 4.5), so SAP treats it as a native content server.

The protocol has been stable for two decades. Any SAP system that can define a content repository in transaction OAC0 can talk to FileRelay.

Supported SAP systems

System Versions
SAP ECC (ERP) 4.6C and later
SAP S/4HANA All
SAP BW / BW/4HANA All
SAP Solution Manager All
SAP GTS All

How SAP talks to FileRelay

Every request is an HTTP(S) call from SAP to the FileRelay endpoint. SAP is the client; FileRelay is the content server. Two parameters identify the document: contRep (repository ID) and docId (document ID).

Create — store a document

POST /ContentServer?contRep=Z1&docId=ABC123&compId=data&pVersion=0047&command=create
Content-Type: multipart/form-data

[document binary]

FileRelay stores the doc, responds success, then routes it to all connected destinations.

Get — retrieve a document

GET /ContentServer?contRep=Z1&docId=ABC123&compId=data&pVersion=0047&command=get

Served from FileRelay's buffer or re-fetched from the destination — depends on workspace relay mode.

Info — check metadata

GET /ContentServer?contRep=Z1&docId=ABC123&compId=data&pVersion=0047&command=info

Returns size, content type, creation date.

Full command set

Command Purpose
create Store a new document
get Retrieve
info Get metadata
update Replace contents
delete Remove
search / attrSearch Find documents (used by some SAP modules)
serverInfo Server capabilities
putCert / getCert Exchange certificates

Standard query parameters

Parameter What it is Example
contRep Repository ID — maps to the FileRelay source Z1
docId Unique document ID 4A3F...
compId Component ID (usually data) data
pVersion Protocol version 0047
command The operation create

End-to-end flow

  1. SAP triggers archiving (e.g. printing with optical archiving on).
  2. SAP resolves the content repository via the document-type linkage (OAC3).
  3. SAP POSTs create to the FileRelay endpoint with the binary.
  4. FileRelay matches contRep to your source. If certificate verification is on, the request signature is checked against the active cert.
  5. FileRelay returns success to SAP.
  6. The document is routed through every active connection wired to the source — each destination forwarder delivers in parallel.

Connecting your SAP system

  1. Create a source in FileRelay with your chosen Repository ID (e.g. Z1).
  2. Configure OAC0 — see the OAC0 Guide.
  3. Exchange certificates — see Certificate Management.
  4. Link document types via transaction OAC3 so each SAP doc type knows to use your repository.
  5. Test via CSADMIN.

Testing with CSADMIN

CSADMIN is SAP's test harness for content servers. Open it → pick your repository → Test to send a small document. The arrival should show up on the FileRelay dashboard. You can also retrieve a document, check server info, and trigger the certificate exchange from this screen.

Next steps