As described in Controller Deployment, the tenant mode determines whether the Controller UI offers single or multiple environments to its users. This page describes how to create and manage accounts in a multi-tenant Controller.
Accessing an Account in the Controller UI
For a SaaS Controller or if multi-tenancy is enabled for an on-premises Controller, users need to enter the account name in the Account field when logging in to the Controller UI.
Instead of having users enter the account name manually, if the account name is passed in the Controller URL as the value of the accountName query parameter, the Account field is pre-populated with the account name.
For example, for a SaaS Controller, pass the account name in the URL as follows:
This form of the URL is useful in links that are shared with Controller UI users in an organization since it relieves those users from having to know and manually enter their account names.
Switch from Single-Tenant to Multi-Tenant Mode
While switching a Controller from single-tenancy to multi-tenancy mode is supported, switching from multi-tenancy to single-tenancy is not. Do not switch to multi-tenant mode unless you are sure that is the mode in which you want your Controller to operate.
To change to multi-tenant mode, in the Administration Console, find the
multitenant.controller Controller Setting and set its value to true.
Create Accounts in Multi-Tenant Mode
In multi-tenant mode, you can add accounts as follows:
- In the AppDynamics Administration Console, log in to the administration console as the AppDynamics root user
- Click Accounts and then New. The Create Account page appears:
- In the new account page, define the licensing entitlements that apply to the account.
Account-level license unit limits enable you to prevent a particular account from using more licensing units than it should. Note that the overall license limits applicable at the Controller level are independent of any specific limits you apply at the account level.
For example, say that you created an account specifically for the exploratory use of a particular group in your organization. If the total limit for the Controller is 100 Java Agents, you can ensure that the new account never interferes with the license availability of another account by setting the Java Units Provisioned value for the account to a much smaller limit, say 5. If you were to set it to 100 instead, and there are other accounts that are also set to 100, the available units for the Controller would be occupied by the first 100 agents that connect to the Controller, regardless of the accounts they report in to. Similarly, you can limit the life span of the account by setting an expiration date for the license.
You can see how many total license units are available to your Controller in the License Management page.
- When finished defining entitlements, click the Create icon.
After enabling multi-tenant mode, users need to specify the account they want to log into in the Account field in the Controller UI login screen. For details see Java Agent Configuration Properties, .NET Agent Configuration Properties, and Database Agent Configuration Properties, Machine Agent Configuration Properties.