Open Documentation Menu

Data communication d.ecs storage manager

The communication between the leading systems and the d.ecs storage manager is handled by

  • for d.3 via file systems (directory structure) and database tables or

  • at SharePoint via the d.ecs storage manager API

In both cases, documents are passed from the leading application to the d.ecs storage manager. The leading system (d.3) directly stores the documents in the directories which are also configured with the d.ecs storage manager or the documents are transferred via API (SharePoint and are temporarily stored in the directories configured with the d.ecs storage manager. The affected directories are configured via the d.ecs storage manager administration in the section Common.

In this process, the Public path and the Archive path (including the subdirectories) act as the directories for the transfer or temporary storage of documents that should be moved from d.ecs storage manager to the configured storage system. The Jukebox path is used by the d.ecs storage manager to provide documents requested by the leading application in this path or to store them temporarily for provision to SharePoint using the API.

Warning

Rights to the directories/files are required by the d.3 processes (d.3 hostimport/d.3 async/d.3 gateway, ...) and by the d.ecs storage manager itself. Typically, all named processes (except for d.3 gateway) are started by d.3 process manager (Windows service). Thus, it is usually sufficient to grant the respective rights to the user under which the service is running. d.3 gateway is also a Windows service and should thus be executed with the same user as d.3 process manager.