Oem Users Guide

7/31/2019 Oem Users Guide

1/182

OEM Users Guide

Abstract

This manual describes the OEM Server and Enterprise Management Adapter components of theOpen Enterprise Management (OEM) Gateway product. It tells how to install, configure, andcustomize the OEM Server to monitor OEM objects, and it documents the applicationprogrammatic interfaces (APIs) for both client applications and enterprise managementframework adapters as a reference for developers planning to use the OEM Server in their owndevelopment efforts.

Product Version

Open Enterprise Management (OEM) Version 3.0 (T8486)

Part Number Published

520330-001 April 2001


2/182

Ordering InformationFor manual ordering information: domestic U.S. customers, call 1-800-243-6886; international customers, contactyour local sales representative.

Document DisclaimerInformation contained in a manual is subject to change without notice. Please check with your authorizedrepresentative to make sure you have the most recent information.

Export StatementExport of the information contained in this manual may require authorization from the U.S. Department of Commerce.

ExamplesExamples and sample programs are for illustration only and may not be suited for your particular purpose. Theinclusion of examples and sample programs in the documentation does not warrant, guarantee, or make anyrepresentations regarding the use or the results of the use of any examples or sample programs in anydocumentation. You should verify the applicability of any example or sample program before p lacing the softwareinto productive use.

U.S. Government CustomersFOR U.S. GOVERNMENT CUSTOMERS REGARDING THIS DOCUMENTATION AND THE ASSOCIATEDSOFTWARE:These notices shall be marked on any reproduction of this data, in whole or in part.NOTICE: Notwithstanding any other lease or license that may pertain to, or accompany the delivery of, thiscomputer software, the rights of the Government regarding its use, reproduction and disclosure are as set forth inSection 52.227-19 of the FARS Computer SoftwareRestricted Rights clause.

RESTRICTED RIGHTS NOTICE: Use, duplication, or disclosure by the Government is subject to therestrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause atDFARS 52.227-7013.RESTRICTED RIGHTS LEGEND: Use, duplication or disclosure by the Government is subject to restrictionsas set forth in paragraph (b)(3)(B) of the rights in Technical Data and Computer Software clause inDAR 7-104.9(a). This computer software is submitted with restricted rights. Use, duplication or disclosure issubject to the restrictions as set forth in NASA FAR SUP 18-52 227-79 (April 1985) Commercial ComputerSoftwareRestricted Rights (April 1985). If the contract contains the Clause at 18-52 227-74 Rights in DataGeneral then the Alternate III clause applies.U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP ScheduleContract.Unpublished All rights reserved under the Copyright Laws of the United States.

Document HistoryPart Number Product Version Published

520330-001 OEM Version 3.0 April, 2001


3/182

Compaq Computer Corporation 520330-001

i

OEM Users Guide

Glossary Index Figures

Whats New in This Manual xi

Manual Information xi

New and Changed Information xi

About This Manual xiii

Audience xiii

Organization xiiiYour Comments Invited xiii

Notation Conventions xiv

1. Introducing the Open Enterprise Management ServerOEM Architecture 1-1

Features of the OEM Server Version 3.0 1-2

Hardware and Software Requirements 1-3

Hardware Requirements 1-3Software Requirements 1-3

Obtaining Support 1-3

2. Installing the Open Enterprise Management ServerSetup 2-1

Files Installed 2-1

Registry Changes 2-2

Uninstalling the OEM 2-2


4/182

Contents

OEM Users Guide 520330-001

ii

3. Configuring the Open Enterprise ManagementServer

3. Configuring the Open Enterprise Management ServerGeneral Options 3-1

Opening the OEM General Options Dialog Box 3-2

Specifying the Number of Reporting Levels 3-2

Including Intermediate-Level State Values in Frameworks and DisplayWindows 3-2

Example 3-3

Reusing Display Windows 3-3

Keeping Display Windows on Top 3-4

Automatically Closing Max Alerts Windows as They Are Used 3-4

Using Custom View Windows for Alerts and Max Alerts 3-5

Automatically Saving Custom View Definitions 3-5

Synchronizing the OEM Alerts Window and Client Applications 3-6

Setting the Icon Size 3-7

Choosing a New Icon Set 3-7

Choosing the Default Tiling Scheme 3-8

Adapter Options 3-8

Viewing the Adapter List 3-9

Adding an Adapter Entry 3-9

Updating an Adapter Entry 3-10

Deleting an Adapter Entry 3-10

Configuring a Framework Adapter 3-10

Adjusting Adapter Priority 3-11

Restoring Default Adapter Settings 3-11

Using the Add/Update Adapter Dialog 3-12

Logging Options 3-12

Opening the OEM Logging Dialog Box 3-13

Setting the Size of the Log 3-13Enabling API and Error Tracing 3-13

Enabling OEM Timer Tracing 3-14

Font Options 3-14

Advanced Options 3-15

Opening the OEM Advanced Options Dialog Box 3-15


5/182

Contents


iii

3. Configuring the Open Enterprise ManagementServer (continued)

3. Configuring the Open Enterprise Management Server (continued)Limiting the Number of Icons Used 3-15

Supplementary Display Windows 3-16

4. OEM WindowsThe Alerts Window 4-1

Opening an Alerts Window 4-2

Alerts Window Fields 4-2

Alerts Window Menus 4-3

View Menu 4-3

Help Menu 4-3

Sorting Alerts Window Items 4-3

Sizing Alerts Window Columns 4-4Aligning Alerts Windows 4-4

Locking the Alerts Window 4-4

Keeping the Alerts Window on Top 4-5

Refreshing Alerts Window Contents 4-5

Creating a New Alerts Window 4-5

Navigating to Client Applications 4-6

Closing the Alerts Window 4-6

The Max Alerts Window 4-6

Opening a Max Alerts Window 4-6

Max Alerts Window Fields 4-7

Max Alerts Window Menus 4-7

View Menu 4-7

Help Menu 4-8

Sorting Max Alerts Window Items 4-8

Sizing Max Alerts Window Columns 4-8Aligning Max Alerts Windows 4-9

Locking the Max Alerts Window 4-9

Keeping the Max Alerts Window on Top 4-10

Refreshing Max Alerts Window Contents 4-10

Creating a New Max Alerts Window 4-10

Navigating to Client Applications 4-10


6/182

Contents


iv

4. OEM Windows (continued)

4. OEM Windows (continued)Closing the Max Alerts Window 4-11

The Clients Window 4-11

Opening a Clients Window 4-11

Clients Window Fields 4-11Clients Window Menus 4-12

View Menu 4-12

Help Menu 4-13

Sorting Clients Window Items 4-13

Sizing Clients Window Columns 4-13

Aligning Clients Windows 4-13

Locking the Clients Window 4-14

Keeping the Clients Window on Top 4-14

Refreshing Clients Window Contents 4-15

Closing the Clients Window 4-15

The Objects Window 4-15

Opening an Objects Window 4-15

Objects Window Fields 4-16

Objects Window Menus 4-17

View Menu 4-18Help Menu 4-18

Sorting Objects Window Items 4-18

Sizing Objects Window Columns 4-19

Aligning Objects Windows 4-19

Locking the Objects Window 4-19

Keeping the Objects Window on Top 4-20

Refreshing Objects Window Contents 4-20

Closing the Objects Window 4-20The Popups Window 4-21

Opening a Popups Window 4-21

Popups Window Fields 4-21

Popups Window Menus 4-22

View Menu 4-22


7/182

Contents


v


4. OEM Windows (continued)Help Menu 4-23

Sorting Popups Window Items 4-23

Sizing Popups Window Columns 4-23

Aligning Popups Windows 4-24Locking the Popups Window 4-24

Keeping the Popups Window on Top 4-25

Refreshing Popups Window Contents 4-25

Closing the Popups Window 4-25

The Popup Navigation Window 4-26

Popup Navigation Window Fields 4-26

Popup Navigation Window Menus 4-26

View Menu 4-26

Help Menu 4-27

Sorting Popup Navigation Window Items 4-27

Sizing Popup Navigation Window Columns 4-27

Aligning Popup Navigation Windows 4-27

Locking the Popup Navigation Window 4-28

Keeping the Popup Navigation Window on Top 4-28

Refreshing Popup Navigation Window Contents 4-29Navigating to Client Applications 4-29

Closing the Popup Navigation Window 4-29

The Log Window 4-29

Opening a Log Window 4-29

Log Window Fields 4-29

Log Window Menus 4-30

View Menu 4-30

Help Menu 4-31Sorting Log Window Items 4-31

Sizing Log Window Columns 4-31

Aligning Log Windows 4-31

Locking the Log Window 4-32

Keeping the Log Window on Top 4-32


8/182

Contents


vi


4. OEM Windows (continued)Refreshing Log Window Contents 4-33

Closing the Log Window 4-33

OEM Server Log Messages 4-33

The Statistics Window 4-34Opening a Statistics Window 4-34

Statistics Window Fields 4-34

Statistics Window Menus 4-34

View Menu 4-35

Help Menu 4-35

Sorting Statistics Window Items 4-35

Sizing Statistics Window Columns 4-35

Automatically Refreshing Displayed Statistics 4-35

Manually Refreshing Displayed Statistics 4-36

Closing the Statistics Window 4-36

OEM Server Statistics 4-36

The Icons Window 4-38

Opening the Icons Window 4-38

Closing the Icons Window 4-39

The Trace Window 4-39Opening the Trace Window 4-39

Closing the Trace Window 4-39

The About Window 4-40

Opening the About Window 4-40

Closing the About Window 4-40

5. Custom Views

Custom Grouping of Objects 5-1State Filtering 5-1

Independent State Propagation and Arbitration for Each View 5-1

Hierarchical and Object-based Display of Data 5-2

Display of All Clients or Max Client Modes 5-2

Alerts and Max Alerts Custom Views 5-3

Custom View Window Layout 5-3


9/182

Contents


vii

5. Custom Views (continued)

5. Custom Views (continued)Custom View Object List 5-3

Custom View Window Fields 5-4

Custom View Links Bar 5-4

Custom View Menus 5-4File Menu 5-5

Items in the File menu control the Custom View window. 5-5

View Menu 5-5

Help Menu 5-6

The Toolbar 5-6

The MinState Field 5-7

The Status Bar 5-7

Configuring Custom View Properties 5-7

Setting Object Specifiers and State Filters 5-7

Viewing Existing Specifiers 5-8

Adding a New Specifier 5-9

Updating an Existing Specifier 5-9

Deleting an Existing Specifier 5-10

Clearing All Existing Specifiers 5-11

The Add/Update Specifier Dialog Box 5-12Choosing the Display Mode 5-12

Selecting the View Format 5-13

Selecting the Client State Reporting Option 5-14

Altering the Window Layout 5-14

Working With Custom Views 5-15

Creating a New Custom View 5-16

Opening an Existing Custom View 5-16

Saving a Custom View Configuration 5-17Sorting Custom View Window Items 5-17

Sizing Custom View Window Columns 5-17

Locking the Custom View Window 5-18

Keeping the Custom View Window on Top 5-18

Refreshing Custom View Window Contents 5-19


10/182

Contents


viii

5. Custom Views (continued)

5. Custom Views (continued)Navigating to Client Applications 5-19

Closing a Custom View Window 5-19

A. OEM External SpecificationComponent Terminology A-1

Interface Terminology A-1

Architectural Overview A-2

Open Enterprise Management Server A-4

Architecture and Design Considerations for the OEM Server A-4

OEM Request API (Client Application to OEM) A-5

ReportingLevels A-5

Popup.Add A-6Popup.Delete A-9

Popup.Cleanup A-10

Object.Add A-11

Object.Delete A-13

Object.Cleanup A-14

LogMessage A-15

SetIcons A-16

DebugDisplayPopups A-17

DebugDisplayObjects A-18

DebugTraceDisable A-20

DebugQueuePause A-21

DebugQueueResume A-22

Client Callback API (OEM to Client Application) A-23

Command A-23

ClientMessage A-25WindowManagementEnabled A-27

Move A-28

Height A-30

Width A-31

WindowCaption A-32

WindowState A-33


11/182

Contents


ix

A. OEM External Specification (continued)

A. OEM External Specification (continued)SetIcons A-35

Framework Adapter A-36

Architecture and Design Considerations for Framework Adapters A-36

Adapter Request API (OEM to Adapter) A-36Popup.Add A-37

Popup.Delete A-39

Popup.Clear A-40

Object.Add A-41

Object.Delete A-43

Object.Clear A-44

AdapterName A-45

SetCallback A-46

IncludeContext A-47

IsConfigurable A-48

Configure A-49

FrameworkWindowPosition A-50

SetIcons A-51

CloseAdapter A-52

OEM Callback API (Adapter to OEM) A-53Command A-53

ClientMessage A-55

RefreshObjects A-57

RefreshPopups A-58

Tile A-59

Cascade A-61

MinimizeAll A-62

RestoreAll A-63LogMessage A-64

SetIcons A-65

DebugTraceEnable A-66

DebugTraceDisable A-66

DebugQueuePause A-67


12/182

Contents


x

A. OEM External Specification (continued)

A. OEM External Specification (continued)DebugQueueResume A-67

Adapter Callback API (Framework to Adapter) A-68

API Summary A-68

OEM Request API A-68Adapter Request API A-69

OEM Callback API A-70

Client Callback API A-71

Class Name Standards A-71

Object Name Standards A-72

Rule #1 - Hierarchical Name Space A-73

Rule #2 - Path Delimiter A-73

Rule #3 - Null Classes and Objects A-73

Rule #4 - Case Sensitivity A-73

Rule #5 - Class Names A-73

State Conventions A-74

Glossary

Index

FiguresFigure A-1. OEM Information Path Example A-2


13/182


xi

Whats New in This ManualManual Information

OEM Users Guide

Abstract

This manual describes the OEM Server and Enterprise Management Adaptercomponents of the Open Enterprise Management (OEM) Gateway product. It tells howto install, configure, and customize the OEM Server to monitor OEM objects, and itdocuments the application programmatic interfaces (APIs) for both client applicationsand enterprise management framework adapters as a reference for developers planningto use the OEM Server in their own development efforts.

Product Version

Open Enterprise Management (OEM) Version 3.0 (T8486)

Document History

New and Changed InformationThis manual is new.

Part Number Published520330-001 April 2001

Part Number Product Version Published

520330-001 OEM Version 3.0 April, 2001


14/182

Whats New in This Manual


xii

New and Changed Information


15/182


xiii

About This ManualThe OEM Gateway consists of a Server component and one or more Adaptercomponents that provide client applications such as Compaq state monitoring,performance monitoring, and command and control graphical user interfaces (GUIs)with a simplified, encapsulated layer to operations management frameworks.

This manual describes how to install, configure, and customize the OEM Server tomonitor OEM objects, and it documents the application programmatic interfaces (APIs)for both client applications and enterprise management framework adapters.

AudienceThis manual addresses two audiences: System managers, network managers, and operators who install, configure, and

customize the OEM Server to monitor OEM objects

Developers planning to use the OEM Server in their own development efforts

OrganizationThis manual consists of five sections and an appendix, as follows: Section 1, Introducing the Open Enterprise Management Server , provides an

overview of the OEM product and lists hardware and software requirements. Section 2, Installing the Open Enterprise Management Server , provides information

about setup, files installed, and system registry changes.

Section 3, Configuring the Open Enterprise Management Server , describes how tocustomize the behavior of the OEM Server and the appearance of OEM windows.

Section 4, OEM Windows , describes the OEM Server windows that are createdeither in response to direct user requests from OEM menus or as a result of callbacks from framework adapters.

Section 5, Custom Views , describes how to create your own logical groupings of OEM objects based on any criteria you choose and including only objects whosestates fall within the range you specify.

Appendix A, OEM External Specification , serves as a reference detailing the OEM

architecture and providing descriptions of the APIs for both client applications andenterprise management framework adapters for developers wanting to use the OEMServer in their own development efforts.

Your Comments InvitedAfter using this manual, please take a moment to send us your comments. You can dothis by returning a Reader Comment Card or by sending an Internet mail message.


16/182

About This Manual


xiv

Notation Conventions

A Reader Comment Card is located at the back of printed manuals and as a separate fileon the User Documentation disc. You can either fax or mail the card to us. The faxnumber and mailing address are provided on the card.

Also provided on the Reader Comment Card is an Internet mail address. When you sendan Internet mail message to us, we immediately acknowledge receipt of your message. Adetailed response to your message is sent as soon as possible. Be sure to include yourname, company name, address, and phone number in your message. If your commentsare specific to a particular manual, also include the part number and title of the manual.

