Sun Java Enterprise System 2005Q4 Installation Planning Guide

Distributed Installations

The quality-of-service requirements for production Java ES solutions lead to architectures that place component instances on more than one computer. For example, to achieve reliable messaging services the architecture might require two instances of Messaging Server on two different computers and use load balancing to establish a failover relationship between the two instances.

The Java ES installer, however, operates on only one computer at a time. Therefore, when you install a distributed solution, you must run the installer on every computer used in the solution.

In many cases, you must install a component or components on a computer and then run configuration wizards to perform the basic configuration. You typically complete installation and configuration on one computer before you proceed to install and configure another set of components on another computer. To install and configure distributed component instances, you might perform a sequence of tasks similar to the one illustrated in Figure 3–1.

Figure 3–1 Distributed Installation Procedure Example

On computer 01, install Messaging Server and Calendar Server,
configure Messaging Server, configure Calendar Server. On computer 02, repeat procedure.