tivoli manager for sybase** user’s...

Tivoli Manager for Sybase** User’s Guide

Version 1.1

Tivoli Manager for Sybase** User’s Guide (March 1999)Copyright NoticeCopyright © 1999 by Tivoli Systems, an IBM Company, including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of Tivoli Systems. Tivoli Systems grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright are granted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished “as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warranties of merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject to restrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

TrademarksThe following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, OS/2, RS/6000, Tivoli Enterprise Console (TEC) Tivoli Management Environment, Tivoli Manager for Sybase, TME 10, TME 10 Distributed Monitoring, and TME 10 Framework.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporation.

Sybase, the Sybase logo, Adaptive Server, Adaptive Server Enterprise, Adaptive Server Monitor, SQL Server, and Transact-SQL are trademarks of Sybase, Inc.

UNIX is a registered trademark in the United States and other countries licensed exclusively through X/Open Company Limited.

Other company, product, and service names mentioned in this document may be trademarks or servicemarks of others.

NoticeReferences in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to Tivoli Systems’ or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter 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 the IBM Director of Licensing, IBM Corporation, 500 Columbus Avenue, Thornwood, New York 10594.

Tivoli Manager for Sybase User’s Guide iii

Tivoli Manager for Sybase User’s Guide

Preface................................................................................................................... ix

Chapter 1—OverviewExtensions to Tivoli ............................................................................................ 1-2

What are Tivoli Administrators? ........................................................................ 1-2

Authorization Roles ............................................................................................ 1-3

Sybase Adaptive Server Objects ......................................................................... 1-4

Using the Tivoli Desktop or Command Line...................................................... 1-8

Using the Desktop Navigator.............................................................................. 1-8

Chapter 2—Guidelines for Setting Up Tivoli Manager for Sybase

Chapter 3—Installing Tivoli Manager for SybaseSoftware Requirements ....................................................................................... 3-1

Installing Tivoli Manager for Sybase ................................................................. 3-2

Installing from the Desktop........................................................................ 3-3

Installing from the Command Line .......................................................... 3-12

Chapter 4—Setting Up Tivoli Manager for SybaseSubscribing to Notice Groups ............................................................................. 4-2

Adding the SybaseDataServer Managed Resource Type ................................... 4-6

Adding or Removing a Managed Resource Type from the Desktop ......... 4-7

Adding or Removing a Managed Resource Type from the Command Line ............................................................................ 4-9

Registering Sybase Servers............................................................................... 4-10

Registering a Sybase Adaptive Server and Sybase Backup Server ......... 4-10

Registering a Sybase Adaptive Server from the Desktop................ 4-11

Registering a Sybase Adaptive Server from the Command Line .... 4-16

iv Version 1.1

Registering a Sybase Monitor Server....................................................... 4-19

Registering a Sybase Monitor Server from the Desktop ................. 4-20

Registering a Sybase Monitor Server from the Command Line ..... 4-24

Integrating with the Tivoli Enterprise Console ................................................ 4-26

Overview of the TEC ............................................................................... 4-26

How Tivoli Manager for Sybase Integrates with the TEC....................... 4-27

Event Class Structures..................................................................... 4-27

The Rule Base ................................................................................. 4-30

Manually Configuring the TEC ............................................................... 4-31

Creating a New Rule Base and Importing Events ........................... 4-32

Importing Event Classes into an Existing Rule Base ...................... 4-34

Creating Event Filters...................................................................... 4-35

Chapter 5—Setting Up Monitoring ProfilesOverview of Monitoring ..................................................................................... 5-2

Guidelines for Setting up Monitoring Profiles ................................................... 5-2

Authorization Roles for Setting Up Monitors .................................................... 5-4

Setting Up Monitors from the Desktop .............................................................. 5-5

Adding a Profile Manager and a Profile .................................................... 5-6

Adding an Indicator Collection................................................................ 5-12

Associating an Indicator Collection with a Profile .................................. 5-15

Adding Monitors to a Profile ................................................................... 5-19

Specifying Response Levels .................................................................... 5-23

Sending Events to the TEC ...................................................................... 5-29

Scheduling the Monitor............................................................................ 5-31

Setting Your Own Default Schedule for a Profile........................... 5-32

Setting Individual Schedules for Individual Monitors .................... 5-35

Restricting a Schedule ..................................................................... 5-38

Setting the User and Group ID for a Profile ............................................ 5-42

Saving the Profile..................................................................................... 5-44

Setting Up Monitors from the Command Line................................................. 5-45

Tivoli Manager for Sybase User’s Guide v

Chapter 6—Using Tivoli Manager for SybaseManaging Sybase Adaptive Servers ................................................................... 6-2

Opening a Sybase Data Server Collection ................................................. 6-2

Changing Sybase Adaptive Server Registration Details ............................ 6-6

Viewing Sybase Adaptive Server Properties ............................................. 6-9

Viewing Sybase Adaptive Server Error Log Contents............................. 6-12

Starting a Sybase Adaptive Server ........................................................... 6-15

Shutting Down a Sybase Adaptive Server ............................................... 6-17

Checking the State of a Sybase Adaptive Server ..................................... 6-20

Managing Objects in Sybase Data Server Collections ..................................... 6-24

Managing a SybaseDatabase Endpoint .................................................... 6-24

Opening a Sybase Database Collection ........................................... 6-24

Viewing SybaseDatabase Endpoint Properties................................ 6-27

Checking the State of a SybaseDatabase Endpoint ......................... 6-29

Managing a SybaseEngine Instance ......................................................... 6-34

Viewing SybaseEngine Instance Properties .................................... 6-34

Checking the State of a SybaseEngine Instance .............................. 6-36

Managing a SybaseBackupServer Endpoint ............................................ 6-40

Opening a Sybase Backup Server Collection .................................. 6-40

Changing Sybase Backup Server Registration Details.................... 6-42

Viewing Sybase Backup Server Properties ..................................... 6-45

Viewing Sybase Backup Server Error Log Contents ...................... 6-47

Starting a Sybase Backup Server..................................................... 6-49

Shutting Down a Sybase Backup Server ......................................... 6-52

Checking the State of a Sybase Backup Server ............................... 6-55

Managing a SybaseMonitorServer Endpoint ........................................... 6-59

Opening a Sybase Monitor Server Collection ................................. 6-59

Changing Sybase Monitor Server Registration Details ................... 6-61

Viewing Sybase Monitor Server Properties .................................... 6-64

Viewing Sybase Monitor Server Error Log Contents ..................... 6-66

Starting a Sybase Monitor Server .................................................... 6-68

vi Version 1.1

Shutting Down a Sybase Monitor Server ........................................ 6-71

Checking the State of a Sybase Monitor Server.............................. 6-75

Removing Objects from a Sybase Data Server Collection ...................... 6-79

Subscribing Endpoints to Profile Managers ..................................................... 6-80

Adding Subscribers to a Profile Manager from the Desktop ................... 6-80

Adding Subscribers to a Profile Manager from the Command Line ....... 6-84

Distributing a Monitoring Collection Profile ................................................... 6-84

Distributing a Monitoring Profile from the Desktop ............................... 6-85

Distributing a Monitoring Profile from the Command Line.................... 6-93

Determining Which Monitors Have Been Distributed to an Endpoint............. 6-94

Determining Which Monitors Are Running at an Endpoint............................. 6-95

Viewing Events in the Tivoli Enterprise Console ............................................ 6-96

Chapter 7—Setting Up and Using Tivoli Manager for Sybase GEM InstrumentationOverview of Tivoli GEM Instrumentation ......................................................... 7-2

Understanding the Topology Server .......................................................... 7-2

Understanding the Topology Console........................................................ 7-3

Understanding Instrumented Components................................................. 7-3

Understanding Instrumentation Policy Regions, Profile Managers, Task Libraries, and Profiles.......................................... 7-7

Understanding Tasks.................................................................................. 7-8

Understanding Monitors .......................................................................... 7-10

Discovering the Sybase Components....................................................... 7-12

Installing and Configuring Tivoli Manager for Sybase GEM Instrumentation 7-12

Preparing to Install Tivoli Manager for Sybase GEM Instrumentation... 7-12

Tivoli Management Regions ........................................................... 7-12

Administrators ................................................................................. 7-13

Installation Prerequisites ................................................................. 7-13

Installing Tivoli Manager for Sybase GEM Instrumentation .................. 7-15

Installing from the Desktop ............................................................. 7-16

Installing from the Command Line ................................................. 7-21

Tivoli Manager for Sybase User’s Guide vii

Setting Up Tivoli Manager for Sybase GEM Instrumentation ......................... 7-21

Configuring the Java Development Kit (JDK)......................................... 7-22

Configuring the Java Runtime Environment (JRE) ................................. 7-23

Configuring the Topology Server for Tivoli Manager for Sybase........... 7-24

Loading Tivoli Manager for Sybase sybase.pkg AMP file ............. 7-26

Initiating Sybase Components Discovery for the Topology Server 7-28

Subscribing Managed Nodes and Distributing File Packages......... 7-34

Subscribing Sybase Resources and Distributing Sentry Profiles .... 7-35

Confirming the Sybase Component Discovery ............................... 7-38

Using Tivoli Manager for Sybase GEM Instrumentation................................. 7-39

Tivoli Manager for Sybase GEM Instrumentation Monitors ................... 7-39

Tivoli Manager for Sybase GEM Instrumentation Tasks ........................ 7-40

Navigating to Sybase Components on the Topology Console ................. 7-42

Using the Tear-Away Log........................................................................ 7-45

Starting a Component Task ...................................................................... 7-45

Viewing Monitor Status ........................................................................... 7-47

Deleting Components from a View.......................................................... 7-48

Appendix A—Monitoring Collection InformationMonitor Type Definitions .................................................................................. A-1

Suggested Monitoring Profiles .......................................................................... A-2

Sybase Adaptive Server Performance Monitors ....................................... A-2

Sybase Adaptive Server Availability Monitors......................................... A-3

Sybase Backup Server Availability Monitors ........................................... A-3

Sybase Monitor Server Availability Monitors .......................................... A-4

Sybase Database Availability Monitors .................................................... A-4

Descriptions of All Monitors with Functional Groups and Monitor Types....... A-5

Appendix B—Authorization Roles

viii Version 1.1

Appendix C—Operator GroupsNumeric Operator Group ....................................................................................C-1

String Operator Group ........................................................................................C-3

Additional Operator Groups ...............................................................................C-5

Appendix D—Supporting Connections to Sybase ComponentsConnections to Sybase GEM Components........................................................ D-1

What Do External Components Connect To?........................................... D-2

Who Should Initiate Relationships with the SybaseDataServer Component? .................................................. D-2

Defining Relationships with the SybaseDataServer Component ...................... D-3

Relating Components ................................................................................ D-3

Tivoli Manager for Sybase GEM Instrumentation Component Connection Types.................................................................. D-4

The Sybase DataServer Component Communication Information .. D-5

Implementing the Relationship in AppDriver.java ................................... D-7

SybaseDataServer getInstanceRelations() Method .......................... D-8

SybaseDataServer Heartbeat Event.................................................. D-9

Preface

Tivoli Manager for Sybase User’s Guide ix

PrefaceThe Tivoli Manager for Sybase User’s Guide describes how to install and use the Tivoli Manager for Sybase software to manage Sybase Adaptive Server (previously called SQL Server) resources through the Tivoli Enterprise software. You can install the software from the Tivoli desktop or from the command line.

You will notice that both Tivoli and TME 10 are used in our product documentation. These terms are interchangeable. We will remove references to TME 10 in future product releases.

Also in our product documentation, the term Adaptive Server is used, but the information also pertains to Sybase SQL Server for releases prior to Sybase Adaptive Server, Version 11.5.

Who Should Read This GuideThis guide explains the concepts you should know to use Tivoli Manager for Sybase. It contains information about server management using Tivoli Manager for Sybase and how this product is integrated into the Tivoli environment.

Readers of this guide should have knowledge of Windows NT, UNIX or similar operating systems, Tivoli Framework (or TME 10), and Sybase Adaptive Server (or SQL Server) database administration.

Prerequisite and Related DocumentsYou must be familiar with the information in the related documents before you install and use Tivoli Manager for Sybase.

■ Tivoli Manager for Sybase Reference Guide, Version 1.1

Contains detailed information about individual monitors in the SybaseServer and SybaseDatabase monitoring collections.

■ TME 10 Distributed Monitoring User’s Guide

Explains how to set up and use Tivoli Distributed Monitoring. You must be familiar Tivoli Distributed Monitoring before you can install and use a monitoring collection.

Preface

x Version 1.1

■ TME 10 Framework Reference Guide

Describes command line interface (CLI) commands and the default and validation policies for Framework components.

■ TME 10 Framework Planning and Installation Guide

Provides information on Tivoli Management Region (TMR) server and client hardware requirements.

■ TME 10 Framework User’s Guide

Contains more detailed information about profile management, including profile managers, profile databases, and profiles.

■ TME 10 Enterprise Console User’s Guide

Contains information about setting up the Enterprise Console to receive distributed monitoring events.

■ Tivoli Global Enterprise Manager Installation and User’s Guide, Version 2.2

Describes how to install, configure, and use the Tivoli Global Enterprise (Tivoli GEM) product.

Also refer to the Sybase Adaptive Server documentation, particularly the following documents:

■ Adaptive Server Enterprise Monitor Server User’s Guide

Describes how to obtain performance statistics. It also explains the wait and nowait states for shutting down a Sybase Monitor Server.

■ System Administration Guide

Describes how to administer security for the Sybase Adaptive Server Enterprise and provides information for specifying character conversion, international language, and sort-order settings. It also explains the wait and nowait states for shutting down a Sybase Adaptive Server and its databases.

■ Transact-SQL User’s Guide

Describes Transact-SQL, Sybase’s enhanced version of the relational database language, SQL.

Preface

Tivoli Manager for Sybase User’s Guide xi

■ Utility Programs Manual (for your platform)

Describes the Sybase Adaptive Server Enterprise utility programs, which you can invoke from the operating system. It also explains the single-user and multi-user modes when starting a Sybase Adaptive Server.

What This Guide ContainsThe Tivoli Manager for Sybase User’s Guide contains the following sections:

■ Chapter 1, “Overview”

Provides an overview of Tivoli Manager for Sybase features, its extensions to Tivoli, authorization roles, and the Sybase Adaptive Server as an endpoint.

■ Chapter 2, “Guidelines for Setting Up Tivoli Manager for Sybase”

Provides an overview chart of the setup procedures for Tivoli Manager for Sybase, which includes cross-references to additional information.

■ Chapter 3, “Installing Tivoli Manager for Sybase”

Contains software and hardware requirements, and provides installation procedures for installing the Tivoli Manager for Sybase software.

■ Chapter 4, “Setting Up Tivoli Manager for Sybase”

Provides procedures for subscribing to notice groups, setting managed resources, registering servers and discovering databases, and integrating Tivoli Manager for Sybase with the Tivoli Enterprise Console (TEC).

■ Chapter 5, “Setting Up Monitoring Profiles”

Provides procedures for setting up monitoring profiles.

Preface

xii Version 1.1

■ Chapter 6, “Using Tivoli Manager for Sybase”

Provides procedures for using the software to manage Sybase Adaptive Servers and their collections of endpoints and objects, subscribing and distributing monitoring profiles, determining which monitors have been distributed and are running at an endpoint, and viewing events in the TEC.

■ Chapter 7, “Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation”

Describes Tivoli Manager for Sybase Global Enterprise Manager (Tivoli GEM) instrumentation that allows you to graphically monitor and control Tivoli Manager for Sybase resources.

■ Appendix A, “Monitoring Collection Information”

Provides suggested monitoring profiles. It also provides a list of all monitors with their descriptions, functional groups, and monitor types.

■ Appendix B, “Authorization Roles”

Summarizes required authorization roles and activities and tells where to find additional information about them in this manual.

■ Appendix C, “Operator Groups”

Describes the operator groups that allow you to define the conditions that must occur for a monitor to send an alert.

■ Appendix D, “Supporting Connections to Sybase Components”

Describes conections to Tivoli Manager for Sybase GEM instrumentation components and the means by which external components can connect to Sybase components.

Preface

Tivoli Manager for Sybase User’s Guide xiii

Typeface ConventionsThe guide uses several typeface conventions for special terms and actions. These conventions have the following meaning:

Bold Commands, keywords, file names, authorization roles, or other information that you must use literally appear in bold. Names of windows, dialogs, and other controls also appear in bold.

Italics Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics.

Bold Italics New terms appear in bold italics when they are defined in the text.

Monospace Code examples, output, and system messages appear in a monospace font.

Platform-specific InformationSee the Tivoli Manager for Sybase Release Notes for detailed and up-to-date information on supported platform versions, disk space, and memory requirements.

Contacting Customer SupportFor support inside the United States, for this or any other Tivoli product, contact Tivoli Customer Support in one of the following ways:

■ Send e-mail to [email protected]

■ Call 1-800-TIVOLI8

■ Navigate our Web site at http://www.support.tivoli.com

For support outside the United States, refer to your Customer Support Handbook for phone numbers in your country. The Customer Support Handbook is available online at http://www.support.tivoli.com.

When you contact Tivoli Customer Support, be prepared to provide identification information for your company so that support personnel can assist you more readily.

Preface

xiv Version 1.1

We are very interested in hearing from you about your experience with Tivoli products and documentation. We welcome your suggestions for improvements. If you have comments or suggestions about this documentation, please send e-mail to [email protected].

Tivoli Manager for Sybase User’s Guide 1–1

Overview

1Overview

Tivoli Manager for Sybase complements existing tools for Sybase Adaptive Servers (previously called SQL Servers, and referred to as Sybase Data Servers on some Tivoli windows and dialogs) and adds features so you can manage a large number of servers in a distributed environment. This product reduces the complexity of managing large distributed database environments and enables database administrators (DBAs) to concentrate on issues associated with each of the individual servers.

This product provides the ability to manage and monitor Sybase Adaptive Servers by providing extensions to Tivoli Framework, Distributed Monitoring, and Enterprise Console. It includes the SybaseServer and the SybaseDatabase monitoring collections, which provide 42 monitoring sources. The monitoring collections enable you to manage distributed Sybase Adaptive Server resources effectively and to the granularity that you need.

Using Tivoli Manager for Sybase, you can do the following:

■ Register the Sybase Adaptive Server, Backup Server, and Monitor Server with Tivoli.

■ Use the SybaseServer and SybaseDatabase monitoring collections for Sybase Adaptive Server, Backup Server, Monitor Server, and database availability and performance monitoring.

■ Use the Free Form SQL Numeric and Free Form SQL String monitoring sources to create user-defined monitoring sources.

1

Extensions to Tivoli

1–2 Version 1.1

■ Alert Tivoli administrators to Sybase Adaptive Server performance problems or serious errors and failures.

■ Integrate with the Tivoli Enterprise Console (TEC) to provide event correlation to determine the severity and relationship of events. You can define rules for automated responses, such as running a corrective task.

■ Use Tivoli Global Enterprise Manager (Tivoli GEM) instrumentation to graphically monitor and control Tivoli Manager for Sybase resources residing on Tivoli managed nodes.

Extensions to TivoliThe Tivoli Manager for Sybase is fully integrated into the Tivoli environment. You should already be familiar with the concepts of Tivoli as outlined in the TME 10 Framework User’s Guide.

What are Tivoli Administrators? Sybase Adaptive Server administrators are known in the Tivoli environment as Tivoli administrators. Administrators are system or database administrators who have the authorization to perform system or database management tasks in policy regions. Each administrator or group of administrators is represented by an icon on the Tivoli desktop.

The Tivoli Manager for Sybase also fully integrates into Tivoli security. To perform Sybase Adaptive Server administration functions, administrators must have authorization roles for both Tivoli Manager for Sybase and Tivoli.

Authorization Roles


Overview

Authorization RolesAuthorization roles determine the range of actions an administrator can perform in a policy region. You assign roles to administrators so they can perform system or database management tasks. A role can apply to the entire Tivoli management region (TMR) or to a specific set of resources, such as those contained in a policy region. Super, senior, admin, and user are examples of Tivoli authorization roles.

The Tivoli Manager for Sybase also adds the following authorization roles:

sybase_dba Provides the ability to perform all server instance functions. An administrator with this role can perform all Tivoli Manager for Sybase administration functions.

sybase_user Provides read-only access to a limited set of Tivoli Manager for Sybase functions. An administrator with this role can open a server icon and view the properties of the server.

sybase_monitor Provides the ability to run a distributed monitoring probe. The user and group ID of the Distributed Monitoring profile must be set to an administrator with this role.

Note: You must assign both Tivoli and Sybase Adaptive Server authorization roles to administrators in the policy regions you want them to administer.

Sybase Adaptive Server Objects

1–4 Version 1.1

Each Tivoli Manager for Sybase procedure has a required authorization role. This guide documents the context and authorization role required for each procedure in the following manner:

For a complete list of all procedures and their required authorization roles, see Appendix B, “Authorization Roles.”

Sybase Adaptive Server ObjectsObjects on the Tivoli desktop include profile endpoints (hereafter referred to as simply endpoints), which are any resources that represent the final destination for a profile distribution. The endpoints for Tivoli Manager for Sybase are servers and databases. Another object is an engine, which is not an endpoint since you cannot distribute profiles to it. Rather, it is an instance of an engine configured in the Sybase Adaptive Server.

Tivoli provides an icon on the desktop for each server and database endpoint, and engine instance, in the same way that it provides an icon for each managed node.

Activity Context Required Role

Add or remove a managed resource type for a policy region

Policy region senior



Overview

The following illustrations show examples of the endpoint and engine icons:

■ A Sybase Adaptive Server is represented by a SybaseDataServer icon, whose name typically is in the form server_identifier@managed_node.

■ A Sybase Backup Server is represented by a SybaseBackupServer icon, whose name typically is in the form backupserver_identifier@dataserver_identifier@managed_node. This endpoint icon is included in the collection window of the Sybase Adaptive Server that it backs up.


1–6 Version 1.1

■ A Sybase Monitor Server is represented by a SybaseMonitorServer icon, whose name typically is in the form monitorserver_identifier@dataserver_identifier@managed_node. This endpoint icon is included in the collection window of the Sybase Adaptive Server that it monitors.

A Sybase Adaptive Server may have one or more databases that require management on an individual or collective basis.

The following illustration shows an example of the database endpoint icon. The SybaseDatabase icon name typically is in the form database_identifier@server_identifier.

The following illustration shows an example of the engine instance icon. The SybaseEngine icon name typically is in the form engine_identifier@server_identifier@managed_node. This instance icon is included in the collection window of the Sybase Adaptive Server where the engine is configured.



Overview

When you double-click on the icon for a SybaseDataServer endpoint, Tivoli displays the Sybase Data Server collection window. The window contains icons for each SybaseBackupServer, SybaseMonitorServer, and SybaseDatabase endpoint, SybaseEngine instance, and any distributed profile icons that are associated with the Sybase Adaptive Server. For details, see “Managing Sybase Adaptive Servers” on page 6-2.

When you open a SybaseDatabase, SybaseBackupServer, or SybaseMonitorServer icon, its collection window does not contain any endpoint icons, but any distributed profile icons are visible. You cannot open a SybaseEngine icon.

Monitors in the SybaseServer collection can be distributed to SybaseDataServer, SybaseBackupServer, and SybaseMonitorServer endpoints. Monitors in the SybaseDatabase collection can only be distributed to SybaseDatabase endpoints.

You can subscribe server and database endpoints to profiles within profile managers in the same way as any other managed resource.

Using the Tivoli Desktop or Command Line

1–8 Version 1.1

Using the Tivoli Desktop or Command LineIn many cases, this manual provides procedures for executing from both Tivoli desktop’s graphical user interface (GUI) or from the command line interface (CLI).

Use the Tivoli desktop when you want to take advantage of visual input prompting, which includes text fields, drop-down or scrolling lists of options, or buttons to select default options.

Tivoli Manager for Sybase has only a few functions that require you to use the command line. However, you can also use the command line if you want to create scripts or rapidly enter other commands.

Using the Desktop NavigatorUsing the Desktop Navigator from the Tivoli desktop allows you to maneuver through the Tivoli environment without going through layers of windows. You can access the Desktop Navigator from any collection window, such as the Tivoli desktop or a policy region window. Tivoli Manager for Sybase resource types are added to the Navigate To scrolling list on the Desktop Navigator dialog.

Using the Desktop Navigator


Overview

For more information, refer to the TME 10 Framework User’s Guide.

Using the Desktop Navigator

1–10 Version 1.1


Gu

idelin

es for S

etting

Up

T

ivoli M

anag

er for S

ybase

2Guidelines for Setting Up Tivoli Manager for Sybase

This chapter provides an overview chart of setup procedures you must perform before you can use Tivoli Manager for Sybase. It includes cross-references to places where you can find additional information.

The setup procedures can be divided into the following categories:

■ Installing Tivoli Manager for Sybase

■ Setting up administrators to use the software

■ Setting managed resource types

■ Registering Sybase Adaptive Servers and Monitor Servers

■ Setting up the monitors

■ Setting up Tivoli Manager for Sybase to work with the Tivoli Enterprise Console (TEC) (optional)

■ Setting up Tivoli Manager for Sybase to work with the Tivoli Global Enterprise Manager (Tivoli GEM) (optional)

2–2 Version 1.1

Set-up Procedure For More Information

Installing software

Make sure you have the appropriate amount of disk space and memory for Tivoli Manager for Sybase.

Refer to the Tivoli Manager for Sybase Release Notes.

Install the software. See “Installing Tivoli Manager for Sybase” on page 3-2.

Setting up administrators

Note: You must assign both Tivoli and Sybase Adaptive Server authorization roles to administrators in the policy regions you want them to administer.

Assign each administrator the appropriate authorization role for the procedures that the administrator will perform.

Assign the sybase_monitor to the administrator who will run the monitoring probes.

See Appendix B, “Authorization Roles” for a list of the authorization roles required for each procedure.

The Tivoli Framework User’s Guide provides information on how to assign authorization roles to Tivoli administrators.

To set the user and group ID for the profile, use the Edit -> Set User & Group ID menu option in the TME 10 Distributed Monitoring Profile Properties window.

Subscribe additional administrators to the appropriate notice groups.

See “Subscribing to Notice Groups” on page 4-2.


Gu

idelin

es for S

etting

Up

T

ivoli M

anag

er for S

ybase

Setting managed resource types

Add the Sybase Adaptive Server as a managed resource type for the policy region.

See “Adding the SybaseDataServer Managed Resource Type” on page 4-6.

Add SentryProfile as a managed resource for the policy region (if you have not already done so), so you can create Sybase Adaptive Server distributed monitor profiles.

Refer to the TME 10 Distributed Monitoring User’s Guide.

Registering the servers

Register the servers. See “Registering Sybase Servers” on page 4-10.

Integrate Tivoli Manager for Sybase with the TEC (optional)

Integrate Tivoli Manager for Sybase with the TEC, and configure TEC to receive monitoring events.

See “Integrating with the Tivoli Enterprise Console” on page 4-26.

Setting up monitoring profiles

Set up the monitors that you want to run. See Chapter 5, “Setting Up Monitoring Profiles” and “Monitor Type Definitions” on page A-1.

Adding an indicator collection (optional)

Add an indicator collection to the policy region containing the Sybase Adaptive Server.

See “Adding an Indicator Collection” on page 5-12.


2–4 Version 1.1

Setting up Tivoli Manager for Sybase GEM Instrumentation (optional)

Set up Tivoli GEM to graphically monitor and control Tivoli Manager for Sybase resources.

See Chapter 7, “Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation.”


Tivoli Manager for Sybase Users Guide 3–1

Installin

g T

ivoli M

anag

er fo

rS

ybase

3Installing Tivoli Manager for Sybase

This chapter provides the requirements and instructions for installing Tivoli Manager for Sybase. It covers the following topics:

■ Software and hardware requirements

■ Instructions for installing Tivoli Manager for Sybase from both the desktop and the command line

Software RequirementsThis section describes the software requirements for Tivoli Manager for Sybase. Successful installation requires that the Tivoli software be installed in the following sequence:

1. Tivoli Framework, Version 3.1, or later

2. Tivoli Distributed Monitoring, Version 2.0.2 Service Pack 1, or later (needed only to install Tivoli Manager for Sybase - Distributed Monitoring)

3. Tivoli Manager for Sybase - Framework

4. Tivoli Manager for Sybase - Distributed Monitoring, Version 1.1

3

Installing Tivoli Manager for Sybase

3–2 Version 1.1

Optionally, you can install the Tivoli Enterprise Console, Version 3.1, or above, any time after installing the Tivoli Framework. For more information about the TEC, refer to the TME 10 Enterprise Console User’s Guide.

Also, optionally, you can install Tivoli Global Enterprise Manager, Version 2.2 (needed only to install Tivoli Manager for Sybase GEM instrumentation) after installing the software described above. For more information, see Chapter 7, “Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation.”

Tivoli Manager for Sybase supports installation using Software Installation Service, Version 1.0 and 3.6. For additional information, refer to the Software Installation Service User’s Guide.

For up-to-date information on the software, plus details on the operating system versions, hardware, and system memory requirements for this product, see the Tivoli Manager for Sybase Release Notes.

Installing Tivoli Manager for SybaseBefore installing Tivoli Manager for Sybase, review the Tivoli Manager for Sybase Release Notes for this release. Make sure all the prerequisites are met before following the installation procedures in this chapter.

You install Tivoli Manager for Sybase on the Tivoli Management Region (TMR) server and on any clients you want to manage. The TMR server can be any system platform supported by this product.

The following table provides the context and authorization role required for the installation procedure:

You can perform this procedure from either the Tivoli desktop or the command line.


Install Tivoli Manager for Sybase

TMR senior



Installin

g T

ivoli M

anag

er fo

rS

ybase

Installing from the DesktopUse the following steps to install the software from the Tivoli desktop.

1. From the Desktop menu, select the Install –> Install Product... option.

This option displays an error message if the media path is not specified correctly.


3–4 Version 1.1

2. Do one of the following:

