FRAM provides a completely isolated instance of FusionReactor which is just for monitoring and instance management, it will continue running even following a JVM crash. FRAM manages and keeps track of all the application servers (and instances) so you can quickly and easily install FusionReactor across your environment.
FusionReactor Administration Manager (FRAM)
If you don't know what is the next step after the installation of FusionReactor on your machine, the following link is going so solve all your questions, After installing FusionReactor, what's next?.
FRAM is a special instance of FusionReactor:
- It provides the Instance Manager which is able to install FusionReactor into other J2EE servers automatically (on the same server);
- It provides an Enterprise Dashboard (enterprise licenses only) which reflects the state of all attached FusionReactor instances – which don't have to be on the same instance. You don't have to use FRAM as your Enterprise Dashboard server – you're free to nominate any other running instance to provide this service (or even multiple instances).
- It provdes FusionAnalytics Communications for any instances whose log engine is set to Centralized Archiving and Logging and whose FusionAnalytics Connector Mode is set to Sent to targets by FRAM.
The FRAM instance runs separately and doesn't require a J2EE container.
Starting and Stopping FRAM
If you've performed a Full installation, FusionReactor has been usually started by the install4j Wizard already. On Windows and Linux platforms FusionReactor Administration Manager has been installed as a Windows Service or Linux daemon which is automatically started at system boot time. On MacOS the user has to manually start FusionReactor Administration Manager after the system has booted.
- Windows: You can use the Windows Services in order to start and stop FusionReactor Administrator. The name of the service is FusionReactor AM Service.
- Linux: You can navigate to the following directory; /opt/fusionreactor/instance/FRAM/ and execute the command "sudo ./framd start" OR "sudo ./framd stop".
- MacOS: uses the service wrapper control script /Applications/FusionReactor/instance/FRAM/framd (assuming you have not changed the default destination directory) to start and stop FusionReactor Administrator Manager.
Accessing FusionReactor Administration Manager
If you've performed a Full installation, you should start by accessing the FusionReactor Administration Manager (FRAM).
There are two ways to do this:
- The simplest method is to use the desktop or Start Menu icons, which were created during installation.
- Alternatively you can call the FusionReactor Administrator (FRAM) directly from a web browser with a URL like below :
In case you have changed the default FRAM configurations, please access the FRAM instance via the browser using your own configurations.
The first page you'll see when you access FRAM will be a login page. Enter the password for the Administrator user, which you entered during installation, and click on the "Login" button. Note that only the Administrator user is available.
Once you are logged in, you'll notice that you have to enter a valid key in order to use FusionReactor. Please check the license guide for detailed information.
FRAM is a completely isolated FusionReactor instance and in most cases is used for monitoring and instance management. In most cases, the Enterprise Dashboard is used as a central dashboard just for monitoring FusionReactor instances, this is a good technique, because FRAM is going to guarantee redundancy and you will be able to monitor all your FusionReactor instances even if a FusionReactor instance is going to crash.
More information about the Enterprise Dashboard and the way of managing servers and groups can be found here, Enterprise Dashboard.
The Instance Manager is used to keep track of the FusionReactor instances monitoring your servers. More information can be found here, Instance Manager.
The logging functionality in FusionReactor is very powerful. Lots of the data shown in the metrics within FusionReactor instances is stored in-memory, so it can be used to generate graphs and reports. If a server were to crash or be shutdown, this in-memory data is lost - however all of this data is captured to one of FusionReactor's extensive log files where you'll be able to determine what went wrong.
On the Logging pages, you are able to set up log rotation to send the logs to a FusionAnalytics Data Collector, where you can have FusionAnalytics import the application log files into an SQL database. The resulting data is processed by the FusionAnalytics Server and visualized by the FusionAnalytics Desktop application. To be able to do this, you must add a FusionAnalytics target.
For a more detailed overview on FusionReactor's logging, please go the Overview of FusionReactor Logs guide.
The Analytics menu provides access to the current status between your instance of FusionReactor and FusionAnalytics. FusionAnalytics is a ColdFusion Application and server analysis tool, which integrates seamlessly with FusionReactor. FusionAnalytics is all about giving you the information and data to help you make better business decisions, improve application performance and the quality of your applications, as well as measure exactly how your applications are performing on a continuous day to day basis.
The FusionAnalytics Connector Status page shows you details such as the size of the archive, the source of the archive (which instance it came from), any exceptions and what target the archive has been set. You can also see all of the archive files (which include the log files) that are going to be transferred to FusionAnalytics. You are able to rotate to have FRAM generate new archives based on the log information gathered since the previous archives was generated.
The archived files are sorted by date, making finding archives easy. You can also delete archives, either individually or by clicking 'Clear all Archives' to empty the whole system.
Please make sure that you are 100% sure before removing all the archives as they will be deleted from the hard disk.
For a more detailed overview, please go to the Connector Status page.