PQ55155: DOCUMENTATION REQUIRED TO CLARIFY INCORRECT CONFIGURATION REQUIREMENTS FOR THE DMZ, HTTP SERVER, PLUGIN AND WEBSPHERE

APAR status
Closed as documentation error.

Error description
The documentation in two of the WebSphere for z/OS and OS/390
publications incorrectly reflects the configuration requirements
for the DMZ, HTTP server, plugin and WebSphere.  The
documentation is incorrect in V400 and V401 publications.  In
the "Getting Started with WebSphere Application Server" book,
the documented configuration does not apply for WebSphere for
z/OS and OS/390 and it should either be clarified what the
correct setup for z/OS and OS/390 should be or the book itself
should be removed from the zOS and OS/390 library since it
contains other information that is incorrect for z/OS and OS390.
The "Assembling J2EE Applications" book, contains information on
setting up the HTTP server with WAS for z/OS and OS/390 but
does not mention the requirement that the HTTP server must
reside on the same system that has a WAS Daemon instance running
on it.  It is more important to get the information correct in
the books specific to WebSphere Application Server for z/OS and
OS/390, such as "Assembling J2EE Applications" and "Installation
and Customization".  A suggested correction could be:
"In order for web applications to be invoked, you must either
1) configure the HTTP Transport Handler in the J2EE Servers
   containing the web applications or
2) install and configure one or more HTTP servers containing
   the WebSphere Plug-In within the same Sysplex as the J2EE
   Servers containing the installed web applications.  An
   instance of a WebSphere Application Server Daemon (the proc
   is called BBODMN in the shipped sample procs) must be active
   on each system in the Sysplex where an HTTP server is
   installed in order for it to communicate with the J2EE
   Servers."
Local fix Problem summary
****************************************************************
* USERS AFFECTED: All users of WebSphere Application Server    *
*                 V4.0.1 for z/OS and OS/390                   *
****************************************************************
* PROBLEM DESCRIPTION: The documentation in two of the         *
*                      WebSphere for z/OS and OS/390           *
*                      publications incorrectly reflects the   *
*                      configuration requirements for the      *
*                      DMZ, HTTP server, V3.5 run-time         *
*                      environment (also known as the plug-in),*
*                      and WebSphere for z/OS.                 *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
Documentation is required to clarify incorrect
configuration requirements for the DMZ, HTTP SERVER, V3.5
run-time environment (also known as the plug-in), and WebSphere
for z/OS.

The documentation in two of the WebSphere for z/OS publications
incorrectly reflects the configuration requirements
for the DMZ, HTTP server, V3.5 run-time environment, and
WebSphere for z/OS. "Getting Started with WebSphere Application
Server" does not document the correct configuration for
WebSphere for z/OS. "Assembling J2EE Applications contains
information on setting up the HTTP server with WebSphere for
z/OS, but does not mention the requirement that the HTTP server
must reside on the same system that has a WebSphere Daemon
instance running on it.
Problem conclusion
New sections in Installation and Customization and Assembling
J2EE Applications were added in the current editions of these
manuals. The sections explain the HTTP Transport Handler
and the V3.5 run-time environment (aka plug-in).

A new rule is added for the WebSphere V3.5 run-time environment:

Rule: For HTTP Servers to communicate with the J2EE servers, an
instance of the WebSphere for z/OS Daemon (whose default start
procedure is BBODMN) must be active on each system in the
sysplex where an HTTP Server is installed.

In addition, "Getting Started with WebSphere Application Server"
has been removed from the WebSphere for z/OS library.
Temporary fix Comments
APAR information
APAR number PQ55155
Reported component name WASKBASE
Reported component ID 5655A9801
Reported release 401
Status CLOSED DOC
PE NoPE
HIPER NoHIPER
Submitted date 2001-11-23
Closed date 2002-05-06
Last modified date 2002-05-07

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


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 #: PQ55155
IBM Group: Software Group
Modified date: May 7, 2002