Fix (APAR):  PK31186

Status:  Fix

Release:  6.0.2.13,6.0.2.11

Operating System:  Linux

Supersedes Fixes:  

CMVC Defect:  xxxxxx

Byte size of APAR:  49669

Date: 2006-10-17

Abstract:  If variables.xml is missing from the repository, ODC throws exceptions.

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

ERROR DESCRIPTION:                                              
ODC throws Exceptions if variable.xml is missing from various   
levels in the config repository.                                
                                                                
Getting the error message below from trace:                     
                                                                
[9/11/06 7:16:34:479 CDT] 0000000a TreeBuilder   W   ODCF0002E: 
Exception:                                                      
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/POC_Ce
ll/nodes/webnode/variables.xml (No such file or directory).     
[9/11/06 7:16:34:523 CDT] 0000000a TreeBuilder   3              
getServerNode                                                   
                                 java.io.FileNotFoundException: 
/opt/IBM/WebSphere/AppServer/profiles/Dmgr01/config/cells/POC_Ce
ll/nodes/webnode/variables.xml (No such file or directory)      
 at java.io.FileInputStream.open(Native Method)                 
 at java.io.FileInputStream.<init>(FileInputStream.java:129)    
 at                                                             
org.eclipse.emf.ecore.resource.impl.URIConverterImpl.createFileI
nputStream(URIConverterImpl.java:423)                           
                                                                

LOCAL FIX:                                                      
No work around for this issue.                                  

PROBLEM SUMMARY

USERS AFFECTED:
All users of WebSphere Application Server
version 6.0.2.11 and above.

PROBLEM DESCRIPTION:
If variables.xml is missing from the
repository, ODC throws exceptions.

RECOMMENDATION:
None

If variables.xml is missing from the repository, ODC throws
exceptions. The code was assuming that variables.xml would be
present and was issuing a "ConfigRoot.getResource
("variables.xml"). This was throwing a FileNotFound exception.
This is done several times while dealing with variable maps.
The exception was not caught and it caused ODC to abort
Transactions.

PROBLEM CONCLUSION:                                             
The call to ConfigRoot.getResource was placed inside a          
try-catch block so that exceptions thrown during reading        
the variable maps will not cause problems.                      
                                                                
The fix for this APAR is currently targeted for inclusion       
in fixpack 6.0.2.17.                                            
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:  
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: