|
|
|
An Archive Request is
handled in the following way:
|
|
- The NG/AMS Server receives
the HTTP request and creates a new thread to handle this.
|
|
- If specified a response
may be send immediately.
|
|
- Based on the type of the
data the best suitable Target Disk Set for the file is found.
|
|
- The file is stored on the
Staging Area of the Target Disk.
|
|
- From the type of data the
Data Archiving Plug-In (DAPI) to handle this kind of data is determined.
|
|
- The request thread
imports/invokes the DAPI on the file.
|
|
- The DAPI checks the file,
extracts the information needed by NG/AMS and returns this to the calling
thread.
|
|
- NG/AMS moves the data file
to the final location defined by the DAPI.
|
|
- It updates the information
about the file in the DB.
|
|
- It replicates the files
(if specified) and updates the information about the Replication File in the
DB.
|
|
- If a response was not
generated at the beginning of the command handling this is generated now.
When updating the DB the DB access class generates temporary snapshot files
reflecting the changes in the DB. The Janitor Thread updates the DB Snapshot
in background.
|