Hi Michael,

Thanks for the instructions. I believe I did everything as you described it, yet when executing the run_scheduler.bat nothing happens. How do I set s1 or s2 as a parameter?

Thanks!

Alexander

You can create Shortcuts:
Right-click on your desktop and in the menu go to New->Shortcut.

In the dialogue enter (change YOUR_ACCOUNT_NAME for your computer account name)

"C:\Users\YOUR_ACCOUNT_NAME\AppData\Local\Visokio Omniscope app\run_scheduler.bat" s1

click next and name this label, e.g. "Service 1"

Make sure that Shortcut on your desktop works, i.e. starts your first scheduler instance.

Repeat the same for the second parameter s2:


"C:\Users\YOUR_ACCOUNT_NAME\AppData\Local\Visokio Omniscope app\run_scheduler.bat" s2

Shortcut name, e.g. "Service 2"

Hi Michael,

Feeling rather stupid as your explenation is really clear. I made a shortcut on the desktop, but it is not working. I get a really fast dissappearing cmd screen. The same happens if I just click on the run_scheduler.bat. Is your explenation for 2.7?

Hope you can help me once more... Thanks!

Regards,
Alexander

Run the bat file from a command prompt, so you can see the output. Or add a "pause" command at the end of the bat file. What do you see?

Hi Steve,

I've added the pause command, attached the output. "Cannot find the path"

You CONF_DIR is empty, you missed out the parameter s1

That is because I executed the Bat file, not the short cut. The output from the shortcut is:

As an alternative for Shortcut you can run from Console:

go to Start , type "cmd.exe "
type in following commands:

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

press enter

run_scheduler.bat s1

press enter

Can you also make sure that you have following directory:

C:\Users\Administrator\AppData\Local\Visokio Omniscope app\service\s1

The same thing, cannot find the path. Did I do something wrong in the config files?

Could you check that you have this directory:
C:\Users\Administrator\AppData\Local\Visokio Omniscope app\service\s1

Yes, I do have that directory.

I sent an email.

Do you have x64 version or x86 ()?

If you have x86 version edit run_scheduler.bat file. Change x64 for x86:


set CONF_DIR=%1
"C:\Users\Administrator\AppData\Local\Visokio Omniscope app\x86\bin\java.exe"
....................
....................
....................


Make sure that
if you have x64 then following file should exist:
C:\Users\Administrator\AppData\Local\Visokio Omniscope app\x64\bin\java.exe

or if you have x86 then following file should exist:
C:\Users\Administrator\AppData\Local\Visokio Omniscope app\x86\bin\java.exe

Hi Michael,

I found the java.exe file, it is in a different directory...C:\Program Files (x86)\Visokio Omniscope\x86\bin\java.exe

Could this be causing the error?

Regards

Alexander

The issue was with the file-path to Omniscope installation. The initial document was for User installation where it is:

"C:\Users\YOUR_ACCOUNT_NAME\AppData\Local\Visokio Omniscope app\"

Alexander has system wide installation and the path to Omniscope installation should be changed to:

"C:\Program Files (x86)\Visokio Omniscope\"

From Omniscope 2.8, to customise the Omniscope Server log filename (both name and extension), uncomment, modify the value and add the following line in the installconfig.properties file:
ADDITIONAL_JVM_ARGS=-DserverLogFilename="FILENAME.ext"

This is highly recommended when running different instances of the Omniscope Server (ex Scheduler) to allow logging on different files.

Can I just ask whether there are any memory configuration settings that need to be changed when running 2 schedulers - we're still on 2.7 (will be upgrading soon).
Can you configure the amount of memory each scheduler is allocated? Thanks, Ed

Both schedulers will use the same default memory setting as per installconfig.properties file located into the Omniscope install application folder.
See
http://www.visokio.com/kb/installconfig

You can configure them to individually use different memory settings by changing your scheduler batch file to provide a different command line for each of your schedulers.

run_scheduler.bat

