Tivoli/Plus for Scopus User’s Guide - IBMpublib.boulder.ibm.com/tividd/td/SCO/Scopus/en_US/PDF/Scopus.pdf · Tivoli/Plus for Scopus User’s Guide v Typeface Conventions The guide

Tivoli/Plus for ScopusUser’s Guide

July 1,1996

Tivoli/Plus for Scopus User’s Guide (July 1, 1996)Copyright NoticeCopyright © 1991–1996 by Tivoli Systems Inc., including this documentation and all software. All rightsreserved. May only be used pursuant to a Tivoli Systems Incorporated Software License Agreement. Nopart of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, ortranslated 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 Inc. Thisdocument was prepared by Tivoli Systems Inc., and was printed in the United States of America.

All software has been developed at private expense and is commercially available at published prices.Federal Acquisition Regulation (FAR) or Defense Federal Acquisition Regulation Supplement (DFARS)RESTRICTED RIGHTS APPLY TO U.S. GOVERNMENT USE, as applicable:

Restricted Rights Notice

SOFTWARE supplied to any unit or agency of the United States Government otherthan the DOD shall be governed by clause 52.227-19(o) of the FAR (or any successorregulations) or, in the case of NASA, in clause 45 CFR 1827.405(a) (or any successorregulations) and, in any such case, the United States Government acquires only“restricted rights” in such SOFTWARE.

Restricted Rights Legend

SOFTWARE supplied to the Department of Defense (“DOD”) is classified as “Com-mercial Software”, and the United States Government acquires only “restricted rights”in SOFTWARE, as such rights are defined in clause 252.227.7013(c)(1)(ii) of theDFARS (or any successor regulations).

Tivoli Systems Inc., 9442 Capital of Texas Hwy North, Arboretum Plaza One, Suite 500, Austin, TX78759

Associated Copyrights

Portions copyright © 1989 by the Eric C. Cooper, Carnegie Mellon University. All rights reserved.Portions copyright © 1990, 1991 by the University of Utah and the Center for Software Science (CSS).All rights reserved.Portions copyright © 1989 by Digital Equipment Corporation. All rights reserved.Portions copyright © 1989, 1990, 1991 by Massachusetts Institute of Technology. All rights reserved.Portions copyright © 1986 by University of Toronto. All rights reserved.Portions copyright © 1989, 1990, 1991 by Larry Wall. All rights reserved.Portions copyright © 1990 by Alfalfa Software Incorporated.All rights reserved.Portions copyright © 1992, 1993 by Free Software Foundation, Inc. All rights reserved.Portions copyright © 1982, 1986, 1991 by Regents of the University of California. All rights reserved.Portions copyright © 1988, 1989, 1991 by Jef Poskanzer. All rights reserved.Portions copyright © 1991, 1992 by RSA Data Security, Inc. All rights reserved.Portions copyright © 1982, 1988, 1989 by Walter Tichy. All rights reserved.Portions copyright © 1990, 1991 by Paul Eggert. All rights reserved.Portions copyright © 1990, 1992 by Hewlett-Packard Company. All rights reserved.Portions copyright © 1989, 1993 by Jim Frost. All rights reserved.Portions copyright © 1990 by GROUPE BULL. All rights reserved.Portions copyright © 1991-1994 by JSB Computer Systems Ltd. All rights reserved.Portions copyright © 1995 by Intel Corporation. All rights reserved.Portions copyright © by DataFocus Incorporated. All rights reserved.Portions copyright © 1992-1994 by Michael A Cooper. All rights reserved.

Trademarks

Tivoli Management Environment, Tivoli Management Platform, Tivoli Management Framework, TivoliApplication Service, Tivoli/ADE, Tivoli/Admin, Tivoli/AEF, Tivoli/Courier, Tivoli/EIF, Tivoli/EnterpriseConsole, Tivoli/FSM, Tivoli/Inventory, Tivoli/net.Commander, Tivoli/Plus, Tivoli/Print, Tivoli/Sentry,Tivoli/UserLink, Tivoli/Workload, and TME are trademarks of Tivoli Systems Inc.

Product and company names mentioned in this document are trademarks or registered trademarks of theirrespective manufacturers.

Patent pending.

Tivoli/Plus for Scopus User’s Guide i

Tivoli/Plus for ScopusUser’s Guide

Preface................................................................................................................... iii

Who Should Read This Guide...................................................................... iii

Prerequisite and Related Documents............................................................ iv

What This Guide Contains ........................................................................... iv

Typeface Conventions................................................................................... v

Platform-Specific Information ...................................................................... v

Contacting Customer Support ..................................................................... vii

Chapter 1—Getting Started with Tivoli/Plus for ScopusInstallation Requirements ...................................................................................1-2

License Key................................................................................................1-2

Software Requirements ..............................................................................1-2

Hardware Requirements .............................................................................1-3

Installing from the Desktop ................................................................................1-4

Installing from the Command Line...................................................................1-14

Tivoli/Plus Icons ...............................................................................................1-14

Tivoli/Plus Unique Features .............................................................................1-15

Starting a Tivoli/Plus Module...........................................................................1-16

Launching the Scopus Application ...................................................................1-19

Chapter 2—Software Distribution for ScopusConfiguring Tivoli/Courier File Packages..........................................................2-2

File Packages for a Windows Platform ......................................................2-3

File Packages for a UNIX Platform ...........................................................2-6

Installing Scopus...............................................................................................2-11

Installing Scopus on All Configured Platforms .......................................2-12

Installing Scopus on a Single Platform ....................................................2-13

ii Version 1.0

Chapter 3—Resource MonitoringUsing Tivoli/Plus for Scopus Monitors .............................................................. 3-2

Viewing the Status of Monitored Resources ...................................................... 3-5

Monitored Resources .......................................................................................... 3-6

Host Status ................................................................................................. 3-7

InformTEAM Daemon Status .................................................................... 3-8

RemoteTEAM Daemon Status................................................................... 3-9

SCOPUSRTD Daemonct Status .............................................................. 3-10

Available Swap Space.............................................................................. 3-11

LogFile Size ............................................................................................. 3-12

Mail Queue Length .................................................................................. 3-13

Kilobytes Paged Out ................................................................................ 3-14

Chapter 4—Enterprise Event ManagementSetting Up the Tivoli/Enterprise Console........................................................... 4-2

Events and Rules................................................................................................. 4-5

Event Correlation ....................................................................................... 4-5

Tivoli/Sentry Events................................................................................... 4-5

Scopus Custom Monitor Events............................................................... 4-11

Setting Up Scopus Trouble Tickets .................................................................. 4-14

Closing Scopus Trouble Tickets .............................................................. 4-14

Chapter 5—Tasks and Jobs for ScopusTivoli/Plus for Scopus Jobs ................................................................................ 5-2

Running a Scopus Job and Saving the Output.................................................... 5-4

Modifying a Scopus Job ..................................................................................... 5-5

Modifying for All Future Executions of the Job........................................ 5-5

Modifying for a Single Execution of the Job ............................................. 5-6

Preface

Tivoli/Plus for Scopus User’s Guide iii

PrefaceTheTivoli/Plus for Scopus User’s Guide describes specific featuresand procedures for using the Tivoli/PlusTM for Scopus module. Thismodule was jointly developed by Tivoli/Systems Inc. and ScopusTechnology, Inc. and provides an integration of the Scopus productwith the Tivoli Management EnvironmentTM (TME). Through thisintegration, the Tivoli/Plus for Scopus module delivers the systemmanagement capabilities of TME for specific use with Scopus. UsingTivoli/Plus for Scopus, the Scopus application can be managed acrossa multi-platform network.

Tivoli/Plus provides different modules for integrating differentproduction control applications with the Tivoli ManagementEnvironment. Since all Tivoli/Plus modules have a common interface,a system administrator can implement the system managementcapabilities of the TME with various production control applicationswhile enjoying the simplicity of a common interface. The addition ofTivoli/CourierTM, Tivoli/SentryTM, and the Tivoli/Enterprise ConsoleTM

provides additional management capabilities in the areas of clientinstallation, resource monitoring, and event correlation.

Who Should Read This GuideThis guide is for system administrators who use the Tivoli/Plus forScopus module to manage the operation of the Scopus help deskapplication. Readers of this guide should be familiar with the TivoliManagement Environment, the Scopus application, and concepts suchas directories, files, and symbolic links. Readers of this guide shouldalso be familiar with the operating systems running on the machineson which they will be using the Tivoli/Plus module, TME, and theScopus application.

Note: All references to “Sentry” in this guide refer tothe Tivoli/Sentry product or its components.

Preface

iv Version 1.0

Prerequisite and Related DocumentsThe information in theTivoli/Plus for Scopus User’s Guidecomplements information presented in theTivoli ManagementPlatform User’s Guideand the Tivoli/Plus User’s Guide. You must befamiliar with Tivoli/Plus before you can effectively use a specificTivoli/Plus module. You should also be familiar with thedocumentation for the Scopus application.

You should be familiar with these guides before attempting to use theinformation in theTivoli/Plus for Scopus User’s Guide.

What This Guide ContainsTheTivoli/Plus for Scopus User’s Guide contains the followingsections:

■ Chapter 1, "Getting Started with Tivoli/Plus for Scopus"Contains the installation requirements and procedures forinstalling Tivoli/Plus for Scopus. This chapter also containsinformation about Tivoli/Plus icons, features unique toTivoli/Plus, and launching the Scopus application.

■ Chapter 2, "Software Distribution for Scopus"Describes how to set up Tivoli/Courier to be used withTivoli/Plus for Scopus for distributing and installing the Scopusapplication across a network.

■ Chapter 3, "Resource Monitoring"Describes how Tivoli/Sentry may be used with Tivoli/Plus forScopus to monitor Scopus resources in order to detect andprevent system problems.

■ Chapter 4, "Enterprise Event Management"Describes how to set up the Tivoli/Enterprise Console to be usedwith Tivoli/Plus for Scopus to provide event management. Thischapter also contains a description of the events and rules specificto Tivoli/Plus for Scopus.

■ Chapter 5, "Tasks and Jobs for Scopus"Describes how to customize and run Scopus jobs and reports withTivoli/Plus for Scopus.

Preface

Tivoli/Plus for Scopus User’s Guide v

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

Bold Commands, keywords, file names, or otherinformation that you must use literally appear inbold.Names of windows, dialogs, and other controls alsoappear inbold.

Italics Variables and values that you must provide appear initalics.

Bold Italics New terms appear inbold italicsthe first time they areused.

Monospace Code examples appear in amonospace font.

This guide may include icons in the left margin. These icons providecontext for the discussion in the text or for performing a step within aprocedure. For example, if you start a procedure by double-clicking ona task icon, that icon appears in the left margin next to the first step. Ifthe fourth step of the procedure instructs you to open another icon, thaticon appears in the left margin next to the fourth step.

Platform-Specific InformationThe following markers are used to identify platform-specificinformation or procedures:

Icon Supported Platform

IBM RS/6000 series running AIX 3.2.5

IBM RS/6000 series running AIX 4.1

Data General AViiON series running DG/UX version5.4R3.00

IBM-compatible PCs 486 or higher running MS-DOS orPC-DOS 3.1 through 6.22

HP9000/700 and 800 series running HP-UX 9.00,HP/UX 9.01, HP/UX 9.03, and HP-UX 9.05

AIX 3.2.5

AIX 4.1

DG/UX

DOS

HP 9.x

Preface

vi Version 1.0

HP9000/700 and 800 series running HP-UX 10.0

Motorola 88K series running SVR4 version R40V4.2

NCR 3000 series running NCR UNIX SVR4 MP-RASRelease 2.02 and 2.03

IBM-compatible PCs 486 or higher running NovellNetWare 3.11, 3.12, or 4.0

IBM-compatible PCs 486 or higher running NEXTSTEPrelease 3.2

IBM-compatible PCs 486 or higher running MicrosoftWindows NT version 3.1, 3.5, or 3.5.1

IBM-compatible PCs 486 or higher running IBM OS/2version 2.0, 2.1, or Warp

DEC Alpha Generation system running DEC OSF/1 3.0or 3.2

Sun SPARC series running Solaris 2.3 or 2.4

Sun SPARC series running SunOS 4.1.2 or 4.1.3

All SVR4-based platforms, to include: NCR UNIXSVR4, DG/UX version 5.4R3.00, Motorola, Solaris, andUnixWare 2.0

IBM-compatible PC 486 or higher running NovellUnixWare 2.0

IBM-compatible PC 486 or higher running MicrosoftWindows 3.1, 3.11, or 3.11 for WorkGroups

Icon Supported Platform

HP 10.0

Motorola

NCR

NetWare

NEXT

NT

OS/2

OSF/1

Solaris

SunOS

SVR4

UnixWare

Windows

Preface

Tivoli/Plus for Scopus User’s Guide vii

Contacting Customer SupportWe are very interested in hearing from you about your experience withthe products in the Tivoli Management Environment. We welcomeyour suggestions for improvements.

If you encounter difficulties with any TME product, please contactyour customer support representative. To assist you, this sectionincludes the TME Problem Report form. You can use this form to faxproblem information to your support provider. Tivoli also includes thewsupport command. This command prompts you for probleminformation, which can be e-mailed to your support provider or savedto a text file. You can then print the saved file, and fax the resultingTME Problem Report form to your support provider.

Preface

viii Version 1.0

TME Problem Report

Name:

E-mail:

Company:

System Type:Operating System Rel:

Tivoli Product:

Problem On:

Priority:

3. Minor

Short Description (10 - 12 words):

Attempted Solutions:

Description / Error Messages:

Phone #:

Fax #:

TMR #:

Version:

Tivoli Server Tivoli Client

2. Major1. Critical

4. No Impact

Previous Call Tracking #:

Tivoli/Plus for Scopus User’s Guide 1–1

Getting S

tarted with

Tivoli/P

lus for Scopus

1Getting Started with Tivoli/Plus forScopus

The Tivoli/Plus for Scopus module provides an integration of theTivoli Management Environment with the Scopus help deskapplication. This integration allows centralized distribution andmanagement of the Scopus application across a multi-platformnetwork. This module provides the following features for managingthe Scopus application:

■ Icons for launching the Scopus application

■ Subscription lists for clients and servers

■ Τivoli/Courier file packages

■ Tivoli/Sentry monitors

