Fix (APAR): PK76488 Status: Fix Release: 6.1.0.21 Operating System: Windows Supersedes Fixes: CMVC Defect: 566137 Byte size of APAR: 33769 Date: 2008-12-09 Abstract: The ConfigEventServiceDerbyDB administrative task fails when the WebSphere Aapplication Server install path has NLSs characters. Description/symptom of problem: PK76488 resolves the following problem: ERROR DESCRIPTION:? Common Event Infrastructure (CEI) is not able to handle NLS characters in the path for Derby. WASX7357I: ????????????????????????????????????????????? WASX7015E: ???????????$AdminTask configEventServiceDerbyDB { -nodeName IBM-D8B39FCCC9FNode01 -serverName server1 -createDB true -dbName EVENT -overrideDataSource false -outputScriptDir {C:??W62profilesProcSrv01dbscriptsCEI_EVENT}}??????? com.ibm.bsf.BSFException: error while eval'ing Jacl expression: com.ibm.ws.scripting.ScriptingException: com.ibm.events.install.db.DBConfigException: com.ibm.events.install.db.DBConfigException: CEIIN0721E ??????????? Derby ???????? The system cannot find the path specified. The java class is not found: org.apache.derby.tools.ij LOCAL FIX:? PROBLEM SUMMARY:? USERS AFFECTED: All users of WebSphere Application Server V6.1 and V7.0 that have NLS characters in the Application Server install path and are trying to configure Common Event Infrastructure (CEI). PROBLEM DESCRIPTION: The ConfigEventServiceDerbyDB administrative task fails when the WebSphere Aapplication Server install path has NLSs characters. RECOMMENDATION: None The ConfigEventServiceDerbyDB administrative task fails when the WebSphere Aapplication Server install path has NLSs characters. $AdminTask configEventServiceDerbyDB fails with the following error when the WesbSphere Application Server install path contains NLS characters: com.ibm.bsf.BSFException: error while eval'ing Jacl expression: com.ibm.ws.scripting.ScriptingException : com.ibm.events.install.db.DBConfigException: com.ibm.events.install.db.DBConfigException: CEIIN0721E ??????????? Derby ???????? The system cannot find the path specified. The java class is not found: org.apache.derby.tools.ij The problem is related to the character encoding, as CEI uses the standard cp1252 and for the machine with NLS characters cp 936 is used. When converting to 1252 the NLS characters are not recognized and this is causing the errors. PROBLEM CONCLUSION:? The character encoding should remain cp936 in order for the nls characters to be recognized during CEI configuration. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.23 and 7.0.0.3. 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.1.0.13 or newer of the Update Installer. Certain iFixes may require a newer version of the Update Installer and the Update Installer will inform you during the installation process if a newer version is required. This can be checked by reviewing the level of the Update Installer in file /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.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: