Summary

WebLogic Server is by far the most performance-proven, battle- tested , and leading J2EE application server in the application infrastructure market today. As a WebLogic Server administrator, you are responsible for ensuring you have throttled as much performance value from WebLogic Server as possible. Opting not to tune the performance of WebLogic Server not only forces your J2EE business solutions to operate in a nonoptimal environment, but you can be hinging the success or failure of a J2EE business solution solely based on its performance. In real-life terms, not performance tuning your WebLogic Server is analogous to buying a Formula One Ferrari and driving it around a Grand Prix track at 50mph.

From all perspectives, performance tuning WebLogic Server is a very time-consuming and meticulous exercise. This chapter has demystified the art of performance tuning WebLogic Server by describing a very easy-to-adopt roadmap, which can help you begin the process of identifying and resolving potential bottlenecks in your WebLogic Server environment. This approach stresses the importance of collaborating with a team of experts who collectively have detailed knowledge of how the entire WebLogic Server environment operates, as well as how performance analysis tools can greatly help you in profiling your WebLogic Server and the applications deployed to it.

This chapter also discussed in detail the concepts, techniques, and monitoring mechanisms for performance tuning the behavior of the primary aspects of WebLogic Server, from where you can derive performance value, such as execute threads, JDBC connection pools, the EJB container, HTTP sessions, and the memory management options of the JVM. You will be responsible for performance tuning all these elements as a WebLogic Server administrator.