RISE customers get all three SAP document protocols. We route documents from any of them to S3, SharePoint, Azure, or anywhere else.
Setup with ArchiveLink
OAC0 to first routed document in under 15 minutes.
Setup with ArchiveLink
Inside your FileRelay deployment, create a workspace and a repository. The ingest endpoints SAP will call are derived from their slugs.
On your FileRelay instance, create a workspace per environment (dev / prod) and a repository per SAP system. FileRelay generates the ArchiveLink Content Server URL automatically — the same repository also accepts CMIS webhooks and OData events at sibling paths.
Every line here is a project we’ve already built so you don’t have to. Compare what your team would own end-to-end to what ships with FileRelay on day one.
6–12 weeks of ABAP + ICF + basis to implement the Content Server HTTP interface
Update one URL in OAC0 — FileRelay speaks ArchiveLink natively
Write a new connector per destination, learn OAuth/SAS/JWT/IAM, maintain SDKs forever
15+ destinations shipped — paste creds, pick a folder, done
Design retry, backoff, dead-letter, and audit log from scratch — and prove it to your auditor
Every document, every routing decision, exportable trail — already there
Build a per-tenant credential vault with key rotation and KMS hooks before you write a single connector
Per-user envelope encryption, AAD-bound to each field, KMS-ready
Workspace isolation, RBAC, per-system routing — that’s the control plane before you ship a feature
Owner/admin/member roles, per-workspace keys, per-SAP routing built-in
Patches, breaking API changes, new destinations as products evolve — forever
We track those changes so your team doesn’t
FileRelay routes SAP ArchiveLink documents to any of these systems.
OpenText, Documentum, and other enterprise systems are on the roadmap. Tell us which you need and we'll prioritize it for your launch.
We deploy FileRelay into your environment so you can test it on your SAP. Request a pilot and we'll be in touch within one business day.