Fix (APAR):  PK59859

Status:  Fix

Release:  6.1.0.15,6.1.0.13,6.0.2.25,6.0.2.23

Operating System:  AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows

Supersedes Fixes:  

CMVC Defect:  PK59859

Byte size of APAR:  45717

Date: 2008-02-01

Abstract:  Start request to the IBM HTTP Server on an unmanaged node, from the WebSphere Application Server Administrative server console fails  due to a null  hostname and port for the IBM A

Description/symptom of problem:  
PK59859 resolves the following problem:

ERROR DESCRIPTION:                                              
Web server start request from the WebSphere Administration      
console  fails. The  Web Server is defined to an unmanaged node 
and administer through the IBM Administration Server. The trace 
indicates that the Administration Server hostname and port are  
null.  This lead to SERVERNOTAVAILABLE exception in the         
Websphere traces. The Administration Server error log           
(admin_error.log) will not show activity because the request was
never sent to the IBM Administration Server.                    

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
IBM WebSphere Application Server V6.1 and
V6.0 Administrative console  users who
Administer the IBM HTTP Server on an
unmanaged node.

PROBLEM DESCRIPTION:
Start request to the IBM HTTP Server
on an unmanaged node, from the
WebSphere Application Server
Administrative server console
fails  due to a null  hostname and
port for the IBM Administration Server.

RECOMMENDATION:
None

Start request to the IBM HTTP Server on an unmanaged node,
from the WebSphere Application Server Administrative server
console fails  due to a null  hostname and port for the IBM
Administration Server. The IBM HTTP Server is defined on an
unanaged node and the WEBSERVER_ADMIN_ADDRESS in the
serverindex.xml is not assigned to the serverControl object
for the IBM HTTP Server. The request to administer the IBM
HTTP Server through the IBM Administration Server are never
send because the IBM Administration Server endpoints are not
asigned for the Mbean Start.

PROBLEM CONCLUSION:                                             
Code changed in Web server serverControl to insure that the     
IBM Administration Server endpoint is assigned to the           
serverControl Object.                                           
                                                                
This APAR fix is currently targeted for fix packs 6.0.2.27 and  
6.1.0.17.                                                       
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   
                                                                
An iFIX is available for 6.1.0.13                               


Directions to apply fix:  
NOTE: Choose the:
1) Release the fix applies to
2) The Editions that apply
3) Delete the Editions & Methods that do not apply and this Note

Fix applies to Editions:
Release 6.0
__ Application Server (Express or BASE)
__ Network Deployment (ND)
__ WebSphere Business Integration Server Foundation (WBISF)
__ Edge Components
__ Developer
__ Extended Deployment (XD)

Install Fix to:
Method:
__ Application Server Nodes
__ Deployment Manager Nodes
__ Both

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Logged in with the same authority level when unpacking a fix, fix pack or refresh pack.
* Be at V6.0.2.2 or newer of the Update Installer. This can be checked by reviewing the level of the Update Installer in file <was_root>/updateinstaller/version.txt.

The Update Installer can be downloaded from the following link:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991

For detailed instructions to Extract the Update Installer see the following Technote:
http://www-1.ibm.com/support/docview.wss?rs=180&uid=swg21205400

1) Copy PKxxxxx.pak file directly to the maintenance directory

2) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that maintenance is being applied to.

3) Launch Update Installer

4) Enter the installation location of the WebSphere product you want to update.

5) Select the "Install maintenance package" operation.

6) Enter the file name of the maintenance package to install (PKxxxxx.pak file which was copied in the maintenance directory).

7) Install the maintenance package.

8) Restart WebSphere







Directions to remove fix:  
NOTE:
* The user must have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* FIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED
* DO NOT REMOVE A FIX UNLESS ALL FIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED
* YOU MAY REAPPLY ANY REMOVED FIX

Example: If your system has fix1, fix2, and fix3 applied in that order and fix2 is to be removed, fix3 must be removed first, fix2 removed, and fix3 re-applied.

1) Shutdown WebSphere
Manually execute setupCmdLine.bat in Windows or . ./setupCmdLine.sh in Unix from the WebSphere instance that uninstall is being run against.

2) Start Update Installer

3) Enter the installation location of the WebSphere product you want to remove the fix.

4) Select  "Uninstall maintenance package" operation.

5) Enter the file name of the maintenance package to uninstall (PKxxxxx.pak).

6) UnInstall maintenance package.

7) Restart WebSphere







Directions to re-apply fix:  
1) Shutdown WebSphere.

2) Follow the Fix instructions to apply the fix.

3) Restart WebSphere.









Additional Information: