laboratorio de itcam

1

Introduction

This lab session is a subset of the official IBM Tivoli education course ITCAM for Transactions 7.3 Implementation and Administration. If you are interested in participating in the full course, visit the Tivoli Education website at:

http://www-306.ibm.com/software/tivoli/education/

This lab session provides hands-on use of monitoring transactions in a typical multitier application infrastructure using IBM Tivoli Composite Application Manager (ITCAM) for Transactions. ITCAM helps manage application availability, resource, and transaction performance of the composite applications.

This lab session uses commonly used Service Oriented Architecture (SOA) middleware, such as the following items:

WebSphere Application Server (a Java EE compliant application server)

IBM HTTP Server

WebSphere MQ for messaging layer

WebSphere Message Broker for enterprise service bus

ITCAM for Transactions can monitor and track user transaction performance through multiple tiers. These tiers might include a web server, an application server, and a database. It might also include enterprise information systems (EIS), such as CICS, IMS, and a messaging environment, such as WebSphere MQ.

Automated monitoring of critical transactions using robotic transaction playback is also part of the ITCAM for Transactions offering. ITCAM for Transactions can also monitor standard Internet server components that are commonly found in any multitiered application environment. Such components include LDAP server, mail server, and HTTP server.

ITCAM for Transactions also offers custom application instrumentation, using the Application Response Measurement (ARM) standard and the ITCAM Transaction Tracking API (TTAPI). TTAPI can track transactions within a single application and within applications across multiple domains. Custom instrumentation with ARM or TTAPI can also cover domains not supported by the product.

2 IBM Tivoli Composite Application Manager for Transactions Copyright IBM Corp. 2012

Lab overview

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Lab overview

This lab guide is organized as follows:

___ 1. Setting up the VMware images

___ 2. Robotic Response Time

___ 3. Tracking transactions

___ 4. Application Management Console

Lab entry skills

To successfully complete the exercises, you must know how to navigate workspaces and use terminology such as navigator, navigator item, query, and link. Complete Lab D01, IBM Tivoli Monitoring: Introduction to Using Tivoli Enterprise Portal, before you attempt this lab session.

Lab exit skills

When you finish this lab session, you can perform the following tasks:

List the challenges and complexities of a multitier application infrastructure.

Identify the components required from ITCAM to monitor a transaction that crosses multiple domains. Such examples include web server, Java EE (WebSphere) application server, messaging layer (WebSphere MQ), and WebSphere Message Broker.

Use ITCAM for Transactions product capabilities to monitor real user transactions, robotic transactions, and application availability.

Copyright IBM Corp. 2012 Introduction to ITCAM for Transactions 3

Introduction to ITCAM for Transactions



A typical workflow for managing application performance involves detecting if there is a problem, diagnosing the problem, and then resolving the problem. The following figure depicts a workflow for managing composite applications.

You can use ITCAM for Transactions to help detect and isolate transaction performance problems. The solution is built on IBM Tivoli Monitoring management infrastructure, which provides a single common user interface called Tivoli Enterprise Portal. IBM Tivoli Monitoring also provides other common management services, such as automation threshold monitoring and take actions, data warehousing of monitored data, and reporting. Custom monitoring solutions can also be built to extend monitoring capabilities using the agent builder technology.

ITCAM transactions monitoring concepts

ITCAM for Transactions monitors transactions: the requests and responses between clients and servers, between applications and within applications. And while ITCAM for Transactions




monitors individual instances of transactions, the instance data is summarized into five major entities:

Transaction: A request to accomplish a particular action or result

Client: Transaction performance and availability data grouped by requesting client host name, IP address or range

Server: Transaction performance and availability data grouped by receiving server

Application: Transaction performance and availability data grouped by application definition

Component: Transaction performance and availability data grouped by a component definition

Transactions are monitored directly. Client servers, components, and applications are monitored by inference from transaction monitoring.


Exercise 1: Setting up the VMware images



In this exercise, you log in to the lab machine and start the appropriate images for this lab exercise. Perform the following steps:

___ 1. Start the following VMware images below in the following order.

