Archive data flow

Enterprise configuration data is generated:
1. User assigns Archive server roles in the framework portal Home page or main UI access point for all WFO applications. (Enterprise Manager) under System Management Module that allows performing suite-wide system management activities from a single, Web-based application, the Enterprise Manager. > Enterprise > Settings.
2. If performing Central Archive, user associates Recorders with servers assigned the Central Archive role.
3. User defines Campaigns (Central or selective Local Archive), schedules, and Archive media in the framework portal under Recording Management > Campaigns.
Enterprise Manager stores configuration data:
1. Media configuration data is stored in the Archive Database.
2. All other configuration data is stored in the Foundation Database.
Enterprise Manager builds configuration files that it distributes.
User defines Archive Drives in Recorder Manager.
Recorder Manager stores configuration details locally in configuration xml files.
The Archiver reads the XML files and determines which interactions to archive:
1. Confirms that archiving is allowed from target recorder based on associated schedule (if any).
2. Queries the calls database for Central Archive jobs or Selective Local Archive jobs.
3. Queries the Recorder Workflow for 100% Compliance Local Archive jobs.
Archiver fetches files in job list:
1. Direct read from call buffer for Local Archive.
2. HTTP fetch from remote Recorder for Central Archive.
  
  Content Server Server role in the Site zone that uses an HTTP/HTTPS Web-based file retrieval component to search for interactions. The content server’s search is triggered by the Locator, which is the Interaction Applications’ DLL. retrieves the files for the HTTP fetch.
Archiver builds TAR files.
- TAR files are built in memory within the Archiver process. 100 MB of RAM is pre-allocated for the TAR for each archive drive.
- Archiver does not recognize interaction In Speech Analytics, an interaction represents a single part of the contact between one employee and the same customer. In Text Analytics, an interaction is the communication session between one or more employees and the same customer with a unifying contextual element. stitching, so segments can be archived to different TAR files.
The Archiver writes the TAR file to the target media.
- Writing occurs every hour (3600 seconds) or sooner if the TAR file reaches the 100-MB file size.
- For supported media, if a recording exceeds 100 MB, a single TAR file is extended in size up to 3.99 GB. As the archive occurs, the TAR file is written to media instead of being buffered in memory.
Archiver updates the Archive Database with TAR file and storage details.