■ Tivoli/Enterprise Console events and rule sets customized forScopus

■ Scopus-specific tasks and jobs

Note: The Tivoli/Courier, Tivoli/Sentry, and Tivoli/EnterpriseConsole applications must be installed and configured beforetheir correspondingTivoli/Plus feature is operational.

1

Installation Requirements

1–2 Version 1.0

Installation RequirementsBefore attempting to install Tivoli/Plus for Scopus into the TivoliManagement Environment, make certain you review the requirementsin this section.

In order for the Tivoli/Plus for Scopus module to function correctly, itmust be installed on the following machines:

■ The Tivoli server.

■ The Tivoli/Enterprise Console server (if there is one).

■ The Scopus server. This machine needs to be a Tivoli managednode.

License KeyYou must obtain a license key to use the Tivoli/Plus for Scopusmodule. You must complete and return the license request form thatcame with this software. Tivoli Customer Support will then provideyou with a license key for your module.

Software RequirementsYou must have a TME 2.5 installation up and running. Additionally,Scopus 3.6.1 should be installed before the Tivoli/Plus for Scopusmodule is installed, and the Scopus dataserver should also be up andrunning.

Tivoli/Plus for Scopus has features that use Tivoli/Courier,Tivoli/Sentry, and the Tivoli/Enterprise Console. If these applicationsare not installed, then the specific feature requiring these applicationswill not work. However, Tivoli/Plus for Scopus installation allows you

Activity Context Required Role

Installing Tivoli/Plus forScopus

TME install_product

Installation Requirements


Getting S

tarted with

Tivoli/P

lus for Scopus

to incrementally re-install those features if you buy the missingproducts at a later date.

Hardware RequirementsThe following table provides the client and server disk spacerequirements for Tivoli/Plus for Scopus. This space is in addition tothe space requirements for the management platform, the Tivoliapplication, and the Scopus help desk application.

Tivoli/Plus for Scopus is installed on the TME server, theTivoli/Enterprise Console server (if you have the Tivoli/EnterpriseConsole), and the Scopus master machines. The space requirementsare the same for all of these machines. The Tivoli/Plus for Scopusmodule uses platform-independent shell and Perl scripts, which is whythe module's requirements do not differ from platform to platform.

Platform Libraries Binaries Database Man PagesMessageCatalogs

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

AIX

HP-UX

Solaris

SunOS

Installing from the Desktop

1–4 Version 1.0

Installing from the DesktopUse the following steps to install Tivoli/Plus for Scopus from theTivoli desktop:

1. Select theInstall -> Install Product... option from theDesktopmenu



Getting S

tarted with

Tivoli/P

lus for Scopus

to display theInstall Product dialog.

If the Tivoli/Plus for Scopus module is listed in theSelectProduct to Install scrolling list, skip to step 3. If it is not listed,proceed to step 2.


1–6 Version 1.0

2. Press theSelect Media... button to display theFile Browserdialog.

TheFile Browser dialog enables you to identify or specify thepath to the installation media.

If you already know the path to the CD-ROM image

a. Enter the full path in thePath Name field.

b. Press theSet Path button to change to the specified directory.



Getting S

tarted with

Tivoli/P

lus for Scopus

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product dialog. The dialog nowcontains a list of products that are available for installation.

If you do not know the exact path to the CD-ROM image

a. From theHosts scrolling list, choose the host on which theinstall media is mounted. Choosing a host updates theDirectories scrolling list to show the directories of the hostyou chose.

b. From theDirectories scrolling list, choose the directorycontaining the install media.

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product dialog. The dialog nowcontains a list of products that are available for installation.


1–8 Version 1.0

3. Select the Tivoli/Plus for Scopus module from theSelectProduct to Install list.



Getting S

tarted with

Tivoli/P

lus for Scopus

4. Enter the information regarding your Scopus installationenvironment in theInstall Options dialog. The followingdescribes each of the fields on this dialog:

• Location of Scopus Distribution. Enter the path to theScopus base directory.

• Scopus Binaries Version No.Enter the Scopus binaryversion number.

• Scopus Binaries Database (syb10/ora7.1/syb4.9). Enter thedatabase type used.

• Scopus Login Name.Enter the Scopus user login name.

• Scopus Login Password.Enter the Scopus user loginpassword.

• Database Type(sybase/oracle).Enter the database typeused.

• Database Admin Login Name.Enter the databaseadministrator’s login name.

• Database Admin Login Password.Enter the databaseadministrator’s login password.

• Database Name.Enter the database name.

• Location of Oracle Installation.Enter the path to the Oracledirectory (for Oracle users only).

• Oracle DataServer Name. Enter the Oracle data servername (for Oracle users only).

• Location of Sybase Installation or Interface file.Enter thepath to the Sybase directory.

• Sybase DataServer Name.Enter the name of the Sybasedataserver (for Sybase users only).

• The Print Report method to be used for Print Task.Enterthe name to be executed when the Print Reports Task icon isselected.

Press theClosebutton when finished.


1–10 Version 1.0



Getting S

tarted with

Tivoli/P

lus for Scopus

5. To specify the clients on which the module will be installed, usethe arrow keys to move machine names between theClients toInstall On scrolling list and theAvailable Clients scrolling list.

By default, all machines in the current Tivoli Managed Region(TMR) are listed in theClients to Install On scrolling list. Tomove a machine name to theAvailable Clients list, choose oneor more clients from theClients to Install On scrolling list andpress the button. The chosen clients are moved from theClients to Install On scrolling list to theAvailable Clientsscrolling list.

6. Enter your license key for the Tivoli/Plus for Scopus module intheLicense Key field.

7. Press theInstall & Close button to install the module and closethe Install Product dialog

- OR -

Press theInstall button to install the module and keep theInstallProduct dialog open. You can then install Tivoli/Plus for Scopuson another set of clients or you can install another product.


1–12 Version 1.0

The installation process prompts you with aProduct Installdialog similar to the following example:

This dialog provides the list of operations that take place wheninstalling the software. This dialog also warns you of anyproblems that you may want to correct before you install theTivoli/Plus for Scopus module.



Getting S

tarted with

Tivoli/P

lus for Scopus

8. Press theContinue Install button to begin the installationprocess

—OR—

Press theCancel button to abort the installation process.

When the installation is complete, theProduct Install dialogdisplays a completion message similar to the following example.

9. Press theClose button when theProduct Install status dialogindicates that the installation is complete.

Completionmessage

Installing from the Command Line

1–14 Version 1.0

Installing from the Command LineUse thewinstall command to install the Tivoli/Plus for Scopusmodule. The following example is the syntax for thewinstallcommand and its parameters:

winstall -c cdrom_path -s installation_server \-i index_file -l license_key

where:

-c cdrom_path Specifies the path to the CD-ROM image.

-s installation serverSpecifies the server on which the product is to beinstalled.

-i index_file Specifies the index file from which the product is to beinstalled

-l license_key Specifies the license key for the product. Thisparameter is optional for installations following thefirst one.

See thewinstall command in theTivoli Management PlatformReference Manualfor more information.

Tivoli/Plus IconsAlthough the Tivoli/Plus for Scopus icons look like (traditional) TMEicons, their functionality has been altered slightly to provide a faster,more intuitive approach to navigating and deploying the module'sfeatures. In some cases, such as a Tivoli/Courier file package profile,menu items have been removed from the icon's pop-up menu to createa more "point and click" environment.