In the example below it is set to 6Gb " -Xmx6183M" for scheduler 1 "s1" and 3Gb for any other scheduler "-Xmx3000M"
e.g
if "%CONF_DIR%" == "s1" (
"OMNISCOPE_INSTALL_DIR\x64\bin\java.exe" -Dsun.java2d.d3d=false -DschedulerConfigLocation="OMNISCOPE_INSTALL_DIR\service\%CONF_DIR%\config.xml" -Xms64M -XX:MaxPermSize=128M -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=30 -XX:NewRatio=8 -XX:+UseSerialGC -Xmx6183M -Dvisokio.localappdata="C:\Users\YOUR_ACCOUNT_NAME\AppData\Local" -Dvisokio.winproxyenable="0" -Dvisokio.winproxyserver="" -cp "OMNISCOPE_INSTALL_DIR\Main.jar;OMNISCOPE_INSTALL_DIR\lib\mail.jar;OMNISCOPE_INSTALL_DIR\lib\activation.jar;OMNISCOPE_INSTALL_DIR\plugins\bccrypto.jar" com.visokio.ent.EntLaunch -scheduler
) else (
"OMNISCOPE_INSTALL_DIR\x64\bin\java.exe" -Dsun.java2d.d3d=false -DschedulerConfigLocation="OMNISCOPE_INSTALL_DIR\service\%CONF_DIR%\config.xml" -Xms64M -XX:MaxPermSize=128M -XX:MinHeapFreeRatio=20 -XX:MaxHeapFreeRatio=30 -XX:NewRatio=8 -XX:+UseSerialGC -Xmx3000M -Dvisokio.localappdata="C:\Users\YOUR_ACCOUNT_NAME\AppData\Local" -Dvisokio.winproxyenable="0" -Dvisokio.winproxyserver="" -cp "OMNISCOPE_INSTALL_DIR\Main.jar;OMNISCOPE_INSTALL_DIR\lib\mail.jar;OMNISCOPE_INSTALL_DIR\lib\activation.jar;OMNISCOPE_INSTALL_DIR\plugins\bccrypto.jar" com.visokio.ent.EntLaunch -scheduler
)

Thanks Donald that's really helpful. Can you just tell me if Omniscope grabs that chunk of memory or is this just a maximum threshold that it can use i.e. it wouldn't actually hog 6GB unless it needed it?

It is a maximum threshold. It won't hog the full 6GB unless it is needed.

Thanks Donald, that's what it looked like when I implemented your suggestion but thought I'd check just in case the allocation hadn't worked.

Hi, I got this working on our dev server which has a local install but when I tried on our live, which is a system wide install I am getting the following error message when trying to exec the run_sheduler.bat file:
"APPLICATION ERROR:
java.lang.UnsupportedOperationException: EntLaunch not enabled
at com.visokio.ent.EntLaunch.a(EntLaunch.java:48)
at com.visokio.ent.EntLaunch.main(EntLaunch.java:28)"
I also get a popup message which I've attached.
I've attached all the relevant files in case I've typed something wrong somewhere!

Currently on our live server we are running Omniscope (single scheduler) as a windows service - can you run multiple schedulers as services? We are currently on 2.7 but I will be updating to 2.8 so happy for 2.8 instructions if it is possible.

You need to run the scheduler as the user who did the license activation. When you activate the license you also need to use the system wide version of Omniscope when using the GUI to activate.

Can you log onto the machine as the user you intend to run the service as and run Omniscope from the system wide installation location.
C:\Program Files (x86)\Visokio Omniscope\Omniscope.exe
or
C:\Program Files\Visokio Omniscope\Omniscope.exe

Select Help->"Licensing and Activation" menu item, this will display either an "Activate Omniscope" dialog box if the license has not been activated for this user or the current license edition, license key and expiry date if it has.





License is NOT activated


License IS activated


The user that is set to run the scheduler service is defined in the Windows Services administration tool, select "Visokio Enterprise" properties and select the "Log On" tab, check the "This account" box and enter the username and password.

Yes you can run multiple instances.
See the post "Scheduler: Running multiple instances concurrently"
http://forums.visokio.com/discussion/1469/scheduler-running-multiple-instances-concurrently/p1

Donald, I've seen that thread as it's the one we're commenting on ;-)
My question, which perhaps wasn't well worded, is really how do the schedulers relate to Omniscope running as a service? We currently have Omniscope running as a service using only one scheduler and we'd like to start running multiple schedulers - other than following the instructions in this thread, is there anything we have to do with regards to the windows service. The bottom line is - if we have one instance of Omniscope running as a service and I implement the instructions above for running 2 schedulers, will both schedulers get started when we reboot the machine?

