OPE Installation and Configuration Guide

Configuring OPE on UNIX


This section provides instructions for configuring OPE once it has been installed. OPE must be configured before it can be used.

The OPE tools are ObjectStore applications. An ObjectStore client run-time environment and Server must be accessible in order for you to configure and use OPE. See ObjectStore Requirements for more information.

Configuring OPE consists of telling it where to place its application schema database so that it can be accessed by an ObjectStore Server. You are asked to supply the following information:

(Depending on your particular configuration, some of this information might be automatically supplied for you.)

Beginning the configuration process

In the following instructions, the command-line prompt is denoted with a > symbol, and sample user input is in bold.

  1. Start the configuration by using the osopesetup installation and configuration utility. If you continued into the configuration step directly from installation, this is done for you.


 	 > $OS_OPE_ROOTDIR/bin/osopesetup config
 	Configuring OPE ...
Specify location of ObjectStore client run time
  1. Set your OS_ROOTDIR environment variable to the path where ObjectStore is installed (see "ObjectStore requirements").
 		The default copy of ObjectStore to use is in 
 		    <default directory loction>.
Is this the copy that you want to use? [yes]
yes Required ObjectStore Release 6.0 is installed in <installation location>.
Specify location of OPE installation
  1. Specify the path where OPE was installed (see Installation Location).
 		The default OPE installation to configure is in 
               <default installation location> .
 		Is this the installation that you want to configure? [yes] yes
OPE Application Schema Database
  1. The OPE Analyzer and related tools use an ObjectStore application schema database ($OS_OPE_ROOTDIR/lib/osopea.adb). This database must be accessible to an ObjectStore Server. The installation and configuration utility checks to see if a local ObjectStore Server can be used to access the database. If a local ObjectStore Server is found, you will see this message. OPE uses the local Server and no further action is required.


 	Verifying accessibility of the OPE application schema database ..
 	Schema database ">" is accessible.
If the schema database is not accessible to a local ObjectStore Server, you see this message:

 	* The default OPE application schema database in
 	* <application schema database pathname>
 	* is not accessible by an ObjectStore server process.
  1. You are asked if you want to specify a network location that is accessible to an ObjectStore Server:


 	Do you want to specify a path right now? [yes] yes
  1. Supply a network path. OPE's application schema database is copied to the location you specify. (See "6.0 run-time Server" for instructions on how to tell whether a particular network location is accessible to an ObjectStore Server.)


 	Enter new path for OPE application schema database: 
 	asterix::/ostore/dbs/ope/osopea.adb
 	Do you want to set the schema path to
 	asterix::/ostore/dbs/ope/osopea.adb? [yes] yes
 	osopeax,osopefx in $OS_OPE_ROOTDIR/bin have been updated.
The network path you specify can be a rawfs database path. In order to specify a network path to an OS/2 or NT computer, use a syntax like this:

		 tweezer::g:\\users\\jones\\osopea.adb
You see this message when you have completed the installation:

	You have successfully configured ObjectStore Performance Expert.

See Other Information before using OPE.



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