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 | This field adds application module URIs to the transaction
class. URI associations are not limited to any one application or module,
so one transaction class could contain all URIs for a payment transaction,
or a name field lookup. With this common grouping an organization can assemble
all categories of transactions into a transaction class to ensure it receives
the priority designated to it by the service policy. Edit this field by selecting the appropriate application and module from the lists. The resulting URIs display in the Available URIs from list. Select the appropriate URIs from the available list. Select multiple URIs by holding the Ctrl key until all of your selections are highlighted, and clicking Add to make the URIs members of the transaction class. Only available URIs from the selected application and web module are shown in the available list. If the list is empty, it is possible that the application and web module are not selected, or no URIs in the application and web module pair are not already mapped to another transaction class. To remove existing URIs from a transaction class, select one or more from the list of current members and click Remove. The selected URIs are removed from the membership list and are made available. If a URI is from the selected application and web module, it will display again in the available list. However, if the URI is not from that selected application and web module, it is not shown in the available list. If you change these to match the application and web module of that removed URI, it should become available. |
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.