PQ65919: NEW FUNCTION

 A fix may be available

Obtain the fix for this APAR



APAR status
Closed as new function.

Error description
Apar to deliver functional enhancements to WebSphere Application
Server for z/OS and OS/390 V4.0.1
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
*                                                              *
****************************************************************
* PROBLEM DESCRIPTION: APAR PQ65919 introduces additional      *
*                      functionality in WebSphere Application  *
*                      Server V4.0.1 for z/OS and OS/390.      *
*                                                              *
*                                                              *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
The following new function is provided in APAR PQ65919:



Dynamic fragment caching
( 83195 83206 83465 83500 83501 83546 83704 83769 83770 83803 )

Description
A WebSphere for z/OS performance enhancement is the ability to
cache the output of dynamic servlets and JSP files. Working
within an application servers Java Virtual Machine (JVM), this
technology intercepts calls to a servlets service method, and
checks whether the invocation can be served from a cache.
Because J2EE applications have such high read-write ratios and
can tolerate a small degree of latency in the freshness of their
data, fragment caching creates an opportunity for significant
gains in server response time, throughput, and scalability, thus
improving overall performance.

WebSphere plug-ins for Web servers Support
( 83490 83608 )

Description
IBM WebSphere plug-ins for Web servers (also called Web server
plug-ins) are provided with the WebSphere for z/OS product. They
provide a means of redirecting servlet and JSP requests from a
Web server installed on a workstation to WebSphere for z/OS
where J2EE Web container functions are supported. Use of this
type of plug-in allows the HTTP Web server function to execute
on a separate platform, directing only those requests requiring
Web container services to the z/OS platform.

Maintaining session data in a DB2 database
( 83155 83558 )

Description
WebSphere Application Server for z/OS and OS/390 needs to
provide improved performance when storing HTTP session data
in DB2.  New function is needed to provide a session persistence
implementation that supports a DB2 table format and tuning
parameters similar to WebSphere Distributed.


Client Certificate support when using the HTTPS Transport
Handler ( 83190 83191 83678 )

Description
WebSphere Application Server for z/OS and OS/390 needs to
provide support for Client certificate support when using the
HTTPS Transport Handler.  Using SSL, WebSphere for z/OS
should allow users to:
- Set up and administer your own certificate authority (CA),
and administer your own certificates.
- Set up client authentication using client certificates
signed by an internal CA.  Using an internal CA to sign your
client certificates is independent of whether you used an
internal or external CA to sign your server certificate.
- Set up client authentication using a server certificate
signed by an external CA .
- Set up client authentication using client certificates that
are signed by an external CA.


Batch compiling of JSPs
(83167 83293 83442 83526 83720 83785 83830 83902 83926 83930 )

Description
WebSphere Application Server for z/OS and OS/390 needs to
provide a tool to batch compile JSP files.  This will allow
the J2EE servers response to the first request for a JSP file
to be much faster because the JSP is translated and compiled
into a servlet before any request is received. Batch compiling
is also useful as a fast way to resynchronize all of the
JSP files for an application.
Problem conclusion Temporary fix Comments
APAR PQ65919 provides the following new functional enhancements:

Dynamic fragment caching
( 83195 83206 83465 83500 83501 83546 83704 83769 83770 83803 )

Description
The Dynamic fragment caching support can be used to cache the
output of servlets and JSP files.  After a servlet is invoked
once (generating the output that will be cached), a cache
entry is created containing not only the output, but also side
effects of the invocation, such as calls to other servlets or
JSP files, as well as meta data about the entry including
timeout and entry priority information.  Unique entries are
distinguished by an ID string generated from the
HttpServletRequest object for each invocation of the servlet.
Servlet caching can then be based on:
- Request parameters and attributes
- The URI used to invoke the servlet
- Session information
- Other options, including cookies

WebSphere for z/OS also provides the Servlet Cache Monitor
application as a tool for verifying that your servlets and JSPs
are being properly cached.
This tool enables you to inspect the contents and behavior of
the fragment cache.

For more information please reference the following publications

WebSphere Application Server
V4.0.1 for z/OS and OS/390: Migration, GA22-7860

WebSphere Application Server V4.0.1 for z/OS and OS/390:
Installation and Customization,    GA22-7834

For more detailed information about the Dynamic Fragment Cache,
refer to WebSphere Application Server V4.0.1 for z/OS and OS/390
Assembling J2EE Applications,    SA22-7836


WebSphere plug-ins for Web servers Support
( 83490 83608 )

Description
IBM WebSphere plug-ins for Web servers (also called Web server
plug-ins) are provided with the WebSphere for z/OS product.
They provide a means of redirecting servlet and JSP requests
from a Web server installed on a workstation to WebSphere for
z/OS where J2EE Web container functions are supported. Use of
this type of plug-in allows the HTTP Web server function to
execute on a separate platform, directing only those requests
requiring Web container services to the z/OS platform.

The WebSphere plug-ins for Web servers shipped with the
WebSphere Application Server Advanced Edition Version 4.2 or
higher product can also be used with the WebSphere for z/OS
product. If you obtain a plug-in from the Advanced Edition
product, you do not have to perform any additional set-up of
the Advanced Edition product in order to use the plug-in and
Web server with WebSphere for z/OS. Just follow the set-up
instructions provided in WebSphere Application Server V4.0.1
for z/OS and OS/390: Assembling J2EE Applications

