************************************************************************ Licensed Material - Property of IBM 5724-M24 (c) Copyright IBM Corp. 2006, 2007. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. ************************************************************************ ************************************************************************ Update WebSphere Business Monitor 6.0.2.1 to Interim Fix 5 level ************************************************************************ This file contains the following sections. A. General information B. Updating WebSphere Business Monitor Server on Windows C. Updating WebSphere Business Monitor Server on AIX D. Updating WebSphere Business Monitor Dashboard on Windows E. Updating WebSphere Business Monitor Dashboard on AIX F. Updating WebSphere Business Monitor Development Toolkit G. Updating WebSphere Business Monitor in a Network Deployment cell H. Activating Fixes for Existing Models ************************************************************************ A. General information ************************************************************************ If you are updating Monitor Development Toolkit, you can ignore the sections about updating Monitor Server and Dashboard. For customers planning to upgrade from WebSphere Business Monitor version 6.0.2.1 to version 6.1, it is STRONGLY RECOMMENDED that you apply Interim Fix 5 to your version 6.0.2.1 installation prior to upgrading to version 6.1. The following issues in WebSphere Business Monitor version 6.0.2.1 are resolved in Interim Fix 5: APAR JR27861 ------------ [Server] If an error occurs during processing of an event, causing emission of a MonitorSituation outbound event, a version 6.1 model cannot consume the event and other business events generated by the processes being monitored may also not be processsed correctly. This can manifest itself during the migration of a model to version 6.1 (from any previous version), when you reconfigure the older version of the model (generated with the corresponding previous version of the Monitor Development Toolkit) to not create new monitoring context instances. This package also contains fixes for the following issues that were originally resolved in Interim Fix 4: APAR JR26927 ------------ [Toolkit] If an outbound event contains a filter expression based on extended data from the event, then monitor EAR generation will fail with a Java compilation error. Additionally, the expression should be restricted by the validator to reference only the outbound event and not an inbound event. APAR JR27048 ------------ [Server/Dashboard] When an SVG file is associated with a monitoring context, line breaks and tabs are stripped from the XML stream when it is written to the MONITOR database (in schema REPOS, table META_MONITORING_CONTEXT, column PROCESS_DIAGRAM) during model deployment. This impacts additions to the SVG, such as JavaScript, which may be dependent on formatting. APAR JR27053 ------------ [Toolkit] If the user-defined name of a monitoring context, event, metric, trigger, counter, or stopwatch contains a '$' character, monitor EAR generation will fail (with an error in the compilation of the deployment descriptor file, ejb-jar.xml). This package also contains fixes for the following issues that were originally resolved in Interim Fix 3: APAR JR27503 ------------ [Server/Toolkit] If you have more than 30,000 active monitoring context instances (whether in a single model or across multiple models) in a single Monitor server and if there is at least one time-based trigger in any of the models, then the on-time situation processing that is required to evaluate the triggers may cause event processing to halt. APAR JR27521 ------------ [Server] A column in the correlation index that is created for each monitoring context definition by the state.ddl script is incorrect. (The state.ddl script is generated during Step 1 of the Setup Wizard for monitor model deployment.) The column represents the monitoring context termination times, and was deprecated in version 6.0.2.1. A new column was added for Daylight Savings Time compatibility. The deprecated column needs to be replaced with the new column in the correlation index. (NOTE: Please see section H for information on how to activate the fixes for APAR JR27503 and APAR JR27521 for monitor models that were deployed on your Monitor server prior to the installation of Interim Fix 3 or higher.) ************************************************************************ B. Updating WebSphere Business Monitor Server on Windows ************************************************************************ (NOTE: If you have installed Monitor Development Toolkit, this section does not apply. Proceed to "Updating WebSphere Business Monitor Development Toolkit.") Perform the following steps to update an existing installation of WebSphere Business Monitor Server version 6.0.2.1 to the Interim Fix 5 level on the Windows platform. 1. Unzip 6.0.2.1-WBI-MONITOR-iFix5.zip to a directory. For example, C:\Monitor. 2. cd to C:\Monitor\update6021iFix5\monsrv 3. Run updateMonitorServer.bat. The script will ask if the update is running on a WAS ND Deployment Manager. Type "y" for "yes" or "n" for "no". Then the script will prompt you for the following information. To accept the defaults, press the Enter key. - WebSphere Business Monitor installation directory - WebSphere Process Server installation directory - WebSphere Process Server profile directory - server name 4. The output from the update tool will be logged in C:\Monitor\update6021iFix5\monsrv\logs\monsrv.log. The log file also will be copied to \update\6.0.2.1-WB-MONITOR-iFix5.install\logs. Additionally, backups of replaced files will be copied to \update\6.0.2.1-WB-MONITOR-iFix5.install\backups\monsrv. 5. If the update succeeded, the last message in the log file will say "Update finished". If the update failed, the last message in the log file will say "Update failed". ************************************************************************ C. Updating WebSphere Business Monitor Server on AIX ************************************************************************ Perform the following steps to update an existing installation of WebSphere Business Monitor Server version 6.0.2.1 to the Interim Fix 5 level on the AIX platform. 1. Create a directory for the update tool. For example, /usr/Monitor 2. Copy the 6.0.2.1-WBI-MONITOR-iFix5.tar.gz file to the directory you created in Step 1. 3. cd to /usr/Monitor 4. Decompress the 6.0.2.1-WBI-MONITOR-iFix5.tar.gz file by running this command: gunzip -d 6.0.2.1-WBI-MONITOR-iFix5.tar.gz This will replace the .gz file with a .tar file named 6.0.2.1-WB-MONITOR-iFix5.tar. 5. Extract the 6.0.2.1-WBI-MONITOR-iFix5.tar file by running this command: tar -xvf 6.0.2.1-WBI-MONITOR-iFix5.tar 6. cd to /usr/Monitor/update6021iFix5/monsrv 7. Run updateMonitorServer.sh. The script will ask if the update is running on a WAS ND Deployment Manager. Type "y" for "yes" or "n" for "no". Then the script will prompt you for the following information. To accept the defaults, press the Enter key. - WebSphere Business Monitor installation directory - WebSphere Process Server installation directory - WebSphere Process Server profile directory - server name 8. The output from the update tool will be logged in /usr/Monitor/update6021iFix5/monsrv/logs/monsrv.log. The log file also will be copied to /update/6.0.2.1-WBI-MONITOR-iFix5.install/logs. Additionally, backups of replaced files will be copied to /update/6.0.2.1-WB-MONITOR-iFix5.install/backups/monsrv. 9. If the update succeeded, the last message in the log file will say "Update finished". If the update failed, the last message in the log file will say "Update failed". ************************************************************************ D. Updating WebSphere Business Monitor Dashboard on Windows ************************************************************************ Perform the following steps to update an existing installation of WebSphere Business Monitor Dashboard version 6.0.2.1 to the Interim Fix 5 level on the Windows platform. If you have installed Monitor Development Toolkit, this section does not apply. Proceed to "Updating WebSphere Business Monitor Development Toolkit." Note: If LDAP security is enabled: a. Disable LDAP security b. Complete the steps in this section. c. Reenable LDAP security. The update will fail without warning if security is not disabled. 1. Unzip 6.0.2.1-WBI-MONITOR-iFix5.zip to a directory. For example, C:\Monitor. 2. cd to C:\Monitor\6.0.2.1-WBI-MONITOR-iFix5\dashboard 3. Run updateDashboard.bat. It will prompt you for the following information. To accept the defaults, press the Enter key. - WebSphere Business Monitor installation directory - WebSphere Application Server installation directory - WebSphere Application Server profile directory - WebSphere Portal installation directory - password for the Portal Admin user (wpsadmin) 4. The output from the update tool will be logged in the C:\Monitor\update6021iFix5\dashboard\logs\dashboard.log. The log file also will be copied to \update\6.0.2.1-WBI-MONITOR-iFix5.install\logs. Additionally, backups of replaced files will be copied to \update\6.0.2.1-WB-MONITOR-iFix5.install\backups\dashboard. 5. If the update succeeded, the last message in the log file will say "Update finished". If the update failed, the last message in the log file will say "Update failed". ************************************************************************ E. Updating WebSphere Business Monitor Dashboard on AIX ************************************************************************ Perform the following steps to update an existing installation of WebSphere Business Monitor Dashboard version 6.0.2.1 to the Interim Fix 5 level on the AIX platform. Note: If LDAP security is enabled: a. Disable LDAP security b. Complete the steps in this section. c. Reenable LDAP security. The update will fail without warning if security is not disabled. 1. Create a directory for the update tool. For example, /usr/Monitor 2. Copy the 6.0.2.1-WBI-MONITOR-iFix5.tar.gz file to the directory you created in Step 1. 3. cd to /usr/Monitor 4. Decompress the 6.0.2.1-WBI-MONITOR-iFix5.tar.gz file by running this command: gunzip -d 6.0.2.1-WBI-MONITOR-iFix5.tar.gz This will replace the .gz file with a .tar file named 6.0.2.1-WB-MONITOR-iFix5.tar. 5. Extract the 6.0.2.1-WBI-MONITOR-iFix5.tar file by running this command: tar -xvf 6.0.2.1-WBI-MONITOR-iFix5.tar 6. cd to /usr/Monitor/update6021iFix5/dashboard 7. Run updateDashboard.sh. It will prompt you for the following information. To accept the defaults, press the Enter key. - WebSphere Business Monitor installation directory - WebSphere Application Server installation directory - WebSphere Application Server profile directory - WebSphere Portal installation directory - password for the Portal Admin user (wpsadmin) 8. The output from the update tool will be logged in the /usr/Monitor/update6021iFix5/dashboard/logs/dashboard.log. The log file also will be copied to /update/6.0.2.1-WBI-MONITOR-iFix5.install/logs. Additionally, backups of replaced files will be copied to /update/6.0.2.1-WB-MONITOR-iFix5.install/backups/dashboard. 9. If the update succeeded, the last message in the log file will say "Update finished". If the update failed, the last message in the log file will say "Update failed". ************************************************************************ F. Updating WebSphere Business Monitor Development Toolkit ************************************************************************ Perform the following steps to update an existing installation of WebSphere Business Monitor Development Toolkit from version 6.0.2.1 to the Interim Fix 5 level on the Windows platform. The Integrated Development Environment (IDE) and, if installed, the Integrated Test Environment (ITE), which includes Monitor Server, will be updated. Note: If you are updating the Monitor Development Toolkit on a Windows 2003 machine, you must update the Data Execution Prevention (DEP) settings before performing the Toolkit update. If you do not update the Data Execution Prevention settings, the Toolkit update will fail. To update the Data Execution Prevention settings, right-click on My Computer, then select Properties. Select the Advanced tab, then in the Performance section, select Settings. Then select the Data Execution Prevention tab. Next, perform either step A or step B. A. Select "Turn on DEP for essential Windows programs and services only" and click Apply. B. Select "Turn on DEP for all programs and services except those I select:" and add these programs to the list: %WID_HOME%\wid.exe %WID_HOME%\rationalsdp.exe %WID_HOME%\setup\lum\wid\enroll.exe Then click Apply. Reboot your machine after making these changes and prior to updating the Toolkit. 1. Unzip 6.0.2.1-WBI-MONITOR-iFix5.zip to a directory. For example, C:\Monitor. 2. cd to C:\Monitor\update6021iFix5\toolkit 3. Run updateDevToolkit.bat. It will prompt you for the following information. To accept the defaults, press the Enter key. - WebSphere Business Monitor installation directory - cell name - node name 4. If you have the Monitor ITE installed, you will be prompted for your WPS userid and password during the course of the installation. When you see the following messages, press Enter. Then you will see the prompts for your WPS userid and password. Press [Enter] and then you will be prompted to enter a user name and password ... 5. The output from the update tool will be logged in C:\Monitor\update6021iFix5\toolkit\logs\toolkit.log and C:\Monitor\update6021iFix5\monsrv\logs\monsrv.log. The log files also will be copied to %WID_HOME%\WBMonitor\update\6.0.2.1-WBI-MONITOR-iFix5.install\logs. Additionally, backups of replaced files will be copied to %WID_HOME$\WBMonitor\update\6.0.2.1-WB-MONITOR-iFix5.install\backups\monsrv and %WID_HOME$\WBMonitor\update\6.0.2.1-WB-MONITOR-iFix5.install\backups\toolkit. 6. After completing the update, the tool will ask you whether you want it to automatically launch WID with the -clean option, as required the first time WID is started after the update. Enter "y" if you want the launch to occur. Otherwise, the log file will be updated with the instructions for launching WID manually with the -clean option. 7. If the update succeeded, the last message in the log file will say "Update finished". If the update failed, the last message in the log file will say "Update failed". ************************************************************************ G. Updating WebSphere Business Monitor in a Network Deployment cell ************************************************************************ Take the following precautions when updating WebSphere Business Monitor version 6.0.2.1 to the Interim Fix 5 level in a Network Deployment cell. 1. Perform the update procedures described above for each WebSphere Business Monitor installation in the cell. 2. Ensure that all federated nodes are updated. If you do not, your system will function unpredictably. ************************************************************************ H. Activating Fixes for Existing Models ************************************************************************ To activate the fixes for APAR JR27503 and APAR JR27521 (monitoring performance improvements) for monitor models that were deployed on your Monitor server prior to the installation of Interim Fix 3 or higher on the server, you must create and deploy a new version of each of these models, using the Monitor toolkit updated with Interim Fix 3 or higher. (These models will remain functional after Interim Fix 3 or higher is installed, but the fixes will not be active for these models.) If you have any models that were deployed on your Monitor server prior to the installation of Interim Fix 3 or higher, for which the procedure specified here has not already been applied, ensure that Interim Fix 3 or higher is installed on your Monitor toolkit. Then, for each of these models, do the following: 1. Start WebSphere Integration Developer. 2. Switch to the Business Monitoring perspective. 3. In the Project Explorer view, expand the Monitor Models folder and double-click the monitor model. 4. If the Monitor Details Model view does not appear in the right pane, click the Monitor Details Model tab at the bottom of the pane. 5. In the Timestamp (UTC) field, type a value into that field or click the Edit... button to select a value. If a value is already displayed, update the value to a later time (this field is what Monitor uses to keep track of different versions of the same model). 6. Select File->Save from the menu to save the change. 7. In the Project Explorer view, right-click the monitor model and select Generate Monitor EAR. 8. In the Generate Monitor J2EE Projects dialog, check the "overwrite existing projects" checkbox and click Finish. 9. Switch to the J2EE perspective. 10. In the Project Explorer view, expand the Enterprise Applications folder, then right-click the EAR generated in step 7 and select Deploy. 11. Right-click the EAR and select Export...->EAR file to create the EAR file. 12. Install the EAR file (application) on the Monitor server using the procedure described in "Installing a monitor model" (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.ibm.btools.help.monitor.doc/Doc/tasks/administration/ad_importingbusinessmeasuresmodel.html) in the WebSphere information center. 13. Deploy the new version of the model using the procedure described in "Deploying a monitor model" (http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/topic/com.ibm.btools.help.monitor.doc/Doc/tasks/administration/ad_setupwizard.html) in the WebSphere information center.