Carbon And Multi-Tenancy

Time Flies .. we have been very busy here at WSO2 !

I promised I would talk about multi-tenancy , in our on-premises product and there it goes, finally! I recently worked on a packaged demo for a Governance Tutorial at WSO2Con – We illustrated how to prepare applications to separate environment specific data from an application. To simulate isolated Dev and QA environments, I leveraged the multi-tenancy feature of our AppServer ( this feature is part of the Carbon platform, and therefore available on-premises in most of our products).

ImageIn order to create a tenant, you need to login as “super-admin” , i.e. out of the box, the default admin/admin credentials. When you log as admin, you are in “super-tenant” mode. Managing tenants is only available in this mode. In the setup above, I have added two tenants: DevAS and QA-AS. Let’s add a third one:

ImageMost of the fields are rather obvious , but two need further attention:

  • Domain name, here this is a unique identifier for my domain. I need to use it to log into the admin console and being taken to my specific tenant, and it’s also used in URLs to distinguish one tenant from another.
  • Usage Plan :  this is inherited from our Stratos PaaS – The idea is that you can limit the capabilities of a tenant using a plan (nb of users, bandwidth, etc.) – The product comes with a predefined list, and you can add your one and/or tailor the existing ones. For on-premises deployment, there is only one default plan, Demo.

Once the tenant is created, you can log out from super tenant mode, log into your tenant, using the admin user you just created, i.e. and work on the application server.

You can now deploy, manage and test applications on this tenant, using the specific tenant URL, for example:

If you want to experience how this works in our PaaS environment, I encourage you to connect to StratosLive, which is a Stratos environment deployed and managed by WSO2.

That’s all for today !



One thought on “Carbon And Multi-Tenancy

  1. Hi isamauny,

    I test WSO2 EMM in multi-tenant mode, but if I create multiple domain I can assign only demo plan, and only the admin/admin user to emm console can add user to default tenant.

    The second tenant I’ve created isn’t able to create user, and to modify Plan.

    is this because this capabilities is available only in your cloud product?



Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s