The Tivoli/Plus icons can be activated in either of two ways:

■ Opening or executing the icon by double-clicking on it with theleft mouse button. In many cases, double-clicking executes anactivity (such as a task) without opening another dialog layer.

■ Displaying the icon’s pull-down menu by pressing and holdingthe right mouse button.

Tivoli/Plus Unique Features


Getting S

tarted with

Tivoli/P

lus for Scopus

Generally, either method may be used to access a particular function.There are cases, however, where a particular function can only beaccessed by one of these methods.

The following icon represents the Tivoli/Plus for Scopus resources:

To prevent confusion between traditional TME and Tivoli/Plus forScopus functionality, each Tivoli/Plus icon has been overlaid with theTivoli/Plus symbol to highlight its special functionality.

Tivoli/Plus Unique FeaturesTivoli/Plus modules use the termprofile manager somewhatdifferently than do the other Tivoli products. In a Tivoli/Plus module,a profile manager's primary function is as asubscription list. Asubscription list identifies the machines that tasks and jobs run onwhen executed. Subscription lists can contain machine names or otherprofile managers. Adding a profile manager to a subscription list issimply a way of subscribing several machines at a time rather thanadding each one individually.

TheTivoli/Plus User's Guide describes the function of profilemanagers in the Tivoli/Plus modules in more detail. For moreinformation, see the section on subscribers and targets in theTivoli/Plus User's Guide.

Starting a Tivoli/Plus Module

1–16 Version 1.0

Starting a Tivoli/Plus ModuleAll Tivoli/Plus modules are kept in a collection under theTivoliPlusicon on the TME desktop. The module’s icon is added to this collectionafter installation. The following icon represents the Tivoli/Pluscollection:

Use the following steps to see the modules included in your Tivoli/Pluscollection:

1. From the main TME desktop, double-click on theTivoliPlusicon



Getting S

tarted with

Tivoli/P

lus for Scopus

to display theTivoliPlus window.

TheTivoliPlus window displays an icon for each Tivoli/Plusmodule installed. In the case above, only the Tivoli/Plus forScopus, the Tivoli/Plus for Challenger, and the Tivoli/Plus forAutoSys System modules have been installed.

Note: In some cases, icons in theTivoliPlus window may beplaceholders for future modules. In the interim, they areused for informational purposes.

2. Double-click on theTivoliPlus for Scopus icon or select theOpen... option from its pop-up menu


1–18 Version 1.0

to display the icons representing the tasks and other tools for managingthe Scopus help desk application.

Launching the Scopus Application


Getting S

tarted with

Tivoli/P

lus for Scopus

Launching the Scopus ApplicationWhen Tivoli/Plus for Scopus is installed on a Scopus server, theinstallation process identifies the location of the Scopus binarydirectories and creates an icon for launching the Scopus help deskapplication from within the TME.

Each Scopus server has its own Scopus icon for launching the Scopusapplication from that server site. For example, for a server named"bart," the following icon appears:

The Scopus help desk application has 5 logical entry points:

■ SupportTEAM/QualityTEAM client

■ SalesTEAM client

■ RemoteTEAM client

■ DesignTEAM server

■ InformTEAM server

Each logical entry point is pre-configured and appears on the pop-upmenu for each Scopus icon.

Launching the Scopus Application

1–20 Version 1.0


Softw

are Distribution for

Scopus

2Software Distribution for Scopus

Tivoli/Plus for Scopus includes hierarchical, pre-configuredTivoli/Courier file packages for distributing and installing Scopusapplications on clients. Much of the configuration activity normallyassociated with a Tivoli/Courier file package has been done for you.Using Tivoli/Plus for Scopus and Tivoli/Courier, you can install theScopus application across a multi-platform network.

Installing Scopus clients is a two-stage process. First, you set up theScopus installation by configuring a Tivoli/Courier file package foreach type of platform on which you are installing Scopus. Forexample, if you are installing Scopus on both a Solaris and a Sunplatform, you need to configure a Tivoli/Courier file package twice,once for each platform.

Second, you distribute the configured file packages by running theInstall Scopus Clients task. This task installs Scopus on the selectedsubscribers for each platform for which you have configured aTivoli/Courier file package. You can distribute Scopus to allconfigured platforms or choose to distribute to only a single platform.

2

Configuring Tivoli/Courier File Packages

2–2 Version 1.0

Configuring Tivoli/Courier File PackagesWhen configuring a Tivoli/Courier file package to be used withTivoli/Plus for Scopus, you establish the location of the Scopusinstallation directories so that Tivoli/Courier can locate the installationbinaries and files when installing. You also identify the destinationdirectory on the target machines to which the binaries will bedistributed.

Tivoli/Plus for Scopus has a different setup icon depending on whetheryou are configuring a file package for a UNIX or a Windows platform.Once configured, the Tivoli/Courier file packages are installed with theInstall Scopus Clients icon. (For an illustration of the install icon, see“Installing Scopus” on page 2-11.)

Function Setup Icon

Configures a Tivoli/Courier filepackage for distributing andinstalling the Scopus applicationson a Windows platform.

Configures a Tivoli/Courier filepackage for distributing andinstalling the Scopus applicationson a UNIX platform.



Softw


Scopus

File Packages for a Windows PlatformUse the following steps to set up Tivoli/Courier to install Scopus on aWindows platform. Online help is available.

1. Double-click on theSetup Scopus Windows Client Install iconto display theConfigure Scopus Windows Install window.

TheConfigure Scopus Windows Install window allows you toconfigure the client installation parameters for a Windowsplatform.


2–4 Version 1.0

2. Select the type of operating system on which you will be runningScopus from theWindows Architecture Type to Configure(win16/win32) pop-up menu.

Note: You need to complete theConfigure Scopus WindowsInstall window for each Windows platform for whichyou will be distributing and installing a Scopusapplication.

3. Identify the location of the Scopus source binaries as follows:

a. In theManaged Node Name field, enter the name of theTME server or the managed node where the Scopus sourcebinaries are located.

b. In thePath to Scopus staging directory field, enter thedirectory path to the Scopus installation binaries.

c. In theScopus Clients to be Distributed field, select theScopus clients to be distributed.



Softw


Scopus

4. Identify the destination of the Scopus source binaries and thetime zone of the target machine as follows:

a. In theScopus Installation Directory on Destinationfield,enter the path to the Scopus directory where the installationbinaries for the Scopus application will be distributed andinstalled on the target machine.

b. Select the correct time zone for the target machine with theDestination Time Zone Setting pop-up menu.

5. Press theSet and Close button to set all of the information youhave entered.


2–6 Version 1.0

File Packages for a UNIX PlatformUse the following steps to set up Tivoli/Courier to install Scopus on aUNIX platform. Online help is available.

1. Double-click on theSetup Scopus Unix Client Install icon'spop-up menu to display theConfigure Scopus Unix PackageInstall window.



Softw


Scopus

The Configure Scopus Unix Package Install window allowsyou to configure the client installation parameters for a UNIXplatform.

2. Select the type of operating system on which you will be runningScopus from theTivoli Interpreter Type to Configure pop-upmenu.