If you received an error message, go to step 3.

—OR—

If you did not receive the error message, go to step 5 on page 3-6.

3. Click the OK button on the error message box to display the File Browser dialog to set the path to the Tivoli installation media.



Installin

g T

ivoli M

anag

er fo

rS

ybase


If you already know the path to the installation media:

a. Enter the full path in the Path Name field.

b. Click the Set Path button to change to the specified directory.

c. Click the Set Media & Close button to save the new media path and return to the Install Product dialog. The dialog now contains a list of products for installation. Go to step 5 on page 3-6.

—OR—

If you do not know the exact path to the installation media:

a. From the Hosts scrolling list, select the host on which the install media is mounted. Selecting a host updates the Directories scrolling list to show all the directories on the chosen host.

b. Select the directory containing the installation media from the Directories scrolling list.

c. Click the Set Media & Close button to save the new media path.


3–6 Version 1.1

5. Tivoli displays the Install Product dialog.

If the Select Product to Install scrolling list is empty, click the Select Media button to access the File Browser dialog to display the list of products. Go back to step 3 on page 3-4.

—OR—

If there are products listed in the Select Product to Install scrolling list, go on to step 6.



Installin

g T

ivoli M

anag

er fo

rS

ybase

6. Select one of the following from the Select Product to Install scrolling list:

• Select Tivoli Manager for Sybase - Framework to install the Framework extension.

Note: You must install Tivoli Manager for Sybase - Framework on the TMR server and on any client where you want to manage Sybase servers or Sybase databases.

• Select Tivoli Manager for Sybase - Distributed Monitoring, Version 1.1 to install the Distributed Monitoring extension.

Note: You must install Tivoli Manager for Sybase - Distributed Monitoring on any client where you want to run monitors.

• Optionally, select Tivoli Manager for Sybase - GEM Instrumentation, Version 1.1 to install the Tivoli GEM extension. See Chapter 7, “Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation.”


3–8 Version 1.1

7. Select the clients to install the product on.

a. Select one or more clients from the Available Clients scrolling list.

Note: You must install Tivoli Manager for Sybase - Framework on the TMR server and on any client where you want to manage Sybase servers or Sybase databases. Also, you must install the Tivoli Manager for Sybase - Distributed Monitoring on any client where you want to run monitors.

b. Click the left arrow button to move the selection to the Clients to Install On scrolling list.

Note: If you decide not to install the product on a client listed in the Clients to Install On scrolling list, select its name, then click the right arrow button to move the selection to the Available Clients scrolling list.



Installin

g T

ivoli M

anag

er fo

rS

ybase

8. To install the product, do one of the following:

Click the Install button to install the product and keep the Install Product dialog open. You can then install the same product on another set of clients, or you can install another product.

—OR—

Click the Install & Close button to install the product and close the Install Product dialog.

9. The installation process prompts you with a Product Install dialog similar to the example on page 3-10. This dialog provides the list of operations that takes place during installation. It also warns about any problems that you might want to correct before you install the application.


3–10 Version 1.1

10. Click the Continue Install button to start the installation, or click the Cancel button to abort the installation. You might do this if any problems are reported in the dialog.

When the installation is complete, the Product Install dialog returns a completion message similar to the example on page 3-11.



Installin

g T

ivoli M

anag

er fo

rS

ybase11. Click the Close button to close the Product Install dialog.

Note: After installing Tivoli Manager for Sybase - Framework, repeat the preceding steps to install Tivoli Manager for Sybase - Distributed Monitoring.


3–12 Version 1.1

Installing from the Command LineYou can use the winstall command to install Tivoli Manager for Sybase from the command line. The partial CLI syntax is as follows:

winstall –c <cdrom-dir> [–s <server>] –i <product> [–n] [–y] [<managed_node>]

where:

–c <cdrom-dir> Specifies the complete path to the installation files (images) for this product.

–s <server> Specifies the managed node in the TMR to use as the product’s installation server.

–i <product> Specifies the product that you want to install. A product installation index file ends with the file extension .IND. For example, the file SFRAME.IND is the installation index file for Tivoli Manager for Sybase - Framework.

–n Installs the product on all managed nodes that do not currently have the product installed. This argument is ignored if you enter a value for managed_node.

–y Specifies that the installation continues without prompting or confirmation.

<managed_node> Specifies the managed node on which a Tivoli product will be installed. Multiple managed nodes can be specified. If no managed nodes are specified, the product will be installed on all managed nodes in the TMR. In most cases, this argument will not be specified.

For more information on the winstall command, refer to the TME 10 Framework Reference Manual.



Installin

g T

ivoli M

anag

er fo

rS

ybase

The following example installs Tivoli Manager for Sybase - Framework on managed node banana. The installation will proceed without prompting for confirmation. The install files are in the directory /mnt on pip. The product installation index file is SFRAME. The installation directory locations are determined by the current settings.

winstall -c /mnt -s pip -i SFRAME banana

The next example installs Tivoli Manager for Sybase - Distributed Monitoring on managed node banana. The installation does not prompt for any confirmation. The install files are in the directory /mnt on pip. The product installation index file is SFRMSNT.

winstall -c /mnt -s pip -i SFRMSNT banana


3–14 Version 1.1

Tivioli Manager for Sybase User’s Guide 4–1

Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

4Setting Up Tivoli Manager for Sybase

This chapter provides the general setup procedures for Tivoli Manager for Sybase. It does not include the information for setting up monitor profiles (see Chapter 5, “Setting Up Monitoring Profiles”) or Tivoli Manager for Sybase GEM instrumentation (see Chapter 7, “Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation”).

Notes:

• For an overview of all the setup tasks, see the chart in Chapter 2, “Guidelines for Setting Up Tivoli Manager for Sybase.”

• Before you begin, you must install Tivoli Manager for Sybase. See Chapter 3, “Installing Tivoli Manager for Sybase.”

This chapter includes the following procedures:

■ Subscribing to notice groups

■ Adding the SybaseDataServer managed resource type

■ Registering Sybase servers

■ Integrating Tivoli Manager for Sybase with the Tivoli Enterprise Console (TEC)

4

Subscribing to Notice Groups

4–2 Version 1.1

Subscribing to Notice GroupsWhen you install Tivoli Manager for Sybase, it creates several notice groups. The software automatically subscribes the Root administrator to the Sybase SQL Server Management and Sybase Sentry notice groups during installation. You must subscribe any other administrators to the appropriate notice groups, which include the following:

■ The Sybase SQL Server Management notice group records Sybase Adaptive Server management activity and contains messages generated by Sybase Adaptive Server administrator activity. The notices include registering and removing endpoints and stopping and starting the Sybase Adaptive Server.

■ The Sybase Sentry notice group contains messages generated when a threshold is reached by a Tivoli Manager for Sybase monitor.

■ The SentryStatus notice group contains diagnostic messages if a monitor fails to run. (This notice group is not part of the Tivoli Manager for Sybase installation, but is created as part of the Tivoli distributed monitoring installation.)

The following table provides the context and authorization role required for this procedure:

You can perform this procedure only from the Tivoli desktop. For additional information about notice group subscriptions, see the TME 10 Framework User’s Guide.


Change a Tivoli administrator properties

Administrators collection

senior



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Use the following steps to subscribe administrators to notice groups:

1. From the Tivoli desktop, double-click on the Administrators icon to open the Administrators collection window.

2. Select the administrator you want to subscribe to the notice groups and click the right mouse button to display the pop-up menu.


4–4 Version 1.1

3. Select the Edit Notice Group Subscriptions... option to display the Set Notice Groups dialog.

The Current Notice Groups scrolling list displays the notice groups to which the administrator is currently subscribed.

The Available Notice Groups scrolling list displays the notice groups to which the administrator can subscribe.

4. Select one or more notice groups from the Available Notice Groups scrolling list.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

5. Click the left arrow button to move your selection to the Current Notice Groups scrolling list.

Note: Another way to move notice groups from one scrolling list to the other is by double-clicking on their name.

6. To remove a notice group subscription, do the following:

a. Select one or more of the notice groups in the Current Notice Groups scrolling list.

b. Use the right arrow button to move the notice groups into the Available Notice Groups scrolling list.

7. Click the Change & Close button to save the changes and return to the Administrators window.

Adding the SybaseDataServer Managed Resource Type

4–6 Version 1.1


Each policy region maintains a list of managed resource types that are valid or defined for that specific policy region. A managed resource is any hardware or software entity represented by a database object and an icon on the Tivoli desktop. SybaseDataServer is a type of managed resource. You can add or remove managed resource types at any time.

To register any Sybase server (SybaseDataServer, SybaseBackupServer, or SybaseMonitorServer) within a policy region, you must set SybaseDataServer as a current resource in the policy region. The software then does the following:

■ Assigns a default policy to the managed resource when you add it to a policy region.

■ Adds the managed resource type to the policy region’s Create menu so that you can create new instances of the managed resource in the policy region.

The following table provides the context and authorization role required for adding the SybaseDataServer managed resource type:



Add or remove a managed resource for a policy region

Policy region senior



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Adding or Removing a Managed Resource Type from the Desktop

Use the following steps to add or remove the SybaseDataServer managed resource type:

1. From the Tivoli desktop, double-click on the policy region icon that contains the Tivoli Manager for Sybase resource to display the Policy Region window.

2. Select the Properties –> Managed Resources... option.


4–8 Version 1.1

Tivoli displays the Set Managed Resources dialog.

The Current Resources scrolling list displays the policy region’s current managed resources.

The Available Resources scrolling list displays the managed resources that you can add to the policy region.

3. Select the SybaseDataServer managed resource from the Available Resources scrolling list.

4. Click the left arrow button to move your selection to the Current Resources scrolling list.

Note: Another way to move notice groups from one scrolling list to the other is by double-clicking on their name.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

5. To remove a managed resource from the policy region, do the following:

a. Select one or more managed resources in the Current Resources scrolling list.

b. Click the right arrow button to move the managed resource into the Available Resources scrolling list.

6. Click the Set & Close button to save the changes and return to the policy region window.

Adding or Removing a Managed Resource Type from the Command Line

Use the wgetpr and wsetpr commands to examine and change the managed resources of a policy region. For more information on these commands, refer to the TME 10 Framework Reference Manual.

Registering Sybase Servers

4–10 Version 1.1

Registering Sybase ServersTo access a Sybase server from the Tivoli desktop, you must register it. Registering the server creates it as an object in the Tivoli environment. The following subsections describe how to register a Sybase Adaptive Server and Sybase Backup Server with a policy region, and a Sybase Monitor Server with a Sybase Adaptive Server instance, from either the Tivoli desktop or the command line.

Registering a Sybase Adaptive Server and Sybase Backup Server

The Sybase Adaptive Server you want to register must be installed on a host that is a managed node in the TMR. When you register a Sybase Adaptive Server in a connected TMR environment, register it in a policy region on the same TMR as the host (managed node) for the server.

To register a Sybase Adaptive Server, you enter information about the Sybase Adaptive Server and Sybase Backup Server in either a registration form on the Tivoli desktop or on the command line. The SybaseDataServer icon appears in the Policy Region window, and the SybaseBackupServer icon appears in the Sybase Data Server collection window.

Once you register a Sybase Adaptive Server, Tivoli Manager for Sybase automatically discovers the server’s databases. Their endpoints also appear in the Sybase Data Server collection window. You can then subscribe the server endpoints and database endpoints to profiles in profile managers in the same way as any other managed resource.

The following table provides the context and authorization role required for registering Sybase Adaptive Server and discovering its databases.


Register a Sybase Adaptive Server

Policy region sybase_dba and senior in the TMR



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase


Registering a Sybase Adaptive Server from the Desktop

Complete the following steps to register a Sybase Adaptive Server (and automatically register a Sybase Backup Server) from the desktop:

1. From the Tivoli desktop, double-click the policy region icon that contains the SybaseDataServer resource. The Policy Region window is displayed.

2. Select the Create –> SybaseDataServer... option.


4–12 Version 1.1

This displays the Register Sybase SQL Server dialog.

Notes:

• When entering text in the fields on Tivoli Manager for Sybase dialogs, do not leave spaces at the end of strings. Any trailing blank spaces will be taken as part of the text string, resulting in a “resource not found” error message.

• If the Sybase Adaptive Server is running on Windows NT, be sure to give the fully-qualified Microsoft DOS file name when specifying any file name. In particular, make sure all of the file extensions are included. When registering the Sybase Adaptive Server pip_1150DS, for example, the following name might be used for the run script: C:\data2\Sybase1150\install\RUN_pip_1150DS.bat



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

3. Enter the name of the Sybase Adaptive Server in the Data Server Name field.

4. Enter the full path to the Sybase installation location in the Directory field.

5. Enter the full path to the interfaces file location in the Interface File field.

6. Enter the name of the host computer in the Host Name field. The host must be a managed node in the TMR and have Tivoli Manager for Sybase installed.

7. Enter the Sybase user name and password that Tivoli Manager for Sybase will use to connect to the Sybase Adaptive Server, Sybase Backup Server, and Sybase Monitor Server (if it is registered).

8. Specify the operating-system-level user name and group to use when starting processes. Enter a user name in the OS User field and a group name in the OS Group field.

Note: If the Sybase Adaptive Server is running on NT, you can leave the OS User and OS Group fields at their default value, or enter empty double quotes (“ ” ).

9. Enter the full path to the location of the Sybase Adapter Server’s run script in the Data Server Run Script field and error log file in the Data Server Error Log field.

10. Enter the name of the Sybase Backup Server as it appears in the interfaces file in the Backup Server Name field.

11. Enter the full path to the location of the Sybase Backup Server’s run script in the Backup Server Run Script field and error log file in the Backup Server Error Log field.

12. Select the Ignore Server Status check box to register a Sybase Adaptive Server, a Sybase Backup Server, or both, that are not running.


4–14 Version 1.1

During registration, Tivoli Manager for Sybase attempts to connect to the Sybase Adaptive Server and Sybase Backup Server. If the Ignore Server Status check box is selected, a failure to connect to either server will be ignored. However, if the Ignore Server Status check box is not selected, then such a failure results in the registration of the Sybase Adaptive Server and Sybase Backup Server failing.

Some administrators might not want to use the Ignore Server Status option. When you use this option and the Sybase Adaptive Server is not running, the databases associated with the server are available only when you refresh the server’s collection of objects with the View –> Refresh menu option when the server is running and Tivoli Manager for Sybase can get a connection to it.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

The completed Register SQLServer dialog will look something like the following example.


4–16 Version 1.1

13. Click the Register & Close button.

Tivoli Manager for Sybase checks that the server exists and is accessible. It then registers the server and updates its collection of objects, which includes databases. Upon successful registration, Tivoli displays the server icon in the Policy Region window.

Registering a Sybase Adaptive Server from the Command Line

You can use the sregsqlsvr command to register a Sybase Adaptive Server and a Sybase Backup Server with a policy region.

Details of this command are described below and in UNIX online manual pages. For additional information about individual command options, refer to the descriptions of the corresponding GUI data entry fields, as described in the previous subsection, “Registering a Sybase Adaptive Server from the Desktop” on page 4-11.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Note: If the Sybase Adaptive Server is running on Windows NT, be sure to give the fully-qualified Microsoft DOS file name when specifying any file name. In particular, make sure all of the file extensions are included. When registering the Sybase Adaptive Server pip_1150DS, for example, the following run script name is required: C:\data2\Sybase1150\install\RUN_pip_1150DS.bat

The CLI syntax for the sregsqlsvr command is:

sregsqlsvr <host_name> <policy_region> <dataserver_name> <sybase_dir> <interface_file> <sybaseuser_name> <sybaseuser_password> <os_user> <os_group> <dataserver_runscript> <dataserver_errorlog> <backupserver_name> <backupserver_runscript> <backupserver_errorlog> {TRUE | FALSE}

where:

<host_name> Specifies the name of the managed node on which the Sybase Adaptive Server being registered is installed. This managed node must be in the TMR and have Tivoli Manager for Sybase installed.

<policy_region> Specifies the name of the policy region with which the SybaseDataServer instance will be registered.

<dataserver_name> Specifies the name of the Sybase Adaptive Server as it appears in the interfaces file.

<sybase_dir> Specifies the installation directory of the Sybase Adaptive Server. Enter either the full path to the installation directory or the environment variable set in the environment. (Usually, this is $SYBASE on UNIX, or %SYBASE% on Windows NT.)

<interface_file> Specifies the location and name of the interfaces file.

<sybaseuser_name> Specifies the user name to use when logging in to the Sybase Adaptive Server.


4–18 Version 1.1

<sybaseuser_password> Specifies the password to use when logging in to the Sybase Adaptive Server.

<os_user> Specifies the operating-system-level user name to use when starting processes.

Note: If the Sybase Adaptive Server is running on Windows NT, enter empty double quotes (“ ” ) to set this variable to NULL.

<os_group> Specifies the operating-system-level group to use when starting processes.

Note: If the Sybase Adaptive Server is running on Windows NT, enter empty double quotes (“ ” ) to set this variable to NULL.

<dataserver_runscript> Specifies the location and name of the Sybase Adaptive Server’s run script.

<dataserver_errorlog> Specifies the location and name of the Sybase Adaptive Server’s error log file.

<backupserver_name> Specifies the name of the Sybase Backup Server as it appears in the interfaces file.

<backupserver_runscript> Specifies the location and name of the Sybase Backup Server’s run script.

<backupserver_errorlog> Identifies the location and name of the Sybase Backup Server’s error log file.

TRUE Ignores the result of a connectivity check. Choosing TRUE allows the Sybase Adaptive Server and Sybase Backup Server to be registered whether or not one or both are running.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

FALSE Enables rollback of registration if a connectivity check fails. Choosing FALSE means that registration will fail if the Sybase Adaptive Server or Sybase Backup Server is not running.

For example, to add a new Sybase Adaptive Server, pip_1150DS, to the pip-region policy region, use the following command. (It is assumed that your Sybase Adaptive Server is installed in the /data2/Sybase1150 directory.)

% sregsqlsvr pip pip-region pip_1150DS /data2/Sybase1150 \/data2/Sybase1150/interfaces sa secret sybase dba \/data2/Sybase1150/install/RUN_pip_1150DS \/data2/Sybase1150/istall/pip_1150DS.log pip_1150BS \/data2/Sybase1150/install/RUN_pip_1150BS \/data2/Sybase1150/install/pip_1150BS.log TRUE

Note: After successfully running the sregsqlsvr command, the next time you open the Policy Region window, the SybaseDataServer icon for the newly-registered Sybase Adaptive Server is displayed. Likewise, when you next open the Sybase Data Server collection window, the SybaseBackupServer icon is displayed. If either the Policy Region window or Sybase Data Server collection window is already open, use the View –> Refresh menu option to display the icons.

Registering a Sybase Monitor ServerThe Sybase Monitor Server you want to register must be installed on a host that is a managed node in the TMR. After you register the server, it appears as an endpoint icon in the Sybase Data Server collection window for the Sybase Adaptive Server that it is configured to monitor.

The following table provides the context and authorization role required for registering Sybase Monitor Servers.


Register a Sybase Monitor Server

Sybase Data Server sybase_dba and senior in the TMR


4–20 Version 1.1


Registering a Sybase Monitor Server from the Desktop

Use the following steps to register a Sybase Monitor Server from the desktop:

1. From the Tivoli desktop, right-click on the icon for the Sybase Adaptive Server you would like to register a SybaseMonitorServer instance with, then select the Register Monitor Server... option.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

This displays the Register Monitor Server dialog.

Notes:

• When entering text in the fields on Tivoli Manager for Sybase dialogs, do not leave spaces at the end of strings. Any trailing blank spaces will be taken as part of the text string, resulting in a “resource not found” error message.

• If the Sybase Monitor Server is running on Windows NT, be sure to give the fully-qualified Microsoft DOS file name when specifying any file name. In particular, make sure all of the file extensions are included. When registering the Sybase Monitor Server pip_1150MS, for example, the following name might be used for the run script: C:\data2\Sybase1150\install\RUN_pip_1150MS.bat

2. In the Server Name field, enter the name of the Sybase Monitor Server as it appears in the interfaces file.


4–22 Version 1.1

3. The read-only Host field is for informational purposes only. It gives the name of the host computer on which the Sybase Monitor Server exists. The Sybase Adaptive Server it is monitoring must exist on the same host.

4. Enter the full path to the Sybase installation location in the Directory field.

5. Enter the full path to the interfaces file location in the Interface File field.

6. Enter the full path to the Sybase Monitor Server’s run script location in the Run Script field and to its error log file location in the Error Log field.

7. Check the Ignore Server Status check box to register a Sybase Monitor Server that is not running.

During registration, Tivoli Manager for Sybase attempts to connect to the Sybase Monitor Server. If the Ignore Server Status check box is checked, then a failure to connect to the server will be ignored. However, if the Ignore Server Status check box is not checked, then in case of such a failure, the Sybase Monitor Server is not registered.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

The completed Register Monitor Server dialog will look similar to the following:

8. Click the Register & Close button.

Tivoli Manager for Sybase checks that the Sybase Monitor Server exists and is accessible. It then registers the server and updates its collection of objects.


4–24 Version 1.1

Upon successful registration, Tivoli displays the server icon in the Sybase Data Server collection window (shown in the lower right corner of the following example).

Registering a Sybase Monitor Server from the Command Line

You can use the sregmonsvr command to register a Sybase Monitor Server with a SybaseDataServer instance.

Details of this command are described below and in UNIX online manual pages. For additional information about individual command options, refer to the descriptions of the corresponding GUI data entry fields, as described in the previous subsection, “Registering a Sybase Monitor Server from the Desktop” on page 4-20.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Note: If the Sybase Monitor Server is running on Windows NT, you must give the fully-qualified Microsoft DOS file name when specifying any file name. In particular, ensure that all the file extensions are included. When registering the Sybase Monitor Server pip_1150MS, for example, the following run script name is required: C:\data2\Sybase1150\install\RUN_pip_1150MS.bat

The CLI syntax for the sregmonsvr command is as follows:

sregmonsvr <dataserver_label> <monitorserver_name> <monitor_home> <interfaces_file> <runscript> <errorlog> {TRUE | FALSE}

where:

<dataserver_label> Specifies the icon label of the existing SybaseDataServer instance.

<monitorserver_name> Specifies the name of the Sybase Monitor Server as it appears in the interfaces file.

<monitor_home> Specifies the installation directory of the Sybase Monitor Server. Enter either the full path to the installation directory or the environment variable set in the environment. (Usually, this is $SYBASE on UNIX, or %SYBASE% on Windows NT.)

<interfaces_file> Specifies the location and name of the interfaces file.

<runscript> Identifies the location and name of the Sybase Monitor Server’s run script.

<errorlog> Identifies the location and name of the Sybase Monitor Server’s error log.

TRUE Ignores the result of a connectivity check. Choosing TRUE enables the Sybase Monitor Server to be registered whether or not it is running.

Integrating with the Tivoli Enterprise Console

4–26 Version 1.1

FALSE Enables rollback of registration if a connectivity check fails. Selecting FALSE means that registration will fail if the Sybase Monitor Server is not running.

For example, to add a new Sybase Monitor Server, pip_1150MS, to the pip_1150DS@pip SybaseDataServer instance, use the following command. It is assumed that your Sybase Monitor Server is installed in the /data2/Sybase1150 directory.

% sregmonsvr pip_1150DS@pip pip_1150MS /data2/Sybase1150 \/data2/Sybase1150/interfaces \/data2/Sybase1150/install/RUN_pip_1150MS \/data2/Sybase1150/install/pip_1150MS.log FALSE

Note: After successfully running the sregmonsvr command, the next time you open the Sybase Data Server collection window, the SybaseMonitorServer icon is displayed. If the collection window is already open, use the View –> Refresh menu option to display the icon.

Integrating with the Tivoli Enterprise ConsoleThis section provides information about integrating Tivoli Manager for Sybase with the TEC. You can skip this section if you do not have the TEC or do not want to send information to it.

This section includes the following:

■ An overview of the TEC

■ An overview of how Tivoli Manager for Sybase integrates with the TEC

■ A procedure for configuring the TEC to receive monitoring events

Overview of the TECIn distributed computing environments, it is essential to address events and conditions that can lead to problems in a timely and efficient manner. The TEC provides the tools for handling problems and for ensuring the availability of applications.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

The event is the central unit of information in the TEC. An event is any significant change in the state of a system resource or application. The TEC accepts almost any type of event, such as network, system, performance, application, and database events.

The TEC uses rules to provide event correlation, which helps determine the severity and relationship of events.

Also, the TEC can provide automatic responses to many common events. For example, when a database becomes unavailable and Tivoli Manager for Sybase monitoring detects the change in state, you can set up responses, such as alerting an administrator or trying to restart the Sybase Adaptive Server.

For more information about the TEC, refer to the TME 10 Enterprise Console User’s Guide.

How Tivoli Manager for Sybase Integrates with the TECTivoli Manager for Sybase uses distributed monitoring technology to forward events to the TEC. To enable the TEC to receive the Tivoli Manager for Sybase events, you must configure the event server to use a rule base that contains class definitions and rule sets. This section describes the event class structures and rule base.

Event Class Structures

An event class classifies an event and indicates the type of information that will be sent to the event server. Event classes are defined hierarchically; that is, child classes inherit attribute value defaults from the parent class. Tivoli Manager for Sybase defines three event classes supplied in the following .baroc files:

ESMSentry.baroc (supplied with Tivoli Manager for Sybase) The ESMSentry class is a child of the Sentry3_5_Base parent class, which is defined in the Sentry.baroc file. Severity levels are configurable at monitor run time. Tivoli Manager for Sybase does not assume severity levels by default.


4–28 Version 1.1

M7SybaseServer.baroc The SybaseServer class is a child of the ESMSentry parent class, which is a child of the Sentry3_5_Base parent class. Each Tivoli Manager for Sybase monitor class is a child class of the SybaseServer class. None of the child classes has additional slots defined, hence the slots of the Sentry3_5_Base class are used. Sentry3_5_Base is a child class of Sentry2_0_Base, which is a child of the EVENT class.

M7SybaseDatabase.baroc The SybaseDatabase class is a child of the ESMSentry parent class, which in turn is a child of the Sentry3_5_Base parent class. Each Tivoli Manager for Sybase database monitor class is a child class of the SybaseDatabase class. None of the child classes has additional slots defined, hence the slots of the Sentry3_5_Base class are used. Sentry3_5_Base is a child class of Sentry2_0_Base, which in turn is a child of the EVENT class.

Note: You must configure the event server to use a rule base that contains the Tivoli Distributed Monitoring event class definitions. Procedures for doing so are given in “Manually Configuring the TEC” on page 4-31.

The following table shows the class names of all events defined for Tivoli distributed monitoring. Tivoli Manager for Sybase passes on the severity set for each event class; therefore, the following table indicates the severity as Unknown.

Event Class Severity

ESMSentry

SybaseServer

SybaseServer_BackupServerErrors Unknown

SybaseServer_BadProcesses Unknown



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

SybaseServer_BlockedProcesses Unknown

SybaseServer_ConnectionsAvailable Unknown

SybaseServer_ConnectionsInUse Unknown

SybaseServer_CPUByProcess Unknown

SybaseServer_CurrentlyOpenDatabases Unknown

SybaseServer_DatabaseStatus Unknown

SybaseServer_DataServerErrors Unknown

SybaseServer_DataServerErrorsBySeverity Unknown

SybaseServer_DeviceMirrorStatus Unknown

SybaseServer_EngineCPUBusy Unknown

SybaseServer_EngineStatus Unknown

SybaseServer_InfectedProcesses Unknown

SybaseServer_LocksAvailable Unknown

SybaseServer_LocksInUse Unknown

SybaseServer_LongRunningTransactions Unknown

SybaseServer_MemoryUsageByProcess Unknown

SybaseServer_PacketErrors Unknown

SybaseServer_PacketsReceived Unknown

SybaseServer_PacketsSent Unknown

SybaseServer_PercentConnectionsUsed Unknown

SybaseServer_PercentLocksAvailable Unknown

SybaseServer_PercentLocksUsed Unknown

SybaseServer_PercentTransactionLogSpaceUsed Unknown



4–30 Version 1.1

The Rule Base

The TEC uses a rule base to manage events. A rule base is a set of rules and event class definitions for which the rules are written. The TEC has a Default rule base, which you cannot edit. You must create a new rule base and then import Tivoli Manager for Sybase event classes into it. You can also copy the Default rule base (or any other rule base) to this rule base.

Procedures for setting up the TEC to import classes into a new or existing rule base are given in the section, “Manually Configuring the TEC,” which follows.

SybaseServer_PhysicalIOByProcess Unknown

SybaseServer_SLDFreeSpace Unknown

SybaseServer_SLDFreeSpaceByDevice Unknown

SybaseServer_SLDSpaceUsedByDevice Unknown

SybaseServer_SQLServerStatus Unknown

SybaseServer_StoppedProcesses Unknown

SybaseServer_UserCPUBusy Unknown

SybaseDatabase

SybaseDatabase_DataBaseState Unknown

SybaseDatabase_FreeFormSQLNumeric Unknown

SybaseDatabase_FreeFormSQLString Unknown

SybaseDatabase_FreeSegmentSpaceBySegment Unknown

SybaseDatabase_PercentFreeSegmentSpace Unknown

SybaseDatabase_PercentTransactionLogSpaceUsed Unknown

SybaseDatabase_TransactionLogFreeSpace Unknown

SybaseDatabase_UsedSegmentSpaceBySegment Unknown




Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Manually Configuring the TECAll monitors provided by Tivoli Manager for Sybase can send events to the TEC. To do this, you must do the following:

■ Install the TEC. (Refer to the TME 10 Enterprise Console User’s Guide.)

■ Configure the TEC manually (described in this section).

■ Configure the individual monitors to send events to the TEC. (See “Sending Events to the TEC” on page 5-29.)

Once you have set up the TEC, you can receive events through it (see “Viewing Events in the Tivoli Enterprise Console” on page 6-96).

This section describes how to do the following:

■ Create a new rule base and import events into it

■ Import events into an existing rule base

■ Create event filters

