| |
The architecture of EnginFrame is logically structured
into three tiers, and widely based on established standards:
 |
 |
Client
Tier, which basically consists of the user's web browser,
provides a comfortable framework for the users to interact with.
|
|
Resource
Tier, where a number of "Agents" control the actual computing
resources (clusters, standalone hosts, etc.), provides distributed
access to existing computing resources using XML and Java technologies.
Questa impostazione preserva le caratteristiche e le scelte storiche
effettuate in passato e si adatta ad esse. |
|
Server
Tier, in which servlet-enabled web servers provide resource
brokering and management, keeps control of resource activities in
the back-end. |
| |
Despite
sometimes two tiers may be overlapping on the same machine (e.g. Web
server or client being part of a Resource cluster), the separation
into three tiers gives the highest architectural freedom to allow
integration with third party resources or information providers.
|
