Your deployment architecture and implementation specifications describe the final state of your solution. The deployment architecture shows you how many component instances are installed, which computer systems the component instances are installed on, and how the component instances interoperate. To reach the state described in the deployment architecture, you must install and configure the component instances in your solution, one computer system at a time, until you have installed and configured the complete solution. Your installation plan must provide installation and configuration procedures for every component instance in your solution, in the correct order.
To develop an installation and configuration plan, you must apply your knowledge of component dependencies and other installation issues to your Java ES deployment architecture and implementation specifications. You must determine the correct sequence for installing and configuring the component instances in your solution and the installation and the correct configuration input values, which will achieve interoperation of the component instances.
This section is a guide to analyzing a deployment architecture and set of specifications and developing an installation plan. In general, you begin as follows:
Open a text file, a blank sheet of paper, or some other medium for recording your plan.
In your deployment architecture, examine the components on each computer system and determine what component dependencies exist.
Identify the component instances that have no dependencies on other components. These are typically instances of Directory Server. You begin your installation plan with instructions for installing these component instances on the specified computer systems. Begin your installation plan by recording these computer systems, and the component instances installed on them.
Determine the correct installation/configuration values in your solution for these component instances on these specific computer systems. Add these configuration values to your installation plan.
Among the remaining components, determine which components have dependencies only on Directory Server. These are typically the computer systems with Access Manager. List these computer systems next in your installation plan.
Continue analyzing your specifications in order of component dependencies. Determine the necessary configuration values, and record these component instances in your plan.
For example, if you use this process to analyze the deployment architecture illustrated in Figure 2–1, you develop an installation plan that looks like Table 3–3.
Table 3–3 shows the first eight steps of the installation plan. In order to make the structure of this plan clear, the individual configuration values are not listed. In this plan, note the following:
The plan lists the computers in the solution according to the order in which the component instances will be installed and configured.
The sequence of installation is determined by applying both solution-level dependencies and the local dependencies. Applying the solution-level dependencies gives a basic sequence of Directory Server, Access Manager, Messaging Server, and then Calendar Server. Applying the local Communications Express dependencies to this sequence adds Web Server instances on computers AM1 and AM2, and also Sun Cluster software and the Sun Cluster agents on computers mscs01 and mscs02.
The plan includes outlines of the installation and configuration procedures for all of the redundancy strategies employed in Java ES solutions. The list of tasks for DS1 and DS2 is an example of a plan for Directory Server multimaster replication. The list of tasks for AM1 and AM2 is an example of a plan for load balanced components. The list of tasks for STR1 and STR2 is an example of a plan for components that run in a Sun Cluster configuration.
The tasks for STR1 and STR2 provide an example of installing and configuring multiple components on one computer. The first time you run the installer, you install the Sun Cluster core component. After you configure the Sun Cluster core component, you run the installer again to install Messaging Server and Calendar Server. These components are configured in order, according to their dependencies. The third time you run the installer on the computer, it installs the Sun Cluster agents for Messaging Server and Calendar Server, which depend on the presence of Messaging Server and Calendar Server.