After you have signed up with ManageCat Platform, you can login to the SaaS Controller using the URL address. To manage your servers, you have to download ManageCat Agents from the Downloads page according to your Apache Tomcat versions. Currently only Tomcat 6,7 and 8 are supported. For the Tomcat 6, only Tomcat starting from 6.0.31 and upwards are supported but it may also work in older versions.  We strongly encourage you to update your Tomcat to the latest versions. If you want to use ManageCat for versions below 6.0.31, please let us know how it works.

Installation and Configuration

Installation of the agents are very easy. Agents is distributed as a WAR archive (console.war). Deploy this WAR archive to your Tomcat which enables agent starting to communicate with the ManageCat Controller. Agent configuration parameters are specified as Java System Properties. You can also add system properties to Tomcat file or add as java system parameters with -Dname=value.

Required Configuration Parameters

  • com.managecat.controller.url : URL address of the controller instance. It must be
  • com.managecat.collector.url : URL address of the collector instance. It must be
  • com.managecat.console.agent.servername : User friendly server name of the agent. Must be unique among the same hosts, for example : Tomcat_7.50
  • com.managecat.console.agent.hostname : Host name of the Tomcat server. This host name is used by Controller instance to communicate with the agent.
  • com.managecat.console.agent.groupname : Group name of the Tomcat server. Every Tomcat instance must belong to a group. If this parameter is not provided, monitored server instance will belong to a default-group.
  • com.managecat.console.agent.port : HTTP/S port of the Tomcat server connector. This port is used by Controller instance to communicate with the agent, for example: 8080 etc.
  • com.managecat.console.agent.contextname : Context name of the deployed agent web application. This name is used by Controller instance to communicate with the agent, for example: managecat-console etc. If you copy downloaded managecat-console.war agent archive directly into the Tomcat deploy folder, context name will be managecat-console. If you change the application context name, you must provide updated context name.
  • com.managecat.console.agent.accountkey : SaaS customer account key.

NOTE : Controller communicates with the agent from AGENT HOST NAME and AGENT port you configured above. Therefore, these ports must be opened in your firewall to allows incoming connections from SaaS controller.

After you add these parameters to your Tomcat or other system properties files, you have to restart Tomcat instance. 

NOTE : If you use HTTPS port of the Tomcat, you also have to configure "" property.

If you successfully installed agent, you will see a log like this in your Tomcat logs:

Jan 02, 2015 10:46:17 AM com.managecat.console.common.servlet.MultiTenantConsoleContextListener$ConnectorRunnable run

INFO: Successfully registered the agent AGENT_NAME with the controller. Registration is taken : 1234 ms

Open Controller and Connect to Your Server:

  • Open controller page from
  • Click "Managed Servers" link from the menu,
  • You will see the servers in the Server Groups tree view.

You can click one of the server, then you will see the server properties in the table.

You can connect to the server view with clicking the "Connect" image. The new popup window will be opened. (If your browser not allow to open popups, you must enable to open popups.)

Below is the Server UI opened after you connect to the server.

Congratulations. Your installation of the agent is successful. You can also read User Manuals to get much more infromation.