New documentation: This page relates specifically to Omniscope version 2.8 b313 (end Sept 2012) and later. If using Omniscope 2.6 or 2.7, or any build of 2.8 up to 312, see the older instructions.
If installed as a Windows Service, Omniscope Server/Publisher will start when your system starts, without a user account login required. This enables 'always-on' 24/7 services to remain running regardless of user account logins or logout.
On typical systems, this is the default option when installing Omniscope. Omniscope will be installed to the user profile under "C:\Users\[username]\AppData\Local\Visokio Omniscope app", and will not be available to other accounts. The same user account will be activated, and will also be used to run the service under.
Follow the steps above. But in this case, Omniscope is installed to "C:\Program Files (x86)\Visokio Omniscope" or "C:\Program Files\Visokio Omniscope".
Regardless of installation location, activation is typically per-user. You must ensure that the service is configured to run as a specific user account, and that same user account must be activated by logging in and entering the key into Omniscope Desktop.
Follow the same instructions as above, but if you are a user with administrative privileges, you won't need to "run as adminstrator" when you launch the command prompt. You may find that Omniscope installs system-wide rather than per-user. See the relevant installation section above.
Log files can be found in "C:\Documents and Settings\[username]\scheduler".
By default the service uses the same memory limit as the desktop app, which is 1100mb on a 32-bit system or approx. 75% installed memory on a 64-bit PC.
Advanced users can customise this to free up memory for multiple schedulers or to squeeze more RAM out of a server.
To edit the service memory configuration, open wrapper.conf in your Omniscope installation folder typically in "C:\Users\[username]\AppData\Local\Visokio Omniscope app\service" or "c:\ProgramFiles\Visokio Omnisope\service" and edit the line "wrapper.java.maxmemory", specifying a number in MB. For example:
wrapper.java.maxmemory=1100 (32-bit limit)
or
wrapper.java.maxmemory=6000 (as recommended on an 8gb server running 64-bit)
The Visokio service will by default run in the 32/64-bit mode as chosen when first installed. By default this is 64-bit on a 64-bit PC and 32-bit on a 32-bit PC. If you are upgrading an older version of Omniscope you will need to replace "wrapper.conf" as detailed above in the installation section, otherwise an old configuration will be used.
To switch between 32-bit and 64-bit, reinstall following the steps above and choosing the right option in the installer, being sure to replace "wrapper.conf" as detailed.
Make sure you're using 2.8 b313 or later and have followed the instructions above carefully. See also Scheduler troubleshooting and the flowchart PDF in this forum post.
If you try to install Visokio as a service on Vista, you will get a"OpenSCManager Failed - Access is Denied. (0x5)" error. On Vista, you need to log on as an administrator when you install the service, as detailed in the installation instructions above.
If your service will not start after it has been installed, please check that you have a clean installation of Omniscope with an updated "wrapper.conf" file as detailed above.
Also make sure the service is configured to run under a user account which has access to the Omniscope installation folder. Make sure the same account has been activated with your license key, and not another user account.
Repeat the installation steps carefully. Get in touch on the forums if you still cannot get the service to start.
If you get out of memory errors (in the scheduler or service log files, in the program folder), please check that you have a clean installation of Omniscope with an updated "wrapper.conf" file as detailed above.
See above Memory configuration section on how to increase memory and switch to 64-bit Java (if you are using a 64-bit machine).
You need to restart the service for the changes to take effect.
Scheduler as a service is unable to access files on mapped network drive, because these drive mappings are only available to a desktop user session on Windows.
The way to get around this issue is by using full UNC paths (\\machine name\path) in your DataManager models and source/output paths.
See System-wide database driver location settings.
This usually means the "wrapper.conf" is old and applies to an older version of Omniscope. Please check that you have a clean installation of Omniscope with an updated "wrapper.conf" file as detailed above.
Old documentation: This page relates specifically to Omniscope versions prior to 2.8 b313 (end Sept 2012). This includes all builds of 2.6 and 2.7, and any build of 2.8 up to 312. You should be using a newer version, please see the latest instructions.
Beginning with version 2.2, it is possible to run Enterprise Edition as a Windows Service. This enables always-on services to remain running regardless of user account logins or logout.
When you have installed the application and activated it with a valid Enterprise license, browse to the applications program folder (generally c:\Program Files\Visokio Omniscope) and you will find a folder called 'Service'
Open the folder and double-click on 'Install Visokio Service.bat'. This will install the application as a service and start it. When you install the application as a service, it will run it as the "Local System" user. For security reasons the service cannot run logged on as the "Local System" user. You will need to change the service to make it log on as a user. To do this open the Services Control Manager from Control Panel, click Administrative Tools, and then click Services. Select Visokio Enterprise, right click, then go to Properties, and choose the "Log on" tab, select "This account" and enter your account name and password, then press "OK". Now start the service.
You can now manage the service as you would any other by going to "Administrative Tools" in the Control Panel and choosing 'Services'.
Configuring scheduled tasks within the Scheduler is done in the same way as before (using the 'Visokio Scheduler' item in the Start menu) the only difference being that you cannot stop the application from here and the application continues to run after the interface is closed.
If you wish to uninstall the service you can go to the same folder and double-click on 'Uninstall Visokio Service.bat'.
By default the service has a fixed limit of 1100mb. For medium and larger data files this will need to be adjusted. We recommend allowing up to 75% of installed RAM, but if running the 32-bit version of Omniscope, limiting further to 1100mb.
To edit the service memory configuration, open wrapper.conf in your Omniscope installation folder typically in "C:\Users\[username]\AppData\Local\Visokio Omniscope app\service" or "c:\ProgramFiles\Visokio Omnisope\service" and edit the line "wrapper.java.maxmemory", specifying a number in MB. For example:
wrapper.java.maxmemory=1100 (32-bit limit)
or
wrapper.java.maxmemory=6000 (as recommended on an 8gb server running 64-bit)
The Visokio service will by default run with the version that has been installed using the installer. For example, if you install Omniscope in 64-bit (default on 64-bit machines), then the service will be configured to run in 64-bit mode. You can verify this, if the wrapper.java.command in the wrapper.conf ends in ...\x64\bin\java (see below). We recommend that if you are using 64-bit machine that you always use 64-bit Java. To switch to 64-bit Java simply change the path in the wrapper.java.command to the 64-bit version (see below for full path).
Note: You will need to restart the service in order for the changes to take effect.32-bit: wrapper.java.command=C:\Program Files (x86)\Visokio Omniscope\x86\bin\java
64-bit: wrapper.java.command=C:\Program Files (x86)\Visokio Omniscope\x64\bin\java
or
32-bit: wrapper.java.command=C:\Users\[username]\AppData\Local\Visokio Omniscope app\x86\bin\java
64-bit: wrapper.java.command=C:\Users\[username]\AppData\Local\Visokio Omniscope app\x64\bin\java
Troubleshooting
If you try to install Visokio as a service on Vista, you will get a"OpenSCManager Failed - Access is Denied. (0x5)" error. On Vista, youneed to log on as an administrator. From the Start menu browse to"Command Prompt", right click and "Run as administrator". Type cd andthe location of the Visokio service folder (generally c:\ProgramFiles\Visokio Omnisope\service) and press Enter then type 'InstallVisokio Service.bat' and press Enter again. This should install your service and start it.
If your service will not start after it has been installed, please check that you have Java in your system path. This can be done by going to the Control Panel, opening "System", choosing "Advanced" ("Advanced Settings" in Vista) and clicking the "Environment Variables..." button. A new window will pop up. Under "System variables" find "Path", click edit and, if the path to the "bin" folder in your java installation is not there, type it at the end (including the "bin").
Alternatively, edit the wrapper.conf file in the service folder of Omniscope's program folder. To use a system VM:
wrapper.java.command=C:\Program Files\Java\jre1.6.0_04\bin\java
Or to configure the service to use the bundled Java VM that comes with Omniscope:
wrapper.java.command=C:\Program Files\Visokio Omniscope\pvm6u4\bin\java
If you get out of memory errors (in the scheduler or service log files, in the program folder), see above Memory configuration section on how to increase memory and switch to 64-bit Java (if you are using a 64-bit machine).
You need to restart the service for the changes to take effect.
Scheduler as a service is unable to access files on mapped network drive. The way to get around this issue is by using full UNC paths (\\machine name\path).
Before installing the application you need to delete your old wrapper.conf file generally at (c:\Program Files\Visokio Omnisope\Service). As there has been configuration changes to wrapper.conf file, and a new installation does not overwrite old wrapper.conf file.