You can create service policies that fit user-defined business goals. Service policies create work-related goals that WebSphere Extended Deployment uses 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.
To categorize work, WebSphere Extended Deployment uses the concept of a transaction class. 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 WebSphere Extended Deployment. Data collected at this level can display performance metrics at the granularity of a single transaction class.
WebSphere Extended Deployment 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. WebSphere Extended Deployment supports average response time goals, as well as percentile response time goals.
When defining a service policy, WebSphere Extended Deployment provides seven different levels of importance that can be used. Creating levels of importance guarantees that in the event the performance goals for all service policies cannot be satisfied because of prolonged intense overload, WebSphere Extended Deployment can use importance to decide which service policy takes priority.
WebSphere Extended Deployment information center (online)