Open Documentation Menu

d.ecs task

In order to use d.ecs task, you must first install it and register it with the d.ecs http gateway app.

Enable the option ENABLE_TASKAPP in the file d3addon.ini file to turn on d.ecs task support for the d.3 server.

Note

Also read the prerequisites and important information about enabling the ENABLE_TASKAPP option in our KB article 000001788 "How do I migrate my mailbox to d.ecs task with the ENABLE_TASKAPP parameter?".

If errors occurred during migration after enabling the option, the KB article 000001797 "Fixing migration errors after enabling the ENABLE_TASKAPP parameter" may help you.

In future versions, d.ecs task will completely replace the d.3 mailbox. In one of the next d.3ecm current versions, this option will be enabled automatically for new installations accordingly. For update installations, the current status for using the d.3 mailbox or d.ecs task remains unchanged.

In d.3 config, enter DECS_SERVICE_USER and DECS_SERVICE_USER_PWD so that the d.3 server can authenticate itself to the Task app. Give the service user you specified in d.3 config the "Service user" role in the Task app. The setup for this can be found in the chapter "Setting up user roles" in the d.ecs task administration manual.

Enabling this has the following effects:

  • All new mailbox entries are no longer created in the d.3 database, table wieder_vorlage, but are forwarded directly to d.ecs task.

  • All API function calls with a direct mailbox reference (except SendHoldFile) run into an error.

  • The previous mailbox entries are forwarded to d.ecs task and deleted from the table wieder_vorlage. Only the entries that have not yet been acknowledged are taken into account. All acknowledged entries are deleted.

  • An entry is created in the history table with the action type WVMIG1 for all mailbox entries which have not been acknowledged.

A subsequent disabling of the parameter has the following effects:

  • The entries at d.ecs task are not transferred back into the d.3 mailbox.