Chapter 7 Communications Services Deployment Example

This chapter contains a Communications Services enterprise deployment example. Depending on the features you want to implement in your deployment, you will need to install different sets of hosts and other networking infrastructure.

Two Tier Deployment Example

Figure 7-1 shows a two tier deployment 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 Identity Server are a complex deployment on their own. This figure represents those components by a “cloud.”

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.

Table 7-1 Protocols And Ports Used by Two Tier Deployment Example
Protocol	Port	Used By
HTTP	80	Clients to communicate with the Messaging Server MEM and Webmail (httpd) components
SMTP	25	Clients to communicate with the Messaging Server MTA component, MTA components on the front end and back end, and Calendar Server (csendp) components for email notifications
IMAP	143	Clients to communicate with the Messaging Server MMP and imapd components
LMTP	225	MTA routes email directly from the front end to the Message Store on the back end, bypassing the back-end MTA
LDAP	389	Front ends and back ends to communicate with LDAP directory
HTTP	8081	Clients to communicate with Calendar Front End (cshttpd)
DWP	9779	Calendar front end (cshttpd) to communicate with Calendar back end (csdwpd)

Previous Contents Index Next
Sun Java System Communications Services 6 2004Q2 Enterprise Deployment Planning Guide