Java IoT Authors: Tim Hinds, Elizabeth White, Yeshim Deniz, Liz McMillan, Pat Romanski

Related Topics: Java IoT

Java IoT: Article

Clustering the BEA WebLogic Application

Clustering the BEA WebLogic Application

Mission-critical Web-based applications ­ customer self-service, distribution channel and supply chain management, online trading and banking ­ must be deployed on a cluster of servers in order to provide scalability and high availability. Scalability means that servers can be dynamically added or removed as needed to meet user demand, and that the overall load of requests is distributed among the servers so that resources remain fully utilized. High availability means that there is no "single point of failure" in either the system or the application, and that requests automatically failover from nonworking components to working components. Ideally, clustering should be transparent to applications: externally, the cluster should present a "single-system image." In addition to simplifying the task of application development, this allows off-the-shelf components to be deployed without modification.

The Java Enterprise APIs are rapidly becoming the primary programming model for Web-based applications. These APIs present two particularly challenging aspects for a clustering solution. First, they require integration with front-end Web servers, a fixed technology that is external to the cluster. Second, they require back-end management of objects, which by their nature have internal state. In contrast, conventional middleware such as TP monitors generally support only stateless RPC-based services. The hard part about managing state is that excessive communication between servers ­ to replicate objects for availability, for example ­ can interfere with scalability.

The BEA WebLogic Server provides an integrated implementation of the Java Enterprise APIs. A BEA WebLogic Cluster is a group of WebLogic servers that coordinate their actions to provide scalable, highly available services in a transparent manner. Since the WebLogic Server is written entirely in Java, WebLogic clusters are independent from the underlying hardware and operating system.

Thus a WebLogic cluster can be composed of, say, uniprocessor Intel machines running Microsoft NT, large-scale Sun multiprocessors running Solaris, and IBM AS/400s. In contrast, platform-specific clustering solutions require that every node run the same operating system. Of course, this allows them to use proprietary hardware, such as shared disks, multitailed disks and high-speed interconnects, for communication between servers. As an alternative, WebLogic uses highly optimized protocols based on new commodity technologies such as IP multicast.

This JDJ feature article presents an overview of BEA WebLogic Clusters.

Architecture of a BEA WebLogic Cluster
Figure 1 shows a high-level view of the architecture of a WebLogic cluster. BEA WebLogic Server provides software-based clustering to ensure scalability and high availability for Web and Java deployments. WebLogic clustering uniquely supports transparent replication, load balancing and failover for Web page generation (presentation logic) and Enterprise JavaBeans components (business logic).

The Web server front end supports dynamic construction of HTML pages using Java Servlets, Java HTML and Java Server Pages (JSP). The application-logic back end hosts objects and components using Java Remote Method Invocation (RMI), Enterprise Java-Beans (EJB) and the Java Naming and Directory Interface (JNDI). Other back-end Java Enterprise APIs, such as JDBC and JMS, are clustered using RMI, EJB and JNDI in much the same way as applications. The front and back ends are made up of rather different components that are clustered independently.

The Web Server Front End
A WebLogic cluster may be positioned behind standard Web servers such as Netscape Enterprise Server or Microsoft Internet Information Server (IIS). HTTP requests from Web clients, such as browsers, may be handled by these Web servers or the WebLogic front end. Requests for dynamically generated pages are proxied from the Web servers to WebLogic Servlet/JHTML/JSP engines in the front end. This is accomplished using Web server proxy plug-ins, e.g., defined according to the Netscape API (NSAPI) or the Microsoft Internet Server API (ISAPI).

The first line of clustering uses "DNS Round Robin" between the Web clients and the Web servers. DNS, the Internet's Domain Name Service, resolves a Web site's name to a list of IP addresses for the site's Web servers. Each time it gets a lookup request, DNS shuffles the list of addresses it returns. A Web client generally contacts the first server on the list provided by DNS. After some timeout period, or if this server fails, the client makes another DNS request and continues with a new server. This provides a simple form of load balancing and failover. It is possible to install more sophisticated IP-level load balancing and failover schemes that, for example, take into account Web server load, remove failed servers from the list returned by DNS and/or ensure that a client session is always handled by the same Web server (modulo failures).

