Post-installation configuration

EAServer provides several options for scripted automated configuration of server properties and application components:

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 install program to configure the server and install application components. For example, you might install your own components by importing them as JAR files with the jagtool or jagant deploy command, then use the install command to install the components to the preconfigured Jaguar server.

There are jagtool and jagant commands that you cannot run in standalone mode and require a connection to a server process. You can make your installer launch the preconfigured Jaguar server during installation. The EAServer Automated Configuration Guide describes the command line syntax for starting the server.

NoteIf you have installed EAServer to run as a Windows service, you must restart the system after installation. For this reason, you may want to avoid enabling the -P WindowsService.active silent installer option, which installs the server as a service. Instead, you can run the start-server command to run the server as a service after you have installed and configured EAServer.

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, connection cache 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.