Full HTML for

Basic foilset Status and Plans of MiddleWare(WebFlow) for Gateway

Given by Tom Haupt at ASC Gateway Project Dayton Ohio on January 7 1999. Foils prepared January 31 1999
Outside Index Summary of Material

What is WebFlow?
  • Start with examples
  • Why improve a good product?
  • Emerging Standards: DATORR
Architecture of the new WebFlow
Gateway Requirements
Deliverables

Table of Contents for full HTML of Status and Plans of MiddleWare(WebFlow) for Gateway

 Denote Foils where Image Critical
Denote Foils where Image has important information
Denote Foils where HTML is sufficient
1 Gateway System (new generation WebFlow)
2 Overview
3 WebFlow Mission
4 WebFlow Implementation
5 Middle-Tier
6 WebFlow over Globus
7 WebFlow Applications
8 Quantum Simulations
9 QS: WebFlow implementation
10 PPT Slide
11 QS: Front-End
12 LMS: Changes in Vegetation
13 LMS: Changes in Vegetation
14 LMS Front-End
15 Why do we need to change anything?
16 Remedy
17 Java Grande: DATORR Desktop Access to Remote Resources
18 CORBA based WebFlow
19 WebFlow Objectives
20 Implementation Strategy
21 Implementation Strategy
22 Multi-tier Architecture of Gateway
23 Gateway Components
24 Security Model
25 Gatekeeper
26 Gateway Portal Page
27 Initialization of a session
28 WebFlow API
29 Middle Tier
30 Building an application
31 Adding a remote module
32 WebFlow Modules
33 Event binding
34 Controlling a module
35 Modules
36 Summary of features
37 Requirements
38 Requirements: Security
39 Requirements: Front End
40 More Front-End Requirements
41 Requirements: Middle-Tier
42 Middle-Tier (cont.)
43 Back-End
44 What is available now
45 Deliverables
46 Pre-Alpha release (Feb/March 99)
47 Alpha release (June 99)
48 Beta release (Sept 99)
49 Gateway 1.0 (SC `99)
50 ASC requirements
51 Web Server Requirements Yes, https
52 User Interface Requirements this defines browser requirements!
53 Middleware Functional Requirements
54 Timeline (YES)

Outside Index Summary of Material

HTML version of Basic Foils prepared January 31 1999

Foil 1 Gateway System (new generation WebFlow)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
NPAC Syracuse University
HTML version of Basic Foils prepared January 31 1999

Foil 2 Overview

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
What is WebFlow?
  • Start with examples
  • Why improve a good product?
  • Emerging Standards: DATORR
Architecture of the new WebFlow
Gateway Requirements
Deliverables
HTML version of Basic Foils prepared January 31 1999

Foil 3 WebFlow Mission

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
The visual HPDC framework that offers an intuitive Web browser based interface and a uniform point of interactive control for a variety of computational modules and applications, running at various labs on different platforms.
Our technology goal is to build a high-level user friendly commodity software based visual programming and runtime environment for HPDC.
HTML version of Basic Foils prepared January 31 1999

Foil 4 WebFlow Implementation

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
WebFlow is implemented as a modern three-tier system
  • Tier 1 is a high-level front-end for visual programming built on top of the Web and OO commodity standards.
  • Distributed object-based, scalable, and reusable Web server and Object broker Middleware forms Tier 2.
  • Back-end services comprise Tier 3. In particular, high performance services are implemented using the metacomputing toolkit of Globus.
HTML version of Basic Foils prepared January 31 1999

Foil 5 Middle-Tier

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Mesh of Web Servers running servlets that manage and coordinate distributed computation.
  • Session Manager,
  • Module Manager,
  • Connection Manager.
HTML version of Basic Foils prepared January 31 1999

Foil 6 WebFlow over Globus

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
In order to run WebFlow over Globus there must be at least one WebFlow node capable of executing Globus commands, such as globusrun
Jobs that require computational power of massively parallel computers are directed to the Globus domain, while others can be launched on much more modest platforms, such as the user's desktop or even a laptop running Windows NT.
Bridge between WebFlow and Globus
HTML version of Basic Foils prepared January 31 1999

Foil 7 WebFlow Applications

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Quantum Simulations
  • Alliance/NCSA
  • demonstrated at Alliance `98 meeting
  • technical paper presented at SC'98
Landscape Management System
  • CEWES: MSRC/PET
HTML version of Basic Foils prepared January 31 1999

Foil 8 Quantum Simulations

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 9 QS: WebFlow implementation

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 10 PPT Slide

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 11 QS: Front-End

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 12 LMS: Changes in Vegetation

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
A decision maker (the end user of the system) wants to evaluate changes in vegetation in some geographical region over a long time period caused by some short term disturbances such as a fire or human's activities.
One of the critical parameters of the vegetation model is soil condition at the time of the disturbance.
This in turn is dominated by rainfalls that possibly occur at that time
HTML version of Basic Foils prepared January 31 1999

Foil 13 LMS: Changes in Vegetation

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Data retrieval
Data preprocessing
Simulation: two interacting codes
  • EDYS
  • CASC2D
Visualization
WMS
EDYS
CASC2D
DEM
Land Use
Soil
Texture
Vegetation
HTML version of Basic Foils prepared January 31 1999

Foil 14 LMS Front-End

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 15 Why do we need to change anything?

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Middle tier is based on a custom protocol implemented directly on top of sockets
  • not scalable
  • difficult to implement security features, fault tolerance, monitoring
  • impossible to take advantage of new technologies
  • non-standard
HTML version of Basic Foils prepared January 31 1999

Foil 16 Remedy

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
New, CORBA based middle tier
  • robust ORB implementations available now (including JWORB)
Event driven system that follows the JavaBeans model
  • based on industry standards for distributed objects technologies
  • similar to JINI and EJB
HTML version of Basic Foils prepared January 31 1999

Foil 17 Java Grande: DATORR Desktop Access to Remote Resources

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Development of WebFlow coincides with DATORR standardization initiative
Could lead to definition of CORBA facilities or Java framework for computing services
Defines:
  • Abstract Task Specification ("user view")
  • Metacomputing Services API ("system view")
  • Security Standards
HTML version of Basic Foils prepared January 31 1999

Foil 18 CORBA based WebFlow

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
(suggested Gateway implementation)
HTML version of Basic Foils prepared January 31 1999

Foil 19 WebFlow Objectives

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
To provide seamless and secure access to remote (HPCC) resources
  • single web-based point of access
  • access policies imposed and monitored by stakeholders
  • no modifications of the current security model and implementation
  • integration with the existing authoring tools
HTML version of Basic Foils prepared January 31 1999

Foil 20 Implementation Strategy

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Follow industry standards
  • distributed objects: CORBA, Java, JavaBeans, EJB, ...
  • security: https, PKI, GSSAPI, SSL, Keberos5
  • CORBA services: naming (LDAP), lifecycle, security, transactions,...
Participate in creation of standards
  • DATORR, Alliance PKI
HTML version of Basic Foils prepared January 31 1999

Foil 21 Implementation Strategy

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Use commodity components (commercial and academic). Examples:
  • secure WebServer (Jigsaw, Apache, JWORB)
  • ORB (ORBacus, JWORB)
  • Java 2 (EJB, JINI)
  • AKENTI
  • Globus, Globus-GSSAPI
  • PBS, Condor
HTML version of Basic Foils prepared January 31 1999

Foil 22 Multi-tier Architecture of Gateway

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 23 Gateway Components

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Front End (Java Applets)
  • many different "plug-ins" implementing WebFlow API
Middle Tier (CORBA)
Back End modules (anything from JBDC to HPF)
  • JavaBeans model
  • Proxy Modules
    • Access to remote HPCC resources
HTML version of Basic Foils prepared January 31 1999

Foil 24 Security Model

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
SECIOP
Front End Applet
https
authentication
& authorization
Gatekeeper
delegation
Stakeholders
HPCC resources
GSSAPI
GSSAPI
Layer 1: secure Web
Layer 2: secure CORBA
Layer 3: Secure access to resources
Policies defined by resource owners
HTML version of Basic Foils prepared January 31 1999

Foil 25 Gatekeeper

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 26 Gateway Portal Page

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
https
mutual authentication
  • X.509 certificates
access policies
  • AKENTI, (LDAP, DB)
  • controlled by stakeholders
returns front-end applet
HTML version of Basic Foils prepared January 31 1999

Foil 27 Initialization of a session

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Portal
Page
Secure
Web Server
Mutual
authentication
start
AKENTI
Credentials
Globus Cert.
Front End
Applet
WebFlow
Server
User
Context
Netscape's ORB
ORBacus ORB
IIOP
HTML version of Basic Foils prepared January 31 1999

Foil 28 WebFlow API

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Middle-tier
Back-End Services
PSE
Data Flow
OO
Command
Line
WebFlow API (Abstract Task Specification)
HTML version of Basic Foils prepared January 31 1999

Foil 29 Middle Tier

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
HTML version of Basic Foils prepared January 31 1999

Foil 30 Building an application

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Applet
Application
Context
Netscape ORB
ORBacus ORB
IIOP
List of servers
List of modules
List of events
List of methods
E
M
Add module
Attach Event
local
remote
Adapter
LLM
HTML version of Basic Foils prepared January 31 1999

Foil 31 Adding a remote module

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Local Host
Add module
Module Factory
Proxy Module
Remote Host
FE
request
Add module
Module Factory
Module
HTML version of Basic Foils prepared January 31 1999

Foil 32 WebFlow Modules

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Are CORBA objects
conform to JavaBeans specification
mimic Java 1.1 (JavaBeans) event model
implemented using Dynamic Invocation Interface (DII) and Dynamic Skeleton Interface (DSI) (thus more general than BeanBox, similar to JINI and EJB)
HTML version of Basic Foils prepared January 31 1999

Foil 33 Event binding

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
addEventListener
rmEventListener
fireEvent(E,M)
method M
Event Source
Event Target
Adapter
Event
ORB
binding
table
DII
DSI
HTML version of Basic Foils prepared January 31 1999

Foil 34 Controlling a module

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Proxy Module
Module
ActionButton1
ActionButton2
....
IIOP
HTML version of Basic Foils prepared January 31 1999

Foil 35 Modules

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Similar to JavaBeans
  • full power of Java (or C++) to implement functionality
  • can encapsulate legacy applications
May serve as Proxies
  • JDBC
  • metacomputing services (such as Globus)
  • schedulers (such as PBS, CONDOR, etc)
HTML version of Basic Foils prepared January 31 1999

Foil 36 Summary of features

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Single web-based access via Gateway portal
Security based on standards: https, PKI, secure ORB, GSSAPI (SSL/Keberos5)
Access policies controlled by stakeholders
WebFlow API allows implementation of many different front-ends
Modern three-tier architecture (distributed objects)
Access to HPCC through metacomputing services
HTML version of Basic Foils prepared January 31 1999

Foil 37 Requirements

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
(yesterday discussions)
to be further discussed and agreed upon
HTML version of Basic Foils prepared January 31 1999

Foil 38 Requirements: Security

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
authentication based on Keberos/SecurID
  • this is a particular implementation of ORB and GSSAPI
  • NPAC suggests PKI approach for the web access
    • Gateway CA
no need for new "WebFlow" user accounts
  • users needs Gateway certificates or "Gateway ID", though
  • mapping between Gateway ID and the user account is needed
  • model for authority delegation is needed
access control
  • reuse existing database
  • AKENTI uses LDAP, ORB uses Access Control Lists
HTML version of Basic Foils prepared January 31 1999

Foil 39 Requirements: Front End

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Java 1.1 Applets
  • Netscape, IE: version 4.0+
Off-shelf "vanilla" browsers
  • depends on the front-end functionality
    • swing? ORB? sophisticated PSE? Java2 plug-in?
  • basic front-end and specialized front-ends?
Make distinction between Gateway Portal and Front-End
HTML version of Basic Foils prepared January 31 1999

Foil 40 More Front-End Requirements

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Several different Front-Ends
  • basic "command line" that allows to submit a job?
  • support for existing PSE
  • independently of this project, NPAC will provide front-ends that support data-flow and oo paradigms
WebFlow API
  • how to add a new front-end
  • how to add a new component to existing FE
  • how to control back-end modules
  • how to access middle-tier services
HTML version of Basic Foils prepared January 31 1999

Foil 41 Requirements: Middle-Tier

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Distinction between user module and system service
suggested system services:
  • job submission and monitoring
  • file transfer
  • database and mass storage access
  • support for editing, debugging, compiling, visualization
  • support file manipulation (find, copy, delete, print,...)
HTML version of Basic Foils prepared January 31 1999

Foil 42 Middle-Tier (cont.)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
More APIs
  • how to add a user module (and control it from the front-end)
  • how to add a new service (such as NetSolve)
  • how to access metacomputing services
HTML version of Basic Foils prepared January 31 1999

Foil 43 Back-End

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Which metacomputing services?
  • Globus over PBS (with GRAM, GASS, MDS)?
  • Globus GSSAPI only?
  • PBS without Globus?
Support from the local system administrator is needed
HTML version of Basic Foils prepared January 31 1999

Foil 44 What is available now

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
We are using commodity components:
  • ORB, secure Web Server, AKENTI, Globus, PBS, JDK
WebFlow is an ORB application.
  • Early prototype is ready (including naming, lifecycle and security services)
WebFlow modules that interface Globus and PBS directly are ready
HTML version of Basic Foils prepared January 31 1999

Foil 45 Deliverables

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
(for the first year)
HTML version of Basic Foils prepared January 31 1999

Foil 46 Pre-Alpha release (Feb/March 99)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Functionality:
  • using a web browser submit a job to PBS and retrieve the results
Software components:
  • simplified gatekeeper, simple front-end
  • secure Web server, WebFlow server
  • basic services: file manipulation, submit a job
Purpose:
  • learn ASC environment, identify technical problems
HTML version of Basic Foils prepared January 31 1999

Foil 47 Alpha release (June 99)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Functionality:
  • using a prototype Front-End build and run an application
New software components:
  • prototype access control
  • front-end conforming to WebFlow API
  • WebFlow Server conforming to specs
  • user modules, new services (as needed by the application)
Purpose:
  • validation of spec, make it available for FE developers, feedback
HTML version of Basic Foils prepared January 31 1999

Foil 48 Beta release (Sept 99)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Functionality:
  • prototype of full functionality (as specified)
New software components:
  • full support for authentication and authorization
  • a collection of FEs, including PSE
  • WebFlow Server conforming to specs
  • complete set of services (as specified)
Purpose:
  • make available for testing by selected users
HTML version of Basic Foils prepared January 31 1999

Foil 49 Gateway 1.0 (SC `99)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Functionality:
  • full support for applications, run from Portland, OR.
New software components:
  • none (debugged beta release)
Purpose:
  • make it available for deployment
HTML version of Basic Foils prepared January 31 1999

Foil 50 ASC requirements

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Middleware Server Requirements
Common File System?? No, WebFlow is distributed
"Outside" the Environment (No NFS or NIS) Yes
No User Accounts !!! TO BE DISCUSSED !!!
Kerberos/SecurID Installed Yes, later
Registered in DNS (???)
Unix System Yes, also UNIX. Btw what UNIX?
Objects Clearly Defined & Detailed Interface Requirements Developed !!! TO BE DISCUSSED !!!
HTML version of Basic Foils prepared January 31 1999

Foil 51 Web Server Requirements Yes, https

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Web Server Requirements Yes, https
Digital Certificate Compatible
Encryption Capable
Browser Requirements Yes, 4.0+ enhanced
Netscape Compatible
Microsoft Internet Explorer Compatible
Encryption Capable
HTML version of Basic Foils prepared January 31 1999

Foil 52 User Interface Requirements this defines browser requirements!

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
"Out" for Advanced Users (from command line to more complex)
Data Facilities (Visualization, Print, Archive, View, etc) (!!! TBD !!!)
CTA Independent (???)
Kerberos/SecurID Login (!!! TO BE DISCUSSED !!!)
Multi-disciplinary Capability (???)
Interactive/Batch (YES, through metacomputing services)
Tool Access (Debuggers, Monitors, Editors, etc) (!!! TBD !!!)
Help/Information/Guidence/Training Mechanisms (!!! TBD !!!)
User-tailorable (YES, through WebFlow API)
Database Access ( YES, a WebFlow module)
Responsive to User (!!! TO BE DISCUSSED !!!)
Import/Export of Data Files (YES, through WebFlow API, or module)
HTML version of Basic Foils prepared January 31 1999

Foil 53 Middleware Functional Requirements

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Batch System Independent (YES)
HPC Platform Independent (YES)
Consistent with Metacomputing Efforts (YES)
Mass Storage Interface (may be different from site to site)
Modular Design (YES)
Multi-disciplinary Capability (YES, but let's define it...)
Compatible with Job Accounting/Allocation (!!! TBD !!!)
Database Access (YES, through a WebFlow module)
Interface with License Server(s) (YES)
Easily Maintained (Low impact to PSEs, other servers, etc)
YES
???
HTML version of Basic Foils prepared January 31 1999

Foil 54 Timeline (YES)

From Status and Plans of MiddleWare(WebFlow) for Gateway ASC Gateway Project Dayton Ohio -- January 7 1999. *
Full HTML Index
Timeline (YES)
  • Scalability (Across Platforms, CTAs, and Sites)
Database Requirements (???)
  • Consistent with Current ASC Efforts
  • Consistent with Metacomputing Efforts
© Northeast Parallel Architectures Center, Syracuse University, npac@npac.syr.edu

If you have any comments about this server, send e-mail to webmaster@npac.syr.edu.

Page produced by wwwfoil on Sun Jan 31 1999