Robelle Environment Variables

If you are doing an upgrade install then you likely have all the environment variable set up, and you may be able to skip this section, however, it is important to be aware of the various variables that drive our product(s).

Robelle Variables

There are some variables that are specific to Robelle products, these are:
  1. ROBELLE Variable. The ROBELLE variable tells the Robelle products where it's supporting files are located. This is universal for all products on HP-UX.
     export ROBELLE=/opt/robelle
  2. ROBELLE_DYN_LOAD. Suprtool can use two methods to dynamically load it's Eloquence and Oracle libraries. By default, Suprtool will look at the SHLIB_PATH variable in order to resolve it's libraries. If you set ROBELLE_DYN_LOAD=Y, then Suprtool will use LD_LIBRARY_NAME, to look for the library that it needs.
     export ROBELLE_DYN_LOAD=Y
These variables are specific to Robelle products, PATH, MANPATH, SHLIB_PATH and LD_LIBRARY_PATH are HP-UX variables that impact all programs on your system, and are also used by Robelle products. The next section discusses this variables and how to set up for the various shells.

Setting up Environment Variables

If this is an upgrade then it is likely that all the environment variables have been setup and you can skip this section.

You can set up various environment variables to make running any of the Robelle products easier. The variables that we recommend setting for Suprtool are: SHLIB_PATH, ROBELLE, PATH and MANPATH.

PATH and MANPATH

The easiest way to add variables accessible to all users is to set the variables in the global exec file for the shell you use.

For the Bourne, Korn and Posix Shells we recommend the following additions to the /etc/profile file.

export PATH=$PATH:$ROBELLE/bin
export MANPATH=$MANPATH:$ROBELLE/man

For the C Shell we recommend that you add the following commands after any existing PATH or MANPATH statements in the /etc/csh.login file:

set path=($path $ROBELLE/bin)
setenv MANPATH "$MANPATH":$ROBELLE/man

SHLIB_PATH and LD_LIBARY_PATH

Suprtool dynamically loads the Eloquence and Oracle libraries it needs where applicable. If you are installing the PA_RISC version of our products it is likely best to set the SHLIB_PATH to point to the variables that are needed. This is the default behaviour of our products.

Here is how you can set SHLIB_PATH as an example:

export SHLIB_PATH=/opt/eloquence6/lib/pa11_32;$ORACLE_HOME/lib/pa_risc
If you are installing the Itanium version then you should set the ROBELLE_DYN_LOAD to Y and set the LD_LIBRARY_PATH to point to the appropriate Itanium libraries.

 export ROBELLE_DYN_LOAD=Y
 export LD_LIBRARY_PATH=/opt/eloquence6/lib/hpux32;$ORACLE_HOME/lib32
Typically you can put these export commands in the
/etc/profile
file and every user that uses the Bourne, Korn and Posix shells will have the variable for each of their sessions.

Configuring different Shells

When you log on to HP-UX, a program is run called the shell. The shell program interprets commands, executes them, and controls command execution. Making configuration changes requires that you know which shell you are using and what files are automatically executed.

Bourne, Korn and Posix Shells

the Bourne, Korn and Posix shells execute the file /etc/profile when you log on to HP-UX. They then look for a file in your home directory called .profile. If it exists, it is executed. If you use SAM to add new users, the file /etc/d.profile is automatically copied to the home group of the new user. If you want to make global changes to the commands that are executed at login in time you typically have to make the changes to the /etc/profile file, and check that the /etc/d.profile (the file that becomes the users .profile file), does not counteract any of the changes that you have made to the global file, such as Path, Manpath or Robelle. You also have may have to warn existing Bourne and Korn shell users to change their .profile file in their home directories.

C Shell

The C shell executes the file /etc/csh.login when you log on to HP-UX. It then looks for the file .login in your home directory. If it exists, it is executed. Next, the C shell executes the file .cshrc in your home directory (also executed any time you invoke a new copy of /bin/csh). If you use SAM to add new users, the files /etc/d.login and /etc/d.cshrc are automatically copied to the home group of the new users. You may need to make changes to /etc/d.login and /etc/d.schrc, so that new users do not override your changes. You may also have to warn existing C shell users to change their .login and .cshrc files in their home directories.