Differences between revisions 1 and 2
Revision 1 as of 2009-11-25 02:19:30
Size: 2392
Editor: SimonFunnell
Comment:
Revision 2 as of 2009-11-26 01:25:52
Size: 3020
Editor: SimonFunnell
Comment:
Deletions are marked like this. Additions are marked like this.
Line 4: Line 4:
{{attachment:W:\ECLIPSE\JamesDocumentation\JamesArchitecture.gif|W:\ECLIPSE\JamesDocumentation\JamesArchitecture.gif}} {{attachment:JamesArchitecture.gif}}
Line 11: Line 11:
==== Unit Responsibility ====
 * Qualifying infrastructure elements.
 * Supplying common transport services (TLS support).
 * Managing the JamesServices and JamesUserServices.

==== Responsible Roles ====
The JamesServer is the responsibility of the Deployer (at runtime) and Engineer (at design time).
Line 14: Line 22:
==== Unit Responsibility ====
 * ClientServices
  * SMTP
  * POP3
  * IMAP
  * NNTP
 * AdminstratorServices
  * Remote Manager
  * Improvements Proposed
 * DeployerServices
  * Remote Manager
  * Improvements Proposed
Line 15: Line 36:
These are the internal services James uses to support the JamesUserServices, they essentially make up the Mail Processing unit. This comprisies of User Information Sources, Repositories, the Mailet Container and its related resources. These are the internal services James uses to support the JamesUserServices, they essentially make up the Mail Processing unit.

==== Unit Responsibility ====
 * User Information Sources -RDBMS/LDAP
 * FetchMail/Mailet Container/Sieve
 * Spool/Repositories/Mailboxes

==== Responsible Roles ====
JamesServices are the responsibility of Adminstrators (at runtime) and Developers (design time).

JamesArchitecture

This is a summary view and some notes on the JamesArchitecture, it attempts to provide some conceptual groupings with associated terminolgy. This page is not authoritative but its reasonable.

JamesArchitecture.gif


Framework

JamesServer

This is the complete unit, it is installable as a standalone server, deployed as component of an existing server or embedded in some other arrangement. The JamesServer uses various tools and frameworks to provide the supporting runtime for JamesUserServices and JamesServices.

Unit Responsibility

Responsible Roles

The JamesServer is the responsibility of the Deployer (at runtime) and Engineer (at design time).

JamesUserServices

These are a number services that provide implement request/response based protocols, they are essentially mail delivery units.

Unit Responsibility

JamesServices

These are the internal services James uses to support the JamesUserServices, they essentially make up the Mail Processing unit.

Unit Responsibility

  • User Information Sources -RDBMS/LDAP
  • FetchMail/Mailet Container/Sieve
  • Spool/Repositories/Mailboxes

Responsible Roles

JamesServices are the responsibility of Adminstrators (at runtime) and Developers (design time).


Configuration

Administrator Configurations

  • Administrator configurations are organsation/business applications.
  • At present, the Admininstrator supplys a specification with organisation/business objects for a Deployer to deploy.
  • Adminstrator services would allow Adminstrators to do this without needing to liase with the Deployer.

Deployer Configurations

  • Deployer configurations are technology infrastructure layouts.
  • At present, the Deployer is responsible for the management of infrastructure and implementing the needs of Administrators .
  • Adminstrator services would resolve this, leaving deployers with much less responsibility.
  • Deployer services are used far less than Adminstrator services.

Current Configuration Files

These are the current files with a few notes.

Mixes Adminstrator Configuration with Deployer Configuration

config.xml/james-smtphandlerchain.xml

Administrator Configuration

miResources.xml

james-listmanager.xml

james-fetchmail.xml

Deployer Configuration

sqlResources.xml - Database statement sources.

james-liststores.xml environment.xml - Mostly logging configuration,

Deployer/Engineer configuration.

assembley.xml - Replaced with juice modules?

JamesArchitecture (last edited 2009-11-26 01:25:52 by SimonFunnell)