Installation and Setup Guide - IBM - United States · Version 1.2 Fix Pack 2 Installation and Setup Guide ... Chapter 1. Introduction .....1 New in this release ... Applications on

IBM SmartCloud Monitoring - Application InsightVersion 1.2 Fix Pack 2

Installation and Setup Guide

SC27-5618-03

��

IBM SmartCloud Monitoring - Application InsightVersion 1.2 Fix Pack 2

Installation and Setup Guide

SC27-5618-03

��

NoteBefore using this information and the product it supports, read the information in “Notices” on page 83.

This edition applies to version 1, release 2, fix pack 2 of SmartCloud Monitoring - Application Insight (productnumber 5725-J97) and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corporation 2013, 2014.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

Contents

Chapter 1. Introduction . . . . . . . . 1New in this release . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . 3

Chapter 2. Installing . . . . . . . . . 5Dependencies . . . . . . . . . . . . . . 5Configuring the firewall for incoming requests to themonitoring infrastructure node . . . . . . . . 9Installing the monitoring infrastructure . . . . . 10

Installing on SmartCloud Provisioning . . . . 11Installing on Amazon EC2 . . . . . . . . 16Installing on VMware . . . . . . . . . . 20Installing on other systems . . . . . . . . 25Upgrading the monitoring infrastructure . . . 28Uninstalling the monitoring infrastructure . . . 29

Installing monitoring agents . . . . . . . . . 29Installing monitoring agents on Linux systems . 30Installing monitoring agents on Windowssystems. . . . . . . . . . . . . . . 33Configuring your monitoring agents . . . . . 35Upgrading monitoring agents . . . . . . . 47Uninstalling monitoring agents . . . . . . . 48

Starting the Application Performance Managementconsole . . . . . . . . . . . . . . . . 49

Chapter 3. Administering . . . . . . . 51Data sources . . . . . . . . . . . . . . 51Entering monitoring infrastructure commands . . . 52Entering agent commands . . . . . . . . . 52Port configuration for agents . . . . . . . . 54Access Credentials . . . . . . . . . . . . 55Changing the apmadmin password . . . . . . 55

Managing applications. . . . . . . . . . . 56Advanced Configuration . . . . . . . . . . 58

Chapter 4. Troubleshooting . . . . . . 65Installation troubleshooting . . . . . . . . . 65

Agent installation fails. . . . . . . . . . 65Recovering from an interrupted monitoringinfrastructure node upgrade . . . . . . . . 66

Getting Started links blocked in Chrome. . . . . 67My Components application. . . . . . . . . 67Dashboard error occurred while loading data . . . 68Dashboards show no data, partial data, or incorrectdata from the monitoring agent. . . . . . . . 69Dashboard shows no events or event status . . . 70Threshold events have unknown severity after agentrecycle . . . . . . . . . . . . . . . . 71Thresholds are not applied to the monitoring agent 71Changed language but some text is still in English 71Locale support . . . . . . . . . . . . . 72Collecting monitoring infrastructure logs for IBMSupport . . . . . . . . . . . . . . . 73Collecting monitoring agent logs for IBM Support 76

Privacy policy considerations . . . . . 79

Accessibility . . . . . . . . . . . . 81

Notices . . . . . . . . . . . . . . 83Trademarks . . . . . . . . . . . . . . 86

Index . . . . . . . . . . . . . . . 89

© Copyright IBM Corp. 2013, 2014 iii

iv IBM SmartCloud Monitoring - Application Insight: Installation and Setup Guide

Chapter 1. Introduction

Read the introductory topics to learn about what's new in this release and to getan overview of the SmartCloud Monitoring - Application Insight features andinfrastructure.

New in this releaseReview the latest enhancements to IBM® SmartCloud Monitoring - ApplicationInsight since the release of Version 1.2 Fix Pack 1.

Version 1.2 Fix Pack 2

Support for new monitoring agentsMonitoring Agent for PHP, Monitoring Agent for PostgreSQL, andMonitoring Agent for Python are available with IBM SmartCloudApplication Performance Management Standard Edition and with IBMApplication Performance Management (SaaS).

Support has been added to the lightweight infrastructure for the new

agents. Click Help > Documentation to access reference informationfor each agent.

IPv6 supportIn previous releases IPv4 was supported for the IP addresses of yourmanaged systems and monitoring infrastructure node. You can now useIPv6 formatted addresses as well as IPv4.

No need to uninstall Version 1.2 Fix Pack 1 lightweight monitoringinfrastructure before upgrade

When upgrading from Version 1.2 Fix Pack 1 to Version 1.2 Fix Pack 2, youcan run the installer without first having to uninstall the Version 1.2monitoring infrastructure node. However, if you are upgrading fromVersion 1.2 or earlier, you must first uninstall the infrastructure node. Formore information, see “Uninstalling the monitoring infrastructure” on page29.

The Monitoring Agent for WebSphere® Applications now supportsupgrades. You are no longer required to uninstall previous versions of thisagent before installing the version shipped with the Version 1.2 Fix Pack 2consumer VM. For information about installing the WebSphereApplications agent, see Installing Agent for WebSphere Applications(http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_install/installingagentforwebsphereapplications.html) in IBM Monitoring Agent forWebSphere® Applications Installation and Configuration Guide.

Version 1.2 Fix Pack 1

The lightweight monitoring infrastructure must be uninstalled before upgradeWhen upgrading from Version 1.2 or earlier to Version 1.2 Fix Pack 1, youmust first uninstall the monitoring infrastructure. For more information,see “Uninstalling the monitoring infrastructure” on page 29.

Monitoring agents from the SmartCloud Monitoring - Application InsightVersion 1.2 consumer VM are automatically upgraded during installation

© Copyright IBM Corp. 2013, 2014 1

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_install/installingagentforwebsphereapplications.html

of the Version 1.2 Fix Pack 1 consumer VM. Any customization for theagent, such as thresholds defined in the Threshold Manager, is retained.The exception is the Monitoring Agent for WebSphere Applications, whichdoes not support upgrades. If you have a previous version of this agent,you must uninstall it before installing the version shipped with the Version1.2 Fix Pack 1 consumer VM. For information about installing theWebSphere Applications agent, see Installing Agent for WebSphereApplications (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_install/installingagentforwebsphereapplications.html) in IBM Monitoring Agent forWebSphere® Applications Installation and Configuration Guide.

Option to change the Application Performance Management consoleadministrator password during monitoring infrastructure installation

The default user name and password for logging into SmartCloudMonitoring - Application Insight is apmadmin apmpass.

After you start the installation script to install the lightweight monitoringinfrastructure on your Linux VM and accept the license agreement, you areprompted to change the administrator password. You can keep the defaultpassword or set a new encrypted password.

Version 1.2

Monitoring infrastructure nodeThe fabric node was renamed to “monitoring infrastructure node”, andalso referred to as the “lightweight monitoring infrastructure”.

The Monitoring Agent for Linux OS is no longer included with theinfrastructure node installation. The operating system monitoring agentsare installed from the consumer VM.

New user interface Application Performance Management consoleThe SmartCloud Monitoring - Application Insight user interface has beenreplaced by the same web user interface that is used by the ApplicationPerformance Management products for viewing managed system metricson dashboards.

Usage Statistics dashboardA new dashboard is available by clicking Reporting > Usage Statistics.The Usage Statistics dashboard presents the average, maximum, andminimum number of open VM systems reporting to the monitoringinfrastructure node over time. You can use these values to help analyzeVM system usage over different time periods.

Access Credentials configurationIf any managed systems are not returning monitoring data, the usercredentials might be different. Click System Configuration > AccessCredentials to update the user name and password that are required forlogging in to the system where the monitoring agent is installed.

Agent ConfigurationFor monitoring agents that can be configured, a new Agent Configurationpage is available. Click System Configuration > Agent Configurationto see a tabbed dashboard; there is one tab for each configurablemonitoring agent.

Discovery on other service delivery platformsIn an environment where you know the identity of the VMs or othersystems that you want to monitor, you can control the systems to monitor

2 IBM SmartCloud Monitoring - Application Insight: Installation and Setup Guide



by providing the host names and IP addresses in a text file. The file is usedby the monitoring infrastructure node for discovery and monitoring. Thediscovery plug-in reviews the text file periodically for any changes thatwere made to the system information. See “Configuring the infrastructurenode for other systems” on page 26.

Support was added for more monitoring agentsIn addition to the Monitoring Agent for Linux OS and Response TimeMonitoring Agent, the monitoring infrastructure node now supports theMonitoring Agent for Windows OS and Monitoring Agent for WebSphereApplications on your virtual machines.

Support was also added for three new monitoring agents: MonitoringAgent for MongoDB, Monitoring Agent for MySQL, and Monitoring Agentfor Ruby.

You can install any of these monitoring agents from the consumer VM andview them in the Application Performance Dashboard. You can select thepredefined application, “My Components”, to see key performanceindicators from your managed systems in group widgets, which you canclick to drill down to detailed KPIs. Administrators can create applicationsfor logical groupings, such as by geography or department, and createcustom thresholds and historical data configurations.

For more information about the Windows OS data source, see theApplication Performance Management console “Monitoring for WindowsOS” help topics.

OverviewEnterprises are increasingly moving to the cloud to accelerate time to market,improve serviceability, and to reduce costs. Cloud computing consumers need tomonitor their applications and workloads and quickly recognize problems.

SmartCloud Monitoring - Application Insight is a lightweight monitoring solutionthat is designed for short-term performance and availability analysis, independentof the management infrastructure, yet providing for scalability.

Application Insight is able to scale up or down elastically in keeping with theability to grow and shrink, and providing multi-tenant monitoring for mostworkload deployments. The monitoring technology can be embedded in virtualmachine base images and initiated automatically when new workloads aredeployed based on those images.

Installation is done in minutes, and you can immediately log on to the SmartCloudMonitoring - Application Insight to see the Application Performance Dashboard fora status check of your managed systems. The dashboard navigator is hierarchicalin nature, giving a status overview of the VMs that you own or have permission tosee. To learn more about your monitored resources, you can click a link in theStatus Overview tab.

Consider, for example, that your application has slow response time. The issue isrevealed in the dashboard. Starting from the top, you can follow the problemdown to the source by clicking links and group widgets to discover the culprit,such as high CPU usage on the VM due to an out-of-control process.

The Application Insight lightweight infrastructure is installed on a managementVM called the monitoring infrastructure node (also referred to as infrastructure node).

Chapter 1. Introduction 3

The application monitoring software is installed on consumer VMs. After you installthe monitoring software on the VMs that you want to use as base library images,you can instantiate VMs that have the monitoring software installed and ready torun. You can install more than one instance of the infrastructure node across yourenterprise, and cloud consumers can each have a separate instance of theinfrastructure node. The monitoring agents are autonomous and have noinfrastructure other than what is provided by the infrastructure node for datasharing. Both the performance and size footprint on individual nodes is small.Data retention is local and short term.

Go to IBM Service Management Connect to get usage tips and insightfulinformation from subject matter experts, ask questions on the forum, and see videodemonstrations: IBM SmartCloud® Monitoring - Application Insight(https://www.ibm.com/developerworks/servicemanagement/apm/sim/index.html). More information is available at IBM Application PerformanceManagement > Application Monitoring (http://www-01.ibm.com/software/tivoli/products/application-monitoring).

Figure 1. SmartCloud Monitoring - Application Insight users and cloud provider users. In this conceptual illustration, thecloud consumers are operations, development operations, and line of business personnel. They might create their ownVM instances or request them. They can monitor their own workloads with the Application Insight dashboards.


https://www.ibm.com/developerworks/servicemanagement/apm/sim/index.html

http://www-01.ibm.com/software/tivoli/products/application-monitoring

http://www-01.ibm.com/software/tivoli/products/application-monitoring

Chapter 2. Installing

Install and configure your SmartCloud Monitoring - Application Insightenvironment through your Amazon EC2, IBM SmartCloud Provisioning, orVMware cloud service provider.

You can also install the environment on a stand-alone system, and installmonitoring agents on the VMs and computers that are running on Linux orWindows systems.

Attention: To install the lightweight monitoring infrastructure and monitoringagents, you must run Linux as the root user or run Windows as the administrator.

DependenciesSmartCloud Monitoring - Application Insight is installed on systems or on VMsthat were instantiated from a Linux image or Windows image (consumer VMonly). Review the dependencies to ensure a successful installation.

Software Product Compatibility Reports

For up-to-date information about supported cloud service providers, operatingsystems, and browsers, and the prerequisites, review the Software ProductCompatibility Reports.

Software Product Compatibility Reports > IBM SmartCloud Monitoring -Application Insight > Monitoring Infrastructure Node

Software Product Compatibility Reports > IBM SmartCloud Monitoring -Application Insight > Consumer VM

Time zone

Use NTP (Network Time Protocol) on managed systems and on the system wherethe monitoring infrastructure node is installed to ensure that the time is accurate.The time zone must be set correctly for the time zone that the system is in, such asUTC-03:00 for Brasilia and UTC +06:30 for Yangon.

Linux dependencies

RPM dependenciesThe monitoring infrastructure node and the monitoring agents it supportsuse Red Hat Package Manager (RPM) files to install the software. Thetables list the dependencies that the RPMs have for a successfulinstallation. Without the required libraries and other software, theprerequisite scanner fails and displays a failure explanation, such as:Expected Property Result Foundregex(libstdc++.so.6 os.lib.libstdc++_32 FAIL Unavailable

A Red Hat Enterprise Linux client that is correctly configured to use theyum (Yellowdog Updater, Modified) package manager can resolve andinstall any missing dependencies that are required by the RPMs. For more


http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=45117390C18C11E290EEB61F0925FE1B&duComponent=Server_452D8710C18C11E290EEB61F0925FE1B

http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=45117390C18C11E290EEB61F0925FE1B&duComponent=Server_452D8710C18C11E290EEB61F0925FE1B

http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=45117390C18C11E290EEB61F0925FE1B&duComponent=Miscellaneous_452E2350C18C11E290EEB61F0925FE1B

http://pic.dhe.ibm.com/infocenter/prodguid/v1r0/clarity-reports/report/html/softwareReqsForProductByComponent?deliverableId=45117390C18C11E290EEB61F0925FE1B&duComponent=Miscellaneous_452E2350C18C11E290EEB61F0925FE1B

information on yum commands, see What is yum? How do I use it?(https://access.redhat.com/site/solutions/9934).

Tips for resolving unmet dependenciesWhen the prerequisite scanner returns errors because of faileddependencies, you can run the yum provides feature_name command tolearn what is required, and the yum install feature_name command toinstall the missing dependency.

For example:

Error The prerequisite scanner shows the following failure message:error: Failed dependencies:libstdc++.so.6 is needed by...

Command “yum provides”Enter the following command:yum provides libstdc++.so.6

The following report is displayed:libstdc++-4.4.7-3.el6.i686 : GNU Standard C++ LibraryRepo : installedMatched from:Other : Provides-match: libstdc++.so.6

Command “yum install”Enter the following command to satisfy the missing feature:yum install libstdc++-4.4.7-3.el6.i686

Table 1. Sample error messages for failed dependencies on Linux and the possibleresolution RPM

Error message Possible resolution

error: Failed dependencies:libstdc++.so.6 is needed by...

rpm -Uhv libstdc++-4.4.6-4.el6.i686.rpm

error: Failed dependencies:libgcc_s.so.1 is needed by

libstdc++-4.4.6-4.el6.i686libgcc_s.so.1(GCC_3.0) is

needed by libstdc++-4.4.6-4.el6.i686libgcc_s.so.1(GCC_3.3) is

needed by libstdc++-4.4.6-4.el6.i686libgcc_s.so.1(GCC_4.2.0) is

needed by libstdc++-4.4.6-4.el6.i686libgcc_s.so.1(GLIBC_2.0) is

needed by libstdc++-4.4.6-4.el6.i686

rpm -Uhv libgcc-4.4.6-4.el6.i686.rpm

error: Failed dependencies:compat-libstdc++-33(i686) is neededby...

rpm -Uhv compat-libstdc++-33-3.2-69.el6.i686.rpm

Installation RPMs for reference

Table 2. RPMs shipped with the monitoring infrastructure node and installed automatically

RPM Description

ibm-java-x86_64-jre-7.0-4.0.x86_64.rpm Java™ runtime environment for themonitoring infrastructure node

smai-1.2-1.el6.x86_64.rpm monitoring infrastructure node


https://access.redhat.com/site/solutions/9934

Table 2. RPMs shipped with the monitoring infrastructure node and installedautomatically (continued)

RPM Description

smai-apmui-1.2-1.el6.x86_64.rpmsmai-ai-apmui-1.2-1.el6.x86_64.rpm

Application Performance Managementconsole and SmartCloud Monitoring -Application Insight features

smai-iehs-1.2-1.el6.x86_64.rpm Eclipse help server

smai-itmcdp-1.2-1.el6.x86_64.rpm SmartCloud Monitoring Application Insightdashboard data provider

smai-oslc-pm-06.35.00.00-1.el6.x86_64.rpm

OSLC (Open Services for LifecycleCollaboration) for establishing applicationrelationships

smai-scr-6.1.2-1.el6.x86_64.rpm Service Component Repository for resource,attribute, and relationship information

smai-server1-1.2-1.el6.x86_64.rpm Server1 application server, which runs theSmartCloud Monitoring Application Insightdashboard data provider and some ServiceComponent Repository components

Table 3. Java RPM bundled with the monitoring infrastructure node

RPM RequirementsCommands to install missingdependencies

smai-framework-jre-07.04.02.00-1.el6.x86_64.rpm

glibc2.3 (or later)libstdc++.so.6

yum install library_name

If you are not able to use yum, you cansearch the Internet for and downloadthe required RPMs individually, andinstall them manually with thefollowing command, replacingrpm_filename with the actual filename:rpm -Uhv rpm_filename

Table 4. RPMs shipped with the Linux consumer VM software

RPM Description


Java runtime environment requires KSH andis required by the monitoring agentframework

smai-framework-core-06.35.02.00-1.el6.x86_64.rpm

Monitoring agent framework

smai-os-06.30.02.20-1.el6.x86_64.rpm Monitoring Agent for Linux OS

smai-mongodb-01.00.02.00-1.el6.noarch.rpm

Monitoring Agent for MongoDB

smai-mysql-01.00.02.00-1.el6.noarch.rpm Monitoring Agent for MySQL

smai-ruby-01.00.02.00-1.el6.noarch.rpm Monitoring Agent for Ruby

smai-response_time-07.40.00.06-1.el6.x86_64.rpm

Response Time Monitoring Agent

smai-apd-was-07.30.02.00-1.el6.x86_64.rpm

Monitoring Agent for WebSphereApplications

Chapter 2. Installing 7

Table 5. RPMs shipped with the Linux extended consumer VM software

RPM Description


Java runtime environment requires KSH andis required by the monitoring agentframework

smai-framework-core-06.35.03.00-1.el6.x86_64.rpm

Monitoring agent framework

smai-php-01.00.01.00-1.el6.noarch.rpm Monitoring Agent for PHP

smai-postgresql-01.00.01.00-1.el6.noarch.rpm

Monitoring Agent for PostgreSQL

smai-python-01.00.01.00-1.el6.noarch.rpm Monitoring Agent for Python

Hardware requirements based on agent load

The results of scale testing indicate that a monitoring infrastructure node installedon a VM with the minimum requirements that are shown in the following tablecan support up to 10 concurrent users.

Table 6. Memory, processor, and storage requirements based on agent load

Fewer than 500 monitoringagents

Between 500 and 1000monitoring agents

Free memory 4 GB 8 GB

Number of processors 2 4

Available disk space 20 GB 20 GB

Swap space 4 GB 4 GB

Attention: Although at least 8 GB of free memory is required if you plan to havemore than 500 agents, there is no way to know how many monitoring agents youplan to have. The prerequisite scanner displays a message about increasing thememory only if memory is under 4 GB.

Prerequisite scanner

After you start the installation script for the monitoring infrastructure node, aprerequisite scanner runs automatically and displays the results, including the pathto a log file that you can review if any of the prerequisites are not met. An out ofdate library or insufficient disk space stops the installation. You must address themissing prerequisite before you can start the installation again. A “soft”prerequisite, such as low available memory, does not stop the installation, but isdisplayed in the results.

Certain ports must be available before you begin installing the monitoringinfrastructure node. The prerequisite scanner checks if they are available andreturns FAIL for each port that is not available:

Table 7. Available ports for installation

Port Description

80 Central Configuration Server

1527 Service Component Repository database

6414 Monitoring infrastructure node database


Table 7. Available ports for installation (continued)

Port Description

8080 Application Performance Management console

9998 EIF receiver

10001 OSLC provider

12315 Service Component Repository Java run time

32105 Internal messages

If a firewall is blocking the ports, you can either configure the firewall to allowtraffic on certain ports or disable the firewall. For more information, see“Configuring the firewall for incoming requests to the monitoring infrastructurenode.”

For an example of prerequisite scanner results, see Dependencies in theSmartCloud Monitoring - Application Insight information center.

User credentials and ports for agent access

User credentialsThe Configuration Wizard and Advanced Configuration pages have fieldsfor setting three sets of default user credentials for accessing managedsystems:v Default user credentialsv Linux operating system user credentialsv Windows operating system user credentials

These settings are for your convenience. Typically, you would set the mainuser credentials for the operating system credentials that are used mostoften to access the managed systems in your environment.

If you have set the Linux and Windows default credentials, the monitoringinfrastructure node determines the credentials to use for accessing amonitoring agent by the OS agent that is installed on that managedsystem. If, however, no OS agent is installed on the managed system, themain default user credentials are used.

For more information, see the options for Default VM Credentials,Default Linux VM Credentials, and Default Windows VM Credentials in“Advanced Configuration” on page 58.

If the default user credentials are not valid for a particular managedsystem, use the Access Credentials page to enter the correct credentials forthat managed system. For more information, see “Access Credentials” onpage 55.

HTTP and HTTPS portsIf you have a firewall that is enabled, ensure that port 51920 for HTTP or53661 for HTTPS (or both) is open in the firewall on each managed system.

Configuring the firewall for incoming requests to the monitoringinfrastructure node

Before installing SmartCloud Monitoring - Application Insight in your cloudenvironment, either temporarily disable your firewall or configure ports forincoming requests.


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_install_dependencies.htm

Before you begin

TCP connections are made between the monitoring agent and monitoringinfrastructure node. Thus, any firewall must allow connections in both directions.Typical Network Address Translation (NAT) configurations do not allow suchconnections and are not supported. For more information about firewallconfiguration, see the documentation for your cloud service provider:

SmartCloud Provisioning 2.1 - Managing the firewall (http://pic.dhe.ibm.com/infocenter/tivihelp/v48r1/topic/com.ibm.scp.doc_2.1.0/ICON/topics/cicn_firewallports.html)Amazon EC2 Security Groups (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)VMware documentation (http://www.vmware.com/support/pubs/)

About this task

Take one of the following steps to either open ports or disable the firewall:

Procedurev Set your cloud firewall for incoming requests on ports used by SmartCloud

Monitoring - Application Insight. Ensure that the following ports are free (noapplication is listening on them):– 80– 443– 1527– 4443– 6414– 8080– 9998– 10001– 12315– 32105

v Disable your cloud firewall and run the following Red Hat Linux commands:service iptables stopchkconfig iptables off

If IPv6 (Internet Protocol Version 6) is enabled, also run the followingcommands:service ip6tables stopchkconfig ip6tables off

What to do next

Install the monitoring infrastructure node and monitoring agents.

Installing the monitoring infrastructureThe monitoring infrastructure node provides the lightweight infrastructure for theApplication Performance Management console. You can install the monitoringinfrastructure before or after installing monitoring agents.


http://pic.dhe.ibm.com/infocenter/tivihelp/v48r1/topic/com.ibm.scp.doc_2.1.0/ICON/topics/cicn_firewallports.html

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html

http://www.vmware.com/support/pubs/

Before you begin

After you obtain the monitoring infrastructure node installation media (seeDownload instructions), decompress the archive file, and start the installation, aprerequisite checker reviews your Red Hat Enterprise Linux system to ensure thatit meets the software, memory, and disk requirements. Any missing prerequisitesare shown in a message. An absolute prerequisite, such as an out of date library orinsufficient disk space, stops the installation. You must address the missingprerequisite before you can start the installation again. A “soft” prerequisite, suchas low available memory, does not stop the installation, but is displayed in amessage. For more information, see “Dependencies” on page 5.

About this task

Complete the instructions for your service provider or on premise environment toinstall and configure the monitoring infrastructure node:

Procedurev “Installing the infrastructure node in SmartCloud Provisioning”v “Installing the infrastructure node in Amazon EC2” on page 16v “Installing the infrastructure node in VMware” on page 20v “Installing the infrastructure node on other systems” on page 25

What to do next

If you have agents to install for monitoring your applications, complete theinstructions in “Installing monitoring agents” on page 29.

Installing on SmartCloud ProvisioningAfter registering with IBM SmartCloud Provisioning, install SmartCloudMonitoring - Application Insight in your environment to monitor your virtualmachines.

Installing the infrastructure node in SmartCloud ProvisioningThe monitoring infrastructure node provides the management services forSmartCloud Monitoring - Application Insight.

To install the infrastructure node, you first must have a VM image instantiated inSmartCloud Provisioning. Then, you can log in to the deployed VM and install theinfrastructure node for managing the monitoring agents.

Before you beginv Review the Prerequisites (http://publib.boulder.ibm.com/infocenter/tivihelp/

v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_prerequisites.htm) and“Dependencies” on page 5 for the supported platforms and requirements formonitoring infrastructure nodes.

v The infrastructure node installation media is named differently depending onwhere you obtained the file. Replace the name of the MIN_Media.tar in theinstructions with the name of the file that you downloaded:– When downloaded for trial evaluation, the file is

MonitoringInfrastructureNode.tar

– When downloaded from IBM Passport Advantage, the file is a part numbersuch as CIY2IML.tar


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_prerequisites.htm

v You must run as the root user to install the monitoring infrastructure node.

About this task

Take the following steps to instantiate the infrastructure node VM in SmartCloudProvisioning and install the infrastructure node software on the deployed VM. Theinstallation step involves downloading the infrastructure node tar file, unpackingthe tar file on the VM, and running the installation script.

Procedure1. Instantiate an infrastructure node VM from a Red Hat Enterprise Linux on

Intel/AMD VM image. The IP address is used to log in to the VM for installingthe infrastructure node software (step 3) and to start the ApplicationPerformance Management console. In the Deployed VMs tab, make a note ofthe IP address of the infrastructure node. You might also want to keep signedin to SmartCloud Provisioning if you are ready to configure the infrastructurenode after installing it.

2. Set Security-Enhanced Linux to permissive mode:setenforce 0getenforce

The setenforce 0 command turns off SELinux; and the getenforce commandreports the current SELinux mode.

3. Install the infrastructure node software on the deployed VM:a. Download the infrastructure node installation file from the following

download site to a staging location of your choosing: IBM SmartCloudMonitoring - Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Download instructions


https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI



(http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

b. Start an SSH (secure shell) connection and log in to the VM that youinstantiated in step 1 on page 12.v For example, enter ssh root@MIN_IPAddress where MIN_IPAddress is the

IP address of the VM (SmartCloud Provisioning Resources page,Deployed VMs tab, in the Private Address column).

v If you are using an SSH client, start the utility to get a dialog box forlogging in with the infrastructure node VM IP address.

c. Copy the infrastructure node installation file from the staging area to theVM with the following command:scp user@hostname:/path/MIN_Media.tar .

whereuser is your user ID for the staging location,hostname is the fully qualified host name of the staging location,/path/ is the path to the download directory, andMIN_Media is the name of the archive file.

d. Extract the infrastructure node installation files:tar -xf MIN_Media.tar

where MIN_Media is the name of the archive file.e. Run the installation script to install the infrastructure node software on the

VM:./install.sh

A prerequisite scan of your environment starts and takes a few moments tocomplete. If any requirements are missing, a message directs you to a logfile with the reason for the failure. A prerequisite such as a missing libraryor insufficient disk space stops the installation. You must address the failureand start the installation again. A “soft” prerequisite such as low availablememory does not stop the installation but you must enter 1 to continueinstalling or 2 to stop. For more information, including the yum providesfeature_name and yum install feature_name commands, see“Dependencies” on page 5.

f. If the International Program License Agreement is displayed for you to read,you can press Enter to read the next screen of text, enter 1 to accept theagreement, 2 to decline it, 3 to print it, or 99 to go back to the previousscreen.

g. After you are prompted to change the default password for theadministrator account, enter either 1 (yes) and create a new encryptedpassword or 2 (no) to keep the default “apmpass” unencrypted password. Ifyou change the password, keep a copy in a safe place; you cannot recoverthe password if you forget it. After you answer the prompt to change theSmartCloud Monitoring - Application Insight administrator password, theinstallation continues. The component and support file names are displayedas they are installed.

4. After installation is complete and the command prompt is available, you canset SELinux back to enforcing mode:setenforce 1getenforce


Results

The infrastructure node is installed on the deployed VM.

What to do nextv You can log in to SmartCloud Monitoring - Application Insight to complete the

configuration, as described in “Configuring the infrastructure node forSmartCloud Provisioning.”

v You can also install monitoring agents on consumer VMs, as described in“Installing monitoring agents” on page 29.

Configuring the infrastructure node for SmartCloud ProvisioningAfter installing the monitoring infrastructure node on your deployed VM, youmust configure the infrastructure node for communication with the SmartCloudProvisioning service delivery platform.

The Configuration Wizard starts automatically the first time you log in toSmartCloud Monitoring - Application Insight after installation. Thereafter, you canstart the wizard whenever you have configuration changes.

Before you begin

Initial configuration of the infrastructure node involves establishing key credentialswith the web service host, starting the database, and initializing the configurationdatabase. Most of the configuration is automatic after the private key has beenestablished.

Have at hand the information that is required from SmartCloud Provisioning forconfiguring the monitoring infrastructure node: the SmartCloud Provisioning webhost IP address, your access ID, and the private key that is associated with yourID.

Procedure1. If you are not already logged in to SmartCloud Monitoring - Application

Insight, enter the following URL where APMUI_host is the IP address of theinfrastructure node VM: https://APMUI_host:9443 The default user ID andpassword are apmadmin and apmpass.

2. If the Configuration Wizard is not open, click System Configuration >Configuration Wizard.

3. For the service delivery platform, select the SmartCloud Provisioning optionand click Next.

4. For the SmartCloud Provisioning platform configuration, complete thefollowing fields and click Next:a. Access ID is shown on the SmartCloud Provisioning Home page after you

sign in.b. Web Service Host is the IP address of the SmartCloud Provisioning host.c. Web Service Port is set to the default 5678.d. Service Region is the region hosted by SmartCloud Provisioning, and is set

to “query” by default.e. Private Key is pasted from SmartCloud Provisioning Home page by

clicking Show Access Key, copying the entire Private Key text including the-BEGIN- and -END- lines, and pasting here.


5. When a message prompts you to set up event notification email, click Yes toopen the Advanced Configuration page to establish event notification now, orclick No.

6. If you clicked Yes to set up event notification email or event forwarding to anevent integration facility (EIF), complete the Event Manager fields.v For forwarding to one or more EIF receivers, you must know the IP address

(IPv4 only) or fully qualified host name of the EIF receiver. Use a comma (,)to separate multiple receivers.

v For sending event notification emails, you must have a configured SMTPserver, the credentials to communicate with it, and the proper port to beconfigured on any firewalls that reside between the cloud and your SMTPserver. Use a comma (,) to separate multiple target email addresses.

v For more information, see the Event Manager options in “AdvancedConfiguration” on page 58.

7. Optional. In the Default tab, enter the default user ID and password for themost commonly used monitoring agent in your workload:a. User ID, such as root.b. Password, such as passw0rd.c. Confirm Password.d. Repeat for the Linux and Windows tabs to enter a default user ID and

password for the monitoring agents that run on those operating systems.

Results

After you click Finish, the configuration parameters are updated on theinfrastructure node.

What to do nextv Install consumer VMs, as described in “Installing monitoring agents on Linux

systems” on page 30 and “Installing monitoring agents on Windows systems” onpage 33.


v Click Performance > Application Performance Dashboard and add a newapplication as described in “Managing applications” on page 56.

v Click System Configuration > Threshold Manager to create thresholds thattest for conditions that you want to monitor and raise an event when keyperformance indicators exceed the threshold.

v Click System Configuration > Historical Data Configuration to see andwork with historical data configurations for data sets that you want to seehistorical data from.

v If you change the service delivery platform type (also referred to as thediscovery plug-in), you must log into the VM where the infrastructure node isinstalled and issue these commands:1. stop fabricNode

2. stop server1

3. start fabricNode

4. start server1

These commands do not have to be entered the first time that you select aservice delivery platform type. They must be entered only if you change fromone type to a different type.

Related reference:“Advanced Configuration” on page 58

Installing on Amazon EC2Install SmartCloud Monitoring - Application Insight in your Amazon ElasticCompute Cloud (EC2) provisioning environment, and begin using it to monitoryour machine images.

Installing the infrastructure node in Amazon EC2The monitoring infrastructure node provides the management services forSmartCloud Monitoring - Application Insight.

To install an infrastructure node, you first must start a Linux instance in AmazonEC2. Then, you can log in to the instance and install the infrastructure node formanaging the consumer VM.







About this task

Take the following steps to instantiate an infrastructure node VM in Amazon EC2and install the infrastructure node software on the deployed VM. The installation



step involves downloading the infrastructure node archive file, unpacking theinstallation files on the VM, and running the installation script.

Procedure1. Start a Linux instance from a Red Hat Enterprise Linux on Intel/AMD VM

image.2. Download the infrastructure node installation file from the following download

site to a staging location of your choosing: IBM SmartCloud Monitoring -Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Downloadinstructions (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

3. Start an SSH (Secure Shell) connection and log in to the instance that youstarted in step 1.v For example, enter ssh root@MIN_IP_Address where MIN_IP_Address is the IP

address of the VM.v This step requires key pair configuration on the SSH client. For more details,

see Connecting to Amazon EC2 Instances (http://docs.amazonwebservices.com/AWSEC2/latest/UserGuide/AccessingInstances.html).

v If you are using an SSH client, start the utility to get a dialog box for loggingin with the infrastructure node VM IP address.

4. Install the Amazon Software Development Kit for Java:a. Create the following directory: /opt/ibm/ccm/lib.b. Download the Amazon SDK for Java from http://aws.amazon.com/

sdkforjava.c. Extract the SDK files.d. Change to the aws-java-sdk-1.3.15/lib directory and copy the SDK JAR

file to /opt/ibm/ccm/lib with the following command:cp aws-java-sdk-1.3.15.jar /opt/ibm/ccm/lib/aws-java-sdk-1.3.15.jar

e. If the version of the downloaded Amazon SDK for Java is newer than1.3.15, copy the JAR file under aws-java-sdk-*/lib to /opt/ibm/ccm/liband rename it to aws-java-sdk-1.3.15.jar

5. Set Security-Enhanced Linux to permissive mode:setenforce 0getenforce


6. Install the infrastructure node software on the Linux instance:a. Copy the infrastructure node installation media from the staging area (step

2) to a directory of your choice on the Linux instance.b. Extract the infrastructure node installation files:

tar -xf MIN_Media.tar

where MIN_Media is the name of the archive file.c. Run the installation script to install the infrastructure node software on the

VM:./install.sh






http://docs.amazonwebservices.com/general/latest/gr/rande.html#ec2_region

http://aws.amazon.com/sdkforjava

http://aws.amazon.com/sdkforjava


d. If the International Program License Agreement is displayed for you toread, you can press Enter to read the next screen of text, enter 1 to acceptthe agreement, 2 to decline it, 3 to print it, or 99 to go back to the previousscreen.

e. After you are prompted to change the default password for theadministrator account, enter either 1 (yes) and create a new encryptedpassword or 2 (no) to keep the default “apmpass” unencrypted password. Ifyou change the password, keep a copy in a safe place; you cannot recoverthe password if you forget it. After you answer the prompt to change theSmartCloud Monitoring - Application Insight administrator password, theinstallation continues. The component and support file names are displayedas they are installed.



configuration, as described in “Configuring the infrastructure node for AmazonEC2.”


Configuring the infrastructure node for Amazon EC2After installing the monitoring infrastructure node on your deployed VM, youmust configure the infrastructure node for communication with the Amazon ElasticCompute Cloud service delivery platform.

The configuration wizard starts automatically the first time you log in toSmartCloud Monitoring - Application Insight after installation. Thereafter, you canstart the wizard whenever you have configuration changes.

Before you begin

Log on to your Amazon Web Service Management Account (http://aws.amazon.com/console) and gather the following information for entry in step 4on page 19:v Your Access Key ID and Secret Access Key as described in Getting Your AWS

Access Keys (http://docs.aws.amazon.com/ses/latest/DeveloperGuide/get-aws-keys.html).

v Your entry point URL, which is based on your Region (shown in the Navigationarea) and listed in the table at Regions and Endpoints - Amazon EC2(http://docs.amazonwebservices.com/general/latest/gr/rande.html#ec2_region).


http://aws.amazon.com/console

http://aws.amazon.com/console

http://docs.aws.amazon.com/ses/latest/DeveloperGuide/get-aws-keys.html

http://docs.aws.amazon.com/ses/latest/DeveloperGuide/get-aws-keys.html

http://docs.amazonwebservices.com/general/latest/gr/rande.html#ec2_region

Review the Prerequisites (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_prerequisites.htm) andDependencies (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_install_dependencies.htm) for the supportedplatforms and requirements for infrastructure nodes.




3. For the service delivery platform, select the Amazon Elastic Compute Cloudoption and click Next.

4. For the Amazon EC2 platform configuration, complete the following fields andclick Next:a. Access Key ID is the Amazon Web Services Access Key ID for accessing

AWS SES.b. Secret Access Key is the Secret Access Key for accessing AWS SES.c. Confirm Secret Access Key is the Secret Access Key, which you enter a

second time to ensure that you typed the key correctly.d. Region Endpoint URL is the URL that represents the entry point for AWS

and is based on your Region, such as http://ec2.us-west-1.amazonaws.comfor US West (Northern California) Region.








Results




http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_install_dependencies.htm







2. stop server1

3. start fabricNode

4. start server1



Installing on VMwareInstall SmartCloud Monitoring - Application Insight in your environment formonitoring your VMware Virtual Machines.

Important: The monitoring infrastructure node can monitor only VMs with aknown IP address. You must have the VMware Tools installed and running on themanaged system VMs. The VMware Tools enable the VMware vCenter to learn theIP address of the VM for passing to the infrastructure node.

Installing the infrastructure node in VMwareThe monitoring infrastructure node provides the management infrastructure forSmartCloud Monitoring - Application Insight.

To install the infrastructure node, you first must have a VM image instantiated inVMware. Then, you can log in to the deployed VM and install the infrastructurenode.









About this task

Take the following steps to instantiate a infrastructure node VM in VMware andinstall the infrastructure node software on the deployed VM. The installation stepinvolves downloading the infrastructure node tar file, unpacking the tar file on theVM, and running the installation script.

Procedure1. Instantiate an infrastructure node VM from a Red Hat Enterprise Linux on

Intel/AMD VM image.2. Set Security-Enhanced Linux to permissive mode:

setenforce 0getenforce


3. Install the infrastructure node software on the deployed VM:a. Download the infrastructure node installation file from the following

download site to a staging location of your choosing: IBM SmartCloudMonitoring - Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Download instructions(http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

b. Start an SSH (secure shell) connection and log in to the VM that youinstantiated in step 1.v For example, enter ssh root@MIN_IPAddress where MIN_IPAddress is the

IP address of the VM.v If you are using an SSH client, start the utility to get a dialog box for

logging in with the infrastructure node VM IP address.c. Copy the infrastructure node installation file from the staging area.d. Extract the infrastructure node installation files:


where MIN_Media is the name of the archive file.e. To install the infrastructure node software on the VM, run the following

script:./install.sh






f. If the International Program License Agreement is displayed for you to read,you can press Enter to read the next screen of text, enter 1 to accept theagreement, 2 to decline it, 3 to print it, or 99 to go back to the previousscreen.

g. After you are prompted to change the default password for theadministrator account, enter either 1 (yes) and create a new encryptedpassword or 2 (no) to keep the default “apmpass” unencrypted password. Ifyou change the password, keep a copy in a safe place; you cannot recoverthe password if you forget it. After you answer the prompt to change theSmartCloud Monitoring - Application Insight administrator password, theinstallation continues. The component and support file names are displayedas they are installed.


Results

The infrastructure node is installed on the deployed VM.


configuration, as described in “Configuring the infrastructure node forVMware.”


Configuring the infrastructure node for VMwareAfter you install the monitoring infrastructure node on your deployed VM, youmust configure the infrastructure node for communication with the VMwareservice delivery platform.

The configuration wizard starts automatically the first time you log in toSmartCloud Monitoring - Application Insight after installation. Thereafter, you canstart the wizard whenever you have configuration changes.




3. For the service delivery platform, select the VMware Virtual Center option andclick Next.

4. For the VMware platform configuration, complete the following fields and clickNext:a. User ID is the VMware login ID.b. Password is the VMware user password.c. Confirm Password is the VMware user password, which you enter a second

time to ensure that it was typed correctly.


d. Host Name is the fully qualified host name or IP address of the VMwareservice host.

e. Port Number is set to the default 80.f. Use SSL is set to false by default, and the Keystore and Validate certificates

fields are disabled. Select true if Secure Socket Layer is used forcommunications with the VMware service host.

g. Keystore File is set to /opt/ibm/ccm/CCM-Certs/ccm.truststore by default.If Use SSL is set to true, it is necessary to add the VMware Virtual CenterSSL certificate to the default ccm.truststore. To use a keystore other thanthe default, enter the full path to the keystore file that contains the set ofcertificates that are trusted by SmartCloud Monitoring - Application Insight.Note that if the Keystore File does not exist, it is created automaticallywhen the first certificate is added.

h. Keystore Password and Keystore Confirm Password are disabled becausethe password is already established. If Use SSL is set to true, these fieldsare enabled for you to set the password.

i. Validate Certificates is set to false by default. If Use SSL is set to true, thisfield is enabled and you can set it to true to validate the SSL connectioncertificates against the certificates that are imported into the infrastructurenode truststore. For details about importing certificates, see Enablingcertificate validation for communication with VMware (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_installvmware_certificate.htm).








Results



http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_installvmware_certificate.htm

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_installvmware_certificate.htm







2. stop server1

3. start fabricNode

4. start server1



Enabling certificate validation for communication with VMwareAdministrators can set up SSL connections that require certification validation(configuration keyword validateCerts set to true) by locating the certificates andimporting them into the Java keystore. Preparing your VMware environment forSmartCloud Monitoring - Application Insight installation involves setting up SSLconnections in your cloud environment.

Before you begin

You must have access to the web console and the proper security credentials.

Procedure1. Copy the default VMware rui.crt certificate file from the system where the

VMware vCenter Server is installed. For example, the default location for theSSL certificate file on Windows is C:\Documents and Settings\AllUsers\Application Data\VMware\VMware VirtualCenter\SSL.

2. On the system where the monitoring infrastructure node is installed, import theVMware Virtual Center certificate into the infrastructure node Java keystore:a. Open the Windows command prompt or Linux shell command.b. Create the directory for the Java certificate store. The following keystore file

is the default used by Application Insight: /opt/ibm/ccm/CCM-Certs/ccm.truststore. Create the directory only: The actual keystore file is createdduring the process of importing the certificates.

c. Change to the /opt/ibm/ccm/CCM-Certs directory.d. Using the Java keytool utility, import the certificate that you created in step

1:


keytool -import -file Certificate -alias ServerName -keystore ccm.truststore

where Certificate is the name of the certificate file, and ServerName is theVMware server name. Example: keytool -import -file rui.crt -aliasVMWARE01 -keystore ccm.truststore

e. After you are prompted to enter the keystore password, type a passwordfor the keystore that you are creating. After you press Enter, the certificateinformation is displayed.

f. After you are prompted to trust the certificate at the end of the certificateinformation, type yes and press Enter. The certificate is imported into theccm.truststore keystore and a message is displayed to confirm that thecertificate was added to the keystore.

Installing on other systemsYou can install the monitoring infrastructure node on a Red Hat Enterprise Linuxsystem for monitoring your environment.

Installing the infrastructure node on other systemsThe monitoring infrastructure node provides the management services forSmartCloud Monitoring - Application Insight.

You can install the infrastructure node, on VM or computer in your network that isrunning Red Hat Enterprise Linux.







About this task

Take the following steps to install the infrastructure node on a Red Hat EnterpriseLinux system. The installation step involves downloading the infrastructure nodeinstallation media, decompressing the installation files on the system, and runningthe installation script.

Procedure1. Download the infrastructure node installation file from the following download

site to a staging location of your choosing: IBM SmartCloud Monitoring -Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Downloadinstructions (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

2. Extract the infrastructure node installation files:








where MIN_Media is the name of the archive file.3. Set Security-Enhanced Linux to permissive mode:

setenforce 0getenforce


4. Install the infrastructure node software on the VM:a. Run the following script:

./install.sh


b. If the International Program License Agreement is displayed for you toread, you can press Enter to read the next screen of text, enter 1 to acceptthe agreement, 2 to decline it, 3 to print it, or 99 to go back to the previousscreen.

c. After you are prompted to change the default password for theadministrator account, enter either 1 (yes) and create a new encryptedpassword or 2 (no) to keep the default “apmpass” unencrypted password. Ifyou change the password, keep a copy in a safe place; you cannot recoverthe password if you forget it. After you answer the prompt to change theSmartCloud Monitoring - Application Insight administrator password, theinstallation continues. The component and support file names are displayedas they are installed.


Results

The infrastructure node is installed on the system.


configuration, as described in “Configuring the infrastructure node for othersystems.”

v You can also install monitoring agents on the computers that you want tomanage, as described in “Installing monitoring agents” on page 29.

Configuring the infrastructure node for other systemsYou can use the Other discovery capability to discover and monitor any set of VMsor stand-alone systems.


Instead of using a cloud provider service to retrieve information about the systemsthat belong to a user, you can create a list of systems to be monitored in a text file.The Other discovery plug-in monitors the text file periodically for changes in thesystem information.

Before you begin

Install SmartCloud Monitoring - Application Insight in your provisioningenvironment, such as VMware, and begin monitoring your VMs.

Procedure1. Create the list of system addresses:

a. On the monitoring infrastructure node VM, create a text file (such asips.txt) in the /opt/ibm/ccm/ directory.

b. Enter each VM address that you want to monitor on a new line with thefollowing syntax:ipaddress hostname description

where:v ipaddress is the IP address of the system to be monitored, such as

9.3.2.1

v hostname is the host name of the same system, such asmywebapps.tivlab.raleigh.ibm.com

v description is the unique description of the system to be monitored,such as My web development environment.If a description is duplicated,such as “Linux” in other entries, an exception is recorded in theccm.trace.log and the system with the duplicate description might notbe available in places such as the Component Editor.

You can include spaces; quotation marks are not necessary. Lines that startwith a number sign (#) are considered commentary and ignored. Emptylines are also ignored. The

c. After you finish creating the list, save and close the text file. Make a note ofthe path and file name for setting in step 5

In the following text file example, the monitoring infrastructure node addressesare for individually monitoring the MySQL data source and the Linux OS datasource; each consumer VM address is added for monitoring the MySQL datasource and the Linux OS data source:# Entries for MIN MySQL9.77.33.11 v1234fdf602 MySQL 001 CVM9.77.33.22 v2345efe713 MySQL 002 CVM

# Entries for MIN Linux OSAgent9.77.33.33 v1234fdf602 My Infrastructure Node9.77.33.44 v2345efe713 Back Office Linux OSAgent CVM9.77.33.55 v3456efe714 R&D Linux OSAgent CVM

2. If you are not already logged in with the Configuration Wizard open, log in asdescribed in “Starting the Application Performance Management console” onpage 49.

3. If the Configuration Wizard does not open automatically, click SystemConfiguration > Configuration Wizard.

4. Select the Other option and click Next.5. Edit the path for the text file that you created earlier; click Next.









Results

The SDP adapter Other plug-in on the infrastructure node uses the address file tolocate the managed systems, maintains the monitoring agents, and gathers data fordisplay in the Application Performance Dashboard.

Important: If you change from one discovery type to another, such as fromVMware to Other, you must log into the VM where the infrastructure node isinstalled and issue these commands:1. stop fabricNode

2. stop server1

3. start fabricNode

4. start server1

You do not have to enter the commands the first time that you select a discoveryplug-in; only after you change from one type to a different type.Related reference:“Advanced Configuration” on page 58

Upgrading the monitoring infrastructureDownload the monitoring infrastructure node installation archive file fromPassport Advantage, decompress the files, and run the installation script toupgrade to the latest version.

Before you begin

When upgrading from Version 1.2 Fix Pack 1 to Version 1.2 Fix Pack 2, you canrun the installer without first having to uninstall the Version 1.2 monitoringinfrastructure node. However, if you are upgrading from Version 1.2 or earlier, youmust first uninstall the monitoring infrastructure node. For more information, see


“Uninstalling the monitoring infrastructure.”

About this task

Complete the procedure for your environment to upgrade the monitoringinfrastructure to the latest version:

Procedurev “Installing the infrastructure node in SmartCloud Provisioning” on page 11v “Installing the infrastructure node in Amazon EC2” on page 16v “Installing the infrastructure node in VMware” on page 20v “Installing the infrastructure node on other systems” on page 25

Results

The monitoring infrastructure is upgraded to the latest version after you confirmthat you want to install an updated version of the monitoring infrastructure node,agree to the terms, and enter the apmadmin password.

Uninstalling the monitoring infrastructureIf you no longer want the monitoring infrastructure node on the VM, you canuninstall it.

The infrastructure node uninstall procedure does not remove the monitoringagents.

Procedure1. On the VM or system where the infrastructure node is installed, start a

command line.2. Run the following command in the /opt/ibm/ccm directory:

uninstall.sh

Results

The infrastructure node components are uninstalled.

Installing monitoring agentsInstall a monitoring agent on the system or VM that you want to monitor.

Some monitoring agents require additional configuration, which can be automatedafter you specify the settings in a silent configuration file or can be doneinteractively, depending on the agent type and your preference.

Before you begin

After you obtain the consumer VM installation media for Linux or Windows (orboth) and decompress the archive file, you can install monitoring agents on theVMs or computers that you want to manage. You can install the monitoring agentsbefore or after the lightweight monitoring infrastructure is installed by starting theinstallation script for each type of monitoring agent that you want to install.


About this task

Follow the instructions for the operating system that the application runs on toinstall the associated monitoring agent:

Procedurev “Installing monitoring agents on Linux systems”v “Installing monitoring agents on Windows systems” on page 33

Installing monitoring agents on Linux systemsTo install a monitoring agent, you must download an archive file from the IBMdownload site, extract the agent installation files, and then start the installationscript.

You can install the following monitoring agents that run on Linux operatingsystems:v Monitoring Agent for Linux OSv Monitoring Agent for MongoDBv Monitoring Agent for MySQLv Monitoring Agent for PHPv Monitoring Agent for PostgreSQLv Monitoring Agent for Pythonv Monitoring Agent for Rubyv Response Time Monitoring Agentv Monitoring Agent for WebSphere Applications

Before you begin

The consumer VM installation archive file is named differently depending onwhere you obtained the file and which monitoring agents you are installing.Replace the name of the ConsumerVM_Media.tar in the instructions with the name ofthe file (or files) that you downloaded: When downloaded from IBM PassportAdvantage, the file isv CIY2KML.tar for the Linux OS, MongoDB, MySQL, Ruby, Response Time, and

WebSphere Applications monitoring agents;v CIY2HML.tar for the PHP, PostgreSQL, and Python monitoring agents.

.

You can install any combination of monitoring agents on a managed system. Forexample, if you install the Monitoring Agent for Ruby for monitoring Ruby OnRails applications, you might want to also install the Response Time MonitoringAgent to gather more response time information for your Ruby applications, andthe Monitoring Agent for Linux OS to monitor other aspects of the system, such asthe overall CPU, memory, and disk.

If you are installing any of the following multi-instance agents on a VM that youplan to use as the base library image, do not configure the agent beforeinstantiating the other consumer VMs: MongoDB agent, MySQL agent, PHP agent,PostgreSQL agent, Python agent, and Ruby agent. The monitoring agent must beconfigured on each instantiated VM.

The following monitoring agent prerequisites apply:


v Monitoring Agent for MySQLTo monitor a MySQL environment, the MySQL server and MySQL JDBC drivermust be installed before you install the Monitoring Agent for MySQL. To installthe JDBC driver use the following command:yum install mysql-connector-java

v Monitoring Agent for PHP– You must have an Apache HTTPD server V2.2.15 or higher installed before

you install the agent.– PHP must be at V5.3.3 or higher.– You must have an existing WordPress-based application installed. The PHP

agent monitors WordPress V3.7.1 or higher.– The agent evaluates only the performance of PHP requests in WordPress

applications. CSS and JS loading are not evaluated.– The agent does not identify URLs via URL arguments.

v Monitoring Agent for PostgreSQL– You must have PostgreSQL V9.2 or higher installed.– You must modify the postgresql.conf configuration file to add

pg_stat_statements.1. Open the postgresql.conf file in a text editor and update the

shared_preload_libraries line as follows:shared_preload_libraries = ’pg_stat_statements’

If you want to monitor SQL functions, you must specify the following:shared_preload_libraries = ’pg_stat_statements’pg_stat_statements.track = all

2. Restart the PostgreSQL server after you have added thepg_stat_statements.

3. Execute the following SQL command by using Psql:create extension pg_stat_statements;select pg_stat_statements_reset();

v Monitoring Agent for Python– You must have an Apache HTTPD server V2.2.15 or higher installed before

you install the agent.– The Apache server must include mod_wsgi V3.2 or higher.– Python must be at V2.6.6 or higher.– The Python agent monitors Django V1.4.10 or higher.– The agent evaluates only the performance of view requests in Django

applications.– The agent does not identify URLs via URL arguments.

About this task

Complete these steps to install monitoring agents on VMs and systems where RedHat Enterprise Linux is installed.

Procedure1. Download the consumer VM or installation archive file from the following

location to a staging directory of your choosing: IBM SmartCloud Monitoring -Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Download





instructions (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

2. Open a terminal shell session on the Red Hat Enterprise Linux system.3. Navigate to the directory where you want to install the monitoring agent

software and copy the consumer VM file from the staging area to the VM.4. Extract the consumer VM installation files with one of the following

commands:tar -xf ConsumerVM_Media.tar

where ConsumerVM_Media.tar is the name of the archive file.5. As the root user, run one of the following scripts to install the monitoring

software on the Linux system or VM:

Command Monitoring agent

./os-agent.sh install Monitoring Agent for Linux OS

./mongodb-agent.sh install Monitoring Agent for MongoDB

./mysql-agent.sh install Monitoring Agent for MySQL

./php-agent.sh install Monitoring Agent for PHP

./postgresql-agent.sh install Monitoring Agent for PostgreSQL

./python-agent.sh install Monitoring Agent for Python

./ruby-agent.sh install Monitoring Agent for Ruby

./was-agent.sh install Monitoring Agent for WebSphereApplications

./rt-agent.sh install Response Time Monitoring Agent

A prerequisite scan of your environment starts and takes a few moments tocomplete. If any requirements are missing, a message directs you to a log filewith the reason for the failure. A prerequisite, such as a missing library orinsufficient disk space, stops the installation. You must address the failure, andstart the installation again. For more information, including the yum installlibstdc++ command, see “Dependencies” on page 5.The monitoring agent is installed in the /opt/ibm/ccm/agent directory.The Linux OS and Response Time agents are configured and startedautomatically.

6. If your monitoring agent requires configuration or you want to review thedefault settings, see “Configuring your monitoring agents” on page 35.v The WebSphere Applications agent must be configured before data is

reported.v The MongoDB, MySQL, PHP, PostgreSQL, Python, and Ruby agents are

multiple instance agents. You must create the first instance and start theagent manually.

v For monitoring agents that require configuration, if you upgraded from aprevious version, be sure to reconfigure the monitoring agent before loggingin to the Application Performance Management console.

7. If the monitoring agent is not started or you want to confirm that it is started,enter one of the following commands:

Command Description

./name-agent.sh start Start the monitoring agent



Command Description

./name-agent.sh status Verify that the monitoring agent is started

For more information about the monitoring agent commands, including thename to use, see “Entering agent commands” on page 52.

8. After installation is complete and the command line is available, you can repeatsteps 5 on page 32 and 6 on page 32 to install more monitoring agents on themanaged system.

What to do nextv If a firewall is enabled, ensure that TCP port 51920 for HTTP or 53661 for

HTTPS on the monitoring agent is open for incoming connections from themonitoring infrastructure node.

v If you have the Response Time Monitoring Agent installed, you can installSmartCloud APM for Mobile Applications, as described in “InstallingSmartCloud APM for Mobile Applications” on page 47.

v If you are not logged in, follow the instructions in “Starting the ApplicationPerformance Management console” on page 49.

Installing monitoring agents on Windows systemsTo install a monitoring agent, you must download an archive file from the IBMdownload site, extract the agent installation files, and then start the installationscript.

You can install the following monitoring agents that run on Windows operatingsystems:v Monitoring Agent for Windows OSv Monitoring Agent for MySQLv Monitoring Agent for WebSphere Applicationsv Response Time Monitoring Agent

Before you begin

The consumer VM installation media is named differently depending on whereyou obtained the file. Replace the name of the ConsumerVM_Media.zip that is shownin the instructions with the name of the file that you downloaded: Whendownloaded from IBM Passport Advantage, the file is CIY2JML.tar.

You can install any combination of monitoring agents on a managed system. Forexample, if you install the Monitoring Agent for MySQL for monitoring MySQLservers, you might want to also install the Response Time Monitoring Agent togather more response time information, and the Monitoring Agent for WindowsOS to monitor other aspects of the system, such as the overall CPU, memory, anddisk usage.

The following agent prerequisites apply:v Monitoring Agent for MySQL

For the Monitoring Agent for MySQL, you must have the MySQL server andMySQL JDBC driver installed before installing the MySQL agent on that system.To install the JDBC driver, see MySQL Connector/J JDBC driver(http://dev.mysql.com/downloads/connector/j). If you are installing the agent


http://dev.mysql.com/downloads/connector/j

on a VM that you plan to use as the base library image, do not configure theMySQL agent before instantiating the other VMs. The MySQL agent must beconfigured on each instantiated VM.

v Response Time Monitoring AgentFor the Response Time Monitoring Agent, WinPcap 4.1.3 is required before youcan install the agent. You can download the driver from http://www.winpcap.org. For detailed instructions, see “Installing Windows packetcapture library” (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/Install_Guide/win_net_mon.html).

About this task

Complete these steps to install monitoring agents on VMs and systems where theWindows operating system is installed.

Procedure1. Download the consumer VM agent installation archive file from the following

location to a staging directory of your choosing: IBM SmartCloud Monitoring -Application Insight trial version (https://www14.software.ibm.com/webapp/iwm/web/preLogin.do?source=SCMAI). For more locations, see Downloadinstructions (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.scmai.doc_1.2/install/scmai_downloaddoc.htm).

2. Extract the consumer VM installation files to the location where you want toinstall the monitoring agent software.

3. While logged on as a user with administrator privileges, run one of thefollowing scripts from the command line to install the monitoring software onthe Windows system or VM:

Command Installs

os-agent.bat install Monitoring Agent for Windows OS

mysql-agent.bat install Monitoring Agent for MySQL

was-agent.bat install Monitoring Agent for WebSphereApplications

rt-agent.bat install Response Time Monitoring Agent

A prerequisite scan of your environment starts and takes a few moments tocomplete. If any requirements are missing, a message directs you to a log filewith the reason for the failure. A prerequisite such as a missing library orinsufficient disk space stops the installation. You must address the failure, andstart the installation again. For more information, see “Dependencies” on page5.The monitoring agent is installed in the C:\IBM\ITM\ directory.The Windows OS agent and Response Time agent are configured and startedautomatically.

4. If your monitoring agent requires configuration or you want to review thedefault settings, see “Configuring your monitoring agents” on page 35.v The WebSphere Applications agent must be configured before data is

reported.v The MySQL agent is a multiple instance agent. You must create the first

instance and start the agent manually.


http://www.winpcap.org

http://www.winpcap.org

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/Install_Guide/win_net_mon.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/Install_Guide/win_net_mon.html





v For monitoring agents that require configuration, if you upgraded from aprevious version, be sure to reconfigure the monitoring agent before loggingin to the Application Performance Management console.

5. If the monitoring agent is not started or you want to confirm that it is started,enter one of the following commands where name is os, mysql, was, or rt:

Command Description

name-agent.bat start Start the monitoring agent

name-agent.bat status Verify that the monitoring agent is started

For more information about the monitoring agent commands, see “Enteringagent commands” on page 52.

6. After installation is complete and the command prompt is available, repeatsteps 3 on page 34 and 4 on page 34 to install and configure more monitoringagents.

What to do nextv If a firewall is enabled, ensure that TCP port 51920 for HTTP or 53661 for

HTTPS on the monitoring agent is open for incoming connections from themonitoring infrastructure node.

v If you have the Response Time Monitoring Agent installed, you can installSmartCloud APM for Mobile Applications, as described in “InstallingSmartCloud APM for Mobile Applications” on page 47.

v If you are not logged in, follow the instructions in “Starting the ApplicationPerformance Management console” on page 49.

Configuring your monitoring agentsIf your monitoring agent requires configuration or you want to review the defaultsettings for an agent, follow the steps provided for your agent.

Ensure agent prerequisites are met before configuring your monitoring agents.Review the prerequisites provided in the Before you begin sections of “Installingmonitoring agents on Linux systems” on page 30 and “Installing monitoring agentson Windows systems” on page 33.

Note: The Monitoring Agent for Linux OS and Monitoring Agent for Windows OSdo not require additional configuration.

Configuring the MongoDB agent

About this task

The Monitoring Agent for MongoDB is a multiple instance agent; you must createthe first instance and start the agent manually. The instance name that you specifyis included in the managed system name, instance_name:host_name:pc, where pc isyour two character product code. The instance name that you specify is limited to28 characters, minus the length of your host name. For example, if you specifyMongo2 as your instance name, your managed system name is Mongo2:hostname:KJ.

In a typical environment, where MongoDB is running as a cluster and there is asingle router on the system where you installed the agent, the only configurationinformation you need to provide is the new instance name. For a typicalenvironment, configure the agent with the default settings.


To change the Java directory, type, port, or router IP address, configure the agentwith customized settings.

Restriction: The MongoDB agent does not support stand-alone MongoDBinstances.

Procedurev To configure the agent with the default settings not responding to prompts,

complete the following steps:1. Enter:

/opt/ibm/ccm/agent/bin/mongodb-agent.sh config instance_name/opt/ibm/ccm/agent/samples/mongodb_silent_config.txtWhere instance_name is the name you want to give to the instance.

2. To start the agent, enter:/opt/ibm/ccm/agent/bin/mongodb-agent.sh start instance_name

v To configure the agent by editing the silent response file and running the scriptwith no interaction, complete the following steps:1. Open /opt/ibm/ccm/agent/samples/mongodb_silent_config.txt in a text

editor.2. For JAVA, you can set the directory where the Java runtime environment is

located if this location is different from the location that is discovered by theinstaller.

3. For TYPE, you can specify whether the systems are a cluster (1) or a singlereplication set (2). By default, the agent monitors a cluster (1).

4. For PORT, to override the automatic discovery of a cluster or to monitor aspecific replication set, set the port number for the router of a MongoDBcluster or a mongod (primary daemon process) instance of a MongoDBreplication set being monitored. If this value is blank, the agent automaticallydiscovers the appropriate MongoDB process ports. Leaving the port valueempty provides more reliable monitoring if there is only one cluster orreplication set on the system.

5. For HOST, you can set the IP address for the MongoDB host system, or leavethis parameter blank to have the installer discover the default IP address.The host IP address is used to select a particular interface on a system whereMongoDB is bound to only one of several addresses.

6. Save and close the mongodb_silent_config.txt file, then enter:/opt/ibm/ccm/agent/bin/mongodb-agent.sh config instance_name/opt/ibm/ccm/agent/samples/mongodb_silent_config.txtWhere instance_name is the name that you want to give to the instance.


v To configure the agent by running the script and responding to prompts,complete the following steps:1. Enter:

/opt/ibm/ccm/agent/bin/mongodb-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. Respond to the prompts by using the description of the parameters that wereprovided earlier for reference.



Configuring the MySQL agent

About this task

The Monitoring Agent for MySQL requires an instance name and the MySQLserver user credentials. You must create the first instance and start the agentmanually. Run the configuration script to create an instance and change anyconfiguration settings. You can edit the MySQL silent response file before you runthe script to bypass the prompting and responses that are otherwise required.

The instance name that you specify is included in the managed system name,instance_name:host_name:pc, where pc is your two character product code. Theinstance name that you specify is limited to 28 characters, minus the length of yourhost name. For example, if you specify MySQL2 as your instance name, yourmanaged system name is MySQL2:hostname:SE.

Procedurev To configure the agent by editing the silent response file and running the script

with no interaction, complete the following steps:1. To configure the agent, open the response file in a text editor:

/opt/ibm/ccm/agent/samples/mysql_silent_config.txt

C:\IBM\ITM\samples\mysql_silent_config.txt

2. For JDBC user name, leave it set to root or change to a user with privilegesto view the INFORMATION_SCHEMA tables.

3. For JDBC password, enter the JDBC user password.4. For JDBC home, leave it at the default, if this path is where Java is installed;

otherwise, enter the correct path. Default path:/opt/ibm/java-x86_64-70/jre

C:\IBM\ITM\java\java70_x64\jre

5. For JDBC Jar File, leave it at the default, if this is the path to the MySQLconnector for the Java jar file; otherwise, enter the correct path. Defaultpath:

/usr/share/java/mysql-connector-java.jar

C:\Program Files (x86)\MySQL\Connector J5.1.26\mysql-connector-java-5.1.26-bin.jar

6. For JDBC port number, leave it at the default 3306 or specify the portnumber if it is different.

7. For Java trace level, leave it at the default level Error or change it to thelevel instructed by IBM Support.

8. Save the response file.9. To configure the agent, enter:

/opt/ibm/ccm/agent/bin/mysql-agent.sh config instance_name/opt/ibm/ccm/agent/samples/mysql_silent_config.txt

C:\IBM\ITM\BIN\mysql-agent.bat config instance_nameC:\IBM\ITM\samples\mysql_silent_config.txt

Where instance_name is the name that you want to give to the instance.Be sure to include the absolute path to the silent response file. Otherwise,no agent data is available in the dashboards.

10. To start the agent, enter:/opt/ibm/ccm/agent/bin/mysql-agent.sh start instance_name


C:\IBM\ITM\BIN\mysql-agent.bat start instance_name

v To configure the agent by running the script and responding to prompts,complete these steps:–

1. To configure the agent, enter:/opt/ibm/ccm/agent/bin/mysql-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. Respond to the prompts by using the description of the parameters thatwere provided earlier for reference.

3. To start the agent, enter:/opt/ibm/ccm/agent/bin/mysql-agent.sh start instance_name

Configuring the PHP agent

Before you begin

Ensure that the Apache HTTPD server is started before you configure the agent.

If the Apache HTTPD server version is lower than V2.4, open the Apache HTTPServer httpd.conf configuration file and ensure that both the mod_status andExtendedStatus On options are enabled. For example:ExtendedStatus On<Location /server-status>

SetHandler server-statusOrder deny,allowAllow from allAllow from 127.0.0.1

</Location>

About this task

Note: The PHP agent and Python agent can coexist in a single Apacheenvironment.

The PHP agent is a multiple instance agent; you must create the first instance andstart the agent manually. The instance name that you specify is included in themanaged system name, instance_name:host_name:pc, where pc is your twocharacter product code. The instance name that you specify is limited to 28characters, minus the length of your host name. For example, if you specify PHP2as your instance name, your managed system name is PHP2:hostname:PJ.

Procedurev To configure the agent with the default settings, not responding to prompts,

complete the following steps:1. Enter:

/opt/ibm/ccm/agent/bin/php-agent.sh config instance_name/opt/ibm/ccm/agent/samples/php_silent_config.txtWhere instance_name is the name you want to give to the instance.

2. To start the agent, enter:/opt/ibm/ccm/agent/bin/php-agent.sh start instance_name

v To configure the agent by editing the silent response file and running the scriptwith no interaction, complete the following steps:1. Open /opt/ibm/ccm/agent/samples/php_silent_config.txt in a text editor.


2. For Location of PHP execution binary, you can specify the directory wherethe PHP execution is located. The default location is /usr/local/bin.

3. For Location of PHP INI file, you can specify the directory where thephp.ini file is located. The default location is /etc.

4. For Web server port, you can specify the port number of the web server thatis running WordPress. The default is 80.

5. For Application DocumentRoot, you can specify the DocumentRoot of thePHP WordPress application. Use a colon to separate multiple records. Toallow the agent to find all the records for you, use the default value of ALL.

6. Save and close the php_silent_config.txt file, then enter:/opt/ibm/ccm/agent/bin/php-agent.sh config instance_name/opt/ibm/ccm/agent/samples/php_silent_config.txtWhere instance_name is the name that you want to give to the instance.



/opt/ibm/ccm/agent/bin/php-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. When prompted to Edit Monitoring Agent for PHP settings, enter 1 tocontinue.

3. When prompted for Location of PHP execution binary, press Enter toaccept the default location or specify your own location.

4. When prompted for Location of PHP INI file, press Enter to accept thedefault location or specify your own location.

5. When prompted for Web server port, press Enter to accept the default portor specify a different port number.

6. When prompted for Application DocumentRoot, press Enter to accept thedefault or specify the DocumentRoot of the PHP WordPress application. Youcan use a colon to separate multiple records.


What to do next

You can verify the PHP agent data is displayed in the Application PerformanceManagement console.

You must ensure that the WordPress plugin-in for the agent is activated. To ensureactivation, complete the following steps:1. In a web browser, enter the following URL http://hostname:port/wp-admin/.2. Access the administrative page by navigating to Plugins > Installed Plugins.3. Ensure that the PHP agent plug-in is activated. The PHP agent plug-in is listed

as WordPress Agent. Typically, the plug-in is already activated. If it is notalready activated, click on Activate.

4. Optionally, you can verify your Apache server-status module is available usingthe following command:/user/local/apache/bin/apachectl fullstatus


Configuring the PostgreSQL agent

Before you begin

If the authentications settings are not correct in the PostgreSQL databasepg_hba.conf file, the PostgreSQL agent cannot connect to the PostgreSQL database.If auth-method is set to ident, the PostgreSQL agent cannot connect. Ensure thatthe PostgreSQL pg_hba.conf authentication file has the correct auth-methodsettings. For example, you might set auth-method to md5, trust, or password.

About this task

The PostgreSQL agent is a multiple instance agent; you must create the firstinstance and start the agent manually. The instance name that you specify isincluded in the managed system name, instance_name:host_name:pc, where pc isyour two character product code. The instance name that you specify is limited to28 characters, minus the length of your host name. For example, if you specifyPostgreSQL2 as your instance name, your managed system name isPostgreSQL2:hostname:PN.


with no interaction, complete the following steps:1. Open /opt/ibm/ccm/agent/samples/postgresql_silent_config.txt in a text

editor.2. For JDBC database name, leave it set to postgres or specify the database

name.3. For JDBC user name, leave it set to postgres or change to a different user

name.4. For JDBC password, enter the JDBC user password.5. For JDBC port number, leave it at the default 5432 or specify the port

number if it is different.6. For JDBC JAR file, leave the path to the PostgreSQL connector for the Java

JAR file at the default if it is correct; otherwise, enter the correct path.Default path: /opt/PostgreSQL/lib/postgresql-9.3-1100.jdbc4.jar.

7. For Java home, confirm that the default path exists; otherwise, enter thecorrect path. Default path: /opt/ibm/ccm/agent/JRE/lx8266/jre.

8. For Java trace level, leave it at the default level Error or change it to thelevel instructed by IBM Support.

9. Save and close the postgresql_silent_config.txt file, and enter:/opt/ibm/ccm/agent/bin/postgresql-agent.sh config instance_name/opt/ibm/ccm/agent/samples/postgresql_silent_config.txtWhere instance_name is the name that you want to give to the instance.

10. To start the agent, enter:/opt/ibm/ccm/agent/bin/postgresql-agent.sh start instance_name


/opt/ibm/ccm/agent/bin/postgresql-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. When prompted to Edit Monitoring Agent for PostgreSQL settings, enter1 to continue.


3. When prompted for JDBC database name, press Enter to accept the defaultor specify a database name.

4. When prompted for JDBC user name, press Enter to accept the default orspecify a user name.

5. When prompted for JDBC password, enter the JDBC user password.6. When prompted for JDBC port number, press Enter to accept the default or

specify a port number.7. When prompted for Java home, press Enter to accept the default or specify a

path.8. When prompted for JDBC JAR file, press Enter to accept the default or

specify the file.9. When prompted for Java trace level, enter 2 to accept the default or

specify the trace.10. To start the agent, enter:

/opt/ibm/ccm/agent/bin/postgresql-agent.sh start instance_name

Configuring the Python agent

Before you begin

Ensure that the Apache HTTPD server is started before you configure the agent.

Open the Apache HTTPD server httpd.conf configuration files and ensure thatmod_status is loaded.

About this task

Note: The Python agent and PHP agent can coexist in a single Apacheenvironment.

The Python agent is a multiple instance agent; you must create the first instanceand start the agent manually. The instance name that you specify is included in themanaged system name, instance_name:host_name:pc, where pc is your twocharacter product code. The instance name that you specify is limited to 28characters, minus the length of your host name. For example, if you specifyPython2 as your instance name, your managed system name isPython2:hostname:PG.


with no interaction, complete the following steps:1. Open /opt/ibm/ccm/agent/samples/python_silent_config.txt in a text

editor.2. For HTTPD listening port, specify the port number to distinguish one group

of HTTPD processes from others. The default is 80.

Note:

– If your Apache server is listening on multiple ports, you can specify anyone of them for this parameter.

– If you have more than one Apache server running on the same system,you must specify a port from the server in which the Django applicationsare running.


3. For Django WSI entry points, specify the Django WSGI entry points. Use acolon to separate multiple entry points.For example, in an Apache configuration file, you might see the followingconfiguration line:WSGIScriptAlias / /var/www/html/mysite/mysite/wsgi.pyIn this example, /var/www/html/mysite/mysite/wsgi.py is provided as theentry point.To include all the entry points that are discovered in the Apacheconfiguration files, leave this parameter blank.

4. For Minimum recorded response time, set the average response time inmilliseconds. Requests that are faster or equal to this number are notrecorded. The default is 300.

5. For Slow request threshold, set the slow request threshold in milliseconds.The default is 500.

6. For Extreme slow request threshold, set the extreme slow request thresholdin milliseconds. The default value is 7000.

7. For Profiler report interval, set the interval in minutes, at which theagent generates the profiler report for slow requests. The minimum settingfor this value is 10, this ensures your applications are not slowed down toexcessive profiling. Typical users set this value greater than 10. The default is10.

8. Save and close the python_silent_config.txt file, then enter:/opt/ibm/ccm/agent/bin/python-agent.sh config instance_name/opt/ibm/ccm/agent/samples/python_silent_config.txtWhere instance_name is the name that you want to give to the instance.

9. To start the agent, enter:/opt/ibm/ccm/agent/bin/python-agent.sh start instance_name


/opt/ibm/ccm/agent/bin/python-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. When prompted to Edit Monitoring Agent for Python settings, enter 1 tocontinue.

3. When prompted for HTTP listening port, press Enter to accept the defaultor specify a port number.

4. When prompted for Django WSI entry points, leave this parameter blank orspecify the entry points.

5. When prompted for Minimum recorded response time, press Enter to acceptthe default or specify the time.

6. When prompted for Slow request threshold, press Enter to accept thedefault or specify a threshold.

7. When prompted for Extreme slow request threshold, press Enter to acceptthe default or specify a threshold.

8. When prompted for Profiler report interval, press Enter to accept thedefault of specify an interval.

9. To start the agent, enter:/opt/ibm/ccm/agent/bin/python-agent.sh start instance_name


What to do next

After you start the agent instance, an injection script to customize your monitoringmiddleware is generated and provided in a temporary directory.

Note: The Apache server must be started before you start the agent instance,otherwise the injection script is not created.To customize your middleware, complete the following steps:1. Execute the script using the following command:

cd /opt/ibm/ccm/agent/tmp/kpg./inject_numeric_string.sh

Where number_string is the numeric string identifying the Django application.If your temporary directory includes multiple injection scripts, execute eachscript.

2. Restart the Apache server to enable the monitoring middleware.

Note: Multiple injection scripts might include the enablement of the Apache statusmodule, however, when executing the scripts the module is only added once.

If you are reconfiguring the Python agent, you must execute the new injectionscripts that are generated and then restart the Apache server.

For your reference, you can use the following stop and restart commands for theApache server:v Stop: apache_bin_directory/httpd -k graceful-stop

v Restart: apache_bin_directory/httpd -k graceful

Configuring the Response Time Monitoring Agent

About this task

You can customize the data that is displayed in the End User Transactionsdashboards by configuring the IP address and type of transactions to monitor, andon which port.


with no interaction, complete the following steps:1. To stop the agent, enter:

/opt/ibm/ccm/agent/bin/rt-agent.sh stop

C:\IBM\ITM\BIN\rt-agent.bat stop

2. To configure the agent, open the response file in a text editor:/opt/ibm/ccm/agent/samples/rt_silent_config.txt

C:\IBM\ITM\samples\rt_silent_config.txt

3. For HTTP port, leave it set to 80 or change to a different port number.4. For Monitor HTTPS transactions?, leave it set to No, or change to Yes and

ensure that you specify an HTTPS keystore and HTTPS server certificatemap. For more information, see Enabling Appliance Mode for HTTPStransactions in the ITCAM for Transactions documentation.

5. For HTTPS keystore, leave it empty or add the keystore.


http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/User_Guide/Web1/wrtappliance_https.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/User_Guide/Web1/wrtappliance_https.html

6. For HTTPS server certificate map, leave it empty or specify the certificate.7. For IP address of the monitored NIC, leave it empty or add the IP address

if the NIC is monitored.8. Save the response file.9. If you are installing SmartCloud Application Performance Management for

Mobile Applications, follow the instructions in “Installing SmartCloud APMfor Mobile Applications” on page 47.

10. To configure the agent, enter:/opt/ibm/ccm/agent/bin/rt-agent.sh config

/opt/ibm/ccm/agent/samples/rt_silent_config.txt

C:\IBM\ITM\BIN\rt-agent.bat config C:\IBM\ITM\samples\rt_silent_config.txt

Be sure to include the absolute path to the silent response file. Otherwise,no agent data is available in the dashboards.

11. To start the agent, enter:/opt/ibm/ccm/agent/bin/rt-agent.sh start

C:\IBM\ITM\BIN\rt-agent.bat start

v To configure the agent by running the script and responding to prompts,complete the following steps:–

1. To stop the agent, enter:/opt/ibm/ccm/agent/bin/rt-agent.sh stop

2. To configure the agent, enter:/opt/ibm/ccm/agent/bin/rt-agent.sh config

3. Respond to the prompts as described earlier.4. To start the agent, enter:

/opt/ibm/ccm/agent/bin/rt-agent.sh start

Configuring the Ruby agent

About this task

The Monitoring Agent for Ruby is a multiple instance agent; you must create thefirst instance and start the agent manually. The instance name that you specify isincluded in the managed system name, instance_name:host_name:pc, where pc isyour two character product code. The instance name that you specify is limited to28 characters, minus the length of your host name. For example, if you specifyRuby2 as your instance name, your managed system name is Ruby2:hostname:KM.

For a typical environment, in which you want to monitor all the Ruby on Railsapplications on the system automatically, you do not have to provide moreconfiguration information other than the new instance name. For a typicalenvironment, configure the agent with the default settings.

If you have multiple Ruby runtimes installed on the system, you must specify theruntime to use to gather data from your Ruby applications. The chosen Rubyruntime must be compatible with the version of Ruby on Rails that is used in theapplication. To specify the runtime to use, configure the agent with customizedsettings.

If you prefer to monitor a subset of your Ruby applications, edit each Rubyapplication that you want to monitor separately.


Procedurev Complete these steps to configure the agent with the default settings:

1. To configure the agent, enter:/opt/ibm/ccm/agent/bin/ruby-agent.sh config instance_name/opt/ibm/ccm/agent/samples/ruby_silent_config.txtWhere instance_name is the name you want to give to the instance.

2. To start the agent, enter:/opt/ibm/ccm/agent/bin/ruby-agent.sh start instance_name

v Complete these steps to configure the agent with customized settings:1. To configure the agent, enter:

/opt/ibm/ccm/agent/bin/ruby-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. When prompted to Edit Monitoring Agent for Ruby settings, enter 1 tocontinue.

3. When prompted for Ruby Runtime Bin Location, specify the binary directory.For example, /usr/local/rvm/rubies/ruby-2.0.0-p247/bin if you use RubyVersion Manager (RVM).

4. When prompted with Allow the Ruby agent to auto-detect all currentrunning Ruby on Rails applications, enter Y to continue.

5. When prompted for Rails Application Server, press Enter to accept thedefault of ruby or specify a name.

6. When prompted for Socket Data Source, press Enter to accept the default of0 to use the ephemeral port.

7. When prompted to Edit 'Ruby_Application' settings, enter 5 to exit.8. To start the agent, enter:

/opt/ibm/ccm/agent/bin/ruby-agent.sh start instance_name

v Complete these steps to edit each Ruby application that you want to monitorseparately:1. To configure the agent, enter:

/opt/ibm/ccm/agent/bin/ruby-agent.sh config instance_nameWhere instance_name is the name you want to give to the instance.

2. When prompted to Edit Monitoring Agent for Ruby settings, enter 1 tocontinue.

3. When prompted for Ruby Runtime Bin Location, press Enter to continue.4. When prompted with Allow the Ruby agent to auto-detect all current

running Ruby on Rails applications, enter N to continue.5. When prompted for Rails Application Server, press Enter to accept the

default of ruby or specify a name.6. When prompted for Socket Data Source, press Enter to accept the default

of 0 to use the ephemeral port.7. When prompted to Edit 'Ruby_Application' settings, enter 1 to specify

an application.8. When prompted, enter the Ruby application name.9. When prompted, enter the Ruby application home directory, for example:

/root/Ruby/myApp.10. For the last prompt, Advanced (select a section to override values),

you can enter q to exit.11. To start the agent, enter:

/opt/ibm/ccm/agent/bin/ruby-agent.sh start instance_name


Note: If you have multiple Ruby runtimes installed and you want to monitorspecific Ruby applications, you can set a runtime override on the Rubyapplication or subnode. As an example, assume that you have two runtimesinstalled and four applications, three of which use one runtime and one ofwhich uses the other runtime. In this case, set the runtime most commonly usedat the agent level, and set the runtime override for the application that uses adifferent runtime.Also, see the note in step 5 of “Managing applications” on page 56.

Configuring the WebSphere Applications agent

About this task

The Monitoring Agent for WebSphere Applications consists of two components, themonitoring agent and the data collector. The data collector is configured to monitorapplication server instances; it passes the information to the monitoring agent,which communicates with the monitoring infrastructure. You must configure thedata collector to monitor application server instances.

Procedurev For a typical configuration, use the following simple configuration procedure:

1. To configure the application server, enter:

cd /opt/ibm/ccm/agent/install-images/kyn/dchome/7.3.0.1.0/bin/./simpleconfig.sh

cd C:\IBM\ITM\dchome\7.3.0.0.0\binsimpleconfig.bat

2. To enable these configuration changes, you must stop and restart the agent:

cd /opt/ibm/ccm/agent/bin./was-agent.sh stop./was-agent.sh start

cd C:\IBM\ITM\binwas-agent.batstop was-agent.bat start

For detailed information, see Configuring the data collector(http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_install/simpleconfigurationofthedatacollector.html).

3. Restart the WebSphere Application Server. If you do not restart the server,the agent operates in Resource Monitoring mode and captures only a subsetof the data until the server is restarted.

v For advanced configuration, complete the steps in Advanced configuration andcustomization for the data collector (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_adv_dc/customization_and_advanced_configuration_for_the_dc.html).If you purchased Application Performance Diagnostics, also complete the stepsin Installing support for diagnostic dashboards on the monitoring infrastructurenode (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/installingsupport.html).


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_install/simpleconfigurationofthedatacollector.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_adv_dc/customization_and_advanced_configuration_for_the_dc.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/chapter_adv_dc/customization_and_advanced_configuration_for_the_dc.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/installingsupport.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/installingsupport.html

Installing SmartCloud APM for Mobile ApplicationsInstall SmartCloud APM for Mobile Applications on the Monitoring InfrastructureNode of the lightweight infrastructure.

Use Mobile Devices and Authenticated Users dashboards to understand the loadscreated by mobile devices and the loads for users. These dashboards are availableonly when SmartCloud Monitoring - Application Insight V1.2 is installed as part ofSmartCloud Application Performance Management V7.7.0.1.

Restriction: SmartCloud APM for Mobile Applications is currently available onlyon Linux 64-bit systems.

Follow these steps to start using Mobile Devices and Authenticated Usersdashboards:1. Install the Response Time Monitoring Agent, as described in “Installing

monitoring agents on Linux systems” on page 30.2. Download SmartCloud APM for Mobile Applications from Passport Advantage

and install it on the Monitoring Infrastructure Node. Run the followingcommand on the Monitoring Infrastructure Node:rpm -ihv smai-response_time-apmui-dashboard-mobile-07.40.00.02-1.el6.noarch.rpm

Tip: To upgrade an existing installation, run:rpm -Uhv smai-response_time-apmui-dashboard-mobile-07.40.00.02-1.el6.noarch.rpm

3. Add new applications or refresh existing applications:v Add applications to the dashboard from the application repository. If the web

or Worklight application that you want to monitor has already beendiscovered by the Response Time agent, it is listed in the Read list. Forinstructions, see “Managing applications” on page 56.

v To see the Mobile Devices and Authenticated Users dashboards for existingapplications:a. Select the application and click Edit.b. Click Save.

Upgrading monitoring agentsIf a new version of an installed monitoring agent is available, you can start theconsumer VM installation script to upgrade the agent automatically.

Before you begin

Monitoring agents from the SmartCloud Monitoring - Application Insight Version1.2 and Version 1.2 Fix Pack 1 consumer VM are automatically upgraded duringinstallation of the Version 1.2 Fix Pack 2 consumer VM. Any customization for theagent, such as thresholds defined in the Threshold Manager, are retained.

About this task

Follow the instructions for the operating system that the monitoring agent runs onto upgrade to the latest version:

Procedurev “Installing monitoring agents on Linux systems” on page 30v “Installing monitoring agents on Windows systems” on page 33


Results

The agent is upgraded to the latest version. If a newer version of the monitoringagent is not available, a message is displayed explaining that the agent is alreadyinstalled; your installed agent is not affected.

Uninstalling monitoring agentsUninstall a single agent or all the agents from a managed system.

Before you begin

For the Monitoring Agent for WebSphere Applications, you must unconfigure thedata collector for all monitored server instances before you uninstall the agent.Follow the instructions in Unconfiguring the data collector (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/unconfiguring.html).

For the Monitoring Agent for Python, backup your Django settings and the Apachehttpd.conf configuration file, because any changes you made to these files afteryou executed the injection scripts are lost during the uninstallation. After youuninstall the agent, you can manually restore your settings using the backup files.

Procedure1. On the VM or system where the monitoring agent (or agents) is installed, start

a command line and change to the binary directory:v /opt/ibm/ccm/agent/bin

v C:\IBM\ITM\BIN

2. To uninstall a specific monitoring agent, enter the agent script name and theuninstall option where name is the agent script name:v ./name-agent.sh uninstall

v name-agent.bat uninstall

For a list of the agent script names, see “Entering agent commands” on page52.The monitoring agent is uninstalled from the managed system.If you have uninstalled all of your monitoring agents individually, complete thenext step to remove the framework files.

3. To uninstall all the monitoring agents from the managed system, enter thescript name and uninstall option:v ./smai-agent.sh uninstall_all

v smai-agent.bat uninstall_all

All monitoring agents are uninstalled from the system or VM.

What to do next

For the Monitoring Agent for Python:1. Delete the Django pyc configuration file to ensure the restored Django pyc file

generates its binary.2. Restart the Apache server to remove the loaded middleware in the Apache

processes.


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apd.doc_11fp/apd_install_config/unconfiguring.html

3. Ensure that the properties of the Apache configuration file are correct. Duringuninstallation, the Apache configuration file is restored with root user andgroup permissions.

Starting the Application Performance Management consoleLog in to SmartCloud Monitoring - Application Insight from your browser toreview the health status of your deployments in the Application PerformanceManagement console dashboards.

Before you begin

The URL for the login is the IP address of the monitoring infrastructure node. Ifthe infrastructure node is on a VM and you do not know what the IP address is,find it by taking one of these steps:v Log on to SmartCloud Provisioning and look on the Resources page in the

Deployed VMs tab. The infrastructure node IP address is in the Private Addresscolumn.

v Log in to your AMAZON AWS account and navigate to the EC2 Instances page.Select to open the Show/Hide Columns window. Select the Public DNS andPrivate DNS check boxes and click Apply. Back on the Amazon EC2 Instancestab, locate the VM that you want to collect IP data from and read the IP datafrom the columns you enabled in the previous step (such as VM MIN BLD -Public IP = 54.242.164.133 - Private IP = 10.111.34.44).

v Start the VMware vSphere client, and go to View > Inventory > VMs andTemplates. Locate the VM that you want to collect the IP data from, select theVM, and go to the Summary tab to see the IP addresses.

Procedure1. Open a browser window and enter the following URL where APMUI_host is the

IP address of the monitoring infrastructure node:https://APMUI_host:9443

You can also enter http://APMUI_host:8080, although the URL is changed tothe secure https and port number 9443 automatically.

2. After you are prompted for a logon ID, enter the following credentials for thedefault user or enter the credentials that were assigned by your cloudadministrator:a. User name apmadmin

b. Password apmpass

The initial user credentials after infrastructure node installation are apmadminwith password apmpass. You can add users to the basic user registry and assignuser roles, as described in the IBM SmartCloud Application PerformanceManagement UI User's Guide: “Configuring a basic user registry for Libertyprofile” (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/config_basic_user_reg.html)and “Mapping users to roles” (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/creating_role_basic_user_registry.html).

Resultsv After you log in, the Getting Started page or the Application Performance

Dashboard is displayed, depending on whether you cleared the check box for


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/config_basic_user_reg.html


http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/creating_role_basic_user_registry.html

showing Getting Started at startup. If you are in the Getting Started page, youcan open the Application Performance Dashboard by clicking ViewApplication Status > .

v If instead of the dashboard, you get the Configuration Wizard, it means that theinfrastructure node must be configured. For instructions, see the topic for yourhost: “Configuring the infrastructure node for Amazon EC2” on page 18,“Configuring the infrastructure node for SmartCloud Provisioning” on page 14,“Configuring the infrastructure node for VMware” on page 22, or “Configuringthe infrastructure node for other systems” on page 26.

What to do nextv Click System Configuration > Threshold Manager and create thresholds to

test for conditions that, when met, cause an event to open. For example, you canhave a threshold that opens an event after storage capacity reaches 90%.

v Click System Configuration > Historical Data Configuration and createhistorical data collection definitions for the data sets from which you want to seehistorical data, which can be 2 - 72 hours.

v If no metrics are shown for a data source, review the topics in Chapter 4,“Troubleshooting,” on page 65 to learn more about the possible causes andresolutions.


Chapter 3. Administering

Administering the monitoring infrastructure and agents involves maintenance taskssuch as changing passwords and customization tasks such as adding and editingapplications.

Data sourcesThe types of applications that you can monitor in the Application PerformanceManagement console are your data sources.

The monitoring agents for supported data sources have predefined thresholds andhistorical data collections to help you get started with monitoring your consumerVM instances as soon as you log in.

Data setsEach type of monitoring agent has many data sets that you can use tocreate thresholds to monitor for specific conditions, and historical datacollection configurations to save data samples for historical reporting. Thedashboards show the values of attributes from data sets.

Many data sets have enumerated attributes: the possible values are in atext format and represented by an integer. For example, the Linux OSagent Agent Active Runtime Status data set has an enumerated attributecalled Agent Availability Status with the following values:

Unknown (0)Not_found (1)Stopped (2)Start_Pending (3)Running (4)Manually_Stopped (5)Stop_Pending (6)Not_Configured (7)

Any dashboards or thresholds in the Application PerformanceManagement console that have enumerated attributes display the integerrather than the text it represents.

ThresholdsClick System Configuration > Threshold Manager to see any definedthresholds for your installed products and to create and edit thresholds.The thresholds that are created for a type of monitoring agent are appliedto all managed systems of the same type.

For enumerated attributes, use the integer rather than the text it representsin the threshold definition. For example, a threshold that detects when theMySQL agent is unavailable specifies Status = 0; not Status = DOWN.

Historical data collection configurationMost monitoring agents have historical data collections that are configuredand ready to begin data collection as soon as the agent is installed on thedata source. You can see the predefined historical data collectiondefinitions for your managed systems by clicking SystemConfiguration > Historical Data Configuration.


Note: The MongoDB agent and Ruby agent cannot be configured forhistorical data collection.

Entering monitoring infrastructure commandsUse the commands for starting and stopping the monitoring infrastructure nodeand other components when necessary for maintenance and troubleshooting tasks.

Procedurev Start or stop the monitoring infrastructure node:

start fabricNodestop fabricNode

v Start or stop the application server:start server1stop server1

v Start or stop the Application Performance Management console server:start apmuistop apmui

v Start or stop the Service Component Repository service:start scrstop scr

Entering agent commandsThe same scripts that you use to install monitoring agents on the consumer VMcan also be used to check the status of an installed agent, stop or start it, oruninstall the agent.

About this task

The agent name and product codes are provided for your reference.

Table 8. Agent names to use when entering the name-agent.sh/.bat commands and theassociated agent product code

Monitoring agent

Agent name to use whenentering the name-agent.sh/.batcommands

Two letterproductcode

Monitoring Agent for Linux OS os lz

Monitoring Agent for MongoDB mongodb kj

Monitoring Agent for MySQL mysql se

Monitoring Agent for PHP php pj

Monitoring Agent for PostgreSQL postgresql pn

Monitoring Agent for Python python pg

Monitoring Agent for Ruby ruby km

Monitoring Agent for WebSphereApplications

was yn

Monitoring Agent for Windows OS os nt

Response Time Monitoring Agent rt t5


Procedurev On the system or VM where you want to send a command to the

monitoring agent, change to the /opt/ibm/ccm/agent/bin directory, and enterany of the following commands where name is the agent script name.

Command Description

./name-agent.sh status Checks the monitoring agent status.

./name-agent.sh start Starts the monitoring agent. If the agent hasinstances, enter an instance name after thecommand.

./name-agent.sh stop Stops the agent. If the agent has instances,enter an instance name after the command.

./name-agent.sh prereqcheck Runs a prerequisite scan.

./name-agent.sh install Installs the monitoring agent. For moreinformation, see “Installing monitoringagents on Linux systems” on page 30.

./name-agent.sh config instance_namepath_to_silent_config_file

Configures the monitoring agent. Run thecommand in the directory where theconfiguration file is located or include it inthe path command.If the agent has instances, enter an instancename. For more information, see “Installinga monitoring agent on Linux”, step 6 onpage 32.

./name-agent.sh uninstall Uninstalls the monitoring agent. For moreinformation, see “Uninstalling monitoringagents” on page 48.

./smai-agent.sh uninstall_all Uninstalls all the monitoring agents on themanaged system.

./name-agent.sh View a description of the functions that areavailable with the script.

v On the system or VM where you want to send a command to themonitoring agent, change to the C:\IBM\ITM\bin directory on the command line,and enter any of the following commands where name is the agent script name.

Command Description

name-agent.bat status Checks the monitoring agent status.

name-agent.bat start Starts the monitoring agent. If the agent hasinstances, enter an instance name after thecommand.

name-agent.bat stop Stops the agent. If the agent has instances,enter an instance name after the command.

name-agent.bat prereqcheck Runs a prerequisite scan.

name-agent.bat install Installs the monitoring agent. For moreinformation, see “Installing monitoringagents on Windows systems” on page 33.

Chapter 3. Administering 53

Command Description

name-agent.bat config instance_namepath_to_silent_config_file

Configures the monitoring agent. Run thecommand in the directory where theresponse file is located or include it in thepath command.If the agent has instances, enter an instancename. For more information, see “Installinga monitoring agent on Windows”, step 4 onpage 34.

name-agent.bat uninstall Uninstalls the monitoring agent. For moreinformation, see “Uninstalling monitoringagents” on page 48.

smai-agent.bat uninstall_all Uninstalls all the monitoring agents on themanaged system.

name-agent.bat View a description of the functions that areavailable with the script.

Port configuration for agentsIf you have a firewall enabled, ensure that port 51920 for HTTP or 53661 forHTTPS (or both) are open in the firewall on each managed system.

If multiple monitoring agents are installed on the same managed system, moreports are used automatically to communicate with the monitoring infrastructurenode and must be open through the firewall. You can reduce the unpredictabilityof the assigned ephemeral port numbers by setting the ports in the firewall.

Locate the KDC_FAMILIES environment variable in the /opt/ibm/ccm/agent/config/global.environment file. Configure the POOL:ip_protocol-port option whereip_protocol is the IP version and protocol, and port is the port numberassignment. Example:KDC_FAMILIES=IP.PIPE PORT:1918 IP.TCP POOL:21001-21005 IP6.TCPPOOL:22001-22005 IP.SSL POOL:31001-31005 IP6.SSL POOL:32001-32005

The parameters map to the following protocol combinations:v IPv4 HTTP = IP.TCPv IPv6 HTTP = IP6.TCPv IPv4 HTTPS = IP.SSLv IPv6 HTTPS = IP6.SSL

Here is an example of an agent log after starting the monitoring agent with theKDC_FAMILIES environment variable:(5282374B.0198-13EC:kdhslqm.c,381,"add_listener") listening: ip6.tcp.http:22001(5282374B.01BB-13EC:kdhslqm.c,381,"add_listener") listening: ip.tcp.http:21001(5282374B.01DB-13EC:kdhslqm.c,381,"add_listener") listening: ip6.ssl.https:32001(5282374B.01FB-13EC:kdhslqm.c,381,"add_listener") listening: ip.ssl.https:31001

The ephemeral ports used the first port number in the respective POOL range. Andnow the well-known listening ports are opened.(5282374B.0221-13EC:kdhslqm.c,381,"add_listener") listening: ip6.tcp.http:1920(5282374B.0264-13EC:kdhslqm.c,381,"add_listener") listening: ip.tcp.http:1920(5282374B.0291-13EC:kdhslqm.c,381,"add_listener") listening: ip6.ssl.https:3661(5282374B.02BB-13EC:kdhslqm.c,381,"add_listener") listening: ip.ssl.https:3661


For more information, see ITM Protocol Usage and Protocol Modifiers(http://www-01.ibm.com/support/docview.wss?uid=swg21422918).

Access CredentialsIf any managed systems are not returning monitoring data, the user credentialsmight have changed. Use the Access Credentials page to update the user name andpassword that are required for logging in to the system where the monitoringagent is installed.

The Default Linux VM Credentials and Default Windows VM Credentials areused only when the OS agent is installed on the VM or computer, and are used forany other types of monitoring agents installed on the same system. When the OSagent is not present, the monitoring infrastructure node is not able to identify themonitoring agent type and uses the Default VM Credentials for access unless youspecify a new password for the managed system. Check the Access Credentialspage for invalid passwords. For more information about Default VM Credentials,see “Advanced Configuration” on page 58.

After logging in to SmartCloud Monitoring - Application Insight, you can clickSystem Configuration > Access Credentials to check for any managed systemsthat don't have valid user credentials associated with them. This can happen if youchange the password of the VM or computer being monitored.

If the list is long, you can click inside the filter text box and typethe beginning of the value to filter by. As you type, the rows that do not fit thecriteria are filtered out. To clear the filter, click the “x” in the filter box

or press the Backspace key.

The Last Updated bar shows the time of the most recent page refresh, which isset to every 30 seconds by default. For an immediate sampling of the page, clickthe bar and select Refresh Now. The other choices set the permanent behaviorof this page: to not automatically refresh, to refresh every 30 seconds, or to refreshevery minute.v Click the Lock indicator and enter valid user credentials that the monitoring

infrastructure node can use to access the system for monitoring.

After you click OK, the credentials you entered are used to access the system thenext time the managed resource is polled, and the Lock indicator is removed ifthe credentials are valid.

Changing the apmadmin passwordThe default user name and password for logging into SmartCloud Monitoring -Application Insight is apmadmin apmpass.

You can change the administrator password and encrypt it at any time.

Procedure1. Enter the command to stop the Application Performance Management console

server:stop apmui

2. Enter the command to stop the Service Component Repository service:stop scr


http://www-01.ibm.com/support/docview.wss?uid=swg21422918

3. Enter the command to stop the monitoring infrastructure node:stop fabricNode

4. Enter the command to export the JAVA_HOME variable:export JAVA_HOME=/opt/ibm/java-x86_64-70

5. Enter the command to encrypt the password:/opt/ibm/wlp/bin/securityUtility encode --encoding=aes new password

6. Update /opt/ibm/wlp/usr/shared/config/basicRegistry.xml with theencrypted password:<user id="apmadmin" name="apmadmin" password="new_encrypted_password"/>

7. Update the apmadmin password in SCR:/opt/ibm/ccm/SCR/XMLtoolkit/bin/setxmlaccess.sh -apmid apmadmin-apmpw new password

8. Enter the command to start the SCR service:start scr

9. Start the Application Performance Management console server:start apmui

10. Enter the command to start the monitoring infrastructure node:start fabricNode

What to do next

You can add and modify users in the basic user registry and assign user roles, asdescribed in the IBM SmartCloud Application Performance Management UI User'sGuide: “Configuring a basic user registry for Liberty profile” (http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/config_basic_user_reg.html) and “Mapping users to roles”(http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/creating_role_basic_user_registry.html).

Managing applicationsThe Application Performance Dashboard navigator has tools that you can use toadd or edit applications and their supporting software resources, or to remove anapplication.

When you add an application, you can create a new application and apply themanaged resources that are available, or select one from any discoveredapplications.

Before you begin

You must have administrator role privileges to use the Add, Remove, andEdit tools in the navigator.

The My Components application in the navigator contains the managed systemsthat were discovered by the monitoring infrastructure node. My Componentscannot be edited or deleted.

About this task

Complete the following steps to add, edit, or remove an application from theApplication Performance Dashboard.



http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.apm.doc_7.7/apm_ui_docs/apmui_77/creating_role_basic_user_registry.html

Procedure1. If the Application Performance Dashboard is not displayed, select it from the

Performance Menu or, if you are in the Getting Started page, clickView Application Status.

2. In the Applications section of the navigator, add, remove, or modify anapplication:v To add an application, click . The Add Application window is displayed.v To modify an application, select it and click . The Edit Application

window is displayed.v To remove an application, select it and click . After you click OK to

confirm, the application is deleted. This method does not uninstall thesupporting components; only their appearance in the ApplicationDashboard.

3. Click Read to open the Read Application window with a list of anydiscovered applications, and take one or more of the following steps.v Click Detail to see the components of an application.v Select the radio button for the application that you want to use, and click

Save. The Read Application window closes, the source repository isdisplayed in the Application read from: field, and the components arelisted in Application components.

v Click Cancel to close the window without making a choice.

A discovered application can save you the effort of defining an application.4. Enter or edit the name of your application in the Application name field. You

can add a description in the Description field. Do not use the ! " % & ’ * ?< > } { symbols in the name or description:

5. In the Template field, keep the Custom Application template or select adifferent template using the button, and click Save. Any associatedcomponent types and instances are shown in the Application components list.If you are editing an application, you cannot specify a different template,except for Custom Application.The Monitoring Agent for Ruby shows two Application components: RubyApplications, for monitoring all the Ruby applications on the managedsystem; and Enable Ruby App Situations, for monitoring thresholds that havebeen defined for instance (subnode) level attributes. Select Ruby Applicationsto see status for all your Ruby applications, however note that situation eventswill not be displayed in your application. To see events that are triggered bythresholds, select Enable Ruby App Situations, click , and select theapplication instance or instances that you want to monitor and view eventsfrom.

Important: If a monitoring agent is not showing in the Applicationscomponents list, it is possible that the user credentials for accessing thecomputer or VM where the agent is installed are incorrect. Click SystemConfiguration > Access Credentials to check for systems that do not havevalid user credentials. See “Access Credentials” on page 55.

6. To add components and instances to the application, take the following steps.a. Click and, in the Select Component window that opens, select a

component from the list. The Component Editor is displayed.b. Click an instance to select it or use the toolbar to search for

instances that contain the text in the search text box, select all instances, orclear all instances. You can also edit the component name, which is used asthe display name in the navigator for this application.


c. Click Add to add the instance or instances, and click Back.d. You can select another component to add instances to, or click Close.

The Application components list is updated with the new component names.A number in parentheses after the name indicates how many instances areassociated with the component.

7. To edit a component name or change the instance that is associated with it,select the component from the Application components list and click :a. To associate a different instance with the component, search for and select

the instance that you want.b. To change the component name that is used as the display name in the

navigator for this application, edit the Component name field.c. Click Save.

The Application components list is updated with the changes that you made.8. To remove a component or instance from the application, select it and click

. Click OK to confirm that you want to remove it.9. If other instances are related to the components in the Application

components list, a button that shows the number of related instances isdisplayed and you can take the following steps:a. Click the button to see the related instances in the Updated Details

window. A bar is shown for each type of update, with the name of theinstance below the bar. For example, if one of the components wasremoved, it shows below the Deleted components bar.

b. Select one or more instances and click Save to update the Applicationresources list.

10. Select from the Roles to access this application list and click Save. Only userswith the assigned roles can view the application data in the dashboard.

11. When you are finished creating or editing the application, close theapplication editor by clicking Save to save your changes, or Cancel to undothe changes.

Results

The new or edited application is displayed in the Application Dashboard and thenavigator Applications section. When the application is selected, the componentsare displayed in the Groups section. If you deleted an application, it is no longerdisplayed.

Advanced ConfigurationInitial monitoring infrastructure node configuration is done in the ConfigurationWizard.

Use the Advanced Configuration page to control communications settings andadvanced features such as event forwarding.

Agent Service InterfaceThe settings here are required information that is used by the infrastructurenode to configure communications with the monitoring agents.v Polling Interval controls the frequency, in minutes, for checking that a

monitoring agent is active. Default: 1 minute.


v Missed Poll Limit, in an IBM Application Performance Management(SaaS) environment, is the number of times that a monitoring agent doesnot respond to a polling event before it is considered to be offline.Default: 5 intervals.

v Port (HTTP) is the HTTP port that is used to communicate withmonitoring agents. Default: 51920.

v Secure Port (HTTPS) is the HTTPS port that is used to communicatewith monitoring agents. Default: 53661.

v Protocol is the default networking protocol to use for communicatingwith the monitoring agents. Default: http.

v Remove Offline System Delay determines the number of minutes towait before removing the display of an offline managed system from thedashboard. If the managed system comes back online, it is displayed inthe dashboard again. Default: 15 minutes.

Agent Central Configuration

v Host Name Override is an optional override for the host name or IPaddress of the Central Configuration Server if the value of theinfrastructure node is not correct.

v Refresh Interval controls the frequency, in minutes, that the monitoringagents use to query configuration details from the infrastructure node.Default: 5 minutes.

v Protocol establishes whether HTTP or HTTPS is the protocol tocommunicate with the monitoring agent. Default: HTTPS.

Trace The trace log component that is used to gather data about the performanceof the Application Insight system.v Package Level Trace String A regular expression string that describes

the classes to trace at a specified JLog level. Default:/com/ibm/tivoli/ccm/config\\.*:ERROR.

v Trace Level The level of detail for logging trace entries. The possiblevalues are, from lowest level to most detailed: ERROR, DEBUG_MIN,DEBUG_MID and DEBUG_MAX. Higher levels give you more detailedinformation, which is useful for investigating any problems or errorsthat occur. Default: ERROR.

v Maximum Log Files determines the number of log files to use beforewrapping the log entries. After the maximum is reached, the oldest logfile is replaced by the newest. Default: 5 files.

v Maximum File Size sets the maximum size of each log file in bytes.Default: 5000000 bytes (5 MB).

Event ManagerThe Event Manager controls the flow through (forwarding toNetcool/OMNIbus Probe for Tivoli® EIF and Simple Mail TransferProtocol) and the storage of received events.v EIF Port is the port to use for Event Integration Facility operations.

Default: 9998.v Event Cache Time determines the number of hours that events are

retained in the local cache, up to 96 hours. If the Event list is long,consider reducing the number of hours that are kept. Or, to see eventsover a weekend period, increase the number of hours. Default: 24 hours.

v Pure Event Close Time determines how long to leave a pure event openbefore closing it. Default: 24 hours.


v EIF Event Target(s) specifies the list of host names or IP addresses towhich all received Event Integration Facility events are forwarded. Forexample, if you are forwarding events to the Netcool/OMNIbus Probefor Tivoli EIF, enter the fully qualified host name or IP address of thecomputer where the probe is installed. Separate each host name with acomma (,), such as 9.87.65.111,9.12.34.115,myhostname.en.ibm.com.IPv6 addresses are not supported for EIF transmission.

v Master Reset Event controls whether to send a master reset event toclear previously received events. Default: True.

v Target Email Addresses specifies the email addresses that events areforwarded to. Separate each address with a comma (,), such [email protected],[email protected],[email protected].

v Email Subject Line is the text to use in the subject line of everyforwarded SMTP email event. Default: SCM-AI Event.

v Sending Email Account is the email address to use when sending anSMTP email event.

v Sending Email Account Password is the password that is associatedwith the sending email account.

v SMTP Server Address is the fully qualified host name of the SMTPserver that is used for sending events as emails, such as smtp.gmail.com.

v Use SSL determines whether to use SSL as the SMTP (Simple MailTransfer Protocol) transport mechanism. Default: False.

v SMTP Port is the port number to use for sending SMTP email. Default:25.

v SSL SMTP Port is the port number to use for sending SMTP emailusing the SSL (Secure Socket Layer) protocol. Default: 465.

HTTP InterfaceThe HTTP interface is used with the Agent Service Interface tocommunicate with the data sources. The time-out values are controlledhere. If the connection times out frequently, consider increasing thetime-out and retry values.v Connection Timeout is the amount of time to wait before an HTTP

connection attempt fails. Default: 2 seconds.v Read Timeout is the amount of time to wait before an HTTP read

attempt fails. Default: 4 seconds.

SDP AdapterThe Socket Direct Protocol (SDP) adapter is responsible for providing theinterface between SmartCloud Monitoring - Application Insight and theunderlying cloud platform.v Discovery Plug-ins determines the plug-in to be started. Select the type

of discovery plug-in from the list: SCP, OTHER, VMWARE, AMAZON.v Discovery Interval is the time to wait between discovery cycles. Default:

30 seconds.

Important: If you change from one discovery type to another, such as fromVMware to Other, you must log into the VM where the infrastructure nodeis installed and issue these commands:1. stop fabricNode

2. stop server1

3. start fabricNode

4. start server1


You do not have to enter the commands the first time that you select adiscovery plug-in; only after you change from one type to a different type.

SDP Adapter - Amazon Plug-inAn SDP adapter specifically to support integration with the Amazon EC2environment.v Amazon Access Key is the access key that is associated with the

Amazon Web Service account.v Amazon Secret Key is the secret key that is associated with the Amazon

Web Service account.v Amazon Regional End-point is the URL that represents the entry point

for the Amazon Web Service.

SDP Adapter - Other Plug-inIn an environment where you know the identity of the resources that youwant to monitor, you can provide the host names and IP addresses in a filethat is used by the monitoring infrastructure node for discovery.v File Name is the fully qualified path and name of the text file that

contains the resource identifiers. For more information, see “Configuringthe infrastructure node for other systems” on page 26. Default:/opt/ibm/ccm/ips.txt.

SDP Adapter - SCP Plug-inA SmartCloud Provisioning plug-in that provides support for the IBMSmartCloud Provisioning environment.v Access ID is the user ID that is used for SmartCloud Provisioning

authentication.v SCP Web Service Host is the SmartCloud Provisioning Web Service host

name.v SCP Web Service Port is the SmartCloud Provisioning Web Service port.

Default: 5678.v SCP Service Region determines the region that defines the SmartCloud

Provisioning service type. Default: query.v Private Key is the text version of the private key. Example:

-----BEGIN RSA PRIVATE KEY-----MIIBOwIBAAJBAMT4+BqTONg6w94VB1YHRTr4TIa9u9nX5ng/FmupfpGTrseS0W6aLTNSQLqmPMzumilEt6Zml6c04kRX6lrR8NUCAwEAAQJBAKssVaf6kubOQtLnYWWwkchKaW6ayfnpNv7+jERpmnV05CS1Pk5Kqxa3MEIwQzvGHC3QSabqef95TJxOgYhBv6ECIQDr8mjucvFFjOvTlyK+oMMQtgvevgM4zpPviWQNHuGfnQIhANW2lA6TtuxBbdxufcX+EGD0n+ex96ik7l5YZELA1/yZAiEAurbMHtZK4/UOshSJ5Dyn4NOPNSc8uXmQTCB3UoK7nWkCIFLvlMuHZZCP36uQsXyZmQ+XP0ryFLM8tkikstv47JjZAiA2WQBTwZi3FVjlUyEeck2iXSf+Duky4S9LNahCVOz1Vg==-----END RSA PRIVATE KEY-----

v SCP Requests Timeout is the number of seconds to wait before arequest to SmartCloud Provisioning times out. Default: 30 seconds.

SDP Adapter - VMware Plug-inAn SDP adapter that provides support for the VMware environment.v Virtual Center User Name is a user ID with sufficient privileges to

collect monitoring data.v Virtual Center Password is the password for the Virtual Center User

Name.v Virtual Center Host is the Virtual Center host name.


v Virtual Center Port is the Virtual Center port. Default: 80 when SSL isdisabled; 443 when SSL is enabled.

v Use SSL determines whether to use an SSL connection to the VirtualCenter. Default: False.

v Validate Certificates determines whether certificate host names must bevalidated. Default: False.

TruststoreThe truststore is the internal security key repository.v Java Keystore File is the fully qualified path of the keystore file

containing the collection of certificates trusted by this client. Default:/opt/ibm/ccm/CCM-Certs/ccm.truststore.

v Java Keystore File Password is the password to access the keystore filethat contains the collection of certificates trusted by this client.

Default VM CredentialsThe default operating system credentials that are used to attempt access tothe managed data source for collecting data.v Default User ID is the user ID to be tried for all monitoring agents that

are used to collect data. Default: root.v Default Password is the password to be tried for all monitoring agents

that are used to collect data. Default: passw0rd.

If you have the Default Linux VM Credentials and Default Windows VMCredentials set, the monitoring infrastructure node determines thecredentials to use for accessing a monitoring agent by the OS agent that isinstalled on that managed system. If, however, no OS agent is installed onthe managed system, the main default user credentials are used.

If the default user credentials are not valid for a particular managedsystem, use the Access Credentials page to enter the correct credentials forthat managed system. For more information, see “Access Credentials” onpage 55.

Default Linux VM CredentialsWhen the Monitoring Agent for Linux OS is installed on a computer orVM in the monitored environment, these are the default operating systemcredentials that are used to attempt access to the Linux OS agent and anyother monitoring agents installed on the Linux system for collecting data.

If the Default VM Credentials are set for the Linux operating system, youdo not have to set them here.v Default User ID is the user ID to be tried for all monitoring agents that

are used to collect data.v Default Password is the password to be tried for all monitoring agents

that are used to collect data.

Default Windows VM CredentialsWhen the Monitoring Agent for Windows OS is installed on a computer orVM in the monitored environment, these are the default operating systemcredentials that are used to attempt access to the Windows OS agent andany other monitoring agents installed on the Windows system forcollecting data.v Default User ID is the user ID to be tried for all monitoring agents that

are used to collect data.v Default Password is the password to be tried for all monitoring agents

that are used to collect data.


Related tasks:“Configuring the infrastructure node for SmartCloud Provisioning” on page 14“Configuring the infrastructure node for Amazon EC2” on page 18“Configuring the infrastructure node for VMware” on page 22“Configuring the infrastructure node for other systems” on page 26



Chapter 4. Troubleshooting

Review the troubleshooting topics for problems you might experience withinstalling, configuring, or using SmartCloud Monitoring - Application Insight.

You can find more troubleshooting information at the following links:v For the Linux OS agent and Windows OS agent, see the IBM Tivoli Monitoring

V6.3 FP2 documentation on the wiki.v For the Response Time Monitoring Agent, see the “Troubleshooting: Web

Response Time” topic in the SmartCloud Application Performance ManagementInformation Center.

v For the WebSphere Applications agent, see the Application PerformanceDiagnostics documentation on the wiki.

Installation troubleshootingReview the installation troubleshooting symptoms and solutions for help withinstallation and upgrade issues.

Agent installation failsIf the monitoring agent fails to install, you can run commands to clean up theenvironment, and start the installation again.

Also, check the installation path. The agent installation fails if parentheses orspaces are included in the installation path. For example, C:\mydownloads\APMaaS_Agent_Install_1.1(1) must be amended toC:\mydownloads\APMaaS_Agent_Install_1.1 for a successful installation.

If a monitoring agent installation or upgrade from a previous version fails, theinstallation might have been terminated abnormally. For example, you might closethe command window while the monitoring agent is being upgraded. An errormessage is displayed, such as KCICF9004E: Installation failed. SeeC:\IBM\ITM\InstallITM\Abort*.log file for more details.

Agent installation or upgrade failsIf the installer reports that the agent installation or upgrade fails, use thefollowing command to uninstall the monitoring agent, and start theinstallation again:

name_agent.sh uninstall

name_agent.bat uninstall

where name is the type of monitoring agent, such as os or rt.

If the uninstall command fails, clean up the environment and run thesmai-agent.sh ininstall_all.sh or agent_cleanup.bat script and start theinstallation again.

Framework installation or upgrade failsIf the installer reports that the framework installation or upgrade fails,clean up the home directory and use the following command to uninstallall monitoring agents, and start the installation again:

smai-agent.sh uninstall_all


https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Monitoring/page/Version%206.3%20Fix%20Pack%202%20documentation

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli%20Monitoring/page/Version%206.3%20Fix%20Pack%202%20documentation

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/TSG/itcam_rt62-probdetermgd37.html

http://publib.boulder.ibm.com/infocenter/tivihelp/v63r1/topic/com.ibm.itcamt.doc_7.4.0.0/rt/TSG/itcam_rt62-probdetermgd37.html

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Application%20Performance%20Diagnostics/page/Documentation%20for%20APD

https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Application%20Performance%20Diagnostics/page/Documentation%20for%20APD

smai-agent.bat uninstall_all

Uninstallation failsIf the uninstall command fails, clean up the environment, run thefollowing command, and start the installation again.

smai-agent.sh ininstall_all

agent_cleanup.bat

On Windows, the clean up script is available after agent installation atC:\IBM\ITM\InstallITM\. On Linux, the script for cleanup is at/opt/ibm/ccm/agent/bin/.

Recovering from an interrupted monitoring infrastructurenode upgrade

An interruption in the monitoring infrastructure node upgrade from SmartCloudMonitoring - Application Insight Version 1.2 Fix Pack 1 to Fix Pack 2 can cause anabnormal termination of the installation process.

Complete the procedure to recover from an upgrade failure, and start theinstallation again.

Procedure1. Check the status of the application server and the Application Performance

Management console server:a. status server1

b. status apmui

2. If the server1 or apmui is running, stop the process:a. stop server1

b. stop apmui

3. If you can locate an /opt/ibm/wlp/usr/servers/apmui/apps/dbdir.bakdirectory, take the following steps:a. Remove the /opt/ibm/wlp/usr/servers/apmui/apps/dbdir directory.b. Rename the /opt/ibm/wlp/usr/servers/apmui/apps/dbdir.bak directory to

/opt/ibm/wlp/usr/servers/apmui/apps/dbdir.4. If you can locate an /opt/ibm/wlp/usr/servers/server1/apps/scrderby/

dbdir.bak directory, take the following steps:a. Delete the /opt/ibm/wlp/usr/servers/server1/apps/scrderby/dbdir

directory.b. Rename the /opt/ibm/wlp/usr/servers/server1/apps/scrderby/dbdir.bak

directory to /opt/ibm/wlp/usr/servers/server1/apps/scrderby/dbdir.5. Start the monitoring infrastructure node installation script again unless you

have completed the upgrade.6. After the upgrade is complete, verify that the /opt/ibm/ccm/logs/

upgscrdb_fp2.out directory exists.7. If the /opt/ibm/ccm/logs/upgscrdb_fp2.out does not exist, take the following

steps:a. Create an /opt/ibm/wlp/usr/servers/server1/apps/scrderby/upgrade

directory.b. Copy the contents of the /opt/ibm/ccm/SCR/schema_update/6.1.2.1_6.1.2.2

directory to /opt/ibm/wlp/usr/servers/server1/apps/scrderby/upgrade.


c. Change to the /opt/ibm/wlp/usr/servers/server1/apps/scrderby/upgradedirectory.

d. Enter upgscrdb_fp2.sh to start the upgrade script.8. Start the application server and Application Performance Management console

server:a. start server1

b. start apmui

Getting Started links blocked in ChromeIn the Chrome v21 browser, you are blocked from going to the linked page.Review the description and solution.

SymptomWhen using the Chrome v21 or later browser, you are blocked fromopening the links in the Getting Started page.

DiagnosisStarting with Chrome v21, any unsecured (HTTP rather than HTTPS) orunauthenticated browser links are blocked.

SolutionClick the shield tool and select “Load unsafe script”" to continue to thepage. Alternatively, right-click the link and select “Open in new tab” or“Open in new browser” to continue to the page.

My Components applicationAny discovered managed systems are shown in an application named MyComponents in the Application Performance Dashboard. You can disable the MyComponents application to improve performance if your application repository hasmany components.

SymptomAfter you click My Components in the Applications section of thenavigator, it takes a long time for the My Components ApplicationDashboard to display.

DiagnosisWhen a large number of components is stored in the application repositoryof SmartCloud Monitoring - Application Insight, enabling the MyComponents application might cause performance issues.

SolutionComplete the following steps to disable the My Components application:1. On the system where the monitoring infrastructure node is running,

change to the following directory:/opt/ibm/wlp/usr/servers/apmui/apps/customCfg

2. Open apmui.cfg in a text editor and set ENABLE_MY_COMPONENTS to false:ENABLE_MY_COMPONENTS=false

3. Run the following command for the changes to take effect:./apmcfg.sh -o APM_UI_port -u APM_admin -p APM_password

whereAPM_UI_port is 9443 for HTTPS (or 8080 for HTTP)APM_admin is a user ID with administrative authority (apmadmin is the

Chapter 4. Troubleshooting 67

default)APM_password is the password that is associated with the user ID

Dashboard error occurred while loading dataIf the dashboard for the selected data source displays an error message instead ofmetrics, the operating system user credentials for the monitoring agent might needto be added to the Access Authorization Group Profile (AAGP).

SymptomAfter you respond to a lock indicator by entering the operating systemuser credentials for the data source, data can be sent to the SmartCloudMonitoring - Application Insight dashboards. If you enter a non-root userID, such as apmadmin, no data is displayed on the dashboard. Instead, youget a message that an error occurred while loading data sources.

DiagnosisBy default, monitoring agents are configured to require root usercredentials to access Agent Service Interface (ASI) transactions.

SolutionTo change this default, you can customize the IBM Tivoli MonitoringAccess Authorization Group Profile (AAGP) to specify user IDs to beincluded in the Administrative group, so that the user has access to all ASItransactions. The non-root user must have a valid user ID on the targetsystem that they can use to log on and does not require root authority ormembership in any specific group. To customize the agent AAGP, takethese steps:1. Log on to the ASI using the root ID (such as http://

agentIPaddress:51920).2. Select Service Interface Request.3. Enter ListAAGP in the text box and click Submit the Request to get the

default AAGP specification.4. Copy the default specification that is displayed in the Agent Response

Payload box, and paste into a text editor. Sample payload:<AAGP><AAGROUP><GROUPNAME>Administrative</GROUPNAME><CLI>ExecCommand</CLI><REFLEXAUTO>ExecAction</REFLEXAUTO><SIAPI>AAGP</SIAPI>SIAPI>AgentInfo</SIAPI>SIAPI>AttrList</SIAPI>SIAPI>CnfgCommand</SIAPI>SIAPI>CnfgControl</SIAPI>...

5. Edit the text to add the smadmin to the AD (administrative) group, asshown in the following example:<ASSIGN>OP</ASSIGN></AAUSER><AAUSER><ID>root</ID><ASSIGN>AD</ASSIGN></AAUSER><AAUSER>


<ID>smadmin</ID><ASSIGN>AD</ASSIGN></AAUSER></AAGP>

6. To reconfigure the agent without restarting it, change the first line ofthe file to <AAGP REFRESH="Y">.

7. Save the text file (for example AAGPupdate.txt).8. Return to the Service Interface Request page and paste the updated

AAGP specification from the text file to the input box and click Submitthe Request.

After the “Request completed successfully” response is displayed, theagent has a new file named lz_aagpcnfg.txt in the $CANDLEHOME$/localconfig/lz directory. It has the configuration necessary for the user(such as smaiuser) to access ASI transactions and for the monitoringinfrastructure node to connect to the agent and retrieve data.

Dashboards show no data, partial data, or incorrect data from themonitoring agent

If you do not see data in the Application Performance Dashboard for a particularmonitoring agent, check for time out errors and ensure you are using NTP(Network Time Protocol) on the monitored system.

Additionally, review the agent-specific solutions in this topic.

SymptomIn the Application Performance Dashboard ( Performance >Application Performance Dashboard), you see no data, partial data, orincorrect data for a specific agent or agents after selecting an item in theGroups or Instance section of the navigator.

Diagnosis and SolutionThis problem can occur when the monitoring agent's clock is notsynchronized with your Application Performance Management console. Ifthe agent's clock is set ahead of the infrastructure clock, the agent mightnot download the latest configuration from the infrastructure.

Use NTP (Network Time Protocol) on monitored systems to insure the timeon the system running the agent is accurate. Time zones must be setcorrectly for the time zone they are in, such as UTC-3 for Brasilia and UTC+9 for Seoul.

If your problem was not solved by using NTP, review the logs toinvestigate further.

All monitoring agents:On the system where the monitoring agent is installed, review themost recent agent log for any command timeout messages. Agentlog names are host_name_pc_agent_instance_name_timestamp.log

wherehost_name is the name of the system on which the agent isinstalledpc is the two-character product code, such as kj or km

agent_instance_name is the name that was given to the instanceduring agent configurationtimestamp is the time and date when the log was saved


and the path isopt/ibm/ccm/agent/logs

C:\IBM\ITM\TMAITM6_x64\logs

If you see that command timeout messages appear frequently, theagent's shell script might be taking too long to return withinformation and is timing out. The time out period is controlled inthe pc_agent_instance_name.config file by theCDP_DP_SCRIPT_TIMEOUT environment variable, which has a defaultvalue of 30 seconds. Set CDP_DP_SCRIPT_TIMEOUT andCDP_DP_REFRESH_INTERVAL to higher values to give the scriptsenough time to complete successfully.

PHP agent:Your Apache version might be lower than the supported version.Check the Apache HTTP Server httpd.conf configuration file andensure that both the mod_status and ExtendedStatus On options areenabled. For more information, see “Configuring the PHP agent”on page 38.

Ensure the PHP agent plug-in in WordPress is activated. For moreinformation, see “Configuring the PHP agent” on page 38.

In the WordPress List widget, you might see PHP or a different textstring listed under WordPress Document Root. This text string doesnot follow the standard format for the WordPress Document Root.This error might be caused by a PHP module exception. To ensurethe PHP modules are working, execute the php -m command.Correct any modules with warnings or exceptions.

Ruby agent:On the system where the monitoring agent is installed, review thekm_agent_instance_name_script.log for any entries withCMD=CONNECTION that start withapp_name#app_root_directory#IP_address#port_number#pid#mem.

Each line following the timestamp corresponds to a different Rubyapplication. For example, if a user has an application named“MongoStore” with root directory /root/Ruby/mongodb_store, oneof the rows might look like this example:

MongoStore#/root/Ruby/mongodb_store#9.42.14.228#4444#20522#4959124

9.42.14.228 corresponds to the IP address of the system thatthe application is on4444 corresponded to the application's listening port number20522 corresponds to the product ID of the application4959124 corresponded to the system's memory

If the line starts with the pound sign (#) instead of the app_name,you must reconfigure the Ruby agent instance to include the Rubyruntime binary location.

Dashboard shows no events or event statusIf you can see metrics from a data source but no severity indicator is displayed inthe Application Performance Dashboard Events tab, or no threshold events arebeing reported, you might need to restart the monitoring agent.


Diagnosis and ResolutionThe monitoring agents for SmartCloud Monitoring - Application Insightrequire a certain version number (see “Dependencies” on page 5). If youhave an earlier version of the monitoring agent installed, you must stopand restart the agent before it can send events to the monitoringinfrastructure node. You must also restart the agent after updating thethresholds or historical data collection before you can see the effect of yourchanges.

If the thresholds are for the Monitoring Agent for Ruby, edit theapplication to confirm that Enable Ruby App Situations is set and theinstances that you want to monitor are selected. For more information, see“Managing applications” on page 56 and the Ruby agent note after step 5on page 57.

Threshold events have unknown severity after agent recycleIf the monitoring agent is stopped and restarted, the event severity information islost and any new events show a severity of Unknown.

Thresholds are not applied to the monitoring agentAfter a threshold is created, the threshold is never applied to the monitoring agent.This problem might occur because of a time synchronization issue.

SymptomAfter a new threshold is created for a data source in the ThresholdManager, the threshold is never applied to the monitoring agent.

DiagnosisThis problem can occur when the monitoring agent's clock is notsynchronized with your Application Performance Management console. Ifthe agent's clock is set ahead of the infrastructure clock, the agent mightnot download the latest configuration from the infrastructure.

SolutionUse NTP (Network Time Protocol) on monitored systems to insure the timeon the system running the agent is accurate. Time zones must be setcorrectly for the time zone they are in, such as UTC-3 for Brasilia and UTC+9 for Seoul.

Changed language but some text is still in EnglishAfter setting the language in your browser, you still see some text in English.Review the diagnosis and possible resolution.

SymptomYou set the primary language in your browser, closed down all browserwindows, restarted the browser, and logged in. Most of the ApplicationPerformance Management console content appears in the language thatyou set but some text is still in English.

DiagnosisSome of the supported browsers distinguish between text returned fromthe monitoring infrastructure node and text rendered locally, and treat thetranslations differently.v In Mozilla Firefox, there is no difference and you should see everything

in the language you set.


v In Google Chrome, if you selected your preferred language andhighlighted it but did not click Display Google Chrome in thislanguage, you might see some text in English.

v In Microsoft Internet Explorer, you might see some text in English.

Solution

v In Google Chrome, return to the language settings, select your preferredlanguage and click Display Google Chrome in this language.

v In Microsoft Internet Explorer, set the operating system for yourlanguage.

Restriction: Some agents, installation scripts, names of data sets, and theircomponent attributes are not translated. This is a current limitation.

Locale supportSmartCloud Monitoring - Application Insight supports the IBM Group 1 languagesand several other languages. The Language Licenses are translated in the IBMGroup 1 languages and the other supported languages, with the exception ofHungarian and Thai.

This product supports the IBM Group 1 languages, which are listed here:v Germanv Spanishv Brazilian Portuguesev Frenchv Italianv Japanesev Koreanv Traditional Chinesev Simplified Chinesev Russian

The following languages are also supported:v Thaiv Czechv Polishv Hungarian

Language licences are translated into the following languages:v Czechv Germanv Greekv Englishv Spanishv Frenchv Indonesianv Italianv Japanesev Korean


v Lithuanianv Polishv Portuguesev Russianv Slovenianv Turkishv Chinesev Traditional Chinese

Collecting monitoring infrastructure logs for IBM SupportGather the log files from the monitoring infrastructure node when requested byIBM Support to help diagnose issues with SmartCloud Monitoring - ApplicationInsight.

Before you begin

Root permission is required to collect system information from the monitoringinfrastructure node.

About this task

To run the log collection command, complete the following steps:

Procedure1. On the command line, change to the monitoring infrastructure node directory:

/opt/ibm/ccm/

2. Run the following command:./collectLogs.sh

A tar.gz file with a time stamp in the file name is generated in the /tmpdirectory, such as /tmp/SCMAI_Logs_Collection_20131114_094335.tar.gz.If a message says that the system cannot find the path specified, you can ignorethe message because it is harmless.

3. Send the output file to your IBM Support representative.

Results

The script gathers the following component logs:

Table 9. Log files created by the collectLogs.sh script

Component Log directory Log file name Description

Monitoring infrastructure node

Monitoringinfrastructure node

/opt/ibm/ccm/logs min.log The main monitoringinfrastructure node log.

server1.log The Server1 communication log.

ccm.trace.log Trace file records the internaloperations of the monitoringinfrastructure node.


Table 9. Log files created by the collectLogs.sh script (continued)


System Informationof monitoringinfrastructure node

/opt/ibm/ccm/logs/sysinfo

machine.info Date and time of collection,hostname, and network interfaceconfiguration.

system.info System hardware andconfiguration information.

cpu.info, memory.info,disk.info

CPU, memory, and diskconfiguration information.

mount.info Information about mountedvolumes.

nsswitch.conf Copy of etc/nsswitch.conf.

hosts Copy of etc/hosts.

resolve.conf DNS information generated bythe Network Manager.

tasklist.info Task list at time of collection.

maint.info Software packages installed atthe time of collection.

OSLC ProviderService

/opt/ibm/ccm/oslc_pm/logs

candle_installation.log Include installation environmentinformation that is collected ateach restart.

UpdateAutoRun.log Sets up automation environment.

hostname_as.inv Index of log files.

hostname_as_NNNNNN.log Trace file for OSLC PerformanceMonitoring service.

/opt/ibm/ccm/oslc_pm_lx8266/as

itmevents.log Log of the IBM TivoliMonitoring events processed bythe OSLC PerformanceMonitoring service.

SCR XML Toolkit /opt/ibm/ccm/SCR/XMLToolKit/log

msgGTM_CI.log.N

msgGTM_XT.log.N

msgGTM_XT.log.N.lck

traceGTM_CI.log.N

traceGTM_XT.log.N

traceGTM_XT.log.N.lck

/opt/ibm/ccm/SCR/XMLToolkit/bin

xmltoolkitsvc.properties XML Toolkit configurationinformation.

/opt/ibm/ccm/SCR/XMLToolkit/log/install/maintenance

DB maintenance scripts and SQLinformation.

Gaian DB

Gaian DB /opt/ibm/gaian gaiandb.log Gaian Node startup andperformance information.

derby.log Gaian Derby startupinformation.

*.properties Gaian configuration information.

WAS Liberty Servers - Server 1




Server1 Main /opt/ibm/wlp/usr/servers/server1

server.xml, jvm.options,bootstrap.properties

Server1 server JVM andconfiguration information.

Server1 Logs /opt/ibm/wlp/usr/servers/server1/logs

messages.log Server1 standard messages.

trace.log Server1 trace logs.

kd8collect<date_time>.tar.gz

Archive that contains CURI DataProvider debug information.

console.log Server1 standard outputcontaining startup, session,transaction, and shutdowninformation.

SCR in Server 1 /opt/ibm/wlp/usr/servers/server1/logs

scrderby.log Service Component RepositoryDerby startup information.

scrserver.log SCR Server process logs.

scrserver-errors.log SCR Server process errormessages.

ccm.trace.log monitoring infrastructure nodeServer1 communications log.

Server1 FFDC /opt/ibm/wlp/usr/servers/server1/logs/ffdc

ffdc_date_time.N.log First failure data capture logs.

exception_summary_date_time.N.log

Exception summaries from FFDCprocessing.

IBM TivoliMonitoring CDP inServer1

/opt/ibm/wlp/usr/servers/server1/kd8/bin

Run export_events.sh togenerate the file:export_gaian_events.txt

SmartCloud Monitoring -Application Insight dashboarddata provider dump of eventinformation from the followingtables:

v CCM_CONFIG_MAIN

v CCM_SITUATIONS

v CCM_EVENTS

Run export_msys.sh to generatethe file:export_gaian_msys.txt

Dashboard data provider dumpof the managed systemsinformation from the followingtables:

v CCM_CONFIG_MAIN

v ELAS_KNOWN_AGENTS

v ELAS_KNOWN_CHANGE_LOG

v ELAS_KNOWN_INSTANCES

v ELAS_KNOWN_IPS

v ELAS_KNOWN_ITM_AGENT_INFO

v ELAS_KNOWN_ITM_SUBNODES

v ELAS_KNOWN_VMS

WAS Liberty Server - APM console




APM UI ServerMain

/opt/ibm/wlp/usr/servers/server1

server.xml, jvm.options,bootstrap.properties

Application PerformanceManagement console (APM UI)server JVM and configurationinformation.

APM UI Server Logs /opt/ibm/wlp/usr/servers/apmui/logs

messages.log APM UI server standard errormessages.

trace.log APM UI server trace log.

console.log APM UI server standard outputcontaining startup, session,transaction, and shutdowninformation.

APM_UI.log APM UI process log.

derby.log APM UI Derby log.

itp.log IT Portal log containing clientand server information.

ccm.trace.log Monitoring infrastructure nodeServer1 communications log.

APM UI FFDC /opt/ibm/wlp/usr/servers/apmui/logs/ffdc

ffdc_date_time.N.log First failure data capture logs.

exception_summary_date_time.N.log

Exception summaries from FFDCprocessing.

/opt/ibm/wlp/usr/servers/apmui/apps

components.log List of installed components inAPM UI.

Collecting monitoring agent logs for IBM SupportUse the problem determination collection tool, pdcollect, to gather required logs andother problem determination information that is requested by IBM Support formonitoring agents.

The PD collector tool is installed with each monitoring agent.

Before you begin

Root or administrator permission is required for the PD collector tool to collectsystem information from the monitoring agents. You can review the agent logsindividually in the (Linux) opt/ibm/ccm/agent/logs and (Windows)C:\IBM\ITM\TMAITM6_x64\logs folders.

About this task

To run the PD collector tool, complete the following steps:

Procedure1. On the command line, change to the agent directory:

v /opt/ibm/ccm/agent/bin

v C:\IBM\ITM\BIN

2. Run the following command:v ./pdcollect


v pdcollect

A file with a time stamp in the file name is generated in the tmp directory, suchas /tmp/pdcollect-nc049021.tar.Z.

3. Send the output file to your IBM Support representative.



Privacy policy considerations

IBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may usesession cookies that collect each user’s user name for purposes of sessionmanagement, authentication, and single sign-on configuration. These cookies canbe disabled, but disabling them will also likely eliminate the functionality theyenable.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, See IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details thesection entitled “Cookies, Web Beacons and Other Technologies” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy


Accessibility

Accessibility features help users with physical disabilities, such as restrictedmobility or limited vision, to use software products successfully. SmartCloudMonitoring - Application Insight supports a command prompt interface forinstallation and a web-based interface for configuration and usage. Productfunctionality and accessibility features vary according to the interface.

The major accessibility features in this product enable users in the following ways:v Use assistive technologies, such as screen-reader software and digital speech

synthesizer, to hear what is displayed on the screen. Consult the productdocumentation of the assistive technology for details on using those technologieswith this product.

v Operate specific or equivalent features using only the keyboard.v Magnify what is displayed on the screen.

In addition, the product documentation was modified to include the followingfeatures to aid accessibility:v All documentation is available in both HTML and convertible PDF formats to

give the maximum opportunity for users to apply screen-reader software.v All images in the documentation are provided with alternative text so that users

with vision impairments can understand the contents of the images.

Application Insight and its related publications, are accessibility-enabled. For moreinformation about the accessibility features of the information center, seeAccessibility and keyboard shortcuts in the information center.

Interface information

The interface offers the greatest range of functionality, but is not entirely accessible.

Navigating the interface using the keyboard

Standard shortcut and accelerator keys are used by the product and aredocumented by the operating system. See the documentation provided by youroperating system for more information.

Magnifying what is displayed on the screen

You can enlarge information on the product windows using facilities provided bythe operating systems on which the product is run. For example, in a MicrosoftWindows environment, you can lower the resolution of the screen to enlarge thefont sizes of the text on the screen. See the documentation provided by youroperating system for more information.

IBM and accessibility

See the IBM Human Ability and Accessibility Center for more information aboutthe commitment that IBM has to accessibility.


http://publib.boulder.ibm.com/infocenter/tivihelp/v15r1/topic/com.ibm.help.ic.doc/info_accessibility.html

http://www.ibm.com/able/index.html


Notices

This information was developed for products and services offered in the U.S.A.IBM may not offer the products, services, or features discussed in this document inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, program, or service may be used. Any functionally equivalent product,program, or service that does not infringe any IBM intellectual property right maybe used instead. However, it is the user's responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not give youany license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785 U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBMIntellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan, Ltd.19-21, Nihonbashi-Hakozakicho, Chuo-kuTokyo 103-8510, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law :

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE.

Some states do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement might not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

Any references in this information to non-IBM Web sites are provided forconvenience only and do not in any manner serve as an endorsement of those Websites. The materials at those Web sites are not part of the materials for this IBMproduct and use of those Web sites is at your own risk.


IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purposeof enabling: (i) the exchange of information between independently createdprograms and other programs (including this one) and (ii) the mutual use of theinformation which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758 U.S.A.

Such information may be available, subject to appropriate terms and conditions,including in some cases payment of a fee.

The licensed program described in this document and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement or any equivalent agreementbetween us.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environments mayvary significantly. Some measurements may have been made on development-levelsystems and there is no guarantee that these measurements will be the same ongenerally available systems. Furthermore, some measurement may have beenestimated through extrapolation. Actual results may vary. Users of this documentshould verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly available sources.IBM has not tested those products and cannot confirm the accuracy ofperformance, compatibility or any other claims related to non-IBM products.Questions on the capabilities of non-IBM products should be addressed to thesuppliers of those products.

All statements regarding IBM's future direction or intent are subject to change orwithdrawal without notice, and represent goals and objectives only.

This information is for planning purposes only. The information herein is subject tochange before the products described become available.

This information contains examples of data and reports used in daily businessoperations. To illustrate them as completely as possible, the examples include thenames of individuals, companies, brands, and products. All of these names arefictitious and any similarity to the names and addresses used by an actual businessenterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, whichillustrate programming techniques on various operating platforms. You may copy,modify, and distribute these sample programs in any form without payment toIBM, for the purposes of developing, using, marketing or distributing applicationprograms conforming to the application programming interface for the operatingplatform for which the sample programs are written. These examples have not


been thoroughly tested under all conditions. IBM, therefore, cannot guarantee orimply reliability, serviceability, or function of these programs. You may copy,modify, and distribute these sample programs in any form without payment toIBM for the purposes of developing, using, marketing, or distributing applicationprograms conforming to IBM's application programming interfaces.

Each copy or any portion of these sample programs or any derivative work, mustinclude a copyright notice as follows: © (your company name) (year). Portions ofthis code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp.2014. All rights reserved.

If you are viewing this information in softcopy form, the photographs and colorillustrations might not be displayed.

Trademarks

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Notices 85

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Privacy policy considerations

IBM Software products, including software as a service solutions, (“SoftwareOfferings”) may use cookies or other technologies to collect product usageinformation, to help improve the end user experience, to tailor interactions withthe end user or for other purposes. In many cases no personally identifiableinformation is collected by the Software Offerings. Some of our Software Offeringscan help enable you to collect personally identifiable information. If this SoftwareOffering uses cookies to collect personally identifiable information, specificinformation about this offering’s use of cookies is set forth below.

Depending upon the configurations deployed, this Software Offering may usesession cookies that collect each user’s user name for purposes of sessionmanagement, authentication, and single sign-on configuration. These cookies canbe disabled, but disabling them will also likely eliminate the functionality theyenable.

If the configurations deployed for this Software Offering provide you as customerthe ability to collect personally identifiable information from end users via cookiesand other technologies, you should seek your own legal advice about any lawsapplicable to such data collection, including any requirements for notice andconsent.

For more information about the use of various technologies, including cookies, forthese purposes, See IBM’s Privacy Policy at http://www.ibm.com/privacy andIBM’s Online Privacy Statement at http://www.ibm.com/privacy/details thesection entitled “Cookies, Web Beacons and Other Technologies” and the “IBMSoftware Products and Software-as-a-Service Privacy Statement” athttp://www.ibm.com/software/info/product-privacy.

TrademarksIBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corp., registered in many jurisdictions worldwide.Other product and service names might be trademarks of IBM or other companies.A current list of IBM trademarks is available on the web at “Copyright andtrademark information” at www.ibm.com/legal/copytrade.shtml.

Adobe, Acrobat, PostScript and all Adobe-based trademarks are either registeredtrademarks or trademarks of Adobe Systems Incorporated in the United States,other countries, or both.

IT Infrastructure Library is a registered trademark of the Central Computer andTelecommunications Agency which is now part of the Office of GovernmentCommerce.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo,Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks orregistered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux is a trademark of Linus Torvalds in the United States, other countries, orboth.


http://www.ibm.com/privacy

http://www.ibm.com/privacy/details

http://www.ibm.com/software/info/product-privacy

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

ITIL is a registered trademark, and a registered community trademark of TheMinister for the Cabinet Office, and is registered in the U.S. Patent and TrademarkOffice.

UNIX is a registered trademark of The Open Group in the United States and othercountries.

Java and all Java-based trademarks and logos are trademarks or registeredtrademarks of Oracle and/or its affiliates.

Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in theUnited States, other countries, or both and is used under license therefrom.

Linear Tape-Open, LTO, the LTO Logo, Ultrium, and the Ultrium logo aretrademarks of HP, IBM Corp. and Quantum in the U.S. and other countries.

Notices 87


Index

Numerics64-bit Intel/AMD64 5

AAccess Credentials page 55accessibility features 81advanced configuration 58agent service interface 58agents

See monitoring agentsAmazon EC2

configuring 18installing 16SDP adapter 61

apmadmin 55applications 56

Ccertificate validation

VMware 24Chrome 67commands 52configuration

advanced 58configuring

agents 35MongoDB agent 35MySQL agent 37PHP agent 38PostgreSQL agent 40Python agent 41Response Time Monitoring

Agent 43Ruby agent 44WebSphere Applications agent 46

consumer VMRed Hat Enterprise Linux 5

cookies 79, 86copyright 83

Ddashboard

data source loading error 68dashboards

no events displayed 71troubleshooting 67

data source loading error 68data sources 51

port 58dependencies 5disk space 8

Eemail configuration 59

error logSee trace log

event integration facility 59event manager 59events

flow and storage configuration 59

Ffirewall

access key ID 10Amazon Web Services 10

GGetting Started 67

HHTTP interface 60

IIBM Group 1 languages 72infrastructure node 52

configuring Amazon EC2 18configuring SmartCloud

Provisioning 14configuring VMware 22installing Amazon EC2 16, 25installing SmartCloud

Provisioning 11installing VMware 20Red Hat Enterprise Linux 5

installing 5agents on Linux 30agents on Windows 33Amazon EC2 16failure 66monitoring agents 29monitoring infrastructure 11on other systems 25SmartCloud APM for Mobile

Applications 47SmartCloud Provisioning 11VMware 20

ips.txt 27

Kkorn shell 5

Llanguage

See localelanguage licenses 72Liberty server 5

libstdc++.so.5 5lightweight infrastructure

See monitoring infrastructureLinux

Red Hat Enterprise 5locale 72

troubleshooting 71log files

collecting agent 76collecting infrastructure node 73

logon 49

Mmanaging applications 56memory 8MongoDB agent

configuring 35monitoring agent

default user 62monitoring agents 51

See also data sourcescommands for 52configuring 35

MongoDB agent 35MySQL agent 37PHP agent 38PostgreSQL agent 40Python agent 41Response Time Monitoring

Agent 43Ruby agent 44WebSphere Applications agent 46

installing 29installing on Linux 30installing on Windows 33log files 76port configuration 54thresholds not applied 71uninstalling 48upgrading 28, 47user ID for accessing 55

monitoring infrastructureinstalling 11uninstalling 29

monitoring infrastructure nodeSee infrastructure nodeconfiguring other discovery 27

MySQL agentconfiguring 37

Nnew in this release 1notices 83

Oother discovery

configuring 27


overview 3

Ppassword

changing apmadmin 55PD collector tool 76PHP agent

configuring 38platform

operating system 5polling interval 58port

25 59443 61465 5951920 5853661 585678 14, 6180 22, 619998 59infrastructure node 22

port configuration 54, 58ports 8PostgreSQL agent

configuring 40prerequisite scanner 8prerequisites 5privacy policy 79, 86Python agent

configuring 41

Rrefresh interval 58Response Time Monitoring Agent

configuring 43Ruby agent

configuring 44

SSDP adapter 60security

Java keystore 62truststore 62

SmartCloud APM for MobileApplications

installing 47SmartCloud Provisioning

configuring 14installing 11SDP adapter 61

SMTP 59Software Product Compatibility

Reports 5SSL 59start and stop commands

apmui 52fabricNode 52scr 52server1 52

starting Application Insight 49

TTivoli monitoring agents

See data sourcestrace log 59trademarks 85, 86troubleshooting 65

Chrome 67dashboards 67infrastructure node

log files 73installation, agent 65PD collector tool 76thresholds not applied to agents 71

Uuninstalling 48

monitoring infrastructure 29upgrade failure 66upgrading

monitoring agents 28, 47user ID 55, 62user interface

start and stop 52

VVMware

certificate validation 24configuring 22installing 20SDP adapter 61

WWebSphere Applications agent

configuring 46what's new in this release 1Windows

dependencies 5


��

Printed in USA

SC27-5618-03