Integrations overview
ARender integrates with document management systems through repository connectors — Java JARs loaded on the viewer's classpath. Each connector implements DocumentAccessor and fetches documents using the ECM's native API (CMIS, FileNet P8 CE, HTTP, etc.).
For the conceptual model, see Connectors concept.
ARender-maintained integrations
| ECM | Guide |
|---|---|
| Alfresco Content Services | Alfresco integration |
| IBM FileNet P8 | IBM FileNet integration |
| IBM Content Navigator | IBM Content Navigator integration |
| Any (custom connector) | Custom connector development |
Partner-maintained integrations
These integrations are developed and supported by partners. Contact the partner for documentation and support.
| ECM | Partner |
|---|---|
| Hyland Nuxeo | Hyland |
| Alfresco Process Services | Hyland |
| OpenText Documentum | OpenText |
| Tessi Docubase / Data Content | Tessi |
| Extedo EXTEDOpulse / esubmanager | Extedo |
| Salesforce | Salesforce |
ARender as a rendering service
The inverse pattern: a host system calls ARender's REST API to generate page images and PDFs for its own previews, thumbnails, and archive, without involving the ARender viewer.