For further information on the TEC, refer to the Tivoli Enterprise Console User’s Guide.

The following table provides the context and authorization roles required for configuring the TEC.

You can perform this procedure from either the Tivoli desktop or the command line. For more information, refer to the Tivoli Enterprise Console Rule Builder’s Guide.


Configure the TEC Managed node (where the event server is installed)

senior


4–32 Version 1.1

The procedures and examples given for manually configuring the TEC make the following assumptions:

■ The event server is installed on the same managed node as the TMR server. If the event server is installed on a managed node other than the TMR server and Tivoli Manager for Sybase is not installed on that node, you might need to copy the .baroc files required to configure the TEC to the event server node.

■ You are creating and configuring a rule base named SybaseBase.

■ You will copy the Default rule base.

■ The rule base directory is $BINDIR/TME/TEC/rulebase_name.

■ You are creating and configuring an event group called SybaseBaseEvent.

■ You loaded the rule base that you created and will restart the event server after configuration.

■ This is not an inter-region environment.

■ You will configure the Tivoli environment by running the setup_env script.

■ You have the appropriate roles to create event server objects.

Creating a New Rule Base and Importing Events

Notes:

• If you already have a rule base set up, skip this section and go to “Importing Event Classes into an Existing Rule Base” on page 4-34.

• The order in which the class and rule set files are imported into a rule base is important. Follow the order in which these files are defined in step 4 on page 4-33.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

Follow these steps to create a new rule base and import events:

1. The event server must be installed before you can configure the TEC. Make sure the event server has been installed and registered by entering the following at the command line:

wlookup -ar EventServer

The wlookup command returns one line similar to the following example—the actual object identification number (OID) will be different.

EventServer 1875322890.1.805#Tec::Server#

If you have an interconnected TMR with an event server installed in each TMR, these event servers will appear as fully-qualified individual entries in the output.

2. Create a new rule base by entering the following command:

wcrtrb -S @EventServer:EventServer \-d $BINDIR/TME/TEC/SybaseBase SybaseBase

3. Copy the Default rule base into the new rule base by entering the following command:

wcprb -S @EventServer:EventServer Default SybaseBase

4. Configure the TEC for Tivoli Manager for Sybase distributed monitoring by entering the following:

Note: Do not type the numbers that precede each entry. They are for reference purposes only.

1 wimprbclass -S @EventServer:EventServer \ tivoli_install_dir/generic/SentryMonitors/ \Sentry.baroc SybaseBase

2 wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ \ SybaseSentry/ESMSentry.baroc SybaseBase

3 wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ \ SybaseSentry/M7SybaseServer.baroc SybaseBase


4–34 Version 1.1

4 wimprbclass -S @EventServer:EventServer \tivoli_install_dir/generic/ \ SybaseSentry/M7SybaseDatabase.baroc \ SybaseBase

5 wcomprules -S @EventServer:EventServer \ SybaseBase

5. Load the rule base by entering the following:

wloadrb -S @EventServer:EventServer SybaseBase


If event server is running, enter the following:

1 wstopesvr -S @EventServer:EventServer

2 wstartesvr -S @EventServer:EventServer

—OR—

If event server is not running, enter the following:

wstartesvr -S @EventServer:EventServer

Importing Event Classes into an Existing Rule Base

This section describes how to import the Tivoli Manager for Sybase event classes into an existing rule base that has been set up to receive Tivoli Distributed Monitoring events. The rule base in the following example is named SybaseBase.

1. Change directories to tivoli_install_dir/generic/SybaseSentry containing theTivoli Manager for Sybase .baroc files.

Note: The .baroc files that define the event classes are installed only on the TMR server.

2. If your TEC server is a different system, copy the files from the TMR server to the TEC server.



Settin

g U

p T

ivoli M

anag

er fo

r Syb

ase

3. Enter the following commands:

Note: You must first import the Sentry.baroc file, if it does not already exist in the rule base.

wimprbclass -S @EventServer:EventServer \ ESMSentry.baroc SybaseBase

wimprbclass -S @EventServer:EventServer \M7SybaseServer.baroc SybaseBase

wimprbclass -S @EventServer:EventServer \M7SybaseDatabase.baroc SybaseBase

4. Enter the following command to compile the new rule base:

wcomprules -S @EventServer:EventServer SybaseBase

5. Stop the event server by entering the following command:

wstopesvr -S @EventServer:EventServer

6. Load the new rule base with the following command:

wloadrb -S @EventServer:EventServer SybaseBase

7. Restart the event server by entering the following command:

wstartesvr -S @EventServer:EventServer

Creating Event Filters

By default, all severity and status levels are displayed in the event message list. You can select the severity or status levels you want to see displayed for specified events. For information about using the Tivoli desktop to display events based on severity and status, refer to the Tivoli Enterprise Console User’s Guide; or if you are using the command line, refer to the Tivoli Enterprise Console Reference Manual or the UNIX manual page for the wlsemsg command.


4–36 Version 1.1


Settin

g U

p M

on

itorin

g

Pro

files

Setting Up Monitoring Profiles

This chapter provides information on how to set up distributed monitoring profiles for distribution to server and database endpoints. (For information on how to subscribe and distribute profiles that you create, see “Subscribing Endpoints to Profile Managers” on page 6-80 and “Distributing a Monitoring Collection Profile” on page 6-84.)

This chapter includes the following topics:

■ An overview of monitoring

■ A chart that provides an overview of all the steps involved in setting up the monitoring profiles

■ Procedures for setting up monitors from the Tivoli desktop or the command line

5

Overview of Monitoring

5–2 Version 1.1

Overview of Monitoring Tivoli distributed monitoring uses profiles to store and distribute application-specific data. A Tivoli distributed monitoring record defines the characteristics of each monitor. A monitor captures and returns information about a resource or application in the Tivoli environment, such as the database status or whether a server is available or not. A monitoring profile is a group of defined monitors in a profile that can be distributed to the subscribed resource within a profile manager.

The monitor definition includes information such as how often to check the status and what to do when certain conditions are met. Tivoli Manager for Sybase does not provide predefined settings and response actions for its monitors; however, the Tivoli Manager for Sybase Reference Guide includes suggested settings and response actions for some monitors.

Before running a monitor, you must subscribe the database or server resource to the profile manager containing the profile in which the monitor is stored. You can then distribute the profile to the resource.

Monitors are organized into groups called monitoring collections. Tivoli Manager for Sybase has two monitoring collections: SybaseServer and SybaseDatabase.

For a brief description of each monitoring collection and their functional groups and monitor types, see Appendix A, “Monitoring Collection Information.” For a full description of each monitor, see the Tivoli Manager for Sybase Reference Guide.

Guidelines for Setting up Monitoring ProfilesThe following table provides an overview of the procedures used in setting up monitoring profiles. Each of the following steps is described in detail later in this chapter.

Note: The following table is one suggested method for setting up monitors; you might decide to use a different method as you gain experience with the system.

Guidelines for Setting up Monitoring Profiles


Settin

g U

p M

on

itorin

g

Pro

files

For more information on adding and editing monitors, refer to the TME 10 Distributed Monitoring User’s Guide.

Procedure For Additional Information

1. Designate a policy region to contain the resources you want monitored.

See “Adding the SybaseDataServer Managed Resource Type” on page 4-6.

See step 1 in “Setting Up Monitors from the Command Line” on page 5-45.

2. Add a profile manager and a profile to the policy region.

See “Adding a Profile Manager and a Profile” on page 5-6.

See steps 2 and 3 in “Setting Up Monitors from the Command Line” on page 5-45.

3. Associate an indicator collection with the profile or profiles you create (optional).

See “Associating an Indicator Collection with a Profile” on page 5-15.


4. Add monitors to the profile and define or edit them.

See “Adding Monitors to a Profile” on page 5-19.


a. Specify response levels, triggering conditions, and the nature of the response for each monitor.

See “Specifying Response Levels” on page 5-23.


b. Set up monitoring events to be sent to the Tivoli Enterprise Console (TEC) (optional).

See “Manually Configuring the TEC” on page 4-31.

See “Sending Events to the TEC” on page 5-29.


Authorization Roles for Setting Up Monitors

5–4 Version 1.1

Authorization Roles for Setting Up MonitorsThe following table summarizes the required roles for the procedures used in setting up monitors:

You can perform these procedures from either the Tivoli desktop or the command line.

c. Schedule the monitor (optional).

See “Scheduling the Monitor” on page 5-31.

5. Set a default user and group ID for the profile.

See “Setting the User and Group ID for a Profile” on page 5-42.


6. Save the profile. See “Saving the Profile” on page 5-44.

Procedure For Additional Information


Add a profile to a profile manager

Profile manager admin

Add an indicator collection Policy region admin

Add and edit a monitor Distributed Monitoring profile

admin

Set user and group ID (default policy)

Distributed Monitoring profile

senior

Setting Up Monitors from the Desktop


Settin

g U

p M

on

itorin

g

Pro

files

Setting Up Monitors from the DesktopThis section explains how to use the Tivoli desktop to set up monitors. It includes the following topics:

■ Adding a profile manager and a profile

■ Adding an indicator collection

■ Associating an indicator collection with a profile

■ Adding monitors to a profile

■ Specifying response levels

■ Sending events to the TEC

■ Scheduling the monitor

■ Setting the user and group ID for a profile

■ Saving the profile

If you prefer to set up monitors from the command line, see “Setting Up Monitors from the Command Line” on page 5-45.


5–6 Version 1.1

Adding a Profile Manager and a ProfileUse the following steps to add a profile manager and profile to the policy region:

1. From the Tivoli desktop, double-click on the appropriate policy region icon. This displays the Policy Region window.

2. To create the profile manager, do the following:

a. Select the Create -> Profile Manager option.



Settin

g U

p M

on

itorin

g

Pro

files

The Create Profile Manager dialog is displayed.

b. Type a unique name that identifies the profile manager icon in the Name/Icon Label field.

c. Do not select the Dataless Endpoint Mode check box. For more information on this option, refer to the TME 10 Framework User’s Manual.


5–8 Version 1.1

d. Click the Create & Close button to return to the Policy Region window.

The icon for the profile manager is displayed with the assigned name. The following example shows the policy region pip-region with the profile manager Server Monitors icon in the center.



Settin

g U

p M

on

itorin

g

Pro

files

3. Create a profile.

a. Double-click on the profile manager icon to display the Profile Manager window.


5–10 Version 1.1

b. Select the Create –> Profile option to display the Create Profile dialog.

Note: If the SentryProfile selection is not available, it has not been added as a resource for this policy region. Use the Properties –> Managed Resources menu option in the Policy Region window to display the Set Managed Resource menu. Move SentryProfile from the Available Resources scrolling list to the Current Resources scrolling list.

c. Type a unique name for the profile icon in the Name/Icon Label field.

d. Select SentryProfile from the Type scrolling list.

e. Click the Create & Close button.



Settin

g U

p M

on

itorin

g

Pro

files

The new profile icon is displayed in the Profile Manager window.


Associate an indicator collection with the profile (optional). See “Associating an Indicator Collection with a Profile” on page 5-15.

—OR—

See “Adding Monitors to a Profile” on page 5-19.


5–12 Version 1.1

Adding an Indicator CollectionAdding an indicator collection to the policy region is optional. However, if you want to view the status icons for TME 10 Distributed Monitoring profiles, you must create an indicator collection for the policy region. See the TME 10 Distributed Monitoring User’s Guide for additional information on indicator collections.

Tivoli suggests that, in general, you create only one collection in each policy region. This simplifies keeping track of TME 10 Distributed Monitoring profiles in several profile managers. However, if you have a policy region with too many TME 10 Distributed Monitoring profiles to handle reasonably in one collection, you can create as many collections as you need in a policy region.

Use the following steps to add an indicator collection:

1. From the Tivoli desktop, double-click on the icon for the policy region containing the SybaseDataServer endpoint. This displays the Policy Region window.

2. Select the Create –> IndicatorCollection option.



Settin

g U

p M

on

itorin

g

Pro

files

Note: If the IndicatorCollection selection is not on the Create menu, it has not been added as a resource for this policy region. Use the Properties –> Managed Resources option to display the Set Managed Resource menu. Move IndicatorCollection from Available Resources to Current Resources.

The Create Indicator Collection dialog is displayed.

3. Type a unique name for the indicator collection in the Name field. If two indicator collections with the same name exist in the TMR, TME 10 Distributed Monitoring cannot distribute status information.

4. Click the Create & Close button.


5–14 Version 1.1

An icon representing the indicator collection is displayed in the Policy Region dialog. (In the following example, the indicator icon is named sybase indicator.)

You can now associate this indicator collection with profiles.



Settin

g U

p M

on

itorin

g

Pro

files

Associating an Indicator Collection with a ProfileAssociating an indicator collection with a profile is optional. However, if you want to view the status icons for distributed monitoring profiles, you must do so.

If you do not already have an indicator collection, you must create one. See “Adding an Indicator Collection” on page 5-12. The TME 10 Distributed Monitoring User’s Guide provides additional information on indicator collections.


Use the following steps to associate an indicator collection with the profile:


2. Double-click on the profile manager icon in the Policy Region window.

3. Double-click on the profile icon in the Profile Manager dialog to display the TME 10 Distributed Monitoring Profile Properties window. The name of the profile (Availability in this example) is displayed in the Configuration Profile field.


5–16 Version 1.1



Settin

g U

p M

on

itorin

g

Pro

files

4. Select the Monitoring –> Select Indicator Collection option.


5–18 Version 1.1

The Select Indicator Collection dialog is displayed.

5. Highlight the indicator collection you want to use.

6. Click the Set & Close button. The indicator collection is now associated with the profile.



Settin

g U

p M

on

itorin

g

Pro

files

Adding Monitors to a ProfileThis procedure describes how to select any monitors that you want to use in a profile and specify any arguments required by the monitors. For more information about specific monitors to include in the profile, see “Suggested Monitoring Profiles” on page A-2.


Use the following steps to add a monitor and specify arguments:

1. From the Tivoli desktop, click on a policy region icon to open the Policy Region window.

2. Double-click on the profile manager icon to open the Profile Manager window.

3. Double-click on the profile icon of your choice in the Profile Manager window to open the TME 10 Distributed Monitoring Profile Properties window.


5–20 Version 1.1

4. Click the Add Monitor... button to display the Add Monitor to TME 10 Monitoring Profile dialog.

5. Select a collection from the Monitoring Collections list. (Selecting a collection populates the Monitoring Sources scrolling list.)

The following collections are included:

SybaseServer Provides global Sybase Adaptive Server, Sybase Backup Server, and Sybase Monitor Server availability and performance monitoring facilities

Distribute these monitors to SybaseDataServer, SybaseBackupServer, and SybaseMonitorServer endpoints.



Settin

g U

p M

on

itorin

g

Pro

files

SybaseDatabase Provides database availability and performance monitoring facilities

Distribute these monitors to SybaseDatabase endpoints.

For more information about the selected collection, click the About This Collection... button to display the online help, or refer to Chapter 2, “The SybaseServer Monitoring Collection,” and Chapter 3, “The SybaseDatabase Monitoring Collection,” in the Tivoli Manager for Sybase Reference Guide.


5–22 Version 1.1

6. Select a monitor from the Monitoring Sources scrolling list. If the selected monitor has no arguments, the Monitor Arguments panel remains empty. However, if the selected monitor has arguments, the Monitor Arguments panel displays the fields for arguments.

7. Enter the responses for any fields in the Monitor Arguments panel. To find information about responses for these fields:

• Click the About This Monitor... button to display the online help for the monitor.

• Refer to the “GUI Data Entry Fields” sections in Chapter 2, “The SybaseServer Monitoring Collection,” and Chapter 3, “The SybaseDatabase Monitoring Collection,” of the Tivoli Manager for Sybase Reference Guide.



Settin

g U

p M

on

itorin

g

Pro

files

8. Click the Add Empty... button to add the monitor and display the Edit Monitor dialog.

Note: Clicking the Add With Defaults... button is not useful since Tivoli Manager for Sybase monitors do not have default settings at this time. Clicking this button will display the following message:

Default values are not available for this monitor. Choose Add Empty.

However, suggested settings and response actions for some monitors are given in the Tivoli Manager for Sybase Reference Guide.

9. Read the next section, “Specifying Response Levels.”

Specifying Response LevelsA response level allows you to associate triggered events to certain conditions. Response levels are critical, severe, warning, normal, and always. You can configure response levels to be reached only when a returned value meets a threshold that you define. For example, when the defined condition triggers a critical response level, you can specify a certain type of action to take. The always response level triggers an action at all times.

For each response level, adjust the type of actions and trigger values for each response required. You can specify any combination of the available responses, such as sending a notice to a notice group and logging to a file.

For general information about response levels, refer to the TME 10 Distributed Monitoring User’s Guide. For specific suggestions on response levels for each monitor, refer to the section called “Suggested Response Levels” in Chapter 2, “The SybaseServer Monitoring Collection,” and Chapter 3, “The SybaseDatabase Monitoring Collection,” of the Tivoli Manager for Sybase Reference Guide.



5–24 Version 1.1

Note: To perform this procedure, you must have the Edit Monitor dialog displayed. (See step 8 on page 5-23.)


If you just added the monitoring source using the procedure in “Adding Monitors to a Profile” on page 5-19 and the Edit Monitor dialog is displayed, go to step 3.

—OR—

If the Edit Monitor dialog is not displayed, do the following:

a. Double-click on the profile icon that contains the monitor you want to edit.

b. Select the monitor you want to edit.



Settin

g U

p M

on

itorin

g

Pro

files

c. Click the Edit Monitor... button to display the Edit Monitor dialog, which displays any previously-entered values at the top of the dialog.

2. Select the argument that you want to edit.

a. If the monitor has multiple arguments, click the up arrow or down arrow button by the argument name. (The buttons are not available when the monitor has no arguments or a single argument.)

b. Enter a new value in the text field.

3. Select a response level.

a. Select the Response level drop-down list to display the selection of responses.


5–26 Version 1.1

The following responses are available:

critical Triggers a response when the returned value meets a threshold that indicates an exceedingly serious problem.

severe Triggers a response when the returned value meets a threshold that indicates a serious, but not critical, problem.

warning Triggers a response when the returned value meets a threshold that indicates a problem important enough to require an alert.

normal Specifies that the returned value does not fall into the established thresholds for the critical, severe, or warning response levels.

This response does not accept a threshold setting.

always Triggers a response whenever the monitor returns any value.

Selecting the always response makes the trigger when and condition fields unavailable, since it indicates the response you want the application to always make, regardless of whether any of the other response level thresholds are triggered.

b. Select a response level.

4. Specify when you want the monitor to trigger at the selected response level.

a. Select the trigger when drop-down list to display the available operators.

b. Select an operator.

The operators are described in Appendix C, “Operator Groups,” of this guide and in the monitor descriptions in Chapter 2, “The SybaseServer Monitoring Collection,” and Chapter 3, “The SybaseDatabase Monitoring



Settin

g U

p M

on

itorin

g

Pro

files

Collection,” of the Tivoli Manager for Sybase Reference Guide.

5. Select one or more of the following actions to occur when the condition that you just specified is met.

Note: For detailed procedures to complete this step, refer to the TME 10 Distributed Monitoring User’s Guide.

Send Tivoli Notice Sends a notice to a specified notice group.

To receive the notice, you must be subscribed to the group. Use the drop-down list to display and select from the list of notice groups.

Popup Displays an alarm message on the desktops of either all administrators (the default) or of the specified administrator.

Click the Admins... button to display a list of administrators.

Change Icon Changes the icon state in an indicator collection to reflect the response level.

You must have an indicator collection associated with the profile.

Tasks... Performs a task specified in any task library.

Although Tivoli Manager for Sybase does not currently provide tasks, clicking this button will allow you to run other available Tivoli tasks.

Send E-mail to Sends e-mail to one or more e-mail addresses.

Separate multiple e-mail addresses with commas.


5–28 Version 1.1

Log to file Writes the information returned by the monitor to a log file.

If the file does not exist, distributed monitoring creates it. You must specify an existing directory for the file.

Note: There are further options available for the Log to file action; for details, refer to the TME 10 Distributed Monitoring User’s Guide.

Run program Launches a program or script

This response is executed under the same user ID and group ID as specified in the profile.

Note: There are further options available for the Run program action; for details, refer to the TME 10 Distributed Monitoring User’s Guide.

Send Enterprise Console event Sends the information returned by the monitor to a TEC server as an event


If you selected Send Enterprise Console event, see the next section, “Sending Events to the TEC.”

—OR—

If you did not select Send Enterprise Console event, see “Scheduling the Monitor” on page 5-31 (optional).

—OR—

If you do not want to send events to TEC or schedule monitors, you must select Change & Close on the Edit Monitor dialog before setting the user and group ID. (See “Setting the User and Group ID for a Profile” on page 5-42.)



Settin

g U

p M

on

itorin

g

Pro

files

Sending Events to the TECNote: You can skip this section if you do not want to send events to

the TEC.

This section describes how to send events from Tivioli Manager for Sybase to the TEC. The event server uses event groups to direct events to the appropriate consoles. For additional information, see “Manually Configuring the TEC” on page 4-31.


Use the following steps to create a TEC event:


If you have finished the procedure in the previous section, “Specifying Response Levels,” go to step 4.

—OR—

If you have not yet finished the “Specifying Response Levels”procedure, go on to step 2.

2. Open the Edit Monitor dialog in a distributed monitoring profile.

3. Select a Response level for the event.

4. Select the Send Enterprise Console event check box.

5. Specify a severity level for the TEC event.

6. Select the TEC event server you wish to send the event to.


5–30 Version 1.1

The following example shows a completed Edit Monitor dialog. The SQL Server Status monitor sends an event to the TEC when it detects that the specified Sybase server is shut down.



Settin

g U

p M

on

itorin

g

Pro

files

Scheduling the MonitorYou can schedule monitors to capture information at specific times.

Note: You can skip this section if:

• You want to use the Tivoli-defined default monitoring schedule for the profile.

• You do not want to schedule individual monitors within the profile.

The Tivoli-defined default schedule for monitors is hourly. You can schedule monitors as frequently as once a minute. Base your monitoring frequency on how often you need updated information and the number of monitors running on a managed node. If you schedule too many monitors too frequently, you might impact system performance.

You have the following options for scheduling monitors:

■ Set your own default schedule for all monitors in a profile.

■ Set a different schedule for each monitor in the profile.

■ Set your own default schedule for the profile and set individual schedules for specific monitors in that profile.

Individual monitor schedules override profile schedules. For example, if you do the following:

■ Set your own default schedule for ProfileX, which contains MonitorA, MonitorB, MonitorC, and MonitorD.

■ Set individual schedules for MonitorA and MonitorB in ProfileX.

Then, when you distribute ProfileX:

■ MonitorA and MonitorB run according to their individual schedules.

■ MonitorC and MonitorD run according to the default schedule for ProfileX.

You can perform this task only from the Tivoli desktop.


5–32 Version 1.1

Setting Your Own Default Schedule for a Profile

Use the following steps to set default profile schedules:


2. Double-click on the profile manager icon in the Policy Region window.

3. Double-click on the profile icon in the Profile Manager dialog to display the TME 10 Distributed Monitoring Profile Properties window for the profile.



Settin

g U

p M

on

itorin

g

Pro

files

4. Select the Edit −> Set Default Schedule... option.

The Set Monitoring Schedule dialog is displayed.


5–34 Version 1.1

Note: The dialog displays the word Default under the profile name (which is Availability in this example).


To start capturing information when the monitor is distributed, do not specify any values in the Start monitoring activity area.

—OR—

To start the monitor at a specific time:

a. Specify the date in the Month, Day, and Year fields.

b. Specify the hour and the minute, then select either AM or PM.

6. Specify how often you want the monitor to run in a given time span with the Check monitor every field and corresponding option menu. Entering 5 and specifying minutes means the monitor is scheduled to run every five minutes.



Settin

g U

p M

on

itorin

g

Pro

files


Restrict this schedule to certain hours or days of the week. (See “Restricting a Schedule” on page 5-38.)

—OR—

Accept the schedule with the default restrictions, which allows monitoring at all times unless there are individual restrictions on individual monitors in the profile.

a. Click the Change & Close button.

b. Set up individual monitor schedules (optional). Go to “Setting Individual Schedules for Individual Monitors” on page 5-35.

c. Click the Change & Close button on the Edit Monitor dialog.

Setting Individual Schedules for Individual Monitors

Use the following steps to set individual monitoring schedules.

To perform this procedure, you must have the Edit Monitor dialog displayed.


If the Edit Monitor dialog is displayed, or if you just added the monitoring source using the procedure in “Adding Monitors to a Profile” on page 5-19, go to step 5.

—OR—

To display the Edit Monitor dialog, do the following:

a. From the Tivoli desktop, double-click on the appropriate policy region icon. This displays the Policy Region window.

b. Double-click on the profile manager icon in the Policy Region window.

c. In the Profile Manager dialog, double-click on the profile icon that contains the monitor.

d. Select the monitor you want to edit.


5–36 Version 1.1

e. Click the Edit Monitor... button to display the Edit Monitor dialog.



Settin

g U

p M

on

itorin

g

Pro

files

2. Click the Set Monitoring Schedule button to display the Set Monitoring Schedule dialog.

The dialog displays the name of the monitor that you want to schedule, in this example SQL Server Status, beneath the profile name, Availability. They appear in the upper right corner of the dialog.


To start capturing information immediately when the monitor is distributed, do not change the default values in the Start monitoring activity area.

—OR—

To start the monitor at a specific time in the future, do the following:

a. Specify the date in the Month, Day, and Year fields.

b. Specify the hour and the minute, then select either AM or PM.

4. Enter how often you want the monitor to run in a given time span with the Check monitor every field and corresponding option. For example, entering 15 and specifying minutes schedules the monitor to run every fifteen minutes.


5–38 Version 1.1


Restrict this schedule to certain hours or days of the week. (See “Restricting a Schedule” on page 5-38.)

—OR—

Accept the schedule with the default restrictions, which allows monitoring at all times unless there are individual restrictions on individual monitors in the profile.

a. Click the Change & Close button.

b. Click the Change & Close button on the Edit Monitor dialog.

c. Go to “Setting the User and Group ID for a Profile” on page 5-42.

Restricting a Schedule

This section tells you how to restrict a specific monitor schedule by setting broad parameters, such as certain hours or days of the week. The default restrictions allow monitoring all the time, unless there are individual restrictions on individual monitors in the profile.



Settin

g U

p M

on

itorin

g

Pro

files

1. Before starting this procedure, set up the schedule using the procedures in either “Setting Your Own Default Schedule for a Profile” on page 5-32 or “Setting Individual Schedules for Individual Monitors” on page 5-35.

2. Click the Restrictions... button on the Set Monitoring Schedule dialog to display the Monitoring Schedule Restrictions dialog.

3. Select one or more of the options under Allow Monitoring Activity:

During the day or At night Runs the monitor during hours set by distributed monitoring. These hours are selected by default. To customize the hours, go to step 5.

During the week or On weekends Runs the monitor on days set by distributed monitoring. These days are selected by default. To customize the days, go to step 5.


5–40 Version 1.1

4. You can now do one of the following:

To customize the restrictions by redefining the options, go to step 5.

—OR—

To accept these restrictions without customizing them, click the Set & Close button. You can then continue with setting up the user and group ID. (See “Setting the User and Group ID for a Profile” on page 5-42.)

5. Click the Customize... button to display the Customize Monitoring Schedule Restrictions dialog.

The AM and PM drop-down lists beside the Daytime hours and Nighttime hours labels mark the time spans set for the During the day and At night options on the Monitoring Schedule Restrictions dialog.

The day of the week drop-down lists beside Week days and Weekend days mark the time spans set for the During the week and On weekends options on the Monitoring Schedule Restrictions dialog.



Settin

g U

p M

on

itorin

g

Pro

files

The drop-down lists beside Custom hours and Custom days mark the time spans set for the those options on the Monitoring Schedule Restrictions dialog.

6. Select the options that customize the restrictions in the best way for your environment.

For example, if you selected the During the day check box to schedule the monitor to run from 3 a.m. through 2 p.m., select 3 and 2 in the AM and PM option menus for the Daytime hours field.

7. Click the Set & Close button to set your choices and return to the Monitoring Schedule Restrictions dialog.

8. Click the Set & Close button to return to the Set Monitoring Schedule dialog.

9. Click the Change & Close button to close the Set Monitoring Schedule dialog.

10. If you set restrictions after setting up the monitor schedule using the procedures in “Setting Your Own Default Schedule for a Profile” on page 5-32, then you have finished.

—OR—

If you set restrictions after setting up the monitor schedule using the procedures in “Setting Individual Schedules for Individual Monitors” on page 5-35, click the Change & Close button on the Edit Monitor dialog.


5–42 Version 1.1

Setting the User and Group ID for a ProfileThe user and group ID for a profile determine the operating system context under which a monitor executes. Only a Tivoli administrator who has the sybase_monitor role can run Sybase Adaptive Server monitors. The administrator must also have a login name for any system on which the monitor runs. You can see the logins for an administrator in the Edit Logins dialog in the Administrators’ collection.

Use the following steps to set the user and group ID:

1. Double-click on the profile manager icon to open the Profile Manager window, if it is not already open.

2. Double-click on the profile’s icon to display the TME 10 Distributed Monitoring Profile Properties window.



Settin

g U

p M

on

itorin

g

Pro

files

3. Select the Edit –> Set User & Group ID... option.

Tivoli displays the Edit Default Policies dialog.

4. Enter the name of the administrator in the Remote user ID field.


5–44 Version 1.1

The monitor runs in the context of the administrator account. This administrator must have a valid login on the operating system as well as a Tivoli login. The administrator must also have the appropriate roles. For example, if the Tivoli administrator: joedoe is running monitors on both UNIX and Windows NT hosts, joedoe must be a valid login name on both hosts and for Tivoli.

5. Set the Remote group ID field for that remote user ID.

6. Click the Change & Close button to return to the TME 10 Distributed Monitoring Profile Properties window.

Saving the ProfileOnce you have completed setting up your profile, you can save it using the following steps:

1. Display the TME 10 Distributed Monitoring Profile Properties window.

2. Select the Profile –> Save option.

Setting Up Monitors from the Command Line


Settin

g U

p M

on

itorin

g

Pro

files

Setting Up Monitors from the Command LineUse the steps in this section to set up your monitors from the command line.

For additional information about the commands in this section, refer to the TME 10 Framework Reference Manual and the TME 10 Distributed Monitoring User’s Manual.

1. Use the wsetpr command to specify the types of resources that you want to work with in your policy region. For example, to specify that the pip-region policy region can contain the SybaseDataServer and SentryProfile resource types, enter the following command:

wsetpr SybaseDataServer SentryProfile \@PolicyRegion:pip-region

2. Use the wcrtprfmgr command to create a profile manager. For example, to create a profile manager named “Server Monitors” in the pip-region policy region, enter the following command:

wcrtprfmgr @PolicyRegion:pip-region \“Server Monitors”

3. Use the wcrtprf command to create a profile. For example, to create a profile called Availability in the “Server Monitors” profile manager, enter the following command:

wcrtprf @ProfileManager:“Server Monitors” \SentryProfile Availability

4. Use the wcrtsntcoll command to add an indicator collection for the policy region. For example, to create a TME 10 Distributed Monitoring indicator collection called “sybase indicator” in the pip_region policy region, enter the following command:

wcrtsntcoll pip-region “sybase indicator”


5–46 Version 1.1

5. Use the wsetcoll command to set the indicator collection affiliation for a monitoring profile. For example, to set the Availability profile to the “sybase indicator” collection, enter the following command:

wsetcoll “sybase indicator” Availability

6. Use the wsub command to add subscribers to the profile manager. The following two examples show how to use the wsub command:

• To add the Sybase Adaptive Server pip_1150DS as a subscriber to the profile manager “Server Monitors” , enter the following command:

wsub @ProfileManager:”Server Monitors” \@SybaseDataServer:pip_1150DS@pip

• To add the database master of pip_1150DS as a subscriber to the profile “Database Monitors” , enter the following command:

wsub @ProfileManager:”Database Monitors” \@SybaseDatabase:master@pip_1150DS

For more information on the wsub command, see “Adding Subscribers to a Profile Manager from the Command Line” on page 6-84, or refer to the TME 10 Framework Reference Manual.

7. Use the waddmon command to create monitors. For specific examples of how to use the waddmon command for Tivoli Manager for Sybase monitors, refer to the sections called “CLI Syntax” and “CLI Examples” in both Chapter 2, “The SybaseServer Monitoring Collection,” and Chapter 3, “The SybaseDatabase Monitoring Collection,” in the Tivoli Manager for Sybase Reference Guide.



Settin

g U

p M

on

itorin

g

Pro

files

To specify that a monitor should send an event to the TEC, the waddmon command would be similar to the following:

waddmon "SybaseServer" "DeviceMirrorStatus" \-a "default" -t "15 minutes" -c critical -R "=~" \"HasNoMirrorDevice" -n "Sybase Sentry" -T fatal \@EventServer:EventServer#nemuchay-region \"Availability"

8. Use the wsetsntid command to set the default user and group ID for a profile. The following example sets user and group IDs for a distributed monitoring profile named Availability.

wsetsntid "root" "other" Availability

where:

“root” Specifies the user ID.

“other” Specifies the group ID.

Availability Specifies the distributed monitoring profile.


5–48 Version 1.1


Usin

g T

ivoli M

anag

er for

Syb

ase

5Using Tivoli Manager for Sybase

After you finish setting up the various components of Tivoli Manager for Sybase, you are ready to manage Sybase Adaptive Server objects. This chapter provides the procedures for using the software and covers the following topics:

■ Managing Sybase Adaptive Servers

■ Managing objects in Sybase Data Server collections

■ Subscribing endpoints to profile managers

■ Distributing a monitoring collection profile

■ Determining which monitors have been distributed to an endpoint

■ Determining which monitors are running on an endpoint

■ Viewing events in the Tivoli Enterprise Console (TEC)

6

Managing Sybase Adaptive Servers

6–2 Version 1.1

Managing Sybase Adaptive ServersThis section provides procedures for using the Tivoli Manager for Sybase software to manage Sybase Adaptive Servers. The following topics are covered:

■ Opening a Sybase Data Server collection

■ Changing Sybase Adaptive Server registration details

■ Viewing Sybase Adaptive Server properties

■ Viewing Sybase Adaptive Server error log contents

■ Starting a Sybase Adaptive Server

■ Shutting down a Sybase Adaptive Server

■ Checking the state of a Sybase Adaptive Server

Opening a Sybase Data Server CollectionTivoli represents the SybaseDataServer endpoint as an icon. Using the icon, you can open the Sybase Data Server collection to view the distributed monitoring profiles distributed to that endpoint, plus the databases, Sybase Backup Server, Sybase Monitor Servers and Sybase Engines associated with the server.

The following table provides the context and authorization roles required for this procedure:

You can perform this procedure from the Tivoli desktop only.


Opening the Sybase Data Server collection

SybaseDataServer sybase_user or sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase

Use the following steps to open a Sybase Data Server collection:

1. From the Tivoli desktop, double-click on the icon for the policy region containing the appropriate SybaseDataServer endpoint.

Note: Alternately, you can right-click on the policy region icon, then select the Open... option on the pop-up menu.


6–4 Version 1.1

This displays the Policy Region window.

2. From the Policy Region window, double-click on the SybaseDataServer icon. This displays the Sybase Data Server collection window.

Note: Alternate means of displaying the Sybase Data Server collection window include the following:

• Right-click on the appropriate SybaseDataServer icon, then select the Open... option on the pop-up menu.

• On the Tivoli desktop, select Desktop –> Navigator... to open the Navigator dialog. Select the ManagedNode object type check box. From the subsequent list of known resources, double-click on the name of the collection you want to open or select the collection name, then click the Go To button.



Usin

g T

ivoli M

anag

er for

Syb

ase

The Sybase Data Server collection window displays the following information:

■ The server identifier is displayed in the window title, typically in the dataserver_name@host_name format. The server identifier in the sample window is pip_1150DS@pip.

■ The server’s databases and the profiles it has received are displayed in this window.

• The database identifier is database_name@dataserver_name. In this example, there are several database identifiers. One is named master@pip_1150DS.

• The Tivoli distributed monitoring profile identifier is profile_name@dataserver_name@host_name. In this example, Availability@pip_1150DS@pip is the profile identifier.


6–6 Version 1.1

Changing Sybase Adaptive Server Registration DetailsYou can use the Registration... option to change the registration details for a Sybase Adaptive Server when the current details are no longer valid. This option only affects the registration details held in the Tivoli environment. (See “Registering Sybase Servers” on page 4-10.) It does not directly affect the Sybase Adaptive Server.

The following table provides the context and authorization role required for registering servers and discovering databases:


Use the following steps to change the registration of the Sybase Adaptive Server:

1. From the Tivoli desktop, double-click on the policy region that contains the appropriate SybaseDataServer endpoint. This displays the Policy Region window.

2. Right-click on the SybaseDataServer icon, then select the Registration... option on the pop-up menu.


Change the registration details of a server

SybaseDataServer sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase


6–8 Version 1.1

Tivoli Manager for Sybase displays the Change Data Server Registration Details dialog.

3. In the Change Data Server Registration Details dialog, change any of the details as appropriate. For more information on entering registration details, see “Registering Sybase Servers” on page 4-10.

4. Click the Change And Close button to save your changes and dismiss the dialog.



Usin

g T

ivoli M

anag

er for

Syb

ase

Viewing Sybase Adaptive Server PropertiesTivoli Manager for Sybase allows you to view a Sybase Adaptive Server’s properties.



Use the following steps to view a Sybase Adaptive Server’s properties:

1. From the Tivoli desktop, double-click on the icon for the policy region containing the appropriate SybaseDataServer endpoint. This displays the Policy Region window.

2. Right-click on the SybaseDataServer icon, then select the Properties... option on the pop-up menu.


View server properties SybaseDataServer sybase_user or sybase_dba


6–10 Version 1.1



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli displays a Sybase Data Server Properties window, listing information about the server, including registration details, current state information, and other endpoint-specific details.

Note: You can view the same information after opening the Sybase Data Server collection window by selecting the Sybase Data Server –> Properties... option.


6–12 Version 1.1

Viewing Sybase Adaptive Server Error Log ContentsTivoli Manager for Sybase allows you to view a Sybase Adaptive Server’s error log contents.



Use the following steps to view the contents of a Sybase Adaptive Server’s error log:


2. Right-click on the SybaseDataServer icon, then select the View Log... option on the pop-up menu.


View server error log contents




Usin

g T

ivoli M

anag

er for

Syb

ase


6–14 Version 1.1

Tivoli Manager for Sybase opens the Sybase Data Server Error Log window, showing the last 75 lines of the log file for the selected server.

Note: You can view the same information after opening the Sybase Data Server collection window by selecting the Sybase Data Server –> View Log... option.



Usin

g T

ivoli M

anag

er for

Syb

ase

Starting a Sybase Adaptive ServerThe Start Server option will start a Sybase Adaptive Server and its databases. You can start the server in single-user or multi-user modes. (For information about single-user and multi-user modes, refer to the “startserver” section in the Sybase Utility Programs for your platform manual.)

The following table provides the context and authorization role required for this procedure:.


The steps to start a Sybase Adaptive Server depend upon the state of the server at the time. (See “Checking the State of a Sybase Adaptive Server” on page 6-20.)

If the Sybase Adaptive Server is in a SHUTDOWN state, use the following steps to start the server:

1. From the Tivoli desktop, double-click on the policy region that contains the SybaseDataServer endpoint. This displays the Policy Region window.

2. Right-click on the SybaseDataServer icon, then select the Start Server –> Multi-User mode or the Start Server –> Single-User mode option on the pop-up menu.


Start the server SybaseDataServer sybase_dba


6–16 Version 1.1

If the Sybase Adaptive Server is in a SUSPECT state, use the previous steps to start the server. However, before the server starts, an acknowledgement dialog is displayed.

Click the Yes button to start the server or the No button to cancel the attempt.



Usin

g T

ivoli M

anag

er for

Syb

ase

Upon successful startup, Tivoli displays the server icon in the NORMAL state, as shown in the following example. (See “General States for a Sybase Adaptive Server” on page 6-20.)

Shutting Down a Sybase Adaptive ServerThe Shutdown Server option enables you to shut down a Sybase Adaptive Server. You can shut down the server with wait or nowait states. For more information about shutting down a Sybase Adaptive Server, refer to the Sybase Adaptive Server Enterprise System Administration Guide.

The following table provides the context and authorization role required for this procedure.



Shut down the server SybaseDataServer sybase_dba


6–18 Version 1.1

Use the following steps to shut down a Sybase Adaptive Server:


2. Right-click on the SybaseDataServer icon, then select either the Shutdown Server –> With ‘nowait’ or Shutdown Server –> With ‘wait’ option.

This displays one of the following acknowledgement dialogs.

3. Click the Yes button to shut down the server or the No button to cancel the attempt.



Usin

g T

ivoli M

anag

er for

Syb

ase

Upon successful shutdown, Tivoli displays the server icon in the SHUTDOWN state. (See “General States for a Sybase Adaptive Server” on page 6-20).


6–20 Version 1.1

Checking the State of a Sybase Adaptive ServerTivoli Manager for Sybase provides two levels of information about the current state of a Sybase Adaptive Server. Details about the general and detailed states are described in the following subsections.

General States for a Sybase Adaptive Server

The general state of a Sybase Adaptive Server is based on an availability check that tests Tivoli’s ability to connect to the server. Therefore, it does not ensure the connection and availability to all users via all configured access paths.

The general state of a Sybase Adaptive Server is reflected in one of the following three icon states:

■ NORMAL means the Sybase Adaptive Server is running normally. (The icon has no sign beside it.)

■ SUSPECT means Tivoli Manager for Sybase cannot connect to the Sybase Adaptive Server, but is not in a Shutdown or No More Connections state. (The icon has a question mark beside it.)

■ SHUTDOWN means the Sybase Adaptive Server is inaccessible because it has been shut down using one of the methods listed for the Shutdown detailed state in the next subsection. (The icon has a no-entry sign beside it.)

The following illustrations show icons for the Sybase Adaptive Server in its three general states: NORMAL, SUSPECT, and SHUTDOWN.



Usin

g T

ivoli M

anag

er for

Syb

ase

Detailed States for a Sybase Adaptive Server

The detailed state is the internal condition of a Sybase object reported with greater detail. Tivoli Manager for Sybase displays the detailed state of a Sybase object in two ways:

■ The properties dialog for an endpoint or object displays its detailed state beside the Status heading. (See “Viewing Sybase Adaptive Server Properties” on page 6-9.)

■ Placing the mouse cursor on an endpoint or object icon displays its name and detailed state in the status bar at the bottom of the window.

The detailed state depends on the type of Tivoli object. A Tivoli object can only be in one detailed state at any one time. For a Sybase Adaptive Server, there are four detailed states. There is no heirarchy. The following paragraphs describe each detailed state and how it relates to the current general state:

■ Available means Tivoli Manager for Sybase can connect to the Sybase Adaptive Server. (The icon has no sign beside it.)

■ Suspect means Tivoli Manager for Sybase cannot connect to the Sybase Adaptive Server, but is not in a Shutdown or No More Connections state. This could occur because the Sybase Adaptive Server crashed, for example, or because the information being used by Tivoli to log on to the server is incorrect. (The icon has a question mark beside it.)

■ No More Connections means Tivoli Manager for Sybase cannot connect to the Sybase Adaptive Server because there are no more connections available, but the server is not in a Shutdown state. (The icon has a question mark beside it.)


6–22 Version 1.1

■ Shutdown (the icon has a no-entry sign beside it) means the Sybase Adaptive Server has been shut down by one of the following:

• The Sybase services manager (if Sybase Adaptive Server runs on NT)

• A user-issued shutdown TSQL statement

• The control panel (if Sybase Adaptive Server runs on NT)

• A third-party utility

Updating the State of a Sybase Adaptive Server

If a Tivoli object’s state changes, it will not be apparent until one of the following happens:

■ An administrator runs the Check State option. (See “Running the Check State Option” on page 6-22.)

—OR—

■ The SQL Server Status monitor checks the server. (For more information, refer to the Tivoli Manager for Sybase Reference Guide.)

—OR—

■ An administrator selects the View –> Refresh option, which checks the status of every object in the collection, removes deleted objects, and adds any new objects.

Running the Check State Option

The following table provides the context and authorization roles required for running the Check State option for a Sybase Adaptive Server:



Check the state of a server




Usin

g T

ivoli M

anag

er for

Syb

ase

Use the following steps to check the state of a Sybase Adaptive Server:


2. Right-click on the icon for the server to display the pop-up menu, then select the Check State option.

Tivoli Manager for Sybase refreshes the SybaseDataServer icon to indicate its current general state and updates the detailed state.

Managing Objects in Sybase Data Server Collections

6–24 Version 1.1


This section describes how to use the Tivoli Manager for Sybase software to manage objects in a Sybase Data Server collection. The following topics are covered:

■ Managing a SybaseDatabase endpoint

■ Managing a SybaseEngine object

■ Managing a SybaseBackupServer endpoint

■ Managing a SybaseMonitorServer endpoint

■ Deleting objects from a Sybase Data Server collection

Managing a SybaseDatabase EndpointThis section provides procedures for using the Tivoli Manager for Sybase software to manage a SybaseDatabase endpoint, including the following topics:

■ Opening a Sybase Adaptive Server database collection

■ Viewing SybaseDatabase endpoint properties

■ Checking the state of a SybaseDatabase endpoint

Opening a Sybase Database Collection

When you register a Sybase Adaptive Server, Tivoli automatically registers any databases associated with that server.

Tivoli displays a SybaseDatabase endpoint as an icon in the Sybase Data Server collection window. You can use the icon to open a collection window to view the profiles distributed to that database.



Open a database collection

SybaseDatabase sybase_user or sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase


Use the following steps to open a database collection:



Double-click on the SybaseDataServer icon.

—OR—

Right-click on the server icon, then select the Open... option on the pop-up menu.

This displays the Sybase Data Server collection window.


Double-click on the appropriate SybaseDatabase icon.

—OR—

Right-click on the database icon, then select the Open... option on the pop-up menu.


6–26 Version 1.1



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli displays the Sybase Database collection window.

The window title is typically displayed as database_name@dataserver_name, which in this example is master@pip_1150DS. The database window displays icons for the profiles it has received through distribution. In this example, the profile icon is database monitors@model@pip_1150DS.

Viewing SybaseDatabase Endpoint Properties

Tivoli Manager for Sybase allows you to view the properties of a SybaseDatabase endpoint.




View database properties



6–28 Version 1.1

Use the following steps to view the properties of a SybaseDatabase endpoint:




—OR—



3. Right-click on the SybaseDatabase icon and select the Properties... option on the pop-up menu.



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli opens a Sybase Database Properties window that lists the name of the database and its current state.

Note: You can view the same information from the Sybase Database collection window by selecting the Sybase Database –> Properties... option.

Checking the State of a SybaseDatabase Endpoint

Tivoli Manager for Sybase provides two levels of information about the current state of a Sybase Adaptive Server. Details about the general and detailed states are described in the following subsections.

General States for a SybaseDatabase Endpoint

The general state of a SybaseDatabase endpoint is reflected in one of three icon states:

■ NORMAL means the database is up and running. (The icon has no sign beside it.)

■ SUSPECT means the database is in an Offline , Read Only, Single User, or DBO Use Only (database owner use only) state. (The icon has a question mark beside it.) For more information, see “Detailed States for a SybaseDatabase Endpoint” on page 6-30.

■ SHUTDOWN means either the database is in an Offline state, or its Sybase Adaptive Server is unavailable. (The icon has a no-entry sign beside it.)


6–30 Version 1.1

The following illustrations show example icons for the SybaseDatabase endpoint, model@pip_1150DS, in its three general states: NORMAL, SUSPECT, and SHUTDOWN.

Detailed States for a SybaseDatabase Endpoint

Tivoli Manager for Sybase displays the detailed state of a Sybase object in two ways:

■ The properties dialog for an endpoint or object displays its detailed state beside the Status heading. (See “Viewing SybaseDatabase Endpoint Properties” on page 6-27.)

■ Placing the mouse cursor on an endpoint or object icon displays its name and detailed state in the status bar at the bottom of the window.

The detailed states depend on the type of Tivoli object. A Tivoli object can only be in one detailed state at any one time. For a SybaseDatabase endpoint, there are seven detailed states:

■ Data Server Unavailable means the Sybase Adaptive Server holding the database is in a Shutdown or Suspect state. (The icon has a no-entry sign beside it.)

■ Suspect means the database is marked as suspect in the sysdatabases system table. (The icon has a question mark beside it.)

■ Offline means the database is marked as offline in the sysdatabases system table. (The icon has a no-entry sign beside it.)

■ Read Only means the read only option has been set for the database. (The icon has a question mark beside it.)

■ Single User means the single user option has been set for the database. (The icon has a question mark beside it.)



Usin

g T

ivoli M

anag

er for

Syb

ase

■ DBO Use Only means the DBO use only (database owner use only) option has been set for the database. (The icon has a question mark beside it.)

■ Online means the database is running normally. (The icon has no sign beside it.)

Note: Only one detailed state is reported for each database. If multiple detailed states apply to a database, only the highest priority state is displayed. (The priority ranking is the same as the order of the detailed states listed above, with Data Server Unavailable as the highest and Online as the lowest priority.) For example, if a database is in both a Read Only and a Single User state, the monitor will report the Read Only state.

Updating the State of a SybaseDatabase Endpoint


■ An administrator runs the Check State option. (See “Running the Check State Option” on page 6-32.)

—OR—

■ The Database State monitor checks the database. (For more information, refer to the Tivoli Manager for Sybase Reference Guide.)

—OR—



6–32 Version 1.1


The following table provides the context and authorization roles required for running the Check State option for a Sybase Adaptive Server database:


Use the following steps to check the state of a SybaseDatabase endpoint:




—OR—

Right-click on the server icon and select the Open... option on the pop-up menu.


3. Right-click on the SybaseDatabase icon, then select the Check State option on the pop-up menu.


Check the state of a database




Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli Manager for Sybase refreshes the SybaseDatabase icon to indicate its current general state and updates the detailed state.


6–34 Version 1.1

Managing a SybaseEngine InstanceThis section provides procedures for using the Tivoli Manager for Sybase software to manage a SybaseEngine instance. The following topics are covered:

■ Viewing SybaseEngine instance properties

■ Checking the state of a SybaseEngine instance

Viewing SybaseEngine Instance Properties

Tivoli Manager for Sybase allows you to view the properties of a SybaseEngine instanceinstance.



Use the following steps to view the properties of a SybaseEngine instance:




—OR—

Right-click on the server icon and select the Open... option on the pop-up menu.


3. Right-click on the appropriate SybaseEngine icon, then select the Properties... option on the pop-up menu.


View engine properties

SybaseEngine sybase_user or sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli opens a Sybase Engine Properties window that lists the engine number and current state of the engine.


6–36 Version 1.1

Checking the State of a SybaseEngine Instance

Tivoli Manager for Sybase provides two levels of information about the current state of a SybaseEngine instance. Details about the general and detailed states are described in the following subsections.

General States for a SybaseEngine Instance

The general state of a SybaseEngine instance is reflected in one of the three following icon states:

■ NORMAL means the engine is up and running. (The icon has no sign beside it.)

■ SUSPECT means the engine is not running normally and is marked in the sysengines system table as Debug, In Destroy, or In Create. (The icon has a question mark beside it.) For more information, see the subsection “Detailed States for a SybaseEngine Instance,” which follows.

■ SHUTDOWN means the engine is offline, or its server is unavailable. (The icon has a no-entry sign beside it.)

The following illustrations show examples of a SybaseEngine icon, 0@pip_1150DS@pip, in its three general states: NORMAL, SUSPECT, and SHUTDOWN.



Usin

g T

ivoli M

anag

er for

Syb

ase

Detailed States for a SybaseEngine Instance


■ The properties dialog for an endpoint or instance displays its detailed state beside the Status heading. (See “Viewing SybaseEngine Instance Properties” on page 6-34.)

■ Placing the mouse pointer on an endpoint or instance icon displays its name and detailed state in the status bar at the bottom of the window.

The detailed states depend on the type of Tivoli object. A Tivoli object can only be in one detailed state at any one time. For a SybaseEngine instance, there are six detailed states:

■ Online means the engine is marked as Online in the sysengines system table. (The icon has no sign beside it.)

■ In Destroy means the engine is marked as In Destroy in the sysengines system table. (The icon has a question mark beside it.)

■ In Create means the engine is marked as In Create in the sysengines system table. (The icon has a question mark beside it.)

■ Debug means the engine is marked as Debug in the sysengines system table. (The icon has a question mark beside it.)

■ Offline means the engine is marked as Offline in the sysengines system table. (The icon has a no-entry sign beside it.)

■ Data Server Unavailable means the Sybase Adaptive Server with the engine is in a Shutdown or Suspect state. (The icon has a no-entry sign beside it.)


6–38 Version 1.1

Updating the State of a SybaseEngine Instance


■ An administrator runs the Check State option. (See the subsection “Running the Check State Option,” which follows.)

—OR—

■ An administrator selects the View –> Refresh menu option, which checks the status of every object in the collection, removes deleted objects, and adds any new objects.


The following table provides the context and authorization roles required for running the Check State option for a SybaseEngine instance:


Use the following steps to check the state of a SybaseEngine instance:




—OR—




Check the state of an engine

SybaseEngine sybase_user or sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase

3. Right-click on the appropriate SybaseEngine icon, then select the Check State option on the pop-up menu.

Tivoli Manager for Sybase refreshes the SybaseEngine icon to indicate its current general state and updates the detailed state.


6–40 Version 1.1

Managing a SybaseBackupServer EndpointThis section provides procedures for using the Tivoli Manager for Sybase software to manage Sybase Backup Servers, including the following topics:

■ Opening a Sybase Backup Server collection

■ Changing Sybase Backup Server registration details

■ Viewing Sybase Backup Server properties

■ Viewing Sybase Backup Server error log contents

■ Starting a Sybase Backup Server

■ Shutting down a Sybase Backup Server

■ Checking the state of a Sybase Backup Server

Opening a Sybase Backup Server Collection

When you register the Sybase Adaptive Server and Sybase Backup Server, a SybaseBackupServer icon appears in the Sybase Data Server collection window.

Using the icon, you can open the Sybase Backup Server collection to view the distributed monitoring profiles distributed to the SybaseBackupServer endpoint.




Open the Sybase Backup Server collection

SybaseBackupServer sybase_user or sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase

Use the following steps to open a Sybase Backup Server collection:




—OR—




6–42 Version 1.1


Double-click on the SybaseBackupServer icon.

—OR—

Right-click on the SybaseBackupServer icon, then select the Open... option on the pop-up menu.

Tivoli displays the Sybase Backup Server collection window.

The window title is typically displayed as backupserver_name@dataserver_name@host_name, which in this example is pip_1150BS@pip_1150DS@pip. The Sybase Backup Server collection window displays icons for the profiles it has received through distribution. In this example, the profile icon is Availability@pip_1150BS@pip_1150DS@pip.

Changing Sybase Backup Server Registration Details

You can use the Registration... option to change the registration details for a Sybase Backup Server when the current details are no longer valid. This option only affects the registration details held in the Tivoli environment. It does not directly affect the Sybase Backup Server.



Usin

g T

ivoli M

anag

er for

Syb

ase

The following table provides the context and authorization role required for registering the Sybase Backup Server:


Use the following steps to change the registration of the Sybase Backup Server:




—OR—




Change the registration details of the backup server

SybaseBackupServer sybase_dba


6–44 Version 1.1

3. Right-click on the SybaseBackupServer icon, then select the Registration... option on the pop-up menu.

Tivoli Manager for Sybase displays the Change Backup Server Registration Details dialog.



Usin

g T

ivoli M

anag

er for

Syb

ase

4. In the Change Backup Server Registration Details dialog, change any of the details as appropriate. For more information on entering registration details, see “Registering a Sybase Adaptive Server and Sybase Backup Server” on page 4-10.


Viewing Sybase Backup Server Properties

Tivoli Manager for Sybase allows you to view a Sybase Backup Server’s properties.



Use the following steps to view a Sybase Backup Server’s properties:




—OR—




View backup server properties



6–46 Version 1.1

3. Right-click on the SybaseBackupServer icon, then select the Properties... option on the pop-up menu.



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli opens the Sybase Backup Server Properties window, listing information about the backup server, including registration details, current state information, and other endpoint-specific details.

Note: You can view the same information after opening the Sybase Backup Server collection window by selecting the Sybase Backup Server –> Properties... option.

Viewing Sybase Backup Server Error Log Contents

Tivoli Manager for Sybase allows you to view a Sybase Backup Server’s error log contents.

The following table provides the context and authorization roles required for this procedures:



View backup server error log contents



6–48 Version 1.1

Use the following steps to view the contents of a Sybase Backup Server’s error log:




—OR—



3. Right-click on the SybaseBackupServer icon, then select the View Log... option on the pop-up menu.



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli Manager for Sybase opens the Sybase Backup Server Error Log window, showing the last 75 lines of the error log file for the backup server.

Note: You can view the same information after opening the Sybase Backup Server collection window by selecting the Sybase Backup Server –> View Log... option.

Starting a Sybase Backup Server

The Start Server option will start a Sybase Backup Server.



The steps to start a Sybase Backup Server depend upon the state of the backup server at the time. (See “Checking the State of a Sybase Backup Server” on page 6-55.)

If the Sybase Backup Server is in a SHUTDOWN state, use the following steps to start the backup server:


Start the backup server



6–50 Version 1.1

1. From the Tivoli desktop, double-click on the icon for the policy region that contains the appropriate SybaseDataServer endpoint. This displays the Policy Region window.



—OR—



3. Right-click on the SybaseBackupServer icon, then select the Start Server option on the pop-up menu.



Usin

g T

ivoli M

anag

er for

Syb

ase

If the Sybase Backup Server is in a SUSPECT state, use the previous steps to start the server. However, before the server starts, an acknowledgement dialog is displayed.


Upon successful startup, Tivoli displays the Sybase Backup Server icon in the NORMAL state, as shown in the following example.


6–52 Version 1.1

Shutting Down a Sybase Backup Server

The Shutdown Server option allows you to shut down a Sybase Backup Server. You can shut down the backup server with wait or nowait states. For more information about shutting down a Sybase Backup Server, refer to the Sybase Adaptive Server Enterprise System Administration Guide.

The following table provides the context and authorization role required for this procedure.


Use the following steps to shut down a Sybase Backup Server:




—OR—



3. Right-click on the SybaseBackupServer icon, then select either the Shutdown Server –> With ‘nowait’ or the Shutdown Server –> With ‘wait’ option on the pop-up menu.


Shut down the backup server




Usin

g T

ivoli M

anag

er for

Syb

ase

This displays an acknowledgement dialog.

4. Click the Yes button to shut down the Sybase Backup Server or the No button to cancel the attempt.


6–54 Version 1.1

Upon successful shutdown, Tivoli displays the Sybase Backup Server icon in the SHUTDOWN state. (See the section “Checking the State of a Sybase Backup Server,” which follows.)



Usin

g T

ivoli M

anag

er for

Syb

ase

Checking the State of a Sybase Backup Server

Tivoli Manager for Sybase provides two levels of information about the current state of a SybaseBackupServer endpoint. Details about the general and detailed states are described in the following subsections.

General States for a Sybase Backup Server

The general state of a Sybase Backup Server is based on an availability check that tests Tivoli’s ability to connect to the backup server. Therefore, it does not ensure the connection and availability to all users over all configured access paths.

The general state of a Sybase Backup Server is reflected in one of three icon states:

■ NORMAL means the Sybase Backup Server is running normally. (The icon has no sign beside it.)

