Fix (APAR): JR25589 Status: Fix Release: 6.0.1.4,6.0.1.3 Operating System: AIX,HP-UX,Linux,Solaris,Windows Supersedes Fixes: CMVC Defect: xxxxxx Byte size of APAR: 8929178 Date: 2007-02-22 Abstract: This interim fix delivers the latest version of the CEI driver for WebSphere Process Server: CEI 6.0.0.8. Description/symptom of problem: JR25589 resolves the following problem: ERROR DESCRIPTION: L2 Engineer: GBH L3 Engineer: FC Environment: CEI v6.0 Problem Description: Cannot override the database schema on zOS without changing the authentication alias. This would require additional RACF setup work that will not be allowed by all customers. DB2 JCC provider allows for specifying a currentSQLID on the datasource customeproperties to override the schema qualifier that CEI is using. Currently all other WPS components provide a vehicle for specifying the Schema Qualifier that does not require RACF userids. If you define a user USER1 in WPS, you can can access with a SQL statement to the schema DB2ADMIN. In the custom porperties of the datasource, the current schema can be set to DB2ADMIN. But when using the CBE Browser, the SQL statement used is incorrect (as seen in the logs), because the connection does not use the current schema but it looks for a connection to USER1.TABLE... (-204) CEI shouldn't assume the user is automatically identical to the schemaname. LOCAL FIX: N/A PROBLEM SUMMARY USERS AFFECTED: WebSphere Process Server users. PROBLEM DESCRIPTION: This interim fix delivers the latest version of the CEI driver for WebSphere Process Server: CEI 6.0.0.8. RECOMMENDATION: None This interim fix packages the latest CEI driver version 6.0.0.8 along with WPS. This CEI driver fixes a number of problems reported by users such as: CEI does not honor a schema name value for storing the events, CEI application needs to be rebooted to fix certain problems etc. A complete list of the problems fixed can be found in the CEI readme file. This is the list of defects fixed in this version of CEI: - Defect aixnm 161260 - Change the version to CEI 6.0.0.8 - Defect aixnm IY92173 - THE DEPLOYMENT OF EVENTSERVICEMDB (CEI) FAILS IN A CLUSTER - Defect aixnm IY92170 - CEI INSTALLATION COMPLETES PROPERLY EVEN IF THE DATABASE HAS NOT BEEN CREATED - Defect aixnm IY92899 - CEI DOES NOT HONOR SCHEMA SETTING FOR AUTHENTICATION. IT ASSUMESTHE DB2 USERID IS THE SAME AS THE SCHEMA NAME FOR THE CEI DB - Defect aixnm IY90306 - PROBLEM WITH CEI INSTALLER UPDATING THE DMGR WHEN INSTALLED INTOA CLUSTER PROBLEM CONCLUSION: Apply the ifix according to the instructions provided. Directions to apply fix: Before applying the iFix ensure that WebSphere Process Server 6.0.1 is installed on the system. Also download and follow Update Installer installation instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 1) Copy the pak file to the directory maintenance in the UpdateInstaller directory 2) Shutdown WebSphere Process Server. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 3) Run the UpdateInstaller and follow the prompts. 4) Restart WebSphere There are specific instructions that need to be followed after applying this ifix on your system so that the CEI driver is truly updated, and the EJB applications delivered by CEI are also updated. These instructions are listed below: 0) Stop the running WPS server if it is a standalone server or stop the cluster and the DMgr if it is a ND setup. Also stop the node agents. 0a) If this is a standalone server, then run stopserver server1. 0b) If this is a network deployment environment, then stop the Deployment Manager, Node Agent(s), clusters(s) and/or servers. 1) Install the Interim fix ------------------------ 1a) Copy the file 6.0.2.0-WS-WBI-IFJR25889.pak to $WPS_HOME/updateinstaller/maintenance directory. 1b) Now launch the UpdateInstaller by clicking on the update.exe program or by double clicking on the recently copied PAT file. 1c) Follow the prompts and install the test fix. At the end of the install action, the CEI driver should be updated in $WPS_HOME/CEI directory. The updated version information is in the file $WPS_HOME/CEI/properties/version/event-build.level file and the correct value is: CMVC_LEVEL=200701171347. 2) Augmenting the profile for CEI ---------------------------------- 2a) Locate the augmentcei.bat(.sh) and cei_augment.rsp files under $WPS_HOME/_uninstwbi/ceiInstall/ceiiinstallsample. 2b) Copy these two files to $WPS_HOME/CEI directory. 2c)Now edit the cei_augment.rsp file to have correct values for the following: PRODUCT_ID which should be "WebSphere Process Server" and WAS_HOME to be the directory where WPS is installed - for example: C:\IBM\WPS602 and finally PROFILE_PATH to point to the directory where the profile is created. For example, set PROFILE_PATH=C:\IBM\WPS602\profiles\ProcSrv602 Augmentation is done on a per-profile basis. So step 2 must be run for each profile where CEI has been setup. 2d) Now edit the cei_augment.bat(.sh) file to ensure that classpath entry is correct for cei_installer.jar which resides under $WPS_HOME/CEI/installer. For example: "%JAVA_HOME%\jre\bin\java" -Djava.util.logging.config.file=.\installer\logging.properties -cp .\installer\cei_installer.jar com.ibm.events.install.impl.CeiInstaller -r .\cei_augment.rsp where -cp option sets the classpath and the augmentcei.bat(.sh) script resides in $WPS_HOME/CEI directory. 2e) Now open up a command prompt or a shell and change driectory to $WPS_HOME/CEI. Run the augmentcei.bat(.sh) script from this directory. Note: 1) step 2 must be repeated for all the profiles for which CEI has been setup. 2) IMPORTANT: Do not deploy the CEI Event Server Application at this point. make sure DEPLOY_EJB=false is set in the cei_augment.rsp file. 3) Installing the eventserver.ear application and eventservermdb.ear application --------------------------------------------------------------------------------- 3a) Start the WPS server for the profile that has been setup for CEI. If it is a Network Deployment, start the DMgr for the cluster and the node agents. 3b) From the admin console of the server or the Dmgr, uninstall the following applications: EventServer.ear EventServerMDB.ear 3c)Install the eventserver.ear application first. You may choose to install the EventServer Application via the admin console if necessary resources exist, or you can install it using the script provided with the CEI driver. 3d) If you wish to install the applications using the admin console, then the new ear file to be installed can be found at: $PROFILE_HOME/event/application/event-application.ear. 3e) If installing the EventServer application using the script provided, you need to follow this step. Otherwise, go to step 3g. Open up a shell or a command prompt and change directory to $WPS_HOME/profiles//event/application 3f)execute the following script from this directory: event-application.jacl as follows: Execute the following command $WPS_HOME/profiles//bin/wsadmin [-conntype none] -profile event-profile.jacl -f event-application.jacl -action install -earfile event-application.ear -backendid [CLOUDSCAPE_V51_1|DB2UDBNT_V82_1|DB2UDBNT_V8_1|ORACLE_V10_1|ORACLE_V9_1|DB2UDBOS390_V8_1|DB2UDBOS390_V7_1|INFORMIX_V94_1|MSSQLSERVER_V7_1|SYBASE_V125_1] -node -server [-cluster ] [-trace] If installing on a cluster specify the cluster option and the name of the cluster. If installing on a server, specify the -server option and the name of the server. 3g) This step will install the EventServerMDB.ear application. Once again, you can install the EventServerMDB.ear application using the admin console or the script provided. To use the admin console, you must have the necessary resources like the messaging queue, queue connection factory etc. already setup. If these are the default values from a previous install, you can still use the admin console to install the EventServerMDB.ear application. 3h) To install using the admin console, locate the updated ear file at $PROFILE_HOME/event/application/event-message.ear. If you have used the default ActivationSpecification for setting up the CEI MDB goto step 3i else goto step 3j. 3i) Default setup: execute the following command: $WPS_HOME/profiles//bin/wsadmin [-conntype none] -profile event-profile.jacl -f default-event-message.jacl -action install -earfile event-message.ear -backendid [CLOUDSCAPE_V51_1|DB2UDBNT_V82_1|DB2UDBNT_V8_1|ORACLE_V10_1|ORACLE_V9_1|DB2UDBOS390_V8_1|DB2UDBOS390_V7_1|INFORMIX_V94_1|MSSQLSERVER_V7_1|SYBASE_V125_1] -node -server [-cluster ] [-trace] This will automatically create the needed resources for deployment on the server. The script will also prompt you for the userid and password for messaging authentication. 3j) If you have setup CEI using custom jndi names for the resources, execute the following command: $WPS_HOME/profiles//bin/wsadmin [-conntype none] -profile event-profile.jacl -f event-message.jacl -action install -earfile event-message.ear -backendid [CLOUDSCAPE_V51_1|DB2UDBNT_V82_1|DB2UDBNT_V8_1|ORACLE_V10_1|ORACLE_V9_1|DB2UDBOS390_V8_1|DB2UDBOS390_V7_1|INFORMIX_V94_1|MSSQLSERVER_V7_1|SYBASE_V125_1] -node -server [-cluster ] [-trace] -qjndi (jndi name for the JMS queue) -qcfjndi (jndi name of the queue connection factory) -listenerport (listener port jndi name) OR -activationspecjndi (jndi name of the actiovation spec for the MDB) Specify only one of ListenerPort or ActivationSpec, not both. The message driven bean in the EventServerMDB.ear application will use either a ListenerPort OR an ActivationSpec. Hence, specify only one of the two values. Now you can start both applications, namely EventServer.ear and EventServerMDB.ear from the admin console. Once this is done, the CEI driver update is complete. Directions to remove fix: NOTE: FIXES MUST BE REMOVED IN THE REVERSE ORDER IN WHICH 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, then fix2 may be removed 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Follow the Fix instructions that are packaged with the Fix Installer on how to uninstall and reinstall the Fix. 3) Restart WebSphere Directions to re-apply fix: 1) Shutdown WebSphere. It is important that you perform a controlled and complete shutdown of the server to ensure that all transactions have completed, before installing the fix. 2) Run the UpdateInstaller and follow the instructions. The Update Installer can be downloaded from the following link: http://www.ibm.com/support/docview.wss?rs=180&uid=swg21205991 3) Restart WebSphere Process Server Additional Information: