We discuss key issues involved in the caching of Enterprise JavaBeans (EJBs) on an Edge-Server, and then present the architecture and algorithms that we have used to build an edge-server that solves these issues. The ability to cache EJBs is important because current edge-servers permit only caching of data such as static HTML pages. Applications that access stateful data must therefore access the back-end server frequently, so that performance is affected by network latency and the existence of system “hot spots”. With cached EJBs, edge-servers can run transactional applications that access dynamically changing data using a well known application programming interface. The behavior of the EJB runtime is functionally indistinguishable from that of a standard J2EE server, and thus the application behavior is unchanged. We also show that, with relatively little effort, non-cached applications can be transparently transformed into edge-server applications.
By: Avraham Leff, James T. Rayfield
Published in: RC22376 in 2002
LIMITED DISTRIBUTION NOTICE:
This Research Report is available. This report has been submitted for publication outside of IBM and will probably be copyrighted if accepted for publication. It has been issued as a Research Report for early dissemination of its contents. In view of the transfer of copyright to the outside publisher, its distribution outside of IBM prior to publication should be limited to peer communications and specific requests. After outside publication, requests should be filled only by reprints or legally obtained copies of the article (e.g., payment of royalties). I have read and understand this notice and am a member of the scientific community outside or inside of IBM seeking a single copy only.
Questions about this service can be mailed to reports@us.ibm.com .