Contents

Hardware consideration

The Collaborating Agents machine should have good amount of free space as the packages will get stored on the agent.

Availability

High availability of the agent is the second important criteria. Ideally, those machines which will be up and running during the period of deployment should be selected as Collaborating Agents.

When the Collaborating agent or a Neighbor Aware Agent request Scalability Server for a list of agents on which a particular package is available, Scalability Server checks the package download policy. If the package download policy is set to 1, it means that neighboring agents can download the package from the nearest Collaborating Agents in the same subnet. If they are unable to reach the collaborating agent in the same subnet, then they can also download from other subnet which is nearer.

This method should preferably be used as the package will be delivered to the neighboring agents even though if the Collaboration agent is in the same subnet or different subnet. If the collaborative agent is down or busy serving the other Neighbor Aware agents, then the Neighbor Aware agents can connect to Collaborating gents in the other subnet and download the package.

Collaborating Agent or a Neighbor Aware Agent request Scalability Server for a list of agents on which a particular package is available. Scalability Server checks the package download policy. If the package download policy is set to 0, then the neighboring agents can download the package from any collaborating agent in the same subnet or from the Scalability server, if Scalability Server is in the same subnet of the requesting agent. The Neighboring agents should download the package from the same subnet or the job will be postponed.

If we configure the Package Download Policy download method 0, then administrator has to identify the different subnets in the network, and accordingly ensure that collaborative agents are existing and are available in each and every subnet.