LEVERAGE
LEarn from Video Extensive Real Atm Gigabit Experiment

Specification of administration and system tools for two sites trials: Deliverable DWP422

A zipped version of this document can be downloaded here.

Abstract :
The overall LEVERAGE architecture is distributed over three sites. Nevertheless, it is obvious that each site has to have its own LEVERAGE architecture to allow the system to work during inter-connected sessions.

The approach described in this document concerns the distributed aspect over the two sites.

The LEVERAGE servers have to provide at least three major functionnalities:

  • a Media provider (video, audio, text, etc.) for all the workstations connected to the LEVERAGE network;
  • a Multipoint conference unit which is responsible of managing all the multipoint communication aspects;
  • a Session Manager which is responsible of managing the conference sessions;
  • an Administration (user management, session management, application conductor, asynchronous messaging, workspace management, etc.) and all the other tools which can be centralized.

The system specified in this document presents the administrative server used as well as the tools available on it that bith provide applications working on users workstations with system and administrative functionalities The administrative server will be based on a WINDOWS NT system. Thus the administrative facilities of this system will be used to manage users, groups, system access, etc.

We will also find within this system the HTTP server that will be used to provide users with HTML pages forming the heart of the LEVERAGE application. This system will be responsible for controlling access to those pages before sending them to workstations that make the request.

A database will be present on this system to provide applications running on the workstations with the global static data needed by the applications.

Within system tools, the workspace management system is responsible for providing users with disk space to store their own files. The asynchronous messaging system will provide users with an e-mail system to exchange messages over the network and a news system to have access to conferences.

Authors: Jean-Pierre BERNARD (CSTL) - Didier PARIS(CSTL)
Date: 30/04/97

Contents:

  1. SYSTEM OVERVIEW
      1.1 - Aim of the system
      1.2 - General constraints
  2. FUNCTIONAL DESCRIPTION
      2.1 - Inputs and Outputs
      2.2 - Functional description of system components
        2.2.1 Administration
          2.2.1.1 Users creation
          2.2.1.2 Groups creation
          2.2.1.3 Access control
          2.2.1.4 Login-logout scripts
          2.2.1.5 Inputs and outputs
        2.2.2 HTTP server
          2.2.2.1 HTML management
          2.2.2.2 HTML pages access control
          2.2.2.3 Inputs and outputs
          2.2.2.4 HTTP Server in a multi-site environment
        2.2.3 Database
          2.2.3.1 Creation, update of static data
          2.2.3.2 Inputs and outputs
          2.2.3.3 Database in the multi-site environment
        2.2.4 Workspace management
          2.2.4.1 User and group Management
          2.2.4.2 Workspace Management
          2.2.4.3 Disk Quota Management
          2.2.4.4 Server connection
          2.2.4.5 Inputs and Outputs
          2.2.4.6 Workspace in the multi-site environment
        2.2.5 Asynchronous messaging system
          2.2.5.1 Inputs and Outputs
  3. ENVIRONMENT DESCRIPTION
      3.1 Cambridge site
      3.2 INT site

LEVERAGE home page
Last updated 24th August 1998
E-mail: leverage@cilt.org.uk