J2EE Performance Test 

The reality

J2EE has establshed itself as the standard platform for enterprise and web applications, and is growing in popularity.

J2EE supports legacy applications and interfaces, many operating systems, distributed partitioned environments and business-critical applications, with support for security and administrative tasks.

By providing frameworks and patterns for creating modular and scalable applications, J2EE allows enterprises and their developers to concentrate on their own application code, without having to worry about details such as security, resource management or scalability.

Leading application servers such as BEA Weblogic Server or IBM Websphere offer high levels of functionality and services. Reliability, availability and scalability are achieved by the cluster and failover capabilities of multiple server instances. Other services such as security and resource management, thread pools, EJB caches and JDBC connection pools are also available.

Third party providers can supply JDBC drivers that provide database abstraction and simplify the coding of different database systems. The result is a high-performance platform that provides abstraction from the underlying technologies and makes possible the development of distributed business-critical applications.

The challenge

It sound as if nothing could ever go wrong, is that right?

Nothing, as long as the application meets the performance and load criteria imposed by the users and the production teams.

The success of a development project or business plans can depend on the facility to find, analyze and resolve performance problems. Because of greater complexity, it is much harder to resolve performance bottlenecks in multi-layer distributed J2EE applications than in monolithic applications.

J2EE environments contain many inter-connected layers consisting of software and hardware that interact with each other in order to process user requests. The members of the performance team (assuming there is one) - the architect, developer, application server administrator and database administrator - have each their own view of the system, and generally use specialised diagnostic tools.

So how can all these people work together to isolate problems?

Without a high-level view of all components of the J2EE system and their interactions, it is hardly possible to discover which part of the application is causing problems.Which resource is responsible? Is it the database, the application server, the operating system, the back-end system or the application itself?

We can help you to find out.

Using our integrated, tried and tested approach, it is possible to put all the components of a J2EE application in relation to each other, and thus gain valuable insights into load and performance behaviour. In that way, load and performance problems can quickly be traced. During development, not in production.

Would you like to know more ? Please get in touch with us