This section is going to provide you with an example of using a Manual Installation for installing your application servers, while FRAM (FusionReactor Administration Manager) is going to be installed in order to monitor ALL the FusionReactor instances.
For this example, we are going to use the following;
- Windows Server 2012
- FusionReactor (6.2.x)
- Apache Tomcat 8
- Java 1.8
Please note that the Enterprise Dashboard in only available with an Enterprise/Ultimate license.
We will assume that you have already downloaded and installed FusionReactor and the Apache Tomcat 8 server on your machine.
If you don't want to use an Apache Tomcat 8 server, then you can install the application server of your preference and follow the instructions below.
- You can download FusionReactor from the following link, Download FusionReactor.
- You can download the Apache Tomcat 8 server from the official website.
Once the Apache Tomcat 8 application server has been successfully installed in your machine, the next step is to manually install FusionReactor. More information about the Manual Installation can be found in the following link, Manual Installation.
When the manual installation process has been completed, then access your FusionReactor instance via your browser. For this example, I have manually install a FusionReactor instance on port 8088.
Provide a new password for the Administrator user and then activate the FusionReactor instance by providing a valid license key. More information about the license activation can be found here, Apply a license key.
Once, FRAM is installed by the use of the automated installer, the next step is to access FRAM via your browser.
Usually FRAM can be accessed by typing the following URL: localhost:8087. In case you have configured FRAM to listen and operate in another port, then you should use the configured port instead of the default port.
When you access FRAM from the first time, you need to login with a username and a password that was configured during the installation process and provide a valid license key in order to activate FRAM. More information can be found here, Install FusionReactor via the automated installer.
The Enterprise Dashboard lets you track the state of installations on one or more servers. When you install an Enterprise or an Ultimate version of FusionReactor on a server it can be queried for its current state. The Enterprise Dashboard lets you instantly monitor the health of ALL of your server instances/machines from a single window. You immediately see the state of memory, CPU, DB load and average request time, in an easy to read graphical dashboard display. In order to start monitor your FusionReactor instances, you need to access the Manage Servers or the Manage Groups area and configure your application servers. If you want to learn more about the Enterprise Dashboard follow the link, Enterprise Dashboard.
When you login to the FRAM, navigate to the Manage Servers area. This can be found under the globe icon > Manage Servers.
For this example, we are going to add the Apache Tomcat 8 server with the following information.
- Name = Apache_Tomcat_8
- URL =
After the configuration of the details, press the Add Server button,
Now, you should be able to see the FusionReactor instance under the Current Servers section. See screenshot below.
If the FusionReactor instance has a green background color, that means that your FusionReactor instance has been successfully configured and now you will be able to start monitoring. More information about the Manager Servers can be found here, Manage Serves.
In the Manage Servers area you can also add a FusionReactor instances that is accessible externally by adding the external IP address in the URL field.
Add an External Server in the Enterprise Dashboard
This section, will provide a simple example of adding an external FusionReactor instance in the Enterprise Dashboard. For this example, an Amazon EC2 instance was used.
Navigate to the Manage Servers tab and add all the details of the external server as described in the section above. See screenshot below.
From the screenshot above, we can see that the Status code of the FusionReactor instance with name "tomcat8_External_Server" is set to "OK". That means, that you should be able to access the FusionReactor instance externally.
FRAM also provides you with the option of Manage Groups or add FusionReactor instances into groups. More information about the configuration can be found here, Manage Groups.
Enterprise Dashboard Overview
In order to access the Enterprise Dashboard, navigate to the global icon > Dashboard.
There, you should be able to locate your FusionReactor instance that was previously configure in the Manage Servers area. For this example, I am going to locate the Apache_Tomcat_8 application server.
If you click in the actual instance, a new area is going to appear with a number of useful information about the performance of the instance. See screenshot below.
In case you have configured groups, the Enterprise Dashboard is going to include those groups as well.
FusionReactor provides you with the ability of adding a FusionReactor instance to the Enterprise Dashboard by the use the following System Properties: -Dfrregisterwith, -Dfrregisterhostname, -Dfrshutdownaction.
- -Dfrregisterwith: If present, FusionReactor will attempt to register with the remote Instance.
- -Dfrshutdownaction: If this System Property and the -Dfrregisterwith is present, FusionReactor will attempt to un-register itself with the registerwith target using either the remove or stop command.
- -Dfrregisterhostname: This System Property is used when registering with remote servers. When using the register with key, the server will be registered using this as the host name on the remote server.
More information about the System Properties can be found here, System Properties.
In the example below, we are going to add an Apache Tomcat 8 server to the current servers in the Enterprise Dashboard of a FRAM running on port 8087. For this example we have assumed that the Apache Tomcat server is using the port 8088. Please note that you need to use the hostname or ip-addresses and not 127.0.0.1 because otherwise the Enterprise Dashboard will not know how to call the instance if it's not running locally.
The System Properties are going to have the following form: