This procedure applies to FusionReactor 4.x and above.
The normal method for installing FusionReactor into a J2EE container is to use the FusionReactor Administration Manager's Instance Manager. This page, located in Instances -> Instance Manager, allows you to easily administer all instances present on a single machine.
If FusionReactor doesn't detect your instance, you may have to install it manually. There are some caveats to this process:
This procedure has been developed for Unix-type operating systems, including Linux. FusionReactor may be installed manually on windows, by changing the corresponding paths. A Windows-specific template configuration is available, and this is noted later in this procedure.
The following list outlines the prerequisites which must be fulfilled prior to beginning this procedure.
This will give a clean environment in which FR4 can be installed.
The FusionReactor Administration Manager, or FRAM, is a cut-down version of FusionReactor which runs inside its own server, and provides administrative and monitoring functionality for other FusionReactor instances.
Although, as a manual install, you won't be able to take advantage of these functions, FRAM does contain an instance template which you can use to create a manually-installed instance.
After the wizard completes, and assuming default answers, the FusionReactor Administration Manager will be installed into /opt/fusionreactor (c:FusionReactor on Windows).
It is not strictly necessary to start FRAM, but if you wish to do so, it can be started using the shell script (/opt/fusionreactor/tomcat/bin/framd start), or by starting the FusionReactor AM service on Windows. If you picked the default port, the service will be available in your browser at http://localhost:8087/.
FusionReactor Administration Manager includes a template instance which you can customize. The four main steps are:
For the purposes of illustration, we will be installing a manual instance into Adobe's ColdFusion server, located in /opt/coldfusion9.
Within the /opt/fusionreactor/instance/cf9/conf folder, you will see two subfolders, unix and windows.
You should now have a reactor.conf and a filter-def.xml file in the conf folder.
The internal web server is configured in the file fram.conf.
|webserver.active||Whether the internal webserver is made available. If not, FusionReactor will be available over your main webserver under http://localhost/fusionreactor.|
|webserver.address||The IP address to which the internal webserver should bind.|
|webserver.all||Whether the webserver should bind to all addresses.|
|webserver.port||The port on which the webserver listens.|
Perhaps most important is the last key: webserver.port. You must ensure you use a port here which is not in use by any other application.
The file filter-def.xml contains an XML snippet which must be added to your J2EE container's web.xml file. You should ascertain the location of this file by referring to the container's documentation.
You should now have inserted the FusionReactor filter and filter-mapping block just prior to the first filter (or servlet) definition.
Within the folder /opt/fusionreactor/etc/lib, you'll find a copy of the fusionreactor.jar file. This must be copied to somewhere visible to your J2EE server's webapp instance.
Some functions of FusionReactor, in particular the CPU usage monitor, reside with a custom native library, also located with the /opt/fusionreactor/etc/lib folder.
There are several options to achieve the last point:
Finally, start your J2EE container, and watch its standard-out and standard-error logs. If anything is misconfigured, you should be able to start debugging the problem from the output presented there.
|Last Updated:||09/Aug/11 10:06 AM|
Comments are closed.