IBM Tivoli OMEGAON XE for Messaging on z/OS Readme (7.1.0.1-TIV-XEforMsg-IF0004-README_AppSupport_ZOS) 1. Abstract This interim fix refreshes the Java certificate of application support files. 2. Problems fixed The following problems are addressed by this interim fix. 2.1 APARs ------------- ITCAM configuration agent for WebSphere MQ N/A ITCAM agent for WebSphere MQ N/A ITCAM agent for WebSphere Message Broker N/A 2.2 Java Certificate Refresh ------------- The certificate of support files in previous versions will expire in April 2016. This interim fix provides re-signed support files. Note: This interim fix is cumulative. For the problems and enhancements addressed in 7.1.0 Fix Pack 1 Interim Fix 1, 7.1.0 Fix Pack 1 Interim Fix 2 and 7.1.0 Fix Pack 1 Interim Fix 3 please see the links below for details: ITCAM Agents for WebSphere Messaging Version 7.1.0 Fix Pack 01 Interim fix 01 (7.1.0.1-TIV-XEforMsg-IF0001) http://www-01.ibm.com/support/docview.wss?uid=swg24035846 ITCAM Agents for WebSphere Messaging Version 7.1.0 Fix Pack 01 Interim fix 02 (7.1.0.1-TIV-XEforMsg-IF0002) http://www-01.ibm.com/support/docview.wss?uid=swg24037468 ITCAM Agents for WebSphere Messaging Version 7.1.0 Fix Pack 01 Interim fix 03 (7.1.0.1-TIV-XEforMsg-IF0003) http://www-01.ibm.com/support/docview.wss?uid=swg24038263 3. Prerequisites Application files of ITCAM Agents for WebSphere Messaging Version 7.1.0 Fix Pack 1 must be installed. See the link below for details: http://www-01.ibm.com/support/docview.wss?uid=swg24035244 Supported IBM Tivoli Monitoring * IBM Tivoli Monitoring 6.2.3 fix pack 3 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.1.0 FP1 also exist in this interim fix. 5. Installation information Note: This interim fix involves TEMS, TEPS and TEP on distributed platforms. You must apply the interim fix to the distributed systems where TEMS, TEPS and TEP are installed. ========================================================================= 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: - li6243 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/FP01IF04_depot, and copy the tems-teps-tepd-unix-710fp01if04-160217.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 'tems-teps-tepd' 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 'tems-teps-tepd' 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 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 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\FP01IF04_depot. Copy tems-teps-tepd-windows-710fp01if04-160217.zip to the newly created directory. 4. Extract the installation package. 5. Open a new command prompt with Administrator privileges 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 -> select TEMS location. In the subsequent dialog box, use 'Ctrl + left click' to select all eight components (if exist) for 'TEMS configurator', 'WebSphere MQ Configuration Agent', 'WebSphere MQ Monitoring Agent' and 'WebSphere Message Broker Monitoring Agent'. 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 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 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 Windows: ========================================================================= 1. Stop TEMS/TEPS/TEP 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 > select TEMS location. In the subsequent dialog box, use 'Ctrl + left click' to select all eight components (if exist) for 'TEMS configurator', 'WebSphere MQ Configuration Agent', 'WebSphere MQ Monitoring Agent' and 'WebSphere Message Broker Monitoring Agent'. 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