Classifying WebSphere transaction workload for WLM

This topic describes how to use transaction classes to classify client workload for workload management. The workload is different WebSphere transactions targeted to separate servant regions, each with goals defined by appropriate service classes. Each transaction is dispatched in its own WLM enclave in a servant region process, and is managed according to the goals of its service class.

Before you begin

This topic describes steps to classify transaction workload as a way of managing the workload service objectives. You also need to define the service objectives (goals) for the service classes used. In addition, you must define the service objectives of the WebSphere Application Server for z/OS servers and your business application servers.

For more information about defining service objectives (goals) for each service class, see the z/OS MVS Planning: Workload Management book, SA22-7602, for example at Target can be accessed only when this topic is linked to the World Wide Web   http://publibz.boulder.ibm.com/epubs/pdf/iea2w131.pdf , or the z/OS WLM Web page at Target can be accessed only when this topic is linked to the World Wide Web   http://www.ibm.com/servers/eserver/zseries/zos/wlm/ .

Why and when to perform this task

You can classify your WebSphere work using the WLM CB-type classification criteria:

Note: To get started, you do not need to define special classification rules and work qualifiers, but you may want to do this for your production system.

To classify work using server and userid criteria, you use a combination of the WLM Workload Classification rules in the WLM ISPF dialog panels. For more information about defining WLM Classification rules, see Workload management (WLM) and its related article that includes an example of classification rules.

To classify work using transaction classes, you define and use transaction class mappings, as described in this task. The steps to classify work using transaction classes are:

Steps for this task

  1. Define transaction class mappings based on the HTTP virtual host name, port number, and URI (Universal Resource Identifier - encoded address for any resource on the Web) provided with each work HTTP or HTTPS request.
    1. Create a Transaction Class mapping file (as a simple text file).
      For example: /wasconfig/t5was/MyTrMapFile.txt

      Note: This file must be in ASCII format.

    2. Edit the Transaction Class mapping file to define each transaction class mapping that you want to use.
      Define each mapping on a separate line, using the following syntax:
      TransClassMap host:port uritemplate tclass

      Note: In the host or port fields, you can use wildcard characters only for the entire field as shown in the following example.

      This syntax is the same syntax as for WebSphere Application Server for z/OS Version 4.0.1. For more information about this syntax, see Transaction class mapping file entries.

      For example:
      TransClassMap wsc4.washington.ibm.com:9080  /MyIVT/index.*    TCLMYIVT
      TransClassMap wsc4.washington.ibm.com:9080  /MyIVT/ivtejb     TCLMYEJB
      TransClassMap wsc4.washington.ibm.com:*     /SuperSnoop*      TCLSNOOP
      TransClassMap wsc4.washington.ibm.com:*     /ssb/*            TCLSSB
      TransClassMap *:*                           /admin*           TCLADMIN
      
  2. Specify the Transaction Class mapping file on the administrative properties for each server that is to handle work classified by transaction class.
    To specify the Transaction Class mapping file for a server, use the administrative console to complete the following steps:
    1. In the navigation pane, click Servers > Application Servers.
    2. In the content pane, select the server instance, server_name.
    3. In the Additional Properties list in the contents pane, select Web Container.
    4. In the Additional Properties list for the Web container, select Advanced Settings.
    5. In the Transaction Class Mapping field, type the name of the Transaction Class mapping file that you edited in an earlier step.
      For example: /wasconfig/t5was/MyTrMapFile.txt

      This sets the following variable in the server's was.env file:

      protocol_http_transport_class_mapping_file=/wasconfig/t5was/MyTrMapFile.txt

    6. If you want to use a transaction class to classify outbound data that is delivered in response to HTTP and HTTPS requests, select the TCLASS option in the Network QoS field.
      If you specify TCLASS, WebSphere Application Server for z/OS uses the transaction class value that was used to classify the inbound request to the z/OS Workload Manager.

Example

The following table shows classification rules for CB-type work in which the default service class is WSMED and has a reporting class of RWSDEFLT. Work run in the WSPROD WebSphere server is classified as WSMED with a reporting class of RWSPROD, unless it has a transaction class of TCLASS1, TCLASS2, or TCLASS2 assigned through the transaction class mapping file below.

Qualifier    Qualifier Start       Service  Report
# type       name      position    Class    Class
- ---------  --------  --------    -------- --------
                          Default: WSMED    RWSDEFLT
1 CN         WSPROD    1           WSMED    RWSPROD
2 . TC       . TCLASS1             WSFAST   RWSPRD1
2 . TC       . TCLASS2             WSMED    RWSPRD2
2 . TC       . TCLASS5             WSSLOW   RWSPRD5
1 CN         WSTEST    1           WSSLOW   RTSTEST
2 . UI       . USER1               WSMED    RTSTSTU2
2 . TC       . TCLASS5             WSSLOW   RTSTST5

The following table shows how work can be assigned a transaction class based on its host name, port number, or URI. For example, a web request of http://ibm.com:80/Webap1/myservlet handled by the WSPROD server would be assigned a transaction class of TCLASS1, a service class of WSFAST, and a reporting class of RWSPRD1 by the classification rules shown above.

TransClassMap www.ibm.com:80 /Webap1/myservlet TCLASS1
TransClassMap www.ibm.com:* /Webap1/myservlet TCLASS2
TransClassMap *:443 * TCLASS3
TransClassMap *:* /Webap1/myservlet TCLASS4
TransClassMap www.ibm.com:* /Webap5/* TCLASS5
TransClassMap * * TCLASS6


Related reference
Web container advanced settings
Transaction class mapping file entries
Controller and Servant WLM classifications



Searchable topic ID:   tjta_ztclass
Last updated: Jun 21, 2007 9:56:50 PM CDT    WebSphere Application Server for z/OS, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.zseries.doc/info/zseries/ae/tjta_ztclass.html

Library | Support | Terms of Use | Feedback