APMSmartPoC-Server-VM1

APMSmartPoC-Agentless-VM2

APMSmartPoC-AppDemo-VM4

Start the Demo Agents

___ 2. Log in to the Server host with the user root and password smartway.

___ 3. Start the components by running the following command:

/root/smartpoc.sh start

Tip: To open a command prompt, right-click the desktop, and click Open Terminal.

The following screen capture are displayed:

___ 4. Complete the step above for the other VMware images. Username and password are root/smartway

C

Confirming the Server host environment___ 5. Start the Manage Tivoli Enterprise Monitoring Services application by completing the

following task:

From a command prompt, run the following command:

/opt/itm/bin/itmcmd manage &




The Manage Tivoli Enterprise Monitoring Services application window opens.

___ 6. Ensure that your Manage Tivoli Enterprise Monitoring Services display resembles the following screen capture:

___ 7. If running services shown in Step 6 are not running, start them now. Right-click each stopped component and click Start.




___ 8. Start the Tivoli Enterprise Portal client by completing the following step:

Click 04 ITM Shortcuts > 02 Start TEP Desktop Client for using the shortcut launcher. Close the launcher window after the Tivoli Enterprise Portal login window opens.

___ 9. Log in to the Tivoli Enterprise Portal as user sysadmin with no password.

Confirming the AppDemo host environment

___ 10. Start the Manage Tivoli Enterprise Monitoring Services application by completing the following step:

From a command prompt, run the following command:

/opt/IBM/ITM/bin/itmcmd manage &The Manage Tivoli Enterprise Monitoring Services application window opens.




___ 11. Ensure that your Manage Tivoli Enterprise Monitoring Services display resembles the following screen capture:

___ 12. If running services shown in Step 11 are not running, start them now. Right-click each stopped component and click Start.

Confirming the Agentless host environment

___ 13. Configure the IP adress of the agents by running the following command. /root/smartpoc.sh config IPofVM1 IPofVM1. See picture below.


Exercise 2: Robotic Response Time



Robotic Response Time provides active monitoring of customer business transactions. These business transactions represent a complex set of steps typically that an end user performs for achieving a business objective. Such examples include logging into an online banking application, checking an account balance, and transferring funds. This set of steps can be recorded and played back using this agent to verify availability and performance. It is installed separately on various desktop and server systems in your enterprise and on the Internet.

In this lab session, scripts have been created that use various transactions in the Trade application. Those scripts are periodically played back and monitored by several Robotic Response Time agents. The playback and monitoring ensure that the applications and transactions are available and performing as expected.

In this exercise, you see how the robotic response time infrastructure is configured and also the monitoring data that is being created.

Robotic response time can be controlled in two ways. When you configure the agent, you can set parameters general to all scripts that play on the agent. Within the Application Management Configuration Editor utility, you can create profiles that configure each script independently.

Configuring and starting a Robotic Response Time agent

This section introduces the Robotic Response Time agent and its configuration parameters. Perform the following steps:

___ 1. On the Server-VM1 host, start the Manage Tivoli Enterprise Monitoring Services application by completing the following task:

Run the following command from a command prompt:/opt/itm/bin/itmcmd manage &

Manage Tivoli Enterprise Monitoring Services launches.




___ 2. Review the configuration parameters of the Robotic Response Time agent.

___ a. Right-click the ITCAM for Robotic Response Time agent and select Reconfigure.

A configuration panel for connecting to a Tivoli Enterprise Monitoring Server window opens.

___ b. Click OK to continue.

The agent configuration window opens.

From this window, you can customize the way the Robotic Response Time agent plays and monitors scripts. Use the Robotic Monitoring Configuration and Data Analysis Configuration tabs to set parameters that apply to all types of scripts. The remaining tabs set parameters that are specific to the type of script identified by the tab name.

___ c. Click each tab and review any parameters that interest you. Hover your cursor over a parameter to view a definition.

___ d. When you are finished reviewing parameters, click Cancel to cancel the configuration and click Yes to confirm.

You are returned to the Manage Tivoli Enterprise Monitoring Services main page.

