An example would be for BAM: Tenant 1 would configure a task, example: summarizing to run on his data.
Tenant 2 would not want this summarizer. But, he has another task which polls a web service as a heartbeat mechanism and records results. So, depending on the tenant we would only allow the task to access only their own key space/ database in their data storage. We also need to load/save the task configurations in the registry ( this part should be trivial). Hope the example is clear. On Sat, Sep 24, 2011 at 6:08 AM, Samisa Abeysinghe <[email protected]> wrote: > What tenant specific task(s) are you talking about? Can you give some > example? > > I assume the ESB task component can run in multi tenant mode. > > Samisa... > > On Fri, Sep 23, 2011 at 3:56 PM, Tharindu Mathew <[email protected]>wrote: > >> Hi everyone, >> >> I believe many products have this requirement. How can we do $subject? >> >> I was thinking of storing task related configurations in the tenant's >> registry. The task engine then executes the task only allowing access to >> resources that the specific tenant has access to. >> >> WDYT? >> >> -- >> Regards, >> >> Tharindu >> >> blog: http://mackiemathew.com/ >> >> >> _______________________________________________ >> Carbon-dev mailing list >> [email protected] >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > _______________________________________________ > Carbon-dev mailing list > [email protected] > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- Regards, Tharindu blog: http://mackiemathew.com/
_______________________________________________ Carbon-dev mailing list [email protected] http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
