PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


Skip to end of metadata
Go to start of metadata

On this page:

The Controller tenancy mode determines whether context within the Controller is divided into separate accounts. Each account is an entirely distinct realm within the Controller UI for purposes of user authentication, agent reporting, and monitoring. 

The tenancy mode of an on-premise AppDynamics Controller (whether it is single-tenancy or multi-tenancy) is set at installation time. You can switch the tenancy mode from single-tenant to multi-tenant mode later, as described here.  

Having a single tenancy Controller is suitable for most installations. Only very large installations or installations that have very distinct sets of users may require multi-tenancy.  

Differences Between Single and Multi-Tenant Mode

In multi-tenant mode:

  • You can create multiple accounts (tenants) in the Controller. 
  • Each account will have its own set of users and applications. 
  • The Controller login page includes an additional field where users need to choose an account to log in to. 
  • Essentially, multi-tenant mode allows you to partition users and access to application data in a logical, secure way. 

In single-tenant mode:

  • There is only one account (tenant) in the Controller system. 
  • All users and applications are part of this single built-in account, so all users have access to all monitored Applications in this mode.
  • The account is not exposed to users in the Controller UI. The account field in the login page is omitted for single tenant mode.
  • AppDynamics recommends single-tenant mode for most installations.

Accessing an Account in the Controller UI 

For a SaaS Controller or if multi-tenancy is enabled for an on-premise 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:  

https://<account-name>.saas.appdynamics.com/controller/#/accountName=<account-name>

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 this 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 in the AppDynamics Administration Console. To add an account, after logging 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 and when done, click the Create icon.

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 Information page. 

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 PropertiesStandalone Machine Agent Configuration Property Reference.

Applying a License to a Multi-Tenant Controller

  1. Login with root user at http://<controllerhost>:<port>/controller/admin.jsp
  2. Click Accounts and select the account you want to apply the license to.
  3. Update the License expiration date and license units based on license.lic 
  4. Save the changes 
  5. With an administrator account, check the license page to see the latest changes.
  • No labels