Knowledge Base

cancel
Showing results for 
Search instead for 
Did you mean: 

What are license rules and how do they work?

Table of Contents

 

What are license rules?

License rules help you specify the allocation and distribution of licenses across all of your applications and machines. There are two types of rules: default and custom. We’ll break down these two types of rules below, though you can also read about them in our official documentation.

 

License rules are not mandatory and can be based on your Controller or account preferences. For example, you can manage multiple accounts as a Controller admin and decide which account should have license rules and which should not. To enable the license rules feature, navigate to the Location → Settings → Licenses → Rules in your Controller and click the blue “Create Rules” button.

 

The following image illustrates the flexibility of license assignments:

License Rules Overview.jpeg 

Here are three examples of how license rules function based on the License Rules Overview diagram above.

  1. Monitored Application e is under License Rule 2 - Application Scope AB, and is also under License Rule 3 - Application Scope AC. If an agent with Application e try to connect using any other license rules, it will fail.
  2. There is an unmonitored application with no name that’s been added to License Rule 2 - Application Scope AB. Should it ever be monitored, it can only connect using the License Rule 2 Access Key.
  3. Application a is deployed on Machine ii. If Machine ii is moved out of scope for Machine Scope MA, Application a and all of the agents on Machine ii will be down and not allowed to connect.

 

What is a default rule?

Default rules automatically distribute licenses evenly across all applications if you don’t have a custom rule set up. To see if you have created any rules, navigate to Location → Settings → Licenses in your Controller. If there are none, click the blue "Create Rules" button. This will set up a "default" rule, which will also be the name of the rule. When it’s created, it will have all license entitlements and its Access Key will be the same as the Account Level Access Key.

 

You can rename the default rule (e.g. “Default” → “John Doe”), but it’s not recommended since it can create confusion. Once you rename it, the only way to know that it is the default one is to match the Access Key to that of the Account Level Access Key.

 

What is a custom rule?

You can also set up custom rules, which let you to specify the number of licenses allocated to certain license modules. When creating a custom rule, you can stipulate how many units to allocate to a rule or which applications/servers can consume agents. Once set up, it will serve as your new “default” and licenses will be allocated according to your new preferences. Please note that the custom rule Access Key will be different than the Account Level Access Key.

 

For detailed instructions on how to create a custom rule and steps to take after setting one up, see: Creating Custom Rules.

 

What agents are supported via License Management?

The screenshot below shows which agents are supported via license management as of 4.4.2+.  Please note that some are not available in 4.3.x versions.

License Management.png

 

What happens if I delete a license rule?

To learn more about this scenario, see: What happens if I delete a license rule?

Version history
Revision #:
4 of 4
Last update:
‎10-24-2018 01:01 PM
Updated by:
 
Labels (1)
0 Kudos