Application Management Console workspaces

These workspaces provide an accurate snapshot of ITCAM for Transactions monitoring in near real time.

Use the Application Management Console to see status summary and trend analysis across managed resources and to perform problem determination. This interface provides real-time aggregated and consolidated application and transaction availability and response time status of all applications monitored by Response Time, Internet Service Monitoring, and Transaction Tracking monitoring agents. It offers the following features and functions:

Collects the data in real time at a configurable, constant interval instead of relying on the Tivoli Data Warehouse.
Provides accurate status directly from the monitoring agent situations.
Offers the ability to customize status definitions based on situations.

The Application Management Console collects data directly from other agents in real time. The Application Management Console currently collects data for the following ITCAM for Transactions agents:

Transaction Reporter (KTO)
Robotic Response Time (KT6)
Web Response Time (KT5)
Internet Service Monitoring (KIS)

Data from the first four agents is aggregated together by application name and is displayed in the Tivoli Enterprise Portal in the Application Management Console > Applications group.

Data from Internet Service Monitoring is sorted according to the defined profile names and is displayed in the Tivoli Enterprise Portal in the Application Management Console > Servers group.

By default, all agents are included in the collection settings. Data from particular agents can be included or excluded using the ITCAM Console. In the Manage Tivoli Enterprise Monitoring Services, right-click ITCAM Console and select Configure. Edit the settings on the Data Collection Configuration tab as required.

The Application Management Console also provides several workspaces with trend graphs that show multiple lines for comparing data across multiple resources. These graphs display either the response or availability over time in the context of real user usage patterns. For example, when comparing client response time across all clients for a particular application, you might see several disconnects in some of the lines in the graphs. This situation indicates that a particular client was not accessing or using that particular application at that time.

Figure 1 shows the path for Application Management Console workspaces:

Figure 1. Application Management Console workspaces

Image showing interaction of Application Management Console workspaces. These links are described in each workspace.

Internet Service Monitoring workspaces

The Application Management Console displays data collected from Internet Service Monitoring version 7.2 (and later) monitoring agents. You might have multiple Internet Service Monitoring agents in your environment, each collecting similar data. In this case you can display all of this data in an aggregated view in Application Management Console workspaces. Using this method gives you a summary overview of the status and trends of the monitored applications across all of your Internet Service Monitoring agents. From this overview, you can display more detailed information for a specific Internet Service Monitoring agent. From there, you can link in context to the associated Internet Service Monitoring workspaces. Using these workspaces helps you resolve problems reported by specific Internet Service Monitoring agents.

Figure 2. Internet Service Monitoring in AMC workspaces

Image showing interaction of the Internet Services Monitoring in Application Management Console workspaces. These links are described in each workspace.

The data that is collected by Internet Service Monitoring agents is different from other Response Time and Transaction Tracking data, and is stored and displayed separately. As you work with Internet Service Monitoring monitoring data in Application Management Console workspaces, keep in mind the following considerations:

Some of the terminology referring to Internet Service Monitoring data is different from other data. For example, Internet Service Monitoring uses the term marginal in a similar context to the Response Time term slow. This state is an interim state between good and failed.
Time-related data is usually expressed in Application Management Console workspaces in seconds. If Internet Service Monitoring data is displayed in milliseconds, it is also displayed in milliseconds in the Application Management Console. This display is consistent with Internet Service Monitoring workspaces and provides continuity when launching in context to those workspaces.
If there are errors associated with collecting data from Internet Service Monitoring agents, existing Application Management Console file transfer error messages are displayed.
The Application Management Console relies on the KT1 file transfer protocol to be installed on the local or remote Tivoli Enterprise Monitoring Server as needed.
Dynamic subnodes under the Servers node in the Physical Navigator view are defined by the profile names that you define. Similar to the Applications subnode, these Server subnodes become inactive after the time window (8 hours by default) has elapsed. If a profile is stopped or deleted, it is not deleted from the Application Management Console for 8 hours.

Tip: Use the Start and End Time columns to review Response Time historical starting and ending time data. Response Time data appears in these columns rather than the Recording Time column. Recording Time displays data when you change your time span and use the Recording Time option.