The leading SAP systems and the interface d.velop archivelink for SAP Solutions (Content Server) communicate via the HTTP/HTTPS protocol. Depending on the connected storage system d.3ecm, ecspand for SharePoint or d.ecs storage manager and depending on the storage modes, the communication takes place via file systems or API import and database tables.

The storage modes synchronous or asynchronous storage, API import as well as the file directories (so-called “export directory") are configured in the configuration of the content repositories under section "Archive Mode” of the administration of d.velop archivelink for SAP Solutions. In the mode API import “Off”, the documents and related metadata files are stored in the export directory. These files can also be additionally protected by using external operating system tools. Having successfully imported into the connected d.3ecm, SharePoint, SharePoint Online or d.ecs storage manager, this information is deleted.

Important: Rights for the directories/files are required by the d.3ecm/SharePoint processes (hostimport/Async/d.3 gateway,ecspand Importservice,...) and the d.ecs storage manager itself. Typically, all named d.3ecm processes (except for d.3 gateway) are started by the d.3 process manager (Windows service). Thus it is typically sufficient to assign the respective rights to the user under which the service is running. The d.3 gateway is also a Windows service and should thus be executed with the same user as the d.3 process manager.

For the ArchiveLink storage of inbound documents, the scanned image files including their JPL files with the barcode and workflow information are directly stored in the file directories for further processing. The file directories are defined in the configuration of the so-called “HTTP script” under “Barcode” and “Workflow directory”. Having successfully stoired and linked the documents, these files are deleted. These files can also be additionally protected by using external operating system tools.