Sun Java System Communications Services 6 2005Q4 Deployment Planning Guide

Chapter 26 Developing a Communications Express Architecture

This chapter contains Communications Express basic deployment architectures. 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:

Basic Communications Express Architecture

This basic Communications Express architecture provides Calendar, Address Book, and Mail modules in a web container on a single host. Messenger Express is the standalone web interface mail application that uses the HTTP service of the Messaging Server. Messenger Express is deployed on the same system as the Calendar and Address Book modules.

To provide this basic functionality, you need to install the following components:

In this example:

Figure 26–1 shows the basic Communications Express architecture.

Figure 26–1 Basic Communications Express Architecture

This diagram shows a basic Communications Express deployment
example.

The following table explains the protocols and port numbers used by this architecture.

Table 26–1 Protocols And Ports Used by Basic Communications Express Deployment Architecture

Protocol  

Port  

Used By  

SMTP 

25 

Messaging Server MTA component to communicate with other systems, and Calendar Server (csenpd) components for email notifications

HTTP 

80 

Internet users to communicate with Communications Express front-end, and Communications Express to communicate with Messaging Server 

HTTP 

81 

Calendar Express on Communications Express to communicate with Calendar Server 

MSHTTP 

82 

Internet users to communicate with Messenger Express 

LDAP 

389 

Messaging Server and Calendar Server to communicate with LDAP directory 

Communications Express on Remote Host Architecture

Figure 26–2 shows a Communications Express architecture for both intranet and Internet users. The intranet users log on to the Communications Express back-end host. The Internet users log on to the Communications Express front-end host in the DMZ, which then communicates with the back-end host. Single sign-on is enabled on the back-end host.

You install the front-end host with the following components:

You install the back-end with the following components:

Figure 26–2 shows the Communications Express on remote host architecture.

Figure 26–2 Communications Express on Remote Host Architecture

This diagram shows an example deployment of Communications Express
on a remote host.

The following table explains the protocols and port numbers used by this architecture.

Table 26–2 Protocols And Ports Used by Communications Express Remote Host Deployment Example

Protocol  

Port  

Used By  

HTTP 

80 

Internet users to communicate with the Communications Express front-end host in the DMZ 

HTTP 

81 

Messaging Express Multiplexor (MEM) on the Communications Express front-end host in the DMZ to communicate with Messenger Express on the back-end host behind the DMZ 

HTTP 

82 

Communications Express on the back-end host to communicate with Calendar Server, also on the back-end host 

LDAP 

389 

Messaging Server and Calendar Server to communicate with LDAP directory 

HTTP 

8081 

Communications Express on the front-end host to communicate with Calendar Server on the back-end host