Service policy overview

You can create service policies that fit user-defined business goals. Service policies create work-related goals used to categorize and prioritize work.

To view this administrative console page, click Operational policies > Service policies.

To create, modify, or remove service policies and transaction classes, you must have administrator or configurator administrative privileges.

The service policies are used to:

To categorize work, the concept of a transaction class is used. Transaction classes are components of a service policy. A transaction class contains user-defined Universal Resource Identifiers (URI). For example, all /buy/*.html URI strings can be associated with the transaction class PayTransactionsClass. Transaction classes are the smallest unit of categorization in the intelligent management environment. Data collected at this level can display performance metrics at the granularity of a single transaction class.

The product can associate performance goals to transaction class level work using a service policy. A service policy is defined as a collection of transaction classes with an associated performance goal. For example, you can create a service policy called Platinum and associate PayTransactionClass as a member. Define performance goals associated with transaction classes in terms of response times. The product supports average response time goals, as well as percentile response time goals.

When defining a service policy, seven different levels of importance can be used. If the performance goals for all service policies are not met due to prolonged intense overload, the importance criteria are used to decide which service policy takes priority.



File name: servicepolicy_overview.html