Installation guide

CHAPTER 3 Creating Embedded EAServer Installations
Installation Guide 35
You can call these tools and APIs from your installation script or install
program to configure the server and install application components. For
example, you might install your own components by importing them as Jaguar
JAR files with the
jagtool or jagant deploy command, then use the install
command to install the components to the preconfigured Jaguar server. You
might also use the
create command to define connection caches.
EAServer allows you to run
jagtool and jagant in standalone mode. This feature
allows you to configure your installation without starting a server. For details,
see What’s New in EAServer.
There are some
jagtool and jagant commands that you cannot run in standalone
mode; they require a connection to a server process. You can make your
installer launch the preconfigured Jaguar server during installation. The
EAServer System Administration Guide describes the command line syntax for
starting the server.
Most tasks that you can accomplish manually in EAServer Manager can be
automated using
jagtool, jagant, or the Jaguar::Management and
Jaguar::Repository APIs. The automated tools and APIs support an additional
feature that can be useful for configuring embedded EAServer installations:
entity collections.
An entity collection allows you to create a single JAR file that contains a server
configuration, connection cache configurations, components, Web
applications, and all other entities required to run your application. For
information on creating entity collections, see the “Entity collection
properties” reference pages in the EAServer System Administration Guide,
Appendix B, “Repository Properties Reference.”
To create a deployable JAR file containing the entity collection, use the
jagtool
export
command. At install time, you can use the jagtool deploy command to
install the entity collection into the EAServer repository.
You can install additional required files as part of the entity collection, such as
the shell script that runs your server (in the EAServer bin directory), and JAR
files that contain utility Java classes or JDBC drivers (in the EAServer java/lib
directory). To add files to an entity collection, list them in the
com.sybase.jaguar.entitycollection.files property; they are installed when you
deploy the entity collection JAR file.
To simplify listener configuration for embedded installations, use
${JAGUAR_HOST_NAME} as the host name property value for listeners. The
machine name is substituted for this value when you start the server. You can
also use
${JAGUAR_IP_ADDRESS}, which substitutes for the machine’s IP
address.