Analyzing the Deployment Architecture

A typical deployment architecture is illustrated in Figure 2–1. This deployment architecture defines a Java ES solution that provides portal and communications services. This particular architecture uses Access Manager to provide single sign-on to the communications services, and it uses both Portal Server and Communications Express to deliver the messaging and calendar services to end users. This architecture includes components from the Communications Suite.

Figure 2–1 Example Deployment Architecture

Figure 2–1 contains much information about the solution, including the following:

• The number of computers used in the solution

• The number of CPUs and the amount of RAM required for each computer

• The component instances installed on each computer

• The number of instances of each component used in the solution

• The redundancy strategies used in the solution (load balancing, Directory Server multimaster replication, and Sun Cluster technology) to meet quality-of-service requirements

• The distributed installation of the Messaging Server subcomponents, another technique used to meet quality-of-service requirements

These characteristics of the example deployment architecture affect how the solution is installed and configured. You begin planning for your installation by analyzing your deployment architecture in the same way, observing how many computer systems are used, how many component instances are installed on each computer system, which redundancy strategies are used, and so on.