Agents allow the distribution of tasks for performance and multi-platform support. To make better use of available resources and allow for higher build throughput, simultaneous builds can be performed on different agents. Agents can participate in multiple environments. This allows the use of an agent that communicates with a network deployment manager capable of deploying applications to multiple environments.
AnthillPro agents are light-weight Java processes that run on the agent machine. The agent contacts the server whenever the agent process is started. Since the agent communicates with the central server, it need not be on the same network as the central server. However, the agent must be able to open a socket connection to the server. By default, all communication between the central server and the agent is not secure. Communication may be secured using SSL. See Configure Server-Agent SSL.
Configured Agents. Ready to use when online.
Available Agents. Installed but are not yet configured, and cannot be used until configured. See Agent Configuration.
Ignored Agents. Temporarily removed from service. To use an ignored agent, select it, click Edit, check settings, click Set then Done.
To view the Agents overview screen, go to the Agents page, and select the Agent from the menu. Agents can be organized in either ascending or descending order by selecting the Menu headings. For example, select the Name heading to list all agents in either alphabetical or reverse alphabetical order; or select the Host heading to similarly organize all agents by host name.
For organizations with a large number of agents, the agent list page provides navigated pagination. Choose to display 5, 25, 50, or 100 agents per page, and use the navigation tool bar (directly above the Operations menu) to view other pages.
The agent properties (go to Agents > Agent > select an agent > Property type) are also stored on the server, making searching for a property easier. When the agent starts up, it passes all of its properties to the server, which then stores it. If a property is added or changed, or the agent is upgraded, etc., the properties will be automatically updated on the server.
If an agent is not responding, it may be restarted in one of two ways:
Restart All Agents will restart every online agent, even agents currently performing work. Once restart has completed, any work being performed by the agents will resume.
Test Communication ensures that the server and agent are communicating properly. Once selected from the Operations menu, a dialog box will pop up describing the action. Please note that checking the communication may take a minute or longer, depending on agent load and locks.
Restart, under the Operations menu, will restart an individual agent. If, at the time of restart, the agent was currently performing work, the work will resume once restart has completed.
See also About AnthillPro Agents.
Use an agent proxy for any agents where the direct agent-sever
communication is prohibited. Once enabled, the proxy allows the agent to
send logs, reports and other artifacts to the server. To use an agent
proxy for server-agent communication, modify the following propertied in
the agent.property file:
locked/agent.http.proxy.host=
locked/agent.http.proxy.port=
Note that only previously installed agents can be set up to use a proxy. If the agent has not already been installed, see Installing AnthillPro.
Shut down the agent.
With a text editor, open the agent.properties
file located in the \conf\agent directory (for example,
C:\%AGENT_HOME%\conf\agent\agent.properties).
Modify the locked/agent.http.proxy.host=
property. Give the host name for
the agent proxy. For example,
locked/agent.http.proxy.host=www.proxy.yourcompany.com.
Modify the locked/agent.http.proxy.port=
property. Give the port on which
the agent proxy is to communicate. It should look something like
locked/agent.http.proxy.port=8900.
Save changes and restart agent.