Note: You need to complete theConfigure Scopus UnixPackage Install window for each UNIX platform onwhich you will be running the Scopus application.


2–8 Version 1.0

3. Identify the location of the Scopus source binaries as follows:

a. In theManaged Node Name field, enter the name of theTME server or the managed node where the Scopus sourcebinaries are located.

b. In theGet Files from field, select whether the files will comefrom an existing Scopus installation or directly from a tar fileor device.



Softw


Scopus

c. In thePath to Existing Scopus Directoryfield, enter thedirectory path where the existing Scopus installation, tar fileor device can be found.

d. If you are installing from a tar file or device, the system needsa directory in which to unpack these files before distribution.Enter the path to the directory that you choose for thispurpose in the80 MB Scratch Directory field.

Note: After you have installed Scopus from a device or tarfile, you can use the scratch directory as the source ofthe Scopus binaries for subsequent installations. Todo this, selectExisting Scopus Installation from theGet Files from field and then enter the path to thescratch directory in thePath to Existing ScopusDirectory field. When you distribute or installScopus for the first time, the system createssubdirectories in the directory that you specified forthe Scopus binaries. These subdirectories are namedwith the following format:

interpreter_type/scopus

where interpreter type refers to the platform onwhich Scopus was installed.

On subsequent installations, be sure to specify thefull path name including the additional directories.For example, if the original path was:

/usr/source_staging

and you installed on a solaris2 platform, you wouldspecify:

/usr/source_staging/solaris2/scopus


2–10 Version 1.0

e. In theScopus Clients and Servers to be Distributedsection, select the clients and servers that you need todistribute. You need to select at least one item from thissection.

4. In theScopus Directory field, enter the path to the directory onthe target machine to which the Scopus binaries andconfiguration files will be distributed.

5. Press theSet and Close button to set all of the information youhave entered.

Installing Scopus


Softw


Scopus

Installing ScopusAfter you have configured a Tivoli/Courier file package for eachplatform on which you wish to install a Scopus application, you areready to install Scopus on these platforms. You can distribute to allplatforms for which you have configured a Tivoli/Courier file packageor to a single platform. Scopus performs pre-installation checks, suchas verifying available disk space and memory. Output for eachplatform is sent to the source machine in the following directory:

/tmp/Scopus_client_install.platform_name

whereplatform_name refers to the operating system on whichScopus was installed.

You will use theInstall Scopus Clients icon to install Scopus. If youwish to view the Tivoli/Courier file packages that you have created,select theOpen... option from theInstall Scopus Clients icon'spop-up menu.

Installing Scopus

2–12 Version 1.0

Installing Scopus on All Configured PlatformsUse the following steps to install Scopus on all platforms for whichyou have configured a Tivoli/Courier file package:

1. Select theSubscribers... option from theInstall Scopus Clientsicon's pop-up menu to display theSubscribers window.

2. Specify the subscription lists to which you want to install Scopusby using the and buttons to move the desired lists intotheCurrent Subscribers field. When finished, press theSetSubscriptions & Close button.

3. Select theDistribute option from theInstall Scopus Clientsicon's pop-up menu. Selecting this option installs Scopus ontothe client machines listed on the subscription lists that you chose.

Installing Scopus


Softw


Scopus

Installing Scopus on a Single PlatformIf you want to install Scopus on only one type of platform, you candistribute only the Tivoli/Courier file package that applies to thatplatform.

Use the following steps to install Scopus on a single platform:

1. Select theOpen... option from theInstall Scopus Clients icon'spop-up menu to display theInstall Scopus Clients window.

2. In theInstall Scopus Clients window, select theSubscribers...option from the pop-up menu of the icon representing the filepackage for the platform.

Installing Scopus

2–14 Version 1.0

3. Specify the subscription lists to which you want to install Scopuson a single platform by using by using the and buttonsto move the desired lists into theCurrent Subscribers field.When finished, press theSet Subscriptions & Close button.

4. Select theDistribute option from the icon's pop-up menu.Selecting this option installs Scopus onto the client machineslisted on the subscription lists that you chose.


Resource M

onitoring

3Resource Monitoring

Tivoli/Plus for Scopus provides the ability to monitor criticalresources with Tivoli/Sentry. The Sentry monitors are predefined toenable you to manage different aspects of the operating system, suchas processes, available swap space, and log file size, or the Scopusserver that are crucial to the continued availability of the Scopusapplication. These monitors allow you to quickly identify and respondto potential problems so that system down time is avoided.

3

Using Tivoli/Plus for Scopus Monitors

3–2 Version 1.0

Using Tivoli/Plus for Scopus MonitorsTivoli/Plus for Scopus comes with three types of monitors: CentralScopus Server Monitors, Remote Scopus Server Monitors, and ScopusClient Monitors.

Before the Tivoli/Plus for Scopus monitors are operational, they mustbe distributed to their subscription lists. To distribute a monitor,simply select theDistribute... option from the monitor's pop-up menuand then click on theDistribute Now button.

Function Monitor Icon

These monitors check the status of theScopus server.

These monitors check the status of theScopus processes, available swapspace, logfile size, and so forth on theremote Scopus servers.

These monitors check the status of theScopus client machines.



Resource M

onitoring

After installation, the monitors are ready to be distributed to theirdefault subscription list. TheScopus Central Monitors aredistributed to the Tivoli server. TheScopus Remote Monitors aredistributed to theScopus Server List. TheScopus Client Monitorsare distributed to theScopus Client List.


3–4 Version 1.0

The default subscription list can be viewed or changed by using theSubscribers... option from the monitor's pop-up menu.

Although the Tivoli/Plus for Scopus monitors come already defined tomonitor resources specific to Scopus, you can add monitors from theTivoli/Sentry collection or delete monitors as you wish. You can alsoedit existing monitors to perform different actions under differentconditions.

Selecting the options on a Scopus monitor’s pop-up menu displays theusual Tivoli/Sentry windows. Refer to the Tivoli/Sentrydocumentation for more detailed information on using these windows.

Displays the Sentry Profile Properties win-dow, which includes functions for adding,deleting, and editing monitors.

Displays the Distribute Profiles windowfor distributing monitors to those managednodes (machines) and profiles included onthe monitor’s subscription list.

Displays the Subscribers window for spec-ifying to which subscription list the moni-tor is distributed.

Viewing the Status of Monitored Resources


Resource M

onitoring

Viewing the Status of Monitored ResourcesUse theScopus Sentry Indicators icon to view the status of themonitored resources.

The thermometer on theScopus Sentry Indicators icon rises as thestatus of a monitored resource becomes more urgent.

Open theCentral Scopus Server Monitors, theRemote ScopusServer Monitors, or theScopus Client Monitors icon to view thestatus of the central Scopus server or the resources on the remoteserver and client machines. For each monitored resource, the monitoronly reports the most urgent status received within a recent time frame.The monitor reports are organized so that the most urgent status levelappears at the top of the report.

For more information on viewing the status of a monitored resourceand on the Tivoli/Sentry indicator collection, refer to the Tivoli/Sentrydocumentation.

Monitored Resources

3–6 Version 1.0

Monitored ResourcesThe following table indicates the network resources that Tivoli/Plusfor Scopus monitors.

Monitored ResourceDescribed on Page

Monitor Icon

Host status page 3-7

