Runtime Workflow Debugging

Do you want to directly influence and change your workflow’s submission process and result? Well, the recently released gUSE 3.6.1 gives you an appropriate solution.

If you want to interact with your workflows in runtime for tracing and debugging, you can use breakpoints. You can configure breakpoints to jobs in the WS-PGRADE within the main job configuration process and then during in the job submission process you can enable or prohibit the running of job instances at these breakpoints.

These breakpoints will be applied to all running instances of a job in the job submission process. During submission the gUSE/WS-PGRADE system runtime detects the defined breakpoints and it calls you when it reaches them. When you received the call about this event, you can enable or prohibit the continuation of the execution. You can stop the running of the job instance (e.g. for job reconfiguration), while you can enable running of another job instance in parallel (with other inputs and therefore with other results) of the same workflow instance.

Thanks to this new solution you can learn much more about your workflows and about what is happening in runtime. By tracing and debugging you are able to filter out the well-running and bad-running job instances in runtime to reach the desired workflow execution results.

For more details, please see the Portal User Manual (chapter 13) and the WS-PGRADE Cookbook (section Tips&Tricks).

Posted by Tibor Gottdank 2013-11-08 Labels: guse debugging workflow

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks