System to provide distributed J2EE processing in a capacity on demand environment
Original Publication Date: 2004-May-25
Included in the Prior Art Database: 2004-May-25
As service provision moves towards the 'on-demand' era there is a need to develop application and infrastructure architectures to enable the delivery of such services. This paper provides a brief discussion and proposed architecture for the delivery of such services on existing J2EE compliant platforms.
System to provide distributed J 2EE processing in a capacity on demand environment
This paper discusses at an abstract level one solution to the delivery of e-business on demand applications which are based on J2EE* platform and architectures. The aim is to provide a mechanism for enabling the distribution of application components, such as EJB*s, the processing of them, and the aggregation and processing of the results such that the components of an application may be delivered across a number of physical or logical nodes in an environment, based on required processing capacity and load. A core element is the use of Web services like interfaces between operational components to support the transfer of request and response data, including those relating to the execution of a transaction on a remote distributed node.
The proposed architecture assumes that an application server platform, conforming with the J2EE specification is already available, and that the required custom modules to enable the operation of the solution may be installed to extend the application server function. Given this infrastructure the architecture provides a system to facilitate the distribution and execution of J2EE architecture compliant components e.g.Beans, EJBs, Servlets, across a number of distributed and unrelated nodes in an ad-hoc basis to support capacity on demand.
The system provides the necessary elements to support (and not limited to) code registration,
code distribution and management, transaction initiation and work load balancing (across the nodes servicing the application components),
transaction result aggregation,
de-registration and housekeeping
The advantage of this system and model of delivering the service is that the expensive hardware and software need not be dedicated solely to the processing of one application, or even one customer's code. When extra capacity is required it may be allocated in either a new logical or physical location transparent to the core J2EE server environment.
At the core of the operation of the environment is the use and implementation of XML and web services interfaces between the major system components to support the flow of data and the exchange of system related messages.
The following diagram provides a logical overview of the main components involved in the system, some of the components being singular representations of what may be multiple instances e.g. web servers, application servers and J2EE execution nodes:
Application ApplicationResource Manager
Web Services Interface
Resource Management Interface
Core J2EE Application Server
Application Interface Module
Web Services Interface
Transaction Packaging Module
Transaction Response Module
J2EE execution node
Web Services interface
Supporting this logical model is a physical model comprising a secure, multi-layered switched network architecture which...