InformTEAM daemon status page 3-8

RemoteTEAM daemon status page 3-9

ScopusRTD Daemonct(RemoteTEAM process) daemonstatus.

page 3-10

Available swap space page 3-11

Logfile sizes:temp.0, temp.1,and temp.2.

page 3-12

Mail queue length page 3-13

Kilobytes paged out page 3-14

Monitored Resources


Resource M

onitoring

Host StatusThe host status monitor checks whether the status of a host is up ordown. This monitor checks the status of any host or other resource onthe network that can respond to a ping request. This monitor checksspecifically to see whether the targeted hosts are up or down.

This monitor runs every 15 minutes.

The following table lists the pre-configured actions for this monitor.

Severity Trigger When Default Actions

Critical Becomes unavailable Send event to theTivoli/Enterprise Console.Change icon.

Severe Never None

Warning Never None

Reset Becomes available Send event.

Normal N/A None

Always N/A None

Monitored Resources

3–8 Version 1.0

InformTEAM Daemon StatusThe InformTEAM daemon status monitors check whether theInformTEAM daemon is up and running.

This monitor runs every minute.

The following table lists the pre-configured actions for this monitor:



Severe Never None

Warning Never None


Normal N/A None

Always N/A None

Monitored Resources


Resource M

onitoring

RemoteTEAM Daemon StatusThe RemoteTEAM daemon status monitor checks whether theRemoteTEAM daemon is up and running.





Severe Never None

Warning Never None


Normal N/A None

Always N/A None

Monitored Resources

3–10 Version 1.0

SCOPUSRTD Daemonct StatusThe SCOPUSRTDaemonct status monitor checks for RemoteTEAMprocess instances.




Critical Greater than 30 entries. Send event to theTivoli/Enterprise Console.Change icon.

Severe Greater than 15 entries. Send event.Change icon.

Warning Greater than 5 entries. Send event.Change icon.

Reset Less than 5 entries. Send event.

Normal N/A None

Always N/A None

Monitored Resources


Resource M

onitoring

Available Swap SpaceThe swap space monitor checks the amount of available swap space.




Critical Less than 10MB Send event to theTivoli/Enterprise Console.Change icon.

Severe Less than 15 MB. Send event.Change icon.

Warning Less than 20MB. Send event.Change icon.

Reset Greater than 20MB. Send event.

Normal N/A None

Always N/A None

Monitored Resources

3–12 Version 1.0

LogFile SizeThe logfile size monitor checks the size of the Scopus log files (temp.0,temp.1, and temp.2).




Critical Greater than 500KB. Send event to theTivoli/Enterprise Console.Change icon.

Severe Greater than 150KB. Send event.Change icon.

Warning Greater than 50KB. Send event.Change icon.

Reset Less than 50KB. Send event.

Normal N/A None

Always N/A None

Monitored Resources


Resource M

onitoring

Mail Queue LengthThe mail queue length monitoring source checks the number of entriesin the mail queue. Monitors that are defined with this monitoringsource use numeric operators to evaluate data.




Critical Greater than 50 entries. Send event to theTivoli/Enterprise Console.Change icon.

Severe Greater than 40 entries. Send event to theTivoli/Enterprise Console.Change icon.

Warning Greater than 20 entries. Send event to theTivoli/Enterprise Console.Change icon.

Reset Less than 20 entries. Send event.

Normal N/A None

Always N/A None

Monitored Resources

3–14 Version 1.0

Kilobytes Paged OutThe kilobytes paged out monitoring source checks the kilobytes pagedout per second on a machine.




Critical Greater than 10 perminute.

Send event to theTivoli/Enterprise Console.Change icon.

Severe Greater than 5 perminute.

Send event.Change icon.

Warning Greater than 1 perminute.

Send event.Change icon.

Reset Less than 1 per minute. Send event.

Normal N/A None

Always N/A None


Enterprise E

ventM

anagement

4Enterprise Event Management

With the Tivoli/Enterprise Console, Tivoli/Plus for Scopus provides aset of filters for identifying events and a set of predefined correlationrules to automate the task of responding to specific events. An event isany significant change in the state of system resources or anapplication. In the case of Tivoli/Plus for Scopus, an event is a changein a monitored resource that affects Scopus or the system on whichScopus is running. Examples of events are the starting and stopping ofa process or a host going down. Event management provides apredefined or automated response to specific events, so that potentialproblems are identified and responded to before causing system downtime. For example, if a process fails, the Tivoli/Enterprise Console canautomatically rerun the process. The Tivoli/Enterprise Console canalso notify the system administrator of repeated process failures thatmay indicate a more severe problem with an application or thenetwork. For some events, there is no automated response except to bedisplayed in the Tivoli/Enterprise Console.

4

Setting Up the Tivoli/Enterprise Console

4–2 Version 1.0

Setting Up the Tivoli/Enterprise ConsoleThe following describes the configuration activity that occurs whensetting up the Tivoli/Enterprise Console to be used with Tivoli/Plus forScopus. This activity takes place on the Tivoli/Enterprise Console andScopus servers.

■ Tivoli/Enterprise Console Server

The Tivoli/Enterprise Console server is set up to

• Recognize and accept Scopus events.

• Respond to Scopus events according to the predefined rules.

• Νotify the system administrator of the events received andthe action taken.

■ Scopus Server

On the machines where Scopus servers are running

• Scopus is configured to send Scopus events to theTivoli/Enterprise Console.

• Τhe logfile adapter is configured to recognize and forwardScopus events to the Tivoli/Enterprise Console.

Tivoli/Plus for Scopus performs most of the setup activityautomatically. The following icon represents theSetup EventServerfor Scopustask.

.



Enterprise E

ventM

anagement

To set up the Tivoli/Enterprise Console:

1. Select theRun job... option from theSetup EventServer forScopus icon's pop-up menu.

2. Specify the rule base that you want to contain the Scopus eventclasses and rules in theNew (or existing) Rule base name field.You can accept the default rule base (Tivoli/Plus) or create a newrule base (by entering a new name) or modify an existing rulebase (by entering an existing name).

Note: It is not advisable to modify the default rule base, so donot enterDefault in theNew (or existing) Rule Basenamefield.


4–4 Version 1.0

New rule bases are created by copying (cloning) and modifyingan existing one. If you are creating a new rule base, enter thename of the rule base to be copied in theRule Base to clone field:

If you are creating a new rule base, specify the path name to thedirectory on the Tivoli/Enterprise Console server in which youwant to create the new rule base. Only use thePath for new RuleBase field if you are creating (not modifying) a rule base.

3. (Optional). Use theName for Event Console To Configurefield to display Scopus related events on a particular systemadministrator's event console. To make this assignment, enter thename that appears under the desired system administrator's eventconsole icon.

4. Press theSet and Close button when finished.

Events and Rules


Enterprise E

ventM

anagement

Events and RulesTivoli/Plus for Scopus configures the Tivoli/Enterprise Console toreceive events from Scopus and Tivoli/Sentry. The Tivoli/EnterpriseConsole classifies the events and then matches them against the rulebase to see if the event has a predefined rule (automated response).