The second line of clustering is for dynamically generated pages and goes between the Web servers and Servlet/JHTML/JSP engines in the front end of the cluster. The Web server proxy plug-ins perform load balancing and failover between the Servlet/JHTML/JSP engines. They use a session-level round-robin algorithm that is weighted by information about server load, which is piggybacked onto HTTP responses. If the WebLogic front end is configured to handle all HTTP requests, so that the standard Web servers are missing, then the situation looks even brighter.

Since the load balancing and failover algorithm is part of the server, it uses information about server load that is shared across the cluster as a matter of course. More important, this algorithm prefers the local Servlet/JHTML/JSP engine, unless the load is very unevenly distributed, so the request never has to leave the address space of the JVM.

When a Web client first contacts a cluster of Web servers, a session is created that lasts until some idle timeout expires. The Java standards include the notion of Servlet Session State, which is automatically retained on the servers during the session. As an example, Servlet Session State might be used to retain the contents of a shopping cart in a retail application. WebLogic clusters provide for highly available Servlet Session State using disk-based or in-memory replication (as described in more detail later).

The Application-Logic Back End
In the back end, a user- or system-level service is clustered by making an instance of an object (RMI) or component (EJB) that provides the service available on several different servers. An unclustered service is invoked by calling methods of a stub, which marshals the arguments and passes them to a particular remote object. A clustered service is invoked by calling methods of a smart stub, which can find the possible instances of the service and switch between them as needed for load balancing and failover. A variety of load balancing and failover algorithms are provided. It is possible to specify the particular algorithm to use with a given service at the time that service is deployed.

The default is a transaction-level round-robin algorithm that attempts to colocate all services invoked within the same transaction. This algorithm takes server load into account only if the stub appears on a server, since load information is expensive to obtain on a client.

When the Servlet/JHTML/JSP engine invokes a clustered back-end service, server-side load balancing occurs. A programmed client may invoke a clustered service directly, resulting in client-side load balancing, or it may have the service invoked on its behalf within the cluster.

There are two forms of clustered back-end services: stateless, which are instance-neutral; and stateful, which are instance-specific. These forms are treated quite differently within the cluster.

Stateless Services
A stateless service may not maintain state on behalf of an application, rather like a conventional RPC. It may of course access application state, but only by loading it temporarily into memory from a database, file system or other external medium. The EJB component model provides a natural way of implementing stateless services, namely, stateless session beans. Stateless services can also be implemented as RMI objects, but then it is up to the programmer to abide by this restriction.

The stateless service model has been widely advocated because it promotes scalability. There are two reasons for this. First, it obviates the need to back up state in the interests of availability, e.g., by replicating it within the cluster. Second, it allows load balancing to occur on every invocation of the service. This is because the service is "instance-neutral," that is, it doesn't matter which instance of the service is invoked.

When a stateless service is deployed in a WebLogic cluster, an instance of the service is created on each server that hosts it. A smart stub obtains references to these instances from the clusterwide naming service and switches between them as needed for load balancing and failover. Retries occur only if it can be guaranteed that a failed operation did not have side effects, e.g., because it never got started, it was transactional and an abort clearly occurred, or it was declared to be idempotent. If such cases do not apply, application code may contain explicit retries, perhaps after undoing side effects. Other than this, clustering is completely transparent to the application.

WebLogic clusters support an important special case of stateless services: service factories that create unclustered stateful service objects. The factory itself is stateless, so its stub can do load balancing and failover in the usual way. The service objects created by the factory are not clustered, however, and may therefore maintain state on behalf of an application. Since this state is not backed up, it will be lost if the object fails. Application code must therefore contain an explicit retry loop that creates a new instance of the object. EJB stateful session beans fit naturally into this model, since they are not persistent. This model may also be used with RMI objects.

Stateful Services
A stateful service may maintain state on behalf of an application. Such a service is "instance-specific" in the sense that each request is intended for a particular instance of the service. In a cluster, the state must be backed up in the interests of availability and can migrate in the interests of load balancing or availability. The cluster must therefore provide some kind of internal activation service that finds or creates service instances. If an instance can be concurrently used by several clients, as is the case for persistent components such as EJB entity beans that are accessed by a global key, then this service must ensure that conflicts do not arise.

One approach to state maintenance is to keep the state in a database or other persistent store. This is particularly suitable for persistent components, but may also be applied to transient objects. This approach scales like stateless services, and in fact differs only in that the latter requires explicit disk reads/writes. The activation service can avoid concurrency conflicts here simply by relying on underlying database locking. In a WebLogic cluster, EJB entity beans always use this approach (see Figure 2).