Once you are set up to use the WebSphere plug-ins for Web
servers, you can use private headers as a mechanism for
forwarding proxy information from these plug-ins to WebSphere
for z/OS. If private headers are not used, this information
cannot be included with the HTTP requests. The private headers
can include such information as the remote (client) user, the
remote (client) host name, or an SSL client certificate. Because
they conform to a naming standard, there is no namespace
collision with the architected HTTP header fields (hence the
name "private").

For more information please reference the WebSphere Application
Server V4.0.1 for z/OS and OS/390: Migration, GA22-7860

For more detailed information about using WebSphere plug-ins
for Web servers, refer to
WebSphere Application Server V4.0.1 for z/OS and OS/390:
Assembling J2EE Applications

Maintaining session data in a DB2 database
( 83155 83558 )

Description
HTTP Session in DB2 Performance Improvements have been included.
WebSphere for z/OS provides two versions of session persistence
for maintaining session data in a DB2 database.
- Version 1, which can be used with either:
The WebSphere for z/OS local redirector plug-in, working in
conjunction with a Web server installed on z/OS or OS/390
sysplex, or An HTTP(S) Transport Handler.

This version is provided for backward compatibility. It uses the
DB2 database, tablespace, and table definitions that were used
in V3.5, V4.0 and V4.0.1 prior to the availability of PTF
UQ90051 and UQ90052.

- Version 2 can only be used with an HTTP(S) Transport Handler
and with cookies enabled. It requires new DB2 session database,
tablespace, and table definitions.
It provides a number of new webcontainer.conf properties that
provide performance tuning options.
(See WebSphere Application Server V4.0.1 for z/OS and OS/390:
Assembling J2EE Applications for a description of these
definitions.)
(The name of the new table must be specified on the
webcontainer.conf session.dbtablename property.)

The primary benefit of using Version 2 is performance
improvements. IBM recommends using Version 2 whenever possible.

For more information please reference the WebSphere Application
Server V4.0.1 for z/OS and OS/390: Migration, GA22-7860

For more detailed information about using DB2 to maintain
session data, refer to
WebSphere Application Server V4.0.1 for z/OS and OS/390:
Assembling J2EE Applications


Client certificate support when using the HTTPS Transport
Handler ( 83190 83191 83678 )
The support for Client certificates when using the HTTPS
Transport Handler will be enabled via APAR 
PQ66445.
This APAR will be delivered in the PTF that immediately
follows Service Level 4.


Batch compiling of JSPs
(83167 83293 83442 83526 83720 83785 83830 83902 83926 83930 )

Description
As an IBM enhancement to JSP support, WebSphere for z/OS
provides a batch JSP compiler tool called the JspBatchCompiler
tool. Use this tool to batch compile your JSP files.
Batch compiling JSP files makes the J2EE servers response to
the first request for a JSP file much faster because the JSP is
translated and compiled into a servlet before any request is
received. Batch compiling is also useful as a fast way to
resynchronize all of the JSP files for an application.

For more information please reference the WebSphere Application
Server V4.0.1 for z/OS and OS/390: Migration, GA22-7860

For more detailed information about batch compiling JSPs,
refer to
WebSphere Application Server V4.0.1 for z/OS and OS/390:
Assembling J2EE Applications.

APAR PQ65919  is associated with SERVICE LEVEL W401400 of
WebSphere Application Server V4.0.1 for z/OS and OS/390.

The following COMPID is affected by these changes:
5655A9800 R401 on z/OS and OS/390.
APAR information
APAR number PQ65919
Reported component name WEBSPHERE OS/39
Reported component ID 5655A9800
Reported release 401
Status CLOSED UR1
PE NoPE
HIPER NoHIPER
Submitted date 2002-09-05
Closed date 2002-09-20
Last modified date 2002-10-02

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros
EJSJSO01 EJSJSO02 EJSJSO03 EJSJSO04 EJSJSO05 EJSJSO06
EJSJSO07 EJSJSO08 EJSJSO09 EJSJSO10 EJSJSO11 EJSJSTJA
EJSJSVJR EJSJWBJR EJSJWCSC EJSJWCWC EJSJWC01 EJSJWC02
EJSJWC03 EJSJWC04 EJSJWC05 EJSJWC06 EJSJWC08 EJSJWC09
EJSJWC10 EJSJWC11 EJSJWC12 EJSJWC13 EJSJWC14 EJSJWC15
EJSJWC16 EJSJWC17 EJSJWC18 EJSJWC19 EJSJWC20 EJSJWC21
EJSJWC22 EJSJWC23 EJSJWC24 EJSJWC25 EJSJWC26 EJSJWC27
EJSJWC28 EJSJWC29 EJSJWC30 EJSJWC31 EJSJWC32 EJSJXERC
EJSJXMJR EJSJ10JR EJSLNLS EJSPCNVT EJSPDEFG EJSPECDG
EJSPMEDA EJSPMIME EJSPMSGS EJSPMTYP EJSPPROD EJSPSAP0
EJSPSEAR EJSPWASC EJSPWCNF EJSPWEAR EJSPWSAM EJSSJB01
EJSSMI01 EJSSMI02 EJSSMI03 EJSSMI04 EJSSSO01 EJSSSO02
EJSSWARW EJSTLDAT EJSTWASC EJSWEXWA EJSXASIN EJSXCWAR
EJSXDC01 EJSXDC02 EJSXDEFS EJSXJVMX EJSXLWAP EJSXXMCF

Fix information
Fixed component name WEBSPHERE OS/39
Fixed component ID 5655A9800

Applicable component levels
R401 PSY UQ90052    UP02/09/27 P F209

  Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS
Operating system(s):
Software version: 401
Software edition:
Reference #: PQ65919
IBM Group: Software Group
Modified date: Oct 2, 2002