Complete the steps in this section to install IBM® Tivoli® monitoring
on one Windows computer.
Procedure
- Launch the installation wizard by double-clicking the setup.exe
file in the WINDOWS subdirectory of the installation media.
- Click Next on the Welcome window.
- Click Accept to accept the license
agreement.
- Choose the directory where you want to install the product.
The default directory is C:\IBM\ITM. Click Next.
Note: If you
specify an incorrect directory name, you will receive the following
error:
The IBM Tivoli Monitoring installation directory cannot exceed 80 characters
or contain non-ASCII, special or double-byte characters.
The directory name can contain only these characters:
"abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ _\:0123456789()~-./".
- Click Next to accept the default
encryption key and then click OK on the popup
window to confirm the encryption key.
- On the Select Features window, select the check boxes for
the components you want to install. Select all components for a complete
installation on one computer.
For additional
information about these components, press the Help button.
Note: The
agent support comprises additional support files for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server,
and the Tivoli Enterprise Portal desktop
client; these are automatically installed whenever you install the
agent support. Also, the Eclipse Help Server is automatically installed
whenever you install a Tivoli Enterprise Portal Server.
- Click Next.
The Agent
Deployment window is displayed. This window lists monitoring agents
that you can deploy to remote computers. For this installation, do
not select any agents for remote deployment.
- Click Next.
- If the TEPS Desktop and Browser Signon ID and
Password window is displayed, enter and confirm the password to be
used for logging on to the Tivoli Enterprise Portal. The default
logon user ID, sysadmin, cannot be changed
on this window. This password is required only when Security:
Validate User has been enabled on the hub monitoring server.
This window is not displayed if the sysadmin user
ID has already been defined in the operating system.
- Review the installation summary details. The summary identifies
the components you are installing. Click Next to
begin the installation. The status bar indicates the progress of your
installation.
After the components are installed, a
configuration window is displayed.
- Click Next to start configuring
all selected components. (Leave all check boxes selected for this
installation.)
- Configure communications for the Tivoli
Enterprise Portal Server:
- Click Next to confirm that you
are installing the portal server on
this computer. (The host name of this computer is displayed by default.)
- If no relational database manager can be found in this
computer, the embedded Derby RDBMS is used by default. However, if
at least one RDBMS product is installed on this computer, a window
is displayed for you to choose the RDBMS product you want to use.
Choose either Embedded TEPS database (that
is, Derby), IBM DB2 Universal Database™ Server,
or Microsoft SQL Server,
and click Next.
- A window is displayed for you to configure the connection
between the portal server and
the portal server database (TEPS
database).
The installation program uses the information
on this window to automatically perform the following tasks:
- Create the portal server database.
- Create a database user for the portal server to
use to access the database.
- Configure the ODBC connection between the portal server and
the database.
Figure 1. Configuration
window for the portal server database using DB2 for Linux, UNIX, and Windows
Figure 1 shows
the configuration window for a
portal server database
using
DB2 for Linux, UNIX, and Windows.
The configuration window for a Derby or Microsoft
SQL Server database
is similar. The fields on the configuration window are described in
the following table:
Table 1. Configuration information
for the portal server databaseField |
DB2 for Linux, UNIX, and Windows default |
MS SQL default |
Description |
Admin User ID |
db2admin |
sa |
The database administrator ID. |
Admin Password |
(no default) |
(no default) |
The password for the database administrator
ID. |
Database User ID |
TEPS |
TEPS |
The login name of the database user that the portal server will
use to access the database. |
Database Password |
(no default) |
(no default) |
The password for the database login user. If
your environment requires complex passwords (passwords that require
both alpha and numeric characters), specify a password that complies
with these requirements. |
Reenter password |
(no default) |
(no default) |
Confirm the password by entering it again. |
Select database instance name |
(no default) |
(no default) |
Pull down the drop-down list, and select the
appropriate database instance. |
- Optionally change the default values for the administrator
ID and database user ID. Enter passwords for the administrator and
database user. Click OK.
- Click OK on the message that
tells you that the portal server configuration
was successful.
- Click Next to accept the default Tivoli Data Warehouse user ID
and password. (You can change these values in a later step.)
- In the TEP Server Configuration window, click OK to
accept the default communications protocol, IP.PIPE. IP.PIPE is the protocol that the portal server will
use to communicate with the Tivoli Enterprise Monitoring Server.
A
second TEP Server Configuration window is displayed. The IP.PIPE area
of this window displays the host name of this computer and the default
port number, 1918.
- Do not select Validate user with LDAP since
user authentication is not enabled during a single computer installation.
It can be configured at a later time.
- Select the Enable the dashboard
data provider check box if Dashboard Application Services
Hub will be used with monitoring dashboard applications such as IBM Infrastructure Management Dashboards
for Servers or will be used to create custom dashboard pages for monitoring
agents. See the Preparing your dashboard environment topic in the IBM Tivoli Monitoring Administrator's
Guide for
details on additional configuration tasks to perform after installation.
- Do not specify a value for the domain override or enable
authorization policies. Authorization policies are not enabled during
a single computer installation. They can be configured at a later
time.
- Click OK to accept the default
host name and port number.
- Click Yes on the message asking
if you want to reconfigure the warehouse connection information for
the portal server.
- Select DB2® or SQL Server from
the list of RDBMS platforms and click OK.
A window is displayed for you to configure the connection
between the portal server and
the Tivoli Data Warehouse
database. (The Tivoli Data
Warehouse database is referred to in the title of this window as the
data source for the Warehouse Proxy. The Warehouse Proxy Agent sends
information collected from monitoring agents
to the Tivoli Data Warehouse.)
The
installation program uses the information on this window to automatically
perform the following tasks:
- Create the Tivoli Data
Warehouse database.
- Create a database user (called the warehouse user) for
the portal server, Warehouse Proxy Agent,
and Summarization and Pruning Agent to use to access the warehouse
database.
- Configure the ODBC connection between the portal server and
the warehouse database.
Figure 2. Configuration window
for the Tivoli Data Warehouse
database using DB2 for Linux, UNIX, and Windows
|
Figure 3. Configuration window for the Tivoli Data Warehouse database
using Microsoft SQL Server
|
The fields on this window are described in the following
table:
Table 2. Configuration information for the Tivoli Data Warehouse databaseField |
DB2 for Linux, UNIX, and Windows default |
MS SQL default |
Description |
Data Source Name |
ITM Warehouse |
ITM Warehouse |
The name of the data source. 1 2 |
Database Name |
WAREHOUS |
WAREHOUS |
The name of the database. |
Admin User ID |
db2admin |
sa |
The database administrator ID. |
Admin Password |
(no default) |
(no default) |
The password for the database administrator
ID. |
Database User ID |
ITMUser |
ITMUser |
The login name of the database user that the portal server, Warehouse Proxy Agent,
and Summarization and Pruning Agent will
use to access the Tivoli Data
Warehouse database. |
Database Password |
itmpswd1 |
itmpswd1 |
The password for the database login user. If
your environment requires complex passwords (passwords that require
both alpha and numeric characters), specify a password that complies
with these requirements. |
Reenter password |
itmpswd1 |
itmpswd1 |
Confirm the password by entering it again. |
Note: - Warehouse Proxy Agent does not create this DSN - it
must already exist. If you are installing Performance Analyzer on
the same machine where the Tivoli Enterprise Portal Server is
installed, you can use the existing data source created by Tivoli Monitoring. Otherwise,
you must create a new System DSN manually, prior to re-configuring
Performance Analyzer.
- On 64-bit versions of Windows,
data sources created by the default ODBC Data Source Administrator applet
available from the Control Panel are not available if you are
installing the 32-bit version of the portal server. In this scenario,
you must use the 32-bit version of the ODBC Data Source Administrator applet
from <WINDOWS>\SysWOW64\odbcad32.exe. If you
are installing the 64-bit version of the portal server then you can
use data source created by the ODBC Data Source Administrator applet.
- Optionally change the default values on this window.
Enter the password of the database administrator. Click OK.
- Click OK on the message that
tells you that the portal server configuration
was successful.
- If your monitoring server is
not local, you must configure communications for the hub Tivoli
Enterprise Monitoring Server:
- Remove the check mark from Security: Validate
User. User authentication is not enabled during a single
computer installation. It can be configured at a later time.
- TEMS Security Compatibility
Mode allows for backwards compatibility with previous
versions of IBM Tivoli Monitoring components shipped before
V6.3 when securing command execution (Situation Take Action, Execute
Command, Take Action, Workflow Policy Take Action). Select this option
if you have a previous version of a portal server, hub monitoring
server, or OMEGAMON® product
connecting to this Tivoli Enterprise
Monitoring Server or if the time is not synchronized across the systems
with monitoring servers, the portal server, and monitoring agents.
Note: If you do not select this option under these conditions
then command executions might fail.
- Click OK to accept the other
defaults on the Tivoli Enterprise Monitoring Server
Configuration window:
The Hub TEMS Configuration window is displayed. The IP.PIPE area
of this window displays the host name of this computer and the default
port number, 1918.
- Click OK to accept the default
host name and port number.
- You are asked if you want to configure the Tivoli Enterprise Monitoring
Automation Server. If you select Yes the Configure
Tivoli Enterprise Monitoring Automation Server window
is displayed. Here you complete your Registry Services configuration
details and Tivoli Enterprise
Monitoring Automation Server connection details. When you select Configure
Registry Services connection, you must specify the correct
Protocol, Hostname, and Port number for the WebSphere® server where Registry Services
is installed.
The
User ID and
Password fields
must be completed with the User ID and Password values for your Registry
Services provider registry. The following criteria apply to the User
ID and Password fields:
- Providing both a user ID and a password is accepted.
- Leaving both the user ID and a password fields blank is accepted.
- Providing one parameter without the other is not accepted.
In the Automation Server connection information section,
provide the HTTP protocol and port for clients to connect to the automation
server.
- If your monitoring server is
not local, you must configure the default communication between any IBM Tivoli Monitoring
component and the hub Tivoli Enterprise Monitoring Server:
- On the configuration window, click OK to
accept the default communications protocol, IP.PIPE
A second configuration window is displayed. The IP.PIPE area
of this window displays the host name of this computer and the default
port number, 1918.
- Click OK to accept the default
host name and port number.
- The Configure Tivoli Performance Analyzer window
is displayed. Configure the agent for Data Warehouse. Some predefined
values will appear depending on whether you choose ODBC or JDBC from
the Agent Database Connection Type dropdown
list.
Figure 4. Configure Tivoli Performance Analyzer window - ODBC
If you choose ODBC from the Agent Database Connection
Type dropdown list, you must specify the following: - Set your Database Type to DB2, MSSQL or ORACLE
- Specify the Data Source Name - Agent ODBC DSN (ITM
Warehouse by default)
Note: - Tivoli Performance Analyzer
does not create this DSN - it must already exist. If you are installing
Performance Analyzer on the same machine where the Tivoli Enterprise Portal Server is
installed, you can use the existing data source created by Tivoli Monitoring. Otherwise,
you must create a new System DSN manually, prior to re-configuring
Performance Analyzer.
- On 64-bit versions of Windows,
data sources created by the default ODBC Data Source Administrator applet
available from the Control Panel are not available
for 32-bit applications. Therefore you must use the 32-bit version
of the ODBC Data Source Administrator applet
from <WINDOWS>\SysWOW64\odbcad32.exe.
- Type the Username and Password.
The entries in these fields are used to connect to the Tivoli Data Warehouse and are the same credentials
as those used by the Tivoli Enterprise
Portal Server, the Warehouse Proxy Agent and the Summarization and
Pruning Agent to communicate with Tivoli Data
Warehouse.
Figure 5. Configure Tivoli Performance Analyzer window - JDBC
If you choose JDBC from the Agent Database Connection Type dropdown
list, you need to specify the following: - Set your Database Type to DB2,
MSSQL or ORACLE.
- Provide the Hostname. The Hostname is the
host where the Tivoli Data
Warehouse is installed.
- Provide the Port number.
- Provide the Database Name.
- Type the Username and Password.
- Specify the JDBC Driver. The default driver name for DB2 is com.ibm.db2.jcc.DB2Driver.
- Specify the JDBC Driver Path, which should be provided as a list
of JAR files with the full path separated by ";".
Note: You can use
the Browse button in order to specify the path.
If you use the Browse button a file list is
added at the end of the JDBC Driver Path text
field separated from the existing content by a path separator. The
data is used to initialize the database, so it must be provided no
matter what Agent Database Connection Type was selected. The driver
path should be provided as a list of JAR files with the full path
separated by ";".
- Regardless of whether you choose ODBC or
JDBC as your Agent Database Connection Type you
can use the Test connection button to check
whether the connection can be initiated. Pressing OK button launches
more tests. Finishing the installation with incorrect connection settings
is impossible unless you use the Bypass connection tests option
in the Advanced configuration window.
- Click Next to proceed
to the Advanced Configuration window.
Figure 6. Configure Tivoli Performance
Analyzer window - Advanced configuration
Note: Do not change any of the values displayed in this window
unless you are an advanced user. Unless you select Enable
advanced configuration, all options are greyed out.
- You can configure Performance
Analyzer to use the IBM SPSS® Statistics Server to support
non-linear trending and forecasting of capacity and performance metrics.
To enable SPSS, select Enable SPSS configuration.
Figure 7. Configure Tivoli Performance Analyzer SPSS Configuration
- Browse to the location of your SPSS Statistics Server. Click Validate to
confirm the path you entered is correct.
Figure 8. Configure Tivoli Performance
Analyzer Enable SPSS Configuration
- Click OK.
Figure 9. Configure Tivoli Performance Analyzer
- Click OK. The system configures
and starts the agent.
- Click Yes on the message asking
if you want to configure the Summarization and Pruning Agent.
A multi-tabbed configuration window is displayed with the Sources tab
at the front.
Figure 10 shows
the configuration window for a
Summarization and Pruning Agent on Windows (values displayed are
for a
DB2 for Linux, UNIX, and Windows warehouse
database). The configuration window for a
Summarization and Pruning Agent on Linux or UNIX is similar.
Figure 10. Sources pane of Configure Summarization
and Pruning Agent window
- Add the names and directory locations of the JDBC driver
JAR files to the JDBC Drivers list box:
- Click Add to display the file browser window.
Navigate to the location of the driver files on this computer and
select the Type 4 driver files for your database platform. See for
the names and default locations of the driver files to add.
- Click OK to close the browser window and
add the JDBC driver files to the list.
If you need to delete an entry from the list, select the entry
and click Remove.
- The default values for the database platform you selected
in the Database Type pane are displayed in the other text fields on
the Sources pane. Change the default value
displayed in the JDBC URL field if it is not
correct. The following table lists the default Tivoli Data Warehouse URLs for
the different database platforms:
Table 3. Tivoli Data Warehouse URLsDatabase platform |
Warehouse URL |
IBM DB2 for Linux, UNIX, and Windows |
jdbc:db2://localhost:60000/WAREHOUS |
Oracle |
jdbc:oracle:thin:@localhost:1521:WAREHOUS |
Microsoft SQL Server |
jdbc:sqlserver://localhost:1433;databaseName=WAREHOUS |
- If the Tivoli Data Warehouse
is installed on a remote computer, specify the host name of the remote
computer instead of localhost.
- Change the port number if it is different.
- If the name of the Tivoli Data
Warehouse database is not WAREHOUS, replace WAREHOUS with the actual
name.
- Verify the JDBC driver name.
The
following table lists the JDBC Type 4 driver names for each database
platform:
Table 4. JDBC driver namesDatabase platform |
JDBC driver name |
IBM DB2 for Linux, UNIX, and Windows |
com.ibm.db2.jcc.DB2Driver |
Oracle |
oracle.jdbc.driver.OracleDriver |
Microsoft SQL Server |
com.microsoft.sqlserver.jdbc.SQLServerDriver
|
- If necessary, change the entries in the Warehouse
user and Warehouse password fields
to match the user name and password that were created for the Tivoli Data Warehouse. The default
user name is itmuser and the default password is itmpswd1.
- In the TEPS Server Host and TEPS
Server Port fields, enter the host name of the computer
where the Tivoli
Enterprise Portal Server is installed and the port number that
it uses to communicate with the Summarization and Pruning Agent.
Note: The default
Tivoli Enterprise Portal Server interface
port of 15001 is also used after the
Summarization and Pruning Agent's
initial connection to the
portal server over
port 1920. Any firewalls between the two need to allow communications
on either 15001 or whichever port is defined for any new
Tivoli Enterprise Portal Server interface
used per the instructions in
Defining a Tivoli Enterprise Portal Server interface on Windows.
- Click Test connection to
ensure you can communicate with the Tivoli Data
Warehouse database.
- Select the Scheduling check
box to specify when you want summarization and pruning to take place. You can schedule it to run on a fixed schedule or on a flexible
schedule:
Figure 11. Scheduling pane of Configure
Summarization and Pruning Agent window
Note: If you select Fixed, the Summarization and Pruning Agent does
not immediately perform any summarization or pruning when it starts.
It performs summarization and pruning when it runs. It runs
according to the schedule you specify on the Scheduling pane.
If you select Flexible, the Summarization and Pruning Agent runs
once immediately after it is started and then at the interval you
specified except during any blackout times.
- Specify shift and vacation settings in the Work
Days pane:
Figure 12. Work
Days pane of Summarization and Pruning Agent configuration window
When you enable and configure shifts, IBM Tivoli Monitoring
produces three separate summarization reports:
- Summarization for peak shift hours
- Summarization for off-peak shift hours
- Summarization for all hours (peak and off-peak)
Similarly, when you enable and configure vacations, IBM Tivoli Monitoring
produces three separate summarization reports:
- Summarization for vacation days
- Summarization for nonvacation days
- Summarization for all days (vacation and nonvacation)
Complete the following steps to enable shifts, vacations, or
both:
- Select when the beginning of the week starts.
- To configure shifts:
- Select Yes in the Specify shifts drop-down
list.
- Optionally change the default settings for peak and off peak hours
by selecting hours in the Select Peak Hours box.
Note: Changing
the shift information after data has been summarized creates an inconsistency
in the data. Data that was previously collected is not summarized
again to account for the new shift values.
- To configure vacation settings:
- Select Yes in the Specify vacation
days drop-down list to enable vacation days.
- Select Yes in the drop-down list if you
want to specify weekends as vacation days.
- Select Add to add vacation days.
- Select the vacation days you want to add from the calendar.
The
days you select are displayed in the list box.
If you want
to delete any days you have previously chosen, select them and click Delete.
Note: - Add vacation days in the future. Adding vacation days in the past
creates an inconsistency in the data. Data that was previously collected
is not summarized again to account for vacation days.
- Enabling shifts or vacation periods can significantly increase
the size of the warehouse database. It will also negatively affect
the performance of the Summarization and Pruning Agent.
- Select the Log Settings check box
to set the intervals for log pruning:
Figure 13. Log Settings pane of Summarization and Pruning Agent configuration
window
- Select Prune WAREHOUSELOG, select the number of units for which
data should be kept, and the unit of time (day, month or year).
- Select Prune WAREHOUSEAGGREGLOG, select the number of units for
which data should be kept, and the unit of time (day, month or year).
- Specify additional summarization and pruning settings in
the Additional Settings pane:
Figure 14. Additional Settings pane of Summarization
and Pruning Agent configuration window
- Specify the number of additional threads you want to use for handling
summarization and pruning processing. The number of threads should
be 2 * N, where N is the number of processors running the Summarization and Pruning Agent.
A higher number of threads can be used, depending on your database
configuration and hardware.
- Specify the maximum rows that can be deleted in a single pruning
transaction. Any positive integer is valid. The default value is 1000.
There is no value that indicates you want all rows deleted.
If
you increase the number of threads, you might consider increasing
this value if your transaction log allows for it. The effective number
of rows deleted per transaction is based on this value divided by
the number of worker threads.
- Indicate a time zone for historical data from the Use
timezone offset from drop down list.
This field indicates
which time zone to use when a user specifies a time period in a query
for monitoring data.
- Select Agent to use the time zone (or time
zones) where the monitoring agents
are located.
- Select Warehouse to use the time zone where
the Summarization and Pruning Agent is
located. If the Tivoli Data
Warehouse and the Summarization and Pruning Agent are
in different time zones, the Warehouse choice
indicates the time zone of the Summarization and Pruning Agent,
not the warehouse.
Skip this field if the
Summarization and Pruning Agent and
the
monitoring agents
that collect data are all in the same time zone.
- Specify the age of the data you want summarized in the Aggregate
hourly data older than and Aggregate daily
data older than fields. The default value is 1 for
hourly data and 0 for daily data.
- The Maximum number of node errors to display refers
to the node error table in the Summarization and Pruning workspace.
It determines the maximum number of rows that workspace is to save
and display.
- The Maximum number of summarization and pruning runs
to display refers to the Summarization and Pruning Run
table in the Summarization and Pruning workspace. It determines the
maximum number of rows that workspace is to save and display.
Maximum
number of Summarization and Pruning runs to display and Maximum number
of node errors to display together determine the number of rows shown
in the Summarization and Pruning overall run table and Errors table
respectively. There is a minimum value of 10 for each. These equate
to keywords KSY_SUMMARIZATION_UNITS and KSY_NODE_ERROR_UNITS in file KSYENV/sy.ini.
- The Database Connectivity Cache Time determines
how long after a positive check for connectivity that the result will
be cached. Longer times may result in inaccurate results in the workspace;
however, it saves processing time.
Database Connectivity Cache
Time records the number of minutes to cache the database connectivity
for reporting purposes. The minimum value is 5 minutes. This equates
to keyword KSY_CACHE_MINS in file KSYENV/sy.ini.
- Batch mode determines if data from different
managed systems are used in the same database batch; this setting
also improves performance.
Batch mode controls the batching method
used by the Summarization and Pruning Agent.
A value of Single Managed System (0) means that data should only be
batched for the same system, whereas a value of Multiple Managed System
(1) means that data from multiple systems can be batched together;
this can lead to higher performance at potentially bigger transaction
sizes. The default value is Single Managed System (0). This equates
to keyword KSY_BATCH_MODE in file KSYENV/sy.ini.
- Specify whether you want to turn Database compression on
or off.
- Specify whether you want to turn Database
Table Partitioning on or off. When partitioning is enabled,
the Summarization and Pruning Agent performs the following functions:
- Creates new summary tables as partitioned tables.
- Adds partitions to existing partitioned tables (including the
detail tables created by the warehouse proxy) based on your configuration.
- Prunes data from partitioned tables by dropping the appropriate
partitions.
To change these values, you can either use the Summarization
and Pruning configuration window's Additional settings tab
or update these parameters directly in file KSYENV/sy.ini.
- Save your settings and close the window. Click Save to
save your settings. Click Close to close the
configuration window.
- Click Finish to complete the installation.
Results
When the installation is complete, the
Manage Tivoli Enterprise Monitoring Services window
is displayed. This window is used for starting, stopping, and configuring
installed components. This window can be displayed at any time from
the Windows Start menu by
clicking
Start → Programs → IBM Tivoli Monitoring → Manage Tivoli Monitoring Services.
Figure 15. Manage Tivoli Enterprise
Monitoring Services window
What to do next
Complete the following tasks after you finish the installation
procedure:
- Start the Eclipse Help Server and the Tivoli Enterprise Portal
Server, if not started. Right-click the component in the Manage Tivoli Enterprise Monitoring Services window
and select Start.
To log on to the Tivoli
Enterprise Portal using the desktop client, double-click the Tivoli
Enterprise Portal icon on your Windows desktop.
Use the sysadmin password that you specified
in Step 9. (For more information
about logging on to the Tivoli Enterprise Portal, see Starting the Tivoli Enterprise Portal client.)
- Configure the Summarization and Pruning Agent.
The
installation procedure automatically starts and configures all the monitoring agents
that you installed except for the Summarization and Pruning Agent.
The Summarization and Pruning Agent is
not configured and started during installation to give you an opportunity
to configure history collection in advance for all installed monitoring agents,
a task that must be performed prior to starting the Summarization and Pruning Agent for
the first time.
To configure and start the
Summarization and Pruning Agent,
see the following procedures:
- If you are using Microsoft SQL Server for
the Tivoli Data Warehouse
database, perform the following additional steps:
- Enable authentication of user credentials (optional)
During
the installation and configuration of the monitoring server and portal
server, user validation was not enabled so any user can use the Tivoli Enterprise Portal client,
run tacmd commands, or issue SOAP server requests. If you want to
enable user authentication through either the portal server (for
LDAP authentication and single sign-on capability) or the monitoring server (for
LDAP or local operating system authentication). See Enabling user
authentication in the IBM Tivoli Monitoring Administrator's
Guide.
- Install and setup a dashboard environment (optional)
If you
want to install IBM Dashboard
Application Services Hub with monitoring dashboard applications or
custom dashboards, see Required software and memory requirements for a dashboard environment and
review the hardware and software requirements for Jazz™ for Service Management to determine if
it can be installed on the same computer as IBM Tivoli Monitoring,
or if you need to install it on a separate computer. After installing IBM Dashboard Application Services
Hub, see Installing and configuring the IBM Infrastructure Management Dashboards for Servers if you plan to use
that dashboard application. Also, if you enabled LDAP user authentication
through the portal server and you plan to use authorization policies
to control access to monitored resources in the dashboards, see Installing and configuring the Tivoli Authorization Policy Server and tivcmd Command-Line Interface for Authorization Policy.