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:
Communications Express
Web container
Messaging Server (Messenger Express)
Calendar Server
Directory Server
Access Manager
Figure 26–2 shows the Communications Express on remote host architecture.
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 |