___ 3. Ensure that the ITCAM for Robotic Response Time agents are started.




Viewing uploaded scripts that are ready for deployment

In this section, you see the scripts that have been created and uploaded into this lab setup.

___ 4. In the Tivoli Enterprise Portal on the Server-VM1 host, find and select the Linux Systems > sysitmsles>Application Management Console > Robotic Scripts node.

This node and workspace is dedicated to uploading and managing uploaded robotic scripts. The view on the right is the multifile upload utility that can be used to upload robotic scripts. The Robotic Scripts view below the Navigator lists uploaded scripts and RPT runtime engines. Several scripts have been uploaded and are ready for deployment, playback, and monitoring.

Confirming the Robotic Response Time configuration

In this section, you use the Application Management Configuration Editor for creating profiles that control the scripts that are deployed to Robotic Response Time agents. You also control their playback. Perform the following steps:




___ 5. Click the AMCE icon to open the Application Management Configuration Editor.

___ 6. Select Profiles from the Navigator menu.

___ 7. Expand Robotic Response Time.

The profiles control robotic response time. The Agentless_Exer profiles is deployed and active.




___ 8. Click the Robotic Response Time profile and click the Transactions tab.

This profile controls one robotic script. From this view, you can add and remove scripts to the profile and configure their playback.

___ 9. Click the SimpleTrade script and the Properties tab below.

The Properties tab displays parameters that control the playback of this specific script.

___ 10. Click the Distribution tab.




You can deploy these scripts to Robotic Response Time agents that you choose for playback and monitoring.

___ 11. Click Cancel to close the Application Management Configuration Editor without saving changes.

Analyzing robotic monitor data

In this section, you navigate the robotic monitoring workspaces. Perform the following steps:

___ 1. Find and select the Robotic Response Time agent under sysitmsles.

This workspace provides an overview of the status of robotic monitoring on this agent. The status includes the following items:

Playback status of each script on this agent (Playback Status)

Performance and availability of applications monitored by the scripts on this agent (Application Current Status)

Situation events that have triggered on this agent (Situation Event Console)

All of the scripts have now played back successfully.




___ 2. Expand Robotic Response Time and click the Playback Status node in the Navigator.

This workspace gives greater detail on the playback status, including the following information:

A playback over time of all scripts on this agent (Overall Agent Script Execution Trend)

The same playback status view in the Robotic Response Time node workspace

A list of any verification point failures (Robotic Script Verification Point Failures) for all scripts on this agent

___ 3. Click the Applications node in the Navigator.

This workspace shows current availability and performance data for each application being monitored on this agent.




By default, each script is defined as its own application. However, multiple scripts can be combined into a single application definition. This definition would make each application shown here a summary of the data from all scripts assigned to that application.

Clicking the link icon next to an application takes you to workspaces with details on just that application.

___ 4. Click Transactions in the Navigator.

This workspace is very similar to the Applications node workspace. But, it shows the performance and availability of each script running on this agent, not the aggregated application definitions.

___ 5. Click the link icon next to SimpleTradee in the Transaction Current Status Details view.




The Transaction Detail workspace opens for the Trade script.

This workspace provides detailed performance and availability information about this one script.

___ 6. Click the link icon next to SimpleTrade in the Selected Transactions view.


Exercise 3: Tracking transactions


The Transaction Status workspace opens.

This workspace give availability and verification point data on the script and includes the performance and availability of the subtransactions within the script.

This step concludes your introduction to robotic response time monitoring.


In this exercise, you explore the transaction-tracking workspaces in Tivoli Enterprise Portal to view the transaction requests created by the sample application. You focus on the following agents for this lab. Some agents are also known by their 2-letter product codes in the IBM Tivoli Monitoring world as shown in parentheses.

Transactions Collector Agent (TO): One or more instances is required, depending on the number of monitoring environments. The main purpose of the Transaction Collector is providing distributed storage for all instance data that is collected from multiple data sources. On this VM, there is one instance of this agent.

Transactions Reporter Agent (TU): Only one instance in the management infrastructure is required. The Transaction Reporter contains a number of complex algorithms to aggregate tracking data and create transaction topologies or transaction instance graphs. A single Transaction Reporter can receive information from one or more Transaction




Collectors through the Tivoli Enterprise Monitoring Server. The same Transaction Reporter can display that information in the Tivoli Enterprise Portal.

MQ Tracking (TH): This agent is required for collecting WebSphere MQ tracking data. There is one instance installed on this VM.

ITCAM for Application Diagnostics 7.1 or ITCAM for WebSphere/J2EE 6.1 Managing Server and Data Collector: This agent is required for cross-domain tracking of the transactions originating from WebSphere.

Perform the following steps:

___ 1. Launch the Tivoli Enterprise Portal, if it is not already running.

In a few minutes, a Navigator update-pending notification message might arrive for your new data collector application.

___ 2. If prompted at any time during this exercise, click either of the locations shown in the figure to accept Navigator updates:

Waiting for an update is not necessary. Proceed with the exercise and accept the updates when they occur.




___ 3. Select sysitmsles>Transaction Collector.

The Transaction Collector in the Tivoli Enterprise Portal is confirmation that the collector is running and connected to the Tivoli Enterprise Monitoring Server.

___ 4. In the Aggregation Periods view, confirm the Number of records is greater than 0 in at least one row.

The Aggregation Periods view shows the start and end times of each aggregation period and the number of records that are collected during that interval. This number of records indicates that the Transaction Collector is receiving transaction data from one or more data collectors.

___ 5. If you have only one line of data, wait several minutes while pressing F5 periodically to refresh the view until a second row appears.

___ 6. In the Tivoli Enterprise Portal, navigate to the sysitmsles> Transaction Reporter node.




The Transaction Reporter node contains attribute group nodes for Applications, Components, Servers, and Transactions.

Note: The data gathering by the Transaction Reporter might take several minutes. If all your components do not currently show, wait a few minutes and refresh the view (F5) until they show.

The default workspace for Transaction Reporter displays a combined server and component topology view and a deviations view that shows all the interactions being monitored. This workspace is the only workspace that contains a combination of agentless and agent-based transaction tracking data.




___ 7. Expand the Transaction Reporter node and select the Applications node.

___ 8. Notice the following items:

The applications that are being tracked and the detailed data on each of them are listed in the lower-left area of the Applications view.

The views on the right show the poorest performing applications in three categories: lowest availability, largest time deviation, and largest transaction rate deviation.

This workspace layout repeats in the default workspaces for the other Transaction Report nodes, but shows data that is appropriate to that node, such as Components, Servers and Transactions.

___ 9. Maximize the Applications view by clicking the Maximize button.




___ 10. Scroll to the right of the table, and browse the gathered data.

The time stamp of the data is earlier than the most current time stamp of the Transaction Collector. This time stamp indicates that there is a delay between the data being collected at the Collector and it then being sent to the Reporter.

The table shows the basic performance data, such as average response time, average availability, transaction counts, and transaction rates. It also shows the baselines for each of these data points and how much the current values deviate from the baseline. Monitoring deviations from the baseline is a crucial part of transaction tracking.

A key factor of monitoring is setting conditions that identify when a problem occurred. When you monitor thousands or tens of thousands of transactions, determining what is the norm and what is outside the norm can be a difficult and time consuming task.

In transaction tracking, a baseline is automatically calculated for each monitored entity (application, component, server, transaction, interaction, and client); providing a norm for comparing the current data against. Current data is compared to the appropriate baseline every aggregation period, and the percent deviation from the baseline is calculated. Deviations greater than the baseline by specific amounts are automatically color-coded, for example, yellow for > 50%, orange for > 100%, and red for > than 200%. Additionally, deviations greater than set amounts also trigger event notifications.




Applications are related for the monitored transactions.

___ 11. In the Navigator, right-click Applications, and place your mouse on Workspaces, but do not select a workspace.

Four workspaces are associated with the Applications node.

___ 12. Click Application Topology.

Notice the following items:

