Agent Handlers automatically cache content and product updates if a Trellix Agent can't access the content directly from the Main Repository on the ePO - On-prem server.
The Trellix Agent, by default, uses the primary ePO - On-prem server (same server as Tomcat) as the Main 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 Main Repository (on the ePO - On-prem server), the Agent Handler manages these requests. Agent Handlers transparently handle requests for software and cache the required files after downloading them from the Main Repository. No configuration is necessary.
Systems 1 and 2 attempt to pull content or product updates from their configured remote repository and the attempt fails.
For System 1, the Trellix Agent is configured, by default, to use Primary Agent Handler 1 that is part of the ePO - On-prem server. If the connection to the remote repository fails, System 1 requests the content or product updates directly from the Main Repository on the ePO - On-prem server.
For System 2, the Trellix Agent is configured to use Secondary Agent Handler 2, if the connection to the remote repository fails.
Secondary Agent Handler 2 requests the content or product updates from the Main Repository.
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.
