There can only be one active Hub TEMS in each environment.

There can be more than one active Hub TEMS in each environment.

The number of needed Hub TEMS is determined by an updated file during installation.

The number of needed Hub TEMS is dependent on the number of active links to agents.

Oracle is now a supported database for TEPS

Authorization policy enforcement is enabled by default.

IBM Tivoli Monitoring V6.3 strongly recommends the upgrade to Java 6.

The dashboard data provider is optionally enabled during the TEPS configuration.

Only IBM tools

Only third-party tools

Only IBM and partner tools

IBM, partner, and third-party tools

Support for self-describing agents.

Support of monitoring file systems of the NES.

New TM capability to perform prerequisite checking for agents before performing an installation.

A variety ofmetrics have been ported from the AIX Premium agent to the TM agent for UNIX OS.

IBM Java 6

IBM Java 7

Oracle Java 6

Oracle Java 7

Bi-directional using the Event Console Agent

Bi-directional using the Event Integration Facility

Uni-directional using the Event Integration Facility

Uni-directional using the IBM Tivoli Monitoring Situation Update Forwarder

Tivoli Event Reporter

Tivoli Enterprise Portal

Tivoli Netcool EIF Probe

IBM Tivoli Netcool/OMNi bus

The run time and completion of the SPA

The connection to the Tivoli Enterprise Portal Server

The size of the tables being summarized and pruned

Availability of space on the disk where the Tivoli Data Warehouse is located

It provides dashboard visualization and reporting services for the Tivoli Data Warehouse.

It receives data collected by monitoring agents and moves it to the Tivoli Data Warehouse database.

It analyzes and enriches the data that is collected by its monitoring agents and provides reports about the performance and capacity of systems.

It provides the ability to customize the length of time to save data and how often to aggregate granular data in the Tivoli Data Warehouse database.

Disable the Situation Event Console and clear alerts

Move the Situation Event Console to a separate server

Use IBM Tivoli Netcool/OMNI bus and send alerts to that console if entitled

The Situation Event Console is multi-threaded so add more processes to the process

audit and policy files

catalog and attribute files

help and presentation files

application configuration files

To get more accurate data from the Tivoli Data Warehouse

So that Summarization and Pruning can complete in its window

To ensure that Tivoli Monitoring agent data is written to the Tivoli Data Warehouse

To allow multiple users to query the Tivoli Data Warehouse from the Tivoli Enterprise Portal Server

Query, User, and Situation

Query, User, and Managed Systems

Query, User, and Workspace Definition

User, Situation, and Workspace Definition

They can only be used if referenced in a policy.

They only run at the Hub Tivoli Enterprise Monitoring Server.

They only run at Remote Tivoli Enterprise Monitoring Servers.

They run at the Hub Tivoli Enterprise Monitoring Server and Remote Tivoli Enterprise Monitoring Server.

As Attribute Events

As Attribute Groups

As Attribute Policies

As Attribute Containers

Click the Query Editor Icon on the Tivoli Enterprise Portal (TEP) tool bar.

Click the Modify Query icon on the TEP tool bar.

Click Administration Mode and then select the Query Editor from the list.

Click Administration Mode, click List, and then select Query Editor from the list.

Run tacmd restore workspace

File >Restore Original Workspace

Restart the Tivoli Enterprise Portal client

It cannot be restored to the original workspace.

No data can be excluded from the export.

Only rows can be excluded from the export.

Only columns can be excluded from the export.

Rows and columns can be excluded from the export.

Attribute Groups

Tivoli Data Warehouse reports

Universal Agent Data Providers

IBM Tivoli Netcool/OMNI bus rules

View only

Workspace only

View and Workspace only

View, Workspace, and Embedded Situations

An historical data collection feature that allows data to be filtered.

A feature used by the Agentless technology that allows better control of agent deployment.

A database data organization feature that can reduce feedback time for Summarization and Pruning agent performance.

A database data organization feature that can significantly improve pruning and query performance in large Tivoli Data Warehouse databases.

Bar chart

Plot chart

Topology view

Linear gauge chart

Pie Chart

Plot Chart

Table View

Graphic View

Default

Unused

Ali Groups

Managed System

A screen in the Tivoli Enterprise Portal (TEP) to display data.

A policy in the TEP for displaying logical views.

A screen that displays only temporary historical data.

A policy in the TEP for displaying information for physical views.

Have Workspace Author Mode and click the Save icon

Click the Create New Workspace icon, create the Workspace, and then click the Save icon

Have Workspace Administration, click the Properties icon, and then click the Apply Button

Click the Save icon and then contact an administrator and ask them to publish the new workspace

The IBM Tivoli Monitoring (ITM) license key is invalid.

The ITM encryption key is invalid.

The Tivoli Data Warehouse agent is not running.

No data was stored in the Tivoli Data Warehouse.

Use only one query per workspace.

Use an associated situation with the query.

Use a filter to filter the data retrieved from the query.

Use a policy to limit the data returned from the query.

assigns a new user group in the Tivoli Enterprise Portal Server

assigns a new user in the Dashboard Application Services Hub

assigns permission to a role in Dashboard Application Services Hub

assigns users or groups to a role in the Tivoli Enterprise Portal Server

Password is validated at the TEMS.

Set password never expires on the TEMS.

LDAP user password is verified as valid at the Tivoli Enterprise Portal Server (TEPS).

No password is requested when a user logs on to the TEPS.

Only the command on the selected Managed System can be run from the Navigator tree.

Only commands from the pre-defined Take Action can be selected and they cannot be edited.

The Take Action command will run with the Administrators Authority (example: as root on UNIX and Linux systems).

The Take Action command will run as the User ID of the User ID used to start the agent (example: mqm started the MQ Monitor selected in the Navigator tree so the command will execute as if User ID mqm submitted the command).

Columns can only be removed.

Only columns that are displayed can be filtered.

The query must be changed to filter on columns.

Columns can be added or removed, and any column can be filtered.

Pruning

Thresholds

Post-filtering

Summarizing

Workspace Author Mode

Launch Administration Mode

Workspace Administration Mode

Launch Application Activation Mode

Historical Modify permission is needed.

The Time Span is present in the view’s toolbar.

The History Collection Configuration button is enabled.

The Monitored Baseline is present in the view’s toolbar.

tacmd start agent

tacmd agent start

tacmd agent start launch

tacmd agent launch

Simple

Relative

Absolute

Dynamic

It is a discovered view.

It is the default navigator view.

It initially shows one navigator item.

It shows the physical hierarchy of an environment by default.

Right-click and select the desired workspace

Double-click and select the desired workspace

Press Ctrl + L so that the list of available workspaces appears

Press Ctrl + W so that the list of available workspaces appears

10

25

50

100

Refresh the Navigator

Check Discrepancies

Apply Pending Updates

Application Support Event

Action> Modify

Custom Navigator Views > Modify

Workspace Administration > Workspace Author Mode

Workspace Administration > Workspace Administration Mode

Use a time event situation and in that situation select the Distribution tab and assign the specific situations that need to be active. Then use the Until tab to define the ending condition being the process xyz.

Use a time event situation and have it trigger a policy and in the policy, select the Start/Stop a Situation to define all the situations need to be active. Then select the Until feature and define the event for process xyz completion. Then select Start/Stop a Situation to define all the situations to stop.

Define two situations. One is a time event situation and the other detects when process xyz is active. Use a policy that triggers when the time event situation becomes true, and use the Start/Stop a Situation to define all the situations that need to be active. Use the Evaluate a Situation Now to check if process xyz is active, and if that situation is false then use the Start/Stop a Situation to stop all of the situations that were activated in this policy.

Define three situations. The first is a time event situation, thesecond detects when process xyz is active and writes a Universal Message, and the third that checks for the Universal Message written by the other situation. Use a policy that triggers when the time event situation becomes true, and use the Start/Stop a situation to define all the situations that need to be active. Use a second policy that triggers when the Universal Message Situation becomes true, and then use Evaluate a Situation

All situations can use Display Item.

Only certain attributes can be displayed.

Any attributes can be designated as display items.

The only purpose of the Display Item is to allow the addition of custom text to an event.

all users of the ITM environment

all users with Expert Advice view permission

all users created from the SYSADMIN role only

users related to the Operation role in the ITM environment

It is configured to run all the time.

It should be linked to a Navigator item.

It is configured to run at restricted times.

It is automatically linked to a Navigator item.

Only one value

Maximum of three values

Unlimited number of values

Limited by the size of the situation

Through the Situation Event Console

From the Tivoli Enterprise Portal client

From the Manage Tivoli Enterprise Monitoring Services tool

Use start WorkflowEditor.sh on UNIX/Linux and start WorkflowEditor.bat on Windows

Take Action in a situation can write to the Universal Message Log, while Take Action in a policy can onlyissue a command.

Take Action in a situation uses the system administrator ID, and within a policy the User ID that created the policy will be used when executing the Take Action.

Take Action in a situation will only issue the command at the Managed System (agent) where the situation became true, while Take Action in a policy can be executed at any managed system.

Take Action in a situation can be issued at the Managed System Tivoli Enterprise Monitoring Server, while in a policy the Take Action canbe issued at the Hub Tivoli Enterprise Monitoring Server.

The system does this automatically.

In the Situation Editor, select the Association tab.

Right-click on the Navigator item and select Situations.

Open the situation, right-click and select Navigator Item.

The situation is deleted automatically.

The situation will no longer be distributed.

The situation still monitors the assigned list system.

A managed system group that is assigned to a situation cannot be deleted.

Acknowledge Permission for Events

Acknowledge Permission for Agents

Acknowledge Permission for Queries

Acknowledge Permission for Workspaces

They allow users to set up performance enhancing attributes.

They are used to compare current data against situation or historical data.

They establish a threshold to perform statistics against for some situations.

They allow users to define different levels of performance based on operating system.

Click the Advance button in the until tab

Click the Advance button in the Formula tab

Click the Add Conditions button in the Formula tab

Click the until tab to define the persistence attribute

When a expired event is started.

When a stopped event is closed.

When an invalid login attempt is detected.

When the event is based on observations made at specific intervals.

From the Self-Monitoring Topology workspace off the Enterprise navigator item, look for Offline agents.

From the Managed System Status workspace off the Enterprise navigator item, look for Offline agents.

Expand the Navigator tree and look for managed systems that are grayed outindicating they are offline.

From the Enterprise Status workspace off the Enterprise navigator item, look in the Message Log workspace view for MS_Offline messages.

The configuration file for the failing agent should have KDEB_NIC= followed by the IP addresses of the NIC cards that should not be used.

The configuration file for the failing agent should have KDEB_INTEREACELIST=! followed by the IP address of the NIC card that should be used.

The configuration file for the failingagent should have KDEB_INTERFACELIST=! followed by the IP addresses of the NIC cards that should not be used.

Issue a telnet command to the TEMS host using port 1918 if IP.PIPE is being used or port 3660 if IP.SPIPE is being used. If it does not succeed then open the port in the firewall.

It removes old IBM Tivoli Monitoring (ITM) log files from the logs directory.

It analyzes ITM log highlighting error conditions.

It converts the timestamps in ITM logs to local time.

It creates a tar (UNIX) or zip (Windows) file of the ITM logs in the logs directory.

Tivoli Enterprise Portal

Tivoli Enterprise Portal Server

Tivoli Enterprise Monitoring Server

Tivoli Enterprise Management Agent

It manages the connection status of the Tivoli Enterprise Monitoring Server.

It collects data from monitored or managed systems and distributes this information to a monitoring server.

It collects and controls points for alerts received from the agents and collectstheir performance and availability data.

It retrieves data from the hub monitoring server in response to user actions at the portal client and sends the data back to the portal client for presentation.

SQL files

Audit files

Catalog files

Presentation files

If summarization is specified, it automatically turns on pruning.

Pruning can only specify the number of days, months, or years.

Pruning can be specified as the number of days, weeks, months, or years.

Summarization only allows summarization at the hourly, daily, and weekly time frames.

Tivoli Dashboard Hub

Dashboard Tivoli Portal Hub

Tivoli Integrated Portal Dashboard

Dashboard Application Services Hub

Secure Shell (SSH)

Simple Object Access Protocol (SOAP)

Web-Based Enterprise Management (WBEM)

Simple Network Management Protocol (SNMP)

Disable workspace updates using the Administrator Console

Create filters for various users to restrict access to some areas

Modify the cache settings in the Administrator Console and increase memory

Remove the situation event console from workspaces where it is not really required

Warehouse Proxy agent

Tivoli Enterprise Portal Server

Tivoli Enterprise Monitoring Server

Summarization and Pruning agent

The dashboard analytics

The dashboard data provider

The self-describing agent feature

The dashboard authorization policies

Log on to the Tivoli Enterprise Portal Server (TEPS) and check the Common Event Console.

Log on to the TEPS and look at the WPA workspaces.

Log in to the system where the WPA is installed and check that the WPAprocess is running.

Use a database client to access the Tivoli Data Warehouse database directly and verify metric data is being written to the database.

Bulk_Failed, Bulk_Complete

Rollout_Failed, Rollout_Retrying

Deploy_Failed, Deploy_Retrying

Install_Failed, Install_Succeeded

A view within a workspace

The Enterprise level of the Navigator tree

The new Export Agent’s level of the Navigator tree

In the Query Editor for the Tivoli Data Warehouse

It can be used by many users.

It can only be used by the user who created it.

It can only be used by users in the same group as the query’s owner.

It can be used by any user who is permitted to either view or make changes to queries.

All new events received are acknowledged.

The situation event console is not refreshed.

A link with a child workspace is automatically created.

Retrieved data remains static until it is manually refreshed.

on the Tivoli Enterprise Portal Server

on the Tivoli Enterprise Monitoring Server

on the local machine of the user but export is possible towards a central location

on the same location as the product defined queries if selected before starting the query creation

TEMS Login, TEPS Login

GMT Time. ITM Performance Data

Manage Systems List, Global Policies

Universal Time, ITM Historical Collection

Information related to the Event Processing flag

Information related to the exported Situation handler

Information related to Autonomous agent process tracking

Information related to the self-describing agent installation process

List the monitored attributes and how much data will be collected

List the situations that will be firing and generate reports on the data

Create a data flow diagram and use the historical reporting workspace

Run a scan with associated situations and map the data to the warehouse

Table view

Graphic view

Situation Event Console

Common Event Console

to show summary status information about remote agent deployments

to give an overview of the situation event status throughout the enterprise

to list the monitoring agents in the managed network and their online or offline status

to provide a visual health check of the monitoring servers in the enterprise and the application support that has been applied

Number of agents

Number of Tivoli Enterprise Portal Servers

Number of Tivoli Enterprise Monitoring Servers

Number of Summarization and Pruning agents

Administration Mode Eligible and Author Mode Eligible

Author Mode Eligible and Workspace Administration Mode

Workspace Administration Mode and Workspace Author Mode

Administration Mode Eligible and Workspace Administration Mode

Historical Situation

Event Integration Facility

Historical Data Collection

The Until feature on a situation

Dashboard Hub Services

Tivoli Enterprise Portal Server

Tivoli Authorization Policy Server

Operating System User Registry

Operations

Management

