Child pages
  • Configuring a Second Instance of Flux to run on the Same Server as an Existing Instance
Skip to end of metadata
Go to start of metadata

Installation Overview Checklist

  • Install second instance in separate directory
  • Configure engine configuration for a different port
  • Optional: configure engine configuration for a different database or use the same database as the first instance (as a Flux cluster)
  • Edit the start.ini to start the second instance operations console on a different port
  • Configure user home to be the flux installation directory
    • On Linux use -Duser.home=. in setenv.sh
    • On Windows CMD line use -Duser.home=. in setenv.bat
    • On Windows Service edit engine.conf adding a wrapper.additional.parameter set to -Duser.home=.
  • Copy the .flux directory from user home to the flux installation directory
  • Edit the opsconsole8.properties file in the flux installation .flux directory to point to a different engine port

To install a second instance of Flux on the same server to run with command prompts as an existing instance.

  • Using the zip file installation of Flux, unzip the Flux installation to a separate location from the original Flux installation.
  • Place your existing license key into the new Flux installation directory.
  • You will have to change the Flux engine port from 7520 to 7521 (or some other value) in the engine-config.properties file, and configure separate database connection so as not to conflict with the existing installation.
  • You will also have to change the ops console port in the start.ini file from 7196 and 7199 to say 8196 and 8199.
  • Start the services for the OpsConsole1 and Engine1 from the Windows Services dialog.
  • When bringing up Flux Cockpit (http://servername:8196) for the first time you will need to point this 2nd ops console to the engine running on port 7521 instead of port 7520.

To install a second instance of Flux on the same server to run as a Windows service as an existing instance.

  • Using the zip file installation of Flux, unzip the Flux installation to a separate location from the original Flux installation.
  • Copy the attached files into the \service\windows directory.
  • Then run, from a command prompt at Administrator level, the following commands. These will install the Flux services into Windows as separate names - to coexist with the existing Flux services.

install-engine1.bat
install-opsconsole1.bat

  • To uninstall these services at some point run

uninstall-engine1.bat
uninstall-opsconsole1.bat

  • Place your existing license key into the new Flux installation directory.
  • You will have to change the Flux engine port from 7520 to 7521 (or some other value) in the engine-config.properties file, and configure separate database connection so as not to conflict with the existing installation.
  • You will also have to change the ops console port in the start.ini file from 7196 and 7199 to say 8196 and 8199.
  • Start the services for the OpsConsole1 and Engine1 from the Windows Services dialog.
  • When bringing up the ops console (http://servername:8196) for the first time you will need to point this 2nd ops console to the engine running on port 7521 instead of port 7520.

stop-opsconsole1.batinstall-opsconsole1.batopsconsole1.stop.confstart-opsconsole1.batstop-engine1.batopsconsole1.confinstall-engine1.batuninstall-opsconsole1.batengine1.stop.confengine1.confstart-engine1.bat

  • No labels