Installation guide

CHAPTER 4 New features in EAServer 5.1
What’s New 17
Web application synchronization enhancement
When synchronizing Web applications, you can optionally exclude Java class
files that are listed in the Web application’s custom class list. Doing so may
save time if these files are already present on the host server or included in the
file set of other entities that are being replicated at the same time. For more
information, see Chapter 6, “Clusters and Synchronization,” in the EAServer
System Administration Guide.
Instance pool monitoring
The runtime monitoring feature in EAServer Manager has been extended to
display component instance pool statistics. For more information, see Chapter
11, “Runtime Monitoring,” in the EAServer System Administration Guide.
Running components externally
In EAServer 4.x and 5.0, you can run stateless C++ components in a separate
process with limited access to EAServer features such as connection caching
and transaction control. Running a component externally protects the server
process from application problems such as memory leaks or segmentation
violations.
In EAServer 5.1, stateless components of any type can run externally, with full
access to server-side features such as cached connections. When you mark a
component to run externally, EAServer runs it in a separate server process. You
can identify which external server runs the component, and assign groups of
related components to run in the same external server. EAServer starts the
external server when required, and restarts the server if it stops responding.
For more information on this feature, see “Running components externally” in
Chapter 4, “Defining Components,” in the EAServer Programmer’s Guide.
Note The previous C++ external execution model is still supported for
backward compatibility.