■ SUSPECT means Tivoli Manager for Sybase cannot connect to the Sybase Backup Server, but it is not in a Shutdown state. (The icon has a question mark beside it.)

■ SHUTDOWN means the Sybase Backup Server is inaccessible because it has been shut down using one of the methods listed for the Shutdown detailed state in the next subsection. (The icon has a no-entry sign beside it.)

The following illustrations show icons for a Sybase Backup Server icon in its three general states: NORMAL, SUSPECT, and SHUTDOWN.


6–56 Version 1.1

Detailed States for a Sybase Backup Server



■ Placing the mouse pointer on an endpoint or object icon displays its name and detailed state in the status bar at the bottom of the window.

The detailed states depend on the type of Tivoli object. A Tivoli object can only be in one detailed state at any one time. For a Sybase Backup Server, there are three detailed states. The following paragraphs describe each detailed state and how it relates to the current general state:

■ Available means Tivoli Manager for Sybase can connect to the Sybase Backup Server. (The icon has no sign beside it.)

■ Suspect means Tivoli Manager for Sybase cannot connect to the Sybase Backup Server, but it is not in a Shutdown state. This could occur because the Sybase Backup Server crashed, for example, or because the logon information is incorrect. (The icon has a question mark beside it.)

■ Shutdown (the icon has a no-entry sign beside it) means the Sybase Backup Server has been shutdown by one of the following:

• The Sybase services manager (if Sybase Backup Server runs on NT)

• A user-issued shutdown TSQL statement

• The control panel (if Sybase Backup Server runs on NT)




Usin

g T

ivoli M

anag

er for

Syb

ase

Updating the State of a Sybase Backup Server


■ An administrator runs the Check State option. (See the subsection “Running the Check State Option,” which follows.)

—OR—


—OR—

■ An administrator selects the View –> Refresh menu option, which checks the status of every object in the collection, removes deleted objects, and adds any new objects.


The following table provides the context and authorization roles required for running the Check State option for a Sybase Backup Server:


Use the following steps to check the state of a Sybase Backup Server:




—OR—


Check the state of a backup server



6–58 Version 1.1



3. Right-click on the SybaseBackupServer icon, then select the Check State option on the pop-up menu.

Tivoli Manager for Sybase refreshes the Sybase Backup Server icon to indicate its current general state and updates the detailed state.



Usin

g T

ivoli M

anag

er for

Syb

ase

Managing a SybaseMonitorServer EndpointThis section provides procedures for using the Tivoli Manager for Sybase software to manage Sybase Monitor Servers includes the following topics:

■ Opening a Sybase Monitor Server collection

■ Changing Sybase Monitor Server registration details

■ Viewing Sybase Monitor Server properties

■ Viewing Sybase Monitor Server error log contents

■ Starting a Sybase Monitor Server

■ Shutting down a Sybase Monitor Server

■ Checking the state of a Sybase Monitor Server

Opening a Sybase Monitor Server Collection

When you register a Sybase Monitor Server, a SybaseMonitorServer icon appears in the Sybase Data Server collection window.

Using the icon, you can open the Sybase Monitor Server collection to view the distributed monitoring profiles distributed to the SybaseMonitorServer endpoint.




Open the Sybase Monitor Server collection

SybaseMonitorServer sybase_user or sybase_dba


6–60 Version 1.1

Use the following steps to open a Sybase Monitor Server collection:




—OR—





Usin

g T

ivoli M

anag

er for

Syb

ase


Double-click on the SybaseMonitorServer icon.

—OR—

Right-click on the database icon, then select the Open... option on the pop-up menu.

Tivoli displays the Sybase Monitor Server collection window.

The window title is typically displayed as monitorserver_name@dataserver_name@host_name, which in this example is pip_1150MS@pip_1150DS@pip. The Sybase Monitor Server collection window displays icons for the profiles it has received through distribution. In this example, the profile icon is Availability@pip_1150MS@pip_1150DS@pip.

Changing Sybase Monitor Server Registration Details

You can use the Registration... option to change the registration details for a Sybase Monitor Server when the current details are no longer valid. This option only affects the registration details held in the Tivoli environment. It does not directly affect the Sybase Monitor Server.


6–62 Version 1.1

The following table provides the context and authorization role required for changing the registration details of a Sybase Monitor Server:


Use the following steps to change the registration of the Sybase Monitor Server:




—OR—



3. Right-click on the appropriate SybaseMonitorServer icon, then select the Registration... option on the pop-up menu.


Change the registration details of the monitor server

SybaseMonitorServer sybase_dba



Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli Manager for Sybase displays the Change Monitor Server Registration Details dialog.


6–64 Version 1.1

4. In the Change Monitor Server Registration Details dialog, change any of the details as appropriate. For more information on entering registration details, see “Registering a Sybase Monitor Server” on page 4-19.


Viewing Sybase Monitor Server Properties

Tivoli Manager for Sybase allows you to view a Sybase Monitor Server’s properties.



Use the following steps to view a Sybase Monitor Server’s properties:




—OR—



3. Right-click on the appropriate SybaseMonitorServer icon, then select the Properties... option on the pop-up menu.


View monitor server properties




Usin

g T

ivoli M

anag

er for

Syb

ase

Tivoli opens the Sybase Monitor Server Properties window, listing registration details, current state information, and other endpoint-specific details about the monitor server.


6–66 Version 1.1

Note: You can view the same information from the Sybase Monitor Server collection window by selecting the Sybase Monitor Server –> Properties... menu option.

Viewing Sybase Monitor Server Error Log Contents

Tivoli Manager for Sybase allows you to view the contents of a Sybase Monitor Server’s error log.



Use the following steps to view the contents of a Sybase Monitor Server’s error log:




—OR—



3. Right-click on the appropriate SybaseMonitorServer icon, then select the View Log... option on the pop-up menu.


View contents of the Sybase Monitor Server error log




Usin

g T

ivoli M

anag

er for

Syb

ase


6–68 Version 1.1

Tivoli Manager for Sybase opens the Sybase Monitor Server Error Log window, showing the last 75 lines of the error log file for the monitor server.

Note: You can view the same information from the Sybase Monitor Server collection window by selecting the Sybase Monitor Server –> View Log... option.

Starting a Sybase Monitor Server

The Start Server option will start a Sybase Monitor Server.




Start the Sybase Monitor Server




Usin

g T

ivoli M

anag

er for

Syb

ase

The steps to follow to start a Sybase Monitor Server depend upon the state of the monitor server at the time. (See “Checking the State of a Sybase Monitor Server” on page 6-75.)

If the Sybase Monitor Server is in a SHUTDOWN state, use the following four steps to start the backup server:




—OR—



3. Right-click on the appropriate SybaseMonitorServer icon, then select the Start Server option on the pop-up menu.


6–70 Version 1.1

If the Sybase Monitor Server is in a SUSPECT state, use the previous steps to start the server. However, before the server starts, an acknowledgement dialog is displayed.




Usin

g T

ivoli M

anag

er for

Syb

ase

Upon successful startup, Tivoli displays the Sybase Monitor Server icon in the NORMAL state, as shown in the following example.

Shutting Down a Sybase Monitor Server

The Shutdown Server option allows you to shut down a Sybase Monitor Server. You can shut down the monitor server with wait or nowait states. For more information about shutting down a Sybase Monitor Server, refer to the Sybase Adaptive Server Enterprise Monitor Server User’s Guide.



Shut down the Sybase Monitor Server



6–72 Version 1.1


Use the following steps to shut down a Sybase Monitor Server:




—OR—



3. Right-click on the appropriate SybaseMonitorServer icon, then select either the Shutdown Server –> With ‘nowait’ or the Shutdown Server –> With ‘wait’ option on the pop-up menu.



Usin

g T

ivoli M

anag

er for

Syb

ase

This displays an acknowledgement dialog.

4. Click the Yes button to shut down the Sybase Monitor Server or the No button to cancel the attempt.


6–74 Version 1.1

Upon successful shutdown, Tivoli displays the Sybase Monitor Server icon in the SHUTDOWN state. (See “Checking the State of a Sybase Monitor Server” on page 6-75.)



Usin

g T

ivoli M

anag

er for

Syb

ase

Checking the State of a Sybase Monitor Server

Tivoli Manager for Sybase provides two levels of information about the current state of a Sybase Adaptive Server. Details about the general and detailed states are described in the following subsections.

General States for a Sybase Monitor Server

There are three general states:

■ NORMAL means the Sybase Monitor Server is running normally. (The icon has no sign beside it.)

■ SUSPECT means Tivoli Manager for Sybase cannot connect to the Sybase Monitor Server, but it is not in a Shutdown state. (The icon has a question mark beside it.)

■ SHUTDOWN means the Sybase Monitor Server is inaccessible because it has been shut down using one of the methods listed for the Shutdown detailed state in the next subsection. (The icon has a no-entry sign beside it.)

Note: The general state of a Sybase Monitor Server is based on an availability check that tests Tivoli’s ability to connect to the monitor server. Therefore, it does not ensure the connection and availability to all users over all configured access paths.

The following illustrations show the icons for a Sybase Monitor Server in its three general states: NORMAL, SUSPECT, and SHUTDOWN.


6–76 Version 1.1

Detailed States for a Sybase Monitor Server



■ Placing the mouse pointer on an endpoint or object icon displays its name and detailed state in the status bar at the bottom of the window.

The detailed states depend on the type of Tivoli object. A Tivoli object can only be in one detailed state at any one time. For a Sybase Monitor Server, there are three detailed states. The following paragraphs describe each detailed state and how it relates to the current general state:

■ Available means Tivoli Manager for Sybase can connect to the Sybase Monitor Server. (The icon has no sign beside it.)

■ Suspect means Tivoli Manager for Sybase cannot connect to the Sybase Monitor Server, but it is not in a Shutdown state. This could occur because the Sybase Monitor Server crashed, for example, or because the logon information is incorrect. (The icon has a question mark beside it.)

■ Shutdown (the icon has a no-entry sign beside it) means the Sybase Monitor Server has been shutdown by one of the following:

• The Sybase services manager (if Sybase Monitor Server runs on NT)

• A user-issued sms_shutdown TSQL statement

• The control panel (if Sybase Monitor Server runs on NT)




Usin

g T

ivoli M

anag

er for

Syb

ase

Updating the State of a Sybase Monitor Server


■ An administrator runs the Check State option. (See the subsection “Running the Check State Option,” which follows).

—OR—


—OR—



The following table provides the context and authorization roles required for running the Check State option for a Sybase Monitor Server:


Use the following steps to check the state of a Sybase Monitor Server:




—OR—


Check the state of a monitor server



6–78 Version 1.1



3. Right-click on the appropriate SybaseMonitorServer icon, then select the Check State option on the pop-up menu.

Tivoli Manager for Sybase refreshes the SybaseMonitorServer icon to indicate its current general state and updates the detailed state.



Usin

g T

ivoli M

anag

er for

Syb

ase

Removing Objects from a Sybase Data Server Collection

There might be times when you want to remove an object from a Sybase Data Server collection.

Use the following steps to delete a SybaseDataServer or SybaseMonitorServer endpoint:

1. Click on the appropriate SybaseDataServer or SybaseMonitorServer icon to select it.

2. Select the Edit –> Delete menu option in the Policy Region window (if deleting a SybaseDataServer icon), or in the Sybase Data Server collection window (if deleting a Sybase Monitor Server).

A warning dialog is displayed.

3. Click the Yes button to delete the icon or the No button to cancel the attempt.

You cannot delete a SybaseBackupServer or SybaseDatabase endpoint, or SybaseEngine object. If you try to delete any of these objects, Tivoli will first display the warning dialog above. If you clickclick the Yes button, the following error message is displayed:

Subscribing Endpoints to Profile Managers

6–80 Version 1.1

Subscribing Endpoints to Profile ManagersSubscribing an endpoint to a profile manager determines which resources receive a profile when it is distributed. To add a subscriber to a monitoring profile, you must add the subscriber to the profile manager.

You must add subscribers to the profile manager before you can distribute a monitoring profile. Tivoli distributed monitoring uses the list of subscribers to determine the endpoints that can be and are being used to monitor resources.



Adding Subscribers to a Profile Manager from the Desktop

Use the following steps to add subscribers to the profile manager:

1. From the Tivoli desktop, double-click on the icon for the policy region that contains the profiles you want to distribute from the Tivoli desktop. This displays the Policy Region window.

2. From the Policy Region window, double-click on the appropriate profile manager icon to display the Profile Manager window.


Add one or more subscribers

Profile manager’s policy region and subscribers policy region or regions

admin (profile)and sybase_dba (server or database endpoint)



Usin

g T

ivoli M

anag

er for

Syb

ase

3. Select the Profile Manager –> Subscribers... option.

This displays the Subscribers dialog.


6–82 Version 1.1

4. Select the subscribers to which you want to distribute the profile that you created from the Available to become Subscribers scrolling list.

5. Click the left arrow button to move the selected subscribers to the Current Subscribers scrolling list.



Usin

g T

ivoli M

anag

er for

Syb

ase

6. Click the Set Subscriptions & Close button.

The new subscribers’ icons are displayed in the Profile Manager window.

Distributing a Monitoring Collection Profile

6–84 Version 1.1

Adding Subscribers to a Profile Manager from the Command Line

You can use the wsub command to add subscribers to the profile manager.

For example, to add subscribers pip_1150DS@pip and pip_1102DS@pip (both SybaseDataServer endpoints) to the profile manager “Server Monitors” , enter the following command:

wsub @ProfileManager:“Server Monitors” \@SybaseDataServer:pip_1150DS@pip \@SybaseDataServer:pip_1102DS@pip

For more details, refer to the TME 10 Framework Reference Manual.

Distributing a Monitoring Collection ProfileOnce your monitoring profile is set up and has subscribers, you can distribute it. For information about setting up profiles, see Chapter 5, “Setting Up Monitoring Profiles.”

The following table provides the context and authorization roles required for these tasks:

You can perform these procedures from either the Tivoli desktop or the command line.


Distribute a profile to the next level

Distributed Monitoring Profile

admin

Distribute a profile to all levels, or distribute from a server or database endpoint

Distributed Monitoring Profile and SybaseDataServer endpoint

admin (profile)and sybase_dba (server or database endpoint)



Usin

g T

ivoli M

anag

er for

Syb

ase

Distributing a Monitoring Profile from the DesktopUse the following steps to distribute the profile:

1. From the Tivoli desktop, double-click on the icon for the policy region that contains the profiles you want to distribute from the Tivoli desktop. This displays the Policy Region window.

2. From the Policy Region window, double-click on the appropriate profile manager icon to display the Profile Manager window.


6–86 Version 1.1

3. Double-click on the profile that you want to distribute to display the TME 10 Distributed Monitoring Profile Properties window.



Usin

g T

ivoli M

anag

er for

Syb

ase

4. Select the Profile −> Distribute option.


6–88 Version 1.1

This displays the Distribute Profile dialog.

5. Select one of the following radio buttons in the Distribute To area to specify which subscribers receive the profile.

Next Level of Subscribers Distributes the profile only to the subscribers listed in the Distribute To These Subscribers scrolling list.

This selection distributes the profile to only the subscribers of the profile manager. It does not distribute to lower-level subscribers. If a profile manager with subscribers resides at the next level, you might need to perform the distribution process from the profile manager at more than one level to reach all the profile endpoints.

—OR—



Usin

g T

ivoli M

anag

er for

Syb

ase

All Levels of Subscribers

Distributes to all levels of subscribers.

Use this option when either of the following conditions exist:

• One or more profile managers subscribe to the profile manager that contains the profile, and you want to distribute the profile to all subscribers in the distribution hierarchy.

• A Sybase Adaptive Server or databases are the only subscribers of the profile manager that contains the profile.

6. Select one of the following options in the Distribute Will area.

Preserve modifications in subscribers’ copy of the profileKeeps entries that appear in the subscriber’s profile, even though they do not appear in the profile being distributed.

—OR—

Make subscribers’ profile an EXACT COPY of this profile Overwrites the subscriber’s profile with a copy of the profile being distributed.

7. Do not use the Distribute to These Subscribers scrolling list for this procedure. (See “Subscribing Endpoints to Profile Managers” on page 6-80.)

8. Distribute the profile immediately or designate a time at which it will be distributed.

To distribute the profile immediately, click the Distribute & Close button to close the dialog after distributing the profile.

—OR—


6–90 Version 1.1

To specify a time to distribute the profile, follow these steps:

a. Click the Schedule... button to display the Add Scheduled Job dialog.

b. Use the Add Scheduled Job dialog to schedule the distribution and to tell Tivoli distributed monitoring to try to distribute the profile again if one or more attempts fail.



Usin

g T

ivoli M

anag

er for

Syb

ase

The following example shows this dialog set up to run the profile distribution job once, as follows:

- Job Label: Server Availability

- Schedule Job For: 2/4/99 at 6:00 p.m.

- When Job Completes: Post Tivoli Notice and Log to File /tmp/Sybase on host pip.


6–92 Version 1.1

For more detailed information about the Add Scheduled Job dialog, refer to the “TME Scheduler” chapter in the TME 10 FrameWork User’s Guide.

c. To schedule the job, click the Schedule Job & Close button. Tivoli displays the Distribute Profile dialog.

d. Click the Distribute & Close button on the Distribute Profile dialog to distribute the profile and return to the TME 10 Distributed Monitoring Profile Properties window.



Usin

g T

ivoli M

anag

er for

Syb

ase

9. Select the Profile −> Close option to close the TME 10 Distributed Monitoring Profile Properties window.

Distributing a Monitoring Profile from the Command Line

You can use the wdistrib command to distribute the profile from the command line.

For example, to distribute a profile named Availability to a SybaseDataServer endpoint with the label pip_1150DS@pip, enter the following command from the command line:

wdistrib -l over_all @SentryProfile:Availability \ @SybaseDataServer:pip_1150DS@pip

The example distributes the profile to the subscribing SybaseDataServer endpoint. This distribution overwrites all local changes.

For more information about using the wdistrib command, refer to the TME 10 Framework Reference Manual.

Determining Which Monitors Have Been Distributed to an Endpoint

6–94 Version 1.1

Determining Which Monitors Have Been Distributed to an Endpoint

From the Tivoli desktop, complete the following steps to quickly determine which monitors have been distributed to a specific endpoint:

1. Locate and double-click on the appropriate endpoint icon. The collection window for that endpoint is displayed.

2. In the endpoint’s collection window, look for an icon that represents a profile (named Availability@pip_1150DS@pip in this example).

Determining Which Monitors Are Running at an Endpoint


Usin

g T

ivoli M

anag

er for

Syb

ase

If you do not find such an icon, no monitors have been distributed to the endpoint.

–OR–

If you do find an icon for a profile, double-click on the icon. The TME 10 Distributed Monitoring Profile Properties window is displayed, which lists the monitors distributed to the endpoint.

Determining Which Monitors Are Running at an Endpoint

You cannot determine which monitors are running at an endpoint from the Tivoli desktop. However, from the command line, you can use the wlseng command to determine which monitors are running at an endpoint. For detailed information about the wlseng command, refer to the TME 10 Distributed Monitoring User’s Guide.

Viewing Events in the Tivoli Enterprise Console

6–96 Version 1.1

Viewing Events in the Tivoli Enterprise ConsoleOnce you have set up the TEC (as described in “Integrating with the Tivoli Enterprise Console” on page 4-26), you can receive events through it.


You can perform this procedure from either the Tivoli desktop or the command line. For more information about using the Tivoli desktop to display events, refer to the Tivoli Enterprise Console User’s Guide; or if you are using the command line, refer to the Tivoli Enterprise Console Reference Manual or the UNIX manual page for the wlsemsg command.

In the following example, the SybaseServer monitor called Sybase Server Status has been configured to send an event with a severity level of CRITICAL to the TEC when it detects that the Sybase Adaptive Server is unavailable. In the example, the Sybase Server Status monitor has detected this condition, and an event with a CRITICAL severity level has been sent to the TEC and displayed in the SybaseBaseEvent Event Group window.


View events in the TEC

Event Console user



Usin

g T

ivoli M

anag

er for

Syb

ase

Use the following steps to view an event from the TEC:

1. Double-click on the appropriate Event Group icon to display the SybaseBaseEvent Group Message List window.

This window displays the Sybase Adaptive Server state as CRITICAL.

2. To view the details of a message, do one of the following:

Double-click on the event in the SybaseBaseEvent Group Message List window.

—OR—

Select an event and click the View Message... button.


6–98 Version 1.1

TEC displays the Event Group Message Viewer window.

Use the scroll bar in the Event Group Message Viewer window to view the entire contents of the event message. For information on the fields, called slots, of an event message, refer to the Tivoli Enterprise Console User’s Guide.


Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

6Setting Up and Using Tivoli Manager for Sybase GEM Instrumentation

This chapter describes Tivoli Manager for Sybase Global Enterprise Manager (GEM) instrumentation. Instrumentation provides information about specific applications, systems software, or components to a management system, such as the Tivoli Global Enterprise Manager (Tivoli GEM). Tivoli Manager for Sybase GEM Instrumentation enables Tivoli GEM to graphically monitor and control Sybase resources residing on Tivoli managed nodes.

This chapter includes the following topics:

■ An overview of Tivoli GEM Instrumentation

■ Instructions for installing Tivoli Manager for Sybase GEM Instrumentation software

■ Procedures for setting up Tivoli Manager for Sybase GEM Instrumentation

■ Procedures for using Tivoli Manager for Sybase GEM Instrumentation tasks and monitors

See Appendix D, “Supporting Connections to Sybase Components,” for additional information, including details on how Tivoli GEM supports connections to external components.

7

Overview of Tivoli GEM Instrumentation

7–2 Version 1.1

Overview of Tivoli GEM InstrumentationTivoli GEM defines the concept of business systems to organize and manage related applications. Tivoli GEM consists of the following:

■ A topology server that runs as an application on the managed node.

■ One or more topology consoles run as Java-based clients.

Tivoli GEM uses application instrumentation to get the necessary data to display and to manipulate these applications in the context of business systems.

Understanding the Topology ServerThe topology server interacts with instrumented applications such as Tivoli Manager for Sybase to provide information for display on the topology console. The topology server is the recipient of heartbeat events from instrumented components. The topology server issues a heartbeat at a specified interval. The heartbeat event identifies the topology server and confirms its existence at configured intervals. Instrumented components are logical representations of Sybase GEM managed resources.

It determines the business system to which a component belongs and queries instrumented applications for related components and their status. This information creates and maintains a view of each business system’s configuration and its availability.

The topology server furnishes the topology console with a set of tasks that are applicable against a component. These tasks appear in context-sensitive menus on the topology console. The topology server also stores files on behalf of the topology console, including icons, backgrounds, help files, log files customization, views, and settings.

For more information on the topology server, refer to the Tivoli Global Enterprise Manager Installation and User’s Guide.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Understanding the Topology ConsoleThe topology console graphically displays the business system information from the topology server. The topology console displays each component as a separate icon, draws lines between icons to denote links or relationships, and uses color to indicate the status of each component and the status of the entire business system. As the topology server receives status updates pertaining to the business systems, it updates the topology console to display the real-time status of the business system.

For more information on the topology server, refer to the Tivoli Global Enterprise Manager Installation and User’s Guide.

Understanding Instrumented ComponentsThe Sybase resources as defined by Tivoli Manager for Sybase are modeled as components at the Tivoli GEM server. Tivoli Manager for Sybase resources include the SybaseDataServer, the SybaseMonitorServer, the SybaseBackupServer, the SybaseDatabase and the SybaseEngine. Each of these components has its own management capability from the GEM console.

Tivoli GEM supports aggregation, which is the logical grouping of instances of the same or different component types. Tivoli Manager for Sybase GEM Instrumentation provides for the automatic aggregation of all Sybase components based on the product and the Sybase Adaptive Server these components are associated with.

Tivoli GEM also supports manual aggregation from the topology console, which enables users to include components in aggregates of their choosing.


7–4 Version 1.1

A Sybase icon represents the highest-level aggregate component. This icon is displayed on the initial top-level view in the Middleware/DB branch of the topology server tree, as shown in the following example.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

On the topology console, you navigate from the aggregate Sybase icon to a view of all its associated SybaseDataServer aggregate icons, as shown in the following example.


7–6 Version 1.1

You can continue navigating from the aggregate SybaseDataServer icon to a view of the specific Sybase components associated with that SybaseDataServer. These components are displayed as SybaseBackupServer, SybaseDatabase, and SybaseEngine icons, as shown in the following example.

Relationships between the components are also shown on this view. The SybaseDataServer component supports connections to it, but does not discover connections. All other Sybase components initiate connections to the SybaseDataServer.

For more information on connecting to the SybaseDataServer, see “Connections to Sybase GEM Components” on page D-1.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Understanding Instrumentation Policy Regions, Profile Managers, Task Libraries, and Profiles

A policy region is created at the installation of Tivoli Manager for Sybase GEM Instrumentation. Also created are a profile manager, a Sentry profile, a File Package profile, and a task library containing resources used by Tivoli GEM to manage each component.

Following is an overview of the expected desktop structure after the Tivoli Manager for Sybase instrumentation installation for each of the components:

■ Top Level Policy Region: Applications_hostname-region

■ Policy Region: PR_Sybase_Default_hostname-region

■ Profile Managers: PM_ Component_1.1.

■ Task Libraries: TL_Sybase_1.1_Default_Component_1.1_hostname-region

■ File Packages (containing instrumentation code): FP_Sybase_1.1_Default_Component_1.1_hostname-region

■ Sentry Profiles (containing instrumentation monitors): SN_Sybase_1.1_Default_Component_1.1_hostname-region


7–8 Version 1.1

Understanding TasksThe topology server provides the topology console with a set of tasks that are applicable to a component. The task menu appears on the console if you highlight and right-click on a component’s icon. The tasks that are supported for each component are defined in the Business System Mapping and software Component Definition Files (CDF) that reside on the topology server. To run these tasks from the topology server, you must be a valid Tivoli administrator with the necessary sybase_dba role authorization.

Note: There might be authorization issues when instrumentation is run on remote systems.

Installing Tivoli Manager for Sybase GEM Instrumentation creates task libraries for the Tivoli Manager for Sybase components. Each task library contains the tasks that are supported from Tivoli GEM for that component. For a list of supported tasks, right-click on the desired component icon, then select one of the task options from the pop-up menu, as shown in the following example. For a description of each supported task, see “Tivoli Manager for Sybase GEM Instrumentation Tasks” on page 7-40.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase


7–10 Version 1.1

Understanding MonitorsThe topology console displays an icon for each monitor instance that is set up for each component, as shown in the following example.

The topology server provides the topology console a list of tasks that are applicable to monitors. The tasks menu appears on the console when you select and right-click on a monitor icon, as shown in the following example.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Tasks allow you to use Tivoli GEM to perform monitor actions such as querying and setting polling intervals from the topology console. All tasks supported for monitors are defined in the software Component Definition Files (CDF) that reside on the topology server. For supported monitors and what they do, see “Tivoli Manager for Sybase GEM Instrumentation Monitors” on page 7-39.

Installing and Configuring Tivoli Manager for Sybase GEM Instrumentation

7–12 Version 1.1

Discovering the Sybase ComponentsThe means by which the Sybase components are discovered are events sent as a result of monitors distributed to the component of interest.

The SybaseDataServer, SybaseBackupServer, SybaseMonitorServer, SybaseDatabase and SybaseEngine components are each discovered by the Sentry monitors (defined for that component by Tivoli Manager for Sybase GEM Instrumentation) distributed to the Sybase resource profile endpoint. These monitors are typed; therefore, it is impossible to discover the SybaseDatabase by distributing the SybaseBackupServer monitors to a SybaseDatabase profile endpoint.

Since the SybaseEngine is not a profile endpoint, discovery of the SybaseEngine component is by distributing the SybaseEngine monitors to its associated SybaseDataServer endpoint.

On the GEM console view, all the logically-related components have lines drawn to their associated SybaseDataServer component to show their relationships. For more information, see “Connections to Sybase GEM Components” on page D-1.


This section describes the installation prerequisites and the steps to install Tivoli Manager for Sybase GEM Instrumentation.

Preparing to Install Tivoli Manager for Sybase GEM Instrumentation

Before attempting to install Tivoli GEM Instrumentation, consider the topics in the following subsections.

Tivoli Management Regions

The Tivoli Management Regions (TMRs) should be properly configured before installing Tivoli GEM Instrumentation. Ensure that the TMR is properly configured for the topology server.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Administrators

To install Tivoli Manager for Sybase GEM Instrumentation, at least the install_product role is required. The senior role is recommended.

To execute Tivoli Manager for Sybase GEM Instrumentation component tasks from the topology console, the sybase_dba role is required for the user ID used to log on to the topology console.

Installation Prerequisites

To manage the SybaseDataServer and associated components from the Tivoli GEM topology console, make sure that all of the following installation prerequisites are met, beginning with these two steps:

■ Make sure that all Tivoli GEM prerequisite software will be installed and run on a GEM-supported operating system. For details about supported hardware and operating systems, prerequisite software, and disk space requirements, refer to the Tivoli Global Enterprise Manager Release Notes, Version 2.2.

■ Tivoli Manager for Sybase - Framework, Version 1.1, and Tivoli Manager for Sybase - Distributed Monitoring, Version 1.1, must be installed prior to installing Tivoli Manager for Sybase, Version 1.1 - GEM Instrumentation. The instrumented Sybase GEM components have a reliance on the objects created by the base module.

The following steps must be completed before installing and configuring Tivoli Manager for Sybase GEM Instrumentation

■ Tivoli Software Distribution, Version 3.1or above, must be installed.

■ Tivoli Enterprise Console, Version 3.1 or above, must be installed and configured for GEM for successful Tivoli Manager for Sybase component discovery and interaction. For information on configuring the TEC for GEM, refer to the Tivoli Global Enterprise Manager Installation and User’s Guide.

■ Tivoli GEM Topology Server 2.2.0

■ Tivoli GEM Topology Console 2.2.0


7–14 Version 1.1

