airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Danushka Menikkumbura <danushka.menikkumb...@gmail.com>
Subject Re: Web based Workflow Execution Interface
Date Sun, 09 Jun 2013 01:17:53 GMT
Sanchit,

You can use the -xdebug option to start Airavata in debug mode and attach
to it remotely. The default port is 8000.

Danushka


On Sun, Jun 9, 2013 at 5:53 AM, Sanchit Aggarwal <
sanchitagarwal108@gmail.com> wrote:

> Hi suresh
>
> I was looking into the code base and to have better understanding
> about the interaction of different modules of the Airavata, ( esp.
> how the workflow is being executed after it is composed) want it to
> run in a debug mode.
>
> do we have to set any configuration in order to do that? can you
> please give me pointers to do that.
> Regards
> Sanchit Aggarwal
> MS Research (Computer Science)
> Center for Visual Information Technology
> IIIT Hyderabad, Gachibowli
> Contact - 9581417330
>
>
>
> On Sat, Jun 1, 2013 at 7:48 PM, Sanchit Aggarwal
> <sanchitagarwal108@gmail.com> wrote:
> > 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.
> >
> >
> >
> > Regards
> > Sanchit Aggarwal
> >
> >
> >
> > On Fri, May 31, 2013 at 6:36 PM, Suresh Marru <smarru@apache.org> 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 <
> sanchitagarwal108@gmail.com> 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
> >>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message