Scheduler: Running from a 3rd party application?

kattasureshkumar · January 11, 2013 8:41AM

We are trying to run Omniscope Scheduler from a 3rd party application by giving the path "C:\Program Files\Visokio Omniscope\OmniscopeEnterprise.exe" . We had prepared a schedule to run certain IOK files to process the data and publish them to tables. But do we have any facility to stop the scheduler once the data processing & publishing is over.

Actually our requirement is , when we have got new flat files, Our front end application will submit a request , this will trigger Omniscope Scheduler as we had provided the Omniscope Scheduler path. Once all the files are submitted, Omniscope Scheduler should stop and should close. Again if the front end application sends a request then Omniscope Scheduler should rerun and process the data and the Scheduler should stop after data is published.

Please let us know if we are doing it in a wrong way.

Thanks, Suresh.

tjbate · January 11, 2013 9:37AM

Suresh - Omniscope Server's Scheduler process is designed to run continuously 24/7, even as a Windows service. If you need event-driven automation, whereby your systems wish to take immediate over-riding control of the Scheduler Task List, this is done by your systems writing an XML Actions text file into the designed continuously-monitored Scheduler watchfolder for immediate execution, as described here:
http://www.visokio.com/kb/watch-folder

steve · January 12, 2013 4:36AM

Alternatively you can execute a single XML action using the command line as described at the end of this page:
http://www.visokio.com/kb/xml-actions

kattasureshkumar · January 15, 2013 6:07AM

If possible please send us a sample script for stopping the scheduler for the XML actions.

January 15, 2013 7:03AM

Sorry, I don't quite follow what you mean. Do you want to run a script that stops the Scheduler from processing the current task?

kattasureshkumar · January 15, 2013 7:13AM

I was asking that XML sample script only. Please send if possible.

tjbate · January 15, 2013 9:14AM

Suresh - You can generate 'model' XML Actions files by exporting them from the Scheduler Task List. Your own systems can then generate their own versions of these model XML Actions (used to trigger immediate execution of specified file actions by saving them to the Scheduler watchfolder) by following the same syntax/schema as the exported 'model' file.

Configure each action in the Scheduler Task List as normal, then select the Task you wish to have a 'model' file for and choose Export selected

I attach some exported examples of XML Actions model files, one for launching a 3rd Party application from a batchfile and another for exporting a custom JAR bundle ( a custom JAR bundle is an IOK data file plus free Viewer installer together in a single JAR)

	Launch3rdPartyAppfrom Batchfile-TaskModel.xml	585B
	ExportCustomJAR-TaskModel.xml	806B

Welcome!

Categories

Ideas Parade

Tagged