MCPServer - Revision history

Sallain at 21:58, 11 February 2020

2020-02-11T21:58:12Z

Sallain at 21:33, 10 October 2018

2018-10-10T21:33:31Z

Hbecker: /* Config File */ Description of config file variables

2017-03-10T01:20:59Z

Config File: Description of config file variables

Hbecker: Stub of config file section, remove link to deprecated page

2017-03-10T00:54:16Z

Stub of config file section, remove link to deprecated page

Hbecker: Remove Client section, link to MCPClient

2017-03-10T00:50:24Z

Remove Client section, link to MCPClient

Hbecker: Update breadcrumbs to MCPServer

2017-03-08T18:24:07Z

Update breadcrumbs to MCPServer

Hbecker: /* Task Types */ Update task types link

2017-03-08T18:19:27Z

Task Types: Update task types link

Hbecker: /* Database Reference */ Update task types link

2017-03-08T18:18:35Z

Database Reference: Update task types link

Hbecker: Hbecker moved page MCP to MCPServer: MCP too broad - this page will only cover the MCPServer, and MCPClient will be its own page

2017-03-08T18:16:45Z

Hbecker moved page MCP to MCPServer: MCP too broad - this page will only cover the MCPServer, and MCPClient will be its own page

Hbecker: /* Old FPR Database Reference */ Make deprecation warning more visible

2016-10-11T18:08:39Z

Old FPR Database Reference: Make deprecation warning more visible

← Older revision		Revision as of 21:58, 11 February 2020
Line 1:		Line 1:
	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP Server		[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP Server

		+	<div style="padding: 10px 10px; border: 1px solid black; background-color: #F79086;">This page is no longer being maintained and may contain inaccurate information. Please see the [https://www.archivematica.org/docs/latest/ Archivematica documentation] for up-to-date information. </div> <p>

	The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system. Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work in the database and log files.		The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system. Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work in the database and log files.

← Older revision		Revision as of 21:33, 10 October 2018
Line 1:		Line 1:
	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP Server		[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP Server

−
−	~~<div class="status">~~
−	~~<div>~~
−	~~Design~~
−	~~<div class="description">~~
−	~~This page proposes a new feature and reviews design options~~
−	~~</div>~~
−	~~</div><div>~~
−	~~Development~~
−	~~<div class="description">~~
−	~~This page describes a feature that's in development~~
−	~~</div>~~
−	~~</div><div class="active">~~
−	~~Documentation~~
−	~~<div class="description">~~
−	~~This page documents an implemented feature~~
−	~~</div>~~
−	~~</div>~~
−	~~</div>~~

	The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system. Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work in the database and log files.		The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system. Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work in the database and log files.

@@ Line 271: / Line 271: @@
 == Config File ==
 Several basic startup settings are read from the config file at <code>/etc/archivematica/MCPServer/serverConfig.conf</code>.
 == Old FPR Database Reference ==

@@ Line 21: / Line 21: @@
 </div>
-The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system.  Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work. To edit basic MCP Configuration, see [[MCP_Basic_Configuration|MCP Basic Configuration]].
+The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system.  Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work in the database and log files.
 Microservices are run in chains.  On startup, Archivematica checks all the watched directories it is aware of.  For each file in those directories, it creates a Job Chain and an associated unit (SIP, DIP or Transfer).  The Job Chain runs until completion, which usually puts the Transfer/SIP in another directory, to start another chain.
@@ Line 268: / Line 268: @@
 |-
 |}

@@ Line 21: / Line 21: @@
 </div>
-The MCP is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system.  Configuration and processing information are held in the database. The user monitors and controls the MCP via the [[ dashboard ]]. The MCP maintains a log of all completed work. To edit basic MCP Configuration, see [[MCP_Basic_Configuration|MCP Basic Configuration]].
+The MCP Server is the core of the Archivematica system. It controls the various [[micro-services]] in the Archivematica system.  Configuration and processing information are held in the database. The user monitors and controls the status & workflow via the [[ dashboard ]]. The MCP Server maintains a log of all completed work. To edit basic MCP Configuration, see [[MCP_Basic_Configuration|MCP Basic Configuration]].
 Microservices are run in chains.  On startup, Archivematica checks all the watched directories it is aware of.  For each file in those directories, it creates a Job Chain and an associated unit (SIP, DIP or Transfer).  The Job Chain runs until completion, which usually puts the Transfer/SIP in another directory, to start another chain.
-The MCP uses the [http://gearman.org gearman]. The MCP Clients are relatively "dumb". They are gearman worker implementations, that inform the gearman server what tasks they can perform, and wait for the server to assign them a task.
+The MCP uses [http://gearman.org gearman] as a task manager. The [[MCPClient | MCP Clients]] are relatively "dumb". They are gearman worker implementations, that inform the gearman server what tasks they can perform, and wait for the server to assign them a task.
 The Archivematica system relies on client and server having access to the same directory, to process the commands. On a distributed system, this is done through the shared directory.
-All files for the MCPServer are found in ''src/MCPServer/lib/'', and all files for the MCPClient are found in ''src/MCPClient/lib/''.
+All files for the MCPServer are found in ''src/MCPServer/lib/'', and all files for the [[MCPClient]] are found in ''src/MCPClient/lib/''.
@@ Line 64: / Line 64: @@
 ===Task Types===
 This has been moved to [[/TaskTypes | a task types sub page]]

← Older revision		Revision as of 18:24, 8 March 2017
Line 1:		Line 1:
−	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP	+	[[Main Page]] > [[Development]] > [[:Category:Development documentation\|Development documentation]] > MCP Server

@@ Line 63: / Line 63: @@
 ===Task Types===
-[[MCP/TaskTypes]]
+This has been moved to [[/TaskTypes | a task types sub page]]
 ==Client==

@@ Line 103: / Line 103: @@
 * '''Referenced by''': TasksConfigs
 * Each TaskType is associated with a linkTaskManager* class
-* [https://www.archivematica.org/wiki/MCP/TaskTypes More detail ]
+* [[/TaskTypes | More detail ]]
 === MicroServiceChainLinksExitCodes ===

@@ Line 275: / Line 275: @@
 == Old FPR Database Reference ==
-'''WARNING''' This is not accurate in Archivematica 1.0 or greater - file identification and normalization rules have been moved to the new FPR schema.
+{| class="wikitable" style="background-color:#ffcccc; font-size: 120%; font-weight: bold; " cellpadding="10"
 === FileIDsBySingleID ===