Administrators

Support Teams

tacmd

tivcmd

itmcmd

wadmin

4

8

12

24

Other workspaces that use that query will be affected.

Only the specific view is affected because queries are associated with a specific view.

Situations that use the specific attribute group associated with the query could be affected.

Only views within the given workspace will be affected because queries are associated with specific workspaces.

Command output is displayed in a pop-up box.

Command output is written to the message log.

Command output is written to the universal message log.

A return code is displayed as to whether or not the command executed.

Tivoli Enterprise Portal

Remote TEMS Console

Dashboard Hub Services

Manage Tivoli Enterprise Monitoring Services

Symbols tab

Members tab

Dynamic Items tab

Monitored Resources tab

Link

Policy

Workflow

Workspace Administration

Expired

Unknown

Reopened

Acknowledged

User ID

Hostname

MAC address of agent

Custom values taken from the kfwenv file

Simple

Relative

Absolute

Advanced

If an agent name is dimmed (grayed out), the agent has started or is responding.

The Navigator does not refresh automatically whenever the status of agents changes between offline and online.

The Navigator updates automatically when an agent is removed from or a new agent is added to the managed network.

A count of changes to the Navigator view is kept as agents are removed from, disabled, or added to the monitoring server.

Go to the Action tab click the Advanced button, and select the Attribute Item to be the Display Item

Go to the Action tab, click the Attribute Substitution button, and select the Attribute Item to be the Display Item

Go to the Formula tab, click the Display Item button, and select the Attribute Item from the drop-down list to be the Display Item

Go to the Formula tab, click the Advanced button, click the Display Item tab, and select the item from the drop-down list to be the Display Item

Send the event to IBM Tivoli Netcool/OMNI bus automatically.

This is not possible with the current version of IBM Tivoli Monitoring.

Run a script that forwards the event to the remote event management system.

Override the default option where the event is forwarded to the remote event management system.

The sampled situation is stopped.

The sampled situation event is closed.

The sampled situation event is expired.

The event is written to the Tivoli Data Warehouse.

A current value and plots it against time in a running graph

Historical data from a time period and plots data based on statistical calculations

Situation data and compares it to a historical boundary equation based on historical data

Situation data and compares it to a statistical boundary equations based on historical data

To show the workflow from the policy

To send e-mail alerts to Administrators

To show the Take Action command issued

To give operators help information or resolution advice

With agent status

With all event correlated

With hardware information

With the last historical data reported

Using Extensions

Using a Pure Event

Using the Event Integration Facility

Using the TADDM Event Forwarder

It is removed.

It is converted to a quick acknowledgment.

It remains, and the status of the event is still set to Acknowledged.

It is expired, and the status of the event is still set to Acknowledged.

Workspace

Navigator Tree

Situation Editor

Navigator Elements

To set an until condition

To prevent alerting on spikes

To make a situation a pure event

To allow the use of only one attribute in the situation definition

It does not close automatically by default.

It has a unique randomized control number.

It links with enterprise workspace automatically.

It returns multiple rows for historical data collection.

Start/Stop SNMP

Start/Stop a Policy

Start/Stop an IBM Tivoli Monitoring Agent

Start/Stop an IBM Tivoli Application Dependency Discovery Manager

The Navigator item will be grey.

The situation icon will appear red for all situations when true.

The situation icon will always appear beside the Navigator item.

The Navigator item will appear when the situation becomes true.

It converts short-term history files to delimited flat files.

It is used to dynamically change the tracing options for an agent.

It is used transfer a file from a remote managed system to a local destination.

It is used to generate the auto start scripts on UNIX and Linux based on the definitions in kcirunas.cfg.

Verify the database is supported.

Verify the Tivoli Enterprise Portal Server user ID is logged in to the TDW.

Verify the Summarization and Pruning agent is running according to its schedule.

Verify the database User ID the Warehouse Prows agent is using has sufficient database privileges.