h1. Communications Suite 6 Update 2 Installation Scenario - Webmail Server
h2. Assumptions
This scenario shows how to install the Messaging Server Webmail Server ({{mshttpd}}) on a separate host. The Webmail Server acts as a front end that handles the HTTP protocol retrieval of messages from the message store. This component is used by Convergence and Communication Express to provide web-based access to end users.
This scenario is based on the _Install Webmail Server_ leaf in the [Communications Suite 6 Update 2 Installation Flowchart]. The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This Webmail Server is one functional component of your multi-host deployment.
* You are installing the Webmail Server on a separate host; you are not bundling the Webmail Server with other Communication Suite products on the same host.
* If you are distributing multiple Webmail Servers across several hosts, you can follow these instructions for each host on which you install the Webmail Server.
* You are installing only the Webmail Server front end; you are not installing message store or SMTP functions.
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for the Webmail Server
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the Webmail Server:
* Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see [Default Port Numbers|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Install and configure the Webmail Server:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the 32-bit or 64-bit version by selecting one of these components:\\
\\
Messaging Server 7 Update 2. (The Comms Installer does not explicitly label the 32-bit version as "32-bit.")\\
\\
Messaging Server (64-bit) 7 Update 2.\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the Webmail Server: [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server].\\
\\
# Run the Messaging Server initial configuration program:\\
\\
For 32-bit: {{# _INSTALLROOT_/messaging/bin/configure}}\\
\\
For 64-bit: {{# _INSTALLROOT_/messaging64/bin/configure}}\\
\\
For detailed instructions, see [Messaging Server 7 Update 2: Initial Configuration|Messaging Server 7 Update 2 Initial Configuration].\\
\\
When the Messaging Server {{configure}} program lists the components to configure, select\\
\\
Webmail Server\\
\\
Make sure that the other components are not selected.\\
\\
# Set the following {{configutil}} parameters. The Webmail Server uses these {{configutil}} parameters to log in to the back-end IMAP servers:
|| {{configutil}} Parameter|| Description||
|{{local.service.proxy.admin}} |Default backend store administrator login name. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: string
Default: {{admin}}|
|{{local.service.proxy.adminpass}} | Default store administrator password. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: string
Default: <_admin.password_>|
|{{local.service.imapport}} | Default IMAP port number for backend store servers. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: integer
Default: 143|
Note that the Webmail Server can communicate with multiple back-end IMAP servers. If the IMAP servers use different values for these parameters are different, you must set individual {{configutil}} parameters for each host, as follows:
|{{local.service.proxy.admin.}}_hostname_|
|{{local.service.proxy.adminpass.}}_hostname_|
|{{local.service.imapport.}}_hostname_|
where _hostname_ is the name of the host on which each back-end IMAP server is running.
h6. Examples
For one back-end IMAP server:
{noformat}
configutil -o local.service.proxy.admin -v myadmin
configutil -o local.service.proxy.adminpass -v <password>
configutil -o local.service.proxy.imapport -v 143
{noformat}
For multiple back-end IMAP servers:
{noformat}
configutil -o local.service.proxy.admin.host1.siroe.com -v admin1
configutil -o local.service.proxy.adminpass.host1.siroe.com -v <password>
configutil -o local.service.proxy.imapport.host1.siroe.com -v 143
configutil -o local.service.proxy.admin.host2.siroe.com -v admin2
configutil -o local.service.proxy.adminpass.host2.siroe.com -v <password>
configutil -o local.service.proxy.imapport.host2.siroe.com -v 143
{noformat}
h2. Assumptions
This scenario shows how to install the Messaging Server Webmail Server ({{mshttpd}}) on a separate host. The Webmail Server acts as a front end that handles the HTTP protocol retrieval of messages from the message store. This component is used by Convergence and Communication Express to provide web-based access to end users.
This scenario is based on the _Install Webmail Server_ leaf in the [Communications Suite 6 Update 2 Installation Flowchart]. The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This Webmail Server is one functional component of your multi-host deployment.
* You are installing the Webmail Server on a separate host; you are not bundling the Webmail Server with other Communication Suite products on the same host.
* If you are distributing multiple Webmail Servers across several hosts, you can follow these instructions for each host on which you install the Webmail Server.
* You are installing only the Webmail Server front end; you are not installing message store or SMTP functions.
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for the Webmail Server
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the Webmail Server:
* Make sure you do not configure conflicting port numbers on a machine when various components are running on a single machine. For a list of port numbers used by Messaging Server, see [Default Port Numbers|Communications Suite 6 Update 2 Component Products Release Notes#GDWUB].
h4. Install and configure the Webmail Server:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the 32-bit or 64-bit version by selecting one of these components:\\
\\
Messaging Server 7 Update 2. (The Comms Installer does not explicitly label the 32-bit version as "32-bit.")\\
\\
Messaging Server (64-bit) 7 Update 2.\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the Webmail Server: [Messaging Server 7 Update 2 - Configuration Worksheet|Configuration Worksheets - Messaging Server].\\
\\
# Run the Messaging Server initial configuration program:\\
\\
For 32-bit: {{# _INSTALLROOT_/messaging/bin/configure}}\\
\\
For 64-bit: {{# _INSTALLROOT_/messaging64/bin/configure}}\\
\\
For detailed instructions, see [Messaging Server 7 Update 2: Initial Configuration|Messaging Server 7 Update 2 Initial Configuration].\\
\\
When the Messaging Server {{configure}} program lists the components to configure, select\\
\\
Webmail Server\\
\\
Make sure that the other components are not selected.\\
\\
# Set the following {{configutil}} parameters. The Webmail Server uses these {{configutil}} parameters to log in to the back-end IMAP servers:
|| {{configutil}} Parameter|| Description||
|{{local.service.proxy.admin}} |Default backend store administrator login name. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: string
Default: {{admin}}|
|{{local.service.proxy.adminpass}} | Default store administrator password. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: string
Default: <_admin.password_>|
|{{local.service.imapport}} | Default IMAP port number for backend store servers. (Restart of HTTP service required; Restart of IMAP service required).
Syntax: integer
Default: 143|
Note that the Webmail Server can communicate with multiple back-end IMAP servers. If the IMAP servers use different values for these parameters are different, you must set individual {{configutil}} parameters for each host, as follows:
|{{local.service.proxy.admin.}}_hostname_|
|{{local.service.proxy.adminpass.}}_hostname_|
|{{local.service.imapport.}}_hostname_|
where _hostname_ is the name of the host on which each back-end IMAP server is running.
h6. Examples
For one back-end IMAP server:
{noformat}
configutil -o local.service.proxy.admin -v myadmin
configutil -o local.service.proxy.adminpass -v <password>
configutil -o local.service.proxy.imapport -v 143
{noformat}
For multiple back-end IMAP servers:
{noformat}
configutil -o local.service.proxy.admin.host1.siroe.com -v admin1
configutil -o local.service.proxy.adminpass.host1.siroe.com -v <password>
configutil -o local.service.proxy.imapport.host1.siroe.com -v 143
configutil -o local.service.proxy.admin.host2.siroe.com -v admin2
configutil -o local.service.proxy.adminpass.host2.siroe.com -v <password>
configutil -o local.service.proxy.imapport.host2.siroe.com -v 143
{noformat}