This section includes Subtype 8: WebContainer interval record (Version 2)
The purpose of the WebContainer interval SMF record is to record activity within a WebContainer running inside a WebSphere Application Server for z/OS transaction server.
The Web container execution environment consists of an EJB that is deployed into the EJB container. The WebContainer acts as a Web Server handling HttpSessions and Servlets. The EJB container is not aware of the purpose of the WebContainer activity record and only records that the EJB has been dispatched, but does not gather any of the detailed information, such as HttpSessions, Servlets, and their respective performance data. A single WebContainer record is created for each Web container.
In addition to data that is associated with an individual activity, there are some cases of Web container work that are performed outside the scope of an individual request. For example, some instances of http session finalization and http session invalidation are performed asynchronously. In such a case a WebContainer interval record would record this data
WebContainer SMF recording is activated and deactivated along with the activation and deactivation of SMF recording for the J2EE container.
WebContainer interval record (Version 2) schema
WebContainer interval record (Version 2) schema.WebContainer interval section
There is one section per record. The WebContainer interval section contains information about each activity that occurred within one WebContainer record.
Offset (decimal) | Offset (hexadecimal) | Name | Length | Format | Description |
0 | 0 | SM120WIA | 64 | EBCDIC | The WebSphere transaction server host name. |
64 | 40 | SM120WIB | 8 | EBCDIC | The WebSphere transaction server name. |
72 | 48 | SM120WIC | 8 | EBCDIC | The WebSphere transaction server instance name. |
80 | 50 | SM120WID | 16 | S390STCK | The time the sample began. |
96 | 60 | SM120WIE | 16 | S390STCK | The time the sample ended. |
112 | 70 | SM120CL5 | 8 | EBCDIC | Cell |
120 | 78 | SM120ND5 | 8 | EBCDIC | Node |
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 | SM120WIF | 4 | binary | "createdSessions": Number of http sessions that were created. |
4 | 4 | SM120WIG | 4 | binary | "invalidatedSessions": Number of http sessions that were invalidated. |
8 | 8 | SM120WIH | 4 | binary | "activeSessions": Current number of http sessions that are actively referenced in the server at the end of the interval. |
12 | C | SM120WII | 4 | binary | "minActiveSessions": Minimum number of active http sessions during the interval.. |
16 | 10 | SM120WIJ | 4 | binary | "maxActiveSessions": Maximum number of active http sessions during the interval. |
20 | 14 | SM120WIK | 4 | binary | "sessionLifeTime": Average lifetime (in milliseconds) of invalidated http sessions. |
24 | 18 | SM120WIL | 4 | binary | "sessionInvalidateTime": Average time (in milliseconds) that was required to process the invalidation of http sessions. |
28 | 1C | SM120WIM | 4 | binary | "finalizedSessions": Number of sessions that were finalized. |
32 | 20 | SM120WIN | 4 | binary | "liveSessions": Total number of http sessions being tracked by the server at the end of the interval. This includes both active and inactive sessions. |
36 | 24 | SM120WIO | 4 | binary | "minLiveSessions": Minimum number of live http sessions during the interval. |
40 | 28 | SM120WIP | 4 | binary | "maxLiveSessions": Maximum number of live http sessions during the interval. |
WebApplication interval section
There are multiple (0-n) sections per record. The WebApplication interval section contains information about all WebApplications involved in this activity.
Offset | Offset | Name | Length | Format | Description |
0 | 0 | SM120WIQ | 256 | Unicode | The WebApplication name. |
256 | 100 | SM120WIR | 4 | binary | "numLoadedServlets":
Number of servlets that were loaded. Note: This value might differ from the number of servlet sections in this record since servlets might exist that have been inactive during the interval. |
260 | 104 | SM120WIS | 4 | binary | Number of servlet triplets in this web application section. |
The following triplet appears 0-n times, once for each servlet section. | |||||
264 | 108 | SM120WIT | 4 | binary | Offset to servlet section from the beginning of this WebApplication section. |
268 | 10C | SM120WIU | 4 | binary | Length of the servlet section. |
272 | 110 | SM120WIV | 4 | binary | Number of servlet section. |
Servlet section
There are multiple (0-n) sections per WebApplication section. The Servlet activity section contains information about all servlets involved per WebApplication in this activity.
Offset | Offset | Name | Length | Format | Description |
0 | 0 | SM120WIW | 256 | Unicode | The servlet name. |
256 | 100 | SM120WIX | 4 | binary | "totalRequests": Number of times the servlet service was requested during the interval. |
260 | 104 | SM120WIY | 4 | binary | "responseTime": Average response time in milliseconds. |
264 | 108 | SM120WIZ | 4 | binary | "minResponseTime": Minimum response time in milliseconds. |
268 | 10C | SM120WJ1 | 4 | binary | "maxResponseTime": Maximum response time in milliseconds. |
272 | 110 | SM120WJ2 | 4 | binary | "numErrors": The number of errors that were encountered during servlet execution. |
276 | 114 | SM120WJ3 | 16 | EBCDIC | "loadedSince":
Timestamp when the servlet was loaded. Sample: Fri May 25 08:42:25 EDT 2001 |
292 | 124 | SM120WJ4 | 8 | binary | Average cpu time in microseconds. |
300 | 12C | SM120WJ5 | 8 | binary | Minimum cpu time in microseconds. |
308 | 134 | SM120WJ6 | 8 | binary | Maximum cpu time in microseconds. |