A related approach is to maintain a write-through cache, which keeps a current copy of the state in memory to avoid subsequent reads. This makes it considerably harder to avoid concurrency conflicts, and doing so can interfere with scalability. Databases are very good at caching objects in memory and doing the minimal disk I/O necessary to provide transactional protection. Application servers may not do much better for persistent components, and so such caching may be best applied to transient objects that are used by a single client.

A third approach is to keep a secondary copy in memory on another machine. This is of course more susceptible to failures and isn't suitable for persistent components. The hard part here is determining when and how the state of an object has changed. (Persistent components are generally just written out on transaction boundaries.) If the application programmer is made responsible, presumably through some proprietary API, then the feature becomes harder to use. If the system is made responsible, then the feature may be less efficient since unnecessarily large updates may be performed more often than necessary.

In a WebLogic cluster, stateful session beans and RMI objects can be configured to use in-memory replication. The replication system relies on the programmer to determine when and how the state of an object has changed. It then takes care of transporting an update delta from the primary copy to the secondary copy. Scalability comes from distributing the primaries and secondaries across the cluster. This is in contrast to replication systems that keep all of the objects on (1) a fixed-size subset of the servers or (2) all of the servers.

The Naming Service
Access to clustered services is obtained through a JNDI-compliant naming service, which is itself replicated across the cluster so there is no single point of failure. To offer an instance of a clustered service, a server advertises a provider at a particular node in the replicated naming tree. Each server in the cluster adds a stub for this provider to a service pool stored at the node in its copy of the tree. When a client looks up the service, it obtains a smart stub that knows about the pool at this node. When the stub needs to find a provider for load balancing or failover, it chooses from a list obtained from this pool.

The BEA WebLogic Server had evolved to meet the demands for scalability and high availability for mission-critical Web-based applications. BEA WebLogic Clusters provide scalable, highly available services in a transparent manner. The challenges of software-only clustering have been met by a combination of careful state management and highly optimized protocols based on new commodity technologies such as IP multicast. Initial measurements show that WebLogic clusters are both high performance and highly scalable. As an example, RMI benchmarks have shown that the throughput of a WebLogic cluster servicing 10,000 active clients scales linearly up to 10 servers, providing a maximum of 7,942 round-trip method invocations per second. In this benchmark, each server was on single-processor running Microsoft NT 4.0 with the JavaSoft JVM and the Symantec JIT. Similarly, tests at IBM have shown linear scaling up to 12 AS/400 processors. In general, experience with the BEA WebLogic Server has shown that Java and EJB do not pose limitations on performance as previously believed, and in fact can deliver the levels of performance, scalability and high availability required for mission-critical Web-based applications.

More Stories By Dean Jacobs

