OPE Installation and Configuration Guide

Prerequisites

The OPE product is composed of several major components: Retriever, Analyzer, and Server Monitor.

The Retriever is a set of libraries that are automatically loaded during ObjectStore application execution if OPE performance monitoring is activated. The Retriever is shipped separately from the OPE product on most ObjectStore platforms (see below for details).

The Analyzer and Server Monitor are graphical tools you can use to gain an understanding of the performance of your ObjectStore applications and Servers. The Analyzer and Server Monitor are shipped with OPE on the ObjectStore platforms described below.

Hardware and Operating System Requirements

The OPE Analyzer and Server Monitor are supported for the following hardware and operating system configurations:

ObjectStore Requirements

OPE requires access to an ObjectStore Client installation (development or runtime), and to an ObjectStore Server. You can use an existing ObjectStore Client installation, as long as it is 6.0 GA or higher. You can use any ObjectStore R6 Server.

You can determine the version of ObjectStore running on a specific machine with the osversion command.

Bundled ObjectStore 6.0 Client Run Time

For your convenience, a suitable ObjectStore Client Run-Time installation is included on the OPE CDROM, as described below:

How you can use this supplied client run time depends on which platform you are installing OPE on:

6.0 run-time Server

The OPE tools must be able to communicate with an ObjectStore Server, during configuration and during normal use. This is required so that OPE can access its application schema database, and in order to create OPE performance databases. This is not necessary if you use OPE on Windows NT or Windows 98 with the ObjectStore / Single version.

You can determine if a Server is running on the installation computer with the ObjectStore commands ossvrping and oshostof:

	> oshostof <ope-install-dir>
	tso
	> ossvrping tso

 	The ObjectStore server on host tso is alive.

OPE is configured, by default, to use an ObjectStore Server running on the installation computer. You can configure OPE differently if an ObjectStore Server is not running on the installation computer, or if you want to use one running on a different computer. If you want to do this, you must specify where on the network OPE should be configured to access its application schema database, and copy it there.

You can specify where the OPE application schema database should be copied to during the OPE configuration step. See Configuring OPE on UNIX for more information on UNIX platforms. For information about this on Windows NT or Windows 98, see "Is an ObjectStore Server running on your machine?".

ObjectStore / Single

The OPE 6.0 Analyzer and Formatter can be run with the ObjectStore/Single runtime libraries of ObjectStore R6.0. In this mode an ObjectStore Server is not required. Performance databases must be stored on a local file-system.

Simply use osopea_sngl (Analyzer) and osopef_sngl (Formatter).

The OPE Server Monitor relies on the network components of ObjectStore and can not be used with ObjectStore/Single.

On UNIX, the ObjectStore/Single libraries are not part of the OPE installation. The scripts osopea_sngl and osopes_sngl require that the Single libraries are installed in $OS_ROOTDIR/lbsngl. For your convenience, a full ObjectStore R6.0 runtime client installation kit including ObjectStore/Single is supplied with the OPE CD.

Note that on UNIX, the environment variables OS_CACHE_FILE and OS_LOG_FILE have to be set to specify the client cache and the transaction log for each ObjectStore/Single application.

On Windows platforms the ObjectStore/Single DLLs are part of the ObjectStore R6.0 runtime client bundled with the OPE installation. Note that there is no item in the OPE Program Group for the Single version of the Analyzer.

Compare also with the OPE Users Guide, chapter 3, "Opening and Formatting a Trace file", sections "Using the Command Line" and "Using the Analyzer".

Monitor Requirements

A color monitor is strongly recommended for use of the OPE Analyzer. A monochrome monitor is sufficient for the Server Monitor.

X Windows Requirements

On UNIX platforms, OPE requires the X Window system.

Once OPE is installed, you might want to customize X Windows for best results. See Instructions for X Windows Users.

Installation Location

The default installation directory for OPE is
Solaris /opt/ODI/OPE6.0
AIX /usr/lpp/ODI/OPE6.0
HP-UX /usr/local/ODI/OPE6.0
Windows NT or Windows 98 C:\ODI\OPE6.0

An alternate installation directory can be chosen at installation time.

Required Disk Space

An OPE installation requires the following amount of disk space:
Solaris
Plus 9 MB in temporary space during non-CDROM-based installation
AIX
see README for AIX
HP-UX
see README for HP-UX

These numbers do not include space requirements for the requisite ObjectStore installation. Note that the executables and the libraries are not stripped.
Windows NT or Windows 98 21 MB Plus 6 MB in temporary space during non-CDROM-based installation

This number includes space requirements for the bundled ObjectStore Client Run Time and ObjectStore / Single installation.

OPE Retriever Configurations and Requirements

The OPE Retriever is provided with all recent releases of ObjectStore:

In addition, the OPE installation might contain more recent versions of the Retriever for one or more platforms and configurations. These updated versions can be found in the patches directory of the OPE installation. Consult the README file in that directory.

Generally speaking, if an updated Retriever library is shipped as a part of an OPE installation, it must be installed in conjunction with a specific version of ObjectStore.

On machines running SunOS, the OPE Retriever requires SunOS 4.1.3_U1.


support@objectstore.net
Copyright © 2004 Progress Software Corporation. All rights reserved.