Fix (APAR):  PK61584

Status:  Fix

Release:  6.1.0.17,6.1.0.15

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

Supersedes Fixes:  

CMVC Defect:  PK61584

Byte size of APAR:  34092

Date: 2008-06-16

Abstract:  Profile creation fails on AIX ppc32 in Turkish.

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

ERROR DESCRIPTION:                                              
Profile creation fails on AIX ppc32 in Turkish.                 
                                                                
This component owns some native code and a java library that    
expose an API to set file permissions from java. We use this    
API to set file permissions when app is expanded by the         
application save/sync logic at the end of deployment.           
                                                                
No workaround because this happens during our install/profile   
creation Phase                                                  

LOCAL FIX:                                                      
 No workaround because this happens during our install/profile  
creation Phase                                                  

PROBLEM SUMMARY

USERS AFFECTED:
 Users of WebSphere Application Server 6.1

PROBLEM DESCRIPTION:
Profile creation fails on AIX ppc32
in Turkish.

RECOMMENDATION:
None

This failure is due to problem in loading native library in
non-English locale.

This failure in turn leads to the unavailability of NativeFile
functionality that is needed for  DiskSpaceValidator for
profile creation.  As a result, the profile creation process
also fails.

In the PMT log, the following messages are recorded:

<record>
<date>2008-04-09T14:54:53</date>
<millis>1207767293136</millis>
<sequence>876</sequence>

<logger>com.ibm.ws.profile.validators.DiskSpaceValidator</logger
>
<level>SEVERE</level>

<class>com.ibm.ws.profile.validators.DiskSpaceValidator</class>
<method>runValidator</method>
<thread>10</thread>
<message>NativeFile functionality is not available</message>
</record>

PROBLEM CONCLUSION:                                             
Code changes made to ensure that the problem in loading         
native library is fixed, and it will get initialized properly.  
The fix for this APAR is currently targeted for inclusion in    
fixpack 6.1.0.21                                                
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: