IBM Tivoli Composite Application Manager for Applications: ITCAM Agents for WebSphere Messaging Version 7.3.0 Fix Pack 1 Interim Fix 1 Readme 1. Abstract This interim fix addresses one defect in previous version and has the following changes: - Provides support of IBM Integration Bus Version 10.0.0.2 - Refreshes the Java certificate of application support files. This readme file provides installation related information about how to apply this interim fix. 2. Problems fixed The following problems are addressed by this interim fix. 2.1 Java Certificate Refresh ------------- The certificate of support files in previous versions will expire in April 2016. This interim fix provides re-signed support files and related SDA files. 2.2 Defect ---------------------- Defect 89467: Duplicated RSOS_S1K was defined in kqi.his file The long term historic data can not be retrieved from the warehouse database. The following error can be found in the KHD log: (56438CE8.0006-22:khdxattr.cpp,364,"convertIntNameToExtName") Column name not found. (56438CE8.0007-22:khdxns1m.cpp,1084,"createExportRequest") New DBC export request (779092933) created, obj=2002814BC80 - "NULL" "RTE1:IPO1:KQIA" 3. Prerequisites 1. ITCAM Agents for WebSphere Messaging Version 7.3.0 Fix Pack 1 must be installed. For details about Version 7.3.0 Fix Pack 1, see the following website: http://www-01.ibm.com/support/docview.wss?uid=swg24040581 2. Make sure that the software installed in your environment is compatible with this interim fix. Supported WebSphere MQ * WebSphere MQ 6.0 * WebSphere MQ 7.0 * WebSphere MQ 7.0.1 * WebSphere MQ 7.1 * WebSphere MQ 7.5 * WebSphere MQ 7.5.0.1 * WebSphere MQ 8.0.0.0 Supported IBM broker products: * WebSphere Message Broker V7.0 * WebSphere Message Broker V8.0 * WebSphere Message Broker V8.0.0.1 * WebSphere Message Broker V8.0.0.2 * IBM Integration Bus V9.0.0.0 * IBM Integration Bus V9.0.0.1 * IBM Integration Bus V9.0.0.2 * IBM Integration Bus 10.0.0.0 * IBM Integration Bus 10.0.0.2 Supported IBM Tivoli Monitoring * IBM Tivoli Monitoring 6.3.0 fix pack 2 or later 4. Known limitations All the limitations of the ITCAM agent for WebSphere MQ, ITCAM configuration agent for WebSphere MQ and ITCAM agent for WebSphere Message Broker in V7.3.0 Fix Pack 1 still exist in this interim fix. 5. Installation information Note: This interim fix involves TEMS, TEPS, TEP, and the agents. You must apply the interim fix to the systems where TEMS, TEPS, TEP, and the agents are installed separately. Even if all those components are installed in the same directory on the same system, you still need to install two separate packages to apply this interim fix for the application files and agents. ========================================================================= Installing the interim fix on UNIX and Linux systems ========================================================================= --- Apply interim fix on TEMS/TEPS/TEP on UNIX/Linux --- 1. Make sure that the portal server is running and back up the portal server database by doing the following steps: 1.1 Go to the [$ITM_HOME]/bin directory, where [$ITM_HOME] is the installation directory of IBM Tivoli Monitoring (the default is /opt/IBM/ITM). 1.2 Issue the following command: ./itmcmd execute cq "runscript.sh migrate-export" This script creates a file named saveexport.sql, which contains all the protal server data. This file is in the/opt/IBM/ITM/$platform/cq/SQLLIB directory, where $platform is one of the following architecture codes: - lx8266 or li6263 for Intel Linux - ls3263 for zSeries Linux - aix533 for AIX 2. Stop the monitoring server, portal server, and portal, if they are running. 3. Create a directory to contain the installation package of this fix pack, for example, $HOME/FP01IF01_depot, and copy the tems-teps-tepd-730fp01if01-151122.tar package to this directory. 4. Go to the newly created directory and extract the installation package with the following command: tar -xvf Where the tar file name is the name of the file that you just copied to the newly created directory. A directory whose name begins with '730fp01if01-151122' is created. Note: Do not extract the interim fix image with the root ID. If you extract the image with the root ID, the user ID and group ID might be invalid to the extracted files. 5. Run the following command from the directory that is created in the previous step. ./patch_install.sh [$ITM_HOME] where [$ITM_HOME] is the IBM Tivoli Monitoring installation directory. Note: The current user ID must have write permission to the directory whose name begins with '730fp01if01-151122' and must have the required authority to execute the patch_install.sh file. 6. Follow the prompts to complete the installation. 7. If the monitoring server is installed on the destination system, start the monitoring server, and run the following command to seed it: cd [$ITM_HOME]/bin/ ./itmcmd support -t [$TEMS_NAME] mq qi mc cf where [$ITM_HOME] is the IBM Tivoli Monitoring installation directory and [$TEMS_NAME] is the monitoring server name. 8. Run the following commands on the portal server to rebuild the workspaces: cd [$ITM_HOME]/bin/ ./itmcmd config -A cq where [$ITM_HOME] is the IBM Tivoli Monitoring installation directory. Important: The "./itmcmd config -A cq" command executes the InstallPresentation.sh file. The InstallPresentation.sh file deletes and imports data against the portal server database. After that, all the components that are installed on this portal server are seeded again. As a result, your customizations of the product-provided workspaces, SQL queries, situations, policies as SYSADMIN in the ADMIN mode will be lost. 9. Start the following components that are installed on the destination system in order : - Monitoring server - Portal server - Portal --- Apply interim fix for the agents on UNIX/Linux --- 1. Stop the agents if they are running. 2. Create a directory to contain the installation package of this fix pack and copy platform specific package to this newly created directory. Tip: You can determine the package to copy according to the package file name. Some package names that might be easy to confuse are listed as follows: 32-bit xLinux: lnx3-li6263-730fp01if01-151122.tar 64-bit xLinux: lnx3-lx8263-730fp01if01-151122.tar 32-bit Solaris: sos-sol283-730fp01if01-151122.tar 64-bit Solaris: sosamd-sol603-730fp01if01-151122.tar 3. Go to the newly created directory and extract the installation package with the following command. tar -xvf Where the tar file name is the name of the file that you have just to the newly created directory. A directory whose name begins with '730fp01if01-151122' is created. Note: Do not extract the interim fix image with the root ID. If you extract the image with the root ID, the user ID and group ID might be invalid to the extracted files. 4. Run the following command from the directory that is created in the previous step: ./patch_install.sh [$ITM_HOME] where [$ITM_HOME] is the IBM Tivoli Monitoring installation directory. Note: The current user ID must have write permission to the directory whose name begins with '730fp01if01-151122' and must have the required authority to execute the patch_install.sh file. 5. Follow the prompts to complete the installation. 6. After the installation completes, start the agents. Note: When a backup is created with the patch_install.sh file, a new directory named backupXX is created. If it is the first time that a backup is created, XX is 00, and then it is incremented by 1 for each subsequent backup to avoid overwriting previously backed-up files. This directory is used as follows: 1.All files overwritten during the installation are copied to this directory. 2.A file named patch_uninstallXX (where XX is the same as the directory name) is created. You can run this program to remove the interim fix. ========================================================================= Installing the interim fix on i5/OS ========================================================================= 1. Open the WebSphere MQ Monitoring menu by issuing from the i5/OS command line: WRKOMAMQ 2. Select the option to stop the agent. 3. Open the jobs menu by issuing the following command from the i5/OS command line: WRKACTJOB Verify that the WebSphere MQ Monitoring agent is stopped.(No KMQLIB job is running). 4. Extract the savf files from iSeries-730fp01if01.zip to a temporary directory on a Windows or a UNIX system. 5. Create save files on the target i5/OS system. 6. On the Windows or UNIX system, use FTP to transfer the savf file in BINARY mode to the newly created savf file on the i5/OS system. 7. Create KMQ7100103 library on the i5/OS system and restore the objects directly into KMQ7300101 library For WebSphere MQ Monitoring agent, run the following commands: RSTOBJ OBJ(*ALL) SAVLIB(KMQ7300101) DEV(*SAVF) SAVF({your_library}/KMQ7300101) MBROPT(*ALL) ALWOBJDIF(*ALL) RSTLIB(KMQ7300101) 8. Backup all files under /QIBM/ProdData/IBM/KMQ/support. 9. Copy the following SDA related files for WebSphere MQ Monitoring agent: CPYTOSTMF FROMMBR('/QSYS.LIB/KMQ7300101.LIB/KMQJSTMS.FILE/JAR.MBR') TOSTMF('/QIBM/ProdData/IBM/KMQ/support/KMQJSTMS.jar') STMFOPT(*REPLACE) CPYTOSTMF FROMMBR('/QSYS.LIB/KMQ7300101.LIB/KMQJSTPS.FILE/JAR.MBR') TOSTMF('/QIBM/ProdData/IBM/KMQ/support/KMQJSTPS.jar') STMFOPT(*REPLACE) CPYTOSTMF FROMMBR('/QSYS.LIB/KMQ7300101.LIB/KMQJSTPW.FILE/JAR.MBR') TOSTMF('/QIBM/ProdData/IBM/KMQ/support/KMQJSTPW.jar') STMFOPT(*REPLACE) CPYTOSTMF FROMMBR('/QSYS.LIB/KMQ7300101.LIB/KMQMSMAN.FILE/KMQMSMAN.MBR') TOSTMF('/QIBM/ProdData/IBM/KMQ/support/KMQMSMAN.txt') STMFOPT(*REPLACE) 10. Open the WebSphere MQ Monitoring menu by issuing one of the following commands from the i5/OS command line: WebSphere MQ Monitoring: WRKOMAMQ Select the option to start the agent. Installation is now complete. ========================================================================= Installing the interim fix on Windows systems ========================================================================= --- Apply interim fix on TEMS/TEPS/TEP on Windows --- 1. Make sure that the portal server is running and back up the portal server database. 1.1 Go to the [$ITM_HOME]\CNPS directory, where [$ITM_HOME] is the IBM Tivoli Monitoring installation directory (the default is C:\IBM\ITM). 1.2 Issue the following command: migrate-export This script creates a file named saveexport.sql in the [$ITM_HOME]\CNPS\SQLLIB directory. It contains all the portal server data. Note: The migrate-export process will stop the portal server if it is currently running. 2. Stop the monitoring server, portal server, and portal, if they are running. 3. Create a directory to contain the interim fix installation package for Windows, for example, C:\patch\FP01IF03_depot. Copy tems-teps-tepd-730fp01if01-151122.zip to the newly created directory. 4. Extract the installation package. A directory whose name begins with '730fp01if01-151122' is created that contains the installation files. 5. Open a new command prompt and go to the directory that is created in step 4. Run the following command in the command prompt and follow the prompts to complete the installation: patch_install.bat [$ITM_HOME] Follow the prompts to complete the installation. 6. Start the monitoring server. 7. Open the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli Enterprise Portal Server and click Advanced -> Add TEMS Application Support. In the subsequent dialog box, select the monitoring server that you want to reseed, and select kmq.sql and kqi.sql. Then click OK. You can also run the following command from the IBM Tivoli Monitoring installation directory and go with the default choices to seed the monitoring server: kinconfg -fm 8. Go to the [$ITM_HOME]\CNPS directory and run the following command to rebuild the workspaces: InstallPresentation Important: The InstallPresentation command deletes and imports data against the portal server database. After that, all components that are installed on this portal server are seeded again. As a result, your customizations of product-provided workspaces, SQL queries, situations, policies as SYSADMIN in ADMIN mode will be lost. 9. Reconfigure the Tivoli Enterprise Portal and Tivoli Enterprise Portal Browser Client by right-clicking them in the Manage Tivoli Enterprise Monitoring Services window and clicking Reconfigure. 10. Click OK in the subsequent dialog. 11. Start the following components that are installed on the destination system in order: Monitoring server Portal server Portal --- Apply interim fix for agents on Windows --- 1. Stop agents if they are running. 2. Create a directory to contain the interim fix installation package for Windows, for example, C:\patch\FP01IF03_depot. Copy wnt-730fp01if01-151122.zip to the newly created directory. 3. Extract the installation package. A directory whose name begins with '730fp01if01-151122' is created that contains the installation files. 4. Open a new command prompt and go to the directory that is created in step 3. Run the following command in the command prompt and follow the prompts to complete the installation: patch_install.bat [$ITM_HOME] Follow the prompts to complete the installation. 5. Start agents. Remember: When a backup is created using patch_install.bat, a new directory named backup is created. If it is the first time a backup is created, another directory named backup_original is also created. The backup directory is used as follows: 1. All files overwritten during the installation process are copied to backup. 2. A file named patch_uninstall.bat is created. You can run this program to uninstall interim fix. 6. Uninstalling ========================================================================= Uninstalling the interim fix on UNIX or Linux: ========================================================================= 1. Stop TEMS/TEPS/TEP/Agents that running in the [$ITM_HOME]. 2. Run the patch_uninstallXX file in the depot directory. 3. If you changed the portal server database, you can restore the original data by importing the exported SQL file. To import the portal server data on a UNIX or Linux system, go to the [$ITM_HOME]/bin directory and run the following command: ./itmcmd execute cq "runscript.sh migrate-import" 4.If Tivoli Enterprise Monitoring Server is installed on the destination system, start the monitoring server, and run the following command to seed the monitoring server: $ITM_HOME/bin/itmcmd support -t [TEMS NAME] mq qi mc cf ========================================================================= Uninstalling the interim fix on i5/OS: ========================================================================= 1. Locate the library files that you backed up during installation. 2. Copy the backup files to the WebSphere MQ Configuration and WebSphere MQ Monitoring production libraries. The interim fix is uninstalled. ========================================================================= Uninstalling the interim fix on Windows: ========================================================================= 1. Stop TEMS/TEPS/TEP/Agents that running in the [$ITM_HOME]. 2. Run the patch_uninstall.bat file in the depot directory. 3. If you changed the portal server database, you can restore the original data by importing the exported SQL file. To import the portal server data, go to the CNPS directory and run the following command: migrate-import Note: Running the migrate-import process will stop the portal server if it is currently running. 4. Start the monitoring server. 5. Open the Manage Tivoli Enterprise Monitoring Services window, right-click Tivoli Enterprise Portal Server and click Advanced > Add TEMS Application Support. 6. In the subsequent dialog box, select the monitoring server that you want to reseed, and select kmq.sql and kqi.sql. Then click OK. 7. Post-installation configuration for ITCAM agent for WebSphere MQ N/A 8. Post-installation configuration for ITCAM agent for WebSphere Message Broker N/A 9. Post-installation configuration for ITCAM configuration agent for WebSphere MQ N/A