■ Tivoli GEM Event Enablement 2.2.0 must be installed and configured on the node where the TEC event server is installed in order for Tivoli GEM events to be supported by TEC and for the TEC to forward events successfully to the topology server.

The Tivoli GEM Event Enablement configuration includes the following:

• Defining the APM_HEARTBEAT, APM_THRESHOLD, APM_CI_CHANGE, and APM_CONNECTION_CHANGE event classes to the TEC

• Defining the topology server or servers to which the Tivoli GEM events will be forwarded

For more information on configuring a topology server, refer to the Tivoli Global Enterprise Manager Installation and User’s Guide.

■ One of the following Java packages must be installed:

• Java Development Kit (JDK) must be installed and configured on all nodes where the Sybase components to be managed by GEM will (or already do) reside. For the levels of JDK, refer to the Tivoli Global Enterprise Manager Release Notes, Version 2.2. Also see “Configuring the Java Development Kit (JDK)” on page 7-22.

—OR—

• Java Runtime Environment (JRE) must be installed and configured on all nodes where the Sybase components to be managed by GEM will (or already do) reside. See “Configuring the Java Runtime Environment (JRE)” on page 7-23.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Installing Tivoli Manager for Sybase GEM Instrumentation

Tivoli Manager for Sybase GEM Instrumentation software is installed in the PR_Sybase_Default_hostname-region sub-policy region in the Applications_hostname-region region.

Install Tivoli Manager for Sybase GEM Instrumentation on only the TMR server. The instrumentation code will then be redistributed using file packages created as part of the instrumentation.

The following table provides the context and authorization role required for the installation procedure:



Install Tivoli Manager for Sybase GEM Instrumentation

TMR senior


7–16 Version 1.1

Installing from the Desktop

Use the following steps to install Tivoli Manager for Sybase GEM Instrumentation software from the Tivoli desktop:

1. Backup the Tivoli database.

2. From the Tivoli desktop menu, select the Install –> Install Product... option.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Tivoli displays the Install Product dialog.


7–18 Version 1.1

3. Click the Select Media…button to access the File Browser dialog to display a list of products.

4. Enter the path to the Tivoli Manager for Sybase, Version 1.1- GEM Instrumentation installation files (normally, this is the path to the CD-ROM) in the Path Name text field.

5. Click the Set Path button to change to the specified directory.

6. Click the Select Media & Close button to save the new media path and close the File Browser dialog.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

7. Tivoli returns to the Install Product dialog, which now contains a list of products for installation. Select Tivoli Manager for Sybase – GEM Instrumentation, Version 1.1 in the Select Product to Install list.

8. Select the TMR server node as the target on which to install Tivoli Manager for Sybase GEM Instrumentation. The selection is listed in the Clients to Install On scrolling list.

Note: Tivoli Manager for Sybase GEM Instrumentation only needs to be installed on the TMR server.

9. Click the Install & Close button to install the product and close the Install Product dialog.

10. The installation process prompts you with a Product Install dialog similar to the example on the next page. This dialog lists all the actions needed to complete the installation.


7–20 Version 1.1

11. Click the Continue Install button to complete the Tivoli Manager for Sybase GEM Instrumentation installation. The Product Install dialog displays messages showing the progress of the installation and a completion message when the installation is finished.

12. Click the Close button.

Setting Up Tivoli Manager for Sybase GEM Instrumentation


Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Installing from the Command Line

Use the winstall command to install Tivoli Manager for Sybase GEM Instrumentation from the command line. For more information on the this command, refer to the TME 10 Framework Reference Manual.


As part of the installation, Tivoli Manager for Sybase GEM Instrumentation creates a policy region, profile managers, profiles, file packages, and task libraries.

Note: Because a task library is created for each Sybase component, installation might take a while.


7–22 Version 1.1

Configuring the Java Development Kit (JDK)If you installed the JDK on the managed nodes where the Sybase components to be managed reside, perform the following steps:

1. On w32-ix86 platforms, you can use the Settings –> Control Panel –> System –> Environment menu options to set the PATH and CLASSPATH variables. Note that these variables are case sensitive.

2. Setup the PATH and CLASSPATH variables as follows:

a. Add the JDK bin directory to the PATH variable. For example:

PATH=%PATH%;\jdk1.1.6\bin

b. Add the JDK classes.zip to the CLASSPATH variable. For example:

CLASSPATH=%CLASSPATH%;\jdk1.1.6\lib\classes.zip

3. On UNIX platforms, you will have to configure the Tivoli environment to include jdk1.1.6/bin and jdk1.1.6/lib/classes.zip by using the following command:

odadmin environ get > odenv.txt

4. Edit the file odenv.txt to include the Java paths and reset the environment by using the following command:

odadmin environ set < odenv.txt

This command takes the updated file and resets the environment with its contents.

5. Recycle the oserv daemon by using the following command:

odadmin reexec

For more information and access to JDK, visit the following Internet site: http://www.sunsoft.com.

For more information on supported version levels of JDK, refer to the Tivoli Global Manager Release Notes, Version 2.2.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Note: When using Tivoli Manager for Sybase GEM instrumentation on a HP-UX platform with an HP-supplied JDK, you should disable the Java version checking by changing the value of gemilib.ignoreJavaVersion to YES in the gemilib.properties file. After installation and component discovery is completed, this file is located on the HP-UX machine in the following Tivoli directory:

<$BINDIR>/../generic_unix/TME/GEM/Sybase/ \Sybase/V1_1_/Sybase/$component/V1_1_/

The preceding string should be treated as a single string even though it is shown with a line-wrap.

Configuring the Java Runtime Environment (JRE)Tivoli Manager for Sybase GEM Instrumentation can use JRE in place of the JDK. To do so, the JRE must be installed in a known location. The installation directory is as follows:

$BINDIR/GEM/Instrumentation/jre

The JRE’s bin and lib directories should also be located in this directory.

If the JRE’s bin directory exists, the Tivoli Manager for Sybase GEM Instrumentation will use the JRE installed in the bin directory rather than the JDK. If the JRE’s bin directory does not exist, then the Tivoli Manager for Sybase GEM Instrumentation will attempt to use the JDK. If the JRE is removed, then the $BINDIR/GEM/Instrumentation/jre directory should also be removed or the invocation will fail.


7–24 Version 1.1

Configuring the Topology Server for Tivoli Manager for Sybase

For Tivoli GEM to manage Sybase components, the following steps must be completed:

1. The Tivoli Manager for Sybase sybase.pkg AMP file must be loaded on the topology server. See the following subsection, “Loading Tivoli Manager for Sybase sybase.pkg AMP file.”

2. Sybase components’ discovery must be initiated for the topology server. See “Initiating Sybase Components Discovery for the Topology Server” on page 7-28.

This section also describes how to confirm Tivoli GEM discovery of Sybase components.

The sybase.pkg file is a jar (zipped) file that contains all the AMS description files, icon files, and Hypertext Markup Language (HTML) help files that define Tivoli Manager for Sybase business components and their management capabilities to the topology server. The following table lists the contents of the sybase.pkg AMP file.

Type of File File Name

General files that relate to all Sybase components:

Description Files: SybaseCompo1_1Tivol.bcdfSybase1-1Sybase.gdfSybase1_1Tivoli.bsdf

Icon Files: 16_sybase_dataserver_normal.gif32_sybase_dataserver_normal.gif

Help File: dialog_sybase_437.html

SybaseDataServer component:

Description Files: SybaseDataSe1_1Sybas.cdfSybaseDataSe1_1Tivol.bmdf

Icon Files: 16_sybase_dataserver_normal.gif32_sybase_dataserver_normal.gif



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Help File: dialog_sybasedataserver_437.html

SybaseBackupServer component:

Description Files: SybaseBackup1_1Sybas.cdfSybaseBackup1_1Tivol.bmdf

Icon Files: 16_sybase_backupserver_normal.gif32_sybase_backupserver_normal.gif

Help File: dialog_sybasebackupserver_437.html

SybaseMonitorServer component:

Description Files: SybaseMonito1_1Sybas.cdfSybaseMonito1_1Tivol.bmdf

Icon Files: 16_sybase_monitorserver_normal.gif32_sybase_monitorserver_normal.gif

Help File: dialog_sybasemonitorserver_437.html

SybaseDatabase component:

Description Files: SybaseDataba1_1Sybas.cdfSybaseDataba1_1Tivol.bmdf

Icon Files: 16_sybase_database_normal.gif32_sybase_database_normal.gif

Help File: dialog_sybasedatabase_437.html

SybaseEngine component:

Description Files: SybaseEngine1_1Sybas.cdfSybaseEngine1_1Tivol.bmdf

Icon Files: 16_sybase_engine_normal.gif32_sybase_engine_normal.gif

Help File: dialog_sybaseengine_437.html

Type of File File Name


7–26 Version 1.1

Loading Tivoli Manager for Sybase sybase.pkg AMP file

To configure the topology server for Tivoli Manager for Sybase, you must load the sybase.pkg file. This can be done in one of two ways:

■ If this is the first time the set of description files is being loaded into the topology server, you can load the sybase.pkg file from the topology console client. From the topology console menu, select the File –> Load New AMP… option and select the sybase.pkg file. The sybase.pkg file is located in the tivoli_install_dir/bin/generic/SybaseScripts directory on the TMR server.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Note: If the topology server is not installed on the same node as the TMR server, this file might need to be copied to a location accessible from the topology server console. The sybase.pkg file also can be found in the SUPPORT directory on the Tivoli Manager for Sybase, Version 1.1, CD-ROM.

–OR–

■ If the description files have been loaded previously, the sybase.pkg as well as the Sybase description files must be deleted from the topology server’s appdefs directory. Use the following steps:

a. Stop the topology server if it is running.

b. Remove all the Sybase description files as well as the sybase.pkg file from the topology server’s appdefs directory

c. Copy the new sybase.pkg file into the appdefs directory and use the ihsaunpk command line utility to unpack sybase.pkg. For more information, refer to the description of the ihsaunpk command in the Tivoli Global Enterprise Manager Installation and User’s Guide.

d. Reset the topology server database if the description files have been modified.

Note: This step must be done with caution because of the likelihood of data loss. For a full description of the process and implications, refer to the Tivoli Global Enterprise Manager Installation and User’s Guide.

e. Restart the topology server.

f. Start the topology console.

g. Initiate discovery of Sybase components. See the following subsection, “Initiating Sybase Components Discovery for the Topology Server.”

h. Interact with discovered components. See “Using Tivoli Manager for Sybase GEM Instrumentation” on page 7-39.


7–28 Version 1.1

Initiating Sybase Components Discovery for the Topology Server

Component discovery is the means of informing the topology server of the existence of components. Tivoli Distributed Monitoring is the means of discovery for Sybase components. A heartbeat event, which specifies information that uniquely identifies a component, is generated and sent to the TEC. This event is then forwarded to the topology server. The topology server then makes available the management capabilities defined for this component in its description files.

Prior to initiating the discovery of Sybase components procedure, make sure all the Sybase components you wish to manage using Tivoli GEM have been registered using Tivoli Manager for Sybase. For information on registering Sybase components, see Chapter 4, “Setting Up Tivoli Manager for Sybase.”

It is important to perform this action because the means of discovery of these components by the topology server depends on them having been registered by Tivoli Manager for Sybase.

Note: The SybaseMonitorServer is not registered by default when you register the SybaseDataServer and SybaseBackupServer resources. The SybaseMonitorServer resource must be registered separately.

For more information, see “Registering a Sybase Monitor Server” on page 4-19.

To initiate the discovery of Tivoli Manager for Sybase components, do one of the following:

■ Auto-initiate Sybase component discovery. See “Auto-initiating Sybase Components Discovery” on page 7-29.

—OR—

■ Manually initiate Sybase component discovery. See “Manually Initiating Sybase Components Discovery” on page 7-33.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Note: Information in the following subsections assumes that you have installed Tivoli Manager for Sybase and registered all Sybase components to be managed from Tivoli GEM using Tivoli Manager for Sybase. For installation information, see Chapter 3, “Installing Tivoli Manager for Sybase.” For registration information, see “Registering Sybase Servers” on page 4-10.

Auto-initiating Sybase Components Discovery

You can initiate the discovery of Tivoli Manager for Sybase components with the DiscoverSybaseComponents.sh script.

The DiscoverSybaseComponents.sh script is located in the tivoli_install_dir/bin/generic/SybaseScripts directory on the TMR server. The Tivoli Manager for Sybase, Version 1.1, CD-ROM also contains the DiscoverSybaseComponents.sh script in the SUPPORT directory (however, you will need to rename DISCSYB.SH to DiscoverSybaseComponents.sh).

This script automates the Sybase components’ discovery initiation process by doing the following:

1. Lists all the available profile endpoints for a Sybase component type.

2. Prompts for user input for endpoints to discover. Accepts all selected endpoints by default.

3. Subscribes specified endpoints to their appropriate GEM-specific component profile manager.

4. Subscribes appropriate managed nodes to GEM-specific component profile manager.

5. Distributes component File Package profiles to specified profile endpoint managed nodes.

6. Unsubscribes managed nodes from a GEM-specific profile manager.

7. Distributes Sentry profiles to profile-selected endpoints.

8. Reports all status to the following log file:

$wtemp/DiscoverSybaseComponents_$timestamp.log.


7–30 Version 1.1

To successfully run DiscoverSybaseComponents.sh script, the following prerequisites must be met:

■ You have configured your Tivoli environment by running setup_env.sh.

■ Tivoli Manager for Sybase is installed and all resources for which component discovery initiation is required are registered using Tivoli Manager to Sybase.

■ Tivoli Manager for Sybase is installed on the TMR server.

■ The oserv process is running.

■ You are running a Korn or Bash shell.

To run the DiscoverSybaseComponents.sh script, enter the following at a command prompt on the TMR server:

bash$ cd <tivoli_install_dir>/bin/generic/SybaseScripts

bash$ sh DiscoverSybaseComponents.sh

A menu similar to the following example will be displayed.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Explanations for the menu prompts are as follows:

1. PRODUCT

Indicates that the product for which component discovery will be made is Sybase. The default setting is Sybase.

2. COMPONENT

Indicates that the component for which discovery will be made is SybaseDataServer. Valid entries are SybaseDataServer, SybaseBackupServer, SybaseMonitorServer, SybaseDatabase, and SybaseEngine.

3. PROFILE MANAGER

Indicates the valid GEM-specific profile manager for the SybaseDataServer component.

4. SENTRY PROFILE

Indicates the valid Sentry profile for the SybaseDataServer component.

5. PROFILE ENDPOINT(S)

Indicates the valid profile endpoints for the SybaseDataServer component. This list is dynamic and will change depending on the available registered Sybase resources and the component option selected.

6. DISCOVER COMPONENTS

Initiates discovery for the options selected, gives status of action being taken, and writes detailed output to a log file.

7. EXIT Quits menu option selection.

Note: Entries for the DiscoverSybaseComponents.sh script are case sensitive; therefore, an entry for COMPONENT such as sybasedataserver is not valid.


7–32 Version 1.1

ENTER OPTION Prompts you select the desired option by typing in its option number. Then press Enter.

For example, to select the pip_1150DS@pip profile as the endpoint for the SybaseDataServer component, enter 5 at the ENTER OPTION prompt and press Enter.

A message appears listing the current values for the selected resource, and prompts you to either enter one of the resource names or press Enter to accept all of the resources. For this example, enter pip_1150DS@pip and press Enter.

Soon after pressing Enter, you will see the menu re-displayed with, for example, pip_1150DS@pip listed as the only profile endpoint, as shown in the following example.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

To discover the SybaseDataServer component, for example, enter 6 at the ENTER OPTION prompt and press Enter.

After pressing Enter, a message appears asking you to wait while the SybaseDataServer component is discovered, followed by another message when the discovery is complete. It also displays steps for you to complete the discovery, as shown in the following example.

Shortly after this action, events will be sent to the TEC that are then forwarded to the specified topology server for component discovery to complete. See “Confirming the Sybase Component Discovery” on page 7-38.

Component discovery initiation can also be done manually. See the following subsection, “Manually Initiating Sybase Components Discovery.”

Manually Initiating Sybase Components Discovery

This subsection describes the procedure that you must perform before you can use the Tivoli GEM Instrumentation.


7–34 Version 1.1

Note: The following procedure assumes that you have installed Tivoli Manager for Sybase and registered all the Sybase components to be managed from Tivoli GEM using Tivoli Manager for Sybase. For installation information, see Chapter 3, “Installing Tivoli Manager for Sybase.” For registration information, see “Registering Sybase Servers” on page 4-10.

Perform the following steps:

1. Distribute the Tivoli Manager for Sybase GEM Instrumentation file packages. See the following subsection, “Subscribing Managed Nodes and Distributing File Packages” on page 7-34.

2. To discover the Sybase components on the topology server, distribute the appropriate Tivoli Manager for Sybase GEM Instrumentation Sentry profiles to those components. See “Subscribing Sybase Resources and Distributing Sentry Profiles” on page 7-35.

3. Make sure the GEM Administrators have valid Tivoli logins and are assigned the appropriate Sybase roles.

Subscribing Managed Nodes and Distributing File Packages

After you install Tivoli Manager for Sybase GEM Instrumentation, you can distribute the following Tivoli Manager for Sybase GEM Instrumentation file packages:

FP_Sybase_1.1._Default_SybaseBackupServer_1.1._\hostname-region

FP_Sybase_1.1._Default_SybaseDataServer_1.1._\hostname-region

FP_Sybase_1.1._Default_SybaseMonitorServer_1.1._\hostname-region

FP_Sybase_1.1._Default_SybaseDatabase_1.1._\hostname-region

FP_Sybase_1.1._Default_SybaseEngine_1.1._hostname-region



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Distribute these file packages to the managed nodes on which the Sybase components exist in order to have the instrumentation code available for local execution. The order of distribution is not important.

Note: Distribute all file packages to all nodes where Tivoli Manager for Sybase objects exist that you wish to manage from the topology server.

Subscribing Sybase Resources and Distributing Sentry Profiles

After you install Tivoli Manager for Sybase GEM Instrumentation, subscribe and distribute the component Sentry profiles as follows.

1. Subscribe the SybaseBackupServer endpoint to profile manager PM_SybaseBackupServer_1.1. and distribute the Sybase Backup Server Sentry profile:

SN_Sybase_1.1_Default_SybaseBackupServer_1.1_\hostname-region

to the SybaseBackupServer components you wish to manage from the topology server.

2. Subscribe the SybaseDataServer endpoint to profile manager PM_SybaseDataServer_1.1. and distribute the Sybase Adaptive Server Sentry profile:

SN_Sybase_1.1_Default_SybaseDataServer_1.1_\hostname-region

to the SybaseDataServer components you wish to manage from the topology server.

3. Subscribe the SybaseMonitorServer endpoint to profile manager PM_SybaseMonitorServer_1.1. and distribute the Sybase Monitor Server Sentry profile:

SN_Sybase_1.1_Default_SybaseMonitorServer_1.1_\hostname-region

to the SybaseMonitorServer components you wish to manage from the topology server.


7–36 Version 1.1

4. Subscribe the SybaseDatabase endpoint to profile manager PM_SybaseDatabase_1.1. and distribute the Sybase Database Sentry profile:

SN_Sybase_1.1_Default_SybaseDatabase_1.1_\hostname-region

to the Sybase database components you wish to manage from the topology server.

5. Subscribe the SybaseDataServer endpoint to profile manager PM_SybaseEngine_1.1. and distribute the Sybase Engine profile:

SN_Sybase_1.1_Default_SybaseEngine_1.1_\hostname-region

to the SybaseDataServer components the engine is associated with and that you wish to manage from the topology server.

Tivoli GEM receives the monitor status through TEC events forwarded to the topology server.

To subscribe and distribute the Tivoli Manager for Sybase GEM Instrumentation profiles to a SybaseDataServer endpoint, do the following:

1. Double-click the PM_SybaseDataServer_1.1. profile manager icon.

2. Add the SybaseDataServer endpoints you wish to manage from Tivoli GEM to the list of subscribers.

Do this by dragging and dropping the SybaseDataServer component on the Profile Manager window’s Subscribers palette.

—OR—

On the Profile Manager window’s main menu, select the Profile Manager –> Subscribers… option.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

3. On the Subscribers dialog, make sure your SybaseDataServer components are in the Current Subscribers scrolling list. Otherwise, select your target SybaseDataServer instances from the Available to become Subscribers scrolling list and click the left-arrow button to transfer the entries to the Current Subscribers list.

4. Click the Set Subscriptions & Close button.

5. Set the Sentry profile distribution defaults.

a. On the Profile Manager window, double-click on the following profile icon:

SN_Sybase_1.1_Default_SybaseDataServer_1.1_\hostname-region

b. On the TME 10 Distributed Monitoring Profile Properties dialog’s main menu, select the Profile –> Distribution Defaults…option.

c. On the Distribution Defaults dialog, make sure the following options are selected:

- All Levels Of Subscribers

- Make subscribers’ profile an EXACT COPY of this profile

6. Click the Set & Close button to return to the TME 10 Distributed Monitoring Profile Properties dialog.

7. Distribute the Sentry profile for:

SN_Sybase_1.1_Default_DataServer_1.1_hostname-region

to the subscribing SybaseDataServer instances.

Do this by dragging and dropping the Sentry profile on the SybaseDataServer instances you wish to manage using Tivoli GEM.

—OR—

Double-click the Sentry profile icon

8. On the Profile Manager window’s main menu, select the Profile Manager –> Distribute…option.


7–38 Version 1.1

9. On the Distribute Profile dialog, make sure only the SybaseDataServer components you wish to manage using Tivoli GEM are in the Distribute To These Subscribers scrolling list.

10. Click the Distribute & Close button to distribute the profile and return to the TME 10 Distributed Monitoring Profile Properties dialog.

Note: The monitors contained in these profiles are typed; therefore, a component discovery will not occur if a specific component profile is distributed to the wrong endpoint. For example, if a SybaseDataServer profile is distributed to the SybaseBackupServer component, a successful discovery of the SybaseBackupServer component will not be made by Tivoli GEM. The Sybase Sentry profiles should not be distributed to managed nodes.

For individual components, the order of subscription and distribution is not important. However, Tivoli advises that the Sybase Adaptive Server is included in all discoveries since all other Sybase components draw a relationship to the SybaseDataServer component and all external components wishing to connect to Sybase components must do so by way of the SybaseDataServer component.

Confirming the Sybase Component Discovery

Observe the active topology console to make sure that the Sybase components are displayed as they are discovered. Note that only components that receive a distribution are discovered.

The heartbeat monitor for each Sybase component sends a heartbeat event for each resource at a user-specified interval. When the TEC server receives a heartbeat event, it forwards the event to the topology server and an icon is displayed on the topology server.

Using Tivoli Manager for Sybase GEM Instrumentation


Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase


After you have successfully installed Tivoli Manager for Sybase GEM Instrumentation, you can use tasks and monitors to manage your registered Sybase components from the topology console. This section describes the Tivoli Manager for Sybase GEM Instrumentation tasks and monitors.

Tivoli Manager for Sybase GEM Instrumentation Monitors

This subsection outlines the monitors supported by each instrumented component:

■ Heartbeat - Informs the topology server of the existence of an instrumented component by sending an APM_HEARTBEAT event.

■ State - Informs the topology server of the state of an instrumented component by sending an APM_THRESHOLD event.

■ Connection - Detects and notifies the topology server about new and deleted connections of a particular instrumented component connection type by sending an APM_CONNECTION_CHANGE event.

■ Component information change - Informs the topology server that an instrumented component’s information has changed by sending an APM_CI_CHANGE event.

Note: You might need to redistribute GEM monitors after oserv shutdown.


7–40 Version 1.1

Tivoli Manager for Sybase GEM Instrumentation Tasks Tivoli Manager for Sybase GEM Instrumentation component tasks are contained in component tasks libraries, as described in “Understanding Instrumentation Policy Regions, Profile Managers, Task Libraries, and Profiles” on page 7-7.

Instrumentation tasks may be run from the topology console, the Tivoli desktop, or from the command line.

Tivoli recommends running all instrumentation tasks from the topology console, as described in “Starting a Component Task” on page 7-45.

Note: The instrumentation library may time out when a task is run and returns no output or causes aggregation not to occur.

The tasks supported by each instrumented component are outlined below:

■ Query State - Returns the status of the instrumented component. Returns UP if status is available, or DOWN if not.

■ Start - Starts the instrumented component and sends an event to update the GEM console view.

Notes:

• The SybaseDataServer component starts in the Multi-User mode.

• The SybaseDatabase and SybaseEngine components do not support a Start task.

■ Stop - Stops the instrumented component with the With ‘nowait’ option and sends an event to update the GEM console view.

Note: The SybaseDatabase and SybaseEngine components do not support a Stop task.

■ DataServerLabel - Returns the SybaseDataServer label. (Used in aggregation.)

■ View Component Properties - Displays the instrumented component’s Tivoli Manager for Sybase registration details.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

■ View Error Log - Displays the last 75 lines of the instrumented component’s error log.

Note: The SybaseDatabase and SybaseEngine components do not support a View Error Log task.

■ Query Value - Returns the current value for a specified monitor.

■ Set Polling Interval - Sets the monitoring schedule to the specified interval in minutes.

■ Query Thresholds - Sends one or more threshold events to the TEC for use by the Tivoli GEM environment.

■ Query Threshold Settings - Returns current threshold settings.

■ Set Pulse - Adjusts the frequency at which the heartbeat monitor is run.

■ Set Thresholds - Defines the circumstances under which threshold events are sent to the topology server.


7–42 Version 1.1

Navigating to Sybase Components on the Topology Console

An aggregate Sybase icon is the highest level Sybase aggregate component. This is displayed at the Middleware/DB branch of the topology server tree view, as shown in the following example.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Double-click the Sybase aggregate icon on the Middleware/DB branch to display the SybaseDataServer aggregate icons, as shown in the following example.

On the topology console, you can navigate from an aggregate SybaseDataServer icon to the specific Sybase components associated with that SybaseDataServer component. Right-click on a component icon to access a pop-up menu from which you can select tasks and other options, as shown in the following example, or you can continue clicking icons to navigate down the tree to see monitors received by the topology server for that component.


7–44 Version 1.1



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Using the Tear-Away LogPrior to starting a task, open the tear-away log provided by the topology console. The log provides current messages that show the progress of the tasks you run. To tear away the topology console log, do the following:

From the topology console menu bar, select the Options –> Tear Away Log option.

Tivoli displays the GEM - Log window, as shown in the following example.

Starting a Component TaskThe following procedure allows you run all Sybase GEM Instrumentation tasks from the topology console.


To perform a task such as shutting down the Sybase Adaptive Server, perform the following steps:

1. Right-click on the SybaseDataServer icon.

2. From the pop-up menu, select the Stop option.


Starting a component task

Sybase GEM component

sybase_dba


7–46 Version 1.1

3. Enter Y in the Confirmation window and click the Set and Execute button.

The topology console tear-away log window provides a progress report listing of the task just executed. In the example GEM - Log window above, the messages indicate that the Sybase Adaptive Server was shutdown.



Settin

g U

p an

d U

sing

T

ivoli M

anag

er for S

ybase

Viewing Monitor StatusTo view the status of the Tivoli Manager for Sybase monitors supported by Tivoli GEM on the topology console, do the following:

■ Navigate to the Sybase component you wish to view monitors for. See “Navigating to Sybase Components on the Topology Console” on page 7-42.

■ Double-click on the component to see the monitors associated with that component, as shown in the following example.


7–48 Version 1.1

Deleting Components from a ViewTo delete Sybase components from the topology console, right-click on the component icon you wish to delete and select the Delete From All Views option from the pop-up menu.

Note: This action deletes the Sybase component from the topology server database but does not delete the Tivoli Sybase resource nor stop the component monitors running. To stop monitors running, unsubscribe the Sybase components from the profile manager by selecting the with Delete all profile copies option.

Tivoli Manager for Sybase User’s Guide A–1

Referen

ce

AMonitoring Collection Information

This appendix provides information on the suggested monitoring profiles. It also provides a list of all monitors with their descriptions, functional groups (either performance or availability), and monitor types.

Monitor Type DefinitionsThe following list defines the monitor types that are used in the tables in this section.

Access Highlights problems with connecting to a server or any of its objects.

CPU Highlights problems with processing of commands.

Error Highlights problems with errors occurring on the server.

IO Highlights problems with disk reads and disk writes or network traffic.

Locks Highlights problems with lock availability.

Recovery Highlights problems with the ability to recover in the case of device failure.

A

Suggested Monitoring Profiles

A–2 Version 1.1

Space Usage Highlights problems with both data and log space usage.

Memory Highlights problems with memory usage.

Suggested Monitoring ProfilesThis section provides a list of recommended profiles containing the minimum set of monitors recommended to monitor a Sybase Adaptive Server. The following recommended profiles are described in the following subsections:

■ Sybase Adaptive Server performance monitors

■ Sybase Adaptive Server availability monitors

■ Sybase Backup Server availability monitors

■ Sybase Monitor Server availability monitors

■ Sybase Database availability monitors

Sybase Adaptive Server Performance MonitorsThis following table lists the minimum set of recommended Tivoli Manager for Sybase monitors to add to a profile for Sybase Adaptive Server performance monitoring. All of the monitors listed come from the SybaseServer monitoring collection.

Distribute a profile with the following monitors to only SybaseDataServer endpoints:

Recommended Monitors Monitor Type

Blocked Processes Locks

Percent Locks Used Locks

CPU by Process CPU

Memory Usage by Process Memory

Engine CPU Busy CPU



Referen

ce

Sybase Adaptive Server Availability MonitorsThis following table lists the minimum set of recommended Tivoli Manager for Sybase monitors to add to a profile for Sybase Adaptive Server availability monitoring. All of the monitors listed come from the SybaseServer monitoring collection.

Distribute the profile with the following monitors to only SybaseDataServer endpoints:

Sybase Backup Server Availability MonitorsThis following table lists the minimum set of recommended Tivoli Manager for Sybase monitors to add to a profile for Sybase Backup Server availability monitoring. All of the monitors listed come from the SybaseServer monitoring collection.

