The following sections are examples of standard Legacy AMC workflows for various requests, followed by a description of the sequence of events for each request.
This chapter includes the following information:
The general Archive workflow is as follows:
The Media Services application submits a JobXML to the Archive service.
The Archive Service loads the fpdiDET2.dll
and DET2
calls provided.
The fpdiDET2
uses the Avid Archive SDK for this purpose.
The fpdiDET2
connects to AMC, and submits the JobXML.
AMC receives the command and then receives the JobXML from fpdiDET2
.
The JobXML is parsed and a list of all files, and their details, is constructed.
AMC confirms whether the clip (or sequence of clips) is part of any existing object, determines if it requires deletion (based on the configuration), and then sends the Archive request to the Manager.
If a Delete operation is required, the workflow in the following is initiated to perform the action.
The Manager notifies the Actor of the request, and then the Actor contacts the AMC service and proceeds to archive the objects.
When a required Delete operation is identified by AMC, the general Delete workflow is as follows:
The Avid Archive Engine sends a Delete command to the AMC service.
The AMC service notifies the Manager that a delete is required, and then the Manager processes the request.
The general Restore workflow is as follows:
The Media Services Application submits a JobXML to the Restore service.
The Restore service loads the fpdiDET2.dll
and DET2
calls provided.
The fpdiDET2
connects to AMC, and then submits the JobXML.
AMC receives the command, and then receives the JobXML from fpdiDET2
.
The JobXML is parsed and a list of all files, and their details, is constructed.
AMC searches all categories and identifies a list of objects to Restore, and then sends the Restore request to the Manager.
The Manager notifies the Actor of the request, and then the Actor contacts the AMC service and proceeds to restore the objects.