tivoli tivoli monitoring sybase ase - ibm...
TRANSCRIPT
Tivoli® IBM Tivoli Monitoring for Databases: Sybase ASE
Installation and Setup Guide
Version 5.1.2
GC32-9135-00
���
Tivoli® IBM Tivoli Monitoring for Databases: Sybase ASE
Installation and Setup Guide
Version 5.1.2
GC32-9135-00
���
Note
Before using this information and the product it supports, read the information in Appendix H, “Notices,” on page 97.
First Edition (Oct. 2004)
This edition applies to this version of the product and to all subsequent releases and modifications until otherwise
indicated in new editions.
© Copyright International Business Machines Corporation 2004. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
Tables . . . . . . . . . . . . . . . v
About this guide . . . . . . . . . . vii
Who should read this guide . . . . . . . . . vii
What this guide contains . . . . . . . . . . vii
Publications . . . . . . . . . . . . . . viii
Accessibility . . . . . . . . . . . . . . x
Tivoli technical training . . . . . . . . . . . x
Support information . . . . . . . . . . . . x
Conventions used in this guide . . . . . . . . x
Chapter 1. Installation road map . . . . 1
Obtaining source files for installing IBM Tivoli
Monitoring for Databases: Sybase ASE . . . . . . 2
Chapter 2. Installing IBM Tivoli
Monitoring for Databases: Sybase ASE
in an existing Tivoli environment . . . . 5
Installing or upgrading IBM Tivoli Monitoring
Component Services . . . . . . . . . . . . 6
Using the command line to install the product . . . 9
Using the Tivoli desktop to install the product . . . 10
Using the Tivoli Software Installation Service to
install the product . . . . . . . . . . . . 12
Chapter 3. Completing the installation 15
Installing IBM Tivoli Language Support for this
product . . . . . . . . . . . . . . . . 15
Setting authorization roles . . . . . . . . . 18
Setting up the Java Runtime Environment . . . . 20
Enabling Sybase ASE for monitoring . . . . . . 23
Configuring the IBM Tivoli Enterprise Console
event server . . . . . . . . . . . . . . 24
Integrating with IBM Tivoli Business Systems
Manager . . . . . . . . . . . . . . . 26
Discovering resources to monitor . . . . . . . 29
Updating IBM Tivoli Monitoring Web Health
Console files . . . . . . . . . . . . . . 31
Enabling historical reporting of monitoring data . . 32
Chapter 4. Distributing resource
models . . . . . . . . . . . . . . . 37
Distributing resource models . . . . . . . . 37
Appendix A. Essential steps for a
command-line installation . . . . . . 39
Appendix B. System and software
requirements . . . . . . . . . . . . 41
Disk space requirements . . . . . . . . . . 41
Supported operating systems . . . . . . . . 41
Required software . . . . . . . . . . . . 42
Optional software . . . . . . . . . . . . 43
Appendix C. Tivoli basics . . . . . . . 47
Overview of the Tivoli environment . . . . . . 47
Accessing the Tivoli Management Framework
environment . . . . . . . . . . . . . . 52
Backing up Tivoli databases . . . . . . . . . 54
Appendix D. Task reference . . . . . . 57
Configure Event Server . . . . . . . . . . 58
Discover . . . . . . . . . . . . . . . 63
Appendix E. Uninstalling the product 69
Uninstalling IBM Tivoli Monitoring for Databases:
Sybase ASE . . . . . . . . . . . . . . 69
Uninstalling IBM Tivoli Monitoring Component
Services . . . . . . . . . . . . . . . 70
Uninstalling IBM Tivoli Monitoring for Databases:
Sybase ASE integration from IBM Tivoli Business
Systems Manager . . . . . . . . . . . . 71
Appendix F. Installing IBM Tivoli
Monitoring for Databases: Sybase ASE
and a complete Tivoli environment . . 73
Creating a hierarchy of files for the installation
utility to reference . . . . . . . . . . . . 74
Verifying the availability of remote execution
services . . . . . . . . . . . . . . . . 77
Completing installation planning sheets . . . . . 79
Using an installation utility to install the product
(for a new Tivoli environment only) . . . . . . 82
Manually creating a Windows proxy endpoint . . . 89
Appendix G. Support information . . . 93
Searching knowledge bases . . . . . . . . . 93
Obtaining fixes . . . . . . . . . . . . . 93
Contacting IBM Software Support . . . . . . . 94
Appendix H. Notices . . . . . . . . . 97
Trademarks . . . . . . . . . . . . . . 99
Index . . . . . . . . . . . . . . . 101
© Copyright IBM Corp. 2004 iii
iv IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Tables
1. Guidelines for installation and setup . . . . 1
2. Source files for installing IBM Tivoli Monitoring
for Databases: Sybase ASE . . . . . . . . 3
3. Guidelines for installing the product . . . . 5
4. Installation media and IND file locations . . . 6
5. Guidelines for completing the installation of
the product . . . . . . . . . . . . 15
6. Names of product index (.IND) files for
language support packages . . . . . . . 16
7. Disk space requirements for installing the
Tivoli environment . . . . . . . . . . 41
8. Platform support . . . . . . . . . . . 42
9. Required software for IBM Tivoli Monitoring
for Databases: Sybase ASE . . . . . . . 43
10. Optional software for IBM Tivoli Monitoring
for Databases: Sybase ASE . . . . . . . 44
11. Tivoli basics . . . . . . . . . . . . 47
12. Distribution of Tivoli software and monitored
applications in a Tivoli environment . . . . 48
13. Ways to invoke tasks . . . . . . . . . 57
14. Guidelines for installation of a complete Tivoli
environment . . . . . . . . . . . . 73
15. Download directories for an Evaluation or
Typical installation . . . . . . . . . . 75
16. Managed resources and their purpose . . . . 79
17. Planning sheet for creating managed nodes 80
18. Planning sheet for creating endpoints . . . . 81
19. Procedures for creating Windows endpoints 82
© Copyright IBM Corp. 2004 v
vi IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
About this guide
This guide describes how to install and set up IBM® Tivoli® Monitoring for
Databases: Sybase ASE to monitor and manage server resources and other objects
in a Tivoli environment.
Who should read this guide
This guide is for system administrators who want to install the product.
Readers should be familiar with the following topics:
v Tivoli management software
v Tivoli application software
v UNIX®–based operating systems
v Microsoft Windows® operating systems
v Tivoli Data Warehouse (optional)
v IBM Tivoli Enterprise Console (optional)
v IBM Tivoli Business Systems Manager (optional)
What this guide contains
This guide contains the following sections:
v Chapter 1, “Installation road map”
Provides an overview of installation tasks.
v Chapter 2, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an
existing Tivoli environment”
Describes how to install the product and a Tivoli environment across multiple
computers.
v Chapter 3, “Completing the installation”
Describes how to finalize and verify the installation of the product.
Note: “Enabling Sybase ASE for monitoring” on page 23 in this chapter
describes how to configure Sybase ASE so that IBM Tivoli Monitoring for
Databases: Sybase ASE can access the data to be monitored.
v Appendix A, “Essential steps for a command-line installation”
Summarizes the essential steps for installing IBM Tivoli Monitoring for
Databases: Sybase ASE. These steps start with upgrading IBM Tivoli Monitoring
and end with the deployment of resource models. The summary includes
appropriate examples for users who choose the command-line installation
option.
v Appendix B, “System and software requirements”
Lists the system requirements and software prerequisites for installing the
product.
v Appendix C, “Tivoli basics,” on page 47
Describes the basic parts of a Tivoli environment and provides procedures for
the basic operations in that environment.
v Appendix D, “Task reference”
© Copyright IBM Corp. 2004 vii
Provides detailed descriptions of Tivoli tasks that are related to installation.
v Appendix E, “Uninstalling the product”
Describes how to uninstall the product.
v Appendix F, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE and a
complete Tivoli environment”
Describes how to install the product with a complete Tivoli environment. This
option applies to computers on which no Tivoli software has been previously
installed.
v Appendix G, “Support information”
Describes options for obtaining support for IBM products.
v Appendix H, “Notices”
Provides information about copyrights and trademarks.
Publications
This section lists publications in the IBM Tivoli Monitoring for Databases: Sybase
ASE library and any other related documents. It also describes how to access
Tivoli® publications online, how to order Tivoli publications, and how to submit
comments on Tivoli publications.
IBM Tivoli Monitoring for Databases: Sybase ASE library
The IBM Tivoli Monitoring for Databases: Sybase ASE library contains the
following publications:
v IBM Tivoli Monitoring for Databases: Sybase ASE Installation and Setup Guide
Provides information about installing and setting up IBM Tivoli Monitoring for
Databases: Sybase ASE.
v IBM Tivoli Monitoring for Databases: Sybase ASE User’s Guide
Provides conceptual, procedural, and reference information about how to
monitor and manage resources with IBM Tivoli Monitoring for Databases:
Sybase ASE. This guide also provides troubleshooting information about the
various components of IBM Tivoli Monitoring for Databases: Sybase ASE, as
well as information about log files and informational, warning, and error
messages.
Prerequisite publications
To use the information in this book effectively, you must have some knowledge of
IBM Tivoli Monitoring, which you can get from the following books:
v IBM Tivoli Monitoring User’s Guide
Provides an overview of IBM Tivoli Monitoring, especially of resource models. It
also describes how to use the user interface.
v Tivoli Management Framework User’s Guide
Provides information about how to use the Tivoli graphical user interface (GUI)
Related publications
The following documents also provide useful information:
v Tivoli Enterprise™ Installation Guide
v Tivoli Management Framework Reference Manual
v IBM Tivoli Enterprise Console Adapters Guide
v IBM® Tivoli Enterprise Console® Event Integration Facility User’s Guide
viii IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v IBM Tivoli Enterprise Console Reference Manual
v IBM Tivoli Enterprise Console Rule Builder’s Guide
v IBM Tivoli Business Systems Manager product documentation
v IBM Tivoli Monitoring product documentation
v Installing and Configuring Tivoli Data Warehouse
v IBM Tivoli Monitoring Component Services, Version 5.1.3, Guide for Warehouse Pack,
Version 1.3.0.0, using Tivoli Data Warehouse 1.2
v Tivoli Data Warehouse product documentation
v IBM Tivoli Monitoring Resource Model Builder User’s Guide
The Tivoli Software Glossary includes definitions for many of the technical terms
related to Tivoli software. The Tivoli Software Glossary is available, in English only,
at http://publib.boulder.ibm.com/tividd/glossary/tivoliglossarymst.htm
Accessing publications online
The documentation CD contains the publications that are in the product library.
The format of the publications is PDF, HTML, or both.
IBM posts publications for this and all other Tivoli products, as they become
available and whenever they are updated, to the Tivoli software information center
Web site. Access the Tivoli software information center by first going to the Tivoli
software library at the following Web address:
http://www.ibm.com/software/tivoli/library/
Scroll down and click the Product manuals link. In the Tivoli Technical Product
Documents Alphabetical Listing window, click M to access all of the IBM Tivoli
Monitoring product manuals.
Note: If you print PDF documents on other than letter-sized paper, set the option
in the File → Print window that allows Adobe Reader to print letter-sized
pages on your local paper.
The IBM Software Support Web site provides the latest information about known
product limitations and workarounds in the form of technotes for your product.
You can view this information at the following Web site:
http://www.ibm.com/software/support
Ordering publications
You can order many Tivoli publications online at the following Web site:
http://www.elink.ibmlink.ibm.com/public/applications/
publications/cgibin/pbi.cgi
You can also order by telephone by calling one of these numbers:
v In the United States: 800-879-2755
v In Canada: 800-426-4968
In other countries, see the following Web site for a list of telephone numbers:
http://www.ibm.com/software/tivoli/order-lit/
About this guide ix
Accessibility
Accessibility features help users with a physical disability, such as restricted
mobility or limited vision, to use software products successfully. With this product,
you can use assistive technologies to hear and navigate the interface. You can also
use the keyboard instead of the mouse to operate most features of the graphical
user interface.
For additional information, see the Accessibility Appendix in the user’s guide for
this product.
Tivoli technical training
For Tivoli technical training information, refer to the following IBM Tivoli
Education Web site:
http://www.ibm.com/software/tivoli/education/
Support information
Appendix G, “Support information,” on page 93 describes the following options for
obtaining support for IBM products:
v “Searching knowledge bases” on page 93
v “Obtaining fixes” on page 93
v “Contacting IBM Software Support” on page 94
Conventions used in this guide
This guide uses several conventions for special terms and actions, and operating
system-dependent commands and paths.
Typeface conventions
This guide uses the following typeface conventions:
Bold
v Lowercase commands and mixed case commands that are otherwise
difficult to distinguish from surrounding text
v Interface controls (check boxes, push buttons, radio buttons, spin
buttons, fields, folders, icons, list boxes, items inside list boxes,
multicolumn lists, containers, menu choices, menu names, tabs, property
sheets), labels (such as Tip:, and Operating system considerations:)
v Keywords and parameters in text
Italic
v Words defined in text
v Emphasis of words (for example, ″Use the word that to introduce a
restrictive clause.″)
v New terms in text (except in a definition list)
v Variables and values you must provide
Monospace
v Code and other examples
v File names, programming keywords, and other elements that are difficult
to distinguish from surrounding text
x IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v Message text and prompts addressed to the user
v Text that the user must type
v Values for arguments or command options
Operating system-dependent variables and paths
The publications in this library use the UNIX® convention for specifying
environment variables and for directory notation.
When using the Windows® command line, replace $variable with %variable% for
environment variables and replace each forward slash (/) with a backslash (\) in
directory paths. The names of environment variables are not always the same in
Windows and UNIX. For example, %TEMP% in Windows is equivalent to $tmp in
UNIX.
Note: If you are using the bash shell on a Windows system, you can use the UNIX
conventions.
Tivoli command syntax
The following special characters define Tivoli command syntax:
[ ] Identifies elements that are optional. Required elements do not have
brackets around them.
... Indicates that you can specify multiple values for the previous element.
Separate multiple values by a space, unless otherwise directed by
command information.
If the ellipsis for an element follows a closing bracket, use the syntax
within the brackets to specify multiple values. For example, to specify two
administrators for the option [–a admin]..., use –a admin1 –a admin2.
If the ellipsis for an element is within the brackets, use the syntax of the
last element to specify multiple values. For example, to specify two hosts
for the option [–h host...], use –h host1 host2.
| Indicates mutually exclusive information. You can use the element on
either the left or right of the vertical bar.
{ } Delimits a set of mutually exclusive elements when a command requires
one of them. Brackets ([ ]) are around elements that are optional.
In addition to the special characters, Tivoli command syntax uses the typeface
conventions described in “Typeface conventions” on page x. The following
examples illustrate the typeface conventions used in Tivoli command syntax:
v wcrtpr [–a admin]... [–s region] [–m resource]... name
The name argument is the only required element for the wcrtpr command. The
brackets around the options indicate they are optional. The ellipsis after the –a
admin resource option means that you can specify multiple administrators
multiple times. The ellipsis after the –m resource option means that you can
specify multiple resources multiple times.v wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}
The –f, –i, and object elements are mutually exclusive. Braces that surround
elements indicate that you are including a required element. If you specify the
object argument, you can specify more than one object.
About this guide xi
xii IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Chapter 1. Installation road map
This installation road map lists the tasks you need to perform to install and set up
IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli
environment. It also tells where you can find the information and procedures that
guide you through the installation. See Appendix C, “Tivoli basics,” on page 47 for
descriptions of basic Tivoli concepts and operations.
Note: When you install the product and, in addition, a new Tivoli environment,
follow the road map that is provided with the following procedure:
Appendix F, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE
and a complete Tivoli environment,” on page 73.
Table 1. Guidelines for installation and setup
What you do Refer to
Prepare for installation
1. Obtain the installation software. “Obtaining source files for installing IBM Tivoli
Monitoring for Databases: Sybase ASE” on page 2
2. Back up the Tivoli environment. If you encounter a
problem during an installation, you can use the
backup to restore the environment to a known
working state.
“Backing up Tivoli databases” on page 54
3. Install the required prerequisite software.
Note: This chapter describes installation of the
product into an existing Tivoli environment. At a
minimum, this environment includes Tivoli
Management Framework, IBM Tivoli Monitoring,
and IBM Tivoli Monitoring Component Services.
“Required software” on page 42
4. Install the optional software that you want to use
with IBM Tivoli Monitoring for Databases: Sybase
ASE, for example, IBM Tivoli Enterprise Console
and IBM Tivoli Business Systems Manager.
“Optional software” on page 43
5. Install the latest maintenance software for the
operating systems on which you plan to install the
product.
Refer to the following Web sites for the latest maintenance
software:
v For the Solaris Operating Environment:
http://sunsolve.sun.com
v For IBM AIX:
http://techsupport.services.ibm.com/rs6k/ml.fixes.html
v For HP-UX:
http://www.hp.com/products1/unix/java/infolibrary/patches.html
Installation
© Copyright IBM Corp. 2004 1
Table 1. Guidelines for installation and setup (continued)
What you do Refer to
6. Install the product using one of the available
installation options. (See Appendix A, “Essential
steps for a command-line installation,” on page
39 for an overview of the entire installation
process.)
v When you install the product in an existing Tivoli
environment, perform one of the following procedures:
– “Using the command line to install the product” on
page 9
—OR—
– “Using the Tivoli desktop to install the product” on
page 10
—OR—
– “Using the Tivoli Software Installation Service to
install the product” on page 12
Note: This optional Tivoli product references a depot
of installation software, automatically checks and
resolves prerequisite software requirements on target
computers, and enables you to run parallel
installation processes.
v When you install the product and also a new Tivoli
environment, perform the following procedure: “Using
an installation utility to install the product (for a new
Tivoli environment only)” on page 82.
Complete installation
7. Complete installation of the product as follows:
v Enable Sybase ASE for monitoring
v Provide Java software to enable resource model
communications.
v (Optional) Send monitoring data to IBM Tivoli
Enterprise Console and IBM Tivoli Business
Systems Manager.
v Discover resources that are available to be
monitored.
v (Optional) Enable the product in languages in
addition to English.
v Verify that the Tivoli server and endpoints are
successfully installed.
Chapter 3, “Completing the installation,” on page 15
8. Verify the functionality of the Tivoli management
region.
“Discovering resources to monitor” on page 29
Obtaining source files for installing IBM Tivoli Monitoring for
Databases: Sybase ASE
To install IBM Tivoli Monitoring for Databases: Sybase ASE, you can use CDs or
use files that you download from the Web. This section lists the CDs or Web
download images that you need to install the product through the Tivoli command
line interface or the Tivoli desktop. You use the installation files to install the
product in an existing Tivoli environment, as described in Chapter 2, “Installing
IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli
environment,” on page 5. (Appendix F, “Installing IBM Tivoli Monitoring for
Databases: Sybase ASE and a complete Tivoli environment,” on page 73 describes a
way to install the product and also a complete Tivoli environment.)
2 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Table 2 lists required and optional groups of software for installation. You have
two options for obtaining the software:
v Pay a fee and receive the software on CDs.
v Download the software from the IBM Web site.
The installation files for IBM Tivoli Monitoring for Databases: Sybase ASE are
available for download from the IBM Passport Advantage Web site:
http://www-3.ibm.com/software/passportadvantage/
IBM Passport Advantage is an IBM licensing program for distributed software.
You can download installation files from Passport Advantage if you enroll in the
program. Upon enrolling, you are assigned a user name and password with
which to access the software files to which you are entitled.
The Passport Advantage Readme First lists the names of the required and optional
product images for installation. All product images for IBM Tivoli Monitoring
for Databases: Sybase ASE are contained in the e-assembly (eASSY) entitled IBM
Tivoli Monitoring for Databases: Sybase ASE on the Passport Advantage Web
site. An e-assembly is a grouping of product images (compressed files) that you
access on the Web by clicking the e-assembly title.
Table 2. Source files for installing IBM Tivoli Monitoring for Databases: Sybase ASE
Software Format Source files
Base Tivoli
software
(The language
support CD is
required only if you
want to install the
base Tivoli software
in a supported
language other than
English.)
CD
—OR—
v Tivoli Management Framework 1 of 2, Version 4.1.1
v Tivoli Management Framework 2 of 2, Version 4.1.1
v Tivoli Management Framework Language Support, Version 4.1.1
v IBM Tivoli Monitoring, Version 5.1.2
v IBM Tivoli Monitoring Language Support, Version 5.1.2
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
IBM Tivoli
Monitoring
Component
Services, 5.1.3
CD
—OR—
IBM Tivoli Monitoring for Databases, Version 5.1.2: Installation Disc 2 for
Sybase ASE
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
IBM Tivoli
Monitoring for
Databases: Sybase
ASE
CD
—OR—
v IBM Tivoli Monitoring for Databases: Sybase ASE, Version 5.1.2:
Installation Disc 1 for Sybase ASE
v IBM Tivoli Monitoring for Databases: Sybase ASE, Version 5.1.2:
Installation Disc 2 for Sybase ASE
These CDs include software used by the installation utility described in
“Using an installation utility to install the product (for a new Tivoli
environment only)” on page 82.
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
Chapter 1. Installation road map 3
Table 2. Source files for installing IBM Tivoli Monitoring for Databases: Sybase ASE (continued)
Software Format Source files
Component
software for IBM
Tivoli Monitoring
for Databases:
Sybase ASE
(The language
support CD is
required only if you
want to install the
base Tivoli software
in a supported
language other than
English.)
CD
—OR—
Sybase ASE:
v IBM Tivoli Monitoring for Databases, Version 5.1.2: Sybase ASE
Component Software
This CD includes software used to install the product as described in
Chapter 2, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE
in an existing Tivoli environment,” on page 5.
Note: The patches for Tivoli Management Framework, Version 4.1.1, are
located on the IBM Tivoli Monitoring for Databases: Sybase ASE, Version
5.1.2: Installation Disc 2 for Sybase ASE CD.
v IBM Tivoli Monitoring for Databases, Version 5.1.2: Sybase ASE Language
Support
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
Tivoli Data
Warehouse
You have the option
to install Tivoli Data
Warehouse to enable
historical reporting
of monitoring data.
CD
—OR—
You receive Tivoli Data Warehouse when you purchase other Tivoli
products. To enable Tivoli Data Warehouse to work with IBM Tivoli
Monitoring for Databases: Sybase ASE, you use the software from the
following CDs:
v IBM Tivoli Monitoring, Version 5.1.2
This CD includes the software for the warehouse pack (ETL1) provided
for IBM Tivoli Monitoring.
v IBM Tivoli Monitoring for Databases, Version 5.1.2: Installation Disc 2
for Sybase ASE
This CD contains IBM Tivoli Monitoring Component Services, 5.1.3. The
CD includes the software for the warehouse pack (ETL2) provided for
IBM Tivoli Monitoring for Databases: Sybase ASE.
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
IBM Tivoli
Monitoring Web
Health Console
This product is
optional.
CD
—OR—
v IBM Tivoli Monitoring Web Health Console for AIX/HP/SUN, Version
5.1.1
v IBM Tivoli Monitoring Web Health Console for Windows/Linux, Version
5.1.1
v IBM Tivoli Monitoring Web Health Console 5.1.1 Fix Pack 6
Web download See the Passport Advantage Readme First for a list of files to download. The
list provides the name of a Web download file that is equivalent to each
installation CD.
IBM Tivoli
Monitoring
Resource Model
Builder
Web download
only
The software enables advanced users to create custom resource models and
is available at http://www-3.ibm.com/software/tivoli/resource-center/availability/code-monitor-resource.jsp
4 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Chapter 2. Installing IBM Tivoli Monitoring for Databases:
Sybase ASE in an existing Tivoli environment
This chapter describes how to install IBM Tivoli Monitoring for Databases: Sybase
ASE in an existing Tivoli environment. See Chapter 1, “Installation road map,” on
page 1 for a comprehensive overview of installation.
Table 3. Guidelines for installing the product
Goal Refer to
1. Verify that the systems on which you want to install the
product comply with system requirements.
Note: You can use the wlsinst Tivoli command to obtain a list
of software that is installed in the Tivoli environment, as in the
following example output:
wlsinst -a
*-----------------------------------------------------*
Product List
*-----------------------------------------------------*
Tivoli Management Framework 4.1.1
IBM Tivoli Monitoring Component Services, Version 5.1.3
IBM Tivoli Monitoring, Version 5.1.2
Compare the list generated for your system to the requirements
listed in “Required software” on page 42.
Appendix B, “System and software requirements,”
on page 41
“Installing or upgrading IBM Tivoli Monitoring
Component Services” on page 6
(To install the product and also a complete Tivoli
environment, see Appendix F, “Installing IBM
Tivoli Monitoring for Databases: Sybase ASE and a
complete Tivoli environment,” on page 73.)
2. Install the product in an existing Tivoli environment using
one of the available installation options.
“Using the command line to install the product”
on page 9
—OR—
“Using the Tivoli desktop to install the product”
on page 10
—OR—
“Using the Tivoli Software Installation Service to
install the product” on page 12 *
* Tivoli Software Installation Service is an optional product. The product references a depot of installation software,
automatically checks and resolves prerequisite software requirements on target computers, and enables you to run
parallel installation processes.
Note: To perform procedures in the Tivoli desktop or command-line interface, you
access the Tivoli environment as described in “Accessing the Tivoli
Management Framework environment” on page 52.
Installing the product in interconnected Tivoli regions:
v The IBM Tivoli Monitoring for Databases: Sybase ASE objects are not qualified
by region name. Object labels, a domain name for example, must be unique
across all interconnected Tivoli regions.
v The Discover task locates instances of Sybase ASE, called objects, that are located
within a Tivoli management region. The managed node on which you run the
task, the managed node on which you create the object, and the computer where
Sybase ASE runs must all be in one Tivoli management region. After you
© Copyright IBM Corp. 2004 5
discover and create the object in its local Tivoli management region, you can
manage it from other Tivoli management regions.
v IBM Tivoli Monitoring for Databases: Sybase ASE provides the following
support for interconnected Tivoli regions.
– Regions interconnected, IBM Tivoli Monitoring for Databases: Sybase ASE not
installed in either region. You can install the product in one or both regions.
– Regions not interconnected, IBM Tivoli Monitoring for Databases: Sybase ASE
not installed in either region. You can install the product in both regions, then
you can interconnect them.
– Regions not interconnected, IBM Tivoli Monitoring for Databases: Sybase ASE
installed in one region. You can interconnect the Tivoli regions and install the
product in the second region.
Installing or upgrading IBM Tivoli Monitoring Component Services
Objective
To install or upgrade IBM Tivoli Monitoring Component Services to provide Tivoli
system features that enable IBM Tivoli Monitoring for Databases: Sybase ASE.
Background information
IBM Tivoli Monitoring Component Services is a required prerequisite for all
specialized IBM Tivoli Monitoring software, for example, IBM Tivoli Monitoring
for Databases or IBM Tivoli Monitoring for Messaging and Collaboration. IBM
Tivoli Monitoring Component Services is a prerequisite for IBM Tivoli Monitoring
for Databases: Sybase ASE.
Table 4 shows the media title (CD or equivalent Web download image) for
upgrades and installation images. The table includes the name of the installation
index (.IND) files that you must use in this procedure.
Table 4. Installation media and IND file locations
Goal Installation media * IND file name and location
Upgrade to IBM Tivoli Monitoring
Component Services, 5.1.3
IBM Tivoli Monitoring for Databases,
Version 5.1.2: Installation Disc 2 for
Sybase ASE
/ITMCS/CS513P
Install IBM Tivoli Monitoring
Component Services, 5.1.3
/ITMCS/CMPTSVCS
* The Installation media column lists a CD title. The equivalent Web download images has a similar title. The
product images for the software listed in this table are contained in the e-assembly (eASSY) entitled IBM Tivoli
Monitoring for Databases eASSY V5.2.1 MultiOS.
Required authorization role
install_product
Before you begin
v Obtain the installation media (CD or equivalent Web download image) for the
software you want to install. See “Obtaining source files for installing IBM Tivoli
Monitoring for Databases: Sybase ASE” on page 2.
v Back up the Tivoli management region as described in“Backing up Tivoli
databases” on page 54.
v Prepare a list of all managed nodes on which to install the software. To display a
list of all installed Tivoli software by managed node, run the wlsinst -ah
command from the Tivoli command line.
6 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
– If no version of IBM Tivoli Monitoring Component Services is listed, install
the services as described in this procedure
– If a version that is older than 5.1.3 is listed, install the upgrade as described
in this procedure.v Start the Tivoli environment for the installation method (command-line interface
or Tivoli desktop) that you plan to use, as described in “Accessing the Tivoli
Management Framework environment” on page 52.
v Ensure that all managed nodes are running and communicating with the Tivoli
server.
When you finish
As a precautionary measure, back up the Tivoli management region databases as
described in “Backing up Tivoli databases” on page 54. Use a unique name for the
new backup files.
Procedure
You can perform this procedure from either the command line or the Tivoli
desktop.
Command line: Before you run the installation command, prepare a list of all
managed nodes on which to install the IBM Tivoli Monitoring Component
Services. To display a list of all installed Tivoli software by managed node, run the
wlsinst -ah command from the Tivoli command line.
v If a version that is older than 5.1.3 is listed, use wpatch to install a software
upgrade.
v If no version of IBM Tivoli Monitoring Component Services is listed, use
winstall to install a new instance of the software.
Use the appropriate command for upgrading or installing:
v For upgrading an existing instance of the software:
wpatch -c source_dir -i IND_file_name [-y]
v For installing a new instance of the software:
winstall -c source_dir [-s server] -i IND_file_name [-y]
where:
-c source_dir
Specifies the complete path to the directory containing the installation
image.
-i IND_file_name
Specifies the name of the IND file. See Background information for a list of
.IND file names.
-s server
(Only valid for the winstall command.) Specifies the name of the managed
node to use as the installation server. By default, the server on which you
are installing the software becomes the Tivoli server.
-y Installs the software without requesting confirmation.
Refer to the Tivoli Management Framework Reference Manual for more information
about the winstall command. Refer to “Tivoli command syntax” on page xi for
information about Tivoli command-line syntax.
The following example installs IBM Tivoli Monitoring Component Services from a
CD located in the ″D″ drive of a Tivoli server that is running on Windows:
Chapter 2. Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli environment 7
winstall -c D:\ITMCS -i CMPTSVCS -y
This command installs the software on the Tivoli management region and on
managed nodes. The ″.IND″ suffix is not required when you specify the name of
the installation index file.
Tivoli desktop:
1. Prepare a list of all managed nodes on which to install the IBM Tivoli
Monitoring Component Services. To display a list of all installed Tivoli software
by managed node, run the wlsinst -ah command from the Tivoli command
line.
v If no version of IBM Tivoli Monitoring Component Services is listed, go to
Step 2.
v If a version that is older than 5.1.3 is listed, go to Step 3.2. Install a new instance of IBM Tivoli Monitoring Component Services as follows:
a. Select Install from the Desktop menu.
b. Select Install Product in the menu to display the Install Product window.
c. Click Select Media to display the File Browser window.
d. In the Path Name text field, type the full path to the .IND file (CMPTSVCS).
Use backward slashes (\) for Windows path names instead of forward
slashes (/). See Table 4 on page 6 for the directory location and name of the
IND file.
e. Click Set Path. The File Browser window displays the contents of the
specified media in the Files scrolling list.
f. Click Set Media & Close.
The Install Product window reopens.
g. Select IBM Tivoli Monitoring Component Services, 5.1.3 from the Select
Product to Install scrolling list.
h. Select the managed nodes on which to install the software from the
Available Clients list.
i. Click the right arrow to move the selected clients to the Clients to Install
On list.
j. Click Install to display the Product Install window and a list of pending
installation actions.
k. Click Continue Install to begin the installation process.
Additional Information: The Product Install window displays the progress of
the installation. View the messages in the task output window to determine
whether the product installation was successful.
l. Click Close to close the Product Install window.
m. Select Refresh from the View menu bar. The desktop displays the icon for
the product you installed.3. Upgrade an existing instance of as IBM Tivoli Monitoring Component Services
follows:
a. Select Install from the Desktop menu.
b. Select Install Patch.
c. If necessary, click OK to bypass a harmless error message about the media
settings.
d. Click Select Media to display the File Browser window.
8 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
e. In the Path Name text field, type the full path to the .IND file (CS513P). Use
backward slashes (\) for Windows path names instead of forward slashes
(/). See Table 4 on page 6 for the directory location and name of the IND
file.
f. Click Set Path. The File Browser window displays the contents of the
specified media in the Files scrolling list.
g. Click Set Media & Close.
h. Select IBM Tivoli Monitoring Component Services, Upgrade to Version
5.1.3 from the Select Patch to Install scrolling list in the Install Patch
window.
i. Select the target clients on which to install the software from the Available
Clients scrolling list.
j. Click the right arrow to move the selected clients to the Clients to Install
On scrolling list.
k. Click Install to display the Patch Install window and a list of pending
installation actions.
l. Click Continue Install to begin the installation process.
Additional Information: The Patch Install window displays the progress of the
installation. View the messages in the task output window to determine
whether the patch installation was successful.
m. Click Close to close the Patch Install window.
Using the command line to install the product
Objective
To use the winstall command to install IBM Tivoli Monitoring for Databases:
Sybase ASE in an existing Tivoli environment, so that you can monitor the
performance and availability of Sybase ASE.
Background information
A Tivoli environment includes the following components:
v Tivoli Management Framework
v IBM Tivoli Monitoring
v IBM Tivoli Monitoring Component Services
Note: Appendix B, “System and software requirements,” on page 41 describes all
required and optional software and the supported versions of that software.(To install the product and also a complete Tivoli environment, see Appendix F,
“Installing IBM Tivoli Monitoring for Databases: Sybase ASE and a complete Tivoli
environment,” on page 73.)
Required authorization
Requires install_product or senior in the Tivoli region
Before you begin
v Obtain the installation software as described in “Obtaining source files for
installing IBM Tivoli Monitoring for Databases: Sybase ASE” on page 2.
v Back up the Tivoli environment as described in “Backing up Tivoli databases”
on page 54. If you encounter a problem during an installation, use the backup to
restore the environment to a known working state.
Chapter 2. Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli environment 9
v Determine the managed nodes on which to install the product. The product
should be installed on the Tivoli management region server managed node, all
gateways, and the server managed node for IBM Tivoli Enterprise Console.
v Ensure that all managed nodes are running and communicating with the Tivoli
server.
When you finish
Complete the activities described in Chapter 3, “Completing the installation,” on
page 15.
Procedure
Access the Tivoli environment as described in “Accessing the Tivoli Management
Framework environment” on page 52.
Run the following command from the command prompt:
winstall -c source_dir [-s server] -i IND_file [-y]
where:
-c source_dir
Specifies the complete path to the directory containing the installation
image. This directory contains the Tivoli installation index (.IND) file and
packet (.PKT) files that are required for installation.
-s server
Specifies the name of the managed node to use as the installation server.
By default, the installation server is the Tivoli management region server.
-i IND_file
Specifies IXB512, the name of the Tivoli installation index (.IND) file.
-y Installs the product without requesting confirmation.
The following example shows a typical installation command:
For example, to install IBM Tivoli Monitoring for Databases: Sybase ASE on all of
the managed nodes in the region when the image is in
/usr/images/Tivoli/SybaseMon, run this command:
winstall -c /usr/images/Tivoli/SybaseMon -i IXB512 -y
(The ″.IND″ suffix is not required when you specific the name of the installation
index file.)
Refer to the Tivoli Management Framework Reference Manual for more information
about the winstall command. Refer to “Tivoli command syntax” on page xi for
information about Tivoli command-line syntax.
Using the Tivoli desktop to install the product
Objective
To use the Tivoli desktop to install IBM Tivoli Monitoring for Databases: Sybase
ASE in an existing Tivoli environment so that you can monitor the performance
and availability of Sybase ASE.
Background information
A Tivoli environment includes the following components:
v Tivoli Management Framework
10 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v IBM Tivoli Monitoring
v IBM Tivoli Monitoring Component Services
Note: Appendix B, “System and software requirements,” on page 41 describes all
required and optional software and the supported versions of that software.(To install the product and also a complete Tivoli environment, see Appendix F,
“Installing IBM Tivoli Monitoring for Databases: Sybase ASE and a complete Tivoli
environment,” on page 73.)
Required authorization
Requires install_product or senior in the Tivoli region
Before you begin
v Obtain the installation software as described in “Obtaining source files for
installing IBM Tivoli Monitoring for Databases: Sybase ASE” on page 2.
v Back up the Tivoli environment as described in “Backing up Tivoli databases”
on page 54. If you encounter a problem during an installation, use the backup to
restore the environment to a known working state.
v Determine the managed nodes on which to install the product. The product
should be installed on the Tivoli management region server managed node, all
gateways, and the server managed node for IBM Tivoli Enterprise Console.
v Ensure that all managed nodes are running and communicating with the Tivoli
server.
When you finish
v Complete the activities described in Chapter 3, “Completing the installation,” on
page 15.
v Deploy resource models as described in Chapter 4, “Distributing resource
models,” on page 37.
Note: See the IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide for
additional configuration options for resource models.
Procedure
1. Access the Tivoli environment as described in “Accessing the Tivoli
Management Framework environment” on page 52.
2. Select Install from the Desktop menu.
3. Select Install Product in the menu to display the Install Product window.
4. Click Select Media to display the File Browser window.
5. In the Path Name text field, type the full path to the .IND file (IXB512) for the
software that you are installing. Use backward slashes (\) for Windows path
names instead of forward slashes (/).
6. Click Set Path. The File Browser window displays the contents of the
specified media in the Files scrolling list.
7. Click Set Media & Close.
The Install Product window reopens.
8. Select IBM Tivoli Monitoring for Databases: Sybase ASE, 5.1.2 from the
Select Product to Install scrolling list.
9. Select the managed nodes on which to install the software from the Available
Clients list.
10. Click the right arrow to move the selected clients to the Clients to Install On
list.
Chapter 2. Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli environment 11
11. Click Install to display the Product Install window and a list of pending
installation actions.
12. Click Continue Install to begin the installation process.
Additional Information: The Product Install window displays the progress of the
installation. View the messages in the task output window to determine
whether the product installation was successful.
13. Click Close to close the Product Install window.
14. Select Refresh from the View menu bar. The desktop displays the icon for the
product you installed.
Using the Tivoli Software Installation Service to install the product
Objective
To use the Tivoli Software Installation Service to install IBM Tivoli Monitoring for
Databases: Sybase ASE in an existing Tivoli environment, so that you can monitor
the performance and availability of Sybase ASE.
Background information
An optional product, the Tivoli Software Installation Service (SIS), can install
multiple Tivoli products on multiple systems in parallel. This Java-based product
can install more products on more systems in less time than the Tivoli
Management Framework’s installation facility. Tivoli Software Installation Service
performs product prerequisite checks and, if defined, user-specified prerequisite
checks to avoid or eliminate installation failure. In most cases, failures occur only
when machines are turned off or removed from the network.
Tivoli Software Installation Service also creates an installation repository into which
you can import the installation image of one or more Tivoli products. You can
import only the interpreter types you require in your environment, which saves
disk space and import time. The installation repository is then the source of all
your Tivoli installations. You can even share a single installation repository across
multiple Tivoli management regions.
For details of the platforms on which the Tivoli Software Installation Service can
run and for instructions on installing and using the product, see the Tivoli Software
Installation Service User’s Guide and the release notes for that product.
A Tivoli environment includes the following components:
v Tivoli Management Framework
v IBM Tivoli Monitoring
v IBM Tivoli Monitoring Component Services
Note: Appendix B, “System and software requirements,” on page 41 describes all
required and optional software and the supported versions of that software.(To install the product and also a complete Tivoli environment, see Appendix F,
“Installing IBM Tivoli Monitoring for Databases: Sybase ASE and a complete Tivoli
environment,” on page 73.)
Required authorization
Requires install_product or senior in the Tivoli region
12 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Before you begin
v Back up the Tivoli environment as described in “Backing up Tivoli databases”
on page 54. If you encounter a problem during an installation, use the backup to
restore the environment to a known working state.
v Obtain the installation software as described in “Obtaining source files for
installing IBM Tivoli Monitoring for Databases: Sybase ASE” on page 2.
When you finish
v Complete the activities described in Chapter 3, “Completing the installation,” on
page 15.
v Deploy resource models as described in Chapter 4, “Distributing resource
models,” on page 37.
Note: See the IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide for
additional configuration options for resource models.
Procedure
This section describes the overall process for using Tivoli Software Installation
Service. See TME 10 Software Installation Service User’s Guide for detailed
descriptions and instructions.
Command line: Use the following command to import a response file and install
products and machines:
wsis response_file
where response_file is the name of the response file you want to import. See TME 10
Software Installation Service User’s Guide for descriptions and examples of response
files.
Tivoli Software Installation Service parses the response file, contacts computers
specified in the file, sets product attributes, and adds this configuration
information to the Install Repository (IR) directory. It then automatically begins an
installation based on the given machine and product attributes. Status from the
installation is sent to standard output and standard error, and HTML log files are
generated in the IR directory.
Tivoli desktop:
1. Install Tivoli Software Installation Service as described in the user’s guide for
that product. Installation includes creation of an Install Repository where you
can store software images to be installed.
2. Access the Tivoli environment as described in “Accessing the Tivoli
Management Framework environment” on page 52.
3. Start Tivoli Software Installation Service.
4. Import the products or patches you want to install into the Install Repository.
5. Select the products and patches to be installed.
6. Select a managed node or PC managed node from the Select Machine window.
Follow the steps to create a managed node if none exists.
7. Specify the installation options you require.
8. Click the Install button and specify the method of installation from the Select
Installation Mechanism window.
Chapter 2. Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli environment 13
14 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Chapter 3. Completing the installation
This section describes how to verify the installation and enable functionality for
IBM Tivoli Monitoring for Databases: Sybase ASE.
Table 5. Guidelines for completing the installation of the product
Goal Refer to
(Optional) Install language support packages so that you
can use the product in languages other than English.
“Installing IBM Tivoli Language Support for this
product” on page 15
Assign authorization roles required to use the product to
manage and monitor applications.
“Setting authorization roles” on page 18
Set up the Java Runtime Environment. “Setting up the Java Runtime Environment” on page 20
Enable Sybase ASE for monitoring. “Enabling Sybase ASE for monitoring” on page 23
(Optional) Enable the IBM Tivoli Enterprise Console
server to receive and display events from IBM Tivoli
Monitoring for Databases: Sybase ASE
“Configuring the IBM Tivoli Enterprise Console event
server” on page 24
(Optional) Enable IBM Tivoli Business Systems Manager
to receive and display events from IBM Tivoli Monitoring
for Databases: Sybase ASE
“Integrating with IBM Tivoli Business Systems Manager”
on page 26
Discover resources to monitor. “Discovering resources to monitor” on page 29
(Optional) Update the optional Web Health Console. “Updating IBM Tivoli Monitoring Web Health Console
files” on page 31
(Optional) Enable historical reporting in Tivoli Data
Warehouse.
“Enabling historical reporting of monitoring data” on
page 32
Installing IBM Tivoli Language Support for this product
Objective
To install language support packages for the product so that you can use the
product in languages other than English.
Background information
By default, IBM Tivoli Monitoring for Databases: Sybase ASE is enabled in English.
This procedure describes how to enable additional languages after you install the
product. If you used the installation utility to install the product, perform this
procedure to add any languages that you did not select during installation.
To add a language, you must install a language support package (also called a
language pack). Each product component has its own set of language packs, one for
each supported language. The language packs for each product component are
available on the language support CD (or equivalent Web download image) for
that component.
Language packs are contained in product index files (.IND files). During
installation, you must specify the names of the .IND files for the language packs
that you want to install. Table 6 on page 16 lists the supported languages and the
names of the .IND files for each product component. The file names are listed
without the .IND extension. When you install a language pack, you must specify
© Copyright IBM Corp. 2004 15
the full file name, including the extension. The IND files are located in the /cdrom
directory on the language support CDs or equivalent Web download images.
Table 6. Names of product index (.IND) files for language support packages
Language Component name
Brazilian Portuguese IXB_PTBR
Chinese (simplified) IXB_ZHCH
Chinese (traditional) IXB_ZHTW
French IXB_FR
German IXB_DE
Italian IXB_IT
Japanese IXB_JA
Korean IXB_KO
Spanish IXB_ES
Some command-line and keyword options are not translated in the language
support packages. This approach avoids any programming complexities for scripts
that can run under multiple locales. Run the scripts under the locale in which the
retrieved data is stored.
The Tivoli Enterprise Installation Guide and the Tivoli Management Framework Release
Notes provide more information about the role of language packs in Tivoli
products. These documents are available on the Tivoli Management Framework
Version 4.1.1 Documentation CD or equivalent Web download image.
Required authorization role
Requires install_product or senior in the Tivoli environment
Before you begin
v You must install language support for the base product, IBM Tivoli Monitoring,
as described in the documentation for that product. You can install one or more
language support packages for IBM Tivoli Monitoring for Databases: Sybase
ASE.
v As a precautionary measure, back up the Tivoli management region as described
in “Backing up Tivoli databases” on page 54.
v Prepare a list of managed nodes on which the product is installed. The list must
include all gateways.
v Ensure that the language support CDs or Web download images are accessible
to the Tivoli server from which you will perform the procedure. Each CD or
Web download image has the name of the product component and the words
Language Support in the title. For example, the language packs for the base
product, IBM Tivoli Monitoring, are located on the CD or equivalent Web
download image.
When you finish
Verify that the Tivoli environment reflects the language option that you installed.
16 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
Command line
1. Access the Tivoli command line as described in “Accessing the Tivoli
Management Framework environment” on page 52.
2. Repeat the following steps for each language pack that you want to install:
a. If you are installing from CDs, insert the language support CD that contains
the language pack you are installing.
b. Run the following command:
winstall -c source_dir -i IND_file_name –y
where:
source_dir is the full directory path to the location of the .IND files. The
full directory path on the language support CDs (or equivalent Web
download images) is /cdrom. Use backward slashes (\) for Windows
path names instead of forward slashes (/).
IND_file_name is the name of the .IND file that contains the language
support package that you want to install. For example, IXB_ES.IND
contains the Spanish language support package for this product. See
“Installing IBM Tivoli Language Support for this product” on page 15
for a list of IND file names for each product component.
Additional information: When the command completes, the message Finished
Product Installation is displayed.
Refer to the Tivoli Management Framework Reference Manual for more information
about the winstall command. Refer to “Tivoli command syntax” on page xi for
information about Tivoli command-line syntax.
Tivoli desktop
1. Access the Tivoli desktop as described in “Accessing the Tivoli Management
Framework environment” on page 52.
2. If you are installing from CDs, insert the language support CD that contains
the language pack you are installing.
3. Click Install in the Desktop menu.
4. Click Install Product.
5. Click Select Media to open the File Browser window.
6. In the Path Name text field, type the full directory path to the location of the
.IND files. The full directory path on the language support CDs (or equivalent
Web download images) is /cdrom. Use backward slashes (\) for Windows
path names instead of forward slashes (/).
7. Click Set Path to refresh the view.
Additional information: The Files list displays the .IND files included on this
language support CD or Web download image.
8. Click Set Media & Close to return to the Install Product window.
9. Select the language that you want to install in the Select Product to Install
list.
Chapter 3. Completing the installation 17
10. Select the target clients on which to install the language pack from the
Available Clients list.
11. Click the right arrow to move the selected clients to the Clients to Install On
list.
12. Click Install & Close to start the installation progress window.
13. Click Continue Install when the prompt is displayed.
14. Click Close when the ″Finished Product Installation message″ is displayed.
15. Repeat these steps to install another language support package.
Setting authorization roles
Objective
To assign IBM Tivoli Monitoring for Databases: Sybase ASE authorization roles for
managing resources to administrators and users.
Background information
When you install IBM Tivoli Monitoring for Databases: Sybase ASE, the following
roles are created:
v SybaseMon_IXB_user
v SybaseMon_IXB_admin
v SybaseMon_IXB_senior
v SybaseMon_IXB_super
All tasks require that you assign at least one of these authorization roles to the
Tivoli administrator who is running the task. In addition, some tasks require Tivoli
authorizations that pertain to the Tivoli management region. To run tasks and
processes, the Tivoli administrator must have the required Tivoli authority and
must be assigned one of IBM Tivoli Monitoring for Databases: Sybase ASE
authorization roles. You can assign IBM Tivoli Monitoring for Databases: Sybase
ASE authorization as Tivoli management region roles or as resource roles,
depending on local authorization requirements.
Be sure to account for the scope of the roles that you assign. For example, you can
enable a role for a specific policy region or you can enable a role for the entire
Tivoli management region, depending on the security protocols, division of labor,
or other factors in your business infrastructure.
Required authorization role
super
Before you begin
Before setting authorization roles, you must have installed IBM Tivoli Monitoring
for Databases: Sybase ASE.
When you finish
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
18 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Procedure
You can perform this procedure from the command line or the Tivoli desktop.
Command line
Use the wsetadmin command to set or change resource authorization roles. The
roles you grant can apply globally in the Tivoli environment or locally to a specific
policy region, as shown in the following examples:
v Setting authorization roles for the product globally: In this example, a Tivoli
administrator PACAdmin is assumed to exist, and the user has the user and
admin roles for the Tivoli environment:
wsetadmin -r global,user:admin:SybaseMon_IXB_user:SybaseMon_IXB_super PACAdmin
Any or all of the IBM Tivoli Monitoring for Databases: Sybase ASE roles may be
included in this list.
v Setting authorization roles for the product locally, in the ″PAC_Region″ policy
region: In this example, a Tivoli administrator PACAdmin is assumed to exist,
and the user has the user and admin roles in the ″PAC_Region″ policy region.
Also, the policy region is assumed to include a managed resource for IBM Tivoli
Monitoring for Databases: Sybase ASE:
wsetadmin -r @PolicyRegion:PAC_Region,user:admin:SybaseMon_IXB_user:\
SybaseMon_IXB_super PACAdmin
Any or all of the IBM Tivoli Monitoring for Databases: Sybase ASE roles may be
included in this list.
See the Tivoli Management Framework Reference Manual for more information on
wsetadmin.
Tivoli desktop
Follow these steps to perform this procedure from the Tivoli desktop:
1. Double-click Administrators.
2. Right-click the administrator whose role you want to modify.
3. Click Edit TMR Roles to access the Set TMR Roles window.
4. Add or remove roles for the selected resources as follows:
v To add roles for the selected resources, select one or more roles from those
shown in the Available Roles list and click the left-arrow button to move the
role to the Current Roles list. You can also double-click an entry in the
Available Roles list to move it to the Current Roles list.
v To remove roles for the selected resources, select one or more roles from
those shown in the Current Roles list and click the right-arrow button to
move the role to the Available Roles list. You can also double-click an entry
in the Current Roles list to move it to the Available Roles list.
Note: The list of roles might include others not mentioned here, depending on
the particular applications installed.
5. Click Change & Close or Change to add and remove the selected roles and
save your changes.
The administrator must restart the Tivoli desktop before this change takes effect.
Chapter 3. Completing the installation 19
Setting up the Java Runtime Environment
IBM Tivoli Monitoring requires a Java Runtime Environment (JRE) on the
endpoint. You set up the JRE as described in “Installing and linking to the Java
Runtime Environment” or “Linking to an existing Java Runtime Environment” on
page 22.
Installing and linking to the Java Runtime Environment
Objective
To install the Java Runtime Environment (JRE) on endpoints and link the endpoint
software to the JRE so that users can run resource models that have Java providers.
Background information
A supported version of the Java Runtime Environment (JRE) must be installed on
endpoint systems that run resource models with Java providers. The endpoint
software must be linked to the JRE before the resource models can run.
This procedure uses a Tivoli command (wdmdistrib) that installs and links the JRE
in one step. When you type the command, you specify the endpoints on which
you want to install and link the JRE. Do not specify,
v Endpoints on which a supported version of the JRE is already installed.
Endpoints other than Solaris require Version 1.3.0 or 1.3.1. Solaris endpoints
require Version 1.3.1_08. If a supported version of the JRE is already installed,
you must link the endpoint software to the JRE using a separate procedure. See
“Linking to an existing Java Runtime Environment” on page 22.
v Endpoints that run the HP-UX operating system.
Install the HP-UX Runtime Environment for Java 2 Version 1.3.1 on each
endpoint locally as a separate step. Then link the endpoint software to the JRE
as described in “Linking to an existing Java Runtime Environment” on page 22.
Obtain the HP-UX JRE from the following Web address and follow the
installation instructions provided there:
http://www.hp.com/products1/unix/java/java2/sdkrte1_3/downloads/index.html
You must perform this procedure using the compressed IBM JRE files provided on
the IBM Tivoli Monitoring Tools CD for (or its equivalent Web download image). Do
not uncompress the files.
Note: IBM Tivoli Monitoring does not support JRE 1.4.
Required authorization role
admin, senior, or super
Before you begin
v Prepare a list of names of endpoints that meet the criteria described in the
Background information section.
v The directory from which the JREs are distributed must be on the local file
system of the Tivoli server (not a managed node). The JREs are located in the
following directory on the IBM Tivoli Monitoring Tools CD for (or the equivalent
Web download image):
/tools/jre/platform
where platform is one of the following directories:
– aix4-rl contains JRE files for supported AIX systems
20 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
– linux-ix86 contains JRE files for supported Linux Intel systems
– linx-s390 contains JRE files for supported Linux zSeries systems
– solaris2 contains JRE files for Solaris systems
– w32-ix86 contains JRE files for supported Windows systems
Copy the platform directories and their contents to the local file system of the
Tivoli server.
v Access the Tivoli command line as described in “Accessing the Tivoli
Management Framework environment” on page 52.
When you finish
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
You must perform this procedure from the command line.
Command line: Run the following command to install and distribute the JRE to
specified endpoints and link the endpoint software to the JRE:
wdmdistrib –J "JRE_location_dir" –l subscriber... [-r]
where
JRE_location_dir
Specifies the directory path to the compressed JRE files, up to but not
including the platform directory. Enclose the path in quotation marks.
Additional Information: The JRE files for each platform must be copied from
the Tools CD for IBM Tivoli Monitoring (or the equivalent Web download
image) to the local file system of the Tivoli server. See the Before you begin
section for information.
-l Specifies the subscriber name. If specified, the parameter allows the
distribution to be targeted also to resources which are not subscribed to the
profile manager to which the profile belongs. This option is ignored when
no subscribers are specified. Option -J must be specified in conjunction
with -l if no profile name is indicated.
-r Indicates that the JRE must be replaced on the target subscribers. This
option has effect only if used in conjunction with the –J option. By default
(when you do not use the -r flag), wdmdistrib and the -J flag cause
installation of the JRE only to subscribers that have no installation of the
JRE or no link to the JRE.
subscriber...
Specifies the names of the endpoints to which you want to distribute the
software. Space between each endpoint name.
Additional information: The following example installs JREs to endpoints named
matrix25-lcf and aix4-lcf:
wdmdistrib -J "/tools/jre" -r -l matrix25-lcf aix4-lcf
See the IBM Tivoli Monitoring User’s Guide for more information about the
wdmdistrib command.
Chapter 3. Completing the installation 21
Linking to an existing Java Runtime Environment
Objective
To link the endpoint software to an existing Java Runtime Environment (JRE) on
endpoint systems that run resource models that use Java providers.
Background information
This procedure describes how to run the Tivoli DMLinkJre task against endpoints
that have the required version of the Java Runtime Environment (Version 1.3.0 or
1.3.1, and Version 1.3.1_08 on Solaris) already installed. This task enables the
endpoint software to identify the correct path to the JRE.
Note: If the setup of the link to an existing JRE fails for any reason, try installing
and using the JRE that IBM Tivoli Monitoring provides, as described in
“Installing and linking to the Java Runtime Environment” on page 20.
You do not need to run the DMLinkJre task against the endpoints where you used
the wdmdistrib command to install and link the JRE in one step, which is the
option that is described in “Installing and linking to the Java Runtime
Environment” on page 20.
Required authorization role
admin, itm_tasks, senior, or super
Before you begin
v Prepare a list of names of endpoints that meet the criteria described in the
Background information section.
v Check the installation path of the JRE on each endpoint. When you run the
DMLinkJre task against a group of endpoints, the JRE installation path, up to the
bin directory, must be identical on all endpoints in the group.
v On endpoints with an HP-UX operating system, install the following HP-UX
patch bundles to enable Java support for this product:
– Hardware Enablement (HEEnable11i)
– Base Quality Pack (GOLDBASE11i)
– Applications Quality Pack (GOLDAPPS11i)
If you do not install the patches, resource models stop running and receive the
following error:
Receiving Java Exception: Time already cancelled error.
When you finish
Check the task output for messages that report path errors for the Java Runtime
Environment. You must correct any error conditions.
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
Command line: Use the wruntask in the command-line interface, as in this
example:
wruntask -t DMLinkJre -l "IBM Tivoli Monitoring Tasks" -h my_endpoint –a jre_directory
22 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
where my_endpoint is the name of the endpoint you want to monitor, and
jre_directory is the full path of the Java Runtime Environment.
Tivoli desktop:
1. Access the Tivoli desktop as described in “Accessing the Tivoli Management
Framework environment” on page 52.
2. Click TMR Connections in the Desktop menu.
3. Click Top Level Policy Regions.
4. Double-click TivoliDefaultMw2kRegion-TMRname, where TMRname is the
name of the Tivoli management region. The Policy Region window is
displayed.
5. Double-click the IBM Tivoli Monitoring Tasks task library icon to display the
Task Library window.
6. Double-click DMLinkJre to display the Execute Task window.
7. Select the endpoints that you want to link to the Java software.
Note: These are endpoints that run instances of Sybase ASE that you want to
monitor.
8. Click Execute to display the DMLinkJre window.
9. Type the directory path of the Java software, up to but not including the bin
directory.
For example on a UNIX system, if the Java software is installed in the
/usr/java/bin/ directory, type /usr/java in the text field. For a user running
the command on Windows, the path might similar to this one: c:\data\jre130.
This directory path must be the same on all endpoints that you selected in
Step 7.
10. Click Set & Execute.
The task validates the link to the Java software or advises you of a path error.
A path error becomes evident later when the distribution of resource models
to the endpoint generates an error stating that the Java software is missing or
not installed.
Enabling Sybase ASE for monitoring
Objective
To enable Sybase ASE for monitoring by IBM Tivoli Monitoring for Databases:
Sybase ASE.
Background information
You must configure Sybase ASE so that it can provide monitoring data to Tivoli.
Required authorization role
See the documentation for Sybase ASE.
Before you begin
None.
Chapter 3. Completing the installation 23
When you finish
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
To enable Resource Models to gather data, the Sybase Adaptive Server needs to be
configured. To configure the Sybase Adaptive Server so that the Resource Models
will successfully capture data:
1. Add ’loopback’ server name alias to the Sybase Adaptive Server. Issue the
following SQL commands:
use master
go
sp_addserver loopback, null, server_name
go
2. Install the monitoring tables into the Sybase Adaptive Server. From the
command line, issue the following command:
isql -Uuser_id -Ppassword \
-S server_name \
-i $SYBASE/$SYBASE_ASE/scripts/installmontables
3. Assign the ’mon_role’ to the user which is stored in the objects’ context. Issue
the following SQL commands:
use master
go
grant role mon_role to user_id
go
4. Enable some configuration parameters in the Sybase Adaptive Server to enable
Sybase to collect monitoring data. Issue the following SQL commands:
sp_configure "enable monitoring", 1
go
sp_configure "wait event timing", 1
go
5. Increase the number of user connections to Sybase to accomodate monitoring.
a. Determine how many connections Sybase is currently configured for:
sp_configure "number of user connections"
go
b. Increase the number of connections Sybase is configured for by 20:
sp_configure "number of user connections", current_setting + 20
go
Configuring the IBM Tivoli Enterprise Console event server
Objective
To set up your IBM Tivoli Enterprise Console event server to process events.
Background information
The IBM Tivoli Enterprise Console provides the following functions:
v Receiving events from various sources
v Processing events using rules
v Grouping events and delegating the groups selectively to administrators
v Responding to events automatically
24 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v Viewing events at a console
You must set up the event server before events can be sent to IBM Tivoli
Enterprise Console. Use the Configure Event Server task to set up the IBM Tivoli
Enterprise Console event server.
The Configure Event Server task performs the following actions:
v Imports IBM Tivoli Monitoring for Databases: Sybase ASE event classes and rule
set
v Imports the IBM Tivoli Monitoring event classes and rules (if they are not
already present)
v Imports the IBM Tivoli Business Systems Manager rule set that forwards events
from IBM Tivoli Monitoring for Databases: Sybase ASE, if appropriate
v Compiles the rule base to incorporate new classes and rules
v Loads the new rule base (optional)
v Optionally stops and restarts the event server
You can configure only one IBM Tivoli Enterprise Console event server for each
Tivoli management region. When you have interconnected Tivoli management
regions, run the Configure Event Server task against each Tivoli management
region that contains a IBM Tivoli Enterprise Console event server.
Required authorization role
SybaseMon_IXB_senior
Before you begin
Verify that IBM Tivoli Monitoring Component Services, 5.1.3, is installed on each
computer that hosts a IBM Tivoli Enterprise Console event server.
When you finish
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
You can run this procedure from the command line or the Tivoli desktop.
Command line
Use the wruntask command to run the Configure Event Server task. For the CLI
syntax for this task, see Appendix D, “Task reference,” on page 57.
Tivoli desktop
Follow these steps to perform this procedure from the Tivoli desktop:
1. Right-click the Monitoring for Sybase ASE policy region.
2. Select Configure Event Server in the pop-up menu.
3. Select the managed node on which you want to configure the event server.
4. Select IBM Tivoli Monitoring for Databases: Sybase ASE in the Product to
configure list.
Additional information: The fields on the Configure Event Server window are, by
default, completed with the information needed to run this procedure. The
Chapter 3. Completing the installation 25
Configure Event Server tasks creates a new rule base by using the contents of
an existing rule base as a starting point. The name of the new rule base is
displayed in the New Rule Base Name field and its location is displayed in the
New Rule Base Path field.
Click Help for information about the other options in this window.
5. Select Forward to TBSM, if you want to enable IBM Tivoli Enterprise Console
to forward events to IBM Tivoli Business Systems Manager.
6. Select Load Rule Base and Restart Server from the Rule Base Activation list.
7. Click Set and Execute.
A confirmation window displays the job status after the task completes.
Integrating with IBM Tivoli Business Systems Manager
Objective
To integrate IBM Tivoli Monitoring for Databases: Sybase ASE with IBM Tivoli
Business Systems Manager so you can view monitoring data through IBM Tivoli
Business Systems Manager.
Background information
Customers who use IBM Tivoli Business Systems Manager might want to integrate
that product with IBM Tivoli Monitoring for Databases: Sybase ASE. IBM Tivoli
Enterprise Console is required to enable this integration, because IBM Tivoli
Enterprise Console event servers receive events from IBM Tivoli Monitoring for
Databases: Sybase ASE and forward them to IBM Tivoli Business Systems Manager.
See “Optional software” on page 43 for a list of valid versions of these software
applications.
Stages for configuring communication with IBM Tivoli Business Systems
Manager:
1. Install software on the IBM Tivoli Business Systems Manager server to achieve
the following goals:
v Define the resources that you want to manage in IBM Tivoli Business
Systems Manager.
v Add IBM Tivoli Monitoring for Databases: Sybase ASE tasks to the object
types in IBM Tivoli Business Systems Manager.
v Define a business system for resources.2. Configure IBM Tivoli Enterprise Console event servers, using the Tivoli
Configure Event Server task.
3. If you are using Tivoli Management Framework, Version 4.1.1, you must toggle
an option in the Tivoli oserv process to allow remote connections, as described
in Step 4 on page 28.
4. Run the Discovery task, as described in “Discovering resources to monitor” on
page 29. The task enables the forwarding of data to IBM Tivoli Business
Systems Manager.
This procedure includes information on the Automated Business System feature of
IBM Tivoli Business Systems Manager. The automated business system function
automatically creates views by monitoring for resources that satisfy a stated
criteria, allowing faster implementation of business systems without use of the
console. See IBM Tivoli Business Systems Manager Administrator’s Guide for more
information.
26 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Required authorization role
Administrator authority on the IBM Tivoli Business Systems Manager server
SybaseMon_IXB_senior and SybaseMon_IXB_super
Before you begin
Configure the IBM Tivoli Enterprise Console event server, as described in
“Configuring the IBM Tivoli Enterprise Console event server” on page 24.
Ensure that the IBM Tivoli Business Systems Manager environment is configured
correctly and that you have Tivoli Event Enablement installed on each IBM Tivoli
Enterprise Console event server that will forward IBM Tivoli Monitoring for
Databases: Sybase ASE events to IBM Tivoli Business Systems Manager. See the
IBM Tivoli Business Systems Manager Installation and Configuration Guide for more
information.
The install program uses the following IBM Tivoli Business Systems Manager
utility commands:
gemgenprod.sh
loadgemicons.ksh
tllparser.sh
bldgemtasks.sh
See the IBM Tivoli Business Systems Manager documentation to determine which
services should be stopped before these commands are executed.
When you finish
Discover resources to monitor as described in “Discovering resources to monitor”
on page 29.
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Configure additional monitoring options as described in the IBM Tivoli Monitoring
for Databases: Sybase ASE: User’s Guide.
Periodically, you should run the TBSM Synchronization task to update the list of
objects that IBM Tivoli Business Systems Manager monitors. Also run the task
whenever you believe that objects have been created or deleted and IBM Tivoli
Business Systems Manager has failed to register the event. For example, this failure
to register objects could happen if the network connection to IBM Tivoli Business
Systems Manager was temporarily down. See the Task Reference appendix in the
IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide for details regarding
the TBSM Synchronization task.
Procedure
1. Install the integration program for IBM Tivoli Monitoring for Databases: Sybase
ASE:
a. Access a command prompt on the IBM Tivoli Business Systems Manager
server.
b. Navigate to the \TBSM directory in the set of installation software.
Chapter 3. Completing the installation 27
v If you have installation software on CDs, this directory is located on the
Component Software CD.
v If you downloaded the installation software, search for the \TBSM
directory in the file hierarchy where you are storing the software.c. Type install to start the installation wizard.
d. Click Next on the welcome screen.
e. Specify an installation location for the IBM Tivoli Business Systems Manager
integration program.
Additional information: The default location is c:\tivoli\itm\IXB. Click
Browse to select a different installation location.
f. Click Next to continue.
g. Provide the following information and click Next to start the installation.
SQL Server
The name of the SQL server with which this IBM Tivoli Business
Systems Manager server is associated
SQL Userid
The SQL user ID
SQL Password
The password for the user ID defined aboveA progress bar is displayed to show the progress of the installation. When
installation is complete, a message is displayed.
h. Click Finish to exit the installation wizard.2. (Optional) The IBM Tivoli Business Systems Manager Administrator might want
to use the Automated Business Systems template file created in the
TBSM_Install_Directory/Data/absfiles directory to merge with existing
Automated Business Systems definitions. See the IBM Tivoli Business Systems
Manager documentation for more information about Automated Business
Systems.
3. Run the Configure Event Server task to configure (or re-configure) each IBM
Tivoli Enterprise Console event server.
Additional information: For information on running this task, see “Configuring
the IBM Tivoli Enterprise Console event server” on page 24 and the Task
Reference appendix in the IBM Tivoli Monitoring for Databases: Sybase ASE:
User’s Guide. When Tivoli Event Enablement exists on the event server, the
Configure Event Server task recognizes it and compiles the rule base that
forwards events to IBM Tivoli Business Systems Manager. You must select the
Forward to TBSM option.
4. (Tivoli Management Framework, Version 4.1.1 only) Run the following commands
to enable IBM Tivoli Business Systems Manager to run tasks in the Tivoli
Management Framework.
Additional information: IBM Tivoli Business Systems Manager uses the IBM
Tivoli Enterprise Console server to run tasks. You enable IBM Tivoli Enterprise
Console server to use a private key to run these tasks in Tivoli Management
Framework, version 4.1.1. Communications for IBM Tivoli Business Systems
Manager require use of a private key. These communications would fail in
Tivoli Management Framework, version 4.1.1, because public keys are required
by default.
28 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Note: The default setting (public keys) provides more secure connection. Take
this fact into account as you design your system and decide whether
Tivoli Management Environment task execution should be enabled for
Tivoli Business Systems Manager.
a. Access the Tivoli environment on the computer that hosts the IBM Tivoli
Enterprise Console server:
# . /etc/Tivoli/setup_env.sh
Note: The odadmin command set exists to configure and manager oserv,
the Tivoli object dispatcher of the Tivoli Management Framework.
See Tivoli Management Framework Maintenance and Troubleshooting
Guide for more information on oserv.
b. Enable Tivoli Management Framework communications with the object
dispatcher of IBM Tivoli Enterprise Console server:
odadmin set_allow_rconnect TRUE object_dispatcher_of_TEC_server
where object_dispatcher_of_TEC_server is the code for the object dispatcher of
the IBM Tivoli Enterprise Console server. The TRUE setting enables
communication based on private keys. For more information see Tivoli
Enterprise Installation Guide which is part of the documentation for Tivoli
Management Framework.
c. Restart oserv:
odadmin reexec object_dispatcher_of_TEC_server
See the section on enabling and disabling remote connections in the Tivoli
Enterprise Installation Guide for additional information. This document is part of
the documentation for Tivoli Management Framework.
5. Use IBM Tivoli Business Systems Manager to view and manage your resources.
See the IBM Tivoli Business Systems Manager User’s Guide for more information
on using IBM Tivoli Business Systems Manager.
Discovering resources to monitor
Objective
To identify Sybase ASE resources so the IBM Tivoli Monitoring for Databases:
Sybase ASE recognizes them, which allows IBM Tivoli Monitoring for Databases:
Sybase ASE to monitor the resources.
Background Information
Tivoli objects that represent Sybase ASE resources are registered in the Tivoli
management region and monitored by the IBM Tivoli Monitoring for Databases:
Sybase ASE resource models.
The Discover task creates objects for resources that exist. These resources must be
running at the time of discovery. With the Discover task, you provide information
about a resource and the task finds the resource and creates an object representing
that resource. You discover resources to monitor by running the Discover task. The
Discover task finds instances of the product that you want to monitor on specific
systems, provided that the instances are running at the time of discovery. When
more than one instance exists on a system, you must rerun the Discover task to
discover each instance. In a clustered environment, you must run the Discover task
for each installation of the target product on each system in the cluster.
Note: If the Tivoli environment traverses a firewall, you should install and
configure the Tivoli Firewall Security Toolbox (FST) in order to correctly
Chapter 3. Completing the installation 29
configure and monitor remote applications. Failing to utilize FST may result
in false discovery and intermittent connectivity issues. See the IBM Redbook
Tivoli Enterprise Management Across Firewalls (publication number SG24-5510)
for more information.
You can run the Discover task from the task library (Tivoli desktop), command
line, or policy region context menu.
The Discover task uses the following items that are created during the installation
of IBM Tivoli Monitoring for Databases: Sybase ASE:
v Task library
v Policy region
v Profile that contains the resource models for IBM Tivoli Monitoring for
Databases: Sybase ASE
v Profile manager that subscribes to the profile
Required authorization role
SybaseMon_IXB_senior
Before you begin
Install IBM Tivoli Monitoring for Databases: Sybase ASE.
Set the authorization roles that you need as described in ″Setting authorization
roles″.
Ensure that the application that you want to monitor is running while you perform
this procedure. For the Discover task to work, the application must be installed and
running.
When you finish
Distribute the resource models using the following procedure: “Distributing
resource models” on page 37. (An alternative method is to use the option of the
Discover task that distributes monitoring when discovery happens.)
View the icons for the managed resources that you installed to verify that they
exist.
Procedure
Discover: You can perform these procedures from the command line or from the
Tivoli desktop.
Note: The Tivoli desktop procedure is easier to use than the command-line
procedure because the user interface window prompts for the required
information.
Command line: See Appendix D, “Task reference,” on page 57 for more information
about the command line syntax and an example.
Use the wruntask command as described in “Discover” on page 63.
Example:
wruntask -t "Discover" \
-l "Monitoring for Sybase ASE Utility Tasks" \
-h "@ManagedNode:MyManagedNode" \
-a "@Endpoint:example_ep @Endpoint:other_ep" \
30 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
-a "MyManagedNode" \
-a "60" \
-a "no" \
-a "no" \
-a "@EventServer" \
-a "5529" \
-a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
-a "/opt/sybase/" \
-a "SybaseASEServer_AP_SYBASE_OS_USER" \
-a "sybase" \
-a "SybaseASEServer_AP_SYBASE_USER" \
-a "sa" \
-a "SybaseASEServer_AP_SYBASE_PASSWORD" \
-a "secret" \
-a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
-a "server1_BS" \
-a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
-a "server1_MS" \
-a "SybaseASEServer_AP_LogMonitorLogname" \
-a "/opt/sybase/ASE-12_5/install/server1.log" \
-m "600"
See the Tivoli Management Framework Reference Manual for details regarding the
wruntask command and see Appendix D, “Task reference,” on page 57 for more
information about the Discover task.
Tivoli desktop:
1. Right-click on the Monitoring for Sybase ASE policy region on the Tivoli
desktop and select Discover Application Configurations.
2. Complete the fields in the Discover window using the information in
Appendix D, “Task reference,” “Discover” on page 63.
3. Click Apply.
4. Click Set and Execute.
Updating IBM Tivoli Monitoring Web Health Console files
Objective
To update the IBM Tivoli Monitoring Web Health Console files after you install a
new component or upgrade IBM Tivoli Monitoring for Databases: Sybase ASE.
Background information
This procedure describes how to update the class files for the IBM Tivoli
Monitoring Web Health Console after you add a component of the product. The
class files specify the standard text that the console displays.
Whenever you add or upgrade components for your installation of IBM Tivoli
Monitoring for Databases: Sybase ASE you must perform this procedure. For
example, if you upgrade the product to a later release, you must update the class
files located on the computer that hosts the IBM Tivoli Monitoring Web Health
Console. The new class files become available after you restart the Web application
server that enables the console.
You do not need to perform this procedure after installing the IBM Tivoli
Monitoring Web Health Console with the installation utility. This utility
Chapter 3. Completing the installation 31
automatically installs the required class files. See Appendix F, “Installing IBM
Tivoli Monitoring for Databases: Sybase ASE and a complete Tivoli environment,”
on page 73 for more information..
Required authorization role
Logon privileges for the computer that hosts the Web Health Console.
Before you begin
Ensure that the following CDs (or equivalent Web download images) are available
to the computer that hosts the Web Health Console:
v The IBM Tivoli Monitoring, Version 5.1.2 CD
v All IBM Tivoli Monitoring for Databases: Sybase ASE CDs that are labeled
Component Software
v The IBM Tivoli Monitoring for Databases: Sybase ASE Language Support CD if
you want to install Web Health Console updates in languages other than English
When you finish
Restart the Web application server on the computer that hosts the IBM Tivoli
Monitoring Web Health Console to make the new class files available.
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
You can perform this procedure from the command line only.
Command line: Copy the contents of the HCONSOLE directory of catalog files
from one of the following installation CDs:
v For the English language updates to IBM Tivoli Monitoring, copy catalog files
from the IBM Tivoli Monitoring Language Support installation CD.
v For the English language updates to IBM Tivoli Monitoring for Databases:
Sybase ASE, copy catalog files from the IBM Tivoli Monitoring for Databases:
Sybase ASE Component Software CD.
v For other languages, copy catalog files from the IBM Tivoli Monitoring for
Databases: Sybase ASE Language Support CD.
You must insert the contents of the HCONSOLE directory in the following
resources directory on the target computer that hosts the IBM Tivoli Monitoring
Web Health Console:
INSTALL_DIR/installedApps/dm.ear/dm.war/WEB-INF/classes/com/tivoli/DmForNt/resources
where INSTALL_DIR is the installation directory of the IBM Tivoli Monitoring Web
Health Console.
Enabling historical reporting of monitoring data
Objective
To install the data warehouse packs provided by the product so that the Tivoli
Data Warehouse (an optional product that comes with IBM Tivoli Monitoring for
Databases: Sybase ASE) can provide historical reports from data collected by
resource models.
32 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Note: This procedure describes the installation of warehouse packs in a Tivoli Data
Warehouse environment that exists on a single Windows computer. This
type of installation simplifies configuration and setup, but might serve only
as a test or demonstration environment. Most monitoring environments
require a distributed installation of Tivoli Data Warehouse. To learn how to
install and configure enablement files for a distributed environment, see
Installing and Configuring Tivoli Data Warehouse.
Background information
The Tivoli Data Warehouse is a central data store where historical data from Tivoli
management applications is aggregated and correlated for use by tools that
perform reporting, planning, analysis, accounting, and other functions. The IBM
Tivoli Monitoring products store resource model data in the Tivoli Data
Warehouse, which uses the data to produce historical reports.
To enable the Tivoli Data Warehouse to receive and store data, each Tivoli
management application provides one or more software modules called a warehouse
enablement pack or warehouse pack. The warehouse packs are separately installed on
the systems where the Tivoli Data Warehouse is installed. Warehouse packs
provide ETL (extract, transform, and load) utilities that gather the data from the
source applications (for example, IBM Tivoli Monitoring for Databases: Sybase
ASE) and disperse the data into data marts. The data marts serve as customized
sources of data for reporting and other tools. There are two basic types of ETL
utility:
v The central data warehouse ETL (called ETL1) reads the data from the data store
used by the source application, modifies it to conform to the Tivoli Data
Warehouse schema, and copies the modified data to the central data warehouse.
The central data warehouse is the common receiving area of the Tivoli Data
Warehouse.
v The data mart ETL (called ETL2) extracts data from the central data warehouse,
transforms it, and transfers it to data marts.
The IBM Tivoli Monitoring products provide the following warehouse packs:
v The base product, IBM Tivoli Monitoring, provides a warehouse pack with a
central data warehouse ETL (ETL1). A three-letter code identifies this and all other
packs. This warehouse pack extracts data from resource models and stores it in
the Tivoli Data Warehouse.
v IBM Tivoli Monitoring Component Services provides a warehouse pack with a
data mart ETL (ETL2). This warehouse pack extracts data from central data
warehouse to build the data marts. The data marts are used for historical
reporting and graphical reports.
v Each of the component software products (for example, IBM Tivoli Monitoring
for Databases: Sybase ASE) provides a warehouse pack with an enablement
script that allows the IBM Tivoli Monitoring Component Services ETL2 to extract
the appropriate data for this product.
This procedure describes how to install both the IBM Tivoli Monitoring warehouse
pack and the warehouse packs provided by the IBM Tivoli Monitoring for
Databases: Sybase ASE components.
Required authorization role
On Windows, the user must have membership in the Administrators group.
You will also need the user ID and password to configure DB2.
Chapter 3. Completing the installation 33
Before you begin
Install IBM Tivoli Monitoring Tivoli Data Warehouse 1.2 Fix Pack 2 or higher and
install the IBM Tivoli Monitoring AMX warehouse enablement pack at version 5.1.2
Fix Pack 2 or higher.
v Install Tivoli Data Warehouse Version 1.2 and the required DB2 database
software on a single Windows computer. See the Installing and Configuring Tivoli
Data Warehouse guide for information.
v The computer requires 250 MB of free disk space for the warehouse packs. This
space requirement is in addition to the space required for Tivoli Data Warehouse
and for the DB2 database that comes with the product. The warehouse packs
reside in the installation directory for Tivoli Data Warehouse.
v Obtain the fully qualified host name of the computer where the Tivoli Data
Warehouse is installed. For example, the fully qualified host name for myhost
might be myhost.mycompany.com.
v The user who performs the installation must have a valid user name and
password to access the DB2 instance for this product.
v Ensure that the following CDs (or their equivalent Web download images) are
available to the computer where you will perform the procedure:
– IBM Tivoli Monitoring, Version 5.1.2
This CD includes the software for the warehouse pack (ETL1) provided for
IBM Tivoli Monitoring.
– IBM Tivoli Monitoring for Databases, Version 5.1.2: Installation Disc 2 for
Sybase ASE
This CD contains IBM Tivoli Monitoring Component Services, Version 5.1.3
The CD includes the software for the warehouse pack (ETL2) provided for
IBM Tivoli Monitoring for Databases: Sybase ASE.
– IBM Tivoli Monitoring for Databases, Version 5.1.2: Component Software CD.
When you finish
Consult the following resources to learn how to complete the implementation of
historical reporting:
v See the IBM Tivoli Monitoring Warehouse Enablement Pack Implementation Guide for
information about configuring Tivoli Data Warehouse for IBM Tivoli Monitoring.
v See the IBM Tivoli Monitoring Component Services, Version 5.1.3, Guide for
Warehouse Pack, Version 1.3.0.0, using Tivoli Data Warehouse 1.2 for your
component for specific post-installation steps you must perform.
v Enable data logging for Tivoli Data Warehouse as described in the component
software user’s guides.
v Refer to the component software user’s guides for information about using the
Tivoli Data Warehouse reports.
Check the list of completion activities at the beginning of Chapter 3, “Completing
the installation,” on page 15. Complete all required procedures, and complete any
optional procedures that enable features that you want for your Tivoli
environment.
Procedure
Perform this procedure using the warehouse pack installation wizard.
Installation wizard:
1. Log on to the computer that runs Tivoli Data Warehouse.
2. Click Start → Programs → Tivoli Data Warehouse → Install a Warehouse Pack.
34 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
This action starts the warehouse pack installation wizard.
3. Click Next on the Welcome window.
The Tivoli Common Logging Directory window displays the name of the
Tivoli common logging directory.
4. Click Next to display the Warehouse Packs to Install window.
Additional Information: The Warehouse Packs to Install window lists the
warehouse packs, fixes, and upgrades that you want to install. The first time
you see this window, the list is empty. You click Add to add a warehouse
pack, fix, or upgrade.
Warehouse packs are installed in the order that you add them to the list. If
one warehouse pack is a prerequisite to another, you must add that
warehouse pack to the list first. The installation program generates an error if
you specify them in the wrong order. In this procedure, you must add the
central data warehouse pack provided by IBM Tivoli Monitoring before you
add the data mart warehouse packs provided by the component software.
5. On the computer that hosts Tivoli Data Warehouse, perform the following
steps to install the central data warehouse pack (ETL1) provided by IBM
Tivoli Monitoring:
a. If you are installing from CDs, insert the IBM Tivoli Monitoring, Version
5.1.2 CD. (If you are installing from downloaded Web files or CD images
in a remote location, go to Step 5b.)
b. Click Add to display the Location of Installation Properties File window.
c. Browse to the location of the warehouse pack installation properties file,
twh_install_props.cfg.
This file is located in the following directory path in files that you
downloaded from the Web or on the IBM Tivoli Monitoring, Version 5.1.2
CD:
\tedw_apps_etl\5.1.2\amx\pkg\
d. Select the twh_install_props.cfg file and click OK.
e. Click Next.
The Warehouse Packs to Install window is displayed again. The IBM
Tivoli Monitoring warehouse pack is now displayed in the list. 6. Verify that you have the correct version of the prerequisite IBM Tivoli
Monitoring warehouse pack.
Additional information: Installation of the prerequisite WEP AMX 5.1.2 Fix Pack
1 can fail with a prerequisite failure even though AMX 5.1.1.600 is installed
because, the process fails to register the warehouse pack version.
a. Run twg_configwep.bat -u user -p password -f list to list the installed
warehouse enablement packs and version information.
Note: To ensure a successful installation, confirm the version number
(AMX 5.1.1.600) before you run the installation of the AMX 5.1.2
Fixpack 1 WEP (version 5.1.1.660) that is a prerequisite for the IBM
Tivoli Monitoring Component Services warehouse enablement pack.
b. If the version number is correct, go to Step 7 on page 36. Otherwise,
continue with Step 6c.
c. Ensure that you access a user account that has DB2 administrator
privileges on the computer that hosts Tivoli Data Warehouse.
d. Access a command prompt.
Chapter 3. Completing the installation 35
e. Manually execute the following command before you install the
warehouse pack that has warehouse pack AMX version 5.1.1.600 as a
prerequisite.
twh_setwepver AMX 5.1.1 5.1.1.600
You need to run this command only once, however it is harmless to run
the command again. The command is located in the following path:
install_dir/twh/tools/bin/twh_setwepver.bat
If the AMX version is 5.1.1.600 or higher, do not reset the version
information.
f. After AMX 5.1.1.660 is installed in the warehouse you can proceed to install
the IBM Tivoli Monitoring Component Services warehouse enablement
pack. 7. On the computer that hosts Tivoli Data Warehouse, perform the following
steps to install the central data warehouse pack (ETL2) provided by IBM
Tivoli Monitoring Component Services:
a. If you are installing from CDs, insert the IBM Tivoli Monitoring for
Databases, Version 5.1.2: Installation Disc 2 for Sybase ASE. If you are
installing from downloaded Web files or from CD images in a remote
location, go to Step 7b.)
b. Click Add to display the Location of Installation Properties File window.
c. Browse to the location of the IBM Tivoli Monitoring Component Services,
Version 5.1.3, warehouse pack installation properties file,
twh_install_props.cfg. This file is located in the following directory path in
the set of installation files:
\ITMCS\tedw_apps_etl\5.1.3\amg\pkg\v120\
d. Select the twh_install_props.cfg file and click OK.
e. Click Next. The Warehouse Packs to Install window is displayed again.
The IBM Tivoli Monitoring Component Services warehouse enablement
pack (identified by the AMG code) now appears in the list. 8. Register IBM Tivoli Monitoring for Databases: Sybase ASE with the warehouse
enablement pack for IBM Tivoli Monitoring Component Services, so that the
product can reference the warehouse and reporting structure for IBM Tivoli
Monitoring Component Services:
a. On the computer that hosts Tivoli Data Warehouse, open a Command
Prompt and run the db2cmd command to access a DB2 command window.
b. Use the db2cmd window to connect to the TWH_CDW central data
warehouse using one of the following commands:
v If the current user is also a db2admin: db2 connect to TWH_CDW
v if the current user is not a DB2 administrator: db2 connect to TWH_CDW
user db2adminID using password
c. Run the wep_enable.bat script.
Additional information: The wep_enable.bat script is located in the
/tedw_apps_etl directory of the Component Software CD or Web
download files for IBM Tivoli Monitoring for Databases: Sybase ASE. This
script runs the wep_enable.sql command. 9. Click Next to display the Summary window.
10. Click Install to begin the installation of all warehouse packs displayed on the
Summary window.
11. When installation is complete, click Finish to exit.
36 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Chapter 4. Distributing resource models
This section describes how to distribute resource models.
Distributing resource models
Objective
To distribute resource models and begin monitoring instances of Sybase ASE.
Background Information
You distribute resource models by distributing a profile that includes the resource
models that you want to distribute. You distribute the profile to subscribers, which
are computers that represent instances of Sybase ASE that you want to monitor.
When you distribute resource models, you set up fixed thresholding for the
resource models, because this is the default setting. See the IBM Tivoli Monitoring
for Databases: Sybase ASE: User’s Guide for information about the options for
modifying thresholding and other settings for resource models.
Required authorization role
admin
Before you begin
Discover the targets for distribution of monitors, using the Discover task described
in “Discover” on page 63.
When you finish
Check the resource models that you distributed to see the results of the
distribution.
(UNIX only) When you are monitoring an application on UNIX, the Availability
resource model will be in Error state when all of the following conditions are true:
v The monitoring engine is running on the system where resource models are
being distributed.
—AND—
v You distribute resource models, as described in this procedure.
—AND—
v You have never run DMXProcess (a resource model from IBM Tivoli Monitoring)
on the target computer.
To resolve this problem, stop and restart the engine for IBM Tivoli Monitoring. For
example, you can use the wdmcmd command to restart the engine on the
endpoint, as in the following example:
wdmcmd -restart -e endpoint_name
Procedure
You can perform this procedure from the command line or from the Tivoli desktop.
Command line: The wdmdistrib command updates subscriber databases and
configuration files. If no subscriber is specified, wdmdistrib updates all
subscribers. The syntax varies depending on the version of Tivoli management
© Copyright IBM Corp. 2004 37
region that you installed. For more information about the wdmdistrib command,
refer to the IBM Tivoli Monitoring User’s Guide.
Use the wdmdistrib command to distribute the profile to the subscribers of the
profile manager as follows:
1. Determine the target objects for distribution:
a. Run the following wlookup command:
wlookup -ar PAC_class
The available classes are as follows:
v SybaseASEServer_IXBb. Locate the objects for distribution using the label that the command returns.
2. Determine the profile:
a. Run the following wlookup command:
wlookup -ar Tmw2kProfile
b. Locate the label of the profile to be distributed.3. Distribute the profile:
a. Run the following wdmdistrib command:
wdmdistrib -p profile_name @PAC_class:PAC_object
Where:
-p profile_name
Name of the profile that is to be distributed. The profile name can
be fully qualified with the policy region name. If no region is
indicated, the local region is assumed. For example:MonitoringforSybaseASESybaseASE\ServerMonitorProfile.
PAC_class
The available classes are as follows:
v SybaseASEServer_IXB
PAC_object
Name of the objects that represent the managed resource instance to
which you are distributing the resource model. The available objects
are as follows:
v server1@SybaseASEServer_IXB@example_epb. See the IBM Tivoli Monitoring 5.1.2 User’s Guide for other options for the
wdmdistrib command.
Tivoli desktop:
1. Double-click the ″Monitoring for Sybase ASE″ policy region to access the policy
region view.
2. Open the ″Monitoring for Sybase ASE Sybase ASE Server Resource Models″
profile manager. The profile manager window displays the profile that it
contains and the profile manager that contains the available instances.
3. Drag the ″MonitoringforSybaseASESybaseASE\ServerMonitorProfile″ profile onto the ″Monitoring for Sybase ASE Sybase ASE
Server Instances″ profile manager to distribute resource models to all available
instances.
38 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix A. Essential steps for a command-line installation
This section summarizes the essential steps for installing IBM Tivoli Monitoring for
Databases: Sybase ASE. These steps start with upgrading IBM Tivoli Monitoring
and end with the deployment of resource models. The summary includes
appropriate examples for users who choose the command-line installation option.
1. Upgrade IBM Tivoli Monitoring 5.1.2 to Fix Pack 02, using your desired
upgrade method. The following command-line example upgrades an
installation of IBM Tivoli Monitoring 5.1.2 to Fix Pack 02 on computer that
hosts the Tivoli server:
wpatch -c d:\temp -i 512ITM02 -y
If you do not have IBM Tivoli Monitoring 5.1.2 installed, you can use an
installation utility to install a new, complete Tivoli environment, as described in
Appendix F, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE and a
complete Tivoli environment,” on page 73. The installation utility provides the
required patches.
2. Apply the ITM-5.1.2-0059 patch as in this example:
wpatch -c d:\temp -i 512M59 -y
3. Install IBM Tivoli Monitoring Component Services 5.1.3 or upgrade IBM Tivoli
Monitoring Component Services to 5.1.3 level.
Additional information: Here is a CLI example for installing IBM Tivoli
Monitoring Component Services 5.1.3 on a system that does not have IBM
Tivoli Monitoring Component Services installed:
winstall -c d:\temp\ITMCS -i CMPTSVCS -y
Here is a CLI example for upgrading an existing IBM Tivoli Monitoring
Component Services to the 5.1.3 level:
wpatch -c d:\temp\ITMCS -i CS513P -y
4. Install IBM Tivoli Monitoring for Databases: Sybase ASE.
winstall -c d:\temp\IXB -i IXB512 -y
5. Set up roles. In this example, a Tivoli administrator PACAdmin is assumed to
exist, and the user has the user and admin roles for the Tivoli environment:
wsetadmin -r global,user:admin:SybaseMon_IXB_user:SybaseMon_IXB_admin:SybaseMon_IXB_senior PACAdmin
6. Run discover task, as shown in the following example:
wruntask -t "Discover" \
-l "Monitoring for Sybase ASE Utility Tasks" \
-h "@ManagedNode:MyManagedNode" \
-a "@Endpoint:example_ep @Endpoint:other_ep" \
-a "HostManagedNode" \
-a "60" \
-a "no" \
-a "no" \
-a "@EventServer" \
-a "5529" \
-a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
-a "/opt/sybase/" \
-a "SybaseASEServer_AP_SYBASE_OS_USER" \
-a "sybase" \
-a "SybaseASEServer_AP_SYBASE_USER" \
-a "sa" \
© Copyright IBM Corp. 2004 39
-a "SybaseASEServer_AP_SYBASE_PASSWORD" \
-a "secret" \
-a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
-a "server1" \
-a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
-a "server1_BS" \
-a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
-a "server1_MS" \
-a "SybaseASEServer_AP_LogMonitorLogname" \
-a "/opt/sybase/ASE-12_5/install/server1.log" \
-m "600"
For detailed information on this example, see the description in “Discover” on
page 63.
7. Distribute resource models.
The following example distributes the profile myProfile that includes resource
models. The target of the distribution is a subscriber called instance_name which
is an instance of resource resource.
wdmdistrib -p myProfile @resource:instance_name
8. Run the following command to confirm that resource models were distributed
and are running:
wdmlseng -e my_endpoint -verbose
See the appropriate sections of the documentation to learn how to supplement
your Tivoli environment with optional products such as IBM Tivoli Enterprise
Console, IBM Tivoli Business Systems Manager and Tivoli Data Warehouse.
See IBM Tivoli Monitoring for Databases: Sybase ASE: User’s Guide to learn how to
customize resource models that you run in the Tivoli environment.
40 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix B. System and software requirements
This appendix describes the following system requirements and software
prerequisites for installing the product. Review these requirements to ensure that
your environment is prepared for installation.
v Operating systems that IBM Tivoli Monitoring for Databases: Sybase ASE
supports for the Tivoli server, managed nodes, and endpoints
v Required and optional software prerequisites
v Disk space requirements for the Tivoli server, managed nodes, and endpoints
Disk space requirements
This section lists the disk space requirements for the elements in the Tivoli
environment.
Table 7. Disk space requirements for installing the Tivoli environment
Element Disk space requirements
Tivoli server
Approximately
5 GB
(including
temporary
installation
files)
v The product installation requires a minimum of 1.5 GB of disk space on the Tivoli management
region server and on managed nodes.
v Tivoli Management Framework and IBM Tivoli Monitoring: 500 MB
Note: On Windows, the depot must reside on the target computer. You cannot perform an
installation of the product on Windows using a depot that is located on a remote system. On
UNIX, provide a directory path that is accessible from the installation computer to the
installation depot.
v The installation depot (temporary directory): 2.6 GB
v Files that the installation utility places in the temporary ($TEMP or %TEMP%) directories that
are defined for your operating system: 3 MB
Additional information: Obtain the name of this directory by accessing the Tivoli command-line
environment (as described in “Accessing the Tivoli Management Framework environment” on
page 52) and entering this command: wtemp.
v The IBM Tivoli Monitoring for Databases: Sybase ASE: 200 to 300 MB
v The Java runtime environment, Version 1.3.0, requires 75 MB of disk space. *
Managed node
Approximately
1.5 GB
v Tivoli Management Framework and IBM Tivoli Monitoring: 500 MB (Includes the space required
by the gateway software that enables the managed node to communicate with an endpoint.)
v IBM Tivoli Monitoring for Databases: Sybase ASE: 200 to 300 MB
v The Java runtime environment, Version 1.3.0, requires 75 MB of disk space. *
Endpoint
Approximately
100 MB
v The endpoint daemon for Tivoli Management Framework: 2 MB
v The Java runtime environment, Version 1.3.0, requires up to 75 MB of disk space. *
* The space requirement for the Java runtime environment varies, depending on
the operating system. For example, the runtime environment on Windows requires
approximately 65 MB.
Supported operating systems
The following table lists the operating systems that the IBM Tivoli Monitoring for
Databases: Sybase ASE supports. The N/A notation indicates that the target
application does not run on this platform.
© Copyright IBM Corp. 2004 41
Table 8. Platform support
Platform Component
Server (TMR & Managed
Nodes)
Client (Endpoints)
AIX 5.1 Y Y
AIX 5.1.0.c Y N/A
AIX 5.2 Y Y
Solaris 8 Y Y
Solaris 9 Y Y
HP-UX 11i Y Y
Windows NT 4.0 N N/A
Windows 2000 Professional Y Y
Windows 2000 Server Y Y
Windows 2000 Advanced Server Y Y
Windows 2000 Data Center Y N/A
Windows 2000 XP Professional N Y
Windows Server 2003 Standard Y Y
Windows Server 2003 Enterprise Y Y
Windows Server 2003 Data Center Y N/A
OS/400 5.1 N N/A
OS/400 5.2 N N/A
OS/390 v2R10 N N/A
zOS v1.2 N N/A
zOS v1.3 N N/A
zOS v1.4 N N/A
RedHat EL Advanced Server 2.1 Y Y
RedHat EL Advanced Server 3.0 Y Y
RedHat EL Advanced Server 3.0 for iSeries & pSeries Y N/A
SuSE SLES 7 for IA32 Y N/A
SuSE SLES 7 for S/390 & zSeries Y N/A
United Linux 1/ SuSE SLES 8 for IA32 Y Y
United Linux 1/ SuSE SLES 8 for zSeries Y N/A
United Linux 1/ SuSE SLES 8 for PowerPC N N/A
United Linux 1/ SuSE SLES 8 for pSeries Y N/A
Required software
This section lists the required software for IBM Tivoli Monitoring for Databases:
Sybase ASE.
42 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Table 9. Required software for IBM Tivoli Monitoring for Databases: Sybase ASE
Product
Supported
releases Required patches, fix packs, or APAR fixes
Required base Tivoli software
This section of the table lists the base Tivoli software required for all installations.
Tivoli Management Framework
The patches for Version 4.1.1 are located in the
patches directory of the IBM Tivoli
Monitoring for Databases, Version 5.1.2,
Installation Disc 2 for Sybase ASE CD.
4.1.1 * 4.1.1-LCF-0004
4.1.1-TMF-0003
4.1.1-TMF-0004
4.1.1-TMF-0010 *
* When you apply Tivoli Management
Framework patch 4.1.1-TMF-0010, Tivoli also
recommends that you apply 4.1.1-TMF-0011 if
the Framework MDist2 GUI, JRIM, JCF or
Mobile features are installed on your Tivoli
management region.
IBM Tivoli Monitoring
Fix Pack 02 is located in the patches directory
of the IBM Tivoli Monitoring for Databases,
Version 5.1.2, Installation Disc 2 for Sybase
ASE CD.
5.1.2 The following Fix Pack and patch are required:
v Fix Pack 02
v ITM-5.1.2-0059
IBM Tivoli Monitoring Component Services 5.1.3 None
Product monitored by IBM Tivoli Monitoring for Databases: Sybase ASE
See “Supported operating systems” on page 41 for a full list of supported operating systems for these products.
Sybase ASE 12.5.0.3
Sybase ASE 12.5.1 EBF 11658 - Solaris 64 bit
Additional software required on the client (Endpoint)
To enable endpoints for all components:
Java™ Runtime Environment (JRE), Version
1.3.
1.3.0 or 1.3.1
(Version 1.3.1_08
for Solaris
endpoints)
None
* If you use Version 3.7.1 of the Tivoli Management Framework the following
patches (or subsequent patches that include these patches) are recommended:
3.7.1-TMF-0104
3.7.1-TMF-0128
3.7.1-LCF-0017
For AIX: Tivoli Management Framework V 3.7, Revision B PTF U482278 AIX 5.1
Support for Framework
Optional software
This section lists the optional software for IBM Tivoli Monitoring for Databases:
Sybase ASE.
Appendix B. System and software requirements 43
Table 10. Optional software for IBM Tivoli Monitoring for Databases: Sybase ASE
Product
Supported
releases
Required patches, fix packs, or APAR
fixes
Software is
provided with
the product
Optional software to provide supplemental monitoring views
IBM Tivoli Monitoring Web Health
Console
5.1.1 Fix Pack 6 Yes
IBM Tivoli Enterprise Console 3.8 and 3.9 For Version 3.8: Fix Pack 2 or higher
For Version 3.9: Fix Pack 1 or higher
No
Adapter configuration facility
This software enables the enables the
product to send events to IBM Tivoli
Enterprise Console.
The adapter
configuration
facility is
supplied with
the supported
IBM Tivoli
Enterprise
Console
releases
None No
Product configuration software for IBM
Tivoli Enterprise Console
None You use this software in the following
procedure: “Configuring the IBM Tivoli
Enterprise Console event server” on page
24.
Yes
IBM Tivoli Business Systems Manager 2.1.1 and 3.1 Version 2.1.1 Patch 2.1.1-BSM-0006 plus
LAFix 2.1.1-BSM-0012-E09
—OR—
Version 3.1 plus 3.1.0.0-TIV-BSM-LA0009.
Also required: TBSM Event Enablement
2.1.1 Patch 2.1.1-BSM-0009 on the IBM
Tivoli Enterprise Console Server.
No
Product integration software for IBM
Tivoli Business Systems Manager
None. You use this software in the following
procedure: “Integrating with IBM Tivoli
Business Systems Manager” on page 26.
Yes
Other optional software
Database support for the Tivoli
Enterprise Data Warehouse: IBM DB2
Universal Database Enterprise Edition
7.2 v Fix Pack 10
Yes
Tivoli Data Warehouse 1.2 Fix Pack 1.2-TDW-FP02
For DBCS systems, an additional fix pack
is required. See the IBM Support and
downloads Web site at
www.ibm.com/support for additional
information.
Apply all required Hot Fixes for Crystal
Reports, an application that you install
with Tivoli Data Warehouse.
Yes
IBM Tivoli Monitoring Enterprise Data
Warehouse Support pack
This software comes on the IBM Tivoli
Monitoring Component Software CD.
5.1.2 Required patch level is
5.1.2-ITM_TEDW-FP02
Yes.
44 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Table 10. Optional software for IBM Tivoli Monitoring for Databases: Sybase ASE (continued)
Product
Supported
releases
Required patches, fix packs, or APAR
fixes
Software is
provided with
the product
IBM Tivoli Monitoring Warehouse
Enablement Pack support
This software is required to enable
Tivoli Data Warehouse for IBM Tivoli
Monitoring for Databases: Sybase ASE.
This warehouse enablement pack must
come from the version of IBM Tivoli
Monitoring required by IBM Tivoli
Monitoring for Databases: Sybase ASE.
See Table 9 on page 43.
5.1.2 Fix Pack 02
Install this patch in both your IBM Tivoli
Monitoring application and Tivoli Data
Warehouse system.
To obtain software that enables data
collection for Tivoli Data Warehouse
(ETL1 and ETL2), access the IBM Tivoli
Monitoring, Version 5.1.2 CD.
Yes
IBM Tivoli Monitoring Component
Services Warehouse Enablement Pack
support
This software is required to enable
Tivoli Data Warehouse for IBM Tivoli
Monitoring for Databases: Sybase ASE.
5.1.3 None.
This warehouse pack is located in the
ITMCS directory of the IBM Tivoli
Monitoring for Databases, Version 5.1.2,
Installation Disc 2 for Sybase ASE CD.
Yes
Tivoli Software Installation Service 3.7 and 4.1.1 None.
This software comes with the set of Tivoli
Management Framework software that is
included with IBM Tivoli Monitoring for
Databases: Sybase ASE
Yes
IBM Tivoli Monitoring Resource Model
Builder *
1.1.3 None. No
* The IBM Tivoli Monitoring Resource Model Builder software is available at the following Web
site:http://www-3.ibm.com/software/tivoli/resource-center/pa/code-monitor-resource.jsp
Appendix B. System and software requirements 45
46 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix C. Tivoli basics
This appendix describes the basic concepts and operations for a Tivoli
environment.
Table 11. Tivoli basics
Goal Refer to
Review basic concepts and elements in a Tivoli environment. “Overview of the Tivoli environment”
Access the Tivoli environment, either the command-line user interface or
the Tivoli desktop user interface.
“Accessing the Tivoli Management
Framework environment” on page 52
Create backup copies of Tivoli object databases on all computers in a
Tivoli management region and use the copies to restore the object
databases to a known working state if there are problems during
installation. Perform the backup procedure before you install the
product in an existing Tivoli environment and whenever you make
other significant changes.
“Backing up Tivoli databases” on page 54
Overview of the Tivoli environment
The following sections provide an overview of the IBM Tivoli Monitoring
environment.
Tivoli environment
The IBM Tivoli Monitoring for Databases: Sybase ASE requires the support of the
following Tivoli software:
v IBM Tivoli Monitoring
IBM Tivoli Monitoring is the base product for IBM Tivoli Monitoring for
Databases: Sybase ASE and other products in the IBM Tivoli Monitoring family
of products. It provides the foundation for server-based monitoring of
applications. The IBM Tivoli Monitoring for Databases: Sybase ASE extends the
base product to monitor specific applications.
– Monitors operating system status
– Sends notification of system or performance problems and takes automated,
corrective actions
– Collects and stores system datav IBM Tivoli Monitoring Component Services
IBM Tivoli Monitoring Component Services provides services for component
software.
v Tivoli Management Framework
The IBM Tivoli Monitoring for Databases: Sybase ASE functions in a distributed
Tivoli environment so that it can monitor and manage applications installed on
many computers. Tivoli Management Framework provides the management
services required for Tivoli products that are installed in a Tivoli environment.
Table 12 on page 48 shows how the supporting base software and the product
component software, as well as the monitored applications, are typically
distributed across a Tivoli environment.
© Copyright IBM Corp. 2004 47
Table 12. Distribution of Tivoli software and monitored applications in a Tivoli environment
Tivoli environment Installed software
Tivoli server The base and component software is installed on the Tivoli server
and managed nodes:
v Tivoli Management Framework
v IBM Tivoli Monitoring
v IBM Tivoli Monitoring Component Services
v The IBM Tivoli Monitoring for Databases: Sybase ASE
component software
Managed nodes
Endpoints Monitored applications are installed on endpoints.
Tivoli automatically distributes required software to existing
endpoints when you install IBM Tivoli Monitoring, IBM Tivoli
Monitoring Component Services, and IBM Tivoli Monitoring for
Databases: Sybase ASE on managed nodes. Specifically, portions of
the component software required for monitoring are automatically
downloaded to the endpoints.
A basic monitoring solution begins with a set of core monitoring products. You can
extend the basic monitoring solution with additional products to take full
advantage of the collected performance and availability data. The following
products constitute a full monitoring solution:
Additional products to extend monitoring capabilities and collected data
v IBM Tivoli Enterprise Console
IBM Tivoli Enterprise Console is a rules-based event management
application that collects, processes, and automatically responds to events.
You can install IBM Tivoli Enterprise Console on the server or any
managed node or gateway within the Tivoli management region.
v IBM Tivoli Monitoring Web Health Console
IBM Tivoli Monitoring Web Health Console, a part of IBM Tivoli
Monitoring, is a Web-based graphical interface that runs on any system
that can be connected through a TCP/IP interface to the Tivoli
management region. The IBM Tivoli Monitoring Web Health Console
enables you to view the health of resources on an endpoint and view
real-time or historical monitored data. A numeric value between 100
(perfect health) and zero (corresponding event conditions met)
represents the health of each resource.
v Tivoli Data Warehouse
Tivoli Data Warehouse provides a data warehouse with which you can
view historical reports and graphs, enabling you to analyze historical
patterns and trends of your environment. The software maintains
historical data for resources that the resource models capture. The
warehouse enablement pack for each component provides prepackaged
reports to analyze this historical data. You can also create reports to meet
your specific needs.
Tivoli Data Warehouse is installed on the Tivoli management region
server. The Tivoli Data Warehouse Support Component (required for
interaction with IBM Tivoli Monitoring) is installed on the Tivoli
management region server, and, optionally, on one or more managed
nodes. You must install the component on the server before you install it
on the managed nodes.
48 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v IBM Tivoli Business Systems Manager
IBM Tivoli Business Systems Manager provides a graphical interface to
determine the health of an information technology (IT) infrastructure.
The software enables you to discover and create a set of topology views
for your resources. Use IBM Tivoli Business Systems Manager to
examine how individual components or resources affect a business
function. You can monitor and manage these resources from an IBM
Tivoli Business Systems Manager console.
IBM Tivoli Business Systems Manager requires the IBM Tivoli Business
Systems Manager adapter to be able to receive IBM Tivoli Monitoring
events. The adapter must be installed on all gateways in a region.
IBM Tivoli Business Systems Manager can be installed on a standalone
computer that can be part of the Tivoli environment or not. You must
install an IBM Tivoli Business Systems Manager adapter on all gateways
in a region to be able to receive IBM Tivoli Monitoring events.
The IBM Tivoli Monitoring and IBM Tivoli Monitoring Web Health
Console components are automatically enabled on the endpoints at the first
profile distribution.
Tivoli management region
A Tivoli region contains three tiers of resources: the Tivoli server, managed nodes
and gateways, and endpoints.
In a Tivoli environment, a managed resource is a database object that represents a
system or network resource and is governed by policies. A resource is a hardware,
software, or data entity that is managed by Tivoli software. Anything that affects
the operation of a computer system is a resource, for example, physical and logical
disks, CPUs, memory, printers, processes that are running, and service such as
LanMan, Windows event log, UNIX syslogd (logging system daemon), and
TCP/IP.
Tivoli management region server
Tivoli Management Framework software provides the base component for
Tivoli products. The computer in which this software is installed becomes
the Tivoli management region server. The Tivoli server includes the libraries,
binaries, data files, and the graphical user interface (GUI) (the Tivoli
desktop) that are required to install and manage your Tivoli environment.
See “Tivoli Management Framework” on page 50 for more information.
Managed nodes
A managed node runs the same software that runs on a Tivoli server.
Managed nodes maintain their own object databases that can be accessed
by the Tivoli server. When managed nodes communicate directly with
other managed nodes, they perform the same communication or security
operations that the Tivoli server performs.
Typically, you add managed nodes to share the work load of the Tivoli
server. The difference between a Tivoli server and a managed node is that
the Tivoli server object database is global to the entire region including all
managed nodes. In contrast, the managed node database is local to the
particular managed node.
To manage a computer system that hosts the managed node, install an
endpoint on that managed node.
Gateways
A gateway controls communication and operations with endpoints. Each
Appendix C. Tivoli basics 49
gateway can support thousands of endpoints. A gateway can launch
methods on an endpoint or run methods on behalf of the endpoint.
A gateway is generally created on an existing managed node. This
managed node provides access to the endpoint methods and provides the
communication with the Tivoli server that the endpoints occasionally
require.
Endpoints
Endpoints communicate with the Tivoli management region through
assigned gateways. An endpoint can be created on UNIX or PC operating
systems, including Windows NetWare and OS/2. An endpoint runs the
IBM Tivoli Monitoring engine.
Components of a Tivoli environment
The following sections provide descriptions of the components in the Tivoli
environment.
Tivoli Management Framework: Tivoli Management Framework is the base
component for Tivoli products. Using Tivoli Management Framework and a
combination of Tivoli software, you can manage large distributed networks with
multiple operating systems, various network services, diverse system operations,
and constantly changing nodes and users.
The Tivoli Management Framework function in your IBM Tivoli Monitoring
software is installed in your Tivoli management region or on your Tivoli
management region server. When installed, you have the following tools for
managing your resources:
Policy regions
The policy region is the entry point into the management functions for
your software installations. It is installed on your administrator desktop.
Task libraries
Each IBM Tivoli Monitoring software contains two or more task libraries.
The name of each task library indicates the type of tasks that the task
library contains. For example, configuration task libraries contain tasks that
support the discovery and Tivoli configuration functions. Operations task
libraries contains tasks that support the daily operations for managing
resources.
Profile managers
A profile manager contains resource model profiles for monitoring your
resources.
Profiles
A profile contains the resource models for monitoring your resources.
Resource models
The resource models provide best practices monitoring functions for your
resources.
IBM Tivoli Enterprise Console event classes and rules
The event classes and rules provide a set of event definitions for viewing
changes on your IBM Tivoli Enterprise Console console, and provide a set
of rules that aggregate and consolidate events to minimize IBM Tivoli
Enterprise Console event traffic.
Icons for resources
Icons represent various resources in your software. Context menus from
50 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
which you can easily access the functions required to manage a resource
are available using the following icons:
v Software icon on your administrator desktop
v Resource icons, one icon for each resource or object being managed
IBM Tivoli Monitoring is installed on the Tivoli management region server. This
application provides three important monitoring elements:
Profile
The profile is a collected set of information corresponding to a Tivoli
application resource. For example, the profile contains resource models that
define monitoring configurations that monitor specific criteria in your
environment.
Heartbeat
A heartbeat function regularly monitors endpoints to verify that they are
available and running correctly. This function provides notification if the
engine on an endpoint fails. The heartbeat function is enabled on the
gateway of the monitored endpoints. The heartbeat monitoring function
sends events to IBM Tivoli Enterprise Console and IBM Tivoli Business
Systems Manager (provided that the IBM Tivoli Business Systems Manager
Adapter component is installed at the gateway) and sends notices to the
IBM Tivoli Monitoring notice group.
Data collector
The data collector is a component that uploads data from the endpoints to
the RIM database for data collection. This RIM database can be the same
database that is used for IBM Tivoli Enterprise Console or a separate
database.
Administrators
Tivoli administrators are system administrators who have the authorization to
perform system or resource management tasks using the Tivoli monitoring
environment. Each administrator or group of administrators is represented by an
icon on the Tivoli desktop.
The IBM Tivoli Monitoring for Databases: Sybase ASE fully integrates into Tivoli
security. To perform administration functions, administrators must have
authorization roles for both IBM Tivoli Monitoring and the Tivoli environment.
Authorization roles
Authorization roles determine the range of actions an administrator can perform.
You assign roles to administrators so they can perform system or resource
management tasks. A role can be over the entire Tivoli management region or over
a specific set of resources, such as those contained in a policy region. Super, senior,
admin, and user are examples of standard authorization roles.
IBM Tivoli Monitoring for Databases: Sybase ASE provides the following
additional authorization roles:
v SybaseMon_IXB_user
v SybaseMon_IXB_admin
v SybaseMon_IXB_senior
v SybaseMon_IXB_super
Appendix C. Tivoli basics 51
User interface options
You can use the following interfaces to work with IBM Tivoli Monitoring for
Databases: Sybase ASE:
v The Tivoli desktop, which is the traditional Tivoli graphical user interface (GUI)
v The command-line interface (CLI)
v IBM Tivoli Monitoring Web Health Console to monitor the health of resource
models
v IBM Tivoli Enterprise Console to work with event management
v IBM Tivoli Business Systems Manager to work with event management and to
run some tasks
v Tivoli Data Warehouse to gather data about your resources
In many cases, this guide provides procedures for executing from either the
desktop or the command-line interface (CLI). You can choose to use the desktop
when you want to take advantage of visual input prompting, which includes
drop-down lists of options, and the defaults provided by options. Use the
command-line interface when you want to create scripts, set tasks to respond to
resource models, and rapidly enter commands.
Accessing the Tivoli Management Framework environment
Objective
To access the Tivoli Management Framework environment so that you can use the
operations and functions of IBM Tivoli Monitoring software.
Background information
You can access the Tivoli Management Framework desktop (Tivoli desktop) or the
Tivoli command line interface in order to use the operations and functions of IBM
Tivoli Monitoring software.
The Tivoli desktop is a user interface that provides point-and-click access to IBM
Tivoli Monitoring for Databases: Sybase ASE features and functions. The Tivoli
desktop provides a central control point for you to organize, manage, and delegate
system management operations.
The IBM Tivoli Monitoring for Databases: Sybase ASE also provides a
command-line interface (CLI) that enables you to enter commands from the
keyboard. You can use these commands in shell scripts and with system utilities
such as the UNIX cron utility. For more information about using commands, refer
to the Tivoli Management Framework Reference Manual.
Required authorization role
At a minimum, you need the user role to access the Tivoli environment. You will
need additional authorization for various operations, according to the
authorization system that a Tivoli administrator at you company sets up.
Before you begin
Not applicable.
When you finish
Not applicable.
52 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Procedure
There are separate logon procedures for UNIX and Windows. For a Windows
operating system, use the Windows menu structure. For a UNIX operating system,
use the UNIX command line.
UNIX: accessing the command-line interface and the Tivoli
desktop
1. Log on to a UNIX managed node or Tivoli management region server.
2. Run the environment initialization and setup script.
v If you are using the Bourne, Korn, or bash shell, run the following command:
. /etc/Tivoli/setup_env.sh
v If you are using the C shell, run the following command:
source /etc/Tivoli/setup_env.csh
You can use the command line to work with the Tivoli environment or you can
use the Tivoli desktop. The next step describes how to launch the Tivoli
desktop in UNIX.
3. Type the tivoli command at a command prompt to bring up the Tivoli logon
screen.
Windows: accessing the command-line interface
1. Log on to a Windows managed node or Tivoli management region server.
2. Launch a command prompt window.
3. Run the environment initialization and setup script:
%SystemRoot%\system32\drivers\etc\setup_env
where %SystemRoot% is the root directory of the Windows operating system.
4. Type the tivoli command at a command prompt to bring up the Tivoli logon
screen.
Windows: accessing the Tivoli desktop
1. Log on to a Windows managed node or Tivoli management region server.
2. Click Start → Programs →Tivoli → Tivoli in the Windows task bar to access the
login screen of the Tivoli desktop.
Note: If you are using a port other than port 94, configure the shortcut to
include ″-port port number″.
3. Type the following values in the fields of the login screen:
Host Machine
Specifies the Tivoli managed node to which the Tivoli desktop should
connect.
Specify the unique domain name for the host name when multiple
computers in the system have the same host name, or it in necessary to
reach the host. For example, the fully qualified name of the tokyo
computer might be tokyo.sales.mycompany.com, where sales is the
domain name of the Sales Department’s domain at the company
mycompany. The full name distinguishes the Sales Department’s server
from a tokyo server in the marketing domain called
tokyo.marketing.mycompany.com.
Log In As
Specifies the login name to the managed node.
Appendix C. Tivoli basics 53
Password
Specifies the password for the specified login name.4. Click OK to open the Tivoli desktop.
Backing up Tivoli databases
Objective
To back up existing Tivoli object databases for all computers in the Tivoli
management region so you can use these backup copies to restore them to a
known working state if you encounter a problem during installation.
Background information
See the Tivoli Management Framework Reference Manual for a description of all the
capabilities of the wbkupdb command. See the Tivoli Management Framework
Maintenance and Troubleshooting Guide for information and planning details
regarding Tivoli backups.
As an extra precaution you can save a compressed version (.tar or .zip format) of
the Tivoli installation directory, because a Tivoli backup does not back up other
Tivoli data such as binaries or libraries. A Tivoli backup backs up only information
in the Tivoli database. You should include all Tivoli servers and file servers in the
full system backups normally performed in your organization using a backup
solution.
For information and planning details regarding restoration of the Tivoli databases
that you back up, see the Tivoli Management Framework Maintenance and
Troubleshooting Guide. “Command line” includes an example of a command to
restore a database.
Required authorization role
backup or super
Note: The default directory to which backup files are written has root write
permissions only. If you cannot log in as the root administrator, you must
change the location of the backup file to a directory for which you have
write access.
Before you begin
You must have a valid user login name and a group name for the computer on
which the backup file is stored.
On UNIX, set umask to 022 for root.
When you finish
None.
Procedure
You can perform backups from the command-line interface (CLI) or in the Tivoli
desktop.
You can perform restore operations from the command-line interface only.
Command line: Use the wbkupdb command.
54 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Examples of backing up Tivoli databases: The following example backs up the Tivoli
databases for all managed nodes in the Tivoli management region from which the
wbkupdb command is run. The backups are written to the user-defined file
/usr/backups/TMR1.bk.
wbkupdb -d /usr/backups/TMR1.bk
where -d specifies the file or device to which the backup file is saved or from
which the backup file is retrieved.
The following example backs up the database of a single managed node, sherman.
In this example, the backup file is saved to the default location.
wbkupdb sherman
Example of restoring a Tivoli database: The following example restores a single
managed node, sherman. The -r flag restores the backed up database on sherman.
The -d flag identifies /usr/backups/TMR1.bk as the backup file to restore.
wbkupdb -r -d /usr/backups/TMR1.bk sherman
See the Tivoli Management Framework Maintenance and Troubleshooting Guide for
information on restoring files that you back up.
Tivoli desktop:
1. Select Backup from the Desktop menu to display the Backup Tivoli
Management Region window.
2. Select one or more managed nodes from the Available managed nodes
scrolling list.
3. Click the left-arrow option to move them to the Backup these managed nodes
area.
4. Type the name of the managed node on which the backup image or device is
located in the Save image on node field.
5. Type the full path name for the backup file in the Device/File field.
6. Click Start Backup to display the Backup Status window and begin backup
operation.
7. Close the Backup Status window.
8. Click Close to close the Backup Tivoli Management Region window and
display the Tivoli desktop window.
Appendix C. Tivoli basics 55
56 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix D. Task reference
A task is an action that can be routinely performed on selected managed resources
throughout the network. A task defines the executables to be run, the authorization
role required to execute the task, and the user or group name under which the task
executes.
You can invoke the tasks in various ways as noted in Table 13.
Table 13. Ways to invoke tasks
Task name Page How to invoke the task
Task library Policy region Context
menu for the
managed
resource
CLI IBM Tivoli
Enterprise
Console
IBM Tivoli
Business
Systems
Manager
Configure Event
Server
58 yes yes no yes no no
Discover 63 yes yes yes yes no no
See the Tivoli Management Framework documentation for more information about
tasks.
This appendix provides the following information for each IBM Tivoli Monitoring
for Databases: Sybase ASE task:
Description
Brief description of the task
Authorization roles
IBM Tivoli Monitoring for Databases: Sybase ASE and Tivoli authorization
roles required to run the task
Target managed resource
Tivoli managed resource to which the task is distributed
Parameters
Description of the parameters that can be set for the task in the task
window or in the command-line interface
CLI example
Sample wruntask command that invokes the task
Return codes
Information that the task returns such as status or availability
Usage notes
Additional notes relevant to using the task
© Copyright IBM Corp. 2004 57
Configure Event Server
Description
Configures the IBM Tivoli Enterprise Console event server to include event classes
and rules so the IBM Tivoli Enterprise Console server is set up to accept IBM
Tivoli Monitoring for Databases: Sybase ASE events and run IBM Tivoli Monitoring
for Databases: Sybase ASE rules.
Authorization roles
senior
Target managed resource
Managed Node where IBM Tivoli Enterprise Console server is installed
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
You must enter CLI parameters in the order in which they are listed in the table.
See example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Not applicable -t ″Configure Event
Server″
Name of the task to run: Configure Event Server
Not applicable -l ″IBM Tivoli
Monitoring Component
Services Tasks″
Name of the task library where this task is located
Event Server node to
configure
-h ″tec_managed_node ″ Managed node where the Event Server is installed:
Command line: If you run the task against a managed node that
is not an IBM Tivoli Enterprise Console server, the task starts to
run, then gives you an error. This is only possible from the
command line, where the target node is a free-form argument.
Tivoli desktop: Select the managed node that is filled in by
default as the managed node hosting the Event Server. Any
managed nodes that are not IBM Tivoli Enterprise Console servers
are not presented as options.
Not applicable -m ″timeout_in_seconds″ Amount of time in seconds that the task has to complete. If the
task does not complete in less than the specified amount of time,
an error is returned to whoever invoked the task saying that the
timeout has expired. However, the task continues to run in the
background until it completes. If a value of 0 is specified for the
timeout, the timeout is disabled and the system waits indefinitely
for the task to complete.
58 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Rule Base
Configuration
(Required)
v Create New Rule
Base
v Create New Rule
Base From Existing
v Update Current®
Rule Base
-a ″CREATE|CLONE|UPDATE″
Use the Tivoli desktop option or the parameter for the command
line that is in parentheses:
v Create New Rule Base (CREATE) creates a new rule base that
has not been initialized with an existing rule base. You must
specify the new rule base name and the path to the new rule
base in the fields or parameters for these names.
v Create New Rule Base From Existing (CLONE) creates a new
rule based on an existing rule base (also called cloning). If you
have not previously created a rule base, use ″Default.″ You
must specify the new rule base name and the path to the new
rule base in the fields or parameters for these names
v Update Current Rule Base (UPDATE) updates an existing rule
base.
Rule Bases -a ″″ The rule base names in this field depend on the rule base
configuration:
v If creating a new rule base not based on an existing rule base,
this field is not active. If no value is needed, specify ″″.
v If creating a new rule base from an existing rule base, this field
contains the names of existing rule bases.
v If updating a current rule base, this field contains the names of
rule bases that can be updated.
New Rule Base
Name
-a ″New_Rule_Base_ \Name″
Name of the rule base to be created
Use a new name that is not currently in use. If you type the name
of an existing rule base, this task issues a message and does not
update the existing rule base.
New Rule Base Path -a ″New_Rule_Base_Path″ Pathname on the event server managed node where the files
related to this rule base are stored
When you run the task on the Tivoli desktop, enter the full path
for the new rule base. The default path is $BINDIR/TME/TEC.
The task appends the name of the new rule base to this field
value to determine the complete path of the new rule base.
Event Forwarding:
Host Name
-a ″″ Not applicable to IBM Tivoli Monitoring for Databases: Sybase
ASE
Event Forwarding:
Port
-a ″″ Not applicable to IBM Tivoli Monitoring for Databases: Sybase
ASE
Forward to TBSM -a ″ON|OFF″ Forward events to IBM Tivoli Business Systems Manager. If the
value is set to ON, events are forwarded to IBM Tivoli Business
Systems Manager. If the value is OFF, events are not forwarded to
IBM Tivoli Business Systems Manager.
Appendix D. Task reference 59
Field name for the
Tivoli desktop
Command-line
parameters for the
wruntask command
Description
Rule Base Activation -a ″LOADONLY|RESTART|″″″
Use the Tivoli desktop option or the parameter for the command
line that is in parentheses:
v Do Not Activate (″″) creates or updates the rule base, but does
not upload the rule base to the event server. Use this option to
review rule base changes before you activate them.
v Load Rule Base Only (LOADONLY) creates or updates the
rule base and uploads it to the event server. The new rule base
is active when the event server is restarted.
v Load Rule Base and Restart Server (RESTART) creates or
updates the rule base, uploads it to the event server, and
restarts the event server.
Product to configure
(Required)
-a ″file_name″ Filename for the product you want to configure. For IBM Tivoli
Monitoring for Databases: Sybase ASE this is:
SybaseMon.pac
Note: You must supply an argument for each -a parameter. If you are not using
one of the properties, you must supply it as a null (″″) property.
CLI example
The following example configures the IBM Tivoli Enterprise Console event server
for IBM Tivoli Monitoring for Databases: Sybase ASE for the managed node named
Tec_Managed_Node in less than 15 minutes. It creates ″NewRule″ rule base by
making a copy of the existing default rule base and updating the copy with the
IBM Tivoli Monitoring for Databases: Sybase ASE event classes and rules. The path
for the new rule base is c:/Tivoli/bin/w32-ix86/TME/TEC. Events are not
forwarded to IBM Tivoli Business Systems Manager. After the rule base is created
and uploaded to the event server the event server restarts.
wruntask -t "Configure Event Server" \
-l "IBM Tivoli Monitoring Component Services Tasks" \
-h "@ManagedNode:Tec_Managed_Node" \
-m "900" \
-a "CLONE" \
-a "Default" \
-a "NewRule" \
-a "c:/Tivoli/bin/w32-ix86/TME/TEC" \
-a "" \
-a "" \
-a "OFF \
-a "RESTART" \
-a "SybaseMon.pac"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code. The only action the task takes is
to exit.
60 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Return
code
Displayed
code
Description Action
1 AMG8154E The task needs to include the Tmw2k.baroc file
supplied by IBM Tivoli Monitoring, but this file
was missing. The likely cause is that IBM Tivoli
Monitoring was not installed.
Re-install IBM Tivoli Monitoring
1 AMG8039E The listed baroc file specified by IBM Tivoli
Monitoring for Databases: Sybase ASE for
inclusion in its rulebase was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8003E The listed rules file specified by IBM Tivoli
Monitoring for Databases: Sybase ASE for
inclusion in its rulebase was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8004E The listed script file specified by the IBM Tivoli
Monitoring for Databases: Sybase ASE to be
installed on the IBM Tivoli Enterprise Console
server was not found.
Re-install IBM Tivoli Monitoring for
Databases: Sybase ASE.
1 AMG8102E The new rulebase you asked to create with the
given name already exists.
Specify another rulebase name
1 AMG8006E The rulebase you asked to clone does not exist. Specify an existing rulebase.
1 AMG8005E The rulebase you asked to update does not exist. Specify an existing rulebase.
1 AMG8103E You specified an invalid option to the Configure
Event Server task. The valid options are
CREATE, CLONE, and UPDATE.
Specify a valid system.
1 AMG8104E The path you specified to locate the rule base in
is invalid. Components of the path may not
exist, or the directory permissions may not allow
the task to write there.
Specify a valid rulebase path.
1 AMG8008E The task was unable to create the rulebase
directory specified by the user.
None.
1 AMG8139E The directory specified to contain the new
rulebase already exists. This can cause IBM
Tivoli Enterprise Console errors if the directory
contents are not consistent with the new rulebase
being created.
Remove the directory or choose a
different location and run the task
again.
1 AMG8012E Compilation of the rulebase failed. There are
most likely syntax errors in the baroc files, or the
baroc files depend on prerequisite classes that
were not included.
None.
1 AMG8014E Creation of the new rulebase in the IBM Tivoli
Enterprise Console server failed.
None.
1 AMG8016E Copying the existing rulebase into new rulebase
failed.
None.
1 AMG8018E Importing the given class into the rulebase
failed. There are most likely syntax errors in the
baroc file, or the baroc file depends on
prerequisite classes that were not included.
None.
1 AMG8106E Importing the given ruleset into the rulebase
failed.
None.
1 AMG8021E Creation of specified event source in the IBM
Tivoli Enterprise Console server failed.
None.
1 AMG8024E Event source already exists and could not be
deleted.
None.
Appendix D. Task reference 61
Return
code
Displayed
code
Description Action
1 AMG8112E The IBM Tivoli Enterprise Console event
forwarding that you requested did not supply
the necessary hostname to which events should
be forwarded.
None.
1 AMG8026E Loading the new rulebase into the IBM Tivoli
Enterprise Console server failed.
None.
1 AMG8037E The rulebase directory that is needed does not
exist.
None.
1 AMG8033E The IBM Tivoli Enterprise Console server failed
to restart.
None.
1 AMG8035E The task was run on a node which is not the
IBM Tivoli Enterprise Console server.
None.
1 AMG8038E The arguments passed to the task are incorrect. None.
1 AMG8040I The task completed successfully. None.
Usage notes
Because the scope of the Discover task is a Tivoli management region, use
managed nodes and endpoints that are within the same Tivoli management region.
Configure the Event Server by adding the event classes and rules related to this
application. You can configure only one Tivoli Enterprise Console event server for
each Tivoli management region. When you have interconnected Tivoli management
regions, run the Configure Event Server task against each Tivoli management
region that contains a Tivoli Enterprise Console event server.
62 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Discover
Description
Creates the objects that represent the managed resources you want to monitor.
Authorization roles
SybaseMon_IXB_senior
Target managed resource
Managed node on which the object is created
The managed node varies depending on how the Discover task was invoked. If
you invoke from the task from the IBM Tivoli Monitoring for Databases: Sybase
ASE policy region icon context menu (right-click on the icon), then the managed
node is the Tivoli management region server. If you invoke the task from the IBM
Tivoli Monitoring for Databases: Sybase ASE Utility Tasks task library, you can
select which managed node to run the task on.
Parameters
This task accepts the parameters listed in the following table. The Field name
column contains the information for the fields you complete when using the Tivoli
desktop GUI. These are not in the order in which they appear on the Tivoli
desktop. The Command-line column contains the corresponding parameters that
you use in the wruntask command for this task. The parameters are listed in the
order in which they must appear in syntax. The Description column contains a
brief description of each of the parameters. Refer to the Tivoli Management
Framework Reference Manual for more information about the wruntask command.
See the example of CLI syntax below the table.
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable -t ″Discover″ Name of the task to run: Discover
Not applicable -l ″Monitoring for Sybase ASE Utility
Tasks″
Name of the task library in which this task is
located
Not applicable -h ″managed_node_where_the_task_will_run″ Name of the managed node on which to run the
task
Endpoint List -a ″@Endpoint:epName1@Endpoint:epName2″
List of endpoints on which to search for resources
to monitor
Tivoli desktop: Select endpoints that run Sybase
ASE.
Command line: Include one or more endpoint
names separated by a space. Surround the entire
list with double quotation marks.
Object Host -a ″managed_node_name_on_which_the_task_
\is_to_create_the_objects″
Name of the managed node where the managed
resource objects representing the discovered
applications are to be created.
Endpoint task
timeout (seconds)
-a ″integer_value_in_seconds ″ Maximum number of seconds that the task runs
on each endpoint to search for application
configurations. The gateway timeout value should
be greater than or equal to this value.
Appendix D. Task reference 63
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Monitor on
discover?
-a ″yes|no″ The monitoring profile is not automatically
distributed to all discovered instances after the
Discover task runs. Application instances are
discovered; the corresponding object instances are
created; and the objects are added to the
subscription list of the monitoring profile. Then,
the profile is distributed or not:
v No: The profile is not distributed.
v Yes: The profiles are distributed to each
discovered instance.
Send notification to
TBSM?
-a ″yes|no″ Whether or not you want to notify IBM Tivoli
Business Systems Manager that a managed
resource was discovered
TEC Server Name -a ″TEC_Server_name″ Name of the IBM Tivoli Enterprise Console Server
to which to send the events.
The value must one of the following:
@EventServer, @EventServer#region_name, or for
non-TME TEC servers, host_name or IP address.
If this parameter is blank (-a ″″ in the command
line), the events are sent to the default IBM Tivoli
Enterprise Console server for the policy region.
For additional information see the IBM Tivoli
Enterprise Console Adapters Guide.
TEC Server Port -a ″port_number″ Port number for which the IBM Tivoli Enterprise
Console server was configured to listen for
events. The default is the IBM Tivoli Enterprise
Console default of 5529.
Sybase identifier -a ″SybaseASEServer_AP_\SYBASE_IDENTIFIER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This identifies the
Sybase ASE Server. Choose a unique value for
each Sybase ASE Server to be monitored. This
value can only contain alphanumeric values.
Sybase installation
path
-a ″SybaseASEServer_AP_\SYBASE_INSTALL_PATH
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the installation
path of Sybase. This path should contain the
trailing delimitier, for example ’C:\sybase\’ or
’/opt/sybase/’
Operating system
user id
-a ″SybaseASEServer_AP_\SYBASE_OS_USER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the operating
system user id to be used to start and interact
with Sybase.
64 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Sybase user id -a ″SybaseASEServer_AP_\SYBASE_USER
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is a Sybase user ID
used to log into Sybase which has been granted
the mon_role.
Sybase password -a ″SybaseASEServer_AP_\SYBASE_PASSWORD
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the password
for the user ID specified. This value must not be
NULL or an empty string.
Sybase Server name -a ″SybaseASEServer_AP_\SYBASE_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server name.
Sybase Backup
Server name
-a ″SybaseASEServer_AP_\SYBASE_BACKUP_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Backup Server name.
Sybase Monitor
Server name
-a ″SybaseASEServer_AP_\SYBASE_MONITOR_SERVER_NAME
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Monitor Server name.
Sybase Adaptive
Server log file name
-a ″SybaseASEServer_AP_\LogMonitorLogname
-a value″
Tivoli desktop: Enter values in the fields.
Command line: Enter values in pairs where the
first value is the variable name and the second is
the value of the variable. Specify each value with
a separate ″-a″ parameter. This is the Sybase
Adaptive Server log file name.
Appendix D. Task reference 65
Field name for the
Tivoli desktop
Command-line parameters for the
wruntask command
Description
Not applicable [-m ″integer_value″] Managed node timeout for the completion of this
task. If Discover runs against a large number of
endpoints, make this timeout longer than
normally needed for a task that runs against one
endpoint. This task runs in 2 phases. The first
phase runs on the managed node. During this
phase, another task is executed on each of the
selected endpoints. These are executed in groups,
but any of these endpoints can fail to complete
the task (for example, if the endpoint is not
running). This can cause each of the stages to take
the full default task timeout. If this happens, you
must make the timeout on the Discover task long
enough to allow each of the endpoint stages to
complete.
Note: Supply an argument for each -a parameter. If you are not using one of the
properties, you must supply it as a null (″″) property.
CLI example
The following example runs the Discover task on the ″vertical″ managed node,
searches the ″vertical″ and ″extreme″ endpoints, and puts the objects that it creates
on the vertical managed node. The task is set to run on each endpoint for a
maximum of 1 minute. The task is not set up to distribute the profile or notify IBM
Tivoli Business Systems Manager that a resource was discovered. The events are to
be sent to the default IBM Tivoli Enterprise Console server for the policy region at
port number 5529. The task has 10 minutes to complete.
The following variables and their values (shown in parentheses) are set up:
v SybaseASEServer_AP_SYBASE_IDENTIFIER (server1)
v SybaseASEServer_AP_SYBASE_INSTALL_PATH (/opt/sybase/)
v SybaseASEServer_AP_SYBASE_OS_USER (sybase)
v SybaseASEServer_AP_SYBASE_USER (sa)
v SybaseASEServer_AP_SYBASE_PASSWORD (secret)
v SybaseASEServer_AP_SYBASE_SERVER_NAME (server1)
v SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME (server1_BS)
v SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME (server1_MS)
v SybaseASEServer_AP_LogMonitorLogname (/opt/sybase/ASE-12_5/install/server1.log)
wruntask -t Discover \
–l "Monitoring for Sybase ASE Utility Tasks" \
–h "@ManagedNode:vertical" \
–a "@Endpoint:vertical @Endpoint:extreme" \
–a "vertical" \
–a "60" \
–a "no" \
–a "no" \
–a "@EventServer" \
–a "5529" \
–a "SybaseASEServer_AP_SYBASE_IDENTIFIER" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_INSTALL_PATH" \
–a "/opt/sybase/" \
66 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
–a "SybaseASEServer_AP_SYBASE_OS_USER" \
–a "sybase" \
–a "SybaseASEServer_AP_SYBASE_USER" \
–a "sa" \
–a "SybaseASEServer_AP_SYBASE_PASSWORD" \
–a "secret" \
–a "SybaseASEServer_AP_SYBASE_SERVER_NAME" \
–a "server1" \
–a "SybaseASEServer_AP_SYBASE_BACKUP_SERVER_NAME" \
–a "server1_BS" \
–a "SybaseASEServer_AP_SYBASE_MONITOR_SERVER_NAME" \
–a "server1_MS" \
–a "SybaseASEServer_AP_LogMonitorLogname" \
–a "/opt/sybase/ASE-12_5/install/server1.log" \
–m "600"
See the Parameters section for descriptions.
Return codes
The following table shows the return code, the displayed code, a description, and
the action that the task takes for each return code.
Return
code
Displayed
code
Description Action
0 The task completed. Verify that the results indicated
match the expected results.
Usage notes
The object host managed node, gateway, and target endpoint must be in the same
Tivoli management region from which the task is being executed.
Appendix D. Task reference 67
68 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix E. Uninstalling the product
This section describes how to uninstall the following software:
v IBM Tivoli Monitoring for Databases: Sybase ASE
v Software that enables communication with IBM Tivoli Business Systems
Manager
Note: Uninstall IBM Tivoli Monitoring for Databases: Sybase ASE before you
uninstall IBM Tivoli Monitoring Component Services. IBM Tivoli
Monitoring for Databases: Sybase ASE must be able to reference IBM
Tivoli Monitoring Component Services during the uninstallation process.
For information on uninstalling related software, see the documentation for the
related software. For example, see the documentation for IBM Tivoli Monitoring to
learn how to uninstall that product.
If you want to uninstall the entire Tivoli environment, you must uninstall the
software in the following order:
1. IBM Tivoli Monitoring for Databases: Sybase ASE (an IBM Tivoli Monitoring
monitoring product)
2. All other specialized IBM Tivoli Monitoring monitoring products, for example,
IBM Tivoli Monitoring for Databases or IBM Tivoli Monitoring for Business
Integration.
Note: Stop the uninstall process here if you want to continue using other
specialized IBM Tivoli Monitoring products. Continue the uninstall
process if you want to remove all specialized monitoring software.
3. IBM Tivoli Monitoring Component Services
Note: You must uninstall all specialized IBM Tivoli Monitoring monitoring
products before you uninstall IBM Tivoli Monitoring Component
Services because these products must be able to reference IBM Tivoli
Monitoring Component Services during the uninstall process.
4. IBM Tivoli Monitoring
5. The Tivoli Management Framework
Consult the documentation for the Tivoli Management Framework for complete
uninstallation instructions.
Uninstalling IBM Tivoli Monitoring for Databases: Sybase ASE
Objective
To remove IBM Tivoli Monitoring for Databases: Sybase ASE from the Tivoli
management region server.
Background information
Uninstalling IBM Tivoli Monitoring for Databases: Sybase ASE removes the
product’s task libraries, policy regions, profiles, and resource models from the
Tivoli environment.
© Copyright IBM Corp. 2004 69
Required authorization role
senior, super, and SybaseMon_IXB_senior
Before you begin
None.
When you finish
None.
Procedure
1. Access the Tivoli environment as described in “Accessing the Tivoli
Management Framework environment” on page 52.
2. Run the following command:
wuninst SybaseMon Tivoli_server [-rmfiles] [-rmepfiles]
where Tivoli_server is the name of the managed node that is the Tivoli server.
Specify the -rmepfiles option to ensure that the endpoint files are removed.
This option is only necessary when managed resource objects reside on
managed nodes other than the Tivoli management region server.″
Uninstalling IBM Tivoli Monitoring Component Services
Objective
To remove IBM Tivoli Monitoring Component Services from the Tivoli
environment.
Note: You must uninstall all specialized IBM Tivoli Monitoring monitoring
products before you uninstall IBM Tivoli Monitoring Component Services
because these products must be able to reference IBM Tivoli Monitoring
Component Services during the uninstall process.
Background information
Uninstalling IBM Tivoli Monitoring Component Services removes it from the Tivoli
environment.
IBM Tivoli Monitoring Component Services is a required prerequisite for all
specialized IBM Tivoli Monitoring software, for example, IBM Tivoli Monitoring
for Databases or IBM Tivoli Monitoring for Messaging and Collaboration. Both
installation and uninstallation of IBM Tivoli Monitoring monitoring products must
reference IBM Tivoli Monitoring Component Services.
Note: Do not uninstall IBM Tivoli Monitoring Component Services when you want
to continue using any specialized IBM Tivoli Monitoring software. It is
imperative that you uninstall all specialized IBM Tivoli Monitoring
monitoring products before you uninstall IBM Tivoli Monitoring Component
Services. Otherwise, you will experience these problems:
v Operations: You will be unable to run any IBM Tivoli Monitoring
monitoring products that you want to continue running. Standard
resource models for the specialized IBM Tivoli Monitoring software will
stop working. Also the objects that represent instances of Sybase ASE,
instances of the LogFile resource models, custom resource models and
other features of the various IBM Tivoli Monitoring monitoring products
will stop working.
70 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
v Uninstall: Uninstallation of IBM Tivoli Monitoring monitoring products
will fail.
Required authorization role
senior and super
Before you begin
Uninstall all specialized IBM Tivoli Monitoring products. For example, IBM Tivoli
Monitoring for Databases: Sybase ASE must be uninstalled before you perform this
procedure.
When you finish
None.
Procedure
1. Access the Tivoli environment as described in “Accessing the Tivoli
Management Framework environment” on page 52.
2. Run the following command:
wuninst ITMCmptSvcs Tivoli_server [-rmfiles]
where Tivoli_server is the name of the managed node that is the Tivoli server.
Uninstalling IBM Tivoli Monitoring for Databases: Sybase ASE
integration from IBM Tivoli Business Systems Manager
Objective
To remove IBM Tivoli Monitoring for Databases: Sybase ASE integration program
from IBM Tivoli Business Systems Manager.
Background information
Uninstalling IBM Tivoli Monitoring for Databases: Sybase ASE integration program
removes the resource definitions and objects from IBM Tivoli Business Systems
Manager.
Required authorization role
Administrator authority on the IBM Tivoli Business Systems Manager server.
Before you begin
None.
When you finish
After you uninstall the product from the IBM Tivoli Business Systems Manager
server, manually delete any Business Systems that were created on the IBM Tivoli
Business Systems Manager Business Systems view for this product. The
Automated Business Systems might have created these Business Systems. You
should also remove references to this product from your Automated Business
Systems.
Procedure
Use the following steps to perform this procedure:
1. From a command prompt on the IBM Tivoli Business Systems Manager server,
navigate to the directory where you installed IBM Tivoli Monitoring for
Databases: Sybase ASE integration program. The default directory is
c:\tivoli\itmIXB.
2. Type uninstall to start the uninstallation wizard.
Appendix E. Uninstalling the product 71
3. Click Next on the welcome screen.
4. The installation location for the IBM Tivoli Business Systems Manager
integration program is displayed. Click Next to continue.
5. Provide the following Microsoft® SQL Server information and click Next to
start the uninstallation:
SQL Server
The name of the SQL server with which this IBM Tivoli Business
Systems Manager server is associated
SQL Userid
The SQL user ID
SQL Password
The password for the user ID defined above6. Click Finish to exit the installation wizard.
72 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix F. Installing IBM Tivoli Monitoring for Databases:
Sybase ASE and a complete Tivoli environment
This chapter describes how to use an installation utility to install IBM Tivoli
Monitoring for Databases: Sybase ASE with a complete Tivoli environment, which
includes the Tivoli Management Framework, IBM Tivoli Monitoring, and IBM
Tivoli Monitoring Component Services. You use this option on systems where no
Tivoli software currently exists.
Table 14 provides an overview of the installation process when you use the
installation utility.
Table 14. Guidelines for installation of a complete Tivoli environment
Goal Refer to
1. Obtain the installation software. “Obtaining source files for installing IBM Tivoli Monitoring
for Databases: Sybase ASE” on page 2
2. Create a hierarchy of files (a depot) for the
installation utility to reference.
“Creating a hierarchy of files for the installation utility to
reference” on page 74
3. Install the latest maintenance software for the
operating systems on which you plan to install the
product.
Refer to the following Web sites for the latest maintenance
software:
v For the Solaris Operating Environment:
http://sunsolve.sun.com
v For IBM AIX:
http://techsupport.services.ibm.com/rs6k/ml.fixes.html
v For HP-UX:
http://www.hp.com/products1/unix/java/infolibrary/patches.html
4. Verify that the computers on which you want to
install the product are recognized by the network.
Run a ping command to call each target computer. For
example, enter the following command in the MS-DOS
command prompt on Windows:
ping name
where name is the name of the target computer.
The target computer replies to the ping command with its
IP address and statistics regarding the transaction if the
name is valid, the network connection is active, and the
target computer is running.
5. Ensure that required processes are running on
computers where you plan to install endpoints or
supplemental Tivoli servers, called managed
nodes. (A managed node can host a gateway that
helps the Tivoli server manage large numbers of
endpoints.)
Note: You do not need to check for these
processes on the computer on which you run the
installation utility. This computer becomes the
principal Tivoli server and automatically receives
all required software.
“Verifying the availability of remote execution services” on
page 77
© Copyright IBM Corp. 2004 73
Table 14. Guidelines for installation of a complete Tivoli environment (continued)
Goal Refer to
6. (Optional) Complete planning sheets. You refer to
the planning sheets when the installation utility
prompts you for information. You can also use
the planning sheets if you plan to expand an
existing Tivoli environment.
“Completing installation planning sheets” on page 79
7. Install IBM Tivoli Monitoring for Databases:
Sybase ASE using the installation utility.
“Using an installation utility to install the product (for a
new Tivoli environment only)” on page 82
8. Install the optional software that you want to use
with IBM Tivoli Monitoring for Databases: Sybase
ASE, for example, IBM Tivoli Enterprise Console
and IBM Tivoli Business Systems Manager.
“Optional software” on page 43
9. If necessary, create a Windows proxy endpoint to
enable the creation of Windows endpoints when
you are installing through a UNIX-based Tivoli
management region server.
“Manually creating a Windows proxy endpoint” on page
89
10. Complete installation of the product as follows:
v Provide Java software to enable resource
model communications.
v (Optional) Send monitoring data to IBM Tivoli
Enterprise Console and IBM Tivoli Business
Systems Manager.
v Discover resources that are available to be
monitored.
v (Optional) Enable the product in languages in
addition to English.
Chapter 3, “Completing the installation,” on page 15
Creating a hierarchy of files for the installation utility to reference
Objective
To set up the required directory structure (called a depot) for installation files that
you download from the Web, so that you can perform an installation using the
installation utility.
Note: You do not need to create a depot when you run the installation utility from
CDs. In that case, the installation utility prompts you for the required CDs
during installation.
Background information
The procedure describes how to place the installation files that you downloaded
from the Web into a depot structure. The installation utility references the depot
during installation. You can reference a single depot located in the network to
perform installations on multiple computers. “Obtaining source files for installing
IBM Tivoli Monitoring for Databases: Sybase ASE” on page 2 describes how to
download the installation files.
Table 15 on page 75 lists the names of the product images that you download from
the Web and the directories that you must create to contain the files that result
from uncompressing the downloaded image files (.tar files).
74 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Note: You do not need to create a depot directory structure if you install from
CDs. See “Obtaining source files for installing IBM Tivoli Monitoring for
Databases: Sybase ASE” on page 2 for information about the CDs that you
need for installation.
Table 15. Download directories for an Evaluation or Typical installation
Download image name
Note: See the Passport Advantage Readme First for a list of full names of the
compressed files to download, decompress, and place in the depot structure.
Download directory
IBM Tivoli Monitoring for Databases, Version 5.1.2, Installation Disc 1 for
Sybase ASE
Any directory other than depot
IBM Tivoli Monitoring for Databases, Version 5.1.2, Installation Disc 2 for
Sybase ASE
depot/
Tivoli Management Framework v4.1.1 1 of 2 depot/TMF41Disk1
Tivoli Management Framework v4.1.1 2 of 2 depot/TMF41Disk2
Tivoli Management Framework Language Support v4.1.1 depot/TMF41Lang
Tivoli Monitoring Install V5.1.2 depot/ITM
Tivoli Monitoring Lang Support V5.1.2 depot/ITMLang
IBM Tivoli Monitoring for Databases, Version 5.1.2: Component Software
where application is the name of the application that you are going to monitor.
IBM Tivoli Monitoring for Databases, Version 5.1.2: Component Software"
depot/application
IBM Tivoli Monitoring for Databases, Version 5.1.2: Language Support
where application is the name of the application that you are going to monitor.
depot/applicationLang
Required authorization role
None.
Before you begin
Determine which Web download images you need. You must create directories
only for the downloaded files that you need. All Web download images listed in
“Obtaining source files for installing IBM Tivoli Monitoring for Databases: Sybase
ASE” on page 2 are required except as listed below:
v Language support download images are optional.
v IBM Tivoli Monitoring Web Health Console is optional if you use the Typical
option in the installation utility.
v The component software download images are optional.
When you finish
You are ready to install the product using the installation utility, as described in
“Using an installation utility to install the product (for a new Tivoli environment
only)” on page 82.
Procedure
1. Create a depot directory (depot) on the hard disk drive of the computer to
which you want to download the installation images.
2. Create another directory, separate from the depot directory, on the same
computer.
Appendix F. Installing the product and a complete Tivoli environment 75
Additional Information: This separate directory is required for the main
installation download image, indicated in the first row of Table 2 on page 3. All
other downloaded files are stored in the depot directory.
3. Create the required subdirectories within the installation depot.
Additional Information: You can create all of the directories listed in Table 15 on
page 75 or you can create just the subdirectories that correspond to the product
images required for your installation. For example, if you do not plan to install
the IBM Tivoli Monitoring Web Health Console, you do not need to create a
WHC directory.
4. On the Passport Advantage Web site, search for the e-assembly entitled IBM
Tivoli Monitoring for Databases: Sybase ASE.
5. Click the IBM Tivoli Monitoring for Databases: Sybase ASE link to open the
e-assembly.
6. Download the compressed product images (.tar files) to the appropriate
directories, as indicated in Table 15 on page 75.
Additional Information: For example, download the product image file that
corresponds to the image name listed in the first row of Table 15 on page 75 to
the directory that you created in Step 2 on page 75. Download the image file
that corresponds to the image name listed in the second row of the table into
the root level of the depot directory (depot/)
7. Uncompress the product images that you downloaded within their respective
directories.
8. Perform the following additional steps if you downloaded product images for
the IBM Tivoli Monitoring Web Health Console:
Note: The following steps show sample commands for UNIX. $depot
represents the depot directory. Use Windows Explorer to accomplish the
same results on Windows systems.
a. Create a new subdirectory named HCONSOLE at the root level of the
$depotdirectory ($depot/HCONSOLE).
cd $depot
mkdir HCONSOLE
b. Display all HCONSOLE subdirectories that exist within the depot directory.
ls */HCONSOLE
Additional Information: When you uncompress the product image files in
Step 7, several directories, including an HCONSOLE directory, are created
within each of the depot subdirectories for IBM Tivoli Monitoring for
Databases: Sybase ASE components. The HCONSOLE directories contain
class files for installation into IBM Tivoli Monitoring Web Health Console.
c. Move the contents of each of the component subdirectories to the top-level
HCONSOLE directory that you created in Step 8a. For example:
mv SybaseMon/HCONSOLE/* HCONSOLE
As an alternative to performing the preceding steps for Web Health Console
files, you can run one of the following programs:
v On UNIX, create and run the following shell script:
#!/bin/sh
# Change to depot dir
depot=/my/depotdir
cd $depot || ( echo "directory $depot does not exist" ; exit 1 )
# make the HCONSOLE dir
mkdir HCONSOLE
76 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
# Move all product HCONSOLE dirs
for i in */HCONSOLE ; do
mv $i/* HCONSOLE/.
done
v On Windows, create and run the following .bat file:
@echo off
set depot=\my\depotdir
REM Change to depot dir
cd %depot% || (
echo directory %depot% does not exist
EXIT /B 1
)
REM make the HCONSOLE dir
if NOT EXIST HCONSOLE mkdir HCONSOLE
REM Move all product HCONSOLE dirs
for /D %%i in ( * ) do (
if EXIST %depot%\%%i\HCONSOLE (
for %%j in ( %depot%\%%i\HCONSOLE\* ) do move %%j %depot%\HCONSOLE
for /D %%j in ( %depot%\%%i\HCONSOLE\* ) do move %%j %depot%\HCONSOLE
)
)
Verifying the availability of remote execution services
Objective
To verify the availability of remote execution services on the target computers that
you configure during installation.
Background information
One of the following basic execution daemons must be running on computers
where you intend to install managed nodes or endpoints:
v For installation on UNIX target computers, test the rexecd daemon.
v For installation on Windows target computers, test the Tivoli Remote Execution
Service (TRIP) process. If this service does not exist, run the setup.exe executable
in the TRIP directory of the software installation CD for Tivoli Management
Framework. Follow the instructions in the panels of the installation wizard to
complete the installation of this service.
Required authorization role
On UNIX, the user must have root privileges. On Windows, the user must have
membership in the Administrators group.
Before you begin
None.
When you finish
(Optional) Gather required installation information as described in “Completing
installation planning sheets” on page 79.
Install the product as described in “Using an installation utility to install the
product (for a new Tivoli environment only)” on page 82.
Procedure
Choose the appropriate access method for the machine that you want to enable by
selecting one of the buttons in the Access section of the window. The values for
User ID and Password vary depending on the operating system of the machine
that you are enabling:
Appendix F. Installing the product and a complete Tivoli environment 77
v To run REXEC on a Windows machine, type the user ID and password for the
Windows Administrator, not the Tivoli Administrator.
v To run REXEC on UNIX machines, type the user ID and password for the root
user. The login shell of this user must be Bourne or Korn shell.
Note: You can use this procedure for the following situations:
v You test connectivity from the command-line interface on a UNIX-based
computer to a remote UNIX-based computer or a remote Windows
computer.
v You test connectivity from the command-line interface on a Windows
computer to a remote UNIX-based computer or a remote Windows
computer.
Command line in a UNIX-based computer:
1. Run an rexec command string against the target computer. The rexec command
runs commands on remote hosts that are running the rexec service. For
example, run the following command:
rexec target_computer_name echo test
2. Respond to the prompt for a user ID and password by typing the root ID and
password for the target computer.
If the command is unsuccessful, you receive an error, for example, an
authentication error, a notice that the server is down, or a notice that rexec
failed to run. Do not proceed to “Using an installation utility to install the
product (for a new Tivoli environment only)” on page 82 until you can enable
the rexec daemon on the target computer.
Note: The syntax for the rexec command varies, depending on the operating
system you are using. You might have different syntax options than shown
in the example above.
Command line in a Windows computer:
1. Run an rexec command string against the target computer. The rexec command
runs commands on remote hosts that are running the rexec service. For
example, run the following command:
rexec target_computer_name cmd /c echo test
Note: The syntax for the rexec command varies, depending on the operating
system you are using. You might have different syntax options than
shown in the example above.
2. Respond to the prompt for a user ID and password by typing the
Administrator ID and password as follows:
v If the command is successful, go to “Using an installation utility to install the
product (for a new Tivoli environment only)” on page 82.
v If the command is unsuccessful, you receive an error, for example, an
authentication error, a notice that the server is down, or a notice that the
process failed to run. Complete the following steps before you proceed:
a. Log on to the target computer on which you want to confirm that the
Tivoli Remote Execution Service exists.
b. Access the Services user interface in the Windows control panel.
c. Find the Tivoli Remote Execution Service in the Services list and perform
one of the following actions:
– If this service exists and the status is ″Stopped,″ click Start.
78 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
—OR—
– If this service exists and the status is ″Started,″ resolve firewall blocks
or other network connectivity problems between this computer and the
computer on which you are installing IBM Tivoli Monitoring. For
example, you can increase access privileges to resolve some types
communication failure.
Completing installation planning sheets
This section provides planning sheets that you can use to gather information about
the Tivoli server, managed nodes, and endpoints that you plan to install using the
Typical option in the installation utility. You can also use the planning sheets if you
want to add managed nodes and endpoints to an existing Tivoli environment
before or after you install the product.
Table 16 provides brief descriptions of the types of managed resources that the
planning sheets cover: managed nodes, gateways on managed nodes, and
endpoints. For complete information about the architecture of a Tivoli
environment, refer to the publications for Tivoli Management Framework.
Table 16. Managed resources and their purpose
Managed resource Purpose
Managed nodes Create managed nodes on servers to supplement the Tivoli server. A managed node runs the
same software that runs on a Tivoli management region server. It can communicate with other
managed nodes and can help the Tivoli management region server manage endpoints. When a
managed node supplements the Tivoli management region server, you achieve the following
benefits:
v The managed nodes share the processing burden of the Tivoli management region server.
The Tivoli management region server works more efficiently because it performs fewer
management and user administration operations.
v Tivoli network transactions flow to multiple servers instead of to the Tivoli management
region server only.
Gateways Create gateways on managed nodes to enable the managed node to perform endpoint
management operations on behalf of the Tivoli server. A gateway transfers large amounts of
data to endpoints more efficiently. By default, the maximum amount of memory to use for
storing transient data is set to 10 MB. Always enable managed nodes for IBM Tivoli Monitoring
as gateways so that they can perform endpoint management operations.
When you perform a Typical installation for this product, the installation utility automatically
establishes gateways on the managed nodes that you create during installation. Be sure to
create gateways on any managed nodes that you create without using the installation utility.
Endpoints Create endpoints on the computers that you want to manage. Endpoints communicate with the
Tivoli management region through a specific gateway on a managed node.
Use the following planning sheets to gather the information you need during
installation:
v Planning sheet for creating managed nodes in Table 17 on page 80
v Planning sheet for creating endpoints in Table 18 on page 81
Appendix F. Installing the product and a complete Tivoli environment 79
Tabl
e 17
. P
lann
ing
shee
t fo
r cr
eatin
g m
anag
ed no
des
Key
C
once
pt:
At
leas
t on
e m
anag
ed no
de
mus
t ex
ist
in a
Tivo
li m
anag
emen
t re
gion
. Thi
s pr
inci
pal
man
aged
no
de
is ca
lled
th
e Ti
voli
serv
er.
Hos
t n
ame
Nam
e of
th
e ta
rget
com
pute
r in
th
e ne
twor
k
Gat
eway
n
ame
*
Nam
e of
th
e ga
tew
ay
**
Pla
tfor
m
Ope
rati
ng sy
stem
of
the
man
aged
no
de
Use
r n
ame
root
or
A
dm
inis
trat
or
Pas
swor
d
Pass
wor
d of
th
e us
er on
the
serv
er
Des
tin
atio
n of
in
stal
lati
on fi
les
Path
on
th
e ta
rget
co
mpu
ter
for
inst
alla
tion
of
th
e pr
oduc
t
Exa
mpl
e:
visi
on03
Exa
mpl
e:
visi
on03
_gw
Exa
mpl
e:
Sola
ris
Exa
mpl
e:
root
—
Exa
mpl
e:
/dat
a/my
node
* T
his
nam
e ca
n in
clud
e al
phan
umer
ic ch
arac
ters
, und
ersc
ores
(_
), hy
phen
s (-
), an
d pe
riod
s (.)
. The
na
mes
ar
e ca
se-s
ensi
tive
. For
ex
ampl
e, th
e na
me
GW
Nam
e is
dif
fere
nt fr
om gw
nam
e.
** Yo
u m
ust
crea
te a
gate
way
on
al
l m
anag
ed no
des
fo
r th
is pr
oduc
t. A
ga
tew
ay en
able
s th
e m
anag
ed no
de
to co
mm
unic
ate
wit
h en
dpo
ints
.
In a
Typi
cal
inst
alla
tion
, the
in
stal
lati
on ut
ility
au
tom
atic
ally
cr
eate
s a
gate
way
on
ev
ery
man
aged
no
de
that
yo
u cr
eate
. The
in
stal
lati
on ut
ility
cr
eate
s a
uniq
ue
nam
e fo
r th
ese
gate
way
s by
ad
din
g th
e _g
w su
ffix
to
th
e ho
st na
me.
You
mus
t pr
ovid
e a
valid
ho
st na
me
for
all
man
aged
no
des
an
d en
dpo
ints
th
at yo
u cr
eate
. Spe
cify
th
e un
ique
d
omai
n na
me
for
the
host
na
me
whe
n m
ulti
ple
com
pute
rs in
th
e sy
stem
ha
ve th
e sa
me
host
na
me.
Fo
r ex
ampl
e, th
e fu
lly qu
alif
ied
na
me
of th
e to
kyo
co
mpu
ter
mig
ht be
to
kyo
.sal
es.m
ycom
pan
y.co
m, w
here
sale
s is
th
e d
omai
n na
me
of th
e Sa
les
Dep
artm
ent’s
d
omai
n at
th
e co
mpa
ny m
ycom
pan
y. T
he fu
ll na
me
dis
ting
uish
es th
e Sa
les
Dep
artm
ent’s
se
rver
fr
om a
tok
yo
serv
er in
th
e m
ark
etin
g d
omai
n ca
lled
to
kyo
.mar
ket
ing.
myc
omp
any.
com
.
80 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Tabl
e 18
. P
lann
ing
shee
t fo
r cr
eatin
g en
dpoi
nts
An
end
poin
t is
a
com
pute
r on
w
hich
Ti
voli
soft
war
e is
in
stal
led
to
en
able
co
mm
unic
atio
n w
ith
the
Tivo
li se
rver
.
Hos
t n
ame
Nam
e of
th
e ta
rget
com
pute
r in
th
e ne
twor
k
En
dp
oin
t n
ame
*
Nam
e yo
u as
sign
to
the
end
poin
t
Pla
tfor
m
Ope
rati
ng sy
stem
of
the
end
poin
t
Use
r n
ame
root
or
A
dm
inis
trat
or
Pas
swor
d
Pass
wor
d of
th
e us
er on
the
serv
er
Des
tin
atio
n of
in
stal
lati
on fi
les
Path
on
th
e ta
rget
co
mpu
ter
for
inst
alla
tion
of
th
e pr
oduc
t
Exa
mpl
e:
visi
on03
Exa
mpl
e:
visi
on03
_ep
Exa
mpl
e:
Sola
ris
Exa
mpl
e:
root
—
Exa
mpl
e:
/dat
a/my
node
* T
his
nam
e ca
n in
clud
e al
phan
umer
ic ch
arac
ters
, und
ersc
ores
(_
), hy
phen
s (-
), an
d pe
riod
s (.)
. The
na
mes
ar
e ca
se-s
ensi
tive
. For
ex
ampl
e, th
e na
me
EP
Nam
e is
dif
fere
nt fr
om ep
nam
e.
The
en
dpo
int
nam
e m
ust
be d
iffe
rent
th
an th
e m
anag
ed no
de
nam
e.
You
mus
t pr
ovid
e a
valid
ho
st na
me
for
all
man
aged
no
des
an
d en
dpo
ints
th
at yo
u cr
eate
. Spe
cify
th
e un
ique
d
omai
n na
me
for
the
host
na
me
whe
n m
ulti
ple
com
pute
rs in
th
e sy
stem
ha
ve th
e sa
me
host
na
me.
Fo
r ex
ampl
e, th
e fu
lly qu
alif
ied
na
me
of th
e to
kyo
co
mpu
ter
mig
ht be
to
kyo
.sal
es.m
ycom
pan
y.co
m, w
here
sale
s is
th
e d
omai
n na
me
of th
e Sa
les
Dep
artm
ent’s
d
omai
n at
th
e co
mpa
ny m
ycom
pan
y. T
he fu
ll na
me
dis
ting
uish
es th
e Sa
les
Dep
artm
ent’s
se
rver
fr
om a
tok
yo
serv
er in
th
e m
ark
etin
g d
omai
n ca
lled
to
kyo
.mar
ket
ing.
myc
omp
any.
com
.
Appendix F. Installing the product and a complete Tivoli environment 81
Using an installation utility to install the product (for a new Tivoli
environment only)
Objective
To use an installation utility to install a Tivoli environment, IBM Tivoli Monitoring
and IBM Tivoli Monitoring for Databases: Sybase ASE so that you can monitor the
performance and availability of Sybase ASE.
Background information
Note: This option is valid for installation of the product with a new Tivoli
environment. You must use the command line or the Tivoli desktop options
to install the product in an existing Tivoli environment as described in
Chapter 2, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE in
an existing Tivoli environment,” on page 5.
During installation, the Tivoli server is installed automatically on the computer on
which you run the installation utility. This Tivoli server is the principal Tivoli
server. During the installation you can specify:
v Additional computers to configure as Tivoli servers. The extra Tivoli servers
improve performance by sharing the workload with the principal Tivoli server.
v Computers that you want to monitor (endpoints)
The installation procedure installs the required Tivoli software that is listed in
“Required software” on page 42.
Note: Tivoli Management Framework and Tivoli endpoint software must not be
previously installed on the computers that are the targets of your installation
activity.
To create Windows endpoints using the installation utility, at least one Windows
endpoint must exist in the domain of the principal Tivoli server. If you are
installing from a Windows system, and no Windows endpoints exist, the
installation utility automatically creates a Windows proxy endpoint, which enables
you to create additional Windows endpoints. If you are installing from a
UNIX-based system, you must create the Windows proxy endpoint by following a
separate procedure. Table 19 summarizes what you need to do under various
conditions.
Table 19. Procedures for creating Windows endpoints
What is the operating
system of the principal
Tivoli server?
Do Windows endpoints already exist in the domain of the principal Tivoli server?
Yes No
Windows Complete this procedure (Using an
installation utility to install the product
(for a new Tivoli environment only)).
Complete this procedure (Using an installation
utility to install the product (for a new Tivoli
environment only)). The installation utility
automatically creates one Windows proxy
endpoint, which enables you to create
Windows endpoints using the installation
utility.
82 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Table 19. Procedures for creating Windows endpoints (continued)
What is the operating
system of the principal
Tivoli server?
Do Windows endpoints already exist in the domain of the principal Tivoli server?
Yes No
UNIX-based Complete this procedure (Using an
installation utility to install the product
(for a new Tivoli environment only)).
1. Complete this procedure (Using an
installation utility to install the product (for
a new Tivoli environment only)) until Step
26 on page 88. During the procedure,
specify the Windows endpoints that you
want to create using the procedure
“Manually creating a Windows proxy
endpoint” on page 89.
2. Return to the installation utility and
complete the installation procedure. The
installation utility creates the endpoints that
you specified earlier.
Required authorization
v On UNIX, the user who installs the product must have root privileges.
v On Windows, the user who installs the product must have membership in the
Administrators group.
v The license key for Tivoli Management Framework is no longer required. Do not
attempt to enter a key.
Before you begin
v Ensure that required processes are running on computers where you plan to
install endpoints or supplemental Tivoli servers, called managed nodes.
Note: You do not need to check for these processes on the computer on which
you run the installation utility. This computer becomes the principal Tivoli
server and automatically receives all required software.
v Verify that the computers to be configured as Tivoli servers (including the
principal Tivoli server) and endpoints meet the following requirements:
– The operating system on each computer is supported by the installation
utility and by the monitoring components that you want to install.
– The required fix packs, patches, or maintenance packages for each operating
system are installed.
– The following software is not installed: Tivoli Management Framework and
Tivoli endpoint software.
– The products targeted by the component software (such as a database product
or a Web server product) are installed on computers that you want to
configure as endpoints.
– Each computer to be configured as a Tivoli server (including the principal
Tivoli server) has a static IP address. If DHCP is enabled, problems occur
with the Tivoli Management Framework software when the IP address
changes (for example, after rebooting).v Collect the following information about the computers that you want to
configure as additional Tivoli servers or endpoints. The installation utility
prompts you for this information.
– The fully qualified host name of the computer. For example, the fully
qualified host name for tokyo might be tokyo.sales.mycompany.com.
– The operating system of the computer.
Appendix F. Installing the product and a complete Tivoli environment 83
– A user ID and password that is authorized to the computer. The user ID must
have full administrative privileges (Administrator on Windows and root on
UNIX). The installation utility needs the user ID and password to install
software on the computer.
– (Endpoints only) A dedicated port number for communication with a Tivoli
server. The installation utility uses the default port number 9495 if you do not
specify any other port number. Make a note of the port number that you
assign and use a different port number for additional endpoints.v If you want to install from downloaded Web files, you must create an
installation depot to contain the downloaded files. Refer to the following
sections to determine which files you need to download from the Web and how
to set up an installation depot:
– “Obtaining source files for installing IBM Tivoli Monitoring for Databases:
Sybase ASE” on page 2
– “Creating a hierarchy of files for the installation utility to reference” on page
74v If you want to install from CDs, obtain the following:
– The base Tivoli software CDs
– The component software CDs for the monitoring components that you want
to install
– The language support CDs for the monitoring components that you want to
install in languages other than Englishv See Chapter 1, “Installation road map,” on page 1 for information about
additional activities required prior to installation.
v Close running applications on all computers.
When you finish
v Complete the activities described in Chapter 3, “Completing the installation,” on
page 15.
v Before you use this product to manage resources, complete the configuration
steps documented in the IBM Tivoli Monitoring for Databases: Sybase ASE: User’s
Guide.
Procedure
1. Log on to the computer that you want to be the principal Tivoli server.
2. Run one of the following setup files to start the installation:
v For Windows, run setupIXB.bat.
v For UNIX, run setupIXB.sh.
Additional information:
v The setup file is located in the root directory of the CD for the IBM Tivoli
Monitoring for Databases: Sybase ASE.
v If you are installing from downloaded Web files, the setup file is located in
the directory where you downloaded and uncompressed installation files
from the following Web download link. See “Creating a hierarchy of files
for the installation utility to reference” on page 74 for more information. 3. Click Next to display the license agreement, and accept the terms of the
license agreement.
4. The installation utility might display a warning about DHCP. Click Next.
5. Specify the directory path where you want to install the product.
6. Click Next.
84 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
7. Specify the directory path of the installation depot.
Additional information:
v The depot is a temporary location for installation files. If you are installing
from downloaded Web files, you already created the depot. If you are
installing from CDs, the installation utility creates the depot in this step.
v On Windows, the depot must reside on the target computer. (The target
computer is the computer to which you logged on when you began the
installation.) You cannot perform an installation of the product on Windows
using a depot that is located on a remote system. On UNIX, specify a depot
directory that the target computer can access. 8. Click Next.
The installation utility copies files from Installation Disk 1 or its downloaded
image to the depot directory.
9. Click Next when the installation utility prompts you to restart.
Additional information: The installation utility restarts from the depot directory
and searches for Tivoli Management Framework software on the target
computer. If the software is not found, a popup window displays a message
that the discovery process is complete.
Note: If Tivoli Management Framework software is discovered, the
installation cannot proceed. You have to remove the software before
starting the installation again on the same computer.
10. Click OK on the Complete popup window.
11. Click Next to display the Installation Options window.
12. (Optional) Select the languages that you want to enable for users of the
product.
Additional information: English is always enabled for this product. The
installation utility installs the language enablement packages for additional
languages that you choose.
13. Click Next to display the Configure Tivoli Servers window.
Additional information:
v The Configure Tivoli Servers window initially displays the host name and
operating system of the local computer. The installation utility configures
this computer as the principal Tivoli server. Use the Configure Tivoli
Servers window to specify additional computers that you want the
installation utility to configure as Tivoli servers. The additional Tivoli
servers share the workload of the principal Tivoli server.
v Windows computers that you want to configure as Tivoli servers must be
running the processes described in“Verifying the availability of remote
execution services” on page 77.14. (Optional) Repeat the following steps for each additional computer that you
want the installation utility to configure as a Tivoli server:
a. Click Add to display the Add a Computer popup window.
b. Specify information about the computer in the fields of the Basic tab:
v Host Name – Type the fully qualified host name of the computer. For
example, the fully qualified host name for tokyo might be
tokyo.sales.mycompany.com.
v Platform — Click the drop-down list and select the name of the
operating system on the computer.
v User — Type a login user ID that is authorized to the computer. The
user ID must have full administrative privileges (Administrator on
Appendix F. Installing the product and a complete Tivoli environment 85
Windows and root on UNIX). The installation utility needs the user ID
and password to install software on the computer.
v Password and Verify Password — Type the login password of the user
specified in the User field.c. Click the Advanced tab.
d. Specify information in the fields of the Advanced tab.
v Destination — (Optional) Type the directory path where you want to
install the Tivoli server software. If you do not specify a directory path,
the installation utility uses the default path displayed in this field.
v Reboot — This check box is automatically selected if you specified
Windows as the operating system of the target computer. The Tivoli
server software is activated after you restart the Windows computer.
v Gateway – Select this check box if this computer is a gateway. A
gateway is a Tivoli server to which endpoints are assigned.
Note: By default, the installation utility names the gateway
hostname-gateway, where hostname is the name of the host on
which the gateway is installed.e. Click OK to save your settings.
Additional information: The Configure Tivoli Servers window is displayed
again. The computer that you specified now appears at the end of the list.
Use the Edit or Remove buttons if you want to edit or remove any entries
that you added.15. Click Next to display the Component Selection window.
16. Select the monitoring components that you want to install.
17. Repeat the following steps to select Tivoli servers on which to install each
monitoring component:
a. Click Next to display the Select Tivoli Servers window.
Additional information: The Select Tivoli Servers window displays the
principal Tivoli server and any additional Tivoli servers that you specified
in Step 14 on page 85. The installation utility displays a separate window
for each monitoring component that you selected.
b. Select the Tivoli servers on which you want to install the specified
monitoring component.18. Click Next to display the Computers to Monitor window.
Additional information:
v The list of computers on the Computers to Monitor window is initially
empty. Use this window to add computers that you want to configure as
Tivoli endpoints.19. Repeat the following steps for each computer that you want to configure as an
endpoint:
a. Click Add to display the Add a Computer popup window.
b. Specify information about the computer in the fields of the Basic tab:
v Host Name – Type the fully qualified host name of the computer. For
example, the fully qualified host name for tokyo might be
tokyo.sales.mycompany.com.
v Label — Type a unique name for the endpoint. This name can include
alphanumeric characters, underscores (_), hyphens (-), and periods (.).
The names are case-sensitive. For example, the name EPName is different
from epname.
86 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Note: The endpoint name should be different from the name of any
Tivoli server in the Tivoli management region.
v Platform — Click the drop-down list and select the name of the
operating system on the computer.
v User — Type a login user ID that is authorized to the computer. The
user ID must have full administrative privileges (Administrator on
Windows and root on UNIX). The installation utility needs the user ID
and password to install software on the computer.
v Password and Verify Password — Type the login password of the user
specified in the User field.c. Click the Advanced tab.
d. Specify information in the fields of the Advanced tab.
v Port — Type a dedicated port number on the endpoint for
communication with the Tivoli server. The default is 9495. Make a note
of the port number that you assign and use a different port number for
additional endpoints.
v Destination — (Optional) Type the directory path on the target computer
where you want to install the Tivoli endpoint software. If you do not
specify a directory path, the installation utility uses the default path
displayed in this field.
v Reboot — Select this check box if you specified Windows as the
operating system of the target computer. The endpoint software is
activated after you restart the Windows computer.e. Click OK to save your settings.
Additional information: The Computers to Monitor window is displayed.
The computer that you specified now appears at the end of the list. Use
the Edit or Remove buttons if you want to edit or remove any entries that
you added.20. Perform the following steps to install from downloaded Web files. Go to the
next step to install from CDs.
Note: The downloaded Web files must be located in specific directories, as
described in “Obtaining source files for installing IBM Tivoli
Monitoring for Databases: Sybase ASE” on page 2.
a. Click Next.
The installation utility displays the first of a series of prompts. Each
prompt asks if you want to copy an installation image to the depot.
Additional information: After you complete the procedure described in
“Creating a hierarchy of files for the installation utility to reference” on
page 74, the installation files are located in the appropriate depot
subdirectories. The installation utility discovers the files and displays a
prompt for each installation image.
b. Click Next at each prompt to accept the default (Do not copy the
installation image).
c. Go to Step 22 on page 88.
Additional information: After you click Next on the final prompt window, the
installation utility displays a message that it is ready to install.
21. Perform the following steps to install from CDs:
a. Click Next.
Appendix F. Installing the product and a complete Tivoli environment 87
The installation utility displays the first of a series of windows. Each
window prompts you for the directory location of a specific installation
CD.
b. Perform the following steps for each CD prompt window that is displayed:
1) Insert the specified CD into the drive if you have the physical CD.
2) Type a directory path or click Browse to specify the path to the CD or
CD image.
3) Click Next.
Additional information: Each CD image is copied to the depot directory. After
you click Next on the final CD prompt window, the installation utility
displays a message that it is ready to install.
22. Click Next to display the Step List window.
Additional information: When the Step List window is displayed, the installation
utility begins installation of the software from the depot to the install location.
The Step List shows the software components that the installation utility
installs, and it displays status updates for the installation process.
23. (Windows only) Click Finish to restart the computer when prompted.
Additional information: The installation utility prompts you to restart the
computer after the second step in the Step List is completed.
24. (Optional) If you want to cancel the installation while the Step List is running,
perform the following steps:
a. Click Stop and allow the currently running process to finish.
Additional information: If you click Cancel without allowing the currently
running process to finish, the system might remain in an unpredictable
state.
b. Click Cancel to stop the installation and close the installation utility.
c. Delete the temporary depot directory created by the installation utility.25. (Optional) Double-click any item in the list to see details and to set processing
instructions for that step in the Details window.
26. (UNIX-based, principal Tivoli management region server only) If you specified
Windows endpoints to create in Step 19 on page 86, and no Windows
endpoints currently exist in the domain of the Tivoli management region
server, perform the following steps:
a. Click Stop at the top of the Step List.
b. Perform installation of proxy endpoints, as described in “Manually
creating a Windows proxy endpoint” on page 89.
Additional information: The installation utility creates the Windows endpoints
that you specified in Step 19 on page 86 after you create the Windows proxy
endpoint and successfully complete the steps in the Step List.
27. Click OK in the final prompt of the Step List.
Additional information: This final prompt is displayed when all steps in the
Step List show a Passed status. If all steps do not show a Passed status, the
problem determination guide for troubleshooting information.
28. Click Next.
29. Select Delete the temporary files to delete the depot directory that you
specified at the beginning of the installation process.
30. Click Next.
31. Click Finish.
88 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Manually creating a Windows proxy endpoint
Objective
To manually create a Windows proxy endpoint on a UNIX-based Tivoli
management region server.
Background information
The installation wizard can create Windows endpoints for the Tivoli management
region server that you are installing. However, this capability exists only when you
are installing the Tivoli management region server on a Windows operating
system. Chapter 2, “Installing IBM Tivoli Monitoring for Databases: Sybase ASE in
an existing Tivoli environment,” on page 5 describes the installation process which
includes creation of endpoints.
A proxy endpoint must exist in a Windows domain to enable the installation utility
to create Windows endpoints. When the Tivoli management region server runs on
Windows and you want to create Windows endpoints, the installation utility
automatically creates the proxy endpoint in the domain in which that server
resides. This proxy should share the same domain as the Tivoli management region
domain because it uses Windows Universal Naming Convention (UNC) methods
to provide remote access to newly created Window endpoints. The proxy endpoint
enables creation of Windows endpoints in any domain that has a trusted
relationship with the domain that contains the proxy. The Tivoli management
region server uses the user ID and password for the proxy endpoint to obtain
access to the file system of the other Windows servers.
The installation wizard also associates the proxy endpoint with a gateway in the
Tivoli management region. Otherwise, the Tivoli management region server cannot
use the proxy endpoint. You perform this procedure at a specific point during the
installation process when a gateway has been created to associate with the proxy
endpoint.
With this proxy access, the Tivoli management region server is able to install
endpoints on Windows systems in that domain and in other Windows domains in
the network that have a trusted relationship. Without a proxy endpoint, the Tivoli
server cannot create Windows endpoints in that remote domain.
In UNIX installations, the wizard does not automatically create the proxy endpoint
that Windows requires. When the Tivoli management region server you are
installing runs a UNIX operating system, you must use this procedure. The
procedure sets up the required proxy endpoint in the Windows domain that
contains target Windows servers that you want to monitor with IBM Tivoli
Monitoring for Databases: Sybase ASE.
You perform this procedure in the product installation utility and Tivoli
Management Framework Endpoint Setup wizard.
This procedure is an optional supplement to the installation process. You perform
the procedure at the point when the installation utility begins to process the Step
List.
Note: Use this procedure only if you are installing the product on a UNIX-based
server. This procedure is not necessary if you are installing the product on a
Windows-based server.
Appendix F. Installing the product and a complete Tivoli environment 89
Required authorization
On UNIX systems, the user who installs the product must have root privileges. On
Windows systems, the user who installs the product must have membership in the
Administrators group.
Before you begin
Perform the first part of the installation procedure described in Chapter 2,
“Installing IBM Tivoli Monitoring for Databases: Sybase ASE in an existing Tivoli
environment,” on page 5. During this procedure you access the Step List wizard
panel. You manually configure a Windows proxy endpoint in the Step List wizard
panel, during the installation procedure.
Identify the Windows computer that will serve as the proxy endpoint. You need
the endpoint name as well as the host name for the machine. For instance, if the
host name is vision35.mycompany.com, you might want to name the endpoint
vision35_ep.
When you finish
None
Procedure
Note: Use this procedure only if you are installing the product on a UNIX-based
server. This procedure is not necessary if you are installing the product on a
Windows-based server. For more information see “Background information”
on page 89.
Installation wizards:
1. Click Stop at the top of the Step List when the installation utility starts running
Step 1.
Additional Information: The system displays a message indicating that it will stop
at the end of the current step.
2. Click OK and wait for the step to finish processing.
3. In the Step List scroll to the TMA installation step, which installs any
endpoints that you have configured.
4. Double-click on the TMA installation step to access the Detail window for the
step.
5. Perform the following steps in the Detail window:
a. Click Toggle Breakpoint.
b. Click OK.
Additional information: This action sets a breakpoint for when the installation
utility begins to install endpoints. A stop sign icon indicates the step at which
you inserted a breakpoint. While this step is in breakpoint mode, you enable
the endpoint proxy as described in Step 7.
6. Click Run All at the top of the Step List window.
Additional information: Processing of the steps in the Step List resumes, until the
installation utility reaches the breakpoint and stops. Prior to the breakpoint you
set in Step 5 the installation utility completes the creation of a gateway. To
install correctly, the proxy endpoint must refer to this gateway. Otherwise the
Tivoli management region server cannot recognize the proxy endpoint.
90 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
7. When the installation utility reaches the breakpoint you created in Step 5,
install the proxy endpoint as follows. Perform these steps on the computer
where you are going to install the proxy endpoint, not on the Tivoli
management region server.
a. Insert the Tivoli Management Framework, Version 4.1.1, CD into the CD drive
of the computer that you want to be the endpoint.
b. Run the setup executable located in the following subdirectory path of the
Tivoli installation directory:
..\pc\lcf\winnt
c. Click Next in the Tivoli Management Framework Endpoint Setup window.
d. Read the license agreement.
e. Click Next to display the Endpoint installation options window.
f. (Optional) Click Browse to change the destination directory for the software.
g. Click Next to display the Tivoli Remote Access Account window.
h. Type the user name and password of the account through which Tivoli
Management Framework accesses remote file systems. If you do not require
access to remote domains, click Next to skip this step.
i. Click Next to access the Advanced Configuration window.
j. Specify the startup and configuration options information listed in the
following table:
Field name Use when ...
Gateway The gateway uses a port number other than the default 9494.
Endpoint You want to specify a port for the endpoint to use other than the
default. The default is 9495.
Other Use the –g host_name_of_the_gateway option to specify the
intercepting gateway. Use the –n host_name_of_the_endpoint option to
specify the name of the endpoint you are installing as the proxy.
k. Click Next to continue the installation process.
Additional information: The installation utility reports that communication of
the proxy endpoint and the gateway was successful. The endpoint is
installed and logged into a gateway. The installation process configures the
endpoint system to automatically start the endpoint service when the
system starts.
If the system does not start, there might be a problem with the
communication between the proxy endpoint and the gateway. You can
remove the endpoint, then reinstall the endpoint.
l. Click Next to display the Setup Complete window.
m. Click Finish to display the Restart Windows window.
n. Select No to prevent the restarting of the operating system.
Additional information: You can restart the system after the installation of
IBM Tivoli Monitoring for Databases: Sybase ASE is complete. When you
restart the computer, the Tivoli Endpoint service is created, with the startup
type set to automatic.8. Press OK to complete the endpoint installation.
9. On the Tivoli management region server, click Run All in the installation utility
and complete the installation steps that follow Step 26 on page 88.
Appendix F. Installing the product and a complete Tivoli environment 91
92 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix G. Support information
This section describes the following options for obtaining support for IBM
products:
v “Searching knowledge bases”
v “Obtaining fixes”
v “Contacting IBM Software Support” on page 94
Searching knowledge bases
If you have a problem with your IBM software, you want it resolved quickly. Begin
by searching the available knowledge bases to determine whether the resolution to
your problem is already documented.
Search the information center on your local system or
network
IBM provides extensive documentation that can be installed on your local machine
or on an intranet server. You can use the search function of this information center
to query conceptual information, instructions for completing tasks, reference
information, and support documents.
Search the Internet
If you cannot find an answer to your question in the information center, search the
Internet for the latest, most complete information that might help you resolve your
problem. To search multiple Internet resources for your product, expand the
product folder in the navigation frame to the left and select Web search. From this
topic, you can search a variety of resources including:
v IBM technotes
v IBM downloads
v IBM Redbooks™
v IBM DeveloperWorks
v Forums and newsgroups
v Google
Obtaining fixes
A product fix might be available to resolve your problem. You can determine what
fixes are available for your IBM software product by checking the product support
Web site:
1. Go to the IBM Software Support Web site
(http://www.ibm.com/software/support).
2. Under Products A - Z, select your product name. This opens a product-specific
support site.
3. Under Self help, follow the link to All Updates, where you will find a list of
fixes, fix packs, and other service updates for your product. For tips on refining
your search, click Search tips.
4. Click the name of a fix to read the description and optionally download the fix.
© Copyright IBM Corp. 2004 93
To receive weekly e-mail notifications about fixes and other news about IBM
products, follow these steps:
1. From the support page for any IBM product, click My support in the
upper-right corner of the page.
2. If you have already registered, skip to the next step. If you have not registered,
click register in the upper-right corner of the support page to establish your
user ID and password.
3. Sign in to My support.
4. On the My support page, click Edit profiles in the left navigation pane, and
scroll to Select Mail Preferences. Select a product family and check the
appropriate boxes for the type of information you want.
5. Click Submit.
6. For e-mail notification for other products, repeat Steps 4 and 5.
For more information about types of fixes, see the Software Support Handbook
(http://techsupport.services.ibm.com/guides/handbook.html).
Contacting IBM Software Support
IBM Software Support provides assistance with product defects.
Before contacting IBM Software Support, your company must have an active IBM
software maintenance contract, and you must be authorized to submit problems to
IBM. The type of software maintenance contract that you need depends on the
type of product you have:
v For IBM distributed software products (including, but not limited to, Tivoli,
Lotus®, and Rational® products, as well as DB2® and WebSphere® products that
run on Windows or UNIX operating systems), enroll in Passport Advantage® in
one of the following ways:
– Online: Go to the Passport Advantage Web page
(http://www.lotus.com/services/passport.nsf/WebDocs/
Passport_Advantage_Home) and click How to Enroll
– By phone: For the phone number to call in your country, go to the IBM
Software Support Web site
(http://techsupport.services.ibm.com/guides/contacts.html) and click the
name of your geographic region.v For IBM eServer™ software products (including, but not limited to, DB2 and
WebSphere products that run in zSeries®, pSeries®, and iSeries™ environments),
you can purchase a software maintenance agreement by working directly with
an IBM sales representative or an IBM Business Partner. For more information
about support for eServer software products, go to the IBM Technical Support
Advantage Web page (http://www.ibm.com/servers/eserver/techsupport.html).
If you are not sure what type of software maintenance contract you need, call
1-800-IBMSERV (1-800-426-7378) in the United States or, from other countries, go to
the contacts page of the IBM Software Support Handbook on the Web
(http://techsupport.services.ibm.com/guides/contacts.html) and click the name of
your geographic region for phone numbers of people who provide support for
your location.
Follow the steps in this topic to contact IBM Software Support:
1. Determine the business impact of your problem.
2. Describe your problem and gather background information.
94 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
3. Submit your problem to IBM Software Support.
Determine the business impact of your problem
When you report a problem to IBM, you are asked to supply a severity level.
Therefore, you need to understand and assess the business impact of the problem
you are reporting. Use the following criteria:
Severity 1 Critical business impact: You are unable to use the program,
resulting in a critical impact on operations. This condition
requires an immediate solution.
Severity 2 Significant business impact: The program is usable but is
severely limited.
Severity 3 Some business impact: The program is usable with less
significant features (not critical to operations) unavailable.
Severity 4 Minimal business impact: The problem causes little impact on
operations, or a reasonable circumvention to the problem has
been implemented.
Describe your problem and gather background information
When explaining a problem to IBM, be as specific as possible. Include all relevant
background information so that IBM Software Support specialists can help you
solve the problem efficiently. To save time, know the answers to these questions:
v What software versions were you running when the problem occurred?
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be recreated? If so, what steps led to the failure?
v Have any changes been made to the system? (For example, hardware, operating
system, networking software, and so on.)
v Are you currently using a workaround for this problem? If so, please be
prepared to explain it when you report the problem.
Submit your problem to IBM Software Support
You can submit your problem in one of two ways:
v Online: Go to the ″Submit and track problems″ page on the IBM Software
Support site (http://www.ibm.com/software/support/probsub.html). Enter
your information into the appropriate problem submission tool.
v Do you have logs, traces, and messages that are related to the problem
symptoms? IBM Software Support is likely to ask for this information.
v Can the problem be recreated? If so, what steps led to the failure?
v Have any changes been made to the system? (For example, hardware, operating
system, networking software, and so on.)
v Are you currently using a workaround for this problem? If so, please be
prepared to explain it when you report the problem.
If the problem you submit is for a software defect or for missing or inaccurate
documentation, IBM Software Support creates an Authorized Program Analysis
Report (APAR). The APAR describes the problem in detail. Whenever possible,
IBM Software Support provides a workaround for you to implement until the
APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the
IBM product support Web pages daily, so that other users who experience the
same problem can benefit from the same resolutions.
Appendix G. Support information 95
For more information about problem resolution, see Searching knowledge bases
and Obtaining fixes.
96 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Appendix H. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user’s responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not give you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION ″AS IS″ WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Some states do not allow disclaimer of express or implied warranties in certain
transactions, therefore, this statement might not apply to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
© Copyright IBM Corp. 2004 97
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
2Z4A/101
11400 Burnet Road
Austin, TX 78758 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurement may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM’s future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
98 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to
IBM for the purposes of developing, using, marketing, or distributing application
programs conforming to IBM’s application programming interfaces.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. © Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information in softcopy form, the photographs and color
illustrations might not appear.
Trademarks
AIX, DB2, IBM, the IBM logo, Lotus, NetView, Tivoli, the Tivoli logo, and IBM
Tivoli Enterprise Console are trademarks or registered trademarks of International
Business Machines Corporation in the United States, other countries, or both.
BizTalk, Microsoft, SharePoint, Windows, Windows NT, and the Windows logo are
trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Solaris Operating Environment, Java, and all Java-based trademarks are trademarks
of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks
of others.
Appendix H. Notices 99
100 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Index
Aaccessibility x
application resource definitions 51
authorization rolesassigning 18
Bbacking up
Tivoli management region 54
booksfeedback viii
online viii
ordering viii
see publications ix
CCDs, to use with the installation
utility 2
command lineuser interface options 52
commandsping 73
special characters xi
syntax xi
wdmdistrib 37
winstall 7, 10
wlsinst -ah 6
wpatch 7
wsetadmin 19
wtemp 41
Configure Event Server taskdescription 58
return codes 60
configuringIBM Tivoli Enterprise Console event
server 28
conventionstypeface x
core monitoring products 48
createWindows proxy endpoint
manually 89
customer supportsee Software Support 94
Ddata collector 51
directory names, notation xi
Discover taskdescription 63
return codes 67
discovering resources 29
discoveryassigning 29
disk space requirements 41
distributed networksmanaging 50
distributing resource models 37
Eeducation
see Tivoli technical training x
endpointmonitoring availability of an 51
uploading data from an 51
endpoints 50
creating 86
linking to existing Java Runtime
Environment 22
environment variables, notation xi
error codesConfigure Event Server task 60
Discover task 67
event classes and rules 50
event serverconfiguring 24
existing Java Runtime Environment,
linking endpoint to 22
Ffixes, obtaining 93
Ggateway 49
Hheartbeat 51
IIBM Passport Advantage 3
IBM Tivoli Business Systems
Manager 44, 48
configuring IBM Tivoli Enterprise
Console to forward events 28
installing 27
integrating with IBM Tivoli
Monitoring for Databases: Sybase
ASE 26
understanding 26
uninstalling 71
IBM Tivoli Business Systems Manager
product configuration software 44
IBM Tivoli Enterprise Console 44, 48
event server, configuring 24, 28
IBM Tivoli Enterprise Console event
classes and rules 50
IBM Tivoli Monitoring 43
enabling the functionality 15
verifying the installation 15
IBM Tivoli Monitoring Component
Services 43
installing 6
uninstalling 70
IBM Tivoli Monitoring for Databases:
Sybase ASEinstallation and setup guidelines for
existing Tivoli environment 1
obtaining installation files 2
uninstalling 69
IBM Tivoli Monitoring IBM Tivoli
Monitoring Web Health Console 44
IBM Tivoli Monitoring Resource Model
Builder 48
IBM Tivoli Monitoring Web Health
Console 48
updating 31
Icons for resources 50
identifying resources 29
information centers, searching to find
software problem resolution 93
installation 82
backing up the Tivoli management
region 54
command line 9, 10, 12
IBM Tivoli Business Systems
Manager 27
managed resources, descriptions
of 79
obtaining installation files 2
optional software 42, 43
planning sheets 79
prerequisites 42, 43
required software 42, 43
setting up an installation depot 74
setup and access Tivoli
environment 52
verifying required software is
running 77
warehouse packs for Tivoli Data
Warehouse 32
installation depot, setting up 74
installation filesobtaining 2
obtaining from CDs 2
obtaining from the Web 3
installation into an existing Tivoli
environmentguidelines for IBM Tivoli Monitoring
for Databases: Sybase ASE 1
installation wizardusing 82
installingfiles to enable Tivoli Data
Warehouse 32
IBM Tivoli Language Support for this
product 15
Java Runtime Environment 20
interconnected regionsconfiguring the event server 62
discover task 67
© Copyright IBM Corp. 2004 101
interconnected regions (continued)installation issues 5
Internet, searching to find software
problem resolution 93
JJava Runtime environment
required versions 43
Java Runtime Environment (JRE)installing 20
link to existing 22
Kknowledge bases, searching to find
software problem resolution 93
LLine of Business 26
Mmanaged node
difference between a Tivoli server and
a 49
managed resource 49
manual installationcreate Windows proxy endpoint 89
manualsfeedback viii
online viii
ordering viii
see publications ix
Nnotation
environment variables xi
path names xi
typeface xi
Oobjects
discovering resources 29
identifying resources 29
online publicationsaccessing ix
ordering publications ix
PPassport Advantage 3
path names, notation xi
ping command 73
planning sheets 79
endpoint 81
managed node 80
Policy regions 50
port numbers for endpoints 91
prerequisite software 42, 43
problem determinationdescribing problem for IBM Software
Support 95
determining business impact for IBM
Software Support 95
submitting problem to IBM Software
Support 95
product CDs, to use with the installer 2
product images, obtaining from the
Web 3
Profile 51
Profile managers 50
profilesdistributing 37
Profiles 50
publicationsaccessing online ix
feedback viii
online viii
ordering viii, ix
Rremote execution services 77
required softwareverifying 77
requirementsdisk space 41
resource 49
resource modeldistribution during discovery 29
resource modelsdistributing 37
Resource models 50
resourcesdiscovering 29
identifying 29
return codesConfigure Event Server task 60
Discover task 67
rexec command 77
RIM databaseuploading data to a 51
rolesauthorization, assigning 18
Sscripts
setup_env.csh 53
setup_env.sh 53
setup_env.csh script 53
setup_env.sh script 53
Software Supportcontacting 94
describing problem for IBM Software
Support 95
determining business impact for IBM
Software Support 95
submitting problem to IBM Software
Support 95
starting monitoring of Sybase ASE 23
Sybase ASEstarting monitoring of 23
system and software requirements 41
TTask libraries 50
tasksConfigure Event Server
description 58
return codes 60
details 57
Discoverdescription 63
return codes 67
discovery 29
invoking 57
Tivoli Adapter Configuration Facility 44
Tivoli Data Warehouse 44, 48
installing warehouse packs for 32
Tivoli desktopuser interface options 52
Tivoli environment 47
accessing 52
components of 50
core monitoring products 48
extending capabilities of 48
setting up 52
Tivoli interconnected regions 5
Tivoli Management Framework 43
accessing 52
IBM Tivoli Enterprise Console event
classes and rules 50
Icons for resources 50
managing distributed networks
with 50
Policy regions 50
Profile managers 50
Profiles 50
Resource models 50
set up and start of the Tivoli
environment 52
Task libraries 50
Tivoli management regionbacking up 54
diagram of 49
Tivoli management region server 49
Tivoli region 49
Tivoli Remote Execution Service 77
Tivoli software information center ix
Tivoli Software Installation Service 45
Tivoli technical training x
training, Tivoli technical x
trip service 77
typeface conventions x
Uupgrading
procedure 7
user interface optionscommand line 52
Tivoli desktop 52
Tivoli Management Framework 52
user interfacesinvoking tasks 57
Vvariables, notation for xi
102 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
Wwdmdistrib command 37
Web download images, to use with the
installation utility 3
Web, obtaining installation files from 3
Windows proxy endpoint, manually
create 89
winstall command 7, 10
wlsinst -ah command 6
wsetadmin command 19
wtemp command 41
Index 103
104 IBM Tivoli Monitoring for Databases: Sybase ASE: Installation and Setup Guide
����
Printed in USA
GC32-9135-00