IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Plan checklist

Correctly planning your installation is probably the most important thing that you can do to achieve a smoothly running environment. By carefully planning the size of your servers, understanding your network topology, and understanding your key requirements, you can create a monitoring environment that meets your needs.

Careful planning is a team effort. Engage the networking team to ensure you understand all of the network firewall configurations and to open ports in the firewall. Understand the key requirements such as fault tolerance, executive dashboards, and reporting. The following sections outline the key planning items that you must complete to have a successful deployment.

Use the Planning checklist in Table 1 to ensure that all important planning tasks are accomplished. Perform all of these tasks before starting the Tivoli Monitoring installation. The following sections of this guide provide the necessary information to complete this checklist.


Planning checklist

Plan activity Comments Status
Attend IBM Tivoli Monitoring Administrator Training.
Complete
Determine the desired platforms for Tivoli Monitoring infrastructure components.
 
Identify the number of Tivoli Monitoring agents (typically 3 monitoring agents per monitoring server).    
Determine high availability and disaster recovery requirements. Map those requirements to the Tivoli Monitoring deployment.    
Determine whether a firewall gateway is required and between which components.    
Determine the location of any remote monitoring servers.    
Determine that an adequate number of Warehouse Proxy Agents are planned.    
Provide Network administrators with a list of ports to open.    
Complete the Warehouse load projection spreadsheet.    
Determine the hardware required for the Tivoli Monitoring components.    
Download all the required software for your supported operating systems including all monitoring agents.    
Complete your deployment Verification Test Plan.    
Review the Readme and Documentation Addendum and determine the installation steps based on your platform.    
Determine the method of user authentication.    
If you plan to use Netcool/OMNIbus as your event server, work with your Netcool/OMNIbus administrator to determine the location of the Netcool/OMNIbus components and to plan the installation of the IBM Tivoli Monitoring Event Synchronization component.    
If you plan to use the IBM Infrastructure Management Dashboards for Servers application or other monitoring dashboard applications for the IBM Dashboard Application Services Hub:

  • determine where to install the IBM Dashboard Application Services Hub and its prerequisites.

  • determine if you will setup a network repository that can be used for installing Jazz for Service Management and IBM Tivoli Monitoring components throughout the enterprise or if you will use the installation launchpad applications provided by Jazz for Service Management and IBM Tivoli Monitoring to perform installations directly from the installation media.

  • determine whether the Authorization Policy Server or Tivoli Enterprise Portal user management will be used to authorize which resources can be viewed by dashboard operators.

  • if you plan to use the Authorization Policy Server, determine where the tivcmd CLI for Authorization Policy component should be installed. Administrators who create and work with authorization policies will use this CLI.

   
If you plan to use IBM Tivoli Monitoring reports with Tivoli Common Reporting, determine where to install Tivoli Common Reporting and its prerequisites.    
If you plan to use the OSLC Performance Monitoring service provider, determine where to the install the Jazz for Services Management Registry Services component and, optionally, the Security Services component and their prerequisites.    

Tivoli Monitoring V6.3 supports integration with LDAP user registries for authentication.

LDAP SSL requires some actions by an LDAP administrator that are not covered by the Tivoli Monitoring V6.3 documentation. Here are some LDAP SSL Web pages for working with LDAP servers:

If the hub monitoring server is configured to use an LDAP server, LDAP SSL communication will also require the creation of a GSKit keystore for the hub monitoring server; see the Securing communication chapter in the IBM Tivoli Monitoring Administrator's Guide.


Parent topic:

Pre-deployment phase

+

Search Tips   |   Advanced Search