Agent configuration tables

The Agent Startup and Agent Registry tables contain the details that help you to configure the process agents in IBM® TRIRIGA®.

The configuration that determines the starting of agents is stored in the AGENT_STARTUP table of the IBM TRIRIGA database.

When a request to start an agent is made, an entry is added to the AGENT_REGISTRY table. When an agent stops, its status in the registry is updated. The Agent Registry table is available to all servers in the installation and is the source of the current activity information that is displayed in the Agent Manager object.

When the status of an agent changes, an INFO entry is written to the server log and contains information about the state transition, for example:

INFO  [com.tririga.platform.agent.AgentManager](http-0.0.0.0-8001-3) Start requested
 for CleanupAgent on server337.
INFO  [com.tririga.platform.agent.BaseAgentThread](CleanupAgent) CleanupAgent on ser
ver337 is now running.
INFO  [com.tririga.platform.agent.AgentManager](http-0.0.0.0-8001-3) Stop requested 
for CleanupAgent on server337.
INFO  [com.tririga.platform.agent.BaseAgentThread](AgentHeartbeatThread) CleanupAgen
t on server337 is now stopped.

The AGENTS_NOT_ALLOWED property in the TRIRIGAWEB.properties file for a server identifies agents that cannot be started on that server. The Agent Manager does not allow a user to start an agent that is listed in the AGENTS_NOT_ALLOWED property for that server where the properties file resides. If a user tries to start an agent that is in the AGENTS_NOT_ALLOWED property, an INFO message is written to the server log and the agent is not started. If an entry in the AGENTS_NOT_ALLOWED property does not correspond to an existing agent, a warning message is written to the server log.

The Agent Startup table includes the agent type, the host name, and the configuration. The Agent Startup table is the source of the TRIRIGAWEB.properties information that is displayed in the Agent Manager.

If a single-instance agent is started while another instance of the same agent is running, the request fails, and a warning is written to the log file.