Architecture Document for airflow/PFE

Authors

TimP

Sections

• Database Structure
• User Interface Templates
• User Authorisation
• Third Party Software Used
• Paneris Software Used

Readership

• The project leader should at least be confident that the developers are confident that the architecture is correct.
• The developers should buy into the architecture as at least one of them should have written it :)
• Future maintainers should be able to understand the way the system as a whole fits together.

Introduction

The data structure for the ACANGold database is given here.

Database Structure

The database structure is created and maintained in MS Access Format.

The above is processed using msaccess2sql to produce the data definition in SQL and the Paneris Datadictionary format.

User Interface Templates

The templates for the user pages are held in the repository.

User Authorisation

User System

A User class which is basically a DDRecord representing the user's organisation record.

The user's id is an integer passed around in the session (read cookie).

Use the two in a handler like this:

         // Find user
        String userid = "";
        Object useridObj = context.getSession().getValue("userid");
        if (useridObj != null)
            userid = useridObj.toString();
        else throw new HandlerException("User Id missing.");

If the session has timed out, or if the user has never logged in, then the login template is presented.

PFELogin

If this handler is passed a username and password field, it will see if it can log the user on. If so, it sets the userid and user_type in the session.

Third Party Software Used

Paneris Software Used

Document Dated: Tue May 25 3:05:00 1999 by TimP
Modify this document
Previous Version