Hi Nipuni, For services invocations Airavata uses WS-Addressing. You may find this paper useful - [1]
Note, the enactment engine is changed from ODE to Airavata's native workflow interpreter, but lots of arguments on asynchronous invocations will be still valid. Suresh [1] - http://grids.ucs.indiana.edu/ptliupages/publications/bpel-lead-gce-09_final.pdf On Mar 19, 2013, at 2:54 AM, Nipuni Perera <[email protected]> wrote: > Hi, > > Yes, asynchronous refers to concurrently invoking web services. > As an example, WS-callback, WS-addressing use *push* pattern for > asynchronous invoke of web services. > Therefore we are interested in whether Airavata supports this feature when > executing workflows, and if so what asynchronous pattern is used. > > Thanks, > Nipuni > > On Mon, Mar 18, 2013 at 8:06 PM, Lahiru Gunathilake <[email protected]>wrote: > >> What do you mean by Synchronous workflows ? Is it like executing all >> the independent node concurrently and execute dependent nodes in the order >> ? >> >> >> Lahiru >> >> >> On Mon, Mar 18, 2013 at 3:43 AM, Nipuni Perera <[email protected] >>> wrote: >> >>> Hi, >>> >>> As we went through the research, we found out that due to large scale of >>> geoscience data, the execution time is considerably large and can range >> to >>> several days. So we need to know whether Airavata supports asynchronous >>> workflows. If so what kind of asynchronous architecture patterns(eg; >> pull, >>> push) are supported. >>> >>> Thanks, >>> Nipuni >>> >>> -- >>> Nipuni Piyabasi Perera >>> Undergraduate >>> Department of Computer Science And Engineering >>> University of Moratuwa >>> Sri Lanka >>> >> >> >> >> -- >> System Analyst Programmer >> PTI Lab >> Indiana University >> > > > > -- > Nipuni Piyabasi Perera > Undergraduate > Department of Computer Science And Engineering > University of Moratuwa > Sri Lanka