Event CorrelationTivoli/Plus for Scopus provides event correlation. Event correlation isthe tracking of multiple events whose occurrence may indicate an errorcondition or abnormal activity. For example, the Tivoli/Plus forScopus module can track such unusual activity as the failure of theInformTEAM Process daemon occurring more than once a day. If thishappens, the Tivoli/Plus for Scopus module sends an event to theTivoli/Enterprise Console to alert the system administrator of suchunusual activity.

Once an error condition is resolved, Tivoli/Plus for Scopus closes thepreviously opened events regarding the error condition. For example,when a failed Scopus daemon becomes available, Tivoli/Plus forScopus closes the related events in the Tivoli/Enterprise Console.

Tivoli/Sentry EventsThe following table describes the events and rules that Tivoli/Sentryuses when monitoring Scopus resources. The table is organizedaccording to the Scopus Tivoli/Sentry monitors that send the event tothe Tivoli/Enterprise Console.

Since Tivoli/Sentry messages follow a standard format, thesemessages are not reproduced in the table. The following is an exampleof a Tivoli/Sentry message:

Sentry Remote Scopus Monitors/Daemon status on host indis20Mon May 06 13:23:00 1996

Status: >>> critical <<<

Daemon status (InformTEAM) Changes to down(Previous: up Current: down Effective: down)Daemon: InformTEAM

Events and Rules

4–6 Version 1.0

Tivoli/Sentry Events

Host Status

The host is unavailable

Event Description:

Event Class:

Event Severity:

Correlation Activity:

A specified host becomes unavailable.

SCOPUS_via_Sentry2_0_ host

CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the event’s repeat count and discard the event.

Create a Scopus trouble ticket.

The host is available

Event Description:

Event Class:

Event Severity:


A specified host becomes unavailable.

SCOPUS_via_Sentry2_0_ host

HARMLESS

Check for previous CRITICAL events of this type. If there areany, close the event.

Mail Queue Status

> 20 entries

Event Description:

Event Class:

Event Severity:


Mail queue has greater than 20 entries.

SCOPUS_via_Sentry2_0_mailqlen

WARNING


Check for previous SEVERE events of this type. If there areany, update the event’s severity to WARNING.

Events and Rules


Enterprise E

ventM

anagement

> 40 entries

Event Description:

Event Class:

Event Severity:




SEVERE


Check for previous WARNING events of this type. If there areany, update the event’s severity to SEVERE.

Sentry indicator icon is changed.

> 50 entries

Event Description:

Event Class:

Event Severity:




CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the event’s repeat count and discard the event. Ifthe repeat count is greater than 1 per day, send a WARNINGevent to the Tivoli/Enterprise Console with the followingmessage:

“Chronic mail queue condition on Host:%s”,\<hostname

Check for previous WARNING or SEVERE events. If thereare any, close the event.



Events and Rules

4–8 Version 1.0

Swap Space

< 20 MB

Event Description:

Event Class:

Event Severity:


Swap space decreases below 20MB on a machine.

SCOPUS_via_Sentry2_0_swapavail

WARNING



Sentry icon is changed.

> 20 MB

Event Description:

Event Class:

Event Severity:


Swap space increases above 20MB on a machine.


HARMLESS

Check for previous CRITICAL, SEVERE, or WARNINGevents of this type. If there are any, close the event.

< 15 MB

Event Description:

Event Class:

Event Severity:




SEVERE


Check for previous WARNING events of this type. If there areany, update the event’s status to SEVERE.

Sentry icon is changed.


Events and Rules


Enterprise E

ventM

anagement

< 10 MB

Event Description:

Event Class:

Event Severity:



SCOPUS _via_Sentry2_0_swapavail

CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the event’s repeat count. If the repeat count isgreater than 1 per day, send a WARNING event to theTivoli/Enterprise Console.

Check for previous WARNING or SEVERE events of thistype. If there are any, close the event.

Sentry Indicator icon is changed.

Kilobytes Paged Out

> 1 Second

Event Description:

Event Class:

Event Severity:


The pageouts are more than 1 second.

SCOPUS_via_Sentry2_0_pageouts

WARNING



< 1 Second

Event Description:

Event Class:

Event Severity:


The pageouts are less than 1 second.


HARMLESS

Check for previous CRITICAL, SEVERE, or WARNINGevents and set their status to closed.



Events and Rules

4–10 Version 1.0

> 5 Seconds

Event Description:

Event Class:

Event Severity:


The pageouts are more than 5 seconds.


SEVERITY




> 10 Seconds

Event Description:

Event Class:

Event Severity:


The pageouts are greater than 10 seconds.


CRITICAL

Check for previous CRITICAL events of this type. If there areany, update the repeat count.

Check for previous WARNING or SEVERE events of thistype. If there are any, close the event.

If the event count is greater than 1 per day per week, then senda WARNING to the Tivoli/Enterprise Console with thefollowing message:

“Chronic page out condition; possible memory\<problems on host:%s”, hostname.



Events and Rules


Enterprise E

ventM

anagement

Scopus Custom Monitor EventsThe following table describes the events generated by the Scopusdaemon monitors, which are specific to the Scopus server process.

Custom Scopus Monitor Event Message

Log File Status

> 50 KB

Event Description:

Event Class:

Event Severity:


The size of one of the logfiles (files temp.0, temp.1, andtemp.2) increases above 50KB.

SCOPUSLogfileSize

WARNING




> 150 KB

Event Description:

Event Class:

Event Severity:


The size of one of the logfiles (files temp.0, temp.1, temp.2)increases above 150KB.

SCOPUSLogfileSize

CRITICAL




Events and Rules

4–12 Version 1.0

> 200KB

Event Description:

Event Class:

Event Severity:


The size of one of the logfiles (files temp.0, temp.1, or temp.2)increases above 200KB.

SCOPUSLogfileSize

CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the repeat count and discard the event.

Check for previous SEVERE or WARNING events of thistype. If there are any, close the event.


SCOPUS Daemon

The InformTEAM process is unavailable

Event Description:

Event Class:

Event Severity:


The InformTEAM process (iteam) is unavailable.

SCOPUSDaemon

CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the repeat count and discard the event. If theevent count is greater than 1 per day, send a WARNING eventto the Tivoli/Enterprise Console with the following message:

“Repeated iteam process failure on Host:s”\<hostname




Events and Rules


Enterprise E

ventM

anagement

The Inform Team Process is available

Event Description:

Event Class:

Event Severity:


The Inform Team Process is available.

SCOPUSDaemon

HARMLESS


The RemoteTEAM server process is unavailable

Event Description:

Event Class:

Event Severity:


The RemoteTEAM server process (rteam) is unavailable.

SCOPUSDaemon

CRITICAL

Check for previous CRITICAL events of this type. If there areany, increase the repeat count and discard the event. If theevent count is greater than 1 per day, send a WARNING eventto the Tivoli/Enterprise Console with the following message:

“Repeated rteam process failure on\<Host:%s”,hostname

Create a Scopus trouble ticket.

The RemoteTEAM server process is available

Event Description:

Event Class:

Event Severity:


The RemoteTEAM server process (rteam) is available.

SCOPUSDaemon

HARMLESS



Setting Up Scopus Trouble Tickets

4–14 Version 1.0

