FusionReactor can be configured to be used in a dynamic (containerized) environment. We provide a series of Java Arguments to automatically configure FusionReactor.
Copying an existing configuration
If you have an existing instance and would like to keep the configuration, you can place a copy of the reactor.conf file from this instance and place it in the conf directory of your new FusionReactor instance.
When moving the reactor.conf file you MUST remove the lines beginning with FRUID and GRUID from the file, as this is a unique identifier for the instance so cannot be cloned.
Java Arguments to configure FusionReactor
You can specify a number of Java arguments to configure your license key, Enterprise Dashboard or Cloud Groups. Here is a full list of available arguments:
Please note that these options should be added in the JVM configuration file of the application server you are using and these should be prefixed with -D e.g -Dfrshutdownaction=stop.
|none - disabled||any||5.0.0||This sets the initial administrator password for FusionReactor on this server (this can be changed in FusionReactor once it is running)|
|frregisterwith||none - disabled||URL to FR instance|
If present, FusionReactor will attempt to register with the remote instance. The supplied URL should be in the following format;and the default URL for FusionReactor is
|frshutdownaction||none - disabled||remove, stop|
If this and the "frregisterwith" property is present, FusionReactor will attempt to un-register itself from the specified target using either the remove or stop command.
We recommend using "remove" in a very dynamic environment, otherwise the Dashboard would quickly fill up with offline servers.
|frregisterhostname||none - retrieved from environment|
any host name/ip address
|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.|
|frregistergroup||none - disabled||comma-separated list of Strings|
This value is used in conjunction with the previous 3 REST commands. This property will allow you to also specify ED groups for your server on start-up/shutdown.
If frshutdownaction is 'remove', groups will remain present on ED. In order to prevent any existing servers from losing their groups.
Enterprise Dashboard Examples with Tomcat
|If present, sets the license key of the instance.|
Licensing Properties Examples with Tomcat
|fr.cloud.group||(none)||comma separated string (group1,group2...)||Sends an array of group names within the connect message. The server will then be automatically added to the defined groups.|
Cloud Properties Example with Tomcat
More information about the System Properties can be found in the following link, System Configuration Keys.