Fix (APAR): PK59791 Status: Fix Release: 6.1.0.13 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 15982 Date: 2008-06-03 Abstract: CMS Keystore (plugin-key.kdb) will not be created upon creating a w eb server. Description/symptom of problem: PK59791 resolves the following problem: ERROR DESCRIPTION: While creating a new webserver, there is an exception during the creation of the CMS keystore which will be seen in ffdc or trace on the dmgr. In the trace.log with Trace String: *=info:SSL=all:com.ibm.ws.security.*=all set on the dmgr shows the following ================================================================ 0000006c CreateCMSKeyS 3 Exception creating CMS keystore. java.lang.IllegalArgumentException: The given LoadStoreParameter is not recognized at com.ibm.security.cmskeystore.CMSKeyStoreSpi.engineStore(CMSKeySt oreSpi.java:1555) at java.security.KeyStore.store(KeyStore.java:1137) at com.ibm.ws.ssl.commands.keyStores.CreateCMSKeyStore.checkIfCMSKe yStoreExistsAndCreateIfNot(CreateCMSKeyStore.java:853) ================================================================ Also, customer may experience the following in the console, manage keys and certificates button sends customer to incorrect location in the console: Customer would go to: Web Servers->webserver1->Plug-in properties->Manage Keys and Certificates And it would take them back to Web Servers->webserver1 This is because the plugin-key.kdb does not exist yet, after applying this APAR, removing the WebServer, and re-creating the web server, this will work properly. LOCAL FIX: None PROBLEM SUMMARY USERS AFFECTED: WebSphere Application Server version 6.1 users wh o are using Web Server Plugin. PROBLEM DESCRIPTION: CMS Keystore (plugin-key.kdb) will not be created upon creating a w eb server. RECOMMENDATION: None Due to improper method usage while generating a CMS keystore, WebSphere Application Server fails to store a newly created CMS keystore. PROBLEM CONCLUSION: With this fix, method usage error is corrected. The fix for this APAR is currently targeted for inclusion in fix pack 6.1.0.15. 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.1 _X_ Application Server (Express or BASE) _X_ 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 _X_ 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 /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: