Transaction class mapping file entries indicate the workload
management (WLM) goal for each class of client work. Each client transaction
is dispatched in its own WLM enclave in a servant region process,
and is managed according to the goals specified for its service class.
Deprecated feature: Transaction class mapping file
support is deprecated. You should use a workload classification document
instead of a transaction class mapping file to classify work requests.
depfeat
Following is the syntax for entries in a transaction class mapping
file:
TransClassMap host:port uritemplate tclass
where:
- host
- Is the value compared against the hostname of the HOST: header
of the request.
Avoid trouble: You cannot use
wild-card characters in the host field unless you use it for the entire
field; for example
*:*.
gotcha
- port
- Is the value compared against the port of the request.
Avoid trouble: You cannot use wild-card characters
in the port field unless you use it for the entire field; for example
*:*.
gotcha
- uritemplate
- Is the value compared against the URI of the request. Any query
string will not be used in the comparison. This value can be a wildcard
'*', or end in a wildcard.
- tclass
- Is the Workload Manager Transaction Class name that will be used
in the creation of the enclave.
Examples:
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:* /webap2/* TCLASS5
TransClassMap * /myservlet TCLASS6
TransClassMap * * TCLASS6