The purpose of the WebContainer activity SMF record is
to record activity within a WebContainer running inside a WebSphere® Application Server for z/OS® transaction
server.
The web container is deployed within an EJB and runs within
the EJB container. The WebContainer acts as a web server handling
HTTP sessions and servlets. The EJB container is not aware of the
work the WebContainer does. Instead, the EJB container only records
that the EJB has been dispatched. Meanwhile, the WebContainer gathers
the detailed information, such as HTTP sessions, servlets, and their
respective performance data. A single WebContainer Activity record
is created for each activity that is run within a web container.
WebContainer
SMF recording is activated and deactivated along with the activation
and deactivation of SMF recording for the J2EE container.
WebContainer activity record (Version 2) schema
This
section includes Subtype 7: WebContainer activity record (Version
2).
WebContainer activity section
.
Table 1. WebContainer activity section. There
is one section per record. The WebContainer activity section contains
information about each activity that occurred within one web container.
Offset (decimal) |
Offset (hexadecimal) |
Name |
Length |
Format |
Description |
0 |
0 |
SM120WAA |
64 |
EBCDIC |
The WebSphere transaction server host name. |
64 |
40 |
SM120WAB |
8 |
EBCDIC |
The WebSphere transaction server name. |
72 |
48 |
SM120WAC |
8 |
EBCDIC |
The WebSphere transaction server instance name. |
80 |
50 |
SM120WAD |
8 |
HEX |
The
WLM enclave token. |
88 |
58 |
SM120WAE |
20 |
HEX |
The
identity of the activity. |
108 |
6C |
SM120WAF |
16 |
S390STCK |
The
time the activity began in the server. |
124 |
7C |
SM120WAG |
16 |
S390STCK |
The
time the activity ended. |
140 |
8C |
SM120CL4 |
8 |
EBCDIC |
Cell |
148 |
94 |
SM120ND4 |
8 |
EBCDIC |
Node |
|
HttpSessionManager section
Table 2. HttpSessionManager section. There is one section
per record. The HttpSessionManager section contains information about
all (there may be zero or one) http sessions associated to one single
activity.
Offset |
Offset |
Name |
Length |
Format |
Description |
0 |
0 |
SM120WAH |
4 |
binary |
"created
Sessions": Number of http sessions that were created. |
4 |
4 |
SM120WAI |
4 |
binary |
"invalidatedSessions":
Number of http session that were invalidated. |
8 |
8 |
SM120WAJ |
4 |
binary |
"activeSessions":
Number of http sessions that were referenced during this activity. |
12 |
C |
SM120WAK |
4 |
binary |
"sessionLifeTime":
lifetime of the session in milliseconds. If "invalidatedSessions" >
0, this is the average lifetime (in milliseconds) of the invalidated
http session. |
|
WebApplication section
Table 3. WebApplication section. There are multiple (0-n)
sections per record. The WebApplication section contains information
about all WebApplications involved in this activity.
Offset |
Offset |
Name |
Length |
Format |
Description |
0 |
0 |
SM120WAL |
256 |
Unicode |
The
name of the WebApplication. |
256 |
100 |
SM120WAM |
4 |
binary |
Number
of servlet triplets in this web application section. |
The following triplet appears 0-n times, once for
each servlet section. |
260 |
104 |
SM120WAN |
4 |
binary |
Offset
to servlet section from the beginning of this WebApplication section. |
264 |
108 |
SM120WAO |
4 |
binary |
Length
of servlet section. |
268 |
10C |
SM120WAP |
4 |
binary |
Number
of servlet sections. |
|
Servlet activity section
Table 4. Servlet activity section. There are multiple (0-n)
sections per WebApplication section. The Servlet activity section
contains information about each servlet associated with WebApplications
involved in this activity.
Offset |
Offset |
Name |
Length |
Format |
Description |
0 |
0 |
SM120WAQ |
256 |
Unicode |
The
name of the servlet. |
256 |
100 |
SM120WAR |
4 |
binary |
"responseTime":
Response time in milliseconds. |
260 |
104 |
SM120WAS |
4 |
binary |
"numErrors":
The number of errors that were encountered during the servlet execution. |
264 |
108 |
SM120WAT |
4 |
binary |
"loaded": 0: The servlet did not have to be loaded as
a result of this request.
1: The servlet had to be loaded
as the result of this request.
|
268 |
10C |
SM120WAU |
16 |
EBCDIC |
"loadedSince":
Timestamp from System.currentTimeMillis() when the servlet was loaded,
in HEX format. Sample: The data as
it appears in the record has the format e7ef7c577c
, which
needs to be converted to a Java long: 996155348860
.
The Java long digits can be converted to java.util.Date: Thu Jul 26 15:49:08 GMT+02:00 2001
|
284 |
11C |
SM120CPU |
8 |
binary |
Cpu
time in microseconds. |
|