Oct. 6, 2003 to Oct. 8, 2003
Achmad I. Kistijantoro , Newcastle University
Graham Morgan , Newcastle University
Santosh K. Shrivastava , Newcastle University
Mark C. Little , Arjuna Technologies Ltd.
A recent trend has seen the extension of object-oriented middleware to component-oriented middleware. A major advantage components offer over objects is that only the business logic of an application needs to be addressed by a programmer with support services required incorporated into the application at deployment time. This is achieved via components (business logic of an application), containers that host components and are responsible for providing the underlying middleware services required by components and application servers that host containers. Well-known examples of component middleware architectures are Enterprise Java Beans (EJBs) and the CORBA Component Model (CCM). Two of the many services available at deployment time in most component architectures are component persistence and atomic transactions. This paper examines, using EJBs, how replication for availability can be supported by containers so that components that are transparently using persistence and transactions can also be made highly available.
Availability, components, CORBA Component Model, Enterprise Java Beans, fault tolerance, middleware, replication, transactions
Achmad I. Kistijantoro, Graham Morgan, Santosh K. Shrivastava, Mark C. Little, "Component Replication in Distributed Systems: A Case Study Using Enterprise Java Beans", SRDS, 2003, Reliable Distributed Systems, IEEE Symposium on, Reliable Distributed Systems, IEEE Symposium on 2003, pp. 89, doi:10.1109/RELDIS.2003.1238058