The Omniscope Evo server app is not designed to run multiple instances concurrently on the same server or VM. However, Omniscope Classic Server does support running multiple instances; this is highly unusual and requires custom configuration, and is not fully supported. But if you're willing to experiment, here's how. 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 Omniscope Classic Server running two instances.

What you can't have is 2 instances of Omniscope Evo.

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 now need a script (e.g. a BAT file on Windows) which launches Omniscope Classic Server. (Rather than using the Windows desktop shortcut to launch).

To get this you can launch "Visokio Omniscope Classic Server (debug)" shortcut; you will find a BAT file appear in e.g. "C:\Users\YourName\AppData\Local\Visokio Omniscope app" containing 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="xxx:80" -cp "C:\Users\YourName\AppData\Local\Visokio Omniscope app\Main.jar;C:\Users\YourName\AppData\Local\Visokio Omniscope app\lib\*" com.visokio.ent.EntLaunch  

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 cannot currently run multiple instances in parallel).

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.