Setting Up Scopus Trouble TicketsTivoli/Sentry forwards events to the Tivoli/Enterprise Console inresponse to changes in the monitored resources. Where appropriate,the Tivoli/Enterprise console sends the event to Scopus so that Scopuscan generate a trouble ticket. In order to generate a trouble ticket,Scopus must be set up to receive and respond appropriately to theevents that the Tivoli/Enterprise Console forwards. For information onhow the Tivoli/Enterprise Console handles specific Tivoli/Sentryevents see “Tivoli/Sentry Events” on page 4-5.

The trouble ticketing system for Scopus (SupportTEAM) is createdduring installation. Trouble tickets are logged as calls inSupportTEAM.

If SupportTEAM is not installed, an event register (sti-tvpluslog) is setup in the Scopus database at installation. The trouble tickets are storedin this event register.

Closing Scopus Trouble TicketsA business rule must be set up on Scopus to close trouble ticketsgenerated by Tivoli/Plus. In addition, the InformTEAM server must beup and running in order to invoke the business rule.

The business rule must contain the following information:

■ The document type must be Logs.

■ The conditions must be set to field log_id > 0 and sti_castype=0.

Note: These conditions uniquely identify the Tivoli/PlusTrouble Ticket.

■ The execute command must be sti_typlus_close and be of typeTCL.

For more information on creating a business rule, refer to the Scopusdocumentation.


Tasks and Jobs forS

copus

5Tasks and Jobs for Scopus

Tivoli/Plus for Scopus provides tasks that allow you to run Scopus jobson multiple machines and operating systems. These tasks are ready tobe executed as soon as you have installed your Tivoli/Plus for Scopusmodule. Simply double-click on the task icon to execute the Scopusjob. You can modify the default execution characteristics of aparticular job, such as where the output of a job is displayed and onwhich machines the job will run. You may also specify whether a jobruns serially on each machine, in parallel on all machines, or staged ingroups of machines.

5

Tivoli/Plus for Scopus Jobs

5–2 Version 1.0

Tivoli/Plus for Scopus JobsThe following table lists the Scopus jobs that can be customized andexecuted with Tivoli/Plus for Scopus. Double-click on the task icon torun the Scopus job.


Job Description Icon

Adds users to Scopus applications.

Deletes users from Scopus applications.

Changes user passwords for all Scopusapplications.

Allows modification of the Scopus setupinformation required by the Tivoli/Plusfor Scopus module. This information wasspecified in theInstall Options dialogwhen installing the Tivoli/Plus for Scopusmodule.



Tasks and Jobs forS

copus

Allows periodic database backups at eachdistributed Scopus server.

Allows database tables to be purged andrevised in the Scopus database.

Adds keywords and meta keywords to theScopus problem resolution engine.

Prints reports on the Scopus server.Invokes the printer and printing methodspecified by the customer at the specifiedserver.


Running a Scopus Job and Saving the Output

5–4 Version 1.0

Running a Scopus Job and Saving the OutputAll Tivoli/Plus for Scopus jobs can be run immediately afterinstallation. You can run a task library job from the desktop only.

To run a Scopus job with the default execution characteristics:

The job’s output is displayed in an output window. To save the job’soutput to a file:

1. Select theSave to File... button to display the Save Job Outputdialog box.

2. Enter the name of the machine on which to save the output file intheOn Host field.

3. Enter the name of the output file that will contain the job’s outputin theOutput File field.

4. Select theSave & Closebutton to save the output of the job tothe file you specified.

You can also use theModify job... option of the job icon’s pop-upmenu to specify that the output be sent to a file.

If Tivoli/Plus for Scopus requires further information to execute thejob, a pop-up dialog appears prompting you for the information.Online help is available to assist you in completing these dialogs. Thejob’s output is displayed on the desktop or sent to a file or both asspecified

—OR—Double-click onthe icon.

Use the icon’s pop-up menu.

Modifying a Scopus Job


Tasks and Jobs forS

copus

Modifying a Scopus JobYou can modify the execution characteristics of a job for each time thejob is run or for only a single execution of the job.

Modifying for All Future Executions of the JobUse the following steps to modify a job for each time it is run:

1. Select theModify job... option from the job icon’s pop-up menu.

Be sure to specifyon which man-aged nodes andprofile managersthe job will run.


5–6 Version 1.0

2. Make the necessary changes in theEdit Job window. Online helpis available to assist you.

Note: Be sure to specify on which managed nodes and profilemanagers the job will run.

3. Click on theChange & Close button when finished.

Modifying for a Single Execution of the JobUse the following steps to modify a job for only a single execution ofthe job. The next time you run the same job, it will return to the defaultexecution characteristics.

1. Select theRun on selected subscribers... option from the jobicon’s pop-up menu.

Be sure to specifyon which managednodes and profilemanagers the jobwill be run thistime.



Tasks and Jobs forS

copus

2. Make the necessary changes in theExecute Taskwindow.Online help is available to assist you.

3. Click on theExecute button when finished.


5–8 Version 1.0

Tivoli/Plus for Scopus User’s Guide Index–1

Index

Aactivating Tivoli/Plus icons 1-14

Ccommand line installation 1-14Configure Scopus Unix Package Install

Window 2-6Configure Scopus Windows 3.x Client Install

window 2-3Configure Tivoli/Enterprise Console for

Scopus Events window 4-3configuring file packages 2-2

for UNIX platforms 2-6for Windows platforms 2-3icons for 2-2

correlating events 4-5

Ddaemon status

event 4-12desktop installation 1-4dialogs

SeewindowsDistribute Profiles window 3-3

EEdit Job window 5-5event management 4-1event messages 4-6– 4-13

eventsCustom Monitor

daemon status 4-12logfile status 4-11

Tivoli/Sentryhost status 4-6mail queue status 4-6paged out status 4-9swap space 4-8

Execute Task window 5-6

FFile Browser window 1-6

Hhost status

events 4-6

Iicons

for configuring file packages 2-2for monitored resources 3-6for monitors 3-2, 3-6for Scopus jobs 5-2for Tivoli/Enterprise Console 4-2Scopus application 1-15

Install Product window 1-5, 1-8installing

command line 1-14desktop 1-4requirements for 1-2

hardware 1-3license key 1-2software 1-2

Scopus 2-11

Index–2 Version 1.0

installing Tivoli/Plus for Scopusrequirements for 1-2– 1-3

Jjobs

list of 5-2

Llogfile status

events 4-11

Mmail queue status

events 4-6monitored resources

icons for 3-6list of 3-6

monitorsicons for 3-2using 3-4

Ppaged out

events 4-9problem report, TME viiiprocedures

configuring file packagesfor Windows platforms 2-3

Product Install window 1-12, 1-13

SSentry Indicator Collection window 3-5setting up

Tivoli/Enterprise Console 4-2trouble tickets 4-14

swap spaceevents 4-8

TTivoli/Courier, configuring file packages

for Windows platforms 2-3icons for 2-2

Tivoli/Enterprise Consolesetup icon 4-2

TMEdesktop window 1-4problem report viii

trouble tickets, setting up 4-14

Uusing monitors 3-4

Wwindows

Configure Scopus 3.x Client Install 2-3Configure Tivoli/Enterprise Console for

Scopus Events 4-3Distribute Profiles 3-3Edit Job 5-5Execute Task 5-6File Browser 1-6Install Product 1-5, 1-8Product Install 1-12, 1-13Sentry Indicator Collection 3-5TME desktop 1-4