Repository cache and how it works

Agent Handlers automatically cache content and product updates if a McAfee Agent can't access the content directly from the Master Repository on the McAfee ePO server.

The McAfee Agent, by default, uses the primary McAfee ePO server (same server as Tomcat) as the Master Repository. Agents fail back to the Agent Handler if they are unable to communicate with their configured remote repository to pull content and product updates. Since the Agent Handler might not be running on the same server as the true Master Repository (on the McAfee ePO server), the Agent Handler manages these requests. Agent Handlers transparently handle requests for software and cache the required files after downloading them from the Master Repository. No configuration is necessary.

  1. Systems 1 and 2 attempt to pull content or product updates from their configured remote repository and the attempt fails.
  2. For System 1, the McAfee Agent is configured, by default, to use Primary Agent Handler 1 that is part of the McAfee ePO server. If the connection to the remote repository fails, System 1 requests the content or product updates directly from the Master Repository on the McAfee ePO server.
  3. For System 2, the McAfee Agent is configured to use Secondary Agent Handler 2, if the connection to the remote repository fails.
  4. Secondary Agent Handler 2 requests the content or product updates from the Master Repository.
  5. Secondary Agent Handler 2 caches those updates, for any subsequent requests, and delivers them to System 2.

This diagram shows how Agent Handlers cache product update content if the configured remote repository is unavailable to remote systems.

Agent Handler repository caching