Other Information
Licenses
The OPE Analyzer and Server Monitor do not require licenses. The OPE Retriever contained in R3.1.H-J Patches requires a license. Contact your support contact at ope-support@odi.com.
Patch information
Check the file patches/README (on Windows NT or Windows 98: patches\README) to see if you must update your ObjectStore installation with more recent versions of the Retriever.
Required environment variables
On UNIX, OPE requires that following environment variables are set:
- OS_ROOTDIR should be set to the ObjectStore installation directory (see Hardware and Operating System Requirements).
- OS_OPE_ROOTDIR should be set to the OPE installation directory
(see Installation Location).- PATH should include $OS_OPE_ROOTDIR/bin and $OS_ROOTDIR/bin.
- On UNIX platforms, MANPATH should include $OS_OPE_ROOTDIR/man and $OS_ROOTDIR/man.
On Windows NT or Windows 98, the OS_OPE_ROOTDIR and PATH variables are automatically set when ObjectStore and OPE are installed. There is no need to set the others on Windows NT or Windows 98.
Color and font configuration
You can configure the colors that the OPE Analyzer and Server Monitor use to display various kinds of information on a per-installation and per-user basis.
- On UNIX, OPE first searches your home directory for a file named .osoperc. If found, OPE reads configuration information from the file; otherwise it reads the per-installation file in $OS_OPE_ROOTDIR/etc/osoperc. You can easily create a per-user configuration file by copying the per-installation file into your home directory as .osoperc.
- On Windows NT or Windows 98, OPE first searches your home directory for a file named osope.ini. If found, OPE reads configuration information from the file; otherwise it reads the per-installation file in %OS_OPE_ROOTDIR%\etc\osope.ini. You can easily create a per-user configuration file by copying the per-installation file into your home directory as osope.ini.
Instructions for X Windows Users
The following instructions are intended to help you get the most out of OPE's graphical interface:
- Make sure that the value of the DISPLAY environment variable includes the host name; setting it to :0.0 is not sufficient. For example, the following is an example of a valid value:
tso:0.0
- These are OPE's default color settings (defined in OS_OPE_ROOTDIR/bin/Xdefaults.sample):
! OPE Analyzer:
osopeax*background: grey
osopeax*foreground: black
osopeax*fontList: 7x13bold
osopeax*initialDelay: 2000
osopeax*borderWidth: 0! OPE Server Monitor:
osopesx*background: grey
osopesx*foreground: black
osopesx*fontList: 7x13bold
osopesx*initialDelay: 2000
osopesx*borderWidth: 0! OPE Online Help:
gwhelp*background: grey
gwhelp*foreground: black
gwhelp*fontList: 7x13bold
gwhelp*borderWidth: 0
- The osopesetup creates an entry for the application defaults in /usr/lib/X11/app-defaults/GRIT.
- If you use the twm window manager, setting the DecorateTransients property ensures that OPE's dialog boxes and other windows have title frames. This makes it easier to move them around on the screen.
If your X DISPLAY variable is set to a SunOS computer...
The SunOS OpenWindows product supplies the OpenLook window manager (olwm) and an X server (xnews). OPE works with OpenLook window manager, but not with xnews; OPE requires an X11R4 server. The X server that OPE uses is the one running on the computer specified in the DISPLAY environment variable.
For your convenience, an X11R4 X Window server and related files are shipped with OPE. They are located in the $OS_OPE_ROOTDIR/etc/X11 directory. See the README file in that directory for directions on how to install this server.
For more information, see Known Problems and Unsupported Features in the OPE Release Notes.