Download Instructions

To download ManageCat Controller and Tomcat Agents, open a web browser and go to ManageCat download page,Download ManageCat.. You may be signup to download the specific components.


Controller is the main component of the ManageCat platform. All connected agents report metrics to the controller and controller persists these metrics to the internal database. Controller instance also hosts web application which is used by administrators to manage and monitor Tomcat instances. According to your system environment multiple installation packages exist.

  • ManageCat Zip Package : It can be used with any type of operating system. Simply unzip the package and it is done.

  • ManageCat Wizard Package : For the Windows based operating system, you can install Controller with basic Wizard based installation package. Simply follow the instruction.

  • ManageCat Agents : There are 3 different agents to support your Tomcat version. Currently only Tomcat with version 6,7,8 are supported by ManageCat.  


Installation of the Controller

If you use SaaS based version of the ManageCat, there is no need to install anything. For the onpremise version, download the applicable package regarding your operating system and starts your installation. For the Windows based operating systems, there is an installation package. Click controller.exe file to start your installation and follows the wizard pages for further configurations.

For the Linux based operating systems, unzip the installation package and update configuration files according to your controller profile.

Installation of the Agents

Agent is a simple WAR (Web Application Archive) file. Simply deploy this WAR file to your monitored Tomcat instance. You must configure your agents before they start to report data to the controller instance. There are some required agent configuration parameters (Java System Properties) which must be configured before the Tomcat is started. These parameter are:

  • com.managecat.controller.url : URL address of the controller instance. Default is http://localhost:8080/managecat-controller/

  • com.managecat.collector.url : URL address of the collector instance. Default is http://localhost:8080/managecat-collector/

  • 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 : If you are using SaaS based controller, you must also configure account key.

After deploying the agent web application into your monitored server, Controller instance will start to communicate with the agent using http://agenthostname:agentport/agentcontextname.

 

Note

If you use the SaaS based controller, controller url must be https://saas.managecat.com/ and collector url must be https://collector.managecat.com/.


Access the ManageCat UI from a Browser

After installing the ManageCat Controller and Agents, open your favorite web browser and connect to the ManageCat Controller UI from http://controller_host_name:controller_port_number/controller_context_name When you first login into the controller, you can use default credentials as username 'admin' and password 'admin'.


Only the administrator role is granted to see the Administrator related pages.