|
| |
| Sun Java System Communications Services 6 2005Q1 Deployment Planning Guide | |
Chapter 28
Communications Services Deployment ExamplesThis chapter contains Communications Services deployment examples. Depending on the features you want to implement in your deployment, you will need to install different sets of hosts and other networking infrastructure.
This chapter contains the following sections:
Note
When making architectural decisions, ranging from single host deployment, to multi-tiered deployments, you should always plan for service definition across multiple tiers. Thus, use logical service names to install, even on a single host deployment. Logical service names position deployments for easier expansion. See Using Logical Service Names for more information.
Communications Services Single-tiered Logical Deployment Example for One HostAs its name implies, this example installs and configures components onto a single server. Consult with your Sun Client Services representative to determine the server type and configuration that best suits your needs.
In general, the single-tiered one host architecture is best suited for enterprises that are:
The trade-offs associated with a single-host configuration include:
Figure 28-1 shows a single-host deployment example. The following Communications Services components are installed on the same host:
In this example, the directory service resides on a different host than Communications Services. Directory Server and Access Manager are a complex deployment on their own. This figure represents those components by a “cloud.”
Figure 28-1 Communications Services Single-tiered Deployment Example for One Host
The following table explains the protocols and port numbers used by this deployment.
To position this deployment for future growth, you would use logical service names to install. Logical service names position deployments for easier expansion. See Using Logical Service Names for more information. You would consider expanding to a two-tiered architecture when issues arise with capacity, performance, multiple geographic sites, and availability.
Communications Services Two-tiered Logical Deployment Example for Multiple HostsFigure 28-2 shows a two-tiered logical deployment example for Messaging Server and Calendar Server. Tier 0 consists of load balancers. Tier 1 consists of Calendar Server and Messaging Server front ends. The Calendar Server and Messaging Server back-end stores form Tier 2.
Directory Server and Access Manager are a complex deployment on their own. This figure represents those components by a “cloud.”
Figure 28-2 Communications Services Two-tiered Deployment Example
In the preceding example, load balancers form Tier 0, and direct user access to the front-end services.
The front-end services consist of four machines. Two machines are installed with Calendar Server front-end components. These Calendar Server front-end machines consist of one or two CPU servers and their own internal disk storage. Two other machines are configured as Messaging Server proxies and MTAs, and share an external disk array. These Messaging Server machines consist of four CPU servers.
The back end also consists of four machines. Two machines serve as mail stores and run the Messaging Server processes. Two other machines serve as the calendar stores and run Calendar Server process. The store machines are attached to a Storage Area Network (SAN). These back-end machines can be deployed in a variety of ways, based upon your CPU needs. Once you determine the total number of CPUs, you can opt for a vertical or horizontal configuration. For example, if your architecture called for a total of twelve CPUs, you could use three four-way servers, two six-way servers, or even one 12-way server.
Another machine serves as an SMTP relay for both Calendar Server notifications and Messaging Server emails.
The following table explains the protocols and port numbers used by this deployment.
