2 Starting Eloquence

Eloquence concepts

Major features include:

• Supports development and debugging in a distributed environment

• State-of-the-art Development Environment

• Process attachment. Debug a process running on an arbitrary machine in the network. Even at the customer site.

Eloquence consists of several components, which can either run on a single system or spread across a network.

The Eloquence eloqd6 server

On each machine where Eloquence shall be used, an 'eloqd6' process has to be started. This process can be a 'master-' or a 'slave-server'. All 'slave servers' have to notify to the 'master server', so this server is the only server in the network who knows about all connected Eloquence systems. Which services a particular server provides, depends on the platform and the configuration. For example, an 'eloqd6' on a Windows 95 system can't have the same services as an 'eloqd6' on a HP-UX system, because the database server doesn't run on the Windows 95 platform.

The Eloquence 'eloqd6' server provides a single point to access services on a particular system. On the server, it provides authorization services, remote execution and works as a supervisor process. In addition, it provides file sharing capabilities to the Development Environment. On client systems it implements remote execution services and communicates with the 'dlgsrv' on the Windows platform.

The Integrated Development Environment (IDE)

The Eloquence Development Environment (IDE) is only available on the Windows platform.

It provides a graphical program development environment. In order to execute programs for debugging, it either spawns an eloqcore process locally or asks a remote 'eloqd6-server' to start a debug process.

The Eloquence Development Environment provides its own file handling in addition to the capabilities already provided in the operating system. This file handling is provided by the 'eloqd6' process. By providing its own file handling, Eloquence can achieve:

• uniform and consistent file handling accross operating systems, e.g. case sensitive file name handling.

• consistent and secure handling accross administrative domains. By providing its own authentification mechanism, Eloquence programs can be transparently executed and debugged on remote systems regardless of the platform and your access permissions.

'eloqcore' is the part of Eloquence which executes your program. In a character oriented environment (on UNIX) it controls the terminal and provides its own development and debugging environment.

In a graphical oriented environment (on NT) it runs in a kind of background. For User I/O the GUI server is used and accessed via network. The development and debugging is done by the development server independently. So different tasks are distributed to different servers. For more information see chapter , Starting the Run-Time Environment.

The Dialog Server

The Dialog Server (DLGSRV) is currently only available in the Windows environment. It provides the graphical user interface (GUI) in a networked environment. For more informationsee chapter 1, HP Eloquence Dialog System.

The Database Server

The Eloquence database server provides access to the database. All requests are received via network, even if the eloqcore process runs on the same machine.

Since all of the Eloquence components are able to communicate over the network, you can easily configure a system with all the components distributed to different machines. The 'master-eloqd' server integrates the components regardless of their real locations and provides a homogenous view of the entire system to the Development Environment. This works even if you dial-in to a 'master-eloqd6' at the customer site.

For more information see chapter 2, Introduction, in data base manual.