Service policy settings

Use this page to change existing service policies or transaction classes, which together create an operational policy. To view this administrative console page, click Operational Policies > Service policies > service policy.

On the configuration tab you can view fields which were previously configured, and in some cases, edit them.

Configuration tab:

Name The name of the service policy is a user-defined field that must contain alpha or numeric characters. Use consistent and meaningful service policy names, for example, PLATINUM, GOLD, SILVER, and BRONZE.
Description The description field complements the name field and is user-defined. This field is optional, but it is recommended, particularly in environments with multiple system administrators, that this field be completed with useful information. For example, a description field for a PLATINUM policy may read, The PLATINUM service policy is reserved for the highest priority work.
Goal type This is a selectable field that may be one of four values:
  • Discretionary: Discretionary is the default value for goal type. Discretionary indicates work that is not high priority and can be scheduled by the on demand router based on the existing workload in the queue.
  • Average response time: Indicates high priority work. This field is used with the goal value and importance to limit the time this work is kept in queue.
  • Queue time: Maximum amount of time acceptable for a job to wait in the scheduler queue before being dispatched for execution and still maintain the level of service which the service policy implies.
  • Percentile response time: This a percentage of requests handled in a specific period of time. This field is used with the goal percent to define the percentage of requests per seconds or milliseconds.
Goal value This field should be set to equal the maximum time allotted for completion. For example, PLATINUM work should not exceed two seconds. Unavailable when the goal type is discretionary.
Goal percentile The percentage of requests to be handled in a specific time frame. Can be a whole number from 1 to 99 inclusive. This field is available when the goal type is percentile response time.
Importance Indicates a level of importance. Unavailable when the goal type is discretionary.
Monitor for persistent policy violations

Selectable field that requires different settings depending on the type of response time:

  • Average response time view
    • When the goal value is exceeded by: An integer that indicates the milliseconds, seconds or minutes of the goal value. Acceptable values are 0 to 3000 milliseconds, 0 to 300 seconds, and 0 to 2147483647 minutes.
    • For the following period of time: An integer that indicates the milliseconds, seconds or minutes after which the goal value is in violation. This can be 0 to 1 day, inclusive.
  • Percentile response time view
    • When the actual percentage of requests served falls short of the configured goal percentile by the following amount: An integer that indicates the percentage of requests below the goal value for which to monitor. This can be 0 to 100, inclusive.
    • For the following period of time: An integer that indicates the milliseconds, seconds or minutes at which the goal value is in violation. This can be 0 to 1 day, inclusive.
Membership Creates an association between transaction classes and a respective service policy. Each transaction policy can be contained in only one service policy. You can do the following:
New
Creates new transaction classes, which can then be made members of a new or existing service policy.
Remove
By selecting a transaction policy from the membership field and clicking this Remove, you can remove the association between a transaction policy and a service policy. This action deletes the transaction policy altogether.
Modify
Changes an existing transaction policy. To edit a transaction policy, you must first select the transaction policy you want to edit and click Modify.
Move
Moves transaction classes from one service policy to another. Because a transaction class cannot exist outside of a service policy association, the only other option to move is remove if you no longer want a transaction class and a service policy to be affiliated. To move a transaction class, select the policy you want to associate with another service policy and click Move.