Fix (APAR):  PK16221

Status:  Fix

Release:  5.1.1.7

Operating System:  AIX,HP-UX,Linux,Linux Red Hat - pSeries,Linux zSeries,OS/390,OS/400,Solaris,Windows,z/OS

Supersedes Fixes:  

CMVC Defect:  PK16221

Byte size of APAR:  13370

Date: 2006-03-13

Abstract:  Properties and schemas are missing four schemas; incorrect references to com.ibm.etools.jca.xsd; errors in java.xsd

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

ERROR DESCRIPTION:                                              
A number of schema files are missing from                       
"WAS_HOME/properties/schemas":                                  
    commonarchive.xsd                                           
    datatype.xsd                                                
    resources.jms.internalmessaging.xsd                         
    resources.jms.mqseries.xsd                                  
Three schema files contain references to                        
"com.ibm.etools.jca.xsd", (should be "jca.xsd"):                
    commonarchive.xsd                                           
    j2cbnd.xsd                                                  
    resources.j2c.xsd                                           
The single schema file java.xsd contains occurrances of         
"Boolean" as a type which should instead be occurrances of      
"boolean".  (The change is from an upper case "B" to a          
lower case "b".)                                                
                                                                
Use of the provided schemas fails with FileNotFoundException    
because of the missing files, and because of the incorrect      
references.                                                     

LOCAL FIX:                                                      
none                                                            

PROBLEM SUMMARY

USERS AFFECTED:
Users of WebSphere Application Server
version 5.1, who are using properties or
schemas files to validate the structure of
configuration files.

PROBLEM DESCRIPTION:
Properties and schemas are missing
four schemas; incorrect references to
com.ibm.etools.jca.xsd; errors in
java.xsd

RECOMMENDATION:
None

A number of schema files are missing from
"WAS_HOME/properties/schemas":
commonarchive.xsd
datatype.xsd
resources.jms.internalmessaging.xsd
resources.jms.mqseries.xsd
Three schema files contain references to
"com.ibm.etools.jca.xsd", (should be "jca.xsd"):
commonarchive.xsd
j2cbnd.xsd
resources.j2c.xsd
The single schema file java.xsd contains occurrances of
"Boolean" as a type which should instead be occurrances of
"boolean".  (The change is from an upper case "B" to a
lower case "b".)

Use of the provided schemas fails with FileNotFoundException
because of the missing files, and because of the incorrect
references.

PROBLEM CONCLUSION:                                             
Ifix PK16221.jar made available 12/20/2005                      
Update placed into the 5.1.1.10 service pack.                   
Please refer to the recommended updates page for delivery       
information:                                                    
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980   

Directions to apply fix:  Fix applies to Editions:
Release:
5.1
_X_ Application Server (Express or BASE)
_X_ Network Deployment (ND)

Install Fix to:
Method:
_X_ Application Server Nodes
_X_ Deployment Manager Nodes

NOTE:
The user must:
* Have Administrative rights in Windows, or be the Actual Root User in a UNIX environments.
* Be logged in with the same authority level when unpacking a fix, fix pack or refresh pack.

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

The Update Installer for V5.0 does not have a maintenance directory.
It uses fixpacks and fixes as the location of the unpacked files.

1) Copy PKxxxxx.jar 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.jar file which was copied in the maintenance directory).
The V5.0 and V5.1 fix packs and fixes are unpacked as .jar files and should be unpacked into fixpacks or fixes 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.jar).

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:  This fix also applies to 5.1.1.8