|(22 intermediate revisions by 5 users not shown)|
document will briefly describe the I-Card Manager Enterprise Application architecture. The I-Card Manager containing a combination of Web and Enterprise JavaBeans (EJB) components that are packaged as EAR file. The conventions for J2EE applications are discussed more in [http://java.sun.com/blueprints/code/projectconventions.html# 65002 Strategy for J2EE Applications] . |+|
This the . The Web components that are packaged as file. The conventions for applications are discussed more in [http://java.sun.com/blueprints/code/projectconventions.html#Strategy for Applications].
|−|The i-card manager enterprise provides users with a web-based management interface to the user's [http://wiki.eclipse.org/index.php/I-Card I-Cards] and underlying context data (if any). This app is accessed by pressing a button (currently a Higgins mouse icon/button) that is added to the browser's toolbar. From a browser, users select from these i-cards to manage it. |+|
| || |
|−|In essence, the i-card manager enterprise consists of a front-end user Web site, which provides a face to its users, and a back-end i-card processor, which handles the i-card processing. |+|
* application users
I-Card Manager Web site application - This application provides the Web pages that let users select, create or update i-cards. The Web site application interacts with the i-card processing module (EJB) to manage i-cards. |+|
* acts as a client the []
I-Card Manager processing module (EJB) - The processing module is responsible for coordinating all activities necessary to manage user's i-cards. It interacts with all the other applications through Web services. For example it acts as a client and accesses the RPPS Web service. |+|
|−|==See Also== |+|
|−|* [ http://eclipse.org/higgins Higgins Home] |+|
|−|* [ [Higgins Wiki]] |+|
|−|* [[Architecture]] |+|
|−|* [[Components]] |+|
Latest revision as of 15:17, 15 August 2014
This page describes the Org.eclipse.higgins.icm. The org.eclipse.higgins.icm contains Web components that are packaged as WAR file. The conventions for Web applications are discussed more in Strategy for Web Applications.
- Front end: Google GWT web application for users
- Back end: acts as a client of the I-Card Service.