Installation guide

Systems management enhancements
80 EAServer
Globally available connection caches
Connection caches are now available to all servers run from the same
EAServer installation. You no longer need to install connection caches into a
server to allow access from components on that server.
Java class file consolidation
EAServer’s runtime Java classes have been consolidated into these JAR files:
• $JAGUAR/java/lib/easserver.jar, required in the CLASSPATH for server-
side Java code.
• $JAGUAR/java/lib/easclient.jar, required in the CLASSPATH for server-
side and client-side Java code.
• $JAGUAR/java/lib/easj2ee.jar, required in the CLASSPATH for server-
side and client-side Java code.
Automated installation and configuration tools
EAServer 4.0 includes tools to automate deployment, configuration, and
installation. These features are useful if you are embedding EAServer in your
own software installation.
For automated deployment and configuration, use these tools:
•
jagtool is a command-line interface that allows you to automate some of
EAServer’s development and deployment tasks.
•
jagant lets you run jagtool commands from Jakarta Ant build files.
For more information, see Chapter 12, “Using jagtool and jagant,” in the
EAServer System Administration Guide.
EAServer 4.0 also includes a script-driven installation utility that you can use
to automate EAServer software installation. For more information, see the the
EAServer Installation Guide.