HPUX ovw[1]
ovw(1) ovw(1)
NAME
ovw - OpenView Windows graphical user interface
SYNOPSIS
ovw [-ro|-rw] [-map map_name] [-submap submap_name]
ovw -verify
ovw -fields
ovw -server
DESCRIPTION
The ovw program is the OpenView Windows graphical user interface for
the Openview network and systems management environment. Openview
Windows is the graphical user interface into the Openview network and
systems management environment. It provides a graphical map of the
environment being managed. The map contains a hierarchy of submaps
accessible via symbols and a set of pull-down menus for access to map
operations and to applications.
For detailed information on all aspects of the map and the
accompanying operations, consult the on-line Help system provided with
ovw, available under the Help menu item on the menu bar.
ovw will only run after the OpenView Windows object database daemon
ovwdb has first been started with ovstart on the management server.
See ovwdb(1M) for more information on the OpenView Windows object
database.
At startup, OpenView Windows reads application and symbol registration
files to define the symbols that are available for the map and the
applications that are integrated into the menu bar and executable
symbols. For more information on registration files, their syntax, and
how they are processed, see OVwRegIntro(5).
ovw can use a map database and object database on a remote management
server. The ovwsetupclient command must first be used to configure the
system as a distributed console. See ovwsetupclient(1M) and HP
OpenView Installation and Configuration Guide on configuring a
distributed ovwconsole.
For full details on using ovw, consult the HP OpenView Windows User's
Guide.
Parameters
In addition to most standard X Toolkit command-line options, ovw
supports the following options.
-fields Creates the fields defined in the currently installed field
registration files in ovw object database. When started with
ovw will not start a normal "windowed" session. It will only
process field registration files during this processing.
Hewlett-Packard Company - 1 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
-map map_name
Open map map_name. Create the map map_name if it does not
exist. The default behavior is to open a configured default
user map based on the user's UID. If no user default map is
configured, ovw opens the map named default.
-ro Open all maps as read-only. This option must not be
specified at the same time as the -rwoption.
-rw Open all maps as read-write if possible. This option is the
default behavior and is only useful if the X-Resources
specify read-only as a default behavior.
-server Print the name of the management server host, the system
where ovw will store map and object information. This option
is useful for verifying that a system configured as a
distributed client with ovwsetupclient(1M) is correctly
recognizing the server host as its management databases
server. When started with this option ovw will not start a
normal windowed session.
-submap submap_name
Open submap submap_name as the initial submap if it exists
on the map being opened. If it does not exist, then ovw
initially opens the home submap of the map being opened.
-verify Check the syntax for all the installed application, symbol
type, and field registration files. Verify the semantics of
the application registration files and report conflicts
among application registration information. When started
with this option ovw will not start a normal "windowed"
session.
Application Authorization
ovw permits applications to programatically connect to it from other
systems. It uses a simple authorization file to control which hosts,
users, and applications are permitted to connect to it. The format of
this file is similar to that of the system hosts.equiv(4) file. The
default system-wide authorization file is
$OV_SHARED_CONF_PATH/ovw.auth. Individual users can specify additional
authroizations in their own file, $HOME/ovw.auth, or in the file
specified by the userAuthFile X resource.
The file contains lines specifying the authorized hosts, users, and
applications. Each line lists a single host, user, and application
list authorized to connect to ovw. The format of each line of the file
is:
hostname username appname1 appname2 appname3
Hewlett-Packard Company - 2 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
If hostname is a +, this represents any host name. If username is a +,
this represents any user name. If no applications are specified, any
application is assumed authorized. If a - preceeds a host or user
name, the line explicitly denies access from that host or by that
user.
If no application name is listed on the line, all applications are
authorized for the listed host and user. Otherwise, only those
applications listed are authorized to connect to ovw sessions from the
listed host and user. Note that the application names listed in the
authorization file must match the registered name of the application,
with the exception that white space in the registered application name
should be represented with underscores.
The example authroization file created at installation contains
examples and more explanation of the file format. More examples of the
ovw authorization file are included below.
Resources
The following resources are used in the X-windows environment and can
be specified using the standard X-windows resource specification
methods:
mapBackground
This resource specifies the background color of the ovw
submap windows.
introImage
This resource is an absolute path specification for the
image displayed at the introduction of the ovw session and
in the About OpenView Windowsdialog. The image file can be a
bitmap, XPM, GIF, JPEG, or TIF image. The image is scaled so
that the dialog does not consume a large area on the screen.
If the resource is a relative path, the path is assumed
relative to the $OV_BITMAP_PATHdirectory.
mapWidth This resource specifies the initial default width of ovw
submap windows.
mapHeight This resource specifies the initial default height of ovw
submap windows.
extraSpacing
This resource specifies the extra amount of space in pixels
to put between the symbols on the following five dialog
boxes: Legend, Add Object, LocateByStatus, LocateByType, and
Change Symbol Type.
symbolInteriorColor
This resource specifies the color used to "fill" in the icon
symbols used in ovw.
Hewlett-Packard Company - 3 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
symbolEdgeColor
This resource specifies the color used to draw the basic
internal patterns in the ovw icon symbols.
borderColor
This resource specifies the color used to draw the outer
shapes of the ovw icon symbols.
labelColor
This resource specifies the color used in drawing the
characters for the ovw symbols labels.
labelBackground
This resource specifies the background color used in drawing
the labels for ovwsymbols.
lineColor This resource specifies the color used to draw miscellaneous
lines such as the bus segment. It is not the color for a
connection.
unmanagedStatusLineColor
This resource specifies the color used to draw connections
with an unmanaged status.
testingStatusLineColor
This resource specifies the color used to draw connections
with a testing status.
restrictedStatusLineColor
This resource specifies the color used to draw connections
with a restricted status.
disabledStatusLineColor
This resource specifies the color used to draw connections
with a disabled status.
unknownStatusLineColor
This resource specifies the color used to draw connections
with an unknown status.
upStatusLineColor
This resource specifies the color used to draw connections
with a normal (up) status.
warningStatusLineColor
This resource specifies the color used to draw connections
with a warning status.
marginalStatusLineColor
This resource specifies the color used to draw connections
with a marginal status.
Hewlett-Packard Company - 4 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
majorStatusLineColor
This resource specifies the color used to draw connections
with a major status.
downStatusLineColor
This resource specifies the color used to draw connections
with a critical (down) status.
lineHighlightColor
This resource specifies the color used to draw a highlighted
connection.
unmanagedStatusColor
This resource specifies the background color for icons with
an unmanaged status.
testingStatusColor
This resource specifies the background color for icons with
a testing status.
restrictedStatusColor
This resource specifies the background color for icons with
a restricted status.
disabledStatusColor
This resource specifies the background color for icons with
a disabled status.
unknownStatusColor
This resource specifies the background color for icons with
an unknown status.
upStatusColor
This resource specifies the background color for icons with
a normal (up) status.
warningStatusColor
This resource specifies the background color for icons with
a warning status.
marginalStatusColor
This resource specifies the background color for icons with
a marginal status.
majorStatusColor
This resource specifies the background color for icons with
a major status.
downStatusColor
This resource specifies the background color for icons with
a critical (down) status.
Hewlett-Packard Company - 5 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
selectColor
This resource specifies the color to draw the "select"
square around selected ovwsymbols.
mapName This resource specifies the map to open. This resource
overrides an option specified using the ovw Configure Map
menu. It is -map" option.
submapName
This resources specifies the initial submap to open. It is
overridden with the " -submap" option.
readOnly This resource is used to specify how to open the map for
user modifications. True indicates the map is to be opened
read-only. False indicates the map is to be opened read-
write (unless other factors dictate the map can only be
opened read-only).
closeTimeout
If non-zero, this resource specifies how long (in seconds)
ovw will wait for map applications ovwMapClose event before
ovw will continue without an application acknowledgment. If
this resource is 0 (the default), ovw will wait forever.
Closing the map without waiting for all map applications to
acknowledge the ovwMapClose event is very likely to
queryAddSymbolTimeout
This resource specifies how long (in seconds) to wait for an
application to respond to the ovwQueryAddSymbol event before
ovw reports that the application did not respond.
queryConnectSymbolsTimeout
This resource specifies how long (in seconds) to wait for an
application to respond to the ovwQueryConnectSymbols event
before ovw reports that the application did not respond.
queryDeleteSymbolsTimeout
This resource specifies how long (in seconds) to wait for
all queried applications to respond to the
ovwQueryDeleteSymbols event before ovw continues to process
the cut ovw determines which symbols it can cut or delete
and which it must deny because of the application(s) that
did not respond.
queryDescribeChangeTimeout
This resource specifies how long (in seconds) to wait for an
application to respond to the ovwQueryDescribeChange event
before ovw reports that the application did
queryAppConfigChangeTimeout
This resource specifies how long (in seconds) to wait for an
Hewlett-Packard Company - 6 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
application to respond to an ovwQueryAppConfigChange event
before ovw reports that the application did
clickDelay
This resource specifies how close together (in milliseconds)
successive mouse clicks must be to activate the double click
behavior on the submap windows.
smallFont This resource specifies the font to use for the smallest
(many characters) size labels (should be an 8 point font).
size10Font
This resource specifies the font to use for small size
labels (should be a 10 point font).
size20Font
This resource specifies the font to use for medium size
labels (should be a 12 point font).
size30Font
This resource specifies the font to use for large (few
characters) size labels (should be a 14 point font).
defaultRadius
This resource specifies the default radius for map symbols
in pixels. This is the standard size used for scaling
symbols. The maximum size of a symbol is derived from the
default radius (the maximum radius is 5/3 of the default
radius). The default is "15".
minimumSubmapBorder
This resource specifies the minimum border on the left and
right sides of a submap window in pixels. If long symbol
labels are used, this value can be increased to prevent
labels from being obscured at the edge of the window. The
default is "30".
submapDialog*XmList*FontList
This resource specifies the fonts to use for the list of
submaps in the "Submaps in Map" dialog box. The first value
is the font to use for submaps which occur only once.
Submaps which appear multiple times in the hierarchy use the
initial font if this occurrence (in the list) is the one
which will show the children of this submap. Only one of the
multiple instances of a particular submap will appear in the
"standard" font. The other instances will be shown with the
font specified with the "=duplicate" specification. For more
information on FontList specification see the X11 and Motif
documentation.
Hewlett-Packard Company - 7 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
userAuthFile
This resource specifies an absolute path for a user
authorization file. See Application Authorization for an
explanation of the ovw authorization file.
Object Database Fields
The following fields are defined in the OVW field registration file
and are available for developer use. There fields are placed in the
OVW object database when ovw -fields is run. For more information on
ovw field registration see OVwRegIntro(5).
OVW Registration Fields
center tab(@); cBcBcBcB llll.
Object Purpose@OVwDb Field Name@OVw FieldType@Field Flags @@@ Global
Capabilities@"vendor"@ovwEnumField@T{ Capability General Locate T}
@@@ Global Name Fields@"Selection Name"@ovwStringField@Name Loc @"IP
Hostname"@ovwStringField@Name Locate @@@ Location
Capabilities@"isNetwork"@ovwBooleanField@Capability
@"isInternet"@ovwBooleanField@Capability @@@ Segment
Capabilities@"isSegment"@ovwBooleanField@Capability
@"isBusSegment"@ovwBooleanField@Capability
@"isStarSegment"@ovwBooleanField@Capability
@"isTokenRingSegment"@ovwBooleanField@Capability
@"isFDDIRingSegment"@ovwBooleanField@Capability
@"isSerialSegment"@ovwBooleanField@Capability @@@ Nodal
Capabilities@"isNode"@ovwBooleanField@Capability
@"isDevice"@ovwBooleanField@Capability
@"isComputer"@ovwBooleanField@Capability
@"isConnector"@ovwBooleanField@Capability
@"isBridge"@ovwBooleanField@Capability
@"isRouter"@ovwBooleanField@Capability
@"isHub"@ovwBooleanField@Capability
@"isRepeater"@ovwBooleanField@Capability @@@ Computer
Types@"isPC"@ovwBooleanField@Capability
@"isWorkstation"@ovwBooleanField@Capability
@"isMini"@ovwBooleanField@Capability
@"isMainFrame"@ovwBooleanField@Capability @@@ Device
Types@"isPrinter"@ovwBooleanField@Capability
@"isAnalyzer"@ovwBooleanField@Capability @@@ Connection
Capabilities@"isConnection"@ovwBooleanField@Capability @@@ Interface
Capabilities@"isCard"@ovwBooleanField@Capability
@"isInterface"@ovwBooleanField@Capability
@"isStarInterface"@ovwBooleanField@Capability
@"isThinInterface"@ovwBooleanField@Capability
@"isThickInterface"@ovwBooleanField@Capability
@"isSerialInterface"@ovwBooleanField@Capability @@@ T{ Client/Server
Capabilities T}@"isClient"@ovwBooleanField@Capability
@"isServer"@ovwBooleanField@Capability @@@ Software
Capabilities@"isSoftware"@ovwBooleanField@Capability @@@ IP
Specific@"isIP"@ovwBooleanField@Capability
Hewlett-Packard Company - 8 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
EXAMPLES
The following is an example of the contents of the ovwauthorization
file:
# You should usually authorize any application run by the current
user.
# To do this, be sure to have a single line listing the name of
# the system(s) where you run ovw.
#
# For example, if my server system is named "bigsystem" and a
client
# system is named "hohum", I should list each of them on a
# separate line in this file.
bigsystem
hohum
# This next line permits user shem from host blimp to run the
# application "Toaster Manager". Note that, since the application
# name include white space, I must represent the whitespace as
# with the underscore character in the authorization file.
shem blimp Toaster_Manager
# This line permits the super user from any host to run any
application.
+ root
# This line denies any application access from host "badguy"
-badguy
AUTHOR
ovw was developed by HP.
FILES
HP-UX 9.x and HP-UX 10.x
/usr/lib/X11/app-defaults/OVw
SunOS 4.1.x and Solaris 2.3, 2.4
/usr/openwin/lib/app-defaults/OVw
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ovw
/usr/OV/bitmaps/*
/usr/OV/databases/mapdb/*
/usr/OV/databases/ovwdb/*
/usr/OV/fields/*
/usr/OV/help/*
/usr/OV/registration/*
/usr/OV/symbols/*
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ovw
/etc/opt/OV/share/bitmaps/*
/var/opt/OV/share/databases/mapdb/*
/var/opt/OV/share/databases/ovwdb/*
Hewlett-Packard Company - 9 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
/etc/opt/OV/share/fields/*
/etc/opt/OV/share/help/*
/etc/opt/OV/share/registration/*
/etc/opt/OV/share/symbols/*
Universal Pathname $OV_BIN/ovw
$OV_BITMAPS/*
$OV_DB/mapdb/*
$OV_DB/ovwdb/*
$OV_FIELDS/*
$OV_HELP/*
$OV_REGISTRATION/*
$OV_SYMBOLS/*
$OV_APP_DEFS/OVw
Universal pathname paths are established according to your shell and
platform requirements. See the file that applies to your platform and
shell for more information about the script used to set HP OpenView
Network Node Manager environment variables:
HP-UX 9.x and SunOS 4.1.x
/usr/OV/bin/ov.envvars.sh (k shell)
/usr/OV/bin/ov.envvars.csh (c shell)
HP-UX 10.x and Solaris 2.3, 2.4
/opt/OV/bin/ov.envvars.sh (k shell)
/opt/OV/bin/ov.envvars.csh (c shell)
SEE ALSO
bitmap(1), xrdb(1), ovstart(1M), ovwdb(1M), OVwRegIntro(5), HP
OpenView Windows User's Guide, X11R5 documentation, and OSF Motif
documentation.
EXTERNAL INFLUENCES
Environment Variables
ovw sets the environmental variable LANG for itself and the other
processes it starts by reading the file $OV_CONF/LANG which, if
present, should contain only the single-word value to which LANG
should be set. LANG determines the language in which messages appear.
If LANG does not exist, and if $OV_CONF/LANG is not set or is set to
the empty string, a default of "C" (see lang(5)) is used.
DISPLAY determines the host and display number to use when contacting
an X server.
XENVIRONMENT determines the name of a resource file for overriding
global ovw X resources.
Hewlett-Packard Company - 10 - NNM Release 4.0: August 1995
ovw(1) ovw(1)
International Code Set Support
Single- and multi-byte character code sets are supported.
Hewlett-Packard Company - 11 - NNM Release 4.0: August 1995