airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sanchit Aggarwal <>
Subject Re: Web based Workflow Execution Interface
Date Sat, 01 Jun 2013 14:18:49 GMT
Hi Suresh

My understanding on the workflow execution is that the Condor DAG/BPEL
is formed after the composition of the workflow which is than
interpreted by the axis2 based workflow interpreter web service. The
workflow execution context is used to specify the parameters for
scheduling , handling of inputs etc. This execution context is given
from the Xbaya GUI where the context header and other are taken a s a
input. Finally a Executable is formed which is then used for running
the job by GFac.

So according to the above understanding, I guess The Execution
interface has to be developed which will export the composed workflow
to various workflow languages like BPEL/DAG etc. Please correct me If
I am wrong.

Since not much has been discussed on the execution interface module of
the master project ,could we have more inputs on the same.

Sanchit Aggarwal

On Fri, May 31, 2013 at 6:36 PM, Suresh Marru <> wrote:
> Sanchit,
> Yes lets start the discussion. Please take the lead and post your understanding and ask
specific questions.
> Suresh
> On May 31, 2013, at 7:32 AM, Sanchit Aggarwal <> wrote:
>> Hi Heshan/All
>> I am covering workflow execution interface part of the master project
>> in my sub-project.Since the current implementation of the workflow
>> execution context specification is expressed in xml schema encompassed
>> within the workflow wsdl it has to be re-framed.
>> Can we all start discussing here so to get a better understanding of
>> workflow execution context and its representation?
>> Regards
>> Sanchit Aggarwal

View raw message