Chapter 7: New Features in EAServer 4.0
EAServer 4.0 includes the following features to improve application performance.
For improved performance, EAServer 4.0 can run with JDK 1.3 and the Java Hotspot virtual machine. On some platforms, EAServer can also use the Java Hotspot VM with JDK 1.2. The server JDK is determined by the command-line syntax that you use to start the server. For details, see Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide.
EAServer 4.0 includes a servlet response cache to improve response times for Web clients. When page caching is enabled for a servlet or JSP, EAServer checks the cache before invoking the servlet. If an appropriate response is found in the cache, EAServer returns the contents of the cache, instead of calling the servlet. If a response is not found in the cache, EAServer invokes the servlet, then saves the response and the response headers in the cache.
Servlet response caching can be enabled and configured in EAServer Manager. No programming is required. For more information, see Chapter 5, “Web Application Tuning,” in the EAServer Performance and Tuning Guide.
EAServer 4.0 supports instance and query caching for EJB entity beans and components of other types that use the entity design pattern. Caching can improve performance for entity components that use automatic persistence by minimizing the number of database select queries required for ejbLoad operations and finder method invocations. For more information, see Chapter 4, “EJB CMP Tuning,” in the EAServer Programmer’s Guide.
EAServer 4.0 enhances the existing stateful failover architecture with support for failover in memory. This feature allows component instance state to be maintained on a pair of servers, without incurring the overhead of using a remote database to store component state. For more information, see Chapter 28, “Configuring Persistence for Stateful Session Components,” in the EAServer Programmer’s Guide.
|Copyright © 2005. Sybase Inc. All rights reserved.|