SDL Archiver service is used to control the running of plugins within TMS.

Early days

Historically there was just a single component of SDLTMS that would solely be responsible for archiving jobs. Over time other components were created through such methods as Broker Scripts (ran in a workflow stage) or server side batch files ran from automated scripts. This wasn't easy to maintain and certainly wasn't organised so the SDL Archiver service was born.

Plugins

Taking it's name from the original function of archiving jobs this service is now used to perform automated tasks that don't quite fit into the workflow processing. SDL Archiver Service runs as a single process and will load up related plugins upon start-up to perform an array of tasks. These plugins will have a configured frequency that they run at and at this point the SDL Archiver Service will start up a child process for this plugin.

SDLTMS will have some default plugins however it is possible to have custom plugins created for this service.  The plugins page can be seen within TMS from System>Services>Plugins and would typically include: