AgileApps Support Wiki Pre Release

Difference between revisions of "Tenant Capabilities"

From AgileApps Support Wiki
imported>Aeric
imported>Aeric
Line 54: Line 54:
;Apply governors in Java code?: Turns tenant-level Governance ON or OFF. The default is '''ON'''. If unchecked, tenant has effectively unlimited use of Java resources. (Protections against runaway code are still in place, but the ceiling is very high.)
;Apply governors in Java code?: Turns tenant-level Governance ON or OFF. The default is '''ON'''. If unchecked, tenant has effectively unlimited use of Java resources. (Protections against runaway code are still in place, but the ceiling is very high.)


;Use custom values for this tenant: Used to set individual limits for the tenant. The default is '''OFF'''. When off, global settings are used. When on, values can be specified for:
;Apply custom limits for tenant: Used to set individual limits for the tenant. The default is '''OFF'''. When off, global settings are used. When on, values can be specified for:
:* '''Tenant level String Size''' - The total size of all strings allocated in the Java heap space during an execution interval.  
:* '''Tenant level string size''' - The total size of all strings allocated in the Java heap space during an execution interval.  
:* '''Tenant level Statement Count''' - The maximum number of Java code statements that can be run during an execution interval.
:* '''Tenant level statement count''' - The maximum number of Java code statements that can be run during an execution interval.
:* '''Tenant level CPU Time''' - The maximum number of CPU milliseconds that can be consumed during an execution interval.
:* '''Tenant level CPU time''' - The maximum number of CPU milliseconds that can be consumed during an execution interval.


''Learn more:'' [[Governors on Java Code]]
''Learn more:'' [[Governors on Java Code]]

Revision as of 00:15, 10 June 2011

Tenant Management System > Tenants > {Tenant} > Quick Links > Manage Tenant Capabilities

Available to Service Providers, this option provides the ability to configure platform options for service subscribers.

Lock-tiny.gif

Considerations
  • Due to the specialized nature of these features and the associated resource commitments, consider deploying only the options that are necessary to each tenant.
To enable/change Tenant Configuration Options
  1. Open the Tenant object
  2. Navigate to the tenant (customer) of interest
  3. In the Quick Links section, click the Manage Tenant Capabilities link
  4. Click the [Edit] button to change the elements available to this customer
  5. Click [Save]

Configuration Options

Use the checkboxes to enable tenant configuration options:

  • If checked, the option is enabled
  • If unchecked, the option is disabled

See the pages below for more information on the available options:

Execution Limits

Java Code Governors

Apply governors in Java code?
Turns tenant-level Governance ON or OFF. The default is ON. If unchecked, tenant has effectively unlimited use of Java resources. (Protections against runaway code are still in place, but the ceiling is very high.)
Apply custom limits for tenant
Used to set individual limits for the tenant. The default is OFF. When off, global settings are used. When on, values can be specified for:
  • Tenant level string size - The total size of all strings allocated in the Java heap space during an execution interval.
  • Tenant level statement count - The maximum number of Java code statements that can be run during an execution interval.
  • Tenant level CPU time - The maximum number of CPU milliseconds that can be consumed during an execution interval.

Learn more: Governors on Java Code

Setting up a Development Environment

These options are typically enabled together to set up a development environment: