|
|
System Functional Specification of administration and system tools: Deliverable DWP421
A zipped version of this document can be downloaded here.
Abstract :
The global LEVERAGE architecture is distributed over three sites. Each site has its own local LEVERAGE architecture, in compliance with specific on-site requirements, while providing network access for work during inter-connected LEVERAGE sessions. The approach described in this document addresses the LEVERAGE architecture for the first site, the University of Cambridge. The distributed architecture for the three sites will be described and built during the next phase of the project. Nevertheless the study and the design of the local architecture has been made in view of the final phase of the LEVERAGE architecture which will be distributed over three sites.
LEVERAGE servers must provide at least three fundamental features :
A media player providing video, audio, and text resources to all workstations connected to the LEVERAGE network
A multipoint conference unit (MCU) responsible for managing all multipoint communications
An administration unit to monitor user management, session management, applications transmission, asynchronous messaging, workspace management, and all other LEVERAGE tools which can be centralised.
The system specified in this document presents the Administrative Server used in the LEVERAGE system and the tools it provides for applications working on user workstations and administrative functions. 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, and access to the system.
The LEVERAGE system will also include an HTTP server that will provide users with HTML pages which constitute the core of the LEVERAGE application. The HTTP server will be responsible for controlling access to HTML pages before sending them to workstations that have made a request.
Among other features, the LEVERAGE system includes a database which provides applications running on workstations with general static data they need. Workspace Management, one of the system tools, is responsible for providing users with disk space to store personal files. The asynchronous messaging system provides users with an e-mail system to exchange messages over the network and a news system to access conferences.
Authors: Laurent LE GRUIEC, Nicolas DELAHAYE, Didier PARIS (CAP GEMINI)
Date: 30.06.96
Contents:
LIST OF FIGURES
- SYSTEM OVERVIEW
1.1 System Architecture
1.1.1 Server Architecture
1.1.2 Workstation Architecture
1.2 Aim of the system
1.3 General constraints
- FUNCTIONAL DESCRIPTION
2.1 Inputs and Outputs
2.2 Functional description of system components
2.2.1 Administration
2.2.1.1 Creating Users
2.2.1.2 Creating Groups
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 and CGI files management
2.2.2.2 HTML pages access control
2.2.2.3 Inputs and outputs
2.2.3 Database
2.2.3.1 Creation and Update of Static Data
2.2.3.2 Inputs and Outputs
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.5 Asynchronous messaging system
2.2.5.1 Inputs and Outputs
- ENVIRONMENT DESCRIPTION
List of figures
FIGURE 1. GENERIC ARCHITECTURE
FIGURE 2. LEVERAGE SERVER ARCHITECTURE
FIGURE 3. WORKSTATION ARCHITECTURE
FIGURE 4. NEW USER WINDOW
FIGURE 5. ACCESS RIGHTS TABLE
FIGURE 6. DIRECTORY PERMISSIONS LISTS
FIGURE 7. NEW GLOBAL GROUP WINDOW
FIGURE 8. EXAMPLE OF TREE
FIGURE 9. FILE MANAGE WINDOW
FIGURE 10. PERMISSION DIRECTORY WINDOW
FIGURE 11. ADD USERS AND GROUPS WINDOW
FIGURE 12. NETSCAPE E-MAIL CONFIGURATION
|
