Use the Repository policy to create the hierarchy. We recommend that you create a three level hierarchy of SuperAgents in your network.
Creating a hierarchy of SuperAgents avoids repetitive download of the content update from ePO - On-prem or distributed repository. For example, in a client network with multiple SuperAgents (SuperAgent 1, SuperAgent 2, SuperAgent 3, and SuperAgent 4) and a distributed repository, configure the hierarchy so that the client systems receive the content updates from their respective SuperAgents (SuperAgent 2, SuperAgent 3, or SuperAgent 4). The SuperAgent 2, 3, and 4 receive and cache updates from SuperAgent 1, and the SuperAgent 1 receives and caches updates from the distributed repository.
In the previous example, SuperAgent 2, SuperAgent 3, and SuperAgent 4 are configured as SuperAgents for the client systems in their respective broadcast domain.
Note
The SuperAgents can't cache content from ePO - On-prem HTTP or FTP repositories.
When creating a hierarchy, make sure that the hierarchy doesn't form a cycle of SuperAgent; for example SuperAgent 1 is configured to pull updates from SuperAgent 2, SuperAgent 2 is configured to pull updates from SuperAgent 3, and SuperAgent 3 in turn is configured to pull updates from SuperAgent 1.
To make sure that the parent SuperAgent is up to date with the latest content update, SuperAgent wake-up calls broadcast must be enabled.
Note
If the SuperAgents don’t serve agents with latest content update, agent falls back to the next repository configured in the policy.