Dean Jacobs is an architect at WebXpress, a BEA company, where he is responsible for the WebLogic Server core and WebLogic clusters. He received his Ph.D. in computer science from Cornell University in 1985.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@ThingsExpo Stories
"There's plenty of bandwidth out there but it's never in the right place. So what Cedexis does is uses data to work out the best pathways to get data from the origin to the person who wants to get it," explained Simon Jones, Evangelist and Head of Marketing at Cedexis, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
In their session at @ThingsExpo, Shyam Varan Nath, Principal Architect at GE, and Ibrahim Gokcen, who leads GE's advanced IoT analytics, focused on the Internet of Things / Industrial Internet and how to make it operational for business end-users. Learn about the challenges posed by machine and sensor data and how to marry it with enterprise data. They also discussed the tips and tricks to provide the Industrial Internet as an end-user consumable service using Big Data Analytics and Industrial C...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...
DXWordEXPO New York 2018, colocated with CloudEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term.
To Really Work for Enterprises, MultiCloud Adoption Requires Far Better and Inclusive Cloud Monitoring and Cost Management … But How? Overwhelmingly, even as enterprises have adopted cloud computing and are expanding to multi-cloud computing, IT leaders remain concerned about how to monitor, manage and control costs across hybrid and multi-cloud deployments. It’s clear that traditional IT monitoring and management approaches, designed after all for on-premises data centers, are falling short in ...
With privacy often voiced as the primary concern when using cloud based services, SyncriBox was designed to ensure that the software remains completely under the customer's control. Having both the source and destination files remain under the user?s control, there are no privacy or security issues. Since files are synchronized using Syncrify Server, no third party ever sees these files.
Cloud-enabled transformation has evolved from cost saving measure to business innovation strategy -- one that combines the cloud with cognitive capabilities to drive market disruption. Learn how you can achieve the insight and agility you need to gain a competitive advantage. Industry-acclaimed CTO and cloud expert, Shankar Kalyana presents. Only the most exceptional IBMers are appointed with the rare distinction of IBM Fellow, the highest technical honor in the company. Shankar has also receive...
In his session at 21st Cloud Expo, Carl J. Levine, Senior Technical Evangelist for NS1, will objectively discuss how DNS is used to solve Digital Transformation challenges in large SaaS applications, CDNs, AdTech platforms, and other demanding use cases. Carl J. Levine is the Senior Technical Evangelist for NS1. A veteran of the Internet Infrastructure space, he has over a decade of experience with startups, networking protocols and Internet infrastructure, combined with the unique ability to it...
"Cloud Academy is an enterprise training platform for the cloud, specifically public clouds. We offer guided learning experiences on AWS, Azure, Google Cloud and all the surrounding methodologies and technologies that you need to know and your teams need to know in order to leverage the full benefits of the cloud," explained Alex Brower, VP of Marketing at Cloud Academy, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clar...
Andrew Keys is Co-Founder of ConsenSys Enterprise. He comes to ConsenSys Enterprise with capital markets, technology and entrepreneurial experience. Previously, he worked for UBS investment bank in equities analysis. Later, he was responsible for the creation and distribution of life settlement products to hedge funds and investment banks. After, he co-founded a revenue cycle management company where he learned about Bitcoin and eventually Ethereal. Andrew's role at ConsenSys Enterprise is a mul...
Internet-of-Things discussions can end up either going down the consumer gadget rabbit hole or focused on the sort of data logging that industrial manufacturers have been doing forever. However, in fact, companies today are already using IoT data both to optimize their operational technology and to improve the experience of customer interactions in novel ways. In his session at @ThingsExpo, Gordon Haff, Red Hat Technology Evangelist, shared examples from a wide range of industries – including en...
"Space Monkey by Vivent Smart Home is a product that is a distributed cloud-based edge storage network. Vivent Smart Home, our parent company, is a smart home provider that places a lot of hard drives across homes in North America," explained JT Olds, Director of Engineering, and Brandon Crowfeather, Product Manager, at Vivint Smart Home, in this SYS-CON.tv interview at @ThingsExpo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Rodrigo Coutinho is part of OutSystems' founders' team and currently the Head of Product Design. He provides a cross-functional role where he supports Product Management in defining the positioning and direction of the Agile Platform, while at the same time promoting model-based development and new techniques to deliver applications in the cloud.
DevOpsSummit New York 2018, colocated with CloudEXPO | DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City. Digital Transformation (DX) is a major focus with the introduction of DXWorldEXPO within the program. Successful transformation requires a laser focus on being data-driven and on using all the tools available that enable transformation if they plan to survive over the long term. A total of 88% of Fortune 500 companies from a generation ago are now out of bus...
delaPlex is a global technology and software development solutions and consulting provider, deeply committed to helping companies drive growth, revenue and marketplace value. Since 2008, delaPlex's objective has been to be a trusted advisor to its clients. By redefining the outsourcing industry's business model, the innovative delaPlex Agile Business Framework brings an unmatched alliance of industry experts, across industries and functional skillsets, to clients anywhere around the world.
Business professionals no longer wonder if they'll migrate to the cloud; it's now a matter of when. The cloud environment has proved to be a major force in transitioning to an agile business model that enables quick decisions and fast implementation that solidify customer relationships. And when the cloud is combined with the power of cognitive computing, it drives innovation and transformation that achieves astounding competitive advantage.
Headquartered in Plainsboro, NJ, Synametrics Technologies has provided IT professionals and computer systems developers since 1997. Based on the success of their initial product offerings (WinSQL and DeltaCopy), the company continues to create and hone innovative products that help its customers get more from their computer applications, databases and infrastructure. To date, over one million users around the world have chosen Synametrics solutions to help power their accelerated business or per...