The SuperAgent caches the contents of its repository in a way that minimizes the load on ePO - On-prem.
If an agent has been converted to a SuperAgent, it can cache content from , the distributed repository, or other SuperAgent to distribute locally to other agents, reducing load on ePO - On-prem.
Note
SuperAgent caching with repository replication is not recommended. The SuperAgent can't cache content from HTTP or FTP repositories.
How LazyCaching works
The LazyCaching feature allows the SuperAgent to retrieve data from the configured repositories only when requested by a local agent. When a client system first requests content, the SuperAgent assigned to that system downloads the requested content from its configured repositories and caches that content. The cache is updated when a newer version of the requested package is available in the Main Repository. Creating a hierarchy of SuperAgents with LazyCaching further saves bandwidth and minimizes the load on ePO - On-prem. When a hierarchical structure of SuperAgent is created, the child SuperAgent receives the requested content update from its parent's cache.
The SuperAgent is guaranteed only to store content required by the agents assigned to it because it does not pull any content from the repositories until requested from a client. This minimizes traffic between the SuperAgent and the repositories. While the SuperAgent is retrieving content from the repository, client system requests for that content are paused.
To enable LazyCaching, go to → → → → → , then select Enable LazyCaching.
Important
The SuperAgent must have access to the repository. Without this access, agents receiving updates from the SuperAgent never receive new content. Make sure that your SuperAgent policy includes access to the repository.
Agents configured to use the SuperAgent as their repository receive the content cached in the SuperAgent instead of directly from ePO - On-prem. This improves agent system performance by keeping most network traffic local to the SuperAgent and its clients.
If the SuperAgent is reconfigured to use a new repository, the cache is updated to reflect the new repository.
How communication interruptions are handled
When a SuperAgent receives a request for content that might be outdated, the SuperAgent tries to contact ePO - On-prem to see if new content is available. If the connection tries time out, the SuperAgent distributes content from its own repository instead. This content transfer is done to make sure that the requester receives content even if that content might be outdated.
Important
Do not use SuperAgent caching with global updating. These features serve the same function in your managed environment, keeping your distributed repositories up to date. But, they are not complementary features. Use SuperAgent caching when limiting bandwidth usage is your primary consideration. Use Global Updating when quick enterprise updating is your primary consideration. See ePO - On-prem product documentation for more details about Global Updating. SuperAgent caching with repository replication is not recommended.