h1. Communications Suite 6 Update 2 Installation Scenario - Install Calendar Server Back End
h2. Assumptions
This scenario shows how to install an instance of Calendar Server as a back end on a separate host. It is based on the _Install Calendar Server Back End_ leaf in the [Communications Suite 6 Update 2 Installation Flowchart]. A Calendar Server back end stores the calendar databases.
The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This Calendar Server back end is one functional component of your multi-host deployment.
* You are installing Calendar Server on a separate host or Solaris zone; you are not bundling Calendar Server with Communication Suite products on the same host.
* If you are distributing multiple instances of the Calendar Server back end across several hosts or zones, you can follow these instructions for each host on which you install the Calendar Server back end.
{note:title=Deploying a Front End and Back End on One Host} What if you intend to deploy a single-server instance of Calendar Server (that is, a Calendar Server deployment with both a front end and back end running on this host)?
To deploy a Calendar Server front end _and_ back end together: Follow the procedure shown below. However, when you run the Calendar Server configuration program, when the *Set Up a Front End-Back End Deployment* screen is displayed, do not select the check box on this screen.
{note}
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for Calendar Server
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the Calendar Server back end:
Be sure you have planned for the following:
* Calendar Server Administrators
* Hosted Domains
For information about these topics, see [Calendar Server Pre-Installation Planning|Calendar Server Pre-Installation Planning].
h4. Install and configure the Calendar Server back end:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the following component:\\
\\
Calendar Server 6.3\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the Calendar Server back end: [Calendar Server 6.3 - Configuration Worksheet|Configuration Worksheets - Calendar Server]\\
\\
# Run the Calendar Server initial configuration program:\\
\\
{{# _INSTALLROOT_/calendar/bin/csconfigurator.sh}}\\
\\
For detailed instructions, see [Calendar Server 6.3: Initial Configuration|Calendar Server 6.3 Initial Configuration].\\
\\
# When the Calendar Server {{csconfigurator.sh}} program displays the *Set Up a Front End-Back End Deployment* screen, select the check box.\\
\\
A Front End-Back End Deployment screen appears.\\
\\
# To configure this instance of Calendar Server as a back-end server, specify the *Service Port*. (Do not check the *Add a Host* box; that box is for configuring a front-end server.) \\
\\
# The *Service Port* box is pre-filled with the port named in the {{ics.conf}} parameters {{service.dwp.server.hostname.port}} and {{service.dwp.port}}. \\
\\
If you want to change the port number, enter the new port number in the *Service Port* box.\\
\\
For detailed instructions on configuring the *Set Up a Front End-Back End Deployment* screen in the {{csconfigurator.sh}} program, see [Configuring a Front-End or Back-End Calendar Server|CSFrontEndDeployment].\\
\\
h2. Assumptions
This scenario shows how to install an instance of Calendar Server as a back end on a separate host. It is based on the _Install Calendar Server Back End_ leaf in the [Communications Suite 6 Update 2 Installation Flowchart]. A Calendar Server back end stores the calendar databases.
The scenario makes these assumptions:
* You are deploying Communications Suite on multiple hosts or Solaris zones.
* This Calendar Server back end is one functional component of your multi-host deployment.
* You are installing Calendar Server on a separate host or Solaris zone; you are not bundling Calendar Server with Communication Suite products on the same host.
* If you are distributing multiple instances of the Calendar Server back end across several hosts or zones, you can follow these instructions for each host on which you install the Calendar Server back end.
{note:title=Deploying a Front End and Back End on One Host} What if you intend to deploy a single-server instance of Calendar Server (that is, a Calendar Server deployment with both a front end and back end running on this host)?
To deploy a Calendar Server front end _and_ back end together: Follow the procedure shown below. However, when you run the Calendar Server configuration program, when the *Set Up a Front End-Back End Deployment* screen is displayed, do not select the check box on this screen.
{note}
h2. Which Software Components and Downloads Do You Need?
* Communications Suite: for Calendar Server
Download sites: [Get the Software].
h2. Which Task Sequence Do You Follow?
h4. Before you install the Calendar Server back end:
Be sure you have planned for the following:
* Calendar Server Administrators
* Hosted Domains
For information about these topics, see [Calendar Server Pre-Installation Planning|Calendar Server Pre-Installation Planning].
h4. Install and configure the Calendar Server back end:
# [Run the Communications Suite installer|Communications Suite 6 Update 2 Installation Guide#installcommssuite].\\
\\
When the Comms Installer lists the components to install, choose the following component:\\
\\
Calendar Server 6.3\\
\\
Make sure that the other components are not selected.\\
\\
# Use the following worksheet to gather configuration information for the Calendar Server back end: [Calendar Server 6.3 - Configuration Worksheet|Configuration Worksheets - Calendar Server]\\
\\
# Run the Calendar Server initial configuration program:\\
\\
{{# _INSTALLROOT_/calendar/bin/csconfigurator.sh}}\\
\\
For detailed instructions, see [Calendar Server 6.3: Initial Configuration|Calendar Server 6.3 Initial Configuration].\\
\\
# When the Calendar Server {{csconfigurator.sh}} program displays the *Set Up a Front End-Back End Deployment* screen, select the check box.\\
\\
A Front End-Back End Deployment screen appears.\\
\\
# To configure this instance of Calendar Server as a back-end server, specify the *Service Port*. (Do not check the *Add a Host* box; that box is for configuring a front-end server.) \\
\\
# The *Service Port* box is pre-filled with the port named in the {{ics.conf}} parameters {{service.dwp.server.hostname.port}} and {{service.dwp.port}}. \\
\\
If you want to change the port number, enter the new port number in the *Service Port* box.\\
\\
For detailed instructions on configuring the *Set Up a Front End-Back End Deployment* screen in the {{csconfigurator.sh}} program, see [Configuring a Front-End or Back-End Calendar Server|CSFrontEndDeployment].\\
\\