Each node is an application with the application name that is displayed next to it.

The lines indicate interactions with another application, and the number indicates the average time for those interactions.




___ 13. Roll over a node.

A panel opens with information about the node.

___ 14. In the Navigator window, click the Transaction Reporter > Components.




___ 15. Right-click Component > Workspace, and click Component topology.

The component topology view shows the correlation between the components that are involved in the transaction.

You can hover the mouse over the discovered nodes to obtain more details about average time that is spent in that component during the most recent sampling interval.




___ 16. Navigate to sysitmsles > Transaction Reporter > Transactions.

The Transactions view shows a list of all the transactions that are currently being tracked. The views on the right show the poorest performing transactions in three categories.

___ 17. Scroll down in the Transactions view and see if you can distinguish HTTP, WebSphere, and DB2 transactions.

___ 18. Scroll to the right of the Transactions view and view the aggregated monitoring data on each transaction.




___ 19. Scroll right, displaying the Enclosing Application and Enclosing Component columns, and scroll down. These values change as you reach the MQ, DB2, WebSphere, and HTTP transactions.

___ 20. In the Transactions view, right-click the link icon ( ) that is beside any transaction, but do not select a workspace.

Selecting one of these workspaces takes you to a new workspace that applies to only this transaction.




___ 21. In the Navigator, right-click Transactions, and place your mouse on Workspaces, but do not select a workspace.

Selecting one of these workspaces takes you to a new workspace that applies to all the transactions that are being tracked.

___ 22. Click Transaction Topology.

___ 23. Enlarge the view by clicking the Maximize icon at the upper-right corner of the view.




A topology similar to this screen capture is displayed.

___ 24. Use the slider control that is under the view title to adjust the scale of the topology view until you can read the text.




Notice the following items:

Each node is a transaction.

The name for each node is displayed.

The lines indicate an interaction with another transaction.

Each interaction line contains a time in milliseconds, which is the average time for that interaction.

Because of the starting point, Transactions Navigator item, this topology view displays the topologies of all transactions that are being tracked even if they do not interact.

The topology shows HTTP transactions interacting with WebSphere transactions and WebSphere transactions interacting with other WebSphere transactions.




___ 25. Hover your mouse over a node.

A panel opens with information about the node.


Exercise 4: Application Management Console



The Application Management Console agent performs as follows:

Provides a single logical application view of availability, performance, and load for the ITCAM monitoring agents.

Aggregates real-time agent status and trends into a single, consistent set of views and workspaces.

Provides diagnoses across servers and monitors.

Provides deep-dive launch or drill-down in context of each ITCAM agent workspace for further diagnosis.

Stores aggregated application trend data in the Tivoli Data Warehouse for analysis.




In this exercise, you explore the data gathered by the Application Management Console. Perform the following steps:

___ 1. In the Navigator, click the Application Management Console node under itm.ibm.com.

The Application Management Console node workspace provides an overview of all ITCAM for Transactions monitoring in your enterprise. For example, the Plants by WebSphere data shown here is a summary of the data from the robotic response time scripts that are running on both the ITM and RPT hosts.

___ 2. Expand and select Application Management Console > Applications > SimpleTrade.

This workspace gives more detail about the performance and availability of the SimpleTrade application across the entire enterprise. In this instance, the details provide summarized data about the ST scripts that are running on the VM1. In this workspace, you can also see other types of monitoring, such as Web Response Time and Transaction Tracking.




You have completed the lab exercise.

Important: Let a proctor know that you are finished, so that the system can be reset for the next attendee. You are welcome to do other labs at this time.

Lab overviewLab entry skillsLab exit skills

Introduction to ITCAM for TransactionsITCAM transactions monitoring concepts

Exercise 1: Setting up the VMware imagesStart the Demo AgentsConfirming the AppDemo host environmentConfirming the Agentless host environment

Exercise 2: Robotic Response TimeConfiguring and starting a Robotic Response Time agentViewing uploaded scripts that are ready for deploymentConfirming the Robotic Response Time configurationAnalyzing robotic monitor data


laboratorio de itcam

Documents