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

Responsible Roles

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


Configuration

Administrator Configurations

Deployer Configurations

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)