Dear Wiki user, You have subscribed to a wiki page or wiki category on "James Wiki" for change notification.
The following page has been changed by JuanMurillo: http://wiki.apache.org/james/WebAdminConsole The comment on the change is: Please add or modify as you see fit New page: = Web Admininistration Console = == Goals == * Zero additional installation / configuration for end user * Increase ease of use and configuration of James * No side effects to mission critical components * Decoupled so that James may be 'management console agnostic' * Developed with simple design / frameworks so as to promote developer involvement and reduce dependencies == Stages == The development of a Web Administration Console should be staged to accomodate for changes in the current James code base. Here are the forseeable stages: * Embed Tomcat * Build Core Web Application * Build Administration Commands Section * Build Health and Status Monitoring Section * Build Configuration Management Section * Build Cluster / Multiple instance Management Section //TODO (Add sections you consider useful to this list) "'Embed Tomcat'" Embed into James and make it run and deploy by adding a call to its ant script in the current run.sh and run.bat a. Copy tomcat-embedded to bin b. Copy ant to bin c. Add ant script to bin, it will run minimal tomcat and auto deploy the web app c. Modify run scripts to call the ant script (Note that ant script is the recommended method by the Tomcat team) "'Build Core Web Application'" Decide on base technologies to be used and create the core components so that adding incremental functionality will be simple and modular. a. Build an empty web application b. Decide on frameworks if any c. Decide on communication system with James server d. Decide on page layout and site navigation e. Build core application components (Controllers, Connectors to James, communication syntax, etc) "'Build Administration Commands Section'" Build this section first because it is already built into the Remote Manager so would be the simplest point to start from. a. Decouple Administrations commands from the RemoteManagerHandler class and into their own classes following the command pattern. b. Build Command calls and result pages for web application. "'Build Health and Status Monitoring Section'" //TODO "'Build Configuration Management Section'" //TODO "'Build Cluster / Multiple Instance Management Section'" //TODO
