Hi Steve! This is a great improvement! Thanks!

We are working with 2.7 in DataManagers and Omniscope dashboards. Can we use the 2.8 Scheduler? Or will the outputs be different as usual. Is it a option to configure the Scheduler in 2.8 and running it in 2.7?

Thank you. Regards,
Alexander

Alexander,

You are free to use the latest alpha Scheduler when publishing files to older versions of the free Viewer. As long as your published files/templates only use functionality/views available in the older versions of the free Viewer, this will work.

The only risk is working with an alpha build is that it may be unstable - but for a given workflow, you will soon know if it has any stability issues that affect you.

Steve

(I'm not sure what you mean by "different as usual" - we strive to make Omniscope completely backwards compatible)

Thanks for the quick response.
The backwards compatibility is good to know.

To be sure (regarding the stability of 2.8) I would like to run the scheduler in 2.7. Yet the import/export/copy/paste functionality will save time. Can I use this functionality using 2.8. Then re-installing 2.7 and let the scheduler run in 2.7? Will that work?

Omniscope 2.8 is still in Alpha, and as such may not have the stability of a stable version.

Omniscope 2.7 scheduler settings should continue to work in 2.8 once you upgrade, if they do not, then it is a bug which we will need to fix, so do let us know.

We recommend that before you upgrade, that you make a copy of all existing config.xml files, data files and any other customisations you may have done. This will allow you to always revert back to previous configuration/files if something goes wrong.

I would personally also recommend that you test 2.8 using a test scenario to ensure everything works before using it with your real data files. Once again, keeping a back-up beforehand in case something goes wrong.

Please also note that when you upgrade from 2.7 to 2.8 it may be the case that certain external libraries Omniscope uses have been replaced, or are no longer valid. To fix this please follow the following steps

Visokio Windows Service

1. Stop the Visokio Enterprise service from windows "Services".
2. Copy the wrapper.conf file located in "service" folder in the Omniscope installation directory i.e. to Desktop temporarily.
   
3. Delete the Wrapper.conf file inside of the service folder.
4. Install the latest 2.8 Omniscope.
5. Open both the newly installed Wrapper.conf and the one saved in step 2 above. Compare and apply your own customised settings. In most cases this will the memory and additional Java parameters.
6. Restart the service from the windows "Services".
7. Once you have verified everything works, you can delete the saved copy of Wrapper.conf.

Starting Omniscope/Scheduler using a script

If you are launching Omniscope/Scheduler using a script rather than the executables located in the Omniscope install directory. We recommend you backup your existing scripts. Run the appropriate _debug.exe file in the Omniscope install directory and update your scripts with the correct paths shown in CMD (black window) that appears on screen.

If you have any problems, or are not sure, do post on the forum or give us a call.

Thank so much for the extensive answer! Will you post on this topic when the build is available?

Regards, Alexander

The build with this feature is available on the 2.8 download site - simply choose the most recent build from the 'Daily builds' section.

This feature is now publicly available in 2.8 beta:
http://forums.visokio.com/discussion/2130/omniscope-2.8-beta