Red Hat Application Server: JOnAS User Guide | ||
---|---|---|
Prev | Chapter 33. JOnAS and JORAM: Distributed Message Beans | Next |
This is clearly a fairly large number of small configuration files on each server. We have automated the process of deploying the servers and their configuration via Ant. Ant 1.6 includes native support for scp and ssh operations, as Ant tasks. We have used these to build Ant tasks that can literally:
Install JOnAS on all our servers.
Create JONAS_BASE directories on each server,
Copy the server-specific configuration over to each server,
Build the JoramDistributionService and deploy it to each server,
launch JORAM and JOnAS on each server in the proper order,
Build a customized version of our application for each type of server (that is, a "frontend" version containing no message beans, and a "backend" version containing only message beans),
Deploy the appropriate application version to each of the three servers,
Test the entire system using our system integration test suite.
In fact, we can do all of the above with a single Ant command.
Doing this with Ant is actually quite straightforward. Without support for automating this deployment process, we would be quite concerned with the complexity of the configuration. With automation, it is easy to place the whole configuration process under source code control, and it is easy to make controlled changes to the configuration of multiple machines.