Fix (APAR): PK66657 Status: Fix Release: 6.1.0.17,6.1.0.15 Operating System: AIX,HP-UX,i5/OS,Linux,Linux pSeries,Linux zSeries,OS/400,Solaris,Windows Supersedes Fixes: CMVC Defect: 513228 Byte size of APAR: 51004 Date: 2008-05-30 Abstract: When configuring CEI with SQL Server 2005 the JDBC Provider supplies the wrong backendid. Description/symptom of problem: PK66657 resolves the following problem: ERROR DESCRIPTION: After creating the Deployment environment(not generate), and using the $AdminTask generateDeploymentEnv to generate the Deployment environment, following exception are seen: wsadmin>$AdminTask generateDeploymentEnv {-topologyName NDTop} WASX7015E: Exception running command: "$AdminTask generateDeploymentEnv {-topolo gyName NDTop}"; exception information: com.ibm.bsf.BSFException: error while eval'ing Jacl expression: com.ibm.ws.scripting.ScriptingException: com.ibm.wbiserver.nd.topology.exception s.WBINDException: com.ibm.wbiserver.nd.topology.exceptions.WBINDException: CWLDB 9016E: The generation for deployment environment NDTop failed. Reason: CWLDB9014 E: The configuration of component WBI_CEI failed. Reason java.lang.Exception: ja va.lang.Exception: com.ibm.events.install.db.DBConfigException: CEIIN0751E The c ommand found an existing Event Service SQLServer data source, which is not compa tible with the SQLServer database. To create the Event Service SQLServer data so urce, run the command again with the overrideDataSource parameter set to true... If in doubt, discard the changes and do not save the failed configuration to the master repository. while executing "$AdminTask generateDeploymentEnv {-topologyName NDTop}" Similar exceptions are seen from the admininstrative console as well. LOCAL FIX: PROBLEM SUMMARY USERS AFFECTED: Users who configure the Common Event Infrastructure (CEI) on Microsoft SQL Server 2005 database on a WebSphere Application Server or a WebSphere Process Server profile. PROBLEM DESCRIPTION: When configuring CEI with SQL Server 2005 the JDBC Provider supplies the wrong backendid. RECOMMENDATION: None CEI configuration fails on SQL Server 2005. The backendid received from the JDBC provider is set incorrectly to SQL Server 2000 which conflicts with the backendid of the database. PROBLEM CONCLUSION: The code has been modified to check the providerType attribute of the JDBC Provider for the SQL Server, and set the backendid correctly so it will coincide with the database backendid. The fix for this APAR is currently targeted for inclusion in fixpack 6.1.0.19. 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 /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: