A J2EE application or a Java 2 Platform Enterprise Edition application is any deployable unit of J2EE functionality. This can be a single J2EE module or a group of modules packaged into an EAR file along with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers.

PropertyValue
p:abstract
  • A J2EE application or a Java 2 Platform Enterprise Edition application is any deployable unit of J2EE functionality. This can be a single J2EE module or a group of modules packaged into an EAR file along with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers. Enterprise applications can consist of the following: * EJB modules (packaged in JAR files); * Web modules (packaged in WAR files); * connector modules or resource adapters (packaged in RAR files); * Session Initiation Protocol (SIP) modules (packaged in SAR files); * application client modules; * Additional JAR files containing dependent classes or other components required by the application; * Any combination of the above. My first article is “J2EE Server Scalability Through EJB Replication”, by Daniel Hagimont, Sylvain Sicard, Noel De Palma. The article starts with the needs of web servers and their evolution. It describes about EJB clustering and the issues faced by those servers. Then the authors put forth various approaches and explain about EJB cache evaluation, replication and partition. They also discuss about partitioning details and Hybrid solution. The article compares servlet server and EJB server. There are two main reasons to switch over to EJB server. They are  clustered JNDI  load-balancing and failover by cluster-aware stubs In EJB clustering, cluster stubs are used for load balancing. Each bean is loaded on every server. As a result, Bean is replicated and lead to consistency problem. We prefer systematic access on Database and consistency should be ensured by database transaction. But, here Beans cannot be cached. There are two approaches for this problem. One of which is EJB server specialization. This server is Server dedicated to a subset of J2EE application’s Beans. Load Balancing depends on accessed Beans. The other one is to enable caching. This article discusses about the performance obtained with the RUBiS benchmark when the cache is enabled. Here the application descriptor specifies that beans cannot be shared. This action site is modeled after eBay. Load injector: 15% read-write interactions. The Database is 1.4 GB. The result is that the throughput increases linearly according to the injected load. The experiment with EJB replication system based on CMI shows that the performance benefits from replication can be counterbalanced by the disabling of the cache. In EJB partitioning method, each EJB is deployed on a single server. There is no EJB replication and allows EJB caching. The number of remote communications is more important in our partitioning solution. With CMI, as soon as a session started in an EJB server, all invocations (to JNDI, a factory or a bean) are local. They go for Hybrid solution to reduce remote communication as much as possible. It is to distinguish read-only data from data which can be written. (en)
p:hasPhotoCollection
rdfs:comment
  • A J2EE application or a Java 2 Platform Enterprise Edition application is any deployable unit of J2EE functionality. This can be a single J2EE module or a group of modules packaged into an EAR file along with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers. (en)
rdfs:label
  • J2EE application (en)
skos:subject
foaf:page
p:redirect