Donald, with regards to the scheduler error - Omniscope was installed and activated as the Administrator account

the service is running as Administrator

and I am currently connected via RDC to the server as that account, therefore trying to run the batch file as Administrator.

I have just reinstalled our dev environment as Omniscope was a local install and not running as a service. Now it is a system wide install and running as a service I am getting the same error as the live server. I'm sure that it must be some sort of permissions problem but I can't figure it out - if anyone can help quickly it would be much appreciated

You can only run one instance of the server using the Windows services wrapper. If you have the service set to automatically start then on reboot it will start the default first instance of the server with the default configuration and first default scheduler.

The method described earlier in the thread requires the licensed user logged on and manually starting each of the scheduler instances. In that case it is starting multiple independent Omniscope instances.

Thanks for the screen sharing session. I can reproduce the error here and we will get back to you tomorrow morning as discussed to resolve the issue.

The scheduler has to be started from the Omniscope installation directory.
e.g. for the run_scheduler.bat add a change directory command
cd "C:\Program Files (x86)\Visokio Omniscope"

The parameter visokio.localappdata passed to Java has to be the users "AppData"
e.g.
change it from
-Dvisokio.localappdata="C:\Program Files (x86)"
to
-Dvisokio.localappdata="C:\Users\Administrator\AppData\Local"

It is also recommended to separate the log for each of your schedulers.
In the batch file you use to start schedulers modify or add the parameter -DserverLogFilename to the java.exe command line you use.

Set a different log file name for each of the scheduler instances
e.g.
-DserverLogFilename=""C:\Users\Administrator\SchedulerSpecificLogFileName.txt"

You can double check the parameters used for starting the scheduler using the "OmniscopeEnterprise_debug.exe" in the installation directory
Open a command prompt and change to the installation directory.
run OmniscopeEnterprise_debug.exe
This will display a dialog saying that diagnostic information has been saved to the users home directory, press OK.
A command prompt will open which you can use to copy and paste the parameters for your batch file.
Remember to modify the schedulerConfigLocation paramter to match each of the schedulers.
-DschedulerConfigLocation="C:\Program Files (x86)\Visokio Omniscope\service\%CONF_DIR%\config.xml"

A dialog box saying Omniscope Scheduler is running will be displayed, press Exit.

Donald,
I've got multiple schedulers up and running in 2.8 b1235 on our dev box and am logging to separate files but have noticed an error in both logs:

ERROR: Unable to start legacy Generator service
Network error
A network error has occurred. Please check your connection and try again.

Address already in use: JVM_Bind

Unable to start legacy Generator service: Port 8301 unavailable for EntServer
Should I be seeing this or have I got something wrong?

Thanks,
Ed

I should probably add that the schedulers are both processing XML

Can you email us a copy of the script you are using to start the schedulers and the config.xml for both schedulers.
We want to check that they are using different ports.

You can ignore this error message when manually running two schedulers with different config files that are correctly configured with different ports.

The message is from the checks when running a single scheduler as a service to detect the console for managing the scheduler and is not applicable in this case.

2014.03.25 18:45:21.216 ERROR: Unable to start legacy Generator service

Network error
A network error has occurred. Please check your connection and try again.
Address already in use: JVM_Bind

Unable to start legacy Generator service: Port 8301 unavailable for EntServer

Update: from Omniscope 2.9 Plus you can enable concurrent scheduler task execution and avoid needing to have the separate configs and BAT files described above.
See http://forums.visokio.com/discussion/2867/scheduler-concurrent-task-execution

Also, from 3.0, the BAT file to launch Omniscope Server with a parameterised config.xml location should be changed to use the EXE directly. This is a much shorter command. For example:

SET CONF_DIR=%1
"C:\Users\YOUR_NAME\AppData\Local\Visokio Omniscope app\OmniscopeEnterprise.exe" "/jvmarg=-DschedulerConfigLocation=C:\PATH\TO\FOLDER\%CONF_DIR%\config.xml" "/jvmarg2=-DserverLogFilename=C:\PATH\TO\SOME\OTHER\FOLDER\log_%CONF_DIR%.txt"