WebSphere Application Server Research Articles

Comprehensive tuning guide: IBM MDM, PME algorithm, services, and configurations

The research paper provides comprehensive guidance on tuning specifics to maximize the efficiency of IBM MDM, particularly in high-performance environments. It addresses several advanced topics and tuning guidelines, focusing on the architectural framework and the details required for sustained performance. Including the recommendations to Handle Long-Chained Duplicates in Suspect Duplicate Processing (SDP), Minimize Deadlocks During Duplicate Processing, and Advanced Database Configurations for High-Performance WebSphere Application Server (WAS) Java Virtual Machine (JVM) and Cache Optimization, and Thread and session management, upgrading the Java version to hava8, Garbage Collection (GC) and Heap Memory Settings, servlet caching, and reduced application logging, MDM Workbench recommendations, Services tuning, and Batch processor tuning. IBM Messaging Queue’s Max server connections and Queue Connection Factory Settings.

Manage HTTP Session in Websphere Application Server V7 Cluster

This paper introduced that how to manage HTTP session in in WebSphere Application Server V7 cluster, and what is Session Affinity, how to achieve the persistence management. The merits and drawbacks of two kinds of schemes are discussed which are be supported by WebSphere Application Server. In the end, some suggestions for persistence management tuning are proposed to meet the users’ requirement of high performance and high reliability.

Reducing trace selection footprint for large-scale Java applications without performance loss

When optimizing large-scale applications, striking the balance between steady-state performance, start-up time, and code size has always been a grand challenge. While recent advances in trace compilation have significantly improved the steady-state performance of trace JITs for large-scale Java applications, the size control aspect of a trace compilation system remains largely overlooked. For instance, using the DaCapo 9.12 benchmarks, we observe that 40% of traces selected by a state-of-the-art trace selection algorithm are short-lived and, on average, each selected basic block is replicated 13 times in the trace cache. This paper studies the size control problem for a class of commonly used trace selection algorithms and proposes six techniques to reduce the footprint of trace selection without incurring any performance loss. The crux of our approach is to target redundancies in trace selection in the form of either short-lived traces or unnecessary trace duplication. Using one of the best performing selection algorithms as the baseline, we demonstrate that, on the DaCapo 9.12 benchmarks and DayTrader 2.0 on WebSphere Application Server 7.0, our techniques reduce the code size and compilation time by 69% and the start-up time by 43% while retaining the steady-state performance. On DayTrader 2.0, an example of large-scale application, our techniques also improve the steady-state performance by 10%.

An immune inspired co-evolutionary affinity network for prefetching of distributed object

In distributed object computing (DOC) containers, cache strategy as a passive approach improves the performance by caching the recently accessed objects. By the advent of large-scale enterprise applications of DOC, caching methods fail to keep pace with the increasing importance of performance and the increasing scale of DOC system. Prefetching is an effective approach to improve the performance. It generates and stores pages or objects in caches in advance, by predicting the requests. In the current DOC container, prefetching strategy is not supported and seldom studied in the literature. The immune system with faster secondary response and its affinity network inspire applying the immune mechanisms to build holistic model of DOC for performance improvement. In this study, a co-evolutionary affinity network (CEA-Net) is proposed for prefetching distributed objects. In CEA-Net, objects are antibodies and computation tasks are antigens. Invocation relations among object classes are modeled by the immune network of antibody genotypes. Multiple affinity measures among antibody, antigen, genotypes of antibody and antigen, genotype set and antibody population are defined to model the complex relations among distributed objects. Especially in the antibody population, immune principles including clonal proliferation, immune memory, immune toleration and elimination are designed to add evolutionary features to the antibody population. Based on CEA-Net, the prefetching architecture for DOC is built including 5 main procedures, Network Abstractor, Access Recorder, Object Factory, Cache Engine and Prefetch Engine. Finally, the experimental study shows the promising access performance and the evolutionary features of CEA-Net. CEA-Net is instructive for the future design of high performance DOC containers, such as WebSphere Application Server and BEA WebLogic Application Server.

An antibody network inspired evolutionary framework for distributed object computing

In order to meet the increasing scale and users requirements for the distributed object computing (DOC) systems, their infrastructures are highly desirable to be redesigned. Based on the principles of immune system and the evolution mechanisms learned from an antibody network model, a novel evolutionary framework for DOC (E-DOC) is proposed. The antibody network model as well as the evolution process including clonal proliferation, immune elimination, and immune memory is studied. Then, E-DOC framework based on the antibody network is proposed, whose simulation platform is designed and implemented. On the platform, the evolutionary features are studied by: (1) diversity and stability of antibodies and genotypes, (2) detection and elimination of antigens, (3) effect of immune memory, and (4) tendency of eliminated and stimulated antigens. The experiment results show that the proposed framework can achieve the evolution ability and the promising performance, which are critical to DOC systems. E-DOC is extendable for the future design of distributed object middleware, such as WebSphere Application Server and BEA WebLogic Application Server.

