|
Eloquence B.08.30 may be installed in parallel with previous Eloquence
versions. It uses a separate product name and a version specific
installation and configuration directory.
/opt/eloquence/8.3/ # installation directory
/etc/opt/eloquence/8.3/ # config directory
/etc/opt/eloquence/8.3/license # B.08.30 license file
/etc/opt/eloquence/8.3/eloqdb.cfg # default db server config
/var/opt/eloquence/8.3/ # scratch files, e.g. pid files
/var/opt/eloquence/socket # default path AF_Unix sockets
SystemV init scripts:
/sbin/init.d/eloq83 # start/stop script
/etc/rc.config.d/eloquence83 # startup configuration
The B.08.30 startup script eloq83 uses a separate configuration file.
A default configuration file is installed in /etc/rc.config.d/eloquence83.
Any customizations from a previous Eloquence version need to be copied
manually. When adjusting the new startup configuration file, notice that
Eloquence versions before B.08.00 used an ELOQDB6 prefix/suffix for
config options, whereas versions since B.08.00 use an ELOQDB prefix/suffix.
As of Eloquence 8.3 only the 64 bit eloqdb database server is shipped
on the HP-UX Integrity platform.
On the HP-UX HP9000 both the 32 bit and the 64 bit eloqdb are shipped.
The installation creates a symbolic link named eloqdb, pointing
to the default database server program (eloqdb32 on HP9000).
You need to manually adjust the symbolic link (using ln -s) if you
prefer to use the 64-bit version.
Note that the choice of the 32-bit or 64-bit database server version
does not depend on whether your client programs are 32-bit or 64-bit
programs (using their respective client libraries). All of the possible
combinations are supported.
You may need to use the 64-bit version if you want to configure the
dedicated Eloquence BufferCache to sizes above 1 GB or configure the
maximum number of concurrent client connections (Threads) to values
above 3000, for example.
The Eloquence config files reside in the config directory
/etc/opt/eloquence/8.3. When updating from a previous
Eloquence version, it may be necessary to change references to
previous config files. For example, some data base utilities
may refer to configuration files for additional database instances.
The installation procedure installs default configuation files
in the /etc/opt/eloquence/8.3 directory.
These are based on the templates shipped in the
/opt/eloquence/8.3/newconfig/config directory.
When updating from a previous Eloquence version it is necessary
to either merge any customizations into the new configuration file
or otherwise copy or link the previous config files to the
Eloquence 8.3 config directory.
Typically, configuration files are compatible, defaults are used
for any omitted settings.
For example
# coming from Eloquence 8.2
cp /etc/opt/eloquence/8.2/eloqdb.cfg \
/etc/opt/eloquence/8.3/eloqdb.cfg
The eloqdb.cfg is used by default by the eloqdb server process
and some database utilities.
If you intend to switch Eloquence versions for a database instance
(for example, during an initial validation phase) you may
consider creating a symbolic link of the configuration file instead
of a copy of the configuration file.
# coming from Eloquence 8.2
ln -sf /etc/opt/eloquence/8.2/eloqdb.cfg \
/etc/opt/eloquence/8.3/eloqdb.cfg
Without one of the steps outlined above, some of the Eloquence
database utilities, like dbvolcreate, dbvolextend, or dbvoldump,
for example, will no longer work without specifying the path to
the config file using the -c command line option explicitly.
As Eloquence 8.3 is installed to the separate /opt/eloquence/8.3
directory, any libraries are also installed in the new directory tree.
Eloquence ships client libraries for 32 bit and 64 bit applications.
Eloquence on the Integrity platform also includes the PA-RISC libraries
to support HP9000 applications running on Integrity systems.
/opt/eloquence/8.3/lib/hpux32 # 32-bit Itanium (IA-64)
/opt/eloquence/8.3/lib/hpux64 # 64-bit Itanium (IA-64)
/opt/eloquence/8.3/lib/pa20_32 # 32-bit PA-RISC 2.0
/opt/eloquence/8.3/lib/pa20_64 # 64-bit PA-RISC 2.0
Please note that PA-RISC 1.1 libraries (previously installed in the
pa11_32 directory) are no longer included. If necessary create
a symbolic link to pa20_32.
It is recommended to compile/link programs and libraries such that
they are enabled to make use of the LD_LIBRARY_PATH and/or
SHLIB_PATH environment variables to control the library search
path on the target system.
Please refer to the dld.sl(5) man page on HP-UX PA-RISC,
the dld.so(5) man page on HP-UX IA64.
This is typically the default on HP-UX IA64 but may need to
be verified/changed with the chatr utility on HP-UX PA-RISC.
You may need to adjust your Unix logon scripts or application specific
start scripts to export the proper LD_LIBRARY_PATH and/or SHLIB_PATH
for using the appropriate versions of the Eloquence client libraries.
Eloquence B.08.30 may be installed in parallel with previous Eloquence
versions. It uses a separate product name and a version specific installation
and configuration directory.
/opt/eloquence/8.3/ # installation directory
/etc/opt/eloquence/8.3/ # config directory
/etc/opt/eloquence/8.3/license # B.08.30 license file
/etc/opt/eloquence/8.3/eloqdb.cfg # default db server config
/var/opt/eloquence/8.3/ # scratch files, e.g. pid files
/var/opt/eloquence/socket # default path AF_Unix sockets
Systemd (optional):
/etc/default/eloquence # override service defaults
[/usr]/lib/systemd/system/ # systemd unit files
SystemV init scripts (optional):
/etc/init.d/eloq83 # start/stop script
/etc/sysconfig/eloquence83 # startup configuration
systemd is a replacement framework for the SystemV init scripts
to manage services and is used by contemporary Linux distributions.
As of B.08.30, Eloquence on the Linux platform preferably uses
systemd to manage services, where available.
The Linux systemd unit files provide a similar functionality as
the Eloquence SystemV start/stop scripts.
Each service type is defined by a unit file that
describes the service and its dependency to systemd.
The following systemd unit files are available with Eloquence:
-
eloquence83.target
-
The Eloquence target encloses any enabled or running Eloquence
B.08.30 services. The target may be used to start or shut down
all Eloquence B.08.30 services.
-
eloqdb83.service
-
The default Eloquence database instance.
-
eloqdb83@.service
-
Additional Eloquence database instances. The instance name is
specified after the @ sign and implies the database server
configuration file name.
For example, a service name eloqdb83@test.service would use
the eloqdb-test.cfg configuration file.
-
eloqsd83.service
-
The Eloquence eloqsd service
-
dbrepl83.service
-
The default Eloquence database replication instance
-
dbrepl83@.service
-
Additional Eloquence database replication instances. The
instance name is specified after the @ sign and implies
the dbrepl configuration file.
For example, a service name dbrepl83@test.service would use
the configuration file repl-test.cfg.
The unit file names are versioned to allow coexistence with other
Eloquence releases. Once enabled and started a service name without
a version number may be used as an alias.
The Eloquence services are not enabled by default. The systemctl
enable command is used to enable the services for autostart.
systemctl enable eloqdb83.service eloqsd83.service
The eloqdb83@ and dbrepl83@ instances must be enabled with an
additional instance name. The instance name also defines the name of
the associated configuration file.
systemctl enable eloqdb83@test.service
The eloqdb83@test.service describes an eloqdb instance using
the configuration file eloqdb-test.cfg.
The eloquence83.target may be used to specify any active or
enabled Eloquence service.
# start/stop any configured Eloquence 8.3 services
systemctl start eloquence83.target
systemctl stop eloquence83.target
# list configured Eloquence 8.3 services and status
systemctl list-dependencies eloquence83.target
# List Eloquence 8.3 unit files and status
systemctl list-unit-files "*83*"
The systemctl start command is used to start the enabled Eloquence
services (requires root).
systemctl start eloquence83.target
- or -
systemctl start eloqsd83.service eloqdb83.service
Changing system wide systemd services requires root permissions.
Using sudo (with an appropriate sudoers entry) may be used to
allow users to start/stop Eloquence services without unlimited
root access.
For Linux distributions that do not support systemd, Eloquence B.08.30
supports SystemV init scripts and configuration.
The B.08.30 startup script eloq83 uses a separate configuration file.
A default configuration file is installed in /etc/sysconfig/eloquence83
(or /etc/default/eloquence83 on Debian derived distributions).
Any customizations from a previous Eloquence version need to be copied
manually.
/etc/init.d/eloq83 # start/stop script
/etc/sysconfig/eloquence83 # startup configuration
The Eloquence config files reside in the config directory
/etc/opt/eloquence/8.3. When updating from a previous
Eloquence version, it may be necessary to change references to
previous config files. For example, some data base utilities
may refer to configuration files for additional database instances.
The installation procedure installs default configuation files
in the /etc/opt/eloquence/8.3 directory.
These are based on the templates shipped in the
/opt/eloquence/8.3/newconfig/config directory.
When updating from a previous Eloquence version it is necessary
to either merge any customizations into the new configuration file
or otherwise copy or link the previous config files to the
Eloquence 8.3 config directory.
Typically, configuration files are compatible, defaults are used
for any omitted settings.
For example
# coming from Eloquence 8.2
cp /etc/opt/eloquence/8.2/eloqdb.cfg \
/etc/opt/eloquence/8.3/eloqdb.cfg
The eloqdb.cfg is used by default by the eloqdb server process
and some database utilities.
If you intend to switch Eloquence versions for a database instance
(for example, during an initial validation phase) you may
consider creating a symbolic link of the configuration file instead
of a copy of the configuration file.
# coming from Eloquence 8.2
ln -sf /etc/opt/eloquence/8.2/eloqdb.cfg \
/etc/opt/eloquence/8.3/eloqdb.cfg
Without one of the steps outlined above, some of the Eloquence
database utilities, like dbvolcreate, dbvolextend, or dbvoldump,
for example, will no longer work without specifying the path to
the config file using the -c command line option explicitly.
As Eloquence 8.3 is installed to the separate /opt/eloquence/8.3
directory, any libraries are also installed in the new directory tree.
Eloquence ships client libraries for 32 bit and 64 bit applications.
/opt/eloquence/8.3/lib # 32-bit
/opt/eloquence/8.3/lib64 # 64-bit
It is recommended to compile/link programs and libraries such that
they are enabled to make use of the LD_LIBRARY_PATH
environment variables to control the library
search path on the target system.
Please refer to the the ld.so(8) man page on Linux.
This is typically the default on Linux.
You may need to adjust your Unix logon scripts or application specific
start scripts to export the proper LD_LIBRARY_PATH
for using the appropriate versions of the Eloquence client libraries.
Eloquence B.08.30 may be installed in parallel with previous Eloquence versions.
It uses a new installation directory and/or new file names for the software and its
configuration files.
On 32-bit Windows:
C:\Program Files\Eloquence\8.3 # installation directory
...\Eloquence\8.3\bin\eloqdb32.exe # 32-bit db server
C:\Program Files\Eloquence\8.3\etc # config directory
...\Eloquence\8.3\etc\license # B.08.30 license file
...\Eloquence\8.3\etc\eloqdb.cfg # default db server config
On 64-bit Windows:
C:\Program Files (x86)\Eloquence\8.3 # installation directory
...\Eloquence\8.3\bin\eloqdb32.exe # 32-bit db server
...\Eloquence\8.3\bin64\eloqdb64.exe # 64-bit db server
C:\Program Files (x86)\Eloquence\8.3\etc # config directory
...\Eloquence\8.3\etc\license # B.08.30 license file
...\Eloquence\8.3\etc\eloqdb.cfg # default db server config
The 32-bit database server executable is named "eloqdb32.exe"
and (on 64-bit Windows) the 64-bit database server executable
is named "eloqdb64.exe". The database service is named "eloqdb".
Please note that on Windows 64-bit, both the 32-bit database server
(eloqdb32.exe) and the 64-bit database server (eloqdb64.exe) are
installed to the Eloquence bin and bin64 directories.
However, depending on the selection in the Custom Setup dialog of
the installer, either the eloqdb64.exe or the eloqdb32.exe is used
to register the Windows service(s) for your database server instance(s).
You may later modify this selection by starting the installation program.
This will cause your
database server instance(s) to be stopped and restarted with either the
64-bit or the 32-bit database server executable.
Note that the choice of the 32-bit or 64-bit database server version
does not depend on whether your client programs are 32-bit or 64-bit
programs (using their respective client libraries). All of the possible
combinations are supported.
You may need to use the 64-bit version if you want to configure the
dedicated Eloquence BufferCache to sizes above 1 GB or configure the
maximum number of concurrent client connections (Threads) to values
above 3000, for example.
The default database server config file name is eloqdb.cfg and it
resides in the changed default directory
C:\Program Files\Eloquence\8.3\etc for 32-bit Windows
or C:\Program Files (x86)\Eloquence\8.3\etc for 64-bit Windows.
These changes are automatically applied by the installer
when you update from an earlier Eloquence version and have used
the previous default config file in the past.
A new installation of the Eloquence B.08.30 software creates a default
database server config etc\eloqdb.cfg that is based on the
newconfig\config\eloqdb.cfg template file:
- 32-bit Windows
- C:\Program Files\Eloquence\8.3\etc\eloqdb.cfg
C:\Program Files\Eloquence\8.3\newconfig\config\eloqdb.cfg
- 64-bit Windows
- C:\Program Files (x86)\Eloquence\8.3\etc\eloqdb.cfg
C:\Program Files (x86)\Eloquence\8.3\newconfig\config\eloqdb.cfg
Note that the contents of the eloqdb.cfg file are upward compatible
with the eloqdb6.cfg file from older Eloquence versions, so you
don't have to make manual adjustments unless you want to make use of
the new or enhanced configuration options. The database server assumes
default values for missing settings.
Eloquence B.08.30 is installed to the new Eloquence\8.3 directory
and it also provides the associated database client libraries there.
Eloquence B.08.30 no longer installs product specific libraries to
the C:\Windows\system32 directory.
On 32-bit Windows:
C:\Program Files\Eloquence\8.3\bin\eloqdb32.dll
C:\Program Files\Eloquence\8.3\bin\image3k.dll
C:\Program Files\Eloquence\8.3\bin\image3kC.dll
C:\Program Files\Eloquence\8.3\bin\ftc.dll
On 64-bit Windows:
C:\Program Files (x86)\Eloquence\8.3\bin\eloqdb32.dll
C:\Program Files (x86)\Eloquence\8.3\bin\image3k.dll
C:\Program Files (x86)\Eloquence\8.3\bin\image3kC.dll
C:\Program Files (x86)\Eloquence\8.3\bin\ftc.dll
C:\Program Files (x86)\Eloquence\8.3\bin64\eloqdb64.dll
C:\Program Files (x86)\Eloquence\8.3\bin64\image3k64.dll
C:\Program Files (x86)\Eloquence\8.3\bin64\ftc64.dll
The database client and utility DLLs are installed in the Eloquence bin
and bin64 directories. In Eloquence B.07.10 or older versions, they were
installed in C:\Windows\System32. As the installation or upgrade process
adds the Eloquence bin and bin64 directories to the PATH variable, the
libraries should be available to application programs without any manual
adjustments.
The related .lib and .def files are installed in the Eloquence lib and
lib64 directories.
Multiple database server instances may be registered as separate
Windows services, each with its own Windows service name.
To set up a database server instance, an instance-specific configuration
file is typically derived from the newconfig\config\eloqdb.cfg
default configuration template, then this file
is specified with the Windows service registration.
For example, to set up a 64-bit eloqdb instance
named "eloqdb-test" using the configuration file
"C:\data\db\conf\eloqdb-test.cfg":
eloqdb64 -install:eloqdb-test -c C:\data\db\conf\eloqdb-test.cfg
Any additional command line options (here: the -c option to specify the
location of an instance-specific configuration file) are saved and will
implicitly be used whenever the instance is started:
net start eloqdb-test
Please note:
After a database server instance has been registered, the Windows Service
Manager may be used to configure it to start/stop automatically when the
system is started or shut down, and, if desired, to use an account
different from SYSTEM.
The Windows Service Manager may then be used to start/stop the instance.
Alternatively, the net start/stop command line may be used:
net start instance_name
net stop instance_name
To remove an instance from the Windows Service Manager:
eloqdb64 -remove:instance_name
|