Distribute the profile with the following monitors to only SybaseBackupServer endpoints:


Percent Connections Used Access

Database Status Access

DataServer Errors Error

Engine Status Access

SLD Free Space Space Usage

Percent Transaction Log Space Used By Server Space Usage

Long Running Transactions Access

SQL Server Status Access



Backup Server Errors Error


A–4 Version 1.1

Sybase Monitor Server Availability MonitorsThis following table lists the minimum set of recommended Tivoli Manager for Sybase monitors to add to a profile for Sybase Monitor Server availability monitoring. All of the monitors listed come from the SybaseServer monitoring collection.

Distribute the profile with the following monitors to only SybaseMonitorServer endpoints:

Sybase Database Availability MonitorsThis following table lists the minimum set of recommended Tivoli Manager for Sybase monitors to add to a profile for Sybase Database availability monitoring. All of the monitors listed come from the SybaseDatabase monitoring collection.

Distribute the profile with the following monitors to only SybaseDatabase endpoints:




Database State Access

Percent Free Segment Space Space Usage

Percent Transaction Log Space Used Space Usage

Descriptions of All Monitors with Functional Groups and Monitor Types


Referen

ce


This section has two tables, which list all the Tivoli Manager for Sybase monitors (in the SybaseServer and SybaseDatabase collections) by their functional groups and monitor types. The tables also provide a brief description of the monitors.

The following table describes all the SybaseServer monitors.

SybaseServer Monitor Name

DescriptionFunctional Group/

Type

Backup Server Errors Checks the Sybase Backup Server error log for error messages in the defined functional area with the specified severity range, and reports the severity.

Availability/Error

Bad Processes Reports processes with a current status of bad status.

Availability/Error

Blocked Processes Reports processes with a current status of lock sleep that have been blocked for longer than the specified number of seconds.

Performance/Locks

Connections Available

Reports the number of user connections currently available on the target server.

Availability/Access

Connections In Use Reports the current number of user connections to the target server.

Availability/Access

CPU by Process Reports the user process with the largest cumulative CPU time in seconds on the target server.

Performance/CPU

Currently Open Databases

Reports the number of currently open databases.

Availability/Access

Database Status Identifies databases found to be in a state specified by the user as an argument to the monitor.

Availability/Access


A–6 Version 1.1

DataServer Errors Checks the Sybase Adaptive Server error log for specific errors. All error messages are categorized and the worst new error message is the trigger.

Availability/Error

DataServer Errors by Severity

Checks the Sybase Adaptive Server error log for error messages of the specified severity levels.

Availability/Error

Device Mirror Status Reports the mirror status of a user-specified device.

Availability/Recovery

Engine CPU Busy Reports the percentage of the server’s time since startup that was used by the engine for CPU activity.

Performance/CPU

Engine Status Reports the number of engines found in the state specified as an argument to the monitor.

Availability/Access

Infected Processes Reports on those processes marked as infected in the system table sysprocesses.

Availability/Error

Locks Available Reports the number of locks currently available on the target server.

Performance/Locks

Locks In Use Reports the number of locks currently in use on the target server.

Performance/Locks

Long Running Transactions

Tracks those processes that have been idle since the monitor was last run, and returns the program names.

Availability/Access

Memory Usage by Process

Checks the amount of memory in pages being used by each process running on the server, and returns the largest amount being used.

Performance/Memory

Packet Errors Returns the number of network errors that have occurred since server startup while it was sending and receiving packets.

Performance/IO



Type



Referen

ce

Packets Received Returns the total number of network packets read by the server since startup.

Performance/IO

Packets Sent Returns the total number of network packets written by the server since startup.

Performance/IO

Percent Connections Used

Returns the current number of user connections to the target server as a percentage of the allowed connections.

Availability/Access

Percent Locks Available

Returns the number of locks currently available on the target server as a percentage of the maximum number of locks allowed.

Performance/Locks

Percent Locks Used Returns the number of locks currently in use on the target server as a percentage of the maximum number of locks allowed.

Performance/Locks

Percent Transaction Log Space Used

Evaluates each database, determines the total space available for the transaction log, calculates the percentage of log space currently in use by the log, and returns the name and the figure for the database with the highest percentage found. The output also includes the transaction log usage figures for all the other databases on the server.

Availability/Space Usage

Physical IO by Process

Examines the number of disk reads and writes for all the user processes on the server, determines the amount of physical I/O so far performed by the current command, and returns the highest physical I/O found for a process.

Performance/IO

SLD Free Space Checks all the devices and returns the name and percentage of free space for the device with the smallest percentage of free space.




Type


A–8 Version 1.1

SLD Free Space by Device

Returns the space, in kilobytes (KB), not allocated to databases on a logical device at the target server.


SLD Space Used by Device

Returns the space, in kilobytes (KB), allocated to databases on a specified device on the target server.


SQL Server Status Checks the ability to connect to the specified server.

Availability/Access

Stopped Processes Returns the number of processes with a current status of Stopped in the system table sysprocesses.

Availability/Error

User CPU Busy Analyzes the amount of CPU time used by each user connected to the server, and returns the highest CPU time used as a percentage of the server’s time since startup. The output also includes all the other CPU times with their associated user IDs.

Performance/CPU



Type



Referen

ce

The following table describes all the Sybase Database monitors.

SybaseDatabaseMonitor Name


Type

DataBase State Checks the status of the target database and reflects a summary of the database states on the desktop icon.

Availability/Access

Free Form SQL Numeric

A user-defined monitor that runs a TRANSACT-SQL SELECT statement, which returns a numeric value.

(Not applicable)

Free Form SQL String A user-defined monitor that runs a TRANSACT-SQL SELECT statement that returns a string value.

(Not applicable)

Free Segment Space by Segment

Checks the space currently used by data and by indexes in a user-specified segment on the target database. Returns the total unused space, in kilobytes (KB).


Percent Free Segment Space

Checks the space currently used by data and by indexes in a user-specified segment on the target database. Returns the total unused space as a percentage of the segment’s total size.


Percent Transaction Log Space Used

Determines the total space available for the transaction log of the target database. Reports the percentage currently used by the log.


Transaction Log Free Space

Determines the total space available for the transaction log of the target database. Reports the space, in kilobytes (KB), currently not used but available for the log.


Used Segment Space by Segment

Checks the space currently used by data and by indexes in a user-specified segment on the target database. Returns the total used space, in kilobytes (KB).



A–10 Version 1.1

Tivoli Manager for Sybase User’s Guide B–1

Referen

ce

BAuthorization Roles

Each Tivoli Manager for Sybase procedure has a required authorization role. The following table summarizes these activities and roles and tells you where to find additional information in this manual:

B

Activity ContextRequired

RoleFor Additional

Information

Install software TMR senior See “Installing Tivoli Manager for Sybase” on page 3-2.

Change a Tivoli administrator properties (subscribe to notice group)

Adminis-trators collection

senior See “Subscribing to Notice Groups” on page 4-2.

Add or remove a managed resource type for a policy region

Policy region senior See “Adding the SybaseData- Server Managed Resource Type” page 4-6.

Register a Sybase Adaptive Server

Policy region sybase_dba and senior in the TMR

See “Registering Sybase Servers” on page 4-10.

B–2 Version 1.1

Register a Sybase Monitor Server

Sybase Adaptive Server

sybase_dba and senior in the TMR

See “Registering a Sybase Monitor Server” on page 4-19.

Configure the TEC

Managed node (where the event server is installed)

super, senior, admin, user, and sybase_dba (must have all roles)

See “Manually Configuring the TEC” on page 4-31.

Add a profile manager to a policy region

Policy region admin See “Adding a Profile Manager and a Profile” on page 5-6.

Add a profile to a profile manager

Profile manager

admin See “Adding a Profile Manager and a Profile” on page 5-6.

Add an indicator collection

Policy region admin See “Adding an Indicator Collection” on page 5-12.

Associate an indicator collection with a profile


admin See “Associating an Indicator Collection with a Profile” on page 5-15.

Add and edit a monitor


admin See “Adding Monitors to a Profile” on page 5-19.


RoleFor Additional

Information


Referen

ce

Set user and group ID (default policy)


senior See “Setting the User and Group ID for a Profile” on page 5-42.

Open a Sybase Adaptive Server collection


sybase_user or sybase_dba

See “Opening a Sybase Data Server Collection” on page 6-2.

Change the Sybase Adaptive Server registration


sybase_dba See “Changing Sybase Adaptive Server Registration Details” on page 6-6.

View Sybase Adaptive Server properties



See “Viewing Sybase Adaptive Server Properties” on page 6-9.

View Sybase Adaptive Server log



See “Viewing Sybase Adaptive Server Error Log Contents” on page 6-12.

Start the Sybase Adaptive Server


sybase_dba See “Starting a Sybase Adaptive Server” on page 6-15.

Shut down the Sybase Adaptive Server


sybase_dba See “Shutting Down a Sybase Adaptive Server” on page 6-17.


RoleFor Additional

Information

B–4 Version 1.1

Check the state of the Sybase Adaptive Server



See “Checking the State of a Sybase Adaptive Server” on page 6-20.

Open a Sybase Database collection

Sybase Database


See “Opening a Sybase Database Collection” on page 6-24.

View Sybase Database properties

Sybase Database


See “Viewing SybaseDatabase Endpoint Properties” on page 6-27.

Check the state of the Sybase Database

Sybase Database


See “Checking the State of a SybaseDatabase Endpoint” on page 6-29.

View Sybase Engine properties

Sybase Engine


See “Viewing SybaseEngine Instance Properties” on page 6-34.

Check the state of a Sybase Engine

Sybase Engine


See “Checking the State of a SybaseEngine Instance” on page 6-36.

Open a Sybase Backup Server collection

Sybase Backup Server


See “Opening a Sybase Backup Server Collection” on page 6-40.


RoleFor Additional

Information


Referen

ce

Change the Sybase Backup Server registration

Policy region sybase_dba See “Changing Sybase Backup Server Registration Details” on page 6-42.

View Sybase Backup Server properties



See “Viewing Sybase Backup Server Properties” on page 6-45.

View Sybase Backup Server log



See “Viewing Sybase Backup Server Error Log Contents” on page 6-47.

Start the Sybase Backup Server


sybase_dba See “Starting a Sybase Backup Server” on page 6-49.

Shut down the Sybase Backup Server


sybase_dba See “Shutting Down a Sybase Backup Server” on page 6-52.

Check the state of the Sybase Backup Server



See “Checking the State of a Sybase Backup Server” on page 6-55.

Open a Sybase Monitor Server collection

Sybase Monitor Server


“Opening a Sybase Monitor Server Collection” on page 6-59.


RoleFor Additional

Information

B–6 Version 1.1

Change the Sybase Monitor Server registration


sybase_dba See “Changing Sybase Monitor Server Registration Details” on page 6-61.

View Sybase Monitor Server properties



See “Viewing Sybase Monitor Server Properties” on page 6-64.

View Sybase Monitor Server log



See “Viewing Sybase Monitor Server Error Log Contents” on page 6-66.

Start the Sybase Monitor Server


sybase_dba See “Starting a Sybase Monitor Server” on page 6-68.

Shut down the Sybase Monitor Server


sybase_dba See “Shutting Down a Sybase Monitor Server” on page 6-71.

Check the state of the Sybase Monitor Server



See “Checking the State of a Sybase Monitor Server” on page 6-75.


RoleFor Additional

Information


Referen

ce

Remove an object from a policy region

Policy region admin, senior, or sybase_dba

See “Removing Objects from a Sybase Data Server Collection” on page 5-79.

Remove an object from a Sybase Adaptive Server collection


sybase_dba See “Removing Objects from a Sybase Data Server Collection” on page 6-79.

Add one or more subscribers

Profile manager’s policy region and subscribers policy region or regions

admin (profile) and sybase_dba

See “Subscribing Endpoints to Profile Managers” on page 6-80.

Distribute a profile to the next level


admin See “Distributing a Monitoring Collection Profile” on page 6-84.Distribute a

profile to all levels, or from a Sybase Adaptive Server or Sybase Database endpoint

Distributed Monitoring profile and Sybase Adaptive Server endpoint

admin (profile) and

sybase_dba

View events in the TEC

Event console user See “Viewing Events in the Tivoli Enterprise Console” on page 6-96.


RoleFor Additional

Information

B–8 Version 1.1

Tivoli Manager for Sybase User’s Guide C–1

Referen

ce

COperator Groups

The Edit Monitor dialog contains the trigger when drop-down list, which enables you to define the conditions that must occur for a monitor to send an alert. The values displayed in this menu vary depending on whether the monitor uses a numeric value, a string value, or a status message. These options are defined in operator groups. Each option of an operator group serves as a mathematical or logical evaluator.

Each operator description includes the value for the waddmon –R argument. The quotation marks for each operator are required. If you want to specify the (never) operator from the command line, omit the –R argument.

Numeric Operator GroupTo define a threshold value, select one of the following options and enter a number in the argument field.

(never) Indicates the response level does not trigger a response. This value affects only the specific response level, not the entire monitor.

Greater than Records the value of each sample, compares it to the specified value, and triggers a response when the current value is greater than the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample.

C

Numeric Operator Group

C–2 Version 1.1

This operator can be specified at the command line by entering “>” .

Less than Records the value of each sample, compares it to the specified value, and triggers a response when the current value is less than the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample. This operator can be specified at the command line by entering “<” .

Equal to Records the value of each sample, compares it to the specified value, and triggers a response when the current value is equal to the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample. This operator can be specified at the command line by entering “==” .

Not equal Records the value of each sample, compares it to the specified value, and triggers a response when the current value is not equal to the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample. This operator can be specified at the command line by entering “!=” .

Increases beyond Compares the current value against the previous value and triggers only if the current value is greater than both the previous value and the threshold specified in the argument field. This operator can be specified at the command line by entering “->>” .

Decrease below Records the value of each sample and triggers a response when the previous resource value is above the threshold specified in the text field, but the current value is below the specified threshold. This operator can be specified at the command line by entering “-<<“ .

String Operator Group


Referen

ce

Increase of Checks the current value against the previous value and triggers a response when the difference is greater than or equal to the threshold value. This operator can be specified at the command line by entering “->=” .

% increase of Checks the current value as a percentage of the previous value and triggers a response when the current value is greater than or equal to the specified value. This operator can be specified at the command line by entering “%>=” .

Changes by Measures an absolute difference between the previous and current value. This operator can be specified at the command line by entering “+>” .

Outside range Compares each sample against the defined range limit and triggers a response when the current value falls outside the specified range. Because the range check is made against the current sample, this monitor type can trigger after any sample. To define the acceptable range, enter a lower and upper limit separated by a dash in the argument field. This operator can be the argument field. This operator can be specified at the command line by entering “<>” .

String Operator GroupTo define the threshold value, select one of the following options and enter a string (which can include wildcard characters) in the argument field.

(never) Indicates the response level does not trigger a response. This value only affects the specific response level, not the entire monitor.

Equal to Records the value of each sample, compares it to the specified value, and triggers a response when the current value is equal to the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample.

String Operator Group

C–4 Version 1.1

This operator can be specified at the command line by entering “==” .

Not equal to Records the value of each sample, compares it to the specified value, and triggers a response when the current value is not equal to the specified value. Because it checks only against the current sample, this type of threshold can trigger after any sample. This operator can be specified at the command line by entering “!=” .

Matches Checks the value returned by the query script value against the threshold value provided for user-defined and asynchronous string monitors. A response is triggered if the response matches the value provided. (The query program is named in the Add Monitor to Tivoli/Sentry Profile dialog.) This operator can be specified at the command line by entering “=~” .

Mismatches Checks the value returned by the query script value against the threshold value provided for the user-defined and asynchronous string monitors. A response is triggered if the response does not match the value provided. (The query program is named in the Add Monitor to Tivoli/Sentry Profile dialog.) This operator can be specified at the command line by entering “!~” .

Changes to Compares the current value returned by the query script value and compared to the threshold value provided for user-defined and asynchronous string monitors against the previous value. A response is triggered if the current value matches the value provided, but the previous value did not. (The query program is named in the Add Monitor Tivoli/Sentry Profile dialog.) This operator can be specified at the command line by entering “->” .

Additional Operator Groups


Referen

ce

Changes from Compares the current value returned by the query script value and compared to the threshold value provided for user-defined and asynchronous string monitors against the previous value. A response is triggered if the current value does not match the value provided, but the previous value did. (The query program is named in the Add Monitor Tivoli/Sentry Profile dialog.) This operator can be specified at the command line by entering “-<“ .

Additional Operator GroupsThere are three additional operator groups, each applicable to only one monitor. Therefore, these operator groups are described in the relevant monitor descriptions in the Tivoli Manager for Sybase Reference Guide. The operator groups are as follows:

Device Mirror Status Operator Group See the Device Mirror Status monitor description in Chapter 2, “The SybaseServer Monitoring Collection,” of the Tivoli Manager for Sybase Reference Guide.

Server Status Operator Group See the SQL Server Status monitor description in Chapter 2, “The SybaseServer Monitoring Collection,” of the Tivoli Manager for Sybase Reference Guide.

Database State Operator Group See the Database State monitor description in Chapter 3, “The SybaseDatabase Monitoring Collection,” of the Tivoli Manager for Sybase Reference Guide.

Additional Operator Groups

C–6 Version 1.1

Tivoli Manager for Sybase User’s Guide D–1

Referen

ce

DSupporting Connections to Sybase Components

This appendix describes the following topics:

■ The approach taken in designing connections to Tivoli Manager for Sybase GEM Instrumentation components.

■ The means by which external components can be connected to Sybase components.

■ The connection types supported by Tivoli Manager for Sybase GEM Instrumentation.

■ The AppDriver.java method implemented to enable the external component to initiate a relationship to the Sybase component.

Connections to Sybase GEM ComponentsThis section deals with the approach taken in designing connections to Sybase GEM components.

D

Connections to Sybase GEM Components

D–2 Version 1.1

What Do External Components Connect To?Applications wishing to connect to the Sybase Relational Database Management System (RDBMS) component must connect to the dataserver component for that Sybase RDBMS. Direct connections to the Sybase components, other than the dataserver component, are not supported. The view is taken that all interactions with the Sybase RDBMS components are managed by the dataserver and showing direct connections to the actual Sybase component is not relevant, or else presents an incomplete view of component interrelations.

For example a client application that uses a Sybase database called tec, connects to the tec database by way of the SybaseDataServer component the tec database is associated with, and not the tec database component itself.

Who Should Initiate Relationships with the SybaseDataServer Component?

Applications wishing to establish a relationship with the Sybase RDBMS component must initiate the relationship to the SybaseDataServer component. It is not practical for the Sybase RDBMS server component to initiate this relationship since the external component might not exist in the management tool’s database, or might not actually be instrumented.

The SybaseDataServer component has no way to determine what components wish to connect to it, nor any way of validating a connection. It is the responsibility of the instrumentor of the external component to ensure that the connection to the database component is valid.

Defining Relationships with the SybaseDataServer Component


Referen

ce


The identity of a relationship between the SybaseDataServer component and an external component is given by the following:

■ The supported SybaseDataServer component connection type.

■ The SybaseDataServer communication object information (name/value pairs for event origin and sub-origin slots).

■ The connection direction.

Relating ComponentsThe relationship initiator must provide information relevant to connecting to the SybaseDataServer component. This information includes the SybaseDataServer component connection type, communication object, and the connection direction.

Specifically, the relationship initiator must provide the following details:

■ A connection type that must be a supported SybaseDataServer connection type.

■ A valid name/value information pair that matches what is in the origin and sub-origin slots of the heartbeat event for the SybaseDataServer component that the initiator wishes to connect to. This may be achieved by implementing the AppDriver.java method getInstanceRelations() to return a relation array containing this information.

■ A valid connection direction. The connection direction is a number representing the connection direction, as follows:

• 1 for origin

• 2 for destination

• 3 for conversational or bi-directional

Note: All Sybase connections supported for external connections are bi-directional.


D–4 Version 1.1

Tivoli Manager for Sybase GEM Instrumentation Component Connection Types

The following table lists the connection types supported by the SybaseDataServer component.

Connection Type

Origin Destination Conversational

DBConnection1 X

Sybase DB1 X

ServedBy2 X

Serves2 X

Notes:

• 1DBConnection and Sybase_DB connection types are bi-directional (conversational) and are defined as interfaces by which external components can connect to the SybaseDataServer component.

• 2ServedBy and Serves connection types are reserved for use as the Sybase component intra-connection types.



Referen

ce

The Sybase DataServer Component Communication Information

The SybaseDataServer component supports the following table of name/value information pairs in its heartbeat event origin and sub-origin slots.

Name/Value Pair Variable Description

Origin - Hostname, hostname

Sub-origin - SybaseDataServer, instanceID_

The hostname is the name of the host the SybaseDataServer resides on (in lower case).

The instanceID_ is the object identity of the SybaseDataServer as determined by: wlookup –r SybaseDataServer pip_1150DS@pip.

Origin - DataServerLabel, labelString

Sub-origin - SybaseDataServer, instanceID_

The labelString is the object label of the SybaseDataServer as determined by the _get_label method. For example, idlcall -v $DataServerOID _get_label.

The instanceID_ is the object identity of the SybaseDataServer as determined by: wlookup –r SybaseDataServer pip_1150DS@pip.


Sub-origin - SybaseServerID, dataserverID


The dataserverID is the identity (or name) of the Sybase installation. This by default corresponds to the host name in upper case on NT. On UNIX, the SybaseDataServer name may be different from the host name.


D–6 Version 1.1


Sub-origin - RDBMSIdentifier, dataserverID



Origin - TCPIPAddress

Sub-origin - RDBMSIdentifier, dataserverID

The TCPIPAddress is the TCP/IP address of the host that the SybaseDatsServer resides on. This may be determined using the Java utility, TCPIPAddress.getLocal().


Notes:

• The italicized words above are variables, whose values must be valid as described in the right column.

• All of the name/value pairs above are as listed in the origin and sub-origin slots of the SybaseDataServer heartbeat event. See “SybaseDataServer Heartbeat Event” on page D-9.

Name/Value Pair Variable Description



Referen

ce

Implementing the Relationship in AppDriver.javaTo initiate a connection to any component you will need to implement the getInstanceRelations() method in AppDriver.java. The getInstanceRelations() method should return a list representing the relationships in which the initiator is currently participating.

An external component wishing to establish a relationship with the Sybase DataServer component must match at least one of the name/value pairs specified in the previous table. Also see “Implementing the Relationship in AppDriver.java” on page D-7.

Note: Values for origin and sub-origin event slots are case sensitive and matches must be exact.

In implementing the getInstanceRelations() method, the objective is to return a relation array that contains the information relevant to forming a relationship with the SybaseDataServer component you wish to connect to (see the example “SybaseDataServer getInstanceRelations() Method” on page D-8). The information relevant to forming this relationship must be at least one of the pairs returned in the origin/sub-origin heartbeat event (see the example “SybaseDataServer Heartbeat Event” on page D-9).


D–8 Version 1.1

SybaseDataServer getInstanceRelations() Method

public Relation[] getInstanceRelations()

{

Log.startLevel("getInstanceRelations()");

rels_ = null;

ExecResults relation = Utility.execShell("relate_to_sybasedataserver.pl "+instanceID_+"");

String connection = relation.getStandardOut().trim();

java.util.StringTokenizer st = new java.util.StringTokenizer(connection);

String connServerLabel = st.nextToken().trim();

String connServerOID = st.nextToken().trim();

relcomms_ = new Communication[1];

relcomms_[0] = new Communication(new GenericAttribute("DataServerLabel", connServerLabel),new GenericAttribute("SybaseDataServer", connServerOID));

rels_ = new Relation[1];

rels_[0] = new Relation("Sybase_DB", relcomms_[0], 3);

Log.endLevel();

return rels_;

}

The external component will have to run a method that returns a valid name/value pair that can then be used for the relation array.

In the above example, the Perl script relate_to_sybasedataserver.pl expects the initiator’s instanceID as an argument and returns the label and OID of the SybaseDataServer that the initiator wishes to form a relationship with.

Note: The initiator may form relationships with multiple components, or other components may form relationships with it.



Referen

ce

SybaseDataServer Heartbeat Event

### EVENT ###

APM_HEARTBEAT;

hostname=’pip’;

adapter_host=’pip’;

source=’Sybase;Sybase;1.1’;

apm_old_source=’Sybase;Sybase;1.1’;

origin=’0=SybaseDataServer=pip;0=DataServerLabel=pip_1150DS@pip;0=Hostname=pip;0=Hostname=pip;0=Hostname=pip;1=146.84.23.168;’;

sub_origin=’0=SybaseDataServer=1875228845.1.888;0=SybaseDataServer=1875228845.1.888;0=RDBMSIdentifier=pip_1150DS;0=SybaseDataServer=1875228845.1.888;0=SybaseServerID=pip_1150DS;0=RDBMSIdentifier=pip_1150DS;’;

severity=’HARMLESS’;

msg=’Sybase;SybaseDataServer;1.1: pip_1150DS@pip is Down’;

apm_hbinterval=360;

apm_old_origin=’0=SybaseDataServer=pip’;

apm_old_sub_origin=’0=SybaseDataServer=1875228845.1.888’;

apm_endpoint_oid=’1875228845.1.888#ESMSybaseDataServer::ESMSybaseDataServerBase#’;

apm_display_name=’pip_1150DS@pip’;

sub_source=’Sybase;SybaseDataServer;1.1’;

apm_data4=’’;

apm_data3=’’;

apm_data2=’’;

apm_data1=’’;

apm_old_sub_source=’Sybase;SybaseDataServer;1.1’;

apm_es_managed_node=’1=JANE’;

apm_application_status=1;

END

;

### END EVENT ###

PROCESSED


D–10 Version 1.1

Tivoli Manager for Sybase User’s Guide Index–1

Index

Symbols.baroc files

ESMSentry.baroc 4-27M7SybaseDatabase.baroc 4-28M7SybaseServer.baroc 4-28

Aactions, monitoring response options 5-27Add Monitor to TME 10 Distributed

Monitoring Profile dialog 5-22Add Monitor to TME 10 Monitoring

Profile dialog 5-20Add Scheduled Job dialog 6-90

example 6-91adding

indicator collections to policy regions 5-12

managed resource types 4-7monitors to profiles 5-19profile managers and profiles to

policy regions 5-6subscribers to profile managers 6-80SybaseDataServer managed

resource type 4-6admin, Tivoli authorization role 1-3administrators

Administrator icon 4-3Root administrator 4-2Tivoli administrators 1-2Tivoli Manager for Sybase GEM

Instrumentation 7-13

Administrators collection window 4-3Edit Notice Group Subscriptions...

option 4-3Administrators icon 4-3aggregation

definition 7-3manually from the topology console 7-3

always, monitor response level 5-26associating indicator collections

with profiles 5-15authorization roles, definition 1-3auto-initiating discover of Sybase components

Tivoli Manager for Sybase GEM Instrumentation 7-29

Available, detailed stateSybase Adaptive Servers 6-21Sybase Backup Servers 6-56Sybase Monitor Servers 6-76

CChange Backup Server Registration

Details dialog 6-44Change Icon, monitoring response

action 5-27Change Monitor Server Registration Details

dialog 6-63changing registration details

Sybase Adaptive Servers 6-6Sybase Backup Servers 6-42Sybase Monitor Servers 6-61

checking statesSybase Adaptive Servers

detailed states 6-21general states 6-20

Sybase Backup Serversdetailed states 6-56general states 6-55

Index–2 Version 1.1

Sybase Monitor Serversdetailed states 6-76general states 6-75

SybaseDatabase endpointsdetailed states 6-30general states 6-29

SybaseEngine instancesdetailed states 6-37general states 6-36

CLISee command line

command lineadding managed resource types 4-9adding subscribers to profile

managers 6-84distributing monitoring profiles 6-93installing Tivoli Manager for Sybase

GEM Instrumentation 7-21integrating with the TEC

creating a new rule base and importing events 4-33

importing event classes into an existing rule base 4-34

registering Sybase Adaptive Servers 4-16

registering Sybase Monitor Servers 4-24removing managed resource types 4-9setting up monitoring profiles 5-45using the command line 1-8

command line interface (CLI)See command line

commandsodadmin 7-22sregmonsvr 4-24sregsqlsvr 4-16wcomprules 4-34, 4-35wcprb 4-33wcrtprf 5-45wcrtprfmgr 5-45wcrtrb 4-33wcrtsntcoll 5-45

wdistrib 6-93wgetpr 4-9wimprbclass 4-33, 4-35winstall 3-12, 7-21wloadrb 4-34, 4-35wlookup 4-33wsetpr 4-9wstartesvr 4-34, 4-35wstopesvr 4-34, 4-35wsub 6-84

configuringTivoli Manager for Sybase GEM

Instrumentation 7-12Java Development Kit (JDK) 7-22

on UNIX platforms 7-22on w32-ix86 platforms 7-22

Java Runtime Environment (JRE) 7-23

topology servers 7-24confirming Sybase component discovery


contents of AMP file table, sybase.pkg file 7-24

Create Indicator Collection dialog 5-13Create Profile dialog 5-10Create Profile Manager dialog 5-7critical, monitor response level 5-26Customize Monitoring Schedule Restrictions

dialog 5-40

DData Server Unavailable, detailed state

SybaseDatabase endpoints 6-30SybaseEngine instance 6-37

database owner use only (DBU) 6-31


database endpointdetailed states 6-30general states 6-29opening a Sybase Database collection

6-24SybaseDatabase endpoint 1-4SybaseDatabase icon 1-6

DBO Use Only, detailed stateSybaseDatabase endpoints 6-31

Debug, detailed stateSybaseEngine instance 6-37

Delete Icons from server collection dialog 6-79

Delete Objects? dialog 6-79deleting components from topology console

view 7-48Desktop Navigator

accessing 1-8using 1-8

Desktop Navigator dialog 1-9detailed states

Sybase Adaptive Servers 6-21Sybase Backup Servers 6-56Sybase Monitor Servers 6-76SybaseDatabase endpoints 6-30

determiningmonitors distributed to endpoints 6-94monitors running at endpoints 6-95

