PK02800: WEBSPHERE APPLICATION SERVER VERSION 5 IHS390WAS50PLUGIN_HTTP NOT UPDATED IN WAS_HOME/BIN WITH APPLYPTF | ||||||||||||||||||||||||||||||||||||||||||||||||
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||
![]() APAR status Closed as program error. Error description Customer encounter issue with ihs390WAS50Plugin_http.so not being updated in the was_home/bin by applyptf. Information Center documentation states the file can be moved to customers HFS as required. Examples stated to use websphere_install_root/bin ....Local fix Problem summary **************************************************************** * USERS AFFECTED: All users of WebSphere Application Server * * V5.0 for z/OS * **************************************************************** * PROBLEM DESCRIPTION: The WebSphere HTTP Plugin for z/OS is * * not updated when PTF maintenance is * * applied. * **************************************************************** * RECOMMENDATION: * **************************************************************** The install process copies the WebSphere HTTP Plugin for z/OS to a WAS_HOME/bin directory. The SMP/E process of PTF maintenac applies the maintenance to the SMP/E install target point only. Therefore the copy at the WAS_HOME/bin directory does not get upgraded with the applied maintenance.Problem conclusion Changed the install process so that there is no copy of the WebSphere HTTP Plugin for z/OS to a WAS_HOME/bin directory. Thi APAR will erase any previously copied version of the WebSphere HTTP Plugin for z/OS from the WAS_HOME/bin directory and then set up a link between the SMPE target point ( install_root ) and the WAS_HOME/bin directory. This link will allow multiple locations/paths for the WebSphere HTTP Plugin for z/OS but will provide the needed single target point for both installation and maintenance. APAR PK02800 requires changes to documentation: The following publication was revised as a result of APAR PK02800: ________________________________________________________________ WebSphere Application Server V5.0 for z/OS Messages and Codes GA22-7915-00 _______________________________________________________________ This APAR requires changes to documentation. NOTE: Periodically, we refresh the documentation on our Web site, so the changes might have been made before you read this text. To access the latest on-line documentation, go to the product library page at: www.ibm.com/software/webservers/appserv/ To access the latest online documentation, go to the product library page at: http://www.ibm.com/software/webservers/appserv/was/library/ The changes are to the description of how to code the HTTP server ServerInit, ServerTerm, and Service directives for the HTTP Server for z/OS plug-in that is contained in the article "Installing the WebSphere HTTP Plug-in for z/OS". - Note "a," that are currently contained in Step 3, will be moved to the introduction to this task. - Note "b," that is currently contained in Step 3, will become the following step: 5. If any of your servlets sets an HTTP response code by any means, such as using methods lastModified() or setStatus(), and the client does not receive the expected response code, add the following directive to the HTTP Server configuration file: ServiceSync On - Note "c," that is currently contained in Step 3, will be merged into step 1. Step 1 will then read: 1. Make sure a Version 5.3 IBM HTTP Server for z/OS and OS/390 is installed on a z/OS or OS/390 system. If you want to use Secure-socket layer (SSL), make sure that the HTTP Server is configured for SSL. The SSL connection between the Web server plug-in and the J2EE server uses the SSL session established by the HTTP Server. (See z/OS HTTP Server Planning, Installing, and Using, Version 5.3, SC34-4826, for a description of how to configure the HTTP Server for SSL.) - Step 3 in this article will be broken into the following two steps: 3. Add ServerInit,, and ServerTerm directives to the httpd.conf configuration file of the HTTP Server to indicate the entry points to the plug-in's initialization and exit routines. These routines exist as entry points init_exit, and term_exit, respectively, within the ihs390WAS50Plugin_http.so DLL file. Example: The ServerInit directive is split here for printing purposes. In the actual httpd.conf file, enter this directive on a single line. ServerInit /http_plugin_dir/bin/ ihs390WAS50Plugin_http.so:init_exit/http_plugin_conf/ plugin-cfg.xml ServerTerm /http_plugin_dir/ ihs390WAS50Plugin_http.so:term_exit Specify the full path to where you put the plugin-cfg.xml file for the variable http_plugin_conf. The value you specify for the variable http_plugin_dir depends on whether or not the HTTP Server is on the same LPAR as the WebSphere Application Server. - If the HTTP Server is on the same LPAR as the WebSphere Application Server, specify the full path of the Application Server's install_root/bin/ directory. Important: If v5.0.2 APAR PK02800 or v5.1.0 APAR PK02801 is applied to the WebSphere Application Server for z/OS environment, the value for the http_plugin_dir must be set to WAS_HOME/bin/. - If the HTTP Server is not on the same LPAR as the WebSphere Application Server, specify the full path that you designated as the destination of the FTP operation in the previous step. Important: Whenever service is applied to the WebSphere Application Server for z/OS product, you must FTP a new copy of the WebSphere HTTP Plugin-in for z/OS from the install_root/bin directory to this directory on your HTTP Server system. 4. Add the following Service directive for each application that will be using the Web server plug-in. This directive indicates the entry point to the plug-in's request routine. The request routine exists as the entry point service_exit within the ihs390WAS50Plugin_http.so Dynamic Link Library (DLL) file. Example: The Service directive is split here for printing purposes. In the actual httpd.conf file, enter this directive on a single line. Service /webapp_contextroot/* /http_plugin_dir/ ihs390WAS50Plugin_http.so:service_exit Specify the application's context root for the variable webapp_contextroot. The value you specify for the variable http_plugin_dir depends on whether or not the HTTP Server is on the same LPAR as the WebSphere Application Server. - If the HTTP Server is on the same LPAR as the WebSphere Application Server, specify the full path of the Application Server's install_root/bin/ directory. Important: If v5.0.2 APAR PK02800 or v5.1.0 APAR PK02801 is applied to the WebSphere Application Server for z/OS environment, the value for the http_plugin_dir must be set to WAS_HOME/bin/. - If the HTTP Server is not on the same LPAR as the WebSphere Application Server, specify the full path that you designated as the destination of the FTP operation in the previous step. Important: Whenever service is applied to the WebSphere Application Server for z/OS product, you must FTP a new copy of the WebSphere HTTP Plugin-in for z/OS from the install_root/bin directory to this directory on your HTTP Server system. APAR PK02800 is associated with SERVICE LEVEL W502033 of WebSphere Application Server V5.0 for z/OS.Temporary fix Comments ž**** PE05/10/26 PTF IN ERROR. SEE APAR PK14144 FOR DESCRIPTION
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: PK02801 Modules/Macros
Publications Referenced
|
Document Information |
Current web document: swg1PK02800.html
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server for z/OS
Operating system(s):
Software version: 500
Software edition:
Reference #: PK02800
IBM Group: Software Group
Modified date: Nov 17, 2005
(C) Copyright IBM Corporation 2000, 2009. All Rights Reserved.