Page tree
Skip to end of metadata
Go to start of metadata

Include Java agent

  1. Add fusionreactor.jar to the following directory of your .WAR file
    1.  WEB-INF/lib 
  2. Package and deploy your .WAR file to AWS

AWS Console Configuration

You must provide a password for FusionReactor to start. This is because FusionReactor's external web access is automatically off until a password has been set. Without providing a password you will not able able to access FusionReactor.
  1. On the Default Environment page, open: Environment Details > Overview

  2. Click Edit Configuration
    On the Container tab, enter the following into the JVM Command Line Options field:

    Tomcat 6:

    -Dfrinstancepath=/usr/share/tomcat6/fusionreactor -Dfrstartupdelay=3000

    Tomcat 7:

    -Dfrinstancepath=/usr/share/tomcat7/fusionreactor -Dfrstartupdelay=3000

    You must configure the path to the javaagent and the location of the fusionreactor folder that you have created in your deployment


  3. Click Apply Changes
  4. Log into FusionReactor via:
    • http://<URL-TO-ELASTIC-BEANSTALK-APPLICATION>/fusionreactor/findex.htm

In AWS environments you normally cannot access FusionReactor via it's internal web server (e.g. 8088) because ports are secured in the environment. If your environment has support for opening a port you can add the following option to start the internal web server.


Note you can deactivate the license used by FusionReactor on shutdown (for dynamic instances) by including the following in the JVM arguments

FusionReactor 's configuration must be stored in a folder that is not overwritten when your application is deployed. We utilize the -Dfrinstancepath system property to tell FusionReactor where to place the configuration files. If you do not provide a location for the instance that is not overwritten on a deploy, FusionReactor will lose it's configuration each time the application is deployed.
  • No labels