Running multiple Omniscope server processes concurrently

You can run multiple Omniscope Evo and Omniscope Classic Server on the same machine, however this is not desirable, and should only be used in specific cases. This is highly unusual and requires custom configuration, and does not support all functionality. 

This replaces older advice from the forums archive.

For example you might want Omniscope Evo and Omniscope Classic Server running concurrently. Or, you might want more than one Omniscope Evo instance running. 

Let's assume you have Omniscope Classic Server (or even, Evo) already running, using "C:\Users\YourName\omniscope-server\" as its main folder.

Inside here you will have config.xml, which is the saved configuration of the server. Normally you should not edit this directly.

Copy this folder to another location, which will be the 2nd instance's configuration, e.g. "C:\Users\YourName\omniscope-server2\".

Edit the new config.xml file and change 'instancePort' which is typically 24679 to the next free number (24680). Save. You may also want to change the watch folder location (if required) 

You now need a script (e.g. a BAT file on Windows) which launches Omniscope Classic Server / Evo. (Rather than using the Windows desktop shortcut to launch).

To get this you can launch go to the installation directory and run the OmniscopeEnterprise_debug.exe, or OmniscopeEvo_debug.exe exectuable.

If you wish to run Omniscope Classic Publisher run: OmniscopeEnterprise_debug.exe

If you wish to run Omniscope Evo run: OmniscopeEvo_debug.exe

This will create appropriate .bat file in your user home directory "Visokio_OmniscopeEnterprise_debug.bat" or "Visokio_OmniscopeEvo_debug.bat" depending on the executable you used.

Edit the batch file in notepad, and copy the JVM launch command contents it should be something like

"C:\Users\YourName\AppData\Local\Visokio Omniscope app\x64\bin\java.exe" -Xms64M -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=50 -XX:+UseG1GC -Xverify:none -Xmx8102M -Dvisokio.localappdata="C:\Users\YourName\AppData\Local" -Dvisokio.winproxyenable="0" -Dvisokio.winproxyserver="" -cp "C:\Users\YourName\AppData\Local\Visokio Omniscope app\Main.jar;C:\Users\YourName\AppData\Local\Visokio Omniscope app\lib\*" com.visokio.ent.EntLaunchX 

NOTE: If you are running OmniscopeEnterprise_debug.exe you will see com.visokio.ent.EntLaunch and not com.visokio.ent.EntLaunchX 

Copy or move this file somewhere convenient. Edit it to include the following; insert it before "-cp":

-DschedulerConfigLocation="C:\Users\YourName\omniscope-server2\config.xml" 

-DdisableDataEngine=true

(This tells Omniscope to run in an isolated folder, the one containing the XML file, and to disable the data engine dependency which can cause issues if enabled). We recommend you disable it, however, you can  omit -DdisableDataEngine=true if you wish to keep data engine enabled and have multiple instances share the default data engine. The admin app, allows you to change the default data engine if necessary (contact Visokio Support for more details). 

Warning (only for running multiple Omniscope Evo instances) and you disable data engine:

Any Workflow blocks connected to Report will not be executable. Omniscope will also not be able to serve any Reports, warning will be shown in the visualisations. You would only typically run multiple Omniscope Evo instances in parallel if you want the same machine to schedule different workflow job queues. If unsure, contact Visokio Suppport.

Remember to configure your batch file executes from the working directory set to the installation folder of Omniscope before you execute the C:\Users\YourName\AppData\Local\Visokio Omniscope app\x64\bin\java.exe"....

For example, your final batch script should look something like:

       cd "C:\Users\YourName\AppData\Local\Visokio Omniscope app" 

"C:\Users\YourName\AppData\Local\Visokio Omniscope app\x64\bin\java.exe" -Xms64M -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=50 -XX:+UseG1GC -Xverify:none -Xmx8102M -Dvisokio.localappdata="C:\Users\YourName\AppData\Local" -Dvisokio.winproxyenable="0" -Dvisokio.winproxyserver="" -DschedulerConfigLocation="C:\Users\YourName\omniscope-server2\config.xml" -DdisableDataEngine=true

-cp "C:\Users\YourName\AppData\Local\Visokio Omniscope app\Main.jar;C:\Users\YourName\AppData\Local\Visokio Omniscope app\lib\*" com.visokio.ent.EntLaunchX 

As mentioned above, you already have the primary instance of Omniscope Classic Server (or Evo) running; should you stop it, you can restart it using the normal launch shortcut.

To launch the secondary instance, run the BAT file you have created. Check in the separate "omniscope-server2" folder for logs if needed.

You can repeat this process to create a 3rd instance, if needed.