.
contact contact

B.08.00 / Release Notes / Changes

New Features and Enhancements

 
.
  This document provides an overview on new features and enhancements in Eloquence B.08.00 and major user visible changes by product component.

Contents:



Installation

The Eloquence product is installed in a separate location and may be installed concurrently with a previous Eloquence release.

This has a few consequences in the Eloquence installation

  • An existing installation of a previous Eloquence release is not updated or replaced when installing Eloquence B.08.00.

  • A separate start/stop script and startup configuration file is used.

  • Any customizations in the config files of a previous Eloquence release are not carried over and must be adapted manually. However, as the Eloquence config files are backwards compatible, the previous config files could be copied or linked to the Eloquence B.08.00 config directory.

  • The config file for the default database environment is now named eloqdb.cfg instead of eloqdb6.cfg.

  • The database server process has changed from eloqdb6 to eloqdb (which is a symbolic link pointing to either eloqdb32 or eloqdb64). Any custom scripts relying on the eloqdb6 name need to be adapted.

  • Eloquence B.08.00 uses a different path for its binaries and the PATH environment variable (or any absolute paths in scripts) may need to be adpated to take advantage of Eloquence B.08.00. Though Eloquence B.08.00 is closely compatible with the previous release and binaries may be mixed, it is recommended to make these changes.

  • Eloquence B.08.00 uses a different path for its shared libraries. To use the B.08.00 libraries, the SHLIB_PATH / LD_LIBRARY_PATH environment variables need to be set appropriately. Though Eloquence B.08.00 is closely compatible with the previous release and previous libraries may be used, it is recommended to make these changes.

In addition, the following builds are supported as of Eloquence B.08.00

  • Linux on IA64 hardware
  • Linux on AMD64/EM64T hardware

Please refer to the following documents for details:


Database server

Major database server changes include
  • The database server was enhanced to further improve scalability.

    • An improved threading implementation allows to make use of available CPU resources. Previously, the server used its own threading sub-system as OS level threading capabilities were limited in previous OS releases. As of B.08.00, the database server makes use of OS level threads and allows use of additional CPU resources.

    • improved scalability on large memory configurations

  • The database server is available as 32bit and 64bit versions. Where appropriate, both versions are included and either version may be used.

  • The database server was enhanced to support replication.

  • The database server was enhanced to support case insensitive indexes.

Other database server changes include

  • The database property DBLOCK-COMPAT was added to enable mandatory DBLOCKs. While we would usually recommend against using this, it may be required for close TurboIMAGE compatibility in rare cases.
  • Forward log is no longer disabled after a database server crash.
  • The Database server config file template was updated
Please refer to the following documents for details:


Database Client Libraries

Changes to the database client library include
  • The EQ_DBENABLEIPC environment variable was added to support SSL/SSH tunneling.

  • The use of a higher resolution timer is expected to improve the efficiency of the client side caching when using remote connections.
Changes to the image3k library include:
  • Information passed to the DBBEGIN, DBEND and DBMEMO calls may optionally be included in forward logs.

  • The HP3K_TPI_COMPAT database property supports additional options to improve Superdex compatibility.

  • The TurboIMAGE compatibility was changed to improve corner case compatibility of the DBFIND call. As documented by the TurboIMAGE documentation it now resets the current record number.

  • The username and password passed in the DBLOGIN call may now be up to 255 characters.
Please refer to the following documents for details:


Database Utilities

Database utility changes include
  • The dbrecover utility was enhanced to support point-in-time recovery. The -T command line option may be used to specify a point-in-time to stop recovering transactions from the forward log.

  • The dbrecover utility was enhanced to support incremental recovery. Instead of starting from the last backup, dbrecover has gained the ability to continue where it previously left off.

  • The schema, dbutil and prschema utilities were enhanced to support additional syntax for case insensitive indexes.

  • The new dbrepl utility is used to replicate database transactions to one or more slave servers.

  • The fwaudit utility was enhanced to support more complex filter expressions, to support the "id" and "conntime" filter criteria and to support information from DBBEGIN/DBEND/DBMEMO calls.

Changes to database utilities include

  • The dbrecover, dblogreset, dbstore, dbbexp, dbcfix support custom cache sizes instead of using the server configuration file.
  • The dblogreset utility was enhanced to retain changes in transaction journal, reapplied during startup recovery, in the forward-log after abnormal server termination.
  • The query3k utility defaults to /var/tmp for temporary files.
  • The query3k utility no longer displays max capacity in form set, if default.
  • The query3k utility was enhanced to improve support for Eloquence database limits that exceed TurboIMAGE limits.
Please refer to the following documents for details:


Database logging, auditing, replication, fwutil

Noticeable changes to the forward logging and auditing subsystem include
  • Forward logs and audit files may now include information on the IMAGE3K DBBEGIN, DBEND and DBMEMO calls.

  • The database server and the dbrepl utility support database server replication from archived transactions in the forward log files

  • The new fwutil library provides incremental and close-to-realtime access to database changes and transactions.
Please refer to the following documents for details:


Database performance metrics (server, sessions)

Changes include
  • The server performance metrics were improved; configuration options for StatFileFlags, SessionStatFile, SessionStatMode were introduced and associated dbctl options for dynamic control were added.

  • The server utilization percentage (in http status page and StatFile) is now based on CPU activity as a result of the architectural changes to the thread-model; previous versions were based on "non idle" time, which included system call time.
Please refer to the following documents for details:


Eloquence Language

Changes to the Eloquence programming language include
  • The limitation of the memory size available for variables was removed. The MEMSIZE config option may be used to specify the overall memory size for variables. The default variable limit was changed to 1 MB.

  • The SORTORDER config option may be used to specify the collating sequence that is used for sorting (SORT BY statement and LEX function).

  • The QFIND IN statement was enhanced to support case-insensitive indexes.

  • Support for JDLG (pass through) printing was added (using PRINTER IS 10)
Please refer to the following documents for details:


Eloquence WEBDLG

WEBDLG enables dialog based Eloquence programs to use a web browser as a user interface (requires Apache web server).

Changes to the Eloquence WEBDLG include

  • The Eloquence WEBDLG and accompanying APACHE modules were ported to the Windows platform. The APACHE 2.0 and APACHE 2.2 web servers are supported.

  • The Eloquence WEBDLG and related APACHE 2.0 and APACHE 2.2 modules were ported to the 64 bit Linux x86_64 platform.

  • The APACHE web server 2.2 is now supported through the WEBDLG eloq_mod22 module.

  • The mod_eloq2 and mod_eloq22 WEBDLG modules for the APACHE 2.x web server are now compatible with the threaded APACHE 2.x multi-processing model (APACHE 2.x MPM worker). Previous versions of the mod_eloq2 module could only be used with the non-threaded APACHE 2.x multi-processing model (APACHE 2.x MPM prefork).
Please refer to the following documents for details:


Eloquence JDLG

JDLG implements a JAVA (tm) based graphical user interface for dialog based Eloquence programs.

Changes to the Eloquence JDLG include

  • New JDLG 1.4.x release available

  • Support for JDLG (pass through) printing was added (using PRINTER IS 10)

  • Support for multi-column ListBox object


 
 
.
 
 
  Privacy | Webmaster | Terms of use | Impressum Revision:  2008-12-03  
  Copyright © 2008 Marxmeier Software AG