+++ Objective Page 1 of 26 Installation of ITM Agents 6.0.3.2 and ITCAM MQ Agents 7.3 in Linux IBM Techdoc: 7048601 http://www.ibm.com/support/docview.wss?uid=swg27048601 Date last updated: 08-Sep-2016 Angel Rivera rivera@us.ibm.com IBM MQ Support The purpose of this document is to provide a tutorial for installation IBM Tivoli Monitoring 6.3.0.2 and IBM Tivoli Composite Application Manager (ITCAM) for Applications 7.3 in a Linux machine. The overall objective is to have ITM and ITCAM services monitoring MQ queue managers in Windows and in Linux, and additional tutorials will provide steps for other components. The Tivoli agents in Linux will connect to the "Tivoli Enterprise Monitoring Server - TEMS" that was setup in the following techdoc: http://www.ibm.com/support/docview.wss?uid=swg27048598 Installation of ITM 6.0.3.2 in Windows to monitor MQ queue managers In order to keep the overall scenario as simple as possible, only the most essential components will be installed. Therefore, this tutorial does not show other ITM and ITCAM components; of course, if you need additional components, then you can go ahead and install/configure them. These are the chapters: Chapter 1: Downloading the software Chapter 2: Adding userid "root" to group "mqm" Chapter 3: Installing the ITM 6.3.0.2 Agents in Linux Agentless Monitoring for Linux Operating Systems V06.30.02.00 Monitoring Agent for Linux OS V06.30.02.00 Tivoli Enterprise Services User Interface Extensions V06.30.02.00 Chapter 4: Configuration of the ITM Linux OS Agent to connect to TEMS in Windows Chapter 5: Installing ITCAM 7.3 MQ Agents - IBM Tivoli Monitoring components Tivoli Enterprise Services User Interface Extensions V06.30.02.00 WebSphere MQ Configuration Agent V07.30.01.00 WebSphere MQ Monitoring Agent V07.30.01.00
Page 2 of 26 Chapter 6: Configuration of the MQ Agents Chapter 7: Configuration of the MQ Monitoring Agent for multi-instance + Set of tutorials and webinar http://www.ibm.com/support/docview.wss?uid=swg27048598 Installation of ITM 6.0.3.2 in Windows to monitor MQ queue managers IBM Techdoc: 7048598 First tutorial in the series. http://www.ibm.com/support/docview.wss?uid=swg27048600 Installation of ITCAM Agents 7.3 in Windows to monitor MQ queue managers IBM Techdoc: 7048600 Second tutorial in the series. http://www.ibm.com/support/docview.wss?uid=swg27048601 Installation of ITM Agents 6.0.3.2 and ITCAM MQ Agents 7.3 in Linux IBM Techdoc: 7048601 Third tutorial in the series. http://www.ibm.com/support/docview.wss?uid=swg27048602 ITM and ITCAM - summary of commands for monitoring MQ queue managers IBM Techdoc: 7048602 Webinar: http://www.ibm.com/support/docview.wss?uid=swg27048572 Using ITCAM to monitor MQ queue managers in Linux and Windows Abstract This WebSphere Support Technical Exchange is designed to present an introduction on basic installation of IBM Tivoli Monitoring (ITM) and IBM Tivoli Composite Application Manager (ITCAM) Agents for WebSphere Messaging to monitor MQ queue managers in Linux and Windows. Level of Difficulty: Beginner
Page 3 of 26 ++ References + ITM https://www.ibm.com/support/knowledgecenter/sstfxa_6.3.0.2/com.ibm.itm.doc_6.3fp2 /welcome.htm IBM Tivoli Monitoring V6.3 Fix Pack 2 documentation https://www.ibm.com/support/knowledgecenter/sstfxa_6.3.0.2/com.ibm.itm.doc_6.3fp2 /install/unixconfig_ma.htm Tivoli Monitoring 6.3.0.2>Version 6.3 Fix Pack 2>Installation and Configuration Guides>Installation Guide>Installing IBM Tivoli Monitoring>Installing monitoring agents>linux or UNIX: Installing a monitoring agent>configuring the monitoring agent https://www.ibm.com/support/knowledgecenter/sstfxa_6.3.0.2/com.ibm.itm.doc_6.3fp2 /install/pc_codes.htm?lang=en Tivoli Monitoring 6.3.0.2>Version 6.3 Fix Pack 2>Installation and Configuration Guides>Installation Guide>IBM Tivoli product, platform, and component codes Component product codes for infrastructure components and base monitoring agents The main Product Code to be used in this techdoc is "lz": Linux OS monitoring agent Other codes: UNIX Log Alert monitoring agent UNIX OS monitoring agent Windows OS monitoring agent Agentless monitoring for Windows operating systems Agentless monitoring for Linux operating systems lz ul ux nt r2 r4 + ITCAM https://www.ibm.com/support/knowledgecenter/ss3jrn_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/welcome_apps7211.html?lang=en IBM Tivoli Composite Application Manager for Applications, Version 7.2.1.1 Note: The Tivoli monitoring agents for MQ are at version 7.3, but they are described in the following online manual (7.2.1.1). At the time of writing this techdoc, there was no online manual for 7.3.
Page 4 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 1: Downloading the software ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Visit IBM Passport Advantage to download the software There are many components to choose from. For the basic configuration described in this document, only 2 components were downloaded into the local Linux PC. + Summary of the components to download The most effective way to find an item in IBM Passport Advantage is by searching for "Pat Number". Number of part to download: CIQ3QML Title on Passport Advantage: IBM Tivoli Monitoring V6.3.0.2 Agents, Multiplatform, Multilingual Downloaded in local PC into the following directory: /downloads/itm/itm_v6.3.0.2_agt_mp_ml.tar.gz Size: 3,294 MB Number of part to download: CN6R0EN Title on Passport Advantage: IBM Tivoli Composite Application Manager Agents for WebSphere Messaging 7.3 Fixpack 1 Multiplatform English Downloaded in local PC into the following directory: /downloads/itcam/itcam_agents_ws_msg_7.3_mf.tar.gz Size 2,920 MB
Page 5 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 2: Adding userid "root" to group "mqm" ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ It is necessary to add the userid "root" to the group "mqm" in order to be an MQ Administrator. This is required in order to work with the ITCAM agents that interact with MQ. It is assumed that you have already installed MQ and that you have a user 'mqm' and a group 'mqm'. It is critical to add the user ID that is to run the agent to the mqm group For this document, the user root is going to run the agent. But root is not a member of the mqm group. The following SLES 11 Linux command will add user root to the group mqm: You need to be root to run it: # groupmod -A root mqm The result is that the output of the following command should show that root is a member of mqm: # id root uid=0(root) gid=0(root) groups=0(root),104(sfcb),501(mqm)
Page 6 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 3: Installing the ITM 6.3.0.2 Agents in Linux ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Login as root Go to the directory where the ITM installation image file was stored: cd /downloads/itm Unpack the tar.gz file: ip-9-30-145-0:/downloads/itm # tar -zxvf ITM_V6.3.0.2_AGT_MP_ML.tar.gz ip-9-30-145-0:/downloads/itm # ls AUTORUN.INF kcirunas.cfg silent_config.txt Deploy license silent_install.txt DeployLnk.sh mibs system_monitor_agent i5os non_ibm_license unix InstallITM notices WINDOWS install.sh PrivateConfigSamples ITM_V6.3.0.2_AGT_MP_ML.tar.gz README.TXT In the directory where you extracted the installation files, run the following command:./install.sh When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default directory (/opt/ibm/itm) or type the full path to a different directory. Enter the name of the IBM Tivoli Monitoring directory [ default = /opt/ibm/itm ]: (press Enter to accept the default) "/opt/ibm/itm" does not exist Try to create it [ 1-yes, 2-no; "1" is default ]? (press Enter to accept the default) Select one of the following: 1) Install products to the local host. 2) Install products to depot for remote deployment (requires TEMS). 3) Install TEMS support for remote seeding 4) Exit install. Please enter a valid number:
Page 7 of 26 - Type 1 to start the installation to the local host and display the software license agreement. 1 - Press Enter to read through the agreement. - Type 1 to accept the agreement and press Enter. 1 - Type a 32 character encryption key and press Enter. This key should be the same as the key that was used during the installation of the monitoring server to which this monitoring agent connects. Enter a 32-character encryption key, or just press Enter to use the default Default = IBMTivoliMonitoringEncryptionKey...+...1...+...2...+...3.. (press enter to accept default) Note from author: The default value was used during the installation of the TEMS in Windows. Product packages are available in /downloads/itm/unix Note from author: The following paragraph could be very cryptic the first time you are encountering. The explanation is this: the ITM components (TEMS, TEPS, TEP Desktop) are very flexible and can understand specific agents, BUT ONLY when the components have been told explicitly to handle the agents. Just the fact that the code for the agents have been installed in the same machine as the ITM components, it does NOT mean that the ITM components will know about them. You MUST configure EACH ITM component to accept the agents! That is, you need to tell TEMS to accept the agents, you need to tell TEPS to accept the agents, you need to tell TEP Desktop to accept the agents. + begin "cryptic" paragraph All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents. + end "cryptic" paragraph The following products are available for installation: 1) Agentless Monitoring for AIX Operating Systems V06.30.02.00 2) Agentless Monitoring for HP-UX Operating Systems V06.30.02.00 3) Agentless Monitoring for Linux Operating Systems V06.30.02.00 4) Agentless Monitoring for Solaris Operating Systems V06.30.02.00 5) Agentless Monitoring for Windows Operating Systems V06.30.02.00
Page 8 of 26 6) Monitoring Agent for Linux OS V06.30.02.00 7) Tivoli Enterprise Services User Interface Extensions V06.30.02.00 8) all of the above Type the numbers that correspond to the products that you want to install. Type "b" to change operating system, or type "q" to quit selection. If you enter more than one number, separate the numbers by a comma or a space. Type your selections here: 3,6,7 The following products will be installed: Agentless Monitoring for Linux Operating Systems V06.30.02.00 Monitoring Agent for Linux OS V06.30.02.00 Tivoli Enterprise Services User Interface Extensions V06.30.02.00 Are your selections correct [ 1=Yes, 2=No ; default is "1" ]? (press enter to accept default) Do you want to check prerequisites for the above components? [ 1=Yes, 2=No ; default is "1" ]? (press enter to accept default) Running Prerequisite Scanner. This may take a few minutes depending on the number of components being checked and the machine's performance. Prerequisite Scanner results for the selected components: PASS IBM Tivoli Monitoring Shared Libraries /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt PASS IBM GSKit Security Interface /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt PASS Tivoli Enterprise-supplied JRE /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt PASS Monitoring Agent for Linux OS /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt NOT AVAILABLE Agentless Monitoring for Linux Operating Systems /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt NOT AVAILABLE Tivoli Enterprise Services User Interface Extensions /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt PASS Prerequisite Scanner Overall Result /opt/ibm/itm/logs/prereqscan/20160301-071127/common/result.txt
Page 9 of 26 Do you want to continue with the installation [ 1=Yes, 2=No ; default is "1" ]? (press enter to accept default) Installing IBM Global Security Toolkit GSkit encryption key has been set. Key File directory: /opt/ibm/itm/keyfiles... installing "Agentless Monitoring for Linux Operating Systems V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "Agentless Monitoring for Linux Operating Systems V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component Agentless Monitoring for Linux Operating Systems V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit).... Agentless Monitoring for Linux Operating Systems V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized.... installing "Monitoring Agent for Linux OS V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "Monitoring Agent for Linux OS V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component Monitoring Agent for Linux OS V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit).... Monitoring Agent for Linux OS V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized.... installing "Tivoli Enterprise Services User Interface Extensions V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "Tivoli Enterprise Services User Interface Extensions V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component Tivoli Enterprise Services User Interface Extensions V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit).... Tivoli Enterprise Services User Interface Extensions V06.30.02.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized. Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is "2" ]? (press enter to accept default)... postprocessing; please wait.... finished postprocessing. Installation step complete. You may now configure any locally installed IBM Tivoli Monitoring product via the "/opt/ibm/itm/bin/itmcmd config" command.
Page 10 of 26 Automatic start at system initialization has been configured. Automatic stop at system shutdown has been configured. The install.sh command creates most of directories and files with world write permissions. IBM Tivoli Monitoring provides the securemain utility to helps you keep the monitoring environment secured. You can secure this installation now or manually execute the securemain utility later. For more information see Appendix G. Securing your IBM Tivoli Monitoring installation on Linux or UNIX in the IBM Tivoli Monitoring Installation and Setup Guide. Do you want to secure this IBM Tivoli Monitoring installation [ 1-yes, 2-no; "2" is default ]? (press enter to accept default) (installer finishes and exits at this time)
Page 11 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 4: Configuration of the ITM Linux OS Agent to connect to TEMS in Windows ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Note from author: It is recommended that you add the following into the PATH for root: export PATH=$PATH:/opt/IBM/ITM/bin This is the general syntax of the ITM configuration command: /opt/ibm/itm/bin/itmcmd config -A productcode where productcode is the product code for your agent. For the UNIX agent, use the product code: ux For the Linux agent, use: lz (*** This is the code that is used in this techdoc ***) Run the following command (In this case it is for Linux): /opt/ibm/itm/bin/itmcmd config -A lz Press Enter when you are asked if the agent connects to a monitoring server. Agent configuration started... Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): (press enter to take default of YES) - Type the protocol that you want to use to communicate with the monitoring server. You have seven choices: ip, ip.pipe, ip.spipe, ip6, ip6.pipe, ip6.spipe, or sna. Press Enter to accept the default protocol (IP.PIPE). (press enter to take default of IP.PIPE). - If you want to set up a backup protocol, enter that protocol and press Enter. If you do not want to use backup protocol, press Enter without specifying a protocol. Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): 0 (press enter to take the default of None)
Page 12 of 26 Note: In the configuration used for this document, the TEMS is located in a remote Windows box, whose host address is: ip-9-30-145-168.svl.ibm.com. The local Linux box does not have a TEMS. Thus, we must specify the host address where the TEMS is located. - Enter the host name of the TEMS: TEMS Host Name for IPv4 (Default is: ip-9-30-145-118): ip-9-30-145-168.svl.ibm.com IP.PIPE Port Number (Default is: 1918): (press enter to take the default of None) Enter name of KDC_PARTITION (Default is: null): (press enter to take the default of null) Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): 2 Enter Optional Primary Network Name or 0 for "none" (Default is: 0): 0 Disable HTTP? [1=YES, 2=NO] (Default is: 2): 1 Agent configuration completed... Note from author: At this point the command finishes. ++ Starting the Linux OS agent Now that the agent has been configured, it is necessary to start it. Issue the following command: # /opt/ibm/itm/bin/itmcmd agent start lz Processing. Please wait... Starting Monitoring Agent for Linux OS... Monitoring Agent for Linux OS started
Page 13 of 26 OK. So far, so good. Question: A question that I could not find a quick answer from the reference material is: now that I installed, configured and started the ITM Linux OS agent, do I have to do something else for the TEMS to recognize the new agent? Answer: No, the start of the ITM Linux OS Agent will contact the TEMS, which in turn will update the TEPS and in turn will communicate it to the TEP Desktop from my Windows box. Then I noticed that the TEP Desktop added a new entry for Linux in the topology: YEAH!!! The next step is to install the ITCAM MQ agents.
Page 14 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 5: Installing ITCAM 7.3 MQ Agents ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ The following will be installed: IBM Tivoli Monitoring components Tivoli Enterprise Services User Interface Extensions V06.30.02.00 WebSphere MQ Configuration Agent V07.30.01.00 WebSphere MQ Monitoring Agent V07.30.01.00 Login as root. Go to the directory where the ITM installation image was stored: cd /downloads/itcam Unpack the tar.gz file: tar -zxvf ITCAM_AGENTS_WS_MSG_7.3_MF.tar.gz Run the installer:./install.sh When prompted for the IBM Tivoli Monitoring home directory, press Enter to accept the default (/opt/ibm/itm): Enter the name of the IBM Tivoli Monitoring installation directory. [ default = /opt/ibm/itm ]: (press enter to accept the default) Press Enter to create the /opt/ibm/itm directory. Type 1 to start the installation and press Enter. Directory "/opt/ibm/itm" already exists. OK to use it [ 1-yes, 2-no; "1" is default ]? (press enter to accept the default) The following processes are currently running: Product = Monitoring Agent for Linux OS PID = 14470 install.sh warning: Existing products found to be running will be restarted during installation., continuing... Continue with this installation [ 1-yes, 2-no; "1" is default ]? (press enter to accept the default) Processing. Please wait... Stopping Watchdog process...
Page 15 of 26 Watchdog process was stopped. Stopping Monitoring Agent for Linux OS... Product Monitoring Agent for Linux OS was stopped gracefully. Agent stopped... Select one of the following: 1) Install products to the local host. 2) Install products to depot for remote deployment (requires TEMS). 3) Install TEMS support for remote seeding 4) Exit install. Please enter a valid number: 1 Initializing... Read the software license agreement and type 1 to accept. 1 Product packages are available in /downloads/itcam/unix The following products are currently installed in "/opt/ibm/itm": Agentless Monitoring for Linux Operating Systems V06.30.02.00 @ Linux x86_64 R2.6, R3.0 (64 bit) IBM GSKit Security Interface V08.00.50.05 @ Linux x86_64 R2.6, R3.0 (64 bit) Monitoring Agent for Linux OS V06.30.02.00 @ Linux x86_64 R2.6, R3.0 (64 bit) Tivoli Enterprise Services User Interface Extensions V06.30.02.00 @ Linux x86_64 R2.6, R3.0 (64 bit) Tivoli Enterprise Services User Interface V06.30.02.00 @ Linux x86_64 R2.6, R3.0 (64 bit) All agents require that application support files that contain agent-specific information be installed on the Tivoli Enterprise Monitoring Server that the agents will connect to, Tivoli Enterprise Portal Server and Tivoli Enterprise Portal desktop and browser client. Install application support before starting to install any Tivoli Enterprise Monitoring Agents. Product packages are available for this operating system and component support categories: 1) IBM Tivoli Monitoring components for this operating system 2) Tivoli Enterprise Portal Browser Client support 3) Tivoli Enterprise Portal Desktop Client support 4) Tivoli Enterprise Portal Server support 5) Tivoli Enterprise Monitoring Server support 6) Other operating systems
Page 16 of 26 Type the number or type "q" to quit selection [ number "1" or "IBM Tivoli Monitoring components for this operating system" is default ]: 1 You selected number "1" or "IBM Tivoli Monitoring components for this operating system" Is the selection correct [ 1=Yes, 2=No ; default is "1" ]? 1 The following products are available for installation: 1) Tivoli Enterprise Services User Interface Extensions V06.30.02.00 2) WebSphere MQ Configuration Agent V07.30.01.00 3) WebSphere MQ Monitoring Agent V07.30.01.00 4) WebSphere Message Broker Monitoring Agent V07.30.01.00 5) all of the above Type the numbers that correspond to the products that you want to install. Type "b" to change operating system, or type "q" to quit selection. If you enter more than one number, separate the numbers by a comma or a space. Type your selections here: 1,2,3 The following products will be installed: Tivoli Enterprise Services User Interface Extensions V06.30.02.00 WebSphere MQ Configuration Agent V07.30.01.00 WebSphere MQ Monitoring Agent V07.30.01.00 Are your selections correct [ 1=Yes, 2=No ; default is "1" ]? 1 Do you want to check prerequisites for the above components? [ 1=Yes, 2=No ; default is "1" ]? 1 Running Prerequisite Scanner. This may take a few minutes depending on the number of components being checked and the machine's performance. Prerequisite Scanner results for the selected components: PASS IBM Tivoli Monitoring Shared Libraries /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt PASS IBM GSKit Security Interface /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt PASS Tivoli Enterprise-supplied JRE /opt/ibm/itm/logs/prereqscan/20160301-
Page 17 of 26 085601/COMMON/result.txt PASS WebSphere MQ Monitoring Agent /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt NOT AVAILABLE Tivoli Enterprise Services User Interface Extensions /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt NOT AVAILABLE WebSphere MQ Configuration Agent /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt PASS Prerequisite Scanner Overall Result /opt/ibm/itm/logs/prereqscan/20160301-085601/common/result.txt Do you want to continue with the installation [ 1=Yes, 2=No ; default is "1" ]? 1 Installing IBM Global Security Toolkit KCIIN2385W WARNING - you are about to install the SAME version of "Tivoli Enterprise Services User Interface Extensions V06.30.02.00" Do you want to install the SAME version [ 1=Yes, 2=No ; default is "2" ]? 2... installing "WebSphere MQ Configuration Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "WebSphere MQ Configuration Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component WebSphere MQ Configuration Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit).... WebSphere MQ Configuration Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized.... installing "WebSphere MQ Monitoring Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit)"; please wait. => installed "WebSphere MQ Monitoring Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit)".... Initializing component WebSphere MQ Monitoring Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit).... WebSphere MQ Monitoring Agent V07.30.01.00 for Linux x86_64 R2.6, R3.0 (64 bit) initialized. Do you want to install additional products or product support packages [ 1=Yes, 2=No ; default is "2" ]? 2... postprocessing; please wait.
Page 18 of 26... finished postprocessing. Installation step complete. You may now configure any locally installed IBM Tivoli Monitoring product via the "/opt/ibm/itm/bin/itmcmd config" command. Automatic start at system initialization has been configured. Automatic stop at system shutdown has been configured. The install.sh command creates most of directories and files with world write permissions. IBM Tivoli Monitoring provides the securemain utility to helps you keep the monitoring environment secured. You can secure this installation now or manually execute the securemain utility later. For more information see Appendix G. Securing your IBM Tivoli Monitoring installation on Linux or UNIX in the IBM Tivoli Monitoring Installation and Setup Guide. Do you want to secure this IBM Tivoli Monitoring installation [ 1-yes, 2-no; "2" is default ]? 2 Processing. Please wait... Starting Monitoring Agent for Linux OS... Monitoring Agent for Linux OS started (the install.sh finishes)
Page 19 of 26 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++ Chapter 6: Configuration of the MQ Agents ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ For ITM, the WebSphere MQ Configuration product code is: and the WebSphere MQ Monitoring product code is: mc mq The hostname information for the TEMS in the Windows system is: ip-9-30-145-168.svl.ibm.com Thus, it is necessary to provide the hostname when asked the question: TEMS Host Name for IPv4 (Default is: ip-9-30-145-0): ip-9-30-145-168.svl.ibm.com - Configure the MQ Configuration Agent (product code: mc) /opt/ibm/itm/bin/itmcmd config -A mc Agent configuration started... Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): 1 Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: ip-9-30-145-0): ip-9-30-145-168.svl.ibm.com IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Disable HTTP? [1=YES, 2=NO] (Default is: 2): 1 Agent configuration completed... - Configure the default MQ Monitoring Agent: /opt/ibm/itm/bin/itmcmd config -A mq Agent configuration started... Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1):
Page 20 of 26 Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: ip-9-30-145-0): angelillo.raleigh.ibm.com IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Disable HTTP? [1=YES, 2=NO] (Default is: 2): 1 Agent configuration completed... As a reminder, you should restart appropriate instance(s) for new configuration settings to take effect.
Page 21 of 26 ++ Configure a dedicated MQ Monitoring Agent for the queue manager QM_LNX1 Issue the following command: /opt/ibm/itm/bin/itmcmd config -A -o QM_LNX1 mq Agent configuration started... Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): Network Protocol [ip, sna, ip.pipe, ip.spipe, ip6, ip6.pipe or ip6.spipe] (Default is: ip.pipe): Now choose the next protocol from one of these: - ip - sna - ip.spipe - ip6 - ip6.pipe - ip6.spipe - 0 for none Network Protocol 2 (Default is: 0): TEMS Host Name for IPv4 (Default is: ip-9-30-145-0): ip-9-30-145-168.svl.ibm.com IP.PIPE Port Number (Default is: 1918): Enter name of KDC_PARTITION (Default is: null): Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): Enter Optional Primary Network Name or 0 for "none" (Default is: 0): Disable HTTP? [1=YES, 2=NO] (Default is: 2): 1 Agent configuration completed... As a reminder, you should restart appropriate instance(s) for new configuration settings to take effect.
Page 22 of 26 *** *** ATTENTION! *** *** At this point, the cfg file for the MQ Monitoring Agent for the queue manager QM_LNX1 has NOT been created! You will need to start and stop the agent in order to create such file. The generated cfg file needs to have additional important customization, which is done in the next section. Start the agent: +++ROOT+++ SUSE-host3: /opt/ibm/itm/config # /opt/ibm/itm/bin/itmcmd agent -o QM_LNX1 start mq Processing. Please wait... Starting WebSphere MQ Monitoring Agent instance: QM_LNX1... Agent Started... Stop the agent: +++ROOT+++ SUSE-host3: /opt/ibm/itm/config # /opt/ibm/itm/bin/itmcmd agent -o QM_LNX1 stop mq Processing. Please wait... Stopping WebSphere MQ Monitoring Agent... Product WebSphere MQ Monitoring Agent was stopped gracefully. Agent stopped... ++ Customization of the configuration files for MQ Agents. + Modify configuration file that was created for the queue manager QM_LNX1, to indicate the name of the queue manager: Filename: /opt/ibm/itm/config/hostname_queuemanager.cfg In this case it is: /opt/ibm/itm/config/ip-9-30-145-0_mq_qm_lnx1.cfg Edit the cfg file: vi /opt/ibm/itm/config/ip-9-30-145-0_mq_qm_lnx1.cfg
Page 23 of 26 You will need to add a statement for SET AGENT and provide the name of the host. The "SET AGENT" is useful to refine the identification of a queue manager. It is not necessary in all cases, but it is a good idea to set it always. But it is needed in 2 situations: - When working with multi-instance queue managers. - When doing remote monitoring. The attribute STATISTICSINFO(REMOVE) for "SET MANAGER" is needed in order for the MQ agent to query the statistics messages generated by the MQ queue manager, when the generation of the statistics has been enabled. Here are the customized lines: SET MANAGER NAME(QM_LNX1) STATISTICSINFO(REMOVE) SET QUEUE NAME(*) MGRNAME(QM_LNX1) QDEFTYPE(PREDEFINED) SET CHANNEL NAME(*) MGRNAME(QM_LNX1) SET AGENT NAME(9.30.145.0)
Page 24 of 26 ++ Modify the mc.ini and mq.ini configuration files (WebSphere MQ 7.1 or later): Specify the library path of WebSphere MQ in the mc.ini file. See Specifying WebSphere MQ library path (WebSphere MQ 7.1 or later). https://www.ibm.com/support/knowledgecenter/ss3jrn_7.2.1.1/com.ibm.itcama.doc_7.2.1.1/install_guide/t_config_kmc_wmq71_unix.html?lang=en Tivoli Composite Application Manager for Applications 7.2.1.1>ITCAM Agents for WebSphere Messaging 7.3>Installation and Setup Guide>Configuring an agent>configuring an agent on UNIX and Linux systems>configuring ITCAM configuration agent for WebSphere MQ > Specifying WebSphere MQ library path (WebSphere MQ 7.1 or later) + begin excerpt If you are using WebSphere MQ 7.1 or later, you must specify the library path of WebSphere MQ for the agent to configure version 7.1 or later queue managers. Add the WebSphere MQ library path to the following variables in the mc.ini file. If you have multiple versions of WebSphere MQ installed, add the library path of the latest version to the parameter. Linux/Solaris/HP-UX (without WebSphere MQ 7.0.1): Add $WMQINSTALL/lib: to the beginning of the LD_LIBRARY_PATH value. where WMQINSTALL is the installation path of WebSphere MQ 7.1 or later. Restart the agent instance for the changes to take effect. + end excerpt Location of mc.ini cd /opt/ibm/itm ip-9-30-145-0:/opt/ibm/itm # find. -name mc.ini -print./config/mc.ini Edit the file and add "/opt/mqm/lib:" to the LD_LIBRARY_PATH: vi /opt/ibm/itm/config/mc.ini Before: LD_LIBRARY_PATH=$ICCRTE_DIR$/$GSKLIB$:$CANDLEHOME$/$BINARCH$/ $PRODUCTCODE$/lib:$CANDLEHOME$/$ARCHITECTURE$/lib After: LD_LIBRARY_PATH=/opt/mqm/lib:$ICCRTE_DIR$/$GSKLIB$:$CANDLEHOME$/$BINARCH$/ $PRODUCTCODE$/lib:$CANDLEHOME$/$ARCHITECTURE$/lib
Page 25 of 26 + Do the same change in the mq.ini (for the MQ Agent): Edit mq.ini in /opt/ibm/itm/config to modify LD_LIBRARY_PATH and to add an important variable: vi /opt/ibm/itm/config/mq.ini 1) Add "/opt/mqm/lib:" to LD_LIBRARY_PATH Before: LD_LIBRARY_PATH=$ICCRTE_DIR$/$GSKLIB$:$CANDLEHOME$/$BINARCH$/ $PRODUCTCODE$/lib:$CANDLEHOME$/$ARCHITECTURE$/lib After: LD_LIBRARY_PATH=/opt/mqm/lib:$ICCRTE_DIR$/$GSKLIB$:$CANDLEHOME$/$BINARCH$/ $PRODUCTCODE$/lib:$CANDLEHOME$/$ARCHITECTURE$/lib 2) Add the line to indicate where is MQ code installed. KMQ_LATEST_WMQ_INSTALLPATH=/opt/mqm Save the file. + Start the agents: Start the MQ Configuration Agent: /opt/ibm/itm/bin/itmcmd agent start mc Start the MQ Monitoring Agent for the queue manager QM_LNX1 /opt/ibm/itm/bin/itmcmd agent -o QM_LNX1 start mq Processing. Please wait... Starting WebSphere MQ Monitoring Agent instance: QM_LNX1... Agent Started... + Find out the ITM processes +++ROOT+++ SUSE-host3: /opt/ibm/itm/config # ps -ef grep -i itm root 8393 1 0 10:00 pts/1 00:00:01 /opt/ibm/itm/lx8266/lz/bin/klzagent root 14491 1 0 10:03 pts/1 00:00:00 /opt/ibm/itm/lx8266/lz/bin/kcawd root 24645 1 0 10:47 pts/1 00:00:00 /opt/ibm/itm/lx8263/mc/bin/kmcrca /opt/ibm/itm/config/mc.cfg root 25148 1 0 10:47 pts/1 00:00:00 /opt/ibm/itm/lx8263/mq/bin/kmqagent /opt/ibm/itm/config/ip-9-30-145-0_mq_qm_lnx1.cfg + Now the TEP Desktop in my Windows box shows:
Page 26 of 26 A new entry for: Linux Systems - A new entry for host: ip-9-30-145-0 - A new entry for the ITM Linux OS Agent - A new entry for the ITCAM MQ agent for queue manager QM_LNX1 YEAH!! +++ end