Cisco Info Center 7.3 Documentation Guide and Supplemental License Agreement
Available Languages
Table Of Contents
Cisco Info Center 7.3 Documentation Guide and Supplemental License Agreement
ADDITIONAL LICENSE RESTRICTIONS
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS
License Terminology and Packaging
Concurrent User (Limited User)
Cisco Info Center Omnibus and Network Manager
Tier 1 (VUE C) Third Party Impact
Tier 3 (VUE C) Third Party Impact
Cisco Info Center Service Quality Management Center
Netcool Customer Experience Manager
Composite Application Manager for SOA
Composite Application Manager for Applications
Composite Application Manager for Transactions
Composite Application Manager for J2EE Operations
Composite Application Manager for Internet Service Monitoring
Monitoring for Microsoft Applications Entry
Monitoring for Energy Management
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco Info Center 7.3 Documentation Guide and Supplemental License Agreement
Revised: April 21, 2010, OL-22325-01This document contains the End User Supplemental License Agreement for Cisco Systems Network Management software and provides links to the Cisco Info Center 7.3 documentation.
Contents
•
Product Documentation Set, page 2
•
•
Product Documentation Set
The following sections indicate the URLs for the Cisco Info Center 7.3 documentation.
Documentation Guide and Supplemental License Agreement
Cisco Info Center 7.3 Documentation Guide and Supplemental License Agreement
http://www.cisco.com/en/US/products/sw/netmgtsw/ps996/
products_documentation_roadmaps_list.htmlCisco Info Center 7.3 Release Notes
Release Notes for Cisco Info Center, 7.3
http://www.cisco.com/en/US/products/sw/netmgtsw/ps996/prod_release_notes_list.html
Tivoli NetCool/OMNIbus Documentation Index Page
Tivoli Netcool/OMNIbus Object Server 7.3 Documentation
•
•
•
•
•
•
•
•
•
Netcool Webtop Server 2.2 Documentation
•
•
•
•
IBM Tivoli Business Service Manager (TBSM) Documentation
To view the IBM TBSM documentation, go to the following location:
Tivoli Network Manager IP Edition 3.8 Documentation
Network Manager IP Edition allows you to discover, visualize, and monitor your network. The auto-discovery capabilities of Network Manager IP Edition include a wide range of devices and protocols, and both physical and logical containment. Topology-based root cause analysis allows network operators to focus on the real problems rather than responding to symptomatic events. Network Manager IP Edition also uses the event management capabilities of Tivoli Netcool/OMNIbus to present an integrated view of network topology and events.
For information on this product, see:
•
•
•
•
•
•
•
•
•
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.networkmanagerip.doc_3.8/nmip_ref_dbpdf_38.pdf
•
•
•
•
Tivoli Network Manager Transmission Edition 5.6 Documentation
The Tivoli Network Manager Transmission Edition product discovers telecommunications networks on multiple technologies and provides a complete, up-to-date inventory of network assets. It integrates complete inventory, facility, and connection data with Tivoli Netcool/OMNIbus alerts so that operators can locate, diagnose, and solve network problems more easily.
For information on this product, see:
•
•
•
•
Tivoli Netcool/Reporter 2.2 Documentation
Netcool Reporter is a real-time, web-based, client-server application that provides accurate reporting on a database data repository. Netcool Reporter includes a set of predefined reports for Object Server data. Netcool Reporter can also generate reports from data sources populated by gateways supplied with other Netcool products.
For information on this product, see:
•
•
See the list of Release Notes on the IBM documentation start page.
•
•
Tivoli Netcool Impact 5.1 Documentation
Tivoli Netcool/Impact streamlines event and alert management, business service management, and incident and problem management processes, improving time to resolution.
For information on this product, see the Tivoli Netcool Impact documentation page at this URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/topic/com.ibm.netcoolimpact.doc/welcome.htm
IBM Tivoli Monitoring Documentation
SSM/ASM 4.0 has been integrated into ITM (IBM Tivoli Monitoring).
Netcool/SSM provides real-time monitoring for systems, applications, and networks. It is a key technology in maintaining overall performance and availability of business and application services. Netcool/SSM is based on the Simple Network Management Protocol (SNMP) and implements the MIB-II, RMON and RMON2 network monitoring standards.
For information on this product, see:
IBM Tivoli Composite Application Manager Documentation
Netcool Tivoli Composite Application Manager (ITCAM), formerly known as Netcool Internet Service Manager (Netcool/ISM), is a set of software components designed to monitor the availability, response time, and performance of Internet services such as Web sites, Web-based e-commerce applications, electronic mail, as well as the underlying services, such as DNS, LDAP, and SMTP, that those Internet services rely on.
ITCAM works by emulating the actions of a real user. For example, the HTTP monitor tries to access particular Web pages, then measures how well the HTTP service performed. The data recorded by the monitor provides immediate indication of the status of the HTTP service to the service operators, and can also be used later to provide graphical reports on service performance.
For information on ITCAM, see the following URL:
Gateway Support Documentation
Specific gateway support documents are available at this URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp
In the Contents frame at the left of the Tivoli Netcool/OMNIbus documentation page, click Network Availability Management, then click Tivoli Netcool/Omnibus and then click Tivoli Netcool/Omnibus Gateways. Then, from the directory tree, select a gateway.
For general information on Tivoli Netcool/Omnibus gateways, including bidirectional gateways, see the following URL:
•
Probe Support Documentation
In addition to operating with probes that are co-developed by Cisco and IBM, Cisco Info Center 7.3 operates with probes for a wide variety of equipment made by other manufacturers. For a complete list of all the available probes, go to this URL:
http://publib.boulder.ibm.com/infocenter/tivihelp/v8r1/index.jsp
Click Network Availability Management in the navigation pane at the left of the screen. Then click IBM Tivoli Netcool/Omnibus > Tivoli Netcool/Omnibus probes and TSMs. Then, from the directory tree, select the plus sign (+) next to a vendor name, for example, Cisco, to see a list of probe documents for that vendor's products.
For general information on Netcool Omnibus probes, see the following URL:
Netcool/Common License Server Documentation Page
The Tivoli Netcool/Common License Server Documentation page provides links to licensing documentation, including the Netcool/Common License Server Administration Guide:
CISCO SYSTEMS—SUPPLEMENTAL LICENSE AGREEMENT FOR CISCO SYSTEMS NETWORK MANAGEMENT SOFTWARE: CISCO INFO CENTER
IMPORTANT READ CAREFULLY: This Supplemental License Agreement ("SLA") contains additional limitations on the license to the Software provided to Customer under the End User License Agreement between Customer and Cisco. Capitalized terms used in this SLA and not otherwise defined herein shall have the meanings assigned to them in the End User License Agreement. To the extent that there is a conflict among any of these terms and conditions applicable to the Software, the terms and conditions in this SLA shall take precedence.
By installing, downloading, accessing or otherwise using the Software, Customer agrees to be bound by the terms of this SLA. If Customer does not agree to the terms of this SLA, Customer may not install, download, or otherwise use the Software.
ADDITIONAL LICENSE RESTRICTIONS
Installation and Use
Customer may only install and run copies of the Software for which the customer has purchased the required licenses. Customer may install and run the Software to manage up to the number of nodes and concurrent user licenses purchased by the customer. Customers whose requirements exceed the number of authorized nodes or concurrent users must purchase and register additional licenses.
Customers may request license keys for the Cisco Info Center components they have purchased by sending an email to cickeys@us.ibm.com. The email should include the Cisco Info Center components for which license keys are required and the relevant Cisco Sales Order Number for each of the Cisco Info Center components.
Components of this Software are provided to Customer solely to be used with this Software.
Reproduction and Distribution
Customer may not reproduce nor distribute software.
DESCRIPTION OF OTHER RIGHTS AND LIMITATIONS
Please refer to the Cisco Systems, Inc. End User License Agreement.
License Terminology and Packaging
Cisco Info Center Terminology
This section describes terms used in determining licensing requirements for Cisco Info Center.
Asset
Tangible resource or item of value that is managed, including production equipment, facilities, transportation, IT hardware and software.
Application Instance
A license entitlement is required for each instance (Install) of an application connected to the Program.
Client Device or Client
Client Device is a unit of measure by which the program can be licensed. A Client Device is a computing device that requests the execution of or receives for execution a set of commands, procedures, or applications from another computer system that is typically referred to as a server or is otherwise managed by the server. Multiple client devices may share access to a common server. A Client Device generally has some processing capability or is programmable to allow a user to do work. Examples include, but are not limited to appliances, automated teller machines, cash registers, disk drive, desktop computers, kiosks, notebook computers, personal digital assistant, point-of-sale terminals, tape drive, and technical workstations. Licensee must obtain entitlements for every Client Device which runs, which uses services provided by, is managed by, or otherwise accesses the Program and every other computer or server where the Program is installed.
Concurrent User
Concurrent User is a unit of measure by which the Program can be licensed. A Concurrent User is a person who is accessing the Program at any particular point in time. Regardless of whether the person is simultaneously accessing the Program multiple times, the person counts only as a single Concurrent User. The Program may be installed on any number of computers or servers, but Licensee must obtain entitlements for the maximum number of Concurrent Users simultaneously accessing the Program. Licensee must obtain an entitlement for each simultaneous Concurrent User accessing the Program in any manner directly or indirectly (for example: via a multiplexing program, device, or application server) through any means
Concurrent User (Limited User)
A concurrent user limited to read-only operation.
Enterprise
Any legal entity (such as a corporation) and the subsidiaries it owns by more than 50 percent.
Install
Install is a unit of measure by which the Program can be licensed. An Install is an installed copy or instance of the Program on a physical or virtual disk made available to be executed on a computer. Licensee must obtain an entitlement for each Install of the Program.
Network Node or Node
Network nodes include routers, switches, hubs, and bridges that contain a network management agent. A single network node may contain any number of interfaces or ports.
Network Security Device
Network security device is any network-based security appliance or server running network security software that provides a source of security events or logs. Examples include, but are not limited to firewalls, application firewalls, intrusion detection systems, intrusion protection systems, virtual private networks (VPNs), threat protection products (antivirus gateways), content filtering (Web, e-mail), identity and access management, directory servers, network anomaly behavior products, and multifunction security appliances.
Port
A port is the physical connection between a device and the network.
Processor Value Unit
The Processor Value Unit (PVU) is a unit of measure by which the Program can be licensed. Proofs of Entitlement for PVUs are based on processor technology (defined within the PVU Table by Processor Vendor, Brand, Type and Model Number at:
http://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html
A processor, for the purpose of PVU-based licensing, is defined to be each processor core on a chip. The licensee must obtain entitlements sufficient to cover every activated processor core in the environment which is made available to the Program.
The physical hardware environment includes all processor cores:
1.
2.
Resource Value Unit
Resource Value Unit (RVU) is a unit of measure by which the Program can be licensed. RVU Proofs of Entitlement are based on the number of units of a specific resource used or managed by the Program. Licensee must obtain sufficient entitlements for the number of RVUs required for Licensee's environment for the specific resources as specified in the table(s) below. RVU entitlements are specific to the Program and the type of resource and may not be exchanged, interchanged, or aggregated with RVU entitlements of another program or resource. The RVU tables are shown for each applicable product example below.
Value Units
A Value Unit (VU) is a unit of measure by which the Program can be licensed. Value Unit entitlements are based on the quantity of a specific designated measurement, for example MSUs, Users, Engines, Tape Drives, etc., for the given software. Licensee must obtain sufficient entitlements for the number of Value Units required for Licensee's environment as specified in the specific Program terms. The Value Unit entitlements are specific to the Program and may not be exchanged, interchanged, or aggregated with other Value Unit entitlements of another program.
Server
Server is a unit of measure by which the Program can be licensed. A Server is a physical computer that is comprised of processing units, memory, and input/output capabilities and that executes requested procedures, commands, or applications for one or more users or client devices. Where racks, blade enclosures, or other similar equipment is being deployed, each separable physical device (e.g., a blade or a rack-mounted device) that has the required components is considered itself a separate Server. For the purpose of Server-based licensing, Licensee must obtain entitlements for each Server which is made available to the Program, regardless of the number of processor cores and/or partitions in the Server or the number of copies of the Program on the Server.
Standby or Backup Systems
For programs running or resident on backup machines, three types of situations are defined: cold, warm and hot. In cold and warm situations, a separate entitlement for the copy on the backup machine is normally not required and typically no additional charge applies. In a hot backup situation, the customer needs to acquire other licenses or entitlements sufficient for that server. All programs running in backup mode must be solely under the customer's control, even if running at another enterprise's location. In practice, the following are definitions and allowable actions concerning the copy of the program used for backup purposes:
•
•
•
Doing work includes, for example, production, development, program maintenance, and testing. It also could include other activities such as mirroring of transactions, updating of files, synchronization of programs, data, or other resources (for example, active linking with another machine, program, database or other resource, and so on), or any activity or configurations that would allow an active hot switch or other synchronized switch-over between programs, databases, or other resources to occur.
In the case of a program or system configuration that is designed to support a high availability environment by using various techniques (for example, duplexing, mirroring of files or transactions, maintaining a heartbeat, active linking with another machine, program, database, or other resource,), the program is considered to be doing work in the hot situation and a license or entitlement must be purchased.
Cisco Info Center Omnibus and Network Manager
Cisco Info Center OMNIbus is priced using the following chargeable components and metrics:
•
•
–
–
–
–
To determine the number of RVUs applicable to licensee use of the program, the licensee must multiply the number of managed entities in a tier by the applicable RVU Factors as follows:
A different RVU Factor applies to different number ranges of the managed entities. Apply an RVU Factor of:
•
•
•
•
•
•
•
Pricing Example
A customer installs two instances of the Cisco Info Center OMNIbus ObjectServer, and is managing 300 point-of-sale terminals and three EMSs.
The customer requires the following:
•
•
•
Cisco Info Center Omnibus and Network Manager is priced using the following chargeable components and metrics:
•
•
•
•
•
•
•
•
•
These tiers have the following characteristics:
•
•
•
•
•
The licensee may purchase RVUs to entitle management of a maximum of 1,000 devices at the Entry Tier.
To determine the number of RVUs applicable to licensee use of the program, the licensee must multiply the number of managed entities in a tier by the applicable RVU Factors as follows.
A different RVU Factor applies to different number ranges of the managed entities. Apply an RVU Factor of:
•
•
•
•
•
•
•
The following are not priced and unlimited instances of these are included in each Cisco Info Center entitlement.
•
•
•
•
•
•
•
VUE 002 Tables
The following Value Unit Exhibit (VUE) Tables apply to the Impact, Service Quality Manager, Reporter, Business Service Manager and Webtop products that are described later in this document.
VUE Tables A and B
VUE Table C
Cisco Info Center Impact
Cisco Info Center Impact is priced per install; each Impact application instance is considered a single install of Impact. It is also priced by tier by the amount of each type of technology that each Impact install (application instances) uses. The number of RVUs required per tier is defined below. Volume scaling is applied to each tier as indicated below per VUE, and as indicated in VUE 002 Table C.
Tier 1 (VUE C) Impact
This is counted by the number of Impact installs (application instances) any of each of the following technologies is used with:
•
•
•
•
•
•
•
•
•
•
•
•
Tier 1 (VUE C) Third Party Impact
This is counted by the number of Impact installs (application instances) any of each of the following technologies is used with:
•
Tier 2 (VUE C) Impact
This is counted by the number of Impact installs (application instances) any of each of the following technologies is used with:
•
•
•
Tier 3 (VUE C) Impact
This is counted by the number of Impact installs (application instances) any of each of the following technologies is used with:
•
•
Tier 3 (VUE C) Third Party Impact
This is counted by the number of Impact installs (application instances) any of each of the following technologies is used with:
•
•
Pricing Examples
Example 1a
ABC Consumer Goods deploys Cisco Info Center Impact over two application instances across four processor cores (multiprocessor core capable) on two servers and each appliance instance interfaces to Oracle, LDAP, and DB2 databases.
Calculation: two Impact application instances connecting to three Tier 1 databases each = six DSA Tier 1 connections.
Example 1b
ABC Consumer Goods deploys Impact over three application instances across six processor cores (multiprocessor core capable) on three servers and each application instance interfaces to Oracle databases, LDAP systems, TCP/IP Sockets, and XML.
Calculation: 3 Impact application instances interfacing to 4 Tier 1 databases each = 12 DSA Tier 1 connections.
Cisco Info Center Service Quality Management Center
Service Quality Management Center is a bundle of three components: Business Service Manager, Service Quality Manager, and Customer Experience Manager. The bundle is priced by the following chargeable components and metrics.
All Components
All components require the following metric:
•
Service Quality Manager
Service Quality Manager requires:
•
•
Netcool Customer Experience Manager
Netcool Customer Experience Manager requires:
•
•
Business Service Manager
Business Service Manager requires:
•
This is counted by the number of end devices monitored via:
–
–
–
–
–
–
–
And the number of:
–
–
–
–
–
–
–
–
–
–
•
This is counted by the number of managed devices from the following list:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
This is also counted by the number of databases managed using ODBC or Informix, which is counted by the number of connections to the managed devices in the following list:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
Pricing Example
A service provider deploys Service Quality Management Center at its country site. The customer only wants to deploy the Service Quality Manager (TNSQM) component of the solution in its environment to manage two services (for example VoIP and IPTV). The customer uses several servers at its country site and has seven million subscribers for both services. The services they want to manage require a total of five data source types.
Note
In a future period, the service provider expands its network to nine million users and wants to deploy Customer Experience Manager (TNCEM) in its environment. The service provider will need to entitle all nine million subscribers for the Customer Experience Manager component. However, the service provider is already entitled to the install for the entire solution. In addition, the service provider has entitlement for seven million subscribers for Service Quality Manager for two services (VoIP and IPTV.) For the additional 4 million subscribers (2 million x 2 services) of Service Quality Manager, the service provider will use the .0006 factor in VUE 002 Table E.
Note
Note
To deploy BSM, the service provider will need to entitle their 3,000 Tier 1 devices and their 20 Tier 2 devices, as shown in the following table.
Note
Note
Netcool/Reporter
Reporter is priced per install and per RVU. Each physical site per environment (production, hot standby, non-production) is considered a single install of Netcool/Reporter. RVU is defined below. Volume scaling is applied to tiers as indicated per specific VUE as indicated in VUE 002 Table C above.
•
Business Services Manager
Business Service Manager is priced per install and per tier RVU (Resource Value Unit). Each physical site is considered a single install of Business Services Manager.
Base per Install per physical site, production, hot standby, and non-production are each considered a single install. The number of base per install components required are the same regardless of how many components of the bundle are being licensed.
RVU per Tier is described below. Volume scaling is applied to tiers as indicated below per specific VUE.
•
–
–
–
–
–
–
–
And the number of:
–
–
–
–
–
–
–
–
–
–
–
•
This is counted by the number of managed devices from the following list:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
And by the number of:
–
–
–
–
–
–
–
–
–
And by the number of databases managed using ODBC or Informix
This is counted by the number of connections to the managed devices in the following list:
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
The customer's environment consists of 3,000 Tier 1 devices and 20 Tier 2 devices as outlined in the metric descriptions above. The customer will need to entitle their 3,000 Tier 1 devices and their 20 Tier 2 devices.
The following tables describe the metrics for Tier 1 devices and Tier 2 devices.
* Using VUE002 Table B, the customer requires 1,499 RVUs to entitle their 3,000 Tier 1 devices. The quantity to order is 1,499 Resource Value Units. The first 10 are at a factor of 1.0, the next 90 at a factor of .9, the next 150 at a factor of .8, the next 250 at a factor of .65, and the final 2,500 at a factor of .45.
** Using VUE002 Table B, the customer requires 19 Resource Value Units to entitle their 20 Tier 2 devices. The quantity to order is 19 Resource Value Units. The first 10 at a factor of 1.0 and the next 10 at a factor of .9.
Webtop
Webtop is priced per install, per concurrent user, and per limited use concurrent user (read-only). Each physical site per environment (production, hot standby, non-production) is considered a single install of Netcool/Webtop. Resource Value Unit (RVU) per tier is described below.
Volume scaling is applied to tiers per specific VUE, as indicated in VUE 002 Tables A and B above:
•
•
Gateways
IBM Tivoli Netcool/OMNIbus Gateways is priced per connection (Tier 1) and application instance (Tier 2).
Tier 1 Gateways
This is counted by:
•
•
•
Tier 1 Third-Party Gateways:
This is counted by the number of databases from the following list that connection is made to:
•
•
•
•
•
Tier 2 Gateway
This is counted by the number of application systems from the following list that connection is made to:
•
•
•
•
•
•
•
•
•
•
Distributed Pricing Examples (Processor Core and Processor Value Unit Based)
The following examples are provided to illustrate the customer's licensing requirements.
References to processor-based licensing do not represent the actual number of entitlements required. Entitlement requirements are Value Unit based. Processors referenced in these examples represent the designated measurement on which the required number of Value Unit entitlements will be calculated.
The number of Value Units required per processor core will depend on the processor type. For more information, refer to the Value Unit definition in the terminology definitions. References to all other non-processor-based metrics do represent the actual number of entitlements required, unless other designated measurements are referenced or unless otherwise specified.
The pricing example below should be used to determine required license entitlements for the following distributed products:
•
•
•
•
•
•
•
Products with an asterisk (*) indicator also have program-specific licensing terms, which are described later in this document. Consult the program-specific licensing terms to determine total licensing requirements for the applicable products.
Pricing Example
The following customer network (referred to as the core environment) applies to all of the examples to enable the reader to see where products tend to manage something less than the entire environment. The customer's overall core environment includes:
•
•
•
•
•
•
•
•
•
•
The customer wants to manage the applicable distributed server environment, which requires Processor Value Unit entitlements associated with the following number of processor cores, as indicated in the following table:
Composite Application Manager for SOA
DataPower SOA Appliances are priced using a fixed one processor charge. In addition to the core environment described above (processor value unit entitlements associated with the 274 Managed Processor requirement for the IBM Tivoli Composite Application Manager for SOA program), the customer decides to manage ten (10) DataPower SOA Appliances. The customer must obtain processor Value Unit entitlements associated with the following number of processors with a processor Value Unit assignment of 100 Value Units per processor, as indicated in the following table:
Composite Application Manager for Applications
If you have licensed the Full Agent Pack, you may use and install any and all agents that are provided. If you have licensed the Three Agent Pack, you are authorized to install and use, on the same managed physical server, only up to 3 of the agents that are provided.
Exclusions
The agents listed below may be installed in addition to the 3 agent limitation described above.
•
•
•
•
•
•
•
Installation and use of more than three agents requires licensing of the Full Agent Pack.
Composite Application Manager for Transactions
Determine the number of licenses required for the monitoring application as follows.
Client Response
Count the number of clients on which the client response monitor will be run. For example, to monitor Lotus Notes on 100 Windows XP desktop systems requires 100 Client Device licenses.
Web Response
The customer wants to manage the Web server environment, which requires Value Unit entitlements associated with the following number of processor cores, as shown in the following tables:
Robotic Response
This is similar to Web response monitoring, but in the case of robotic response monitoring, the number of licenses is determined by where the robot is being run, sometimes called points of presence. It does not matter how many servers or devices make up the transaction. In this example, the customer wants to monitor transactions from several points of presence, which requires Value Unit entitlements associated with the following number of processor cores, as shown in the following table:
Transaction Tracking
Transaction tracking is licensed based on the environment through which the transaction is being tracked, which determines the number of required Value Units. In the example shown in the following table, the transactions run across the following environment:
Composite Application Manager for J2EE Operations
IBM Tivoli Composite Application Manager for J2EE Operations V6.0 is licensed by managed server. A license is required for each server that is managed by the program. As shown in the following table, if the customer's managed environment include the servers shown in the following table, the requirements are as indicated in the following table:
Composite Application Manager for Internet Service Monitoring
A license is required for each protocol on each server that is managed by the program. IBM Tivoli Composite Application Manager for Internet Service Monitoring is licensed by protocol for each managed server. If the customer's managed environment includes:
•
•
•
•
The customer will require the entitlements shown in the following table:
Monitoring for Microsoft Applications Entry
IBM Tivoli Monitoring for Microsoft Applications Entry is licensed by managed servers. The customer's overall managed environment includes the number of servers indicated in the Quantity in Customer Environment column for the specified number of servers to be systems managed, as shown in the following table.
Monitoring for Energy Management
Monitoring for Energy Management is priced based on the managed environment approach. For example, to manage the Assets in the environment described below requires the following licenses, as shown in the following table:
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.htm
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Feedback