The Deployment Architecture

The second step in developing an architecture for a solution is preparing a deployment architecture. The deployment architecture integrates the logical architecture and the quality of service requirements. When you develop a deployment architecture you answer such questions as the following:

• Which redundancy strategies are you using to meet your availability and reliability requirements? (Some of the redundancy strategies available to you are installing and configuring multiple instance of a component and load balancing the instances to achieve availability and reliability, installing and configuring multiple instances of a component and using Sun clustering technology to achieve availability and reliability, and using multiple instances of Directory Server that are synchronized through the multi-mastering and replication features to achieve availability and reliability.)

• How many instances of each component must be installed and configured in order to implement the redundancy strategies you use in your solution?

• How are your component instances combined on computer hardware systems? For example, in a medium-sized solution, you could install and configure instances of both Messaging Server and Calendar Server on two computer systems. You utilize Sun Cluster technology to cluster the two computer systems, and this architecture achieves availability and reliability for your messaging and calendar services.

• How many CPUs are needed on each computer system to achieve the performance specified in you quality of service requirements?

The answers to these questions lead to a deployment architecture for your solution. A deployment architecture is typically represented graphically, with a set of boxes that represent the computer systems in the solution. Each box is labeled with the components that are installed on that computer system. The deployment architecture for the evaluation solution is illustrated in Figure 2–2.

Figure 2–2 Evaluation Solution Deployment Architecture

Figure 2–2 shows that the minimal quality of service requirements for the evaluation use cases are easily satisfied by installing all of the components used in the evaluation solution on one system. The system is represented by the box labeled evaluation_host. The rest of this document describes how to install, configure, and use the evaluation solution on one system.

The deployment architecture for a production solution would represent a number of computer systems, with different combinations of components installed on each system. For an example of a large scale deployment architecture suitable for a production solution, see Java ES solution, see Java Enterprise System Deployment Planning Guide (http://download.oracle.com/817-5759)