Hi, On Mon, Mar 24, 2014 at 8:04 PM, Sagara Gunathunga <[email protected]> wrote:
> > > > On Mon, Mar 24, 2014 at 11:52 AM, Kasun Indrasiri <[email protected]> wrote: > >> I would like to clarify the objective of this task: >> >> - Introduce the concept of a Task provider in to ESB. Which means any >> existing task (task config) can be ran on the available task provider( this >> can be ntask, quartz or anything) >> > > Is this means we continue to support Quartz as well ? IMO for simple use > cases it's important to continue support for Quartz while Task server may > fit into complex use cases. > Something to clarify here, it seems most doesn't properly understand/explain use of ntask component and the Task Server itself. It is not the Task Server itself that is put into the ESB, it is the ntask component. Using this component, you can run tasks in several modes, namely, STANDALONE, CLUSTERED, and REMOTE. STANDALONE is the exact same thing as you have now in the ESB scheduler. And btw, ntask component also uses Quartz internally, so it is the same behavior. The existing ESB task implementation is kept because we cannot add the WSO2 specific ntask component to the Synapse project, so as Kasun explained, the Task Provider abstraction is brought in because of that. The REMOTE mode mentioned there for the ntask component, can be used to interface that with an external Task Server. Task Server would be running separately, and with this mode, the ESB tasks triggering would be automatically offloaded to TS. This mode is mainly used in a cloud setup with the ELB, where it is used in scenarios like tenant partioning aware task load balancing. CLUSTERED mode is the normal mode you would use when you have your own server cluster and you want the task to be highly available and load balanced. So basically all these modes are simply a configuration setting and the user/developer will not see any different when using/developing the tasks. Cheers, Anjana. > > Thanks ! > > >> - However, the recipes concept is completely transparent at Synapse >> level. Simply we don't have to thing about recipes when doing this. >> Recipe(or Dish) can be consider as a place where specific logic is executed >> on top of generic task. >> - All the details on sequence deployment, template invocation is not >> related to ESB task provider concept. >> >> >> On Sat, Mar 22, 2014 at 7:36 AM, Ishan Jayawardena <[email protected]>wrote: >> >>> I am working on $subject to support scheduled invocation of recipes in >>> the ESB. This mainly includes replacing the existing quartz based task >>> scheduler with ntask scheduler. The new task type is based on ntask, and it >>> will be added as a new component in the mediation category. We can use the >>> existing task management UI of the ESB to add and manage tasks. >>> >>> In addition to the task schedule information, template name and template >>> parameter values, a special property must be added to the task parameter >>> list at the time of task creation so that the task can invoke the template >>> within its execute method. >>> >>> The task, >>> reads properties and builds a synapse sequence by inserting the >>> recipe template in it, >>> deploys the sequence into synapse, >>> injects a message to the above sequence to invoke the template. >>> >>> Thanks, >>> Ishan. >>> >>> -- >>> Ishan Jayawardena >>> Senior Software Engineer >>> Mobile: +94 (77) 408 2330 >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Kasun Indrasiri >> Software Architect >> WSO2, Inc.; http://wso2.com >> lean.enterprise.middleware >> >> cell: +94 77 556 5206 >> Blog : http://kasunpanorama.blogspot.com/ >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Sagara Gunathunga > > Senior Technical Lead; WSO2, Inc.; http://wso2.com > V.P Apache Web Services; http://ws.apache.org/ > Linkedin; http://www.linkedin.com/in/ssagara > Blog ; http://ssagara.blogspot.com > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Anjana Fernando* Technical Lead WSO2 Inc. | http://wso2.com lean . enterprise . middleware
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