Many of the improvements you see in manuals are a result of suggestions from ourcustomers. Please take this opportunity to help us improve future manuals.

Notation Conventions

Hypertext Links

Blue underline is used to indicate a hypertext link within text. By clicking a passage of text with a blue underline, you are taken to the location described. For example:

This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2.

General Syntax Notation

The following list summarizes the notation conventions for syntax presentation in thismanual.

UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enterthese items exactly as shown. Items not enclosed in brackets are required. For example:

MAXATTACH

lowercase italic letters. Lowercase italic letters indicate variable items that you supply.Items not enclosed in brackets are required. For example:

file-name

[ ] Brackets. Brackets enclose optional syntax items. For example:

TERM [\ system-name .]$ terminal-name

INT[ERRUPTS]

A group of items enclosed in brackets is a list from which you can choose one item ornone. The items in the list may be arranged either vertically, with aligned brackets oneach side of the list, or horizontally, enclosed in a pair of brackets and separated byvertical lines. For example:

FC [ num ][ -num ][ text ]

K [ X | D ] address -1


17/182

About This Manual


xv

General Syntax Notation

{ } Braces. A group of items enclosed in braces is a list from which you are required tochoose one item. The items in the list may be arranged either vertically, with alignedbraces on each side of the list, or horizontally, enclosed in a pair of braces and separatedby vertical lines. For example:

LISTOPENS PROCESS { $ appl-mgr-name }{ $ process-name }

ALLOWSU { ON | OFF }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed inbrackets or braces. For example:

INSPECT { OFF | ON | SAVEABEND }

Ellipsis. An ellipsis immediately following a pair of brackets or braces indicates that youcan repeat the enclosed sequence of syntax items any number of times. For example:

M address -1 [ , new-value ]...

[ - ] {0|1|2|3|4|5|6|7|8|9}...An ellipsis immediately following a single syntax item indicates that you can repeat thatsyntax item any number of times. For example:

" s-char ..."

Punctuation. Parentheses, commas, semicolons, and other symbols not previously describedmust be entered as shown. For example:

error := NEXTFILENAME ( file-name ) ;

LISTOPENS SU $ process-name .# su-name

Quotation marks around a symbol such as a bracket or brace indicate the symbol is arequired character that you must enter as shown. For example:

"[" repetition-constant-list "]"

Item Spacing. Spaces shown between items are required unless one of the items is apunctuation symbol such as a parenthesis or a comma. For example:

CALL STEPMOM ( process-id ) ;

If there is no space between two items, spaces are not permitted. In the followingexample, there are no spaces permitted between the period and any other items:

$ process-name .# su-name

Line Spacing. If the syntax of a command is too long to fit on a single line, each continuationline is indented three spaces and is separated from the preceding line by a blank line.This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example:

ALTER [ / OUT file-spec / ] LINE

[ , attribute-spec ]...


18/182

About This Manual


xvi

Notation for Messages

!i and !o. In procedure calls, the !i notation follows an input parameter (one that passes datato the called procedure); the !o notation follows an output parameter (one that returnsdata to the calling program). For example:

CALL CHECKRESIZESEGMENT ( segment-id !i, error ) ; !o

!i,o. In procedure calls, the !i,o notation follows an input/output parameter (one that bothpasses data to the called procedure and returns data to the calling program). Forexample:

error := COMPRESSEDIT ( filenum ) ; !i,o

!i:i. In procedure calls, the !i:i notation follows an input string parameter that has acorresponding parameter specifying the length of the string in bytes. For example:

error := FILENAME_COMPARE_ ( filename1:length !i:i, filename2:length ) ; !i:i

!o:i. In procedure calls, the !o:i notation follows an output buffer parameter that has acorresponding input parameter specifying the maximum length of the output buffer inbytes. For example:

error := FILE_GETINFO_ ( filenum !i, [ filename:maxlen ] ) ; !o:i

Notation for MessagesThe following list summarizes the notation conventions for the presentation of displayedmessages in this manual.

Bold Text. Bold text in an example indicates user input entered at the terminal. For example:ENTER RUN CODE

? 123

CODE RECEIVED: 123.00

The user must press the Return key after typing the input.

Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed orreturned exactly as shown. For example:

Backup Up.

lowercase italic letters. Lowercase italic letters indicate variable items whose values aredisplayed or returned. For example:

p-register

process-name


19/182

About This Manual


xvii

Notation for Management Programming Interfaces

[ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed. Forexample:

Event number = number [ Subject = first-subject-value ]

A group of items enclosed in brackets is a list of all possible items that can be displayed,of which one or none might actually be displayed. The items in the list might bearranged either vertically, with aligned brackets on each side of the list, or horizontally,enclosed in a pair of brackets and separated by vertical lines. For example:

proc-name trapped [ in SQL | in SQL file system ]

{ } Braces. A group of items enclosed in braces is a list of all possible items that can bedisplayed, of which one is actually displayed. The items in the list might be arrangedeither vertically, with aligned braces on each side of the list, or horizontally, enclosed ina pair of braces and separated by vertical lines. For example:

obj-type obj-name state changed to state , caused by{ Object | Operator | Service }

process-name State changed from old-objstate to objstate{ Operator Request. }{ Unknown. }

| Vertical Line. A vertical line separates alternatives in a horizontal list that is enclosed inbrackets or braces. For example:

Transfer status: { OK | Failed }

% Percent Sign. A percent sign precedes a number that is not in decimal notation. The% notation precedes an octal number. The %B notation precedes a binary number. The%H notation precedes a hexadecimal number. For example:

%005400

P=% p - register E=%e - register

Notation for Management Programming InterfacesThe following list summarizes the notation conventions used in the boxed descriptionsof programmatic commands, event messages, and error lists in this manual.

UPPERCASE LETTERS. Uppercase letters indicate names from definition files; enter thesenames exactly as shown. For example:

ZCOM-TKN-SUBJ-SERV

lowercase letters. Words in lowercase letters are words that are part of the notation,including Data Definition Language (DDL) keywords. For example:

token-type


20/182

About This Manual


xviii

Change Bar Notation

!r. The !r notation following a token or field name indicates that the token or field isrequired. For example:

ZCOM-TKN-OBJNAME token-type ZSPI-TYP-STRING. !r

!o. The !o notation following a token or field name indicates that the token or field isoptional. For example:

ZSPI-TKN-MANAGER token-type ZSPI-TYP-FNAME32. !o

Change Bar NotationChange bars are used to indicate substantive differences between this edition of themanual and the preceding edition. Change bars are vertical rules placed in the rightmargin of changed portions of text, figures, tables, examples, and so on. Change barshighlight new or revised information. For example:

The message types specified in the REPORT clause are different in the COBOL85environment and the Common Run-Time Environment (CRE).

The CRE has many new message types and some new message type codes for oldmessage types. In the CRE, the message type SYSTEM includes all messagesexcept LOGICAL-CLOSE and LOGICAL-OPEN.


21/182


1-1

1Introducing the Open EnterpriseManagement Server

The OEM Gateway (OEM) provides client applications with an encapsulated interfacelayer to enterprise management frameworks.

The OEM consists of a Server component and one or more Adapter components. Clientapplications communicate with the Server component. The Server communicates withthe Adapter or Adapters on behalf of the clients, while the Adapters handlecommunication to and from the enterprise management framework.

Interfaces are implemented as ActiveX OLE servers/components. ActiveX minimizesthe impact and effort required to integrate existing clients. The interface provides clientssuch as Compaq state monitoring, performance monitoring, and command and control

graphical user interfaces (GUIs) with a simplified, encapsulated layer to operationsmanagement frameworks.

The OEM layer handles all details of the interface to enterprise managementframeworks. As a result, clients effectively communicate information in a uniform andconsistent manner with minimal impact to existing code.

OEM ArchitectureThe Open Enterprise Management architecture allows clients such as the CompaqAvailability Statistics and Performance (ASAP) monitor to communicate withEnterprise Management frameworks through a standard ActiveX interface. As a result,client applications do not have to be framework aware.

Conversely, framework commands are sent back to applications through callbacks to theOEM, with the OEM routing these commands to the appropriate client by encapsulatedstate arbitration. The clients themselves are not required to have knowledge of theproprietary callback formats of any given framework; the OEM translates callbacksfrom all frameworks to a standard OEM command format.

Clients need only integrate with the OEM Server to participate in any managementframework. The OEM Server and framework adapters are responsible for all routing andtranslation functions.


22/182

Introducing the Open Enterprise ManagementServer


1-2

Features of the OEM Server Version 3.0

The following figure shows the basic Open Enterprise Management architecture andcomponent pieces:

This design has the following architectural benefits: Encapsulates the client interface Minimizes the impact on client applications wanting to participate in enterprise

management Provides an adapter interface to enterprise management frameworks Provides client integration with enterprise management frameworks Provides state arbitration between multiple clients

Features of the OEM Server Version 3.0OEM Server 3.0 includes the following enhancements and new features: The ability to supply user-configurable icons for OEM entity and state information.

All OEM windows, including Alerts and Custom Views, will utilize the specifiedicons. In addition, any change to the OEM icon set is automatically communicatedto all clients and adapters, making it easy to keep the icon sets within the variouscomponents in sync.

Enhanced Client Request API, Adapter Request API, OEM Callback API, andClient Callback API. All of these APIs now include a SetIcons method, whichadapters or clients can utilize to cause the OEM to utilize a different icon set.


23/182



1-3

Hardware and Software Requirements

Hardware and Software RequirementsHardware and software required to run the Open Enterprise Management Server are asfollows.

Hardware Requirements IBM-compatible PC, Pentium-166 or higher 16 MB of RAM Mouse or compatible pointing device 10 MB of available disk space (20 MB during installation)

Software Requirements Microsoft Windows 95, Microsoft Windows 98, Microsoft Windows NT 4.0 (any

version), Microsoft Windows 2000 (any version), or Microsoft Windows ME. An optional framework adapter if you want to integrate OEM data with your

enterprise management framework

Obtaining SupportSupport for the OEM Server is available from the Compaq Computer CorporationGlobal Customer Support Center at (800) 255-5010.


24/182



1-4

Obtaining Support


25/182


2-1

2Installing the Open EnterpriseManagement ServerSetup

The OEM Server is installed as an ActiveX component as part of the setup of any clientapplication that uses it. There is no need to perform a stand-alone setup of the OEM.

Files InstalledThe OEM Server is installed in the Program Files\Tandem\OEM directory. System andlibrary files are installed in your Windows system directory. On Windows 95 or 98, thisis Windows Directory \SYSTEM. On Windows NT, this is Windows

Directory\ SYSTEM32. The following files are installed:

File Name Install Location

OEMSERV.CNT Application directory\OEM

OEMSERV.DOC Application directory\OEM

OEMSERV.EXE Application directory\OEM

OEMSERV.HLP Application directory\OEM

OEMSUPP.EXE Application directory\OEM

README.TXT Application directory\OEM

ALL CPUS.OEM Application directory\OEM\Views

ALL DISKS.OEM Application directory\OEM\Views

OBJECTS IN ERROR.OEM Application directory\OEM\Views

COMCTL32.OCX Windows system directory

CTL3D32.DLL Windows system directory

MFC40.DLL Windows system directory

MSVCIRT.DLL Windows system directory

MSVCRT.DLL Windows system directory

MSVCRT20.DLL Windows system directory

MSVCRT40.DLL Windows system directory


26/182

Installing the Open Enterprise Management Server


2-2

Registry Changes

Registry ChangesThe OEM Server updates the system registry with installation and configuration data.This information is stored under theHKEY_CURRENT_USER\SOFTWARE\TANDEM\OEM Server key.

Uninstalling the OEMThe OEM Server is installed as an ActiveX component as part of the setup of any clientapplication that uses it. To uninstall the OEM Server, uninstall any client applicationsthat use it.

OLEPRO32.DLL Windows system directory

VB40032.DLL Windows system directory

VEN2232.OLB Windows system directory

File Name Install Location


27/182


3-1

3Configuring the Open EnterpriseManagement Server

The behavior of the OEM Server and the appearance of the OEM windows can betailored to fit the needs of any user. The following subsections describe the five maincategories of OEM Server settings in detail: General Options on page 3-1 Adapter Options on page 3-8 Logging Options on page 3-12 Font Options on page 3-14

Advanced Options on page 3-15

General OptionsUse the OEM General Options dialog box to control the basic behavior of the OEMServer by: Specifying the Number of Reporting Levels on page 3-2 Including Intermediate-Level State Values in Frameworks and Display Windows on

page 3-2

Reusing Display Windows on page 3-3 Keeping Display Windows on Top on page 3-4 Automatically Closing Max Alerts Windows as They Are Used on page 3-4 Using Custom View Windows for Alerts and Max Alerts on page 3-5 Automatically Saving Custom View Definitions on page 3-5 Synchronizing the OEM Alerts Window and Client Applications on page 3-6 Setting the Icon Size on page 3-7

Choosing a New Icon Set on page 3-7


28/182

Configuring the Open Enterprise ManagementServer


3-2

Opening the OEM General Options Dialog Box

Opening the OEM General Options Dialog BoxTo open the OEM General Options dialog box:

1. Either: Right-click the OEM icon in the system tray. From the menu, choose Options. From the View menu of any OEM display window, choose Options .

The OEM Options dialog box appears.

2. Click the General tab if it is not already selected.

Specifying the Number of Reporting LevelsThe Reporting Levels value allows client applications to determine how many levels of object hierarchy are to be reported to the OEM. For example, a Reporting Levels valueof 1 could indicate that information should be reported only at the node level. AReporting Levels value of 2 might indicate that both node and entity class information(for example, DISK and CPU) should be reported.

To set the number of Reporting Levels:

1. Open the OEM Options dialog box and click the General tab. (See Opening theOEM General Options Dialog Box on page 3-2 .)

2. Enter the new value in the Reporting Levels field in the State Reporting panel, oruse the up arrow and down arrow to adjust the value.

3. Click OK or Apply to save the change, or click Cancel to discard it.

Including Intermediate-Level State Values in Frameworks and DisplayWindowsIn some cases, a client application might not be able to report on objects with the degreeof detail given by the Reporting Levels value and instead must supply intermediate-levelstate information. The OEM Server allows this and tracks this data in the same fashionas all other object state data. You can specify whether these intermediate values shouldbe ignored or passed through to enterprise management framework adapters andincluded in OEM display windows.

To specify intermediate values options:


2. Set the Include Intermediate Values option: To allow intermediate values to be passed to adapters and included in display

windows, in the State Reporting panel, select the Include IntermediateValues check box. Any intermediate values supplied by client applications areincluded in updates to framework adapters, and this state information displays inOEM Alerts, Max Alerts, and Custom View windows.


29/182



3-3

Reusing Display Windows

To ignore intermediate values, in the State Reporting panel, uncheck theInclude Intermediate Values check box. No intermediate values are includedin updates to framework adapters, and this state information does not appear inOEM Alerts, Max Alerts, or Custom View windows. However, the OEM Serverretains this data internally so that you can choose to include it at a later time.


ExampleAs an example of how the Include Intermediate Values feature works, assume thefollowing: The OEM Server Reporting Levels value has been set to 3. Client A reports \London\Disk\$System with state 7. Client B reports \London\Disk with state 5.

In this situation, Client A reports at the correct level. However, Client B supplies onlytwo levels of detail. Furthermore, the information Client B supplies specifies stateinformation on an intermediate level of the object hierarchy - \London\Disk. This isconsidered to be an intermediate level because Client A has already reported moredetailed information on \London\Disk, namely that $System has a state of 7. Given thisinformation, what data should be passed to the framework adapters, and what datashould appear in Alerts, Max Alerts, and Custom View windows? If Include Intermediate Values is checked, the \London\Disk\$System state of 7

and the \London\Disk state of 5 are passed to the framework adapters, and bothvalues appear in the appropriate display windows.

If Include Intermediate Values is not checked, only the \London\Disk\$Systemstate of 7 are passed through to the framework adapters, and only that value appears

in any display windows.

Reusing Display WindowsThe OEM Server can display several different types of windows, each of which iscustomized for a particular class of data. The OEM creates these windows on demand asrequests are received. The Re-Use Display Forms option controls whether the OEM usesan existing window of a given type to display new data or creates a new window foreach request.

To enable or disable display window reuse:


2. Set the Re-Use Display Forms option:

Note. The Re-Use Display Forms setting does not apply to Custom View windows. BecauseCustom Views display a subset of objects, each active Custom View has its own dedicated

window.


30/182


31/182



3-5

Using Custom View Windows for Alerts and MaxAlerts


2. Set the Close Max Alerts Window On Click option: To close Max Alerts windows once an object has been selected, in the Display

panel, check the Close Max Alerts Window On Click check box. Each MaxAlerts window closes after you select an object in it.

To leave Max Alerts windows open after an object has been selected, in theDisplay panel, clear the Close Max Alerts Window On Click check box. MaxAlerts windows are not closed as you select objects from them.


Using Custom View Windows for Alerts and Max AlertsThe OEM Server can use the new Custom View window format for displaying Alertsand Max Alerts. A Custom View window allows you to navigate through object

information in a hierarchical fashion rather than limiting you to a basic list of objectsand their states. You can also take advantage of the Custom View display formats, suchas choosing large icons or small icons. However, you cannot add object filters to theAlerts or Max Alerts view definitions or alter the existing filters.

To specify whether Custom View windows are used for Alerts and Max Alerts display:


2. Set the Use Custom View Alerts Window option: To use a Custom View window to display Alerts and Max Alerts data, in the

Display panel, check the Use Custom View Alerts Window check box. Alertsand Max Alerts are displayed using a predefined Custom View window. To use the standard Alerts and Max Alerts display windows, in the Display

panel, clear the Use Custom View Alerts Window check box. Alerts and MaxAlerts are displayed using the standard object list format.


Automatically Saving Custom View DefinitionsEach Custom View has an associated set of properties and parameters, which are stored

in an OEM view definition file. Each time you make a configuration change to a view,such as adding a specifier or repositioning the window on the screen, you must save theupdated information to the view definition file. To save this information automatically,enable the Auto Save View Definitions option. Each time a Custom View windowcloses, the OEM updates the definition file for that view and automatically preserves thelatest configuration information.


32/182



3-6

Synchronizing the OEM Alerts Window and ClientApplications

To specify whether Custom View definitions are automatically saved:


2. Set the Auto Save View Definitions option:

To save view definitions automatically when a Custom View window closes, inthe Display panel, check the Auto Save View Definitions check box. EachCustom View definition file is updated when the corresponding window isclosed.

To prevent the OEM from automatically saving view definitions, in the Display panel, clear the Auto Save View Definitions check box. To save viewdefinitions , click Save on the Custom View window toolbar or choose Save from the File menu of the Custom View window.


Synchronizing the OEM Alerts Window and Client ApplicationsWhenever the OEM receives an Alerts or Max Alerts callback from an enterprisemanagement framework, it displays information about the relevant objects in an Alertsor Max Alerts window. When you subsequently select an item in one of these windows,an Alerts or Max Alerts callback is sent to the client application that reported the item inquestion.

In some cases, however, you might prefer to have the client application(s) receive theAlerts or Max Alerts callback at the same time as the OEM. This strategy keeps theclient and OEM displays synchronized so that you can quickly see the detailed status of an object. The OEM supports this capability through the Synchronize Alerts and Clientsoption. When this feature is enabled, the OEM Server automatically passes all Alertsand Max Alerts callbacks to client applications. The client applications can then updatetheir windows at the same time the OEM is updating the Alerts or Max Alerts window.

To specify client application synchronization options:

1. Open the OEM Options dialog box and click the General tab if it is not alreadyselected. (See Opening the OEM General Options Dialog Box on page 3-2 .)

2. Set the Synchronize Alerts And Clients option: To keep the OEM Alerts window and clients synchronized, in the Display

panel, check the Synchronize Alerts And Clients check box. The OEM

automatically passes all Alerts and Max Alerts callbacks received from EMframeworks on to client applications. For other callbacks, the OEM Server stillupdates its Alerts window to contain information on the target object in additionto passing the callback to the appropriate client application.

To prevent the OEM from updating client applications automatically wheneveran Alerts or Max Alerts callback is received from an enterprise managementframework, in the Display panel, clear the Synchronize Alerts And Clients check box. The OEM updates only its own Alerts/Max Alerts windows; nonotification is passed to client applications. Any other callbacks received are


33/182



3-7

Setting the Icon Size

routed to the appropriate client, but OEM windows are not updated to show datafor the target object.


Setting the Icon SizeThe OEM Server's Alerts, Max Alerts, and Custom View windows contain an icon foreach object, each icon depicting an object's state. By default, these icons measure 16 by16 pixels. If you want, you can set the default icon size to 32 by 32.

To set the icon size:


2. Set the Use Large Icons option: To use the larger 32 by 32 icons, in the Display panel, check the Use Large

Icons check box. All Alerts, Max Alerts, and Custom View windows display thelarge icons. The Custom View windows Small Icon view still uses small icons,but the Large Icon, List, and Details views use large icons.

To use the smaller 16 by 16 icons, in the Display panel, clear the Use LargeIcons check box. All Alerts, Max Alerts, and Custom View windows display thesmall icons. The Custom View windows Large Icon view still uses large icons,but the Small Icon, List, and Details views use small icons.


Choosing a New Icon Set

The OEM utilizes entity and state icons to depict information about a given object.Instead of using the OEMs default set, you can supply your own set of icons.

To select a new icon set:


2. Click Choose Icons to display the Icon Server dialog box.

3. In the Icon Server dialog box, select the new icon set.

4. Click OK or Apply in the Icon Server dialog to use the new icon set, or click Cancel to discard the change.

Note. Only Alerts, Max Alerts, and Custom View windows support the 32 by 32 icon size; allother display windows always use 16 by 16 icons.


34/182



3-8

Choosing the Default Tiling Scheme

Choosing the Default Tiling SchemeAs the OEM creates display windows of a given type, it attempts to display them in anonoverlapping fashion to make it easier to view OEM data. The Tiling optiondetermines whether the OEM displays the windows side by side or top to bottom.

The Tiling option also controls how the OEM behaves when responding to tile requestsfrom framework adapters.

To specify the default tiling scheme:


2. Set the Tiling option: To tile windows from top to bottom first and then left to right, in the Tiling

panel, click the Top Down option. When a new window is created, the OEMtries to place it below an existing window of the same type. If no space isavailable, the OEM tries to place the window beside an existing window of thesame type.

To tile windows first from left to right and then top to bottom, in the Tiling panel, click the Side By Side option. When a new window is created, the OEMtries to place it beside an existing window of the same type. If no space isavailable, the OEM tries to place the window below an existing window of thesame type.


Adapter OptionsFramework adapters allow the OEM to communicate with various enterprisemanagement frameworks. This subsection describes the adapter options and how towork with them: Viewing the Adapter List on page 3-9 Adding an Adapter Entry on page 3-9 Updating an Adapter Entry on page 3-10 Deleting an Adapter Entry on page 3-10 Configuring a Framework Adapter on page 3-10 Adjusting Adapter Priority on page 3-11 Restoring Default Adapter Settings on page 3-11 Using the Add/Update Adapter Dialog on page 3-12


35/182



3-9

Viewing the Adapter List

Viewing the Adapter ListThe Adapter List contains information about each adapter, including the adapter name,its external OLE class name, and its state. Set these values using the Add/UpdateAdapter dialog.

To view the Adapter List:

1. Do one of the following: Right-click the OEM icon in the system tray and choose Options from the

menu. From the View menu of any OEM display window, choose Options .


2. Click the Adapters tab to display the currently defined adapters.

Adding an Adapter EntryFor the OEM Server to communicate with an enterprise management framework, youmust configure an adapter for that framework within the OEM environment. Theconfiguration information consists of the name of the adapter, its externally accessibleOLE class name, and a state specifying whether the adapter should be activated.

By default, two framework adapters are preconfigured in the OEM: the Compaq ObjectIntegration Layer (OIL) adapter and the CA TNG adapter.

To add an adapter entry:

1. Display the currently defined adapters by opening the OEM Options dialog box andselecting the Adapters tab. (See Viewing the Adapter List on page 3-9 .)

2. Click Add .

The OEM Server: Add Adapter dialog box appears.

3. Enter the name of the adapter in the Adapter Name field and the OLE class name inthe Class Name field.

4. Set the Active option: Click Yes if you want the adapter to be activated. Click No if you want to configure the adapter now but activate it at a later time.

5. Click OK in the OEM Server: Add Adapter dialog box to add the new entry to theadapter list. Click Cancel to cancel the operation.

6. Click OK or Apply in the OEM Options dialog box to save the changes. Click Cancel to discard any changes you have made.

For more information about specifying adapter properties, see Using the Add/UpdateAdapter Dialog on page 3-12 .


36/182


37/182



3-11

Adjusting Adapter Priority

2. Select the adapter you want to configure: If the Configure option is disabled, the selected adapter does not support any

user-configurable options. If the Configure option is enabled, the selected adapter supports

user-configurable options.

a. Click Configure to open the adapter configuration dialog.

b. In the adapter configuration dialog, change any values as needed. Thesesettings are specific to the selected adapter and are outside the control of theOEM Server.

c. Click either OK or Apply in the adapter configuration dialog box to savethe changes. Click Cancel to discard any changes you have made.


Adjusting Adapter PriorityThe OEM Server sends update information to the active framework adapters in the ordergiven by the adapter list. You can alter this order to give adapters higher or lower priorityas needed.

To adjust the priority of an adapter:

1. Display the currently defined adapters by opening the OEM Options dialog box andclicking the Adapters tab. (See Viewing the Adapter List on page 3-9 .)

2. Select the adapter you want to adjust.

3. Click + (plus) to move the adapter up in the list or (minus) to move it down.The adapter list is updated accordingly.


Restoring Default Adapter SettingsBy default, four framework adapters are preconfigured in the OEM: the Compaq ObjectIntegration Layer (OIL) adapter, the Tivoli NetView adapter, the HP OpenView adapter,and the CA TNG adapter.

To reset the adapter list to contain only default entries:

1. Display the currently defined adapters by opening the OEM Options dialog box andclicking the Adapters tab. (See Viewing the Adapter List on page 3-9 .)

2. Click Defaults .

The adapter list is updated to contain only the preconfigured adapters.


38/182



3-12

Using the Add/Update Adapter Dialog


Using the Add/Update Adapter DialogWhenever you add or update an adapter entry, the OEM Server: Add/Update Adapterdialog box appears. Use this dialog box to specify configuration information for thegiven adapter. The OEM Server: Add/Update Adapter dialog box contains these fields: Adapter Name

The Adapter Name field defines the name of the adapter within the OEM Serverenvironment. This name is used only within the OEM itself and can be any valueyou choose. It cannot contain a backslash (\) or a period (.), and it is limited to 255characters. It is not case-sensitive.

Class NameThe Class Name field specifies the name of the adapters externally accessible OLEinterface class. The OEM Server uses this interface to communicate with theadapter. The vendor of the adapter can supply you with the correct class name forthe particular adapter.

Active Flag

The Active flag controls whether the adapter is activated or deactivated by theOEM. If you select Yes, the OEM attempts to start the adapter. If successful, the

adapter is marked as Active in the Adapter List. The OEM passes all object andpop-up information to the adapter and passes all process callbacks from it. If theadapter cannot be started because it was not found or an error occurred, it ismarked as Not Installed in the Adapter List. The entry remains in the list, but theOEM does not attempt to communicate with the adapter until the problem iscorrected and the adapter is reactivated.

If you select No, the OEM shuts down the adapter if it is running and marks itInactive in the Adapter List. The entry remains in the list, but the OEM does notattempt to communicate with the adapter until it is reactivated.

Logging OptionsThe OEM Server maintains an in-memory log of error and status information related tothe OEM environment and also provides detailed tracing capabilities for interactionswith client applications and framework adapters. You can work with the logging andtracing options by: Setting the Size of the Log on page 3-13 Enabling API and Error Tracing on page 3-13

Note. This operation does not restore any adapter-specific settings. Use the adapterconfiguration to restore these settings.


39/182



3-13

Opening the OEM Logging Dialog Box

Enabling OEM Timer Tracing on page 3-14

Opening the OEM Logging Dialog BoxTo open the OEM Logging dialog box:




2. Click the Logging tab if it is not already selected.

Setting the Size of the Log

You can specify how many messages the OEM Server should retain in its in-memorylog. Storing more messages lets you look further back to detect problems or determinewhen parts of the OEM environment changed state, but it consumes more memory. TheOEM default setting of 500 messages should be more than sufficient for mostinstallations, but you can alter that value if necessary.

To set the number of log messages the OEM Server retains in the in-memory log:

1. Open the OEM Options dialog box and click the Logging tab. (See Opening theOEM Logging Dialog Box on page 3-13 .)

2. Type the new value in the Number Of Log Messages To Retain field, or use the uparrow and down arrow to adjust the value.


Enabling API and Error TracingThe OEM Server can support many clients and framework adapters simultaneously.Because these entities are all independent, it can be difficult to determine exactly what isgoing on when one or more pieces are not operating correctly.

To help resolve these situations, the OEM Server supplies an API call and error tracingmechanism so that you can view all interactions with the OEM Server. You canunderstand exactly how clients and framework adapters are using the OEM Server and

where things might be going wrong.Caution. API call and error tracing is disabled by default. You can enable it as needed, butdoing so can have a performance impact on the OEM Server. Use API call and error tracingonly to diagnose an existing problem.


40/182



3-14

Enabling OEM Timer Tracing

To enable or disable API and error tracing:


2. Set the API/Error Trace Enabled option:

To enable API call and error tracing, in the Tracing panel, check the API/ErrorTrace Enabled check box. To disable API call and error tracing, in the Tracing panel, clear the API/Error

Trace Enabled check box.


Enabling OEM Timer Tracing

It might appear that the OEM Server is not functioning correctly or is a bottleneck between clients and framework adapters. Under these circumstances, use the OEM timer

tracing facility to view how the OEM is managing its internal queues and how quickly itis responding to requests.

To enable or disable timer tracing:


2. Set the Timer Event Trace Enabled option: To enable timer tracing, in the Tracing panel, check the Timer Event Trace

Enabled check box. To disable timer tracing, in the Tracing panel, clear the Timer Event Trace

Enabled check box.


Font OptionsUse the Fonts tab to alter the display font used in Alerts, Max Alerts, Clients, Objects,

Pop-ups, and Log display windows. You can change the font itself, adjust the font size,and specify the bold, italic, strikethrough, and underline styles.

To alter the OEM font settings:



Caution. Timer tracing is disabled by default. You can enable it as needed, but doing so canhave a severe performance impact on the OEM Server. Use timer tracing only to diagnose anexisting problem.


41/182



3-15

Advanced Options


2. Click the Fonts tab.

3. Set the desired font options.

The list of font names varies from system to system, depending on which fonts are

installed in the given environment. The available font sizes can also vary. If aparticular size is invalid for a specific font, the OEM automatically uses the closestavailable font size.

4. Click OK or Apply to save the changes, or click Cancel to discard them.

Advanced OptionsUse the Advanced Options dialog box to access OEM Server advanced configurationsettings and windows that display information about the OEMs internal data and status.This subsection describes:

Limiting the Number of Icons Used on page 3-15 Supplementary Display Windows on page 3-16

Opening the OEM Advanced Options Dialog Box

To open the OEM Advanced Options dialog box:


menu.

From the View menu of any OEM display window, choose Options .The OEM Options dialog box appears.

2. Click the Advanced tab if it is not already selected.

Limiting the Number of Icons UsedThe OEM Server uses entity and state icons to show the type and state of objects in theOEM internal database. Because of the number of entity types and states, the totalnumber of icons in the OEMs entity and state icon matrix can be quite large. Thissituation is not a problem on Windows NT systems because Windows NT is designed to

handle this type of load. On Windows 95 and Windows 98 systems, however, iconsoccupy space in a GDI pool shared by all applications and the operating system. Thisspace is a limited resource, and the full OEM icon matrix could consume a significantportion of it.

To alleviate this problem, you can enable the OEMs Show State Icons Only option. TheOEM Server displays only an objects state icon; the entity type icon is not shown. TheOEMs GDI resource consumption is reduced by more than 75 percent, making it easierto run other applications concurrently with the OEM.


42/182


43/182


4-1

4 OEM WindowsThe OEM Server can display several different types of windows, each containing aparticular class of OEM data. These windows are created either in response to directuser requests from OEM menus or as a result of callbacks from framework adapters. The

behavior of a given type of window is always the same, regardless of the reason for itscreation.

The following subsections describe each of these OEM window types: The Alerts Window on page 4-1 The Max Alerts Window on page 4-6 The Clients Window on page 4-11 The Objects Window on page 4-15 The Popups Window on page 4-21 The Popup Navigation Window on page 4-26 The Log Window on page 4-29 The Statistics Window on page 4-34 The Icons Window on page 4-38 The Trace Window on page 4-39 The About Window on page 4-40

The Alerts WindowThe Alerts window serves as the main window of the OEM Server. It contains a list of objects in the OEM database sorted by object state from highest to lowest. This givesyou an easy way to view, in priority order, the state of monitored objects in yournetwork.

By default, the Alerts window displays a list of all objects contained in the OEMdatabase. However, enterprise management frameworks can limit this list to a subset of objects by supplying a filter string on Alerts callbacks. If such a filter is supplied, onlythose objects that match it are displayed. For example, if an enterprise managementframework supplied the filter \NewYork\DISK, only disk drives on \NewYork wouldbe displayed in the Alerts window.One object can have multiple entries in the OEM database if it is reported on by morethan one client application. Because these clients are, in most cases, reporting ondifferent properties of the object, the reported states could be different. In this situation,the OEM shows all reported states for the object in the Alerts window. For example, if client A reports object X with state 5, and client B reports it with state 3, both entrieswould appear in the Alerts window. Only the highest state for X, however, is reported tothe enterprise management frameworks.


44/182

OEM Windows


4-2

Opening an Alerts Window

Opening an Alerts WindowYou can open an Alerts window using any of the following methods: Right-click the OEM icon in the system tray and choose Alerts from the menu. From an OEM Max Alerts window View menu, choose Alerts . From an enterprise management framework menu, choose Alerts .

The Re-Use Display Forms option setting affects how Alerts windows are created: If Re-Use Display Forms is checked, an Alerts window is created the first time you

choose Alerts from a menu. If you subsequently choose Alerts from a menu again,the existing Alerts window is used to display the newly requested data.

If Re-Use Display Forms is cleared, a new Alerts window is created every time youchoose Alerts from a menu.

Alerts Window Fields

The Alerts window contains the following fields for each object:Path The complete path for the object. For example, if the object

added is \CHICAGO\DISK\$DATA, Path contains \CHICAGO\DISK.

Name The name of the object. For example, if the object added is \CHICAGO\DISK\$DATA, Name contains $DATA.

State The numeric state of the object. This value is defined by theclient application that reported the object.

Context The client-defined context data associated with the object. In

general, this field contains descriptive text identifying the reasonthe object is in its reported state.

Client Name The name of the client application that reported this object.


45/182

OEM Windows


4-3

Alerts Window Menus

Alerts Window MenusThe Alerts window View and Help menus provide access to common OEM displaywindow functions and settings.

View MenuItems in the View menu control the Alerts window and how data is displayed in it.

Help MenuItems in the Help menu provide access to information about using the OEM Server.

Sorting Alerts Window ItemsTo sort the Alerts list by any of the Alerts fields, click the column heading by which youwant to sort: Click once to sort objects in ascending order. Click twice to sort objects in descending order.

Menu Item Action Performed

Alerts Displays a list of all objects and their states

Max Alerts Displays a list of all objects whose state is equal to the higheststate recorded in the OEM database

New Creates a new Alerts or Max Alerts window

Locked Locks or unlocks the window

Stay On Top Enables or disables the On Top property of the windowRefresh Refreshes the data in the window

Size Columns Sizes the display columns according to their contents, saveddimensions, or OEM default dimensions

Align Windows Aligns OEM windows using the dimensions of the currentwindow

Options Opens the OEM options dialog

Close Closes this window

Close All DisplayWindows

Closes all OEM display windows


Contents Displays the Help file table of contents

Search Displays the Help file search dialog

About Displays OEM Server version information


46/182

OEM Windows


4-4

Sizing Alerts Window Columns

Sizing Alerts Window ColumnsYou can resize the columns in the Alerts window: To resize each of the columns in the window, select the divider between column

headings and drag it right or left as desired.

To resize all columns at once:1. From the View menu, choose Size Columns .

2. Choose Defaults , Size To Window , or Size To Contents . The behavior of eachof these options is as follows:

The OEM saves the adjusted column widths in the system registry. These values areused the next time an Alerts window is created.

Aligning Alerts WindowsYou can resize and align all Alerts windows using the dimensions of the currentlyselected Alerts window: To align Alerts windows, from the View menu, choose Align Windows . All Alerts

windows are tiled and resized to match the current window. To specify the tiling method, choose Top Down or Side By Side from the OEM

Options window General tab.

Locking the Alerts Window

The OEM Server automatically updates all display windows whenever it receives newdata from a client application. In some cases, you might want to prevent this action fromoccurring for a particular window; for example, if you are analyzing the data in thewindow and want to ensure that it does not change until you are finished.

To lock a display window, from the View menu, choose Locked .The indicator (Locked) is appended to the window title, and the OEM does notupdate the window contents if new data is received. You can manually update thewindow at any time by choosing Refresh from the View menu.


Defaults Sizes each column using the saved value for that column

Size To Window Sizes each column using a fixed percentage of availablespace

Size To Contents Sizes each column based on the largest item in thecolumn


47/182

OEM Windows


4-5

Keeping the Alerts Window on Top

To unlock a display window and re-enable updates, choose Locked from the View menu again.

The (Locked) indicator disappears, and the OEM updates the window the next timenew data is received.

Repeatedly choosing Locked from the View menu toggles the locked attribute onand off.

Keeping the Alerts Window on TopYou can specify whether each new Alerts window created by the OEM always remainson top. Windows with the On Top property enabled cannot be obscured by any otherwindow on your system.

When the OEM creates a new Alerts window, it sets the windows On Top propertybased on the Display Forms Stay On Top option setting. If Display Forms Stay On Top is checked, the new window is created with its On

Top property enabled. If Display Forms Stay On Top is not checked, the new window is created with its

On Top property disabled.

To override the default value and toggle the On Top property of an individual window: If Stay On Top is checked on the View menu, the current window is an On Top

window. Choose Stay On Top from the View menu to disable the On Top attribute. If Stay On Top is not checked on the View menu, the current window is not an On

Top window. From the View menu, choose Stay On Top to enable the On Topattribute.

Repeatedly selecting Stay On Top from the View menu toggles the On Topattribute on and off.

Refreshing Alerts Window ContentsBecause the OEM Server automatically updates all display windows whenever new datais received from a client application, there is usually no reason to perform a manualrefresh. However, if a window has been locked for some period of time, it might notcontain current data. To update the contents with the latest data, from the View menu,choose Refresh .

Creating a New Alerts WindowTo create a new Alerts window to view a different set of data:

1. From the View menu, choose New .2. Choose Alerts Window to create a new Alerts window.


48/182

OEM Windows


4-6

Navigating to Client Applications

Navigating to Client ApplicationsThe OEM Server gives you access to active client applications so that you can viewdetailed information on objects and their states. To navigate to the client that reported aparticular object, click the object in the Alerts window. An Alert message is sent to theassociated client and that client then provides detailed information about the objects

state and history.Closing the Alerts Window

To close the Alerts window, choose Close from the View menu, or click the close box.

The Max Alerts WindowThe Max Alerts window is similar to the Alerts window, except that it only containsinformation on objects whose state is equal to the highest reported state in the OEMdatabase. For example, if the highest state of any object in the OEM database is 7, the

Max Alerts window contains only objects whose state is equal to 7. These objects aresorted by object name. The Max Alerts window allows you to quickly view the list of monitored objects in your network that need the most immediate attention.

By default, the Max Alerts window displays a list of all objects contained in the OEMdatabase whose state is equal to the highest reported state. However, enterprisemanagement frameworks can limit this to a subset of objects by supplying a filter stringon Max Alert callbacks. If such a filter is supplied, the OEM compares the states of allobjects that match the filter and displays only the object or objects with the highest statevalue. For example, if an enterprise management framework supplies the filter

\NewYork\DISK, only the disk drive or drives on \NewYork with the highest state valueare displayed in the Max Alerts window.

One object can have multiple entries in the OEM database if it is reported on by morethan one client application. If these multiple entries have the same state value, and thestate values are equal to the maximum reported state, each of the multiple entriesappears in the Max Alerts window.

Opening a Max Alerts WindowYou can open a Max Alerts window using any of the following methods: Right-click the OEM icon in the system tray and choose Max Alerts from the

menu.

From an OEM Alerts window View menu, choose Max Alerts . From an enterprise management framework menu, choose Max Alerts .

In this case, a Max Alerts window is created only if more than one object is at thehighest state. If a single object is at the highest state, the OEM automatically sends aMax Alert message to the client application that reported that object.


49/182

OEM Windows


4-7

Max Alerts Window Fields

The setting of the Re-Use Display Forms option affects how Max Alerts windows arecreated: If the Include Intermediate Values option is checked, a Max Alerts window is

created the first time you choose Max Alerts from a menu. If you subsequentlychoose Max Alerts from a menu again, the existing Max Alerts window displays thenewly requested data.

If Re-Use Display Forms is cleared, a new Max Alerts window is created everytime you choose Max Alerts from a menu.

Max Alerts Window Fields

The Max Alerts window contains the following fields for each object:

Max Alerts Window MenusThe Max Alerts window View and Help menus provide access to common OEM displaywindow functions and settings.

View Menu

Items in the View menu control the Max Alerts window and how data is displayed in it.

Path The complete path for the object. For example, if the objectadded was \CHICAGO\DISK\$DATA, Path would contain

\CHICAGO\DISK.

Name The name of the object. For example, if the object added was \CHICAGO\DISK\$DATA, Name would contain $DATA.

State The numeric state of the object. This value is defined by theclient application that reported the object.

Context The client-defined context data associated with the object. Ingeneral, this field contains descriptive text identifying the reasonthe object is in its reported state.

Client Name The name of the client application that reported this object.


Alerts Displays a list of all objects and their states.

Max Alerts Displays a list of all objects whose state is equal to the higheststate recorded in the OEM database.

New Creates a new Alerts or Max Alerts window.

Locked Locks or unlocks the window.

Stay On Top Enables or disables the On Top property of the window.

Close On Use Enables or disables the Close On Use property of the window.


50/182

OEM Windows


4-8

Sorting Max Alerts Window Items

Help MenuItems in the Help menu provide access to information about using the OEM Server.

Sorting Max Alerts Window Items

To sort the Max Alerts list by any of the Max Alerts fields, click the column heading bywhich you want to sort:

Clicking once sorts objects in ascending order. Clicking twice sorts objects in descending order.

Sizing Max Alerts Window Columns

You can resize the columns in the Max Alerts window: To resize each of the columns in the window, select the divider between column

headings and drag it right or left as desired. To resize all columns at once:

1. From the View menu, choose Size Columns .

Refresh Refreshes the data in the window.

Size Columns Sizes the display columns according to their contents, saveddimensions, or OEM default dimensions.

Align Windows Aligns OEM windows using the dimensions of the current

window.Options Opens the OEM options dialog.

Close Closes this window.


Closes all OEM display windows.

Menu Item Action PerformedContents Displays the Help file table of contents.

Search Displays the Help file search dialog.

About Displays OEM Server version information.


51/182

OEM Windows


4-9

Aligning Max Alerts Windows

2. Choose Defaults , Size To Window , or Size To Contents . The behavior of eachof these options is as follows:

The OEM saves the adjusted column widths in the system registry. These values areused the next time a Max Alerts window is created.

Aligning Max Alerts WindowsYou can resize and align all Max Alerts windows using the dimensions of the currently

selected Max Alerts window. To align Max Alerts windows, choose Align Windows from the View menu. AllMax Alerts windows are tiled and resized to match the current window.

To specify the tiling method, from the OEM Options window General tab, chooseTop Down or Side By Side .

Locking the Max Alerts Window

The OEM Server automatically updates all display windows whenever new data isreceived from a client application. In some cases, you might want to prevent this actionfrom occurring for a particular window; for example, if you are analyzing the data in thewindow and want to ensure that it does not change until you are finished.To lock and unlock a window: To lock a display window, from the View menu, choose Locked .

The indicator (Locked) is appended to the window title, and the OEM does notupdate the window contents if new data is received. You can manually update thewindow at any time by choosing Refresh from the View menu.

To unlock a display window and reenable updates, choose Locked from the View menu again.

The (Locked) indicator disappears, and the OEM updates the window the next timenew data is received. Repeatedly selecting Locked from the View menu toggles the locked attribute on

and off.


Defaults Sizes each column using the saved value for that column.

Size To Window Sizes each column using a fixed percentage of availablespace.

Size To Contents Sizes each column based on the largest item in thecolumn.


52/182

OEM Windows


4-10

Keeping the Max Alerts Window on Top

Keeping the Max Alerts Window on TopYou can specify whether each new Max Alerts window created by the OEM alwaysremains on top. Windows with the On Top property enabled cannot be obscured by anyother window on your system.

When the OEM creates a new Max Alerts window, it sets the windows On Topproperty based on the Display Forms Stay On Top option setting: If Display Forms Stay On Top is checked, the new window is created with its On

Top property enabled. If Display Forms Stay On Top is not checked, the new window is created with its

On Top property disabled.

To override the default value and toggle the On Top property of an individual window: If Stay On Top is checked on the View menu, the current window is an On Top

window. To disable the On Top attribute, choose Stay On Top from the View menu .

If Stay On Top is not checked on the View menu, the current window is not an ontop window. To enable the On Top attribute, choose Stay On Top from the View menu.

Repeatedly selecting Stay On Top from the View menu toggles the On Topattribute on and off.

Refreshing Max Alerts Window Contents

Because the OEM Server automatically updates all display windows whenever new datais received from a client application, there is usually no reason to perform a manualrefresh. However, if a window has been locked for some period of time, it might notcontain current data. To update the contents with the latest data, choose Refresh fromthe View menu.

Creating a New Max Alerts Window

To create a new Max Alerts window to view a different set of data:

1. From the View menu, choose New .2. Choose Max Alerts Window to create a new Alerts window.

Navigating to Client Applications

The OEM Server gives you access to active client applications so you can view detailedinformation on objects and their states. To navigate to the client that reported aparticular object, click the object in the Max Alerts window. A Max Alert message issent to the associated client and that client then provides detailed information about theobjects state and history.


53/182


54/182

OEM Windows


4-12

Clients Window Menus

Clients Window MenusThe Clients window View and Help menus provide access to common OEM displaywindow functions and settings.

View MenuItems in the View menu control the Clients window and how data is displayed in it.

Class Name The name of the client applications OLE callback class, if onewas supplied.

Window Mgt. A flag indicating whether the client will participate in windowmanagement callbacks (for example, tile or cascade) from theOEM. This value is updated whenever the OEM attempts toperform a window management operation, so the value displayedin the Clients window might not be current if the clientapplication has changed its setting since the last windowmanagement callback.

Instance ID The index of the OLE object used by the client to communicatewith the OEM.


Clients Displays a list of all active client applications.

Objects Displays a list of all objects contained in the OEM database.

Popups Displays a list of all popup menu items defined in the OEM.

Locked Locks or unlocks the window.Stay On Top Enables or disables the On Top property of the window.

Refresh Refreshes the data in the window.

Size Columns Sizes the display columns according to their contents, saveddimensions, or OEM default dimensions.

Align Windows Aligns OEM windows using the dimensions of the currentwindow.

Options Opens the OEM options dialog.

Close Closes this window.


Closes all OEM display windows.


55/182


56/182

OEM Windows


4-14

Locking the Clients Window

To specify the tiling method, choose Top Down or Side By Side from the OEMOptions window General tab.

Locking the Clients WindowThe OEM Server automatically updates all display windows whenever new data is

received from a client application. In some cases, you might want to prevent this fromoccurring for a particular window; for example, if you are analyzing the data in thewindow and want to ensure that it does not change until you are finished.

To lock and unlock a window: To lock a display window, choose Locked from the View menu.

The indicator (Locked) is appended to the window title, and the OEM does notupdate the window contents if new data is received. You can manually update thewindow at any time by choosing Refresh from the View menu.

To unlock a display window and re-enable updates, choose Locked from the View

menu again.The (Locked) indicator disappears, and the OEM updates the window the next timenew data is received.

Repeatedly selecting Locked from the View menu toggles the locked attribute onand off.

Keeping the Clients Window on TopYou can specify whether each new Clients window created by the OEM always remainson top. Windows with the On Top property enabled cannot be obscured by any other

window on your system.When the OEM creates a new Max Alerts window, it sets the windows On Topproperty based on the Display Forms Stay On Top option setting: If Display Forms Stay On Top is checked, the new window is created with its On

Top property enabled. If Display Forms Stay On Top is not checked, th

Oem Users Guide

Documents

Transcript of Oem Users Guide