Project creation may need to be customized per tenant. For example, project 
approval steps during project creation.  Therefore, sub tenant space is best.

 a client may have unique requirements for every aspect  , and require 
customization per tenant.  By default,  run in tenant space instead of super 
tenant space.

With our MT servers and multiple topology options, performance scaling should 
be orthogonal to tenant personalization.

/Chris



On Aug 2, 2013, at 5:24, Dimuthu Leelarathne <[email protected]> wrote:

> Hi all,
> 
> I think the question does not convey the real problem, which is whether to 
> run BPEL in or super tenant only - which is the current case. I believe the 
> correct thing is
> 
> 1 - Run the tenant creation BPEL in super tenant
> 2 - Run rest of the BPEL in tenant space
> 
> Feature-wise i think it is the best way to do it.
> 
> If we have lot of node - cluster the BPEL. If we have even more, do tenant 
> partition of it, which is orthogonal to the real question.
> 
> thanks,
> dimuthu
> 
> 
> On Fri, Aug 2, 2013 at 2:01 PM, Nihanth Joseph <[email protected]> wrote:
>> Hi,
>> 
>> We are having problem during appfactory, application creations. At the 
>> moment, appfactory app creation is handled by super tenant (application 
>> creation is handled by BPEL service and it is deployed as super tenant), 
>> therefore when number of tenants increase, there will be over-loaded in BPEL 
>> service. In order to prevent that, do we want to deploy BPEL per tenant or 
>> BPEL as a stand alone service or is there any other way of solution to 
>> prevent service overload? 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> -- 
>> Nihanth Joseph
>> Senior Software Engineer
>> Mob: +94719187136
> 
> 
> 
> -- 
> Dimuthu Leelarathne 
> Architect & Product Lead of App Factory
> 
> WSO2, Inc. (http://wso2.com)
> email: [email protected]
> Mobile : 0773661935 
> 
> Lean . Enterprise . Middleware
> _______________________________________________
> Dev mailing list
> [email protected]
> http://wso2.org/cgi-bin/mailman/listinfo/dev
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Reply via email to