dialogsAdd Monitor to TME 10 Distributed

Monitoring Profile 5-22Add Monitor to TME 10 Monitoring

Profile 5-20Add Scheduled Job 6-90Change Backup Server Registration

Details 6-44Change Monitor Server Registration

Details 6-63Create Indicator Collection 5-13Create Profile 5-10Create Profile Manager 5-7

Customize Monitoring Schedule Restrictions 5-40

Delete Icons from server collection warning 6-79

Delete Objects? 6-79Desktop Navigator 1-9Distribute Profile 6-88, 6-92Edit Default Policies 5-43Edit Monitor 5-24, 5-25, 5-30,

5-36File Browser 3-4, 7-18Install Product 3-6, 7-17Monitoring Schedule Restrictions 5-39Product Install 7-20

completion message 3-11, 7-20list of install operations 3-10

Register Monitor Server 4-21Register Sybase SQL Server 4-12Select Indicator Collection 5-18Set Managed Resources 4-8Set Monitoring Schedule 5-33, 5-34,

5-37, 5-38Set Notice Groups 4-4Shutdown Server

with ’nowait’ 6-18, 6-53, 6-73with ’wait’ 6-18, 6-53, 6-73

Start Server Confirmation 6-16, 6-51, 6-70

Subscribers 6-82Distribute Profile dialog 6-88, 6-92distributing file packages, topology server

7-34distributing monitoring collection

profiles 6-84distributing monitoring profiles

from the command line 6-93from the Tivoli desktop 6-85

distributing Sentry profiles 7-35


EEdit Default Policies dialog 5-43Edit Monitor dialog 5-24, 5-36

example 5-30response level options 5-25

endpointsdatabase 1-4

detailed states 6-30general states 6-29managing 6-24SybaseDatabase icon 1-6

definition 1-4determining

which monitors are running 6-95which monitors were distributed

6-94servers 1-4

SybaseBackupServer icon 1-5SybaseDataServer icon 1-5SybaseMonitorServer icon 1-6

subscribing to profile managers 6-80SybaseBackupServer

detailed states 6-56general states 6-55managing 6-40

SybaseMonitorServerdetailed states 6-76general states 6-75managing 6-59

enginesicon 1-6instances 1-4

ESMSentry.baroc event class 4-27event class structures 4-27

definition 4-27ESMSentry.baroc class 4-27M7SybaseDatabase.baroc class 4-28M7SybaseServer.baroc class 4-28table of class names for events 4-28

event filters 4-35Event Group Message Viewer window 6-98events

sending to the TEC 5-29viewing in the TEC 6-96extensions

TEC 1-1Tivoli Distributed Monitoring 1-1Tivoli Framework 1-1

FFile Browser dialog 3-4, 7-18

GGEM - Log window 7-45general states

Sybase Adaptive Servers 6-20Sybase Backup Servers 6-55Sybase Monitor Servers 6-75SybaseDatabase endpoints 6-29SybaseEngine instances 6-36

graphical user interface (GUI)See Tivoli desktop

group ID, setting for a profile 5-42GUI, See Tivoli desktop

Hheartbeat events, definition 7-2


Iicons

Administrators object 4-3distributed profile 1-4indicator collection 5-14policy region, Open... option 6-3profile 5-11profile manager 5-8Subscriber, NORMAL state 6-83Sybase aggregate 7-4SybaseBackupServer

Check State option 6-58NORMAL state 6-51, 6-55Open... option 6-41Properties... option 6-46Registration... option 6-44Shutdown Server option

With ’nowait’ 6-53With ’wait’ 6-53

SHUTDOWN state 6-54, 6-55Start Server option 6-50SUSPECT state 6-55View Log... option 6-48

SybaseBackupServer component 7-6SybaseBackupServer endpoint 1-5SybaseDatabase

Check State option 6-33NORMAL state 6-30Open... option 6-26Properites... option 6-28SHUTDOWN state 6-30SUSPECT state 6-30

SybaseDatabase component 7-6SybaseDatabase endpoint 1-6SybaseDataServer

Check State option 6-23NORMAL state 6-17, 6-20Properties... option 6-10Shutdown Server -> With ’nowait’

option 6-18

Shutdown Server -> With ’wait’ option 6-18

SHUTDOWN state 6-20Start Server -> Multi-User mode

option 6-16Start Server -> Single User mode

option 6-16SUSPECT state 6-20View Log... option 6-13

SybaseDataServer aggregate 7-5SybaseDataServer endpoint 1-5SybaseEngine

Check State option 6-39NORMAL state 6-36Properties... option 6-35SHUTDOWN state 6-36SUSPECT state 6-36

SybaseEngine component 7-6SybaseEngine instance 1-6SybaseMonitorServer

Check State option 6-78NORMAL state 6-75Open... option 6-60Properties... option 6-65Registration... option 6-63Shutdown Server option



SybaseMonitorServer endpoint 1-6In Create, detailed state

SybaseEngine instance 6-37In Destroy, detailed state

SybaseEngine instance 6-37


indicator collectionsadding to policy regions 5-12associating with profiles 5-15icon 5-14

initiating discover of Sybase componentstopology server 7-28

Install Product dialog 3-6, 7-17installation prerequisites


installingfrom the command line

example 3-13winstall command 3-12

Tivoli Manager for Sybase 3-1, 3-2from the command line 3-12from the Tivoli desktop 3-3procedure 3-2

Tivoli Manager for Sybase - Distributed Monitoring, CLI example 3-13

Tivoli Manager for Sybase - Framework, CLI example 3-13

Tivoli Manager for Sybase GEM Instrumentation 7-12, 7-15

instances, SybaseEnginedetailed states 6-37general states 6-36managing 6-34icon 1-6

instrumentationunderstanding policy regions 7-7understanding profile managers 7-7understanding profiles 7-7understanding task libraries 7-7understanding instrumented

components 7-3modeled from Sybase

resources 7-3SybaseBackupServer 7-3SybaseDatabase 7-3SybaseDataServer 7-3

SybaseEngine 7-3SybaseMonitorServer 7-3

integrating with the TECcreating a new rule base 4-32importing events 4-32creating event filters 4-35description 4-26event class structures

definition 4-27ESMSentry.baroc class 4-27M7SybaseDatabase.baroc

class 4-28M7SysbaseServer.baroc class 4-28table of class names for events 4-28

importing event classes into an existing rule base 4-34

manually configuring the TECdescription 4-31procedure 4-32

overview of the TEC 4-26rule base, definition 4-30

JJava Development Kit (JDK)

configuringon UNIX platforms 7-22on w32-ix86 platforms 7-22

Java Runtime Environment (JRE), configuring Tivoli Manager for Sybase GEM Instrumentation 7-23

Lloading sybase.pkg file 7-26Log to file, monitoring response action 5-28


MM7SybaseDatabase.baroc event class 4-28M7SybaseServer.baroc event class 4-28managed resources

adding from command line 4-9adding from Tivoli desktop 4-7definition 4-6removing from the command line 4-9removing from the Tivoli desktop 4-7SybaseDataServer 4-6

managingobjects in Sybase Data Server collections

running Check State option 6-32, 6-38, 6-57, 6-77

SybaseBackupServer endpoints 6-40

SybaseDatabase endpoints 6-24SybaseEngine instances 6-34SybaseMonitorServer endpoints

6-59Sybase Adaptive Servers 6-2

changing registration details 6-6checking states 6-20opening collections 6-2running Check State option 6-22shutting down 6-17starting 6-15updating states 6-22viewing error log contents 6-12viewing properties 6-9

manually initiating discover of Sybase components 7-33

Middleware/DB branch, top level topology console view 7-4

Middleware/DB/Sybase branch, second level topology console view 7-5

Middleware/DB/Sybase/JANE branch, third-level topology console view 7-6

monitor definitions 5-2monitoring collection

distributing profile 6-84monitoring collections

distributing monitors 1-7distributing profiles 6-85SybaseDatabase 1-1SybaseServer 1-1

monitoring profilesdefinition 5-2distributing


overview of monitoring 5-2setting up

authorization roles 5-4from the command line 5-45from the Tivoli desktop 5-5guidelines 5-2introduction 5-1

Monitoring Schedule Restrictions dialog 5-39

monitorsadding to profiles 5-19definition 5-2determining

which are running at an endpoint 6-95

which were distributed to an endpoint 6-94

distributing from collections 1-7overview of monitoring 5-2saving profiles 5-44scheduling

description 5-31restricting schedules 5-38setting default schedules for

profiles 5-32setting individual schedules for

individual monitors 5-35


setting upfrom the command line 5-45from the Tivoli desktop 5-5

specifying response levels 5-23SybaseDatabase collection 1-1, 1-7SybaseServer collection 1-1, 1-7understanding 7-10using Tivoli Manager for Sybase GEM

Instrumentation 7-39

Nnavigating to Sybase components,

topology console 7-42No More Connections, detailed state

Sybase Adaptive Servers 6-21SybaseDataServer endpoints 6-21

NORMAL stateSubscriber icon 6-83Sybase Backup Servers 6-55SybaseDatabase icon 6-30SybaseDataServer icon 6-20SybaseEngine icon 6-36SybaseMonitorServer icon 6-71, 6-75

normal, monitor response level 5-26notice groups

SentryStatus 4-2subscribing 4-2Sybase Sentry 4-2Sybase SQL Server Management 4-2

Oodadmin command, examples 7-22Offline, detailed state

SybaseDatabase endpoints 6-30SybaseEngine instance 6-37

Online, detailed stateSybaseDatabase endpoints 6-31SybaseEngine instance 6-37

openingSybase Data Server collection 6-2Sybase Database collection 6-24Sybase Monitor Server collection 6-59SybaseBackupServer collection 6-40

overviewchart of setup procedures 2-1monitoring 5-2Tivoli GEM Instrumentation 7-2Tivoli Manager for Sybase 1-1

PPolicy Region window 4-7, 6-4, 7-21

Create -> Indicator Collection option 5-12

Create -> Profile Manager option 5-6Create -> SybaseDataServer option 4-11Edit -> Delete option 6-79Properties -> Managed Resources...

option 4-7Register Monitor Server... option 4-20

policy regionsadding indicator collections 5-12adding profile managers and profiles

5-6icon, Open... option 6-3managed resources

adding SybaseDataServer 4-6definition 4-6

Popup, monitoring response action 5-27preparing to install Tivoli Manager for Sybase

GEM Instrumentation 7-12procedures

adding managed resource types 4-7adding SybaseDataServer managed

resource type 4-6


chart for setting up Tivoli Manager for Sybase 2-1

installing, Tivoli Manager for Sybase 3-2

integrating with the TECevent class structures 4-27manually configuring the TEC 4-31overview 4-26rule base, definition 4-30

registeringSybase Adaptive Servers 4-10Sybase Backup Servers 4-10Sybase Monitor Servers 4-19

removing managed resource types 4-7setting up monitoring profiles

authorization roles 5-4from the command line 5-45from the Tivoli desktop 5-5guidelines 5-2introduction 5-1overview of monitoring 5-2

settng up Tivoli Manager for Sybase GEM Instrumentation 7-1, 7-21

configuring 7-12installing 7-12

subscribing to notice groups 4-2using Tivoli Manager for Sybase 6-1

determining monitors distributed to endpoints 6-94running at endpoints 6-95

distributing monitoring collection profiles 6-84

managing objects in Sybase Data Server

collections 6-24Sybase Adaptive Servers 6-2

subscribing endpoints to profile managers 6-80

viewing events in the TEC 6-96

using Tivoli Manager for Sybase GEM Instrumentation 7-1

Product Install dialogcompletion message 3-11, 7-20list of install operations 3-10, 7-20

Profile Manager window 5-9, 6-85Create -> Profile option 5-10Profile Manager -> Subscribers... option

6-81profile managers

adding subscribersfrom the command line 6-84from the Tivoli desktop 6-80

adding to a policy region 5-6icon 5-8subscribing endpoints 6-80

profilesadding monitors 5-19adding to a policy region 5-6associating indicator collections 5-15icon 5-11saving 5-44setting up

default schedules 5-32guidelines 5-2user and group IDs 5-42

RRead Only, detailed state

SybaseDatabase endpoints 6-30Register Monitor Server dialog 4-21

example 4-23Register Sybase SQL Server dialog 4-12

example 4-15registering

Sybase Adaptive Serverdescription 4-10from the command line 4-16from the Tivoli desktop 4-11


Sybase Backup Server 4-10Sybase Monitor Servers

description 4-19from the command line 4-24from the Tivoli desktop 4-20

removingmanaged resource types 4-7objects from Sybase Data Server

collection 6-79response levels

See also actions and trigger whendefinition 5-23list 5-26specifying 5-23

restricting a schedule 5-38Root administrator, subscribing to

notice groups 4-2rule base, definition 4-30Run program, monitoring response

action 5-28running Check State option

SybaseDataServer icon 6-22SybaseBackupServer icon 6-57SybaseDatabase icon 6-32SybaseEngine icon 6-38SybaseMonitorServer icon 6-77

Ssaving profiles 5-44scheduling monitors

description 5-31restricting schedules 5-38setting

default schedules for profiles 5-32individual schedules for individual

monitors 5-35Select Indicator Collection dialog 5-18Send E-mail to, monitoring response

action 5-27

Send Enterprise Console event, monitoring response action 5-28

Send Tivili Notice, monitoring response action 5-27

sending events to the TEC 5-29senior, Tivoli authorization role 1-3SentryStatus notice group 4-2Set Managed Resources dialog 4-8Set Monitoring Schedule dialog 5-33,

5-34, 5-37, 5-38Set Notice Groups dialog 4-4setting up

monitoring profilesauthorization roles 5-4from the command line 5-45from the Tivoli desktop 5-5adding

indicator collections 5-12monitors to profiles 5-19profile managers and profiles

5-6associating indicator collections with

profiles 5-15saving profiles 5-44scheduling monitors 5-31sending events to the TEC 5-29setting user and group IDs profiles

5-42specifying response levels 5-23guidelines 5-2introduction 5-1overview of monitoring 5-2

Tivoli Manager for Sybase GEM Instrumentation 7-1, 7-21

task libraries 7-21user and group IDs for profiles 5-42


setupadding managed resource types 4-7adding SybaseDataServer managed

resource type 4-6chart of procedures 2-1integrating with the TEC 4-26removing managed resource types 4-7setting up monitoring profiles 5-1setting up Tivoli Manager for Sybase

GEM Instrumentation 7-21subscribing to notice groups 4-2

severe, monitor response level 5-26Shutdown Server dialog

with ’nowait’ 6-18, 6-53, 6-73with ’wait’ 6-18, 6-53, 6-73

SHUTDOWN stateSybaseBackupServer icon 6-54SybaseDatabase icon 6-30SybaseDataServer icon 6-20SybaseEngine icon 6-36SybaseMonitorServer icon 6-70,

6-74, 6-75Shutdown, detailed state

Sybase Adaptive Servers 6-22Sybase Backup Servers 6-56Sybase Monitor Servers 6-76SybaseDataServer endpoints 6-22

shutting downSybase Adaptive Servers 6-17Sybase Backup Servers 6-52Sybase Monitor Servers 6-71

Single User, detailed stateSybaseDatabase endpoints 6-30

software requirements 3-1specifying response levels 5-23

See also actions and trigger whenlist 5-26

sregmonsvr commandexample 4-26syntax 4-25

sregsqlsvr commandexample 4-19syntax 4-17

Start Server Confirmation dialog 6-16, 6-51, 6-70

startingSybase Adaptive Servers 6-15Sybase Backup Servers 6-49Sybase Monitor Servers 6-68

starting a component taskTivoli Manager for Sybase GEM

Instrumentation 7-45Subscriber icon

NORMAL state 6-83subscribers

adding to profile managersfrom the command line 6-84from the Tivoli desktop 6-80

Subscribers dialog 6-82subscribing endpoints to profile managers

6-80subscribing managed nodes

topolgy serverTivoli Manager for Sybase GEM

Instrumentation 7-34subscribing Sybase resources


subscribing to notice groups 4-2super, Tivoli authorization role 1-3SUSPECT state

Sybase Backup Servers 6-55SybaseDatabase icon 6-30SybaseDataServer icon 6-20SybaseEngine

icon 6-36SybaseMonitorServer icon 6-75

Suspect, detailed stateSybase Adaptive Servers 6-21Sybase Backup Servers 6-56Sybase Monitor Servers 6-76


SybaseDatabase endpoints 6-30SybaseDataServer endpoints 6-21

Sybase Adaptive Serversauthorization roles 1-3changing registration details 6-6checking states 6-20


managing 6-2objects on the Tivoli desktop 1-4registering


running Check State option 6-22shutting down 6-17starting 6-15SybaseDataServer icon 1-5updating states 6-22viewing error log contents 6-12viewing properties 6-9

Sybase aggregate icon 7-4Sybase Backup Server collection window

6-42Sybase Backup Server Error Log window

6-49Sybase Backup Server Properties window

6-47Sybase Backup Servers

changing registration details 6-42checking states 6-55


registering 4-10shutting down 6-52starting 6-49SybaseBackupServer icon 1-5updating states 6-57viewing error log contents 6-47viewing properties 6-45

Sybase components

Tivoli Manager for Sybase GEM Instrumentation

initiating discovery 7-28sybase components

discovering 7-12Sybase Data Server collection

managing objects 6-24opening 6-2removing objects 6-79

Sybase Data Server collection window 1-7, 4-24, 6-5

Edit -> Delete option 6-79Sybase Data Server Error Log window 6-14Sybase Data Server Properties window 6-11Sybase Data Servers

See Sybase Adaptive ServersSybase Database collection

opening 6-24Sybase Database collection window 6-27Sybase Database Properties window 6-29Sybase Engine Properties window 6-35Sybase Monitor Server collection

opening 6-59Sybase Monitor Server collection window

6-61Sybase Monitor Server Error Log window

6-68Sybase Monitor Server Properties window

6-65Sybase Monitor Servers

changing registration details 6-61checking states 6-75

general states 6-75detailed states 6-76general states 6-75registering


shutting down 6-71


starting 6-68SybaseMonitorServer icon 1-6updating states 6-77viewing error log contents 6-66viewing properties 6-64

Sybase Sentry notice group 4-2Sybase SQL Server Management notice

group 4-2Sybase SQL Servers

See Sybase Adaptive Serverssybase.pkg file


configuring topology servers 7-24loading 7-26

sybase_dba, Tivoli Manager for Sybase authorization role 1-3

sybase_monitor, Tivoli Manager for Sybase authorization role 1-3

sybase_user, Tivoli Manager for Sybase authorization role 1-3

SybaseBackupServerendpoint 1-5

detailed states 6-56managing 6-40

icon 1-5Check State option 6-58NORMAL state 6-51, 6-55Open... option 6-41Properties... option 6-46Registration... option 6-44Shutdown Server option



opening a collection 6-40SybaseBackupServer collection

opening 6-40SybaseBaseEvent Event Group window

6-96SybaseBaseEvent Group Message List

window 6-97SybaseDatabase

endpoint 1-6checking states 6-29


managing 6-24updating states 6-31viewing properties 6-27

icon 1-6Check State option 6-33NORMAL state 6-30Open... option 6-26Properties... option 6-28SHUTDOWN state 6-30SUSPECT state 6-30

SybaseDatabase monitoring collection 1-1distributing monitors 1-7

SybaseDataServerendpoint 1-5icon 1-5

Check State option 6-23NORMAL state 6-17, 6-20Properties... option 6-10Register Monitor Server... option

4-20Shutdown Server -> With ’nowait’

option 6-18Shutdown Server -> With ’wait’

option 6-18SHUTDOWN state 6-16, 6-19,

6-20Start Server -> Multi-User mode

option 6-16Start Server -> Single user mode


option 6-16SUSPECT state 6-20View Log... option 6-13

managed resource type 4-6SybaseDataServer aggregate

associated componentsSybaseBackupServer icon 7-6SybaseDatabase icon 7-6SybaseEngine icon 7-6

SybaseDataServer aggregate icon 7-5SybaseEngine

icon 1-6Check State option 6-39NORMAL state 6-36Properties... option 6-35SHUTDOWN state 6-36SUSPECT state 6-36

instance 1-6checking states 6-36detailed states 6-37managing 6-34updating states 6-38viewing properties 6-34

SybaseMonitorServerendpoint 1-6

managing 6-59icon 1-6

Check State option 6-78NORMAL state 6-71, 6-75Open... option 6-60Properties... option 6-65Registration... option 6-63Shutdown Server option


SHUTDOWN state 6-70, 6-74, 6-75

Start Server option 6-70SUSPECT state 6-75

View Log... option 6-67SybaseServer monitoring collection 1-1

distributing monitors 1-7

Ttask libraries


tasksstarting


understanding 7-8using


Tasks... , monitoring response action 5-27tear-away log

usingTivoli Manager for Sybase GEM

Instrumentation 7-45TEC

configuring manuallydescription 4-31procedure 4-32

extensions 1-1importing Tivoli Manager for Sybase

events 5-29integrating with Tivoli Manager for

Sybase 4-26creating a new rule base and

importing events 4-32creating event filters 4-35event class structures 4-27importing event classes into an

existing rule base 4-34rule base, definition 4-30

overview 4-26viewing events 6-96


Tivoli administratorsAdministrators icon 4-3definition 1-2Root administrator 4-2

Tivoli authorization rolesadmin 1-3See also authorization roles, Sybase

Adaptive Server, and Tivoli Manager for Sybase

senior 1-3super 1-3user 1-3

Tivoli desktopadding subscribers to profile managers

6-80changing registration details


distributing monitoring profiles 6-85endpoints 1-4icons 1-4installing


instances 1-4objects 1-4opening

Sybase Data Server collection 6-2Sybase Database collection 6-24

opening Sybase Monitor Server collection 6-59

opening SybaseBackupServer collection 6-40

removing objectsSybase Data Server collection

6-79resources 1-4running Check State option

Sybase Adaptive Servers 6-22SybaseBackupServer icon 6-57

SybaseDatabase icon 6-32SybaseEngine icon 6-38SybaseMonitorServer icon 6-77

See also GUIsetting up


setting up monitoring profiles 5-5setup procedures

adding managed resource types 4-7

adding SybaseDataServer managed resource type 4-6

registering Sybase Adaptive Servers 4-11

registering Sybase Monitor Servers 4-20

removing managed resource types 4-7

subscribing to notice groups 4-2shutting down


startingSybase Adaptive Servers 6-15Sybase Backup Servers 6-49Sybase Monitor Servers 6-68

using the graphical user interface (GUI) 1-8

viewing error log contentsSybase Adaptive Servers 6-12Sybase Backup Servers 6-47Sybase Monitor Servers 6-66

viewing propertiesSybase Adaptive Servers 6-9Sybase Backup Servers 6-45Sybase Monitor Servers 6-64SybaseDatabase endpoint 6-27


SybaseEngine instance 6-34Tivoli Distributed Monitoring

extensions 1-1Tivoli Enterprise Console (TEC)

See TECTivoli Enterprise Manager (Tivoli GEM)

See Tivoli GEMTivoli Framework

extensions 1-1Tivoli GEM Instrumentation

discovering Sybase components 7-12overview 7-2understanding

instrumentation profile managers 7-7

instrumentation profiles 7-7instrumentation task libraries 7-7instrumented components 7-3monitors 7-10policy instrumentation policy

regions 7-7tasks 7-8topology console 7-3topology server 7-2

Tivoli GEM topology console windowStop option 7-44

Tivoli Global Enterprise Manager (Tivoli GEM)

See Tivoli GEMTivoli Global Enterprise Manager window

File -> Load New AMP... option 7-26Tivoli Management Regions (TMRs)


Tivoli Manager for Sybaseadding SybaseDataServer managed

resource typeadds SybaseDataServer icon on

Tivoli desktop 4-6adds SybaseDataServer to Create

menu 4-6

assigns default policy 4-6alerting administrators 1-1authorization roles

sybase_dba 1-3sybase_monitor 1-3sybase_user 1-3

chart of setup procedures 2-1determining

monitors distributed to endpoints 6-94

monitors running at endpoints 6-95


ESMSentry.baroc event class 4-27installing


integrating with the TEC 1-1, 4-26managing

objects in Sybase Data Server collections 6-24

Sybase Adaptive Servers 6-2overview 1-1registering servers 1-1removing managed resource types 4-7setting up monitoring profiles 5-1setting up Tivoli Manager for Sybase

GEM Instrumentation 7-21subscribing endpoints to profile

managers 6-80subscribing to notice groups 4-2user-defined monitoring sources 1-1using 6-1

command line interface (CLI) 1-8Desktop Navigator 1-8graphical user interface (GUI) 1-8monitoring collections 1-1Tivoli desktop 1-8


Tivoli GEM instrumentation 1-1using Tivoli Manager for Sybase GEM

Instrumentation 7-1viewing events in the TEC 6-96

Tivoli manager for Sybasesetting up Tivoli Manager for Sybase

GEM Instrumentation 7-1Tivoli Manager for Sybase - Distributed

MonitoringCLI installation example 3-13

Tivoli Manager for Sybase - FrameworkCLI installation example 3-13


administrators 7-13configuring 7-12

topology servers 7-24deleting components from views 7-48installation 7-15installation prerequisites 7-13installing 7-12


navigating to Sybase componentstopology console 7-42

preparing to install 7-12setting up 7-1

configuring Java Development Kit (JDK) 7-22

configuring Java Runtime Environment (JRE) 7-23

from the Tivoli desktop 7-21starting a component task 7-45Tivoli Management Regions (TMRs)

7-12using 7-1

monitors 7-39tasks 7-40tear-away log 7-45

viewing monitor status 7-47TME 10 Distributed Monitoring

See Tivoli Distributed MonitoringTME 10 Distributed Monitoring Profile

Properties window 5-16, 5-19, 5-42

Edit -> Set Default Schedule... option 5-33

Edit -> Set user & Group ID... option 5-43

example 5-32Monitoring -> Select Indicator Collection

option 5-17Profile -> Close option 6-93Profile -> Distribute option 6-87Profile -> Save option 5-44

TME 10 Enterprise Console window 6-96TME 10 Framework

See Tivoli FrameworkTME Desktop for Administrator window

3-3, 6-3Desktop menu

Install -> Install Product... option 3-3

Install -> Install Product... option 7-16topology console

definition 7-2manual aggregation 7-3navigating to Sybase components


understanding 7-3topology console view

top-levelMiddleware/DB branch 7-4

topology console viewssecond level

associated SybaseDataServer aggregate icons 7-5

Middleware/DB/Sybase branch 7-5

third levelMiddleware/DB/Sybase/JANE


branch 7-6relationships between components

7-6top level

Middleware/DB branch 7-4topology server

configuringTivoli Manager for Sybase GEM

Instrumentation 7-24definition 7-2understanding 7-2

trigger when, monitoring response option 5-26

Uunderstanding

instrumentationpolicy regions 7-7profile managers 7-7profiles 7-7task libraries 7-7

instrumented components 7-3topology console 7-3topology server 7-2

UNIX platformsconfigure JDK

edit odenv.txt file 7-22updating states

Sybase Adaptive Servers 6-22Sybase Backup Servers 6-57Sybase Monitor Servers 6-77SybaseDatabase endpoints 6-31SybaseEngine instances 6-38

user ID, setting for a profile 5-42user, Tivoli authorization role 1-3using

command line interface (CLI) 1-8Desktop Navigator 1-8graphical user interface (GUI) 1-8

tear-away logTivoli Manager for Sybase GEM

Instrumentation 7-45Tivoli desktop 1-8Tivoli Manager for Sybase 6-1

determining monitors distributed to endpoints 6-94

determining monitors running at endpoints 6-95


managing objects in Sybase Data Server collections 6-24

managing Sybase Adaptive Servers 6-2

subscribing endpoints to profile managers 6-80

viewing events in the TEC 6-96Tivoli Manager for Sybase GEM

Instrumentation 7-1monitors 7-39tasks 7-40

Vviewing error log contents


viewing events in the TEC 6-96viewing monitor status


viewing propertiesSybase Adaptive Servers 6-9Sybase Backup Servers 6-45Sybase Monitor Servers 6-64SybaseDatabase endpoint 6-27SybaseEngine instance 6-34


Ww32-ix86 platforms

configuring JDKSettings -> Control Panel -> System

-> Environment option 7-22warning, monitor response level 5-26wcomprules command, examples 4-34,

4-35wcprb command, example 4-33wcrtprf command, example 5-45wcrtprfmgr command, example 5-45wcrtrb command, example 4-33wcrtsntcoll command, example 5-45wdistrib command, example 6-93wgetpr command 4-9wimprbclass command, examples 4-33,

4-35windows

Administrators collection 4-3Event Group Message Viewer 6-98GEM - Log 7-45Policy Region 4-7, 5-6, 6-4, 7-21Profile Manager 5-9, 6-81, 6-85Sybase Backup Server collection 6-42Sybase Backup Server Error Log 6-49Sybase Backup Server Properties 6-47Sybase Data Server 6-26Sybase Data Server collection 1-7,

4-24, 6-5Sybase Data Server Error Log 6-14Sybase Data Server Properties 6-11Sybase Database collection 6-27Sybase Database Properties 6-29Sybase Engine Properties 6-35Sybase Monitor Server collection 6-61Sybase Monitor Server Error Log 6-68Sybase Monitor Server Properties 6-65SybaseBaseEvent Event Group 6-96SybaseBaseEvent Group Message List

6-97

Tivoli GEM topology console 7-44TME 10 Distributed Monitoring Profile

Properties 5-16, 6-86, 6-93TME 10 Enterprise Console 6-96TME Desktop for Administrator 3-3,

6-3, 7-16winstall command 3-12, 7-21

examplesinstalling Tivoli Manager for Sybase

- Distributed Monitoring 3-13installing Tivoli Manager for Sybase

- Framework 3-13wloadrb command, examples 4-34, 4-35wlookup command, example 4-33wsetpr command 4-9wsetpr command, example 5-45wstartesvr command, examples 4-34, 4-35wstopesvr command, examples 4-34, 4-35wsub command

example 6-84