Web-based random variate generation for stochastic simulations

This paper presents a random variate generation (RVG) world wide web (web) service and an RVG web-based software application, both of which are developed in compliance with the Java 2 Enterprise Edition (J2EE) architecture and run under the IBM WebSphere Application Server. The RVG web service can be invoked programmatically over the web by using simple object access protocol (SOAP) through the hyper text transfer protocol (HTTP) using the extensible markup language (XML). The RVG web service and software both generate random variates from 27 probability distributions and provide general statistics, scatter plot, and histogram of the requested random variates. The plots and histograms are created in the scalable vector graphics (SVG) format. The RVG web service can be used for stochastic input data modelling of a web-based simulation. The RVG software can be used as a web-based application for a variety of purposes including teaching random variate generation, probabilistic modelling and random experimentation.

Sharp choices [.Net and J2EE

When Microsoft launched its .Net environment, the company also launched two new languages to be used with its Visual Studio.Net tools: C# and VB.Net These were designed to drive the next generation of Web services and applications. C# was based on C++ and was intended to be both simpler than its parent and confer features associated with Java, such as type safety. VB.Net can be regarded as a new version of Visual Basic but is sufficiently different to its parent to represent a big change for developers. Microsoft has claimed that there are advantages in learning these new languages but the key question remains is whether there is a demand among Microsoft shops for IT professionals to learn them. Currently, enterprises have to make a choice between two competing architectures: .Net, based on Windows technologies; and Java 2.0 Enterprise Edition (J2EE), which is used in products such as the IBM Websphere and BEA logic application server.

WebSphere Application Server: A foundation for on demand computing

WebSphere® Application Server is the foundation for IBM's middleware software portfolio. It has evolved rapidly from a simple extension for Web servers and a server runtime for business objects to the IBM distributed operating system for mission-critical computing and the leading application server in the industry. WebSphere Application Server plays a central role in the transformation from a distributed operating system to a distributed on demand operating system. This transformation is achieved by forging extensions to the WebSphere Application Server foundation for the grid-computing infrastructure, rich Web-based interaction models, service-oriented architecture, autonomics, business process management, and dynamic provisioning and utility management. This paper describes elements of the WebSphere Application Server architecture and how this architecture provides a foundation for the on demand computing infrastructure and application environment.

Designing WebSphere Application Server for performance: An evolutionary approach

Performance and scalability are critical elements for a successful Web site and therefore, are fundamental design criteria for the IBM WebSphere® platform. This paper focuses on the evolution of IBM WebSphere Application Server performance and scalability features, the improvements that were achieved, and directions for future work. There are three design principles underlying the success of WebSphere: (1) optimize the design for the predominant (no-failure) case, (2) make finite resources appear infinite, and (3) minimize the number of interprocess calls. We illustrate the application of these design principles in key areas, including workload management, Hypertext Transfer Protocol (HTTP) session management, back-end connection management, session data and content caching, and Enterprise JavaBean™ (EJB™) design and deployment patterns.

WebSphere Dynamic Cache: Improving J2EE application performance

The Dynamic Cache is part of the IBM solution for improving performance of Java 2 Platform, Enterprise Edition (J2EE™) applications running within WebSphere Application Server. It supports caching of Java™ servlets, JavaServer Pages™ (JSP™), WebSphere® command objects, Web services objects, and Java objects. This paper describes the techniques used by the Dynamic Cache for caching these objects and demonstrates the performance improvement gained by applying these techniques to a typical enterprise Web application.

WebSphere connector architecture evolution

The ability of applications to communicate with resources that are outside of the application server process and to use those resources efficiently has always been an important requirement for application developers. Equally important is the ability for vendors to plug in their own solutions for connecting to and using their resources. These capabilities have evolved over time in the IBM WebSphere Application Server, from the JDBC™ application programming interface to the Common Connector Framework and later to the J2EE™ Connector Architecture, the latter providing functions such as application server inbound communications, life cycle management, and work management. In this paper, the evolution of the WebSphere Application Server implementation of these architectures, their benefits, and their trade-offs are discussed. A preview of an important new architecture, the WebSphere Channel Framework Architecture (a logical extension to the J2EE Connector Architecture) is also presented.

The WebSphere Application Server architecture and programming model

This paper discusses the infrastructure that IBM is providing to support the World Wide Web and to facilitate Web applications and commerce. This effort started as an architecture called the Network Computing Framework (NCF), and is now the foundation of the IBM WebSphere Application ServerTM. The WebSphere Application Server is a product IBM first delivered in June 1998. In this paper we discuss this architecture and programming model We start with a brief introduction and history of the NCF, then examine the architecture of the WebSphere Application Server. We take a close look at the core run time of the WebSphere Application Server, then delve into the JavaTM programming model that supports this architecture. We also present the reasons why Java is a prominent part of this architecture, and see what relevant technologies Java provides for this run time.