[James Wiki] Update of "JamesArchitecture" by SimonFunnell

[Apache Wiki <wi...@apache.org>]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "James Wiki" for change notification.

The "JamesArchitecture" page has been changed by SimonFunnell.
http://wiki.apache.org/james/JamesArchitecture

--------------------------------------------------

New page:
= 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.

{{attachment:W:\ECLIPSE\JamesDocumentation\JamesArchitecture.gif|W:\ECLIPSE\JamesDocumentation\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.

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

=== JamesServices ===
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.

----
== 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?