Difference between revisions of "Manage Tenant Capabilities"

From LongJump Support Wiki
imported>Aeric
imported>Aeric
Line 60: Line 60:


;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.)
These governors apply to each ''execution request''--a request for platform execution resources that begins when tenant code executes (Java code in a Data Policy, Java code in a JSP page, or JavaScript code in an HTML page), and ends when that code terminates.


;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:
;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 request.  
:* '''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 request.
:* '''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 request.


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

Revision as of 00:20, 14 July 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

Maximum number of Rollup Summary Fields
The maximum number of Rollup Summary Fields allowed in the platform. (Each carries out operations in the background to keep the value up-to-date across the database, increasing the load on the system.)
Max. Job Count
The maximum number of scheduled jobs that can be executed per day. (This value only affects legacy customers enrolled in old billing plans. It is ignored for newer customers for whom Block Pricing is in force.)
Active
Determines whether the tenancy is active. Unchecking this box prevents that tenant's users from logging in.
External Library Folder
The place where external libraries are stored, so they can be used in Java classes. A relative path from the {platform_install}/tomcat/lib directory.}}

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.)

These governors apply to each execution request--a request for platform execution resources that begins when tenant code executes (Java code in a Data Policy, Java code in a JSP page, or JavaScript code in an HTML page), and ends when that code terminates.

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 request.
  • Tenant level statement count - The maximum number of Java code statements that can be run during an execution request.
  • Tenant level CPU time - The maximum number of CPU milliseconds that can be consumed during an execution request.

Learn more: Governors on Java Code

Setting up a Development Environment

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