EAServer provides several options for scripted automated configuration of server properties and application components:
jagtool is a command line configuration program that you can call from installation scripts or batch files.
jagant allows you to configure EAServer from Jakarta Ant scripts.
For information on jagtool and jagant, see “Using jagtool and jagant” in the EAServer Automated Configuration Guide.
You can call these tools from your installation script or installer program to configure the server and install application components. For example, you might install your own components by importing them as EAServer JAR files with the jagtool or jagant deploy command, then use the install command to install the components to the preconfigured server. You can use the create command to define data sources.
Most tasks that you can accomplish manually from the Management Console can be automated using jagtool or jagant. In addition, the EAServer Automated Configuration Guide explains how to use Ant-based configuration scripts for configuring embedded EAServer installations: entity collections.
An entity collection allows you to create a single JAR file that contains a server configuration, data source configurations, components, Web applications, and all other entities required to run your application.
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 will be installed when you deploy the entity collection JAR file.
