Transaction class

Use this page to edit existing transaction classes, which are components of a service policy. Transaction classes apply the business goals of a service policy to specific application URIs. To view this administrative console page, click Operational Policies > Service Policy > New or edit an existing > Transaction Classes.

This page is divided in two tabs: Configuration and Local Topology. On the configuration tab you can view fields which were previously configured, and in some cases, edit those fields. On the local topology tab, you can see the transaction class memberships in a tree.

Configuration tab:

Name The name of the transaction class is a user-defined field that must contain alpha or numeric characters. This field is only editable when new transaction classes are being created.
Description The description field is complementary to 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.
Membership

Local topology tab:

The local topology tab visually represents the membership hierarchy for the given transaction class. The structure exists such that the highest level is the transaction class. Directly below the transaction class is the application and nested below that is the Web module. Finally, at the base of the hierarchy is the URI that was mapped to the transaction class during initial configuration.

The local topology is not editable. Any URI member mapping changes must be made under the configuration tab.