2 Installing Eloquence on the HP-UX platform
Customizing the Eloquence Configuration Files
This discussion assumes that the Eloquence software has already been installed on your system. The information in this section is directed to the system administrator for the Eloquence software.
NOTE: The configuration steps mentioned here are not related to Eloquence database operation. If the only Eloquence component you intend to use is the database, you can skip this section.
Before Eloquence can be used, its resources must be configured. Eloquence programs usually don't use system resources directly, instead they rely on a mapping of pathes, printers and device files in Eloquence configuration files.
There are three different levels of configuration:
System global
This is achived with the eloq.config configuration file which is located in the Eloquence configuration directory.
Group specific
This is achived with the group.<GroupName> configuation file which is located in the Eloquence directory.
User specific
This is achived with the .eloqrc configuration file which is located in the home directory of the user.
The Eloquence configuration files are read by the eloqcore process, when it is started. The configuration files are processed in an order such that more specific definitions override the more general ones. So a system global assignment can be overriden from a group specific configuration file, a user specific definition will override group and system global definitions.
The system global configuration file, eloq.config is usually copied during the installation process to Eloquence configuration directory and should be adapted to local requirements. Template configuration files are provided in the directory
/opt/eloquence6/newconfig/config. The template configuration files provide comlete inline documentation and are included at the end of this section for your reference.
Eloquence resource configuration
Eloquence resources go back to the "dark ages" when a precedessor of Eloquence was implemented in hardware (called HP250/HP260 at that time) and the resources definition actually were real OS resources. Since programs depended on a program independent resource configuration and it a convenient mechanism anyway, the concept was kept. Instead of real devices Eloquence resources can be mapped to whatever is appropriate. Eloquence is of course able to access native operating resources directly.
Since the following names are not commonly used, let's define them first:
- VOLUME
- A VOLUME is the Eloquence concept of a directory. Instead of using the path directly, it is possible to assign an identifier for a path and refer to it in a symbolic manner.
- MSI
- This is a short form of MASS STORAGE IS and species the default VOLUME on which pathes should be related unless an absolute path or another VOLUME is given.
- PRINTER
- A PRINTER is the Eloquence concept of an output depvice. A PRINTER is identified by a number and could be mapped to a device file or to a sequence of commands.
- The device numbers 8 to 10 have a special predefined meaning:
8: Display terminal.
9: Bit bucket (Eloquence equivalent of /dev/null)
10: Local terminal printer
-
- PORT
- A PORT is the Eloquence equivalent of a (tty) device file. Eloquence provides prowefull machanisms to handle them in a efficient manner.
The eloq.config configration file
The eloq.config file provides system global definitions and is usually copied during the installation process into the Eloquence configuration directory from the template file d.eloq.config.
The group specific configuration file
To provide group specific definitions, you could install a group specific configuration file in the Eloquence configuration directory. Consider we would like to have a specific configuration for the sales group you would perform the following steps:
- Change to the Eloquence confuration directory:
cd /etc/opt/eloquence6
- Create a group specifc configuration file from the template group configuration file. The group specific file should be named group.sales.
cp /opt/eloquence6/newconfig/config/d.group group.sales
- Use a text editor, such as vi to edit the file
vi group.sales
The user specific configuration file
To provide user specific definitions, you could install a user specific configuration file in the gome directory of the user. Consider we would like to have a specific configuration for the user mike, you would perform the following steps:
- Change to the home directory of the user:
cd ~mike
- Create a user specifc configuration file from the template user configuration file. The user specific file should be named .eloqrc:
cp /opt/eloquence6/newconfig/config/d.eloqrc .eloqrc
- Use a text editor, such as vi to edit the file
vi .eloqrc
Eloquence Installation and Configuration - 29 OCT 2004