Sun Java Communications Suite 6 Update 2 on a Single Host (Linux)

h1. Deployment Example: Sun Java Communications Suite 6 Update 2 on a Single Host (Linux)

This deployment example describes how to install Sun Java Communications Suite 6 Update 2 software on a single Red Hat Enterprise Linux 4 computer for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.
{info:title=Note}
Installing the messaging, calendar, instant messaging, and address book servers on the same system is not the optimal configuration, nor does it provide the best performance. This example deployment is not intended for production purposes. Use this configuration for evaluation and for training purposes only. Performance is improved when services are deployed across multiple systems.
{info}
{toc:minLevel=2|maxLevel=2}
h2. Comparison to Communications Suite 6 Update 1 guide

Each new release or update of Communications Suite provides additional functionality which in-turn is reflected by modifications to the Single Host install guide to make best use of this functionality. The following is a brief overview of the changes made to the guide.

* Delegated Administrator 7.0 Direct LDAP mode used.
** Removes dependency on Access Manager 7.1.
* Instant Messaging Server 8.1 LDAP storage for policy and authentication.
** Removes dependency on Access Manager 7.1.
* Access Manager 7.1 installation and configuration steps removed.
** Removes requirement to download and install JES5 update 1.
** Removes dependency on JDK5.
* JDK6 used as primary JVM release
** Improves performance of products using the JVM including Sun Convergence, Instant Messaging Server, Communications Express and Application Server.

New features for Communication Suite 6 Update 2 can also be found in the [Communications Suite 6 Update 2 Release Notes]

The following is a brief overview of the additions to the guide.

* [Hosted Domain configuration and creation|#hostedconfig]
* [Single host installation tuning tips|#tuningtips]

h2. About This Deployment Example

This section provides an overview of this deployment scenario, the hardware and software used, and the procedures you follow to install, configure, and use this deployment.

This section contains the following topics:
{toc-zone:minLevel=3|maxLevel=3|location=top|type=list}

h3. Installation Overview

This scenario results in a functioning deployment suited for the evaluation and testing of Sun Java Communications Suite 6 Update 2 on Red Hat Enterprise Linux 4. These instructions are not intended to act as a replacement for the individual component documentation, but to merely guide the evaluator through an initial installation.

h4. What Components Are Installed?

This example guides you through installing the following Communications Suite and pre-requisite components:

* Sun Java System Messaging Server 7 Update 2
* Sun Java System Calendar Server 6.3 + Patches
* Sun Java System Instant Messaging 8 Update 1
* Sun Java System Directory Server 6.3
* Sun Java System Application Server 9.1 Update 2
* Sun Java System Delegated Administrator 7.0
* Sun Java System Communications Express 6.3 + Patches
* Sun Convergence 1 Update 2
* All Shared Components

The example installation in this document uses the following data that you change according to your installation and test machine:

* Domain name: {{comms.beta.com}}
* Host name: {{demo}} (running Red Hat Linux 4)
* Fully qualified (external) host name: {{demo.comms.beta.com}}
* Password: {{adminpass}} used for all passwords except the {{amldapuser}} password

This example installs all of the software on a single system. Adjust host names accordingly if you install the components on multiple systems.

h4.Recommended Ports

For convenience, this example uses a set of recommended ports. If you use different ports, be sure to make the changes consistently throughout the installation. For example, this document uses port 4848 for the Application Server admin port. If you decide to use port 3333 instead, be sure to change it everywhere 4848 occurs in the deployment example. See [Table 3|#Table3] for more information.

h3.Implementation Specifications for This Example

This section describes implementation specifications for this example.

*Table 1 Evaluation Host Hardware and Software Requirements*
||Component||Platform Requirement||
|CPU|x86|
|RAM|2 Gbytes or more|
|Disk Space|2.1 Gbytes or more free disk space for installed software. 1.5 Gbytes additional disk space may be needed for temporary storage of Communications Suite zip files.|
|Software|Red Hat Linux EL 4.|
|Users|Provisioned with test users.|

*Table 2 Client Software Requirements*
||Component||Platform Requirement||
|Browser|Firefox 2.0.0.X or 3.0.X, Internet Explorer 7.x|

{anchor:Table3}
*Table 3 Server Configuration Information*
||Component||Install Notes||Install Location||Database Location||Port Name||Port Number||
|Application Server 9.1|Installed separately. Required for Convergence, Delegated Administrator and Communications Express|/opt/sun/appserver|/opt/sun/appserver/domains/domain1|HTTP Port|80|
| | | | |Admin Port|4848|
| | | | |HTTPS Port|443|
|Directory Server 6.3|Installed separately.|/opt/sun/directory|/var/opt/sun/dsins1|Directory Server Port|389|
| | | | |LDAP Port|389|
| | | | |SSL Port|636|
|Messaging Server 7 Update 2|Installed by using Communications Installer. Additional configuration required.|/opt/sun/comms/messaging|/var/opt/sun/comms/messaging|Webmail Port (HTTP)|8990|
| | | | |SMTP Port|25|
| | | | |POP Port|110|
| | | | |IMAP Port|143|
|Calendar Server 6.3|Installed using Communications Installer. Additional configuration required.|/opt/sun/comms/calendar|/var/opt/sun/comms/calendar|Calendar Server Port|3080|
|Instant Messaging 8|Installed using Communications Installer. Additional configuration required.|/opt/sun/comms/im|/var/opt/SUNWiim|XMPP Port|5222|
| | | | |Multiplexed XMPP Port|45222|
| | | | |Server-to-Server Port|5269|

h3.Installation Time Estimates

The following table provides time estimates for installing this example.

*Table 4 Installation Time Estimates*
||Activity||Estimate||
|Install Red Hat Linux OS|2 hours|
|Install Communications Suite, Application Server and Directory Server|1 hour|
|Configure software|3 hours|
|Total|6 hours (average)|

As part of the configuration, you will use Delegated Administrator to add users for Messaging Server, Calendar Server and Instant Messaging Server.

h3.Installation Notes and Recommendations

# Use {{gzip -d}} or {{gunzip}} to decompress the {{*.gz}} files.
# Use unzip to decompress the {{*.zip}} files.

*Expected User Input*

During installation, your are prompted for various input. User input is indicated by text of the form *<user-input>*. The following table helps you plan for the types of information you must provide during installation.

*Table 5 Information Input During Installation*
||User Input||User Input Action||
|*<enter>*|Just hit enter, but verify that the default value shown makes sense.|
|*<sample-password>*|Any password, minimum of 8 characters in length, suitable for evaluation purposes. These instructions assume that anywhere *<sample-password>* is specified, you will enter the same value each time.|
|*<amldapuser-password>*|Same criteria as *<sample-password>*, but must be different from *<sample-password>*.|
|*<fully-qualified-hostname>*|For example, assuming that the host name is {{abc}}, and the domain name is {{demo.xyz.com}}, then this value would be {{abc.demo.xyz.com}}.|
|*<full-cookie-domainname>*|For example, assuming that the full domain name is {{demo.xyz.com}}, then this value would be {{.demo.xyz.com}} (note the inclusion of the leading "{{.}}").|

h3.Summary of Installation and Configuration

Installing and configuring this example involves the following high-level steps:

# Preparing the system for Sun Java Communications Suite
# Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, Convergence, and Communications Express
# Installing and configuring Directory Server 6.3
# Installing and configuring Application Server 9.1 Update 2
# Deploying and enabling the Directory Server Control Center
# Configuring Delegated Administrator and Communications CLI
# Configuring Messaging Server
# Configuring Calendar Server
# Configuring Communications Express
# Configuring Instant Messaging Server
# Configuring Convergence

These installation steps result in a suitable deployment to evaluate and test Communications Suite 6 Update 2. These instructions are not intended to act as a replacement for the individual component documentation, but to merely guide the evaluator through an initial installation.

{toc-zone}
h2. Installing the Example

This section describes how to install and configure components on a single machine for evaluation purposes. Some components are configured after installation, using component configuration tools.
{info:title=Note}
Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as the *root* user.
{info}
This section contains the following topics:
{toc-zone:minLevel=3|maxLevel=3|location=top|type=list}

h3.Checking Installation Requirements

Before you install components, use the steps in this section to make sure the computer on which you are installing is ready.

*To Check System Requirements*

The computer should meet the following requirements:

* These instructions assume all actions are performed by the {{root}} user unless mentioned otherwise.
* The computer must have 1.5 GB free disk space for the zip files and zip image.

*To Check DNS*

Verify that DNS is running and configured properly:

# Make sure that the {{/etc/resolv.conf}} file has name server entries with the IP addresses of valid name servers. For example:
\\
{noformat:nopanel=true}
domain comms.beta.com
nameserver 192.168.100.22
nameserver 192.168.100.23
nameserver 192.168.100.24
nameserver 192.168.100.25
{noformat}
# Make sure that the {{/etc/hosts}} file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
{noformat:nopanel=true}
10.1.82.52 demo.comms.beta.com wireless demo
{noformat}
# Make sure that the {{/etc/nsswitch.conf}} file is configured to use files first to resolve host names. The hosts line in the {{nsswitch.conf}} file should list files first in its entry:
{noformat:nopanel=true}
hosts: files dns nis [NOTFOUND=return]
# OR (if NIS is not used)
hosts: files dns
{noformat}

*To Check for Sufficient Number of File-Descriptors*

The default installation of Red Hat Enterprise Linux 4.6 uses 1,024 file descriptors, which is insufficient for the correct operation of Communications Suite 6. A Communications Suite 6 system needs the maximum file descriptors set to 16,384.

# In a terminal window, as {{root}} user, verify the number of file descriptors.
{{ulimit -n}}
# If this number is less than 16,384 you will need to increase the value.
# To change the number of file descriptors, add the following to the {{/etc/sysctl.conf}} file. Or, if the parameter is already set, increase the value to 16384.
{{fs.file-max = 16384}}
# Add the following two lines to the {{/etc/security/limits.conf}} file.
{noformat}
# Increase max file descriptors
* - nofile 16384
{noformat}
# Either reboot the system for the value to take effect or run the following command:
{{sysctl -p /etc/sysctl.conf}}.
# In a new terminal window, as {{root}} verify the change.
{{ulimit -n}}

h3. Getting the Necessary Software

*To Get the Software*
# [Get the Communications Suite, Application Server and Directory Server|CommSuite6U2:Get the Software].

h2. Installing Communications Suite Components

Deploying Communications Suite components is a two-step process. You first install the software and the shared components then you configure the individual server components. This section describes how to install the Communications Suite software on your host.

# Create the /tmp/JCS6U2 directory, move the Communication Suite 6 update 2 software (SunJava_CommsInstaller_Suite6u2_linux-x86.zip) to this directory and extract the files.
{noformat}
cd /tmp/JCS6U2
unzip SunJava_CommsInstaller_Suite6u2_linux-x86.zip
{noformat}
# Run the Communications Suite installer.
{noformat}
./commpkg install
{noformat}
# Press Return to continue when prompted.
# Review the license and type {{{*}c{*}}} to continue when prompted.
You can also type {{{*}s{*}}} to skip the license display.
# Accept the License Agreement by typing {{{*}yes{*}}} when prompted.
# Accept the default Install location: {{/opt/sun/comms}}
# Select the following components for installation.
{noformat}
1. Messaging Server 7 Update 2 (7.2-7.02)
2. Comms DSsetup 6.4 (6.4-4.04)
3. Comms Delegated Administrator 7 (7.0-0.00)
4. Calendar Server 6.3 (6.3-15.01)
5. Instant Messaging 8 Update 1 (8.1-01.03)
6. Communications Express 6.3 (6.3-13.01)
7. Convergence 1 Update 2 (1.0-7.01)
{noformat}
# The installation script prompts for a series of options.
You might not be prompted for these options, depending on your operating system configuration and previously installed software.
# The following table shows how to respond to the configuration options:
*Table 9 Values for Unicode, NSS/NSPR/JSS, Service Tags and Java Development Kit (JDK) Options*
|| Option || \[Default Value\] || Enter: ||
| Upgrade Unicode | \[n\] | *y* |
| Upgrade NSS/NSPR/JSS | \[n\] | *y* |
| Upgrade Service Tags | \[n\] | *y* |
| Upgrade Java Development Kit | \[n\] | *y* |
# Press Return when prompted to continue.
The installation proceeds.
# Press Return when prompted to continue.
# Continue with the next section.

h3. Installing and Configuring Directory Server 6.3

*To Install the Zip Version of Directory Server 6.3*
# Move the downloaded Directory Server 6.3.1 zip file {{DSEE.6.3.Linux-X86-full.tar.gz}} to a temporary location, such as {{/tmp/DSEE63}}.
# Unzip the file.
{noformat}
tar -xzf DSEE.6.3.Linux-X86-full.tar.gz
{noformat}
# Deploy the DSEE6.3 software to the {{/opt/sun/directory}} directory.
{noformat}
cd DSEE_ZIP_Distribution
./dsee_deploy install -I -i /opt/sun/directory
{noformat}
# Create a new directory server instance in the {{/var/opt/sun/directory/dsins1}} directory.
{noformat}
mkdir -p /var/opt/sun/directory/
cd /opt/sun/directory/ds6/bin
./dsadm create /var/opt/sun/directory/dsins1
{noformat}
# When prompted, type *{{adminpass}}* for the Directory Manager password.
# Create the user and group suffix *{{o=isp}}*.
{noformat}
cd /opt/sun/directory/ds6/bin
./dsadm start /var/opt/sun/directory/dsins1
./dsconf create-suffix "o=isp"
{noformat}
# When prompted, type *Y* to accept the certificate.
# When prompted, type *{{adminpass}}* for the Directory Manager password.
# Continue with the next section.

h3. Installing and Configuring Application Server 9.1 Update 2

Application Server 9.1 Update 2 is the primary web container used by Convergence, Communications Express, Delegated Administrator, Access Manager, Directory Control Center, and Instant Messaging.

# Move the downloaded Application Server Update 2 installer {{sjsas_ee-9_1_02-linux.bin}} to a temporary location, such as {{/tmp/APPSVR91U2}}.
# Launch the installer.
{noformat}
cd /tmp/APPSVR91U2
chmod +x sjsas_ee-9_1_02-linux.bin
./sjsas_ee-9_1_02-linux.bin -console
{noformat}
# When prompted, press Enter to continue.
# Accept the License Agreement by typing *yes* when prompted.
The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 6 Application Server Settings*
||Option||\[Default Value\]||Enter:||
|Installation Directory|\[/opt/SUNWappserver\]|*/opt/sun/appserver*|
|Create Directory or Choose New|Create Directory|_accept default_|
|Install Node Agent|\[yes\]|_accept default_|
|Install High Availability Database Server|\[no\]|_accept default_|
|Install Load Balancing Plugin|\[no\]|_accept default_|
|Install Domain Administration Server|\[yes\]|_accept default_|
|Install Sample Applications|\[yes\]|*no*|
|Java Configuration|\[1. Install Java 2 SDK (5.0)\]|*2. Reuse existing Java 2 SDK*|
|Existing JDK Location|\[/usr/java/jdk1.6.0_13\]|*/usr/java/latest*|
|Admin User|\[admin\]|_accept default_|
|Admin User's Password|--|*adminpass*|
|Master Password for SSL Certificate|---|*adminpass*|
|Admin Port|\[4848\]|_accept default_|
|HTTP Port|\[8080\]|*80*|
|HTTPS Port|\[8181\]|*443*|
|Enable Updatecenter client|\[yes\]|*no*|
|Upgrade from previous AS version|\[no\]|_accept default_|
# Select {{Install Now}} at the Ready to Install screen.
The installer begins to install the software.
# Start the Application Server:
{noformat}
cd /opt/sun/appserver/bin
./asadmin start-domain domain1
{noformat}
# When prompted, type:
username: *{{admin}}*
admin password: *{{adminpass}}*
master password: *{{adminpass}}*
# Perform the following steps to save the {{admin}} username and password so they don't need to be provided each time Application Server is started. (You must still type the master password.)
{noformat}
cd /opt/sun/appserver/bin
./asadmin login
{noformat}
# Type *{{admin}}* and *{{adminpass}}* as the username and password when prompted.
# Continue with the next section.

*To Deploy and Enable Directory Server Control Center (DSCC)*

The Directory Server Control Center is a web-based GUI used to configure and administer Directory Server instances.

# Enable the DSCC registry.
{noformat}
cd /opt/sun/directory/dscc6/bin/
./dsccsetup ads-create
{noformat}
# At the Choose password for Directory Service Manager option, type *{{adminpass}}* (the default password).
# Edit the {{/opt/sun/appserver/domains/domain1/config/server.policy}} file to add the following required DSCC permissions:
{code}
// Permissions for Directory Service Control Center
grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc/-"
{
permission java.security.AllPermission;
};
{code}
# Access the Application Server administration console using a web-browser at the following location:
{nolink}https://_fully-qualified-hostname_:_admin-port_/{nolink}
In this example, type:
*{nolink}https://demo.comms.beta.com:4848/{nolink}*
# Log in by using the {{admin}} username and {{adminpass}} password.
# To deploy application from the {{/opt/sun/directory/var/dscc6/dscc.war}} file, select *Applications* then *Web Applications* from the left-hand menu in the Administration Console.
# Select the *Deploy* option from the Web Applications menu.
# Select Local packaged file or directory that is accessible from the Application Server.
# Type the full path of the DSCC war file: *{{/opt/sun/directory/var/dscc6/dscc.war}}*.
# Click the OK button at the bottom of the page.
# Log out of the Administration Console once the DSCC deployment has completed.
# Restart Application Server:
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# When prompted, type the master password: *{{adminpass}}*

*To Register the Directory Server Instance in DSCC*

# Access the DSCC console at the following location:
{nolink}http://_fully-qualified-hostname_:_application-server-port_/dscc{nolink}
In this example, type:
*{nolink}http://demo.comms.beta.com/dscc{nolink}*
# Log in by using the {{admin}} username and {{adminpass}} password.
# Select the {{Directory Servers}} tab.
# Select {{Register Existing Server...}} action from the {{More Server Actions}} drop-down menu.
A new screen appears.
# Type or select the following values:
#* Host: *{{demo.comms.beta.com}}*
#* Instance Path: *{{/var/opt/sun/directory/dsins1}}*
#* DSCC Agent Port: *{{11162}}*
#* Description: *{{Demo Directory Server}}*
# Select the Next button to continue.
# In the Provide Authentication Information for the Host step, type the following values:
#* User ID: *{{root}}*
#* Password: _root-password_
# Select the Next button to continue.
# In the Review Server Certificate step, select the Next button.
{info:title=Note}
Bug 6710506 (DSCC Application Error Exception encountered during forward when registering a ds instance in dscc) can cause an Exception error at this step. If you experience this error, repeat the registration steps from the beginning.
{info}
# In the Provide Authentication Information step, type the following values:
#* Administration DN: *{{cn=Directory Manager}}*
#* Password: *{{adminpass}}*
# Select the *Next* button to continue.
# At the final Summary step, click the *Finish* button to complete the process then close the window once the registration has completed.
You should now see the server {{demo.comms.beta.com:389}} listed in the Directory Servers listing.
# Log out of the DSCC interface.
# Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.
{toc-zone}

h2. Configuring Communications Suite Components

This section describes how to run the individual component configuration utilities to perform initial software configuration.

This section contains the following topics:
{toc-zone:minLevel=3|maxLevel=3|location=top|type=list}

h3. Preparing the LDAP Directory Server
This section explains how to prepare the Directory Server LDAP schema.

*To Apply Schema 2 to Your Directory Tree*
# Change the directory where the {{comm_dssetup script}} is located and run the script, for example:
{noformat}
cd /opt/sun/comms/dssetup/sbin/
./comm_dssetup.pl
{noformat}
# Type *{{y}}* to continue.
The perl script prompts for a series of options. The following table shows how to respond to the prompts.
*Table 10 Values for comm_dssetup.pl Script*
||Option||\[Default Value\]||Enter:||
|Directory server root|\[/opt/sun/directory/var/dscc6/dcc\]|*/var/opt/sun/directory*|
|Directory server instance|\[dsins1\]|_accept default_|
|Directory Manager DN|\[cn=Directory Manager\]|_accept default_|
|Directory Manager Password|-|*adminpass*|
|Use directory server for users/groups|\[yes\]|_accept default_|
|Users/Groups base suffix|\[o=isp\]|_accept default_|
|Schema type?|\[1\]|*2*|
|Confirm Schema Type?|\[n\]|*y*|
|Update the schema files?|\[yes\]|_accept default_|
|Configure new indexes?|\[yes\]|_accept default_|
|Reindex new indexes?|\[yes\]|_accept default_|
# Confirm your choices and type *{{y}}* to continue.
The {{comm_dssetup}} script proceeds.
# When prompted, type *{{y}}* to continue with the script.
# Continue with the next section after {{comm_dssetup}} completes and the Successful Completion message is displayed.

h3. Configuring Delegated Administrator and Communications CLI
This section describes configuring Delegated Administrator console and utility, which provide user and group management.

*To Configure Delegated Administrator*

# Change to the directory where the configuration script was installed and run the script, for example:
{noformat}
cd /opt/sun/comms/da/sbin
./config-commda -nodisplay
{noformat}
# Select Enter in the Welcome window.
# Accept the default, {{/var/opt/sun/comms/da}}, for the Directory to store Configuration and Data Files:
If the directory does not exist, select {{Create Directory}} to create the directory.
# Install {{Delegated Administrator Utility}}, {{Console}}, and {{Server}}.
The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 11 Values for config-commda Script*
||Option||\[Default Value\]||Enter:||
|DA Web-Container Hostname|\[demo.comms.beta.com\]|_accept default_|
|DA Web-Container Port|\[8080\]|*80*|
|Default Domain|\[comms.beta.com\]|_accept default_|
|Default SSL Port|\[443\]|_accept default_|
|Web Container|\[Web Server 6.x/WEB\]|*APP8*|
|Install Directory (for DA Console)|\[/opt/sun/appserver\]|_accept default_|
|Domain Directory|\[/var/opt/sun/appserver/domains/domain1\]|*/opt/sun/appserver/domains/domain1*|
|Doc Root Directory|\[/var/opt/sun/appserver/domains/domain1/docroot\]|*/opt/sun/appserver/domains/domain1/docroot*|
|Server Target Name|\[server\]|_accept default_|
|Virtual Server Identifier|\[server\]|_accept default_|
|Server Instance HTTP Port|\[80\]|_accept default_|
|Administration Server Port|\[4849\]|*4848*|
|Administrator User ID|\[admin\]|_accept default_|
|Administrator Password|-|*adminpass*|
|Secure Administration Server Instance?|\[yes\]|_accept default_|
|Default Domain Separator|\[@\]|_accept default_|
|Directory Server Interface|\[DL\]|_accept default_|
|Web Container|\[Web Server 6.x/WEB\]|*APP8*|
|Install Directory (for DA Server)|\[/opt/sun/appserver\]|_accept default_|
|Domain Directory|\[/var/opt/sun/appserver/domains/domain1\]|*/opt/sun/appserver/domains/domain1*|
|Doc Root Directory|\[/var/opt/sun/appserver/domains/domain1/docroot\]|*/opt/sun/appserver/domains/domain1/docroot*
|Server Target Name|\[server\]|_accept default_|
|Virtual Server Identifier|\[server\]|_accept default_|
|Server Instance HTTP Port|\[80\]|_accept default_|
|Administration Server Port|\[4849\]|*4848*|
|Administrator User ID|\[admin\]|_accept default_|
|Administrator Password|-|*adminpass*|
|Secure Administration Server Instance?|\[yes\]|_accept default_|
|URL of Directory Server|\[ldap://demo.comms.beta.com:389\]|_accept default_|
|Bind As|\[cn=Directory Manager\]|_accept default_|
|Password|-|*adminpass*|
|Internal LDAP user (daAdmin) Password|-|*adminpass*|
|Organization DN|\[o=comms.beta.com,o=isp\]|_accept default_|
|Top Level Admin for Default Organization|\[admin\]|_accept default_|
|Password|-|*adminpass*|
|Load Sample Service Packages|\[yes\]|_accept default_|
|Load Sample Organizations|\[yes\]|*no*|
# Select *1* - Configure Now.
The script begins to run.
# When the panel displays "All Tasks Passed," click *Next* to continue.
Two warnings appear: one reminds you to restart the Application Server; the other to remind you to enable the mail and calendar services in the domain. The following steps address these issues.
# Select *Close/Done* to exit the Delegated Administrator Configuration wizard.
# Restart the Application Server
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# Type the master password when prompted: *adminpass*
# Modify the default domain to provide mail, calendar and IM services then create a test user account with a username of {{jdoe}} and password of {{demo}} by using the {{commadmin}} utility:
{noformat}
cd /opt/sun/comms/da/bin/
./commadmin domain modify -D admin -w adminpass -d comms.beta.com -S mail,cal,im \
-H demo.comms.beta.com -B demo.comms.beta.com
./commadmin user create -D admin -w adminpass -S mail,cal,im -H demo.comms.beta.com -B demo.comms.beta.com \
-F John -L Doe -l jdoe -W demo -d comms.beta.com -E jdoe@comms.beta.com
{noformat}
You can create as many users as you like at this point.
# Continue with the next procedure.

*To Log in to Delegated Administrator*
# In your web browser, open a URL for Delegated Administrator.
{nolink}http://_fully-qualified-hostname_:_app-server-port_/da/{nolink}
In this example, type:
*{nolink}http://demo.comms.beta.com:80/da{nolink}*
# Log in using *admin* and *adminpass* as the user ID and password.
# After verifying that you can access the Delegated Administrator GUI interface, log out.
# Continue with the next section to configure Messaging Server

h3. Configuring Messaging Server
This section describes configuring Messaging Server.

*To Disable sendmail*
Prior to configuring Messaging Server, use the following to stop the current sendmail process and prevent it from starting during boot.
{noformat}
/etc/init.d/sendmail stop
chkconfig --del sendmail
{noformat}

*To Configure Messaging Server*
# Change to the directory where the Messaging Server configure script is stored, then run the script, for example:
{noformat}
cd /opt/sun/comms/messaging/bin
./configure -nodisplay
{noformat}
The Configuration Wizard appears. Read the introductory information and proceed.
# Verify the following:
#* Fully qualified host name of messaging server, FQHN: {{demo.comms.beta.com}}
#* Directory to store config/data files: {{/var/opt/sun/comms/messaging}}
#* Select {{MTA}}, {{Message Store}}, and {{Webmail Server}} to install.
# The installation script prompts for a series of options.
The following table shows how to respond to the configuration options:
*Table 12 Values for Messaging Server configure Script*
||Option||\[Default Value\]||Enter:||
|Messaging Server Unix user|\[mailsrv\]|_accept default_|
|Messaging Server Unix group|\[mail\]|_accept default_|
|User/Group Server Ldap|\[ldap://demo.comms.beta.com:389\]|_accept default_|
|Bind As|\[cn=Directory Manager\]|_accept default_|
|Password|-|*adminpass*|
|Postmaster email address|-|*jdoe@comms.beta.com*|
|Password for Messaging Server accounts|-|*adminpass*|
|Default email Domain|\[comms.beta.com\]|_accept default_|
|Organization DN|\[o=comms.beta.com,o=isp\]|_accept default_|
# Select *Configure Now*.
# When configuration is finished, Select *Next/Done* to continue and exit the configuration utility
# Enable Communications Express (UWC) access to webmail server
{noformat}
cd /opt/sun/comms/messaging/bin
./configutil -o local.webmail.sso.uwcenabled -v 1
./configutil -o service.imap.maxsessions -v 1000
{noformat}
# Start Messaging Server.
{noformat}
cd /opt/sun/comms/messaging/bin
./start-msg
{noformat}
# Continue with the next section to configure Calendar Server.

h3. Configuring Calendar Server
This section shows you how to run the Calendar Server configuration script and how to verify the Calendar Server configuration.

*To Configure Calendar Server*
# Change to the directory where the configuration script was installed then run the configuration script, for example:
{noformat}
cd /opt/sun/comms/calendar/calendar/sbin
./csconfigurator.sh -nodisplay
{noformat}
# Select *Next/Enter* at the Welcome page.
# The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 13 Values for Calendar Server csconfigure Script*
||Option||\[Default Value\]||Enter:||
|LDAP Server Host Name|\[demo.comms.beta.com\]|_accept default_|
|LDAP Server Port|\[389\]|_accept default_|
|Directory Manager DN|\[cn=Directory Manager\]|_accept default_|
|Directory Manager Password|-|*adminpass*|
|Virtual Domains settings: |\[comms.beta.com\]|*1. comms.beta.com*|
|Calendar Administrator Username|\[calmaster\]|_accept default_|
|Calendar Administrator Password|-|*adminpass*|
|Calendar Administrator Email address|\[root@comms.beta.com\]|*calmaster@comms.beta.com*|
|Site administrator|\[1. Yes\]|_accept default_|
|Create calmaster@comms.beta.com account|\[1. Create it\]|_accept default_|
|Setup a Front End/Back End deployment|\[2. No\]|_accept default_|
|Administrator Email Address|\[calmaster@comms.beta.com\]|_accept default_|
|SMTP Host Name|\[demo.comms.beta.com\]|_accept default_|
|Service Port|\[80\]|*3080*|
|Maximum Sessions|\[5000\]|_accept default_|
|Maximum Threads|\[20\]|_accept default_|
|Number of server processes|\[1\]|_accept default_|
|Runtime User ID|\[icsuser\]|_accept default_|
|Runtime Group ID|\[icsgroup\]|_accept default_|
|Start Calendar Server after successful configuration|\[2. No\]|_accept default_|
|Start Calendar Server on system startup|\[1. Yes\]|*2. No*|
|Create "icsuser" User ID?|\[Create User ID\]|_accept default_|
|Config Directory|\[/etc/opt/sun/comms/calendar/calendar/config\]|_accept default_|
|Database Directory|\[/var/opt/sun/comms/calendar/calendar/csdb\]|_accept default_|
|Attachment Store Directory|\[/var/opt/sun/comms/calendar/calendar/astore\]|_accept default_|
|Logs Directory|\[/var/opt/sun/comms/calendar/calendar/logs\]|_accept default_|
|Temporary Files Directory|\[/var/opt/sun/comms/calendar/calendar/tmp\]|_accept default_|
|Enable Archive|\[1. enable\]|_accept default_|
|Archive Directory|\[/var/opt/sun/comms/calendar/calendar/csdb/archive\]|_accept default_|
|Keep archives for (in days)|\[Minimum: 3, Maximum: 6\]|_accept default_|
|Enable Hot Backup|\[1. enable\]|_accept default_|
|Hot Backup Directory|\[/var/opt/sun/comms/calendar/calendar/csdb/hotbackup\]|_accept default_
|Keep hot backups for (in days)|\[Minimum: 3, Maximum: 6\]|_accept default_|
# Select *Configure Now* to configure Calendar Server.
# Select *2. Done* when the configuration is complete and exit the configurator.
# Open the {{/opt/sun/comms/calendar/calendar/config/ics.conf}} file by using your preferred editor e.g. {{vi}}.
# Set the following values to enable Calendar Server reminders:
{noformat}
caldb.serveralarms = "yes"
caldb.serveralarms.url = "enp:///ics/customalarm"
caldb.serveralarms.contenttype = "text/xml"
{noformat}
# Start the Calendar Server daemons, for example:
{noformat}
cd /opt/sun/comms/calendar/calendar/sbin
./start-cal
{noformat}
# Continue with the next section to configure Communications Express.

h3. Configuring Communications Express
# Change to the directory where you installed Communications Express then run the configuration utility, for example:
{noformat}
cd /opt/sun/comms/ce/uwc/sbin
./config-uwc -nodisplay
{noformat}
# Select *Enter* at the Welcome page.
# Accept the default directory, {{/var/opt/sun/comms/ce/uwc}}, in which to store Configuration and Data Files.
If the directory does not exist, select {{Create Directory}} to create the directory.
# Install both the {{Mail}} and {{Calendar}} Components
The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 14 Values for Communications Express Configuration Utility*
||Option||\[Default Value\]||Enter:||
|Host Name|\[demo\]|_accept default_|
|DNS Domain Name|\[comms.beta.com\]|_accept default_|
|Web Container|\[Webserver 7.X\]|*App Server (APP)*|
|Application Server Install Directory|\[/opt/sun/appserver\]|_accept default_|
|Application Server Domain Directory|\[/var/opt/sun/appserver/domains/domain1\]|*/opt/sun/appserver/domains/domain1*|
|Application Server Doc Root Directory|\[/var/opt/sun/appserver/domains/domain1/docroot\]|*/opt/sun/appserver/domains/domain1/docroot*|
|Server Instance HTTP Port|\[80\]|_accept default_|
|Administration Server Port|\[4849\]|*4848*|
|Administrator User ID|\[admin\]|_accept default_|
|Administrator Password|-|*adminpass*|
|Secure Admin Server Instance|\[no\]|*yes*|
|Module Name|\[Communications_Express\]|_accept default_|
|Web Container User|\[root\]|_accept default_|
|Web Container Group|\[root\]|_accept default_|
|URI Path|\[/uwc\]|_accept default_|
|Hosted Domain Support|\[yes\]|_accept default_|
|LDAP URL|\[ldap://demo.comms.beta.com:389\]|_accept default_|
|Bind DN|\[cn=Directory Manager\]|_accept default_|
|Bind Password|-|*adminpass*|
|DC Tree Suffix|\[o=isp\]|_accept default_|
|Default Domain|\[comms.beta.com\]|_accept default_|
|Access Manager for SSO|\[no\]|_accept default_|
|Webmail Host Name|\[demo.comms.beta.com\]|_accept default_|
|Webmail Port Number|-|*8990*|
|Login in Secure Mode|\[no\]|_accept default_|
|Webmail SSL Port Number|-|*8991*|
|Webmail Administrator Username|-|*admin@comms.beta.com*|
|Webmail Adminstrator Password|-|*adminpass*|
|Calendar Server Host Name|\[demo.comms.beta.com\]|_accept default_|
|Calendar Server Port Number|\[9004\]|*3080*|
|Calendar Server Administrator Username|\[calmaster\]|*calmaster@comms.beta.com*|
|Calendar Server Adminstrator Password|-|*adminpass*|
|PAB Directory Server URL|\[ldap://demo.comms.beta.com\]|_accept default_|
|PAB Directory Server Bind DN|\[cn=Directory Manager\]|_accept default_|
|PAB Directory Server Bind Password|-|*adminpass*|
# Select *Configure Now* to configure Communications Express (UWC).
# Select *Done* when the configuration is complete and close the configurator.
# Restart the Application Server
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# Type the master password when prompted: *{{adminpass}}*

*To Log in to Communications Express*
# In your web browser, open a URL for Communications Express. The URL for Communications Express (UWC) is:
{{http://}}_fully-qualified-hostname_:_app-server-port_{{/uwc/}}
In this example, type:
*{nolink}http://demo.comms.beta.com:80/uwc{nolink}*
# Log in using *jdoe* and *demo* as the user ID and password.
# After verifying that you can access Communications Express, log out.
# Continue with the next section to configure Instant Messaging Server.

h3. Configuring Instant Messaging Server

This section shows you how to run the Instant Messaging configurator script.

*To Configure Instant Messaging Server*

# Change to the directory where the configuration script was installed then run the configurator script, for example:
{noformat}
cd /opt/sun/comms/im/sbin
./configure --nodisplay
{noformat}
# Select *Next/Enter* at the Welcome page.
The Components Selection page appears.
# Select both {{Server}} and {{Client}} components for configuration.
# The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 15 Values for Instant Messaging configure Script*
||Option||\[Default Value\]||Enter:||
|Use AM for Single-Sign-On|\[no\]|_accept default_|
|Use AM for Policy|\[no\]|_accept default_|
|IM User Properties store location|\[1. On the file system\]|*2. In the directory*|
|User ID|\[inetuser\]|_accept default_|
|Group ID|\[inetgroup\]|_accept default_|
|Runtime Directory|\[/var/opt/sun/im\]|_accept default_|
|Create User ID?|\[2. Choose New\]|*1. Create User ID*|
|Domain Name|\[comms.beta.com\]|_accept default_|
|XMPP Port|\[5222\]|_accept default_|
|Multiplexed XMPP Port|\[45222\]|_accept default_|
|XMPP Server Port|\[5269\]|_accept default_|
|Disable Server (enable only multiplexor)|\[no\]|_accept default_|
|LDAP Host Name|\[demo.comms.beta.com\]|_accept default_|
|LDAP Port Number|\[389\]|_accept default_|
|Base DN|\[dc=comms,dc=beta,dc=com\]|*o=isp*|
|Bind DN|-|*cn=Directory Manager*|
|Bind Password|-|*adminpass*|
|Enable Email Integration|\[yes\]|_accept default_|
|SMTP Server|\[demo.comms.beta.com\]|_accept default_|
|Enable Email Archiving|\[yes\]|_accept default_|
|Deploy Messenger Resources|\[yes\]|_accept default_|
|Codebase|\[http://demo.comms.beta.com:80/im\]|_accept default_|
|Enable Audio|\[no\]|*yes*|
|Webcontainer Path|-|*/opt/sun/appserver*|
|Web Administration URL|-|*{nolink}https://demo.comms.beta.com:4848/{nolink}*|
|Web Administrator User Id|\[admin\]|_accept default_|
|Web Administrator Password|-|*adminpass*|
|Deploy IM HTTP Gateway|\[yes\]|*no*|
|Deploy IM IMPS Gateway|\[yes\]|*no*|
|Enable Calendar Agent|\[no\]|*yes*|
|Enable local component|\[no\]|*yes*|
|XMPP server hostname|\[demo.comms.beta.com\]|_accept default_|
|XMPP server port|\[5269\]|_accept default_|
|Notification Server Hostname|-|*demo.comms.beta.com*|
|Notification Server Port|\[57997\]|_accept default_|
|Calendar alarm URL|\[enp:///ics/customalarm\]|_accept default_|
|Enable SMS Gateway|\[no\]|_accept default_|
|Enable local component|\[no\]|_accept default_|
|Enable MSN Gateway|\[no\]|_accept default_|
|Enable local component|\[no\]|_accept default_|
|Enable AIM Gateway|\[no\]|_accept default_|
|Enable local component|\[no\]|_accept default_|
|Enable YIM Gateway|\[no\]|_accept default_|
|Enable local component|\[no\]|_accept default_|
|Start Services After Successful Configuration|\[yes\]|*no*|
|Start Services When System starts|\[yes\]|*no*|
# At the Configuration Summary page, select *Done* to exit.
# Edit the {{/opt/sun/comms/im/config/iim.conf}} file using your preferred editor, e.g. {{vi}}, to prepare for the Convergence web-interface.
Add the new httpbind and avatar component JIDs to this file by making the following changes/additions:
{noformat}
! known components/agent. Add yours as needed
!iim_server.components = "agent-calendar,httpbind,smppbind,msn_gateway,aim_gateway,yim_gateway"
iim_server.components = "agent-calendar,httpbind,avatar"
iim_agent.enable = "true"

! httpbind component (HTTP/XMPP Gateway)
! ======================================
iim_agent.httpbind.enable = "true"
httpbind.jid = "demo.httpbind.comms.beta.com"
httpbind.password = "adminpass"

! avatar component
! ======================================
iim_agent.avatar.enable = "true"
avatar.jid = "demo.avatar.comms.beta.com"
avatar.password = "adminpass"
{noformat}
{info:title=Note}The {{httpbind.jid}} and {{avatar.jid}} strings are in the form <host>.httpbind.<domain> and <host>.avatar.<domain> respectively as this will be the value auto-generated during upcoming Convergence configuration stage.{info}
Enable Hosted Domain Schema 2 support by making the following changes/additions:
{noformat}
! whether to use Identity Server for policy storage, default to no (iim_ldap)
!iim.policy.modules = "iim_ldap"
iim.policy.modules = "iim_ldap_schema2"
iim_ldap.schema2.domain_config_root = "o=isp"
{noformat}
# Start the Instant Messaging server.
{noformat}
cd /opt/sun/comms/im/sbin/
./imadmin start
{noformat}
# Restart the Application Server.
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# Type the master password when prompted: *{{adminpass}}*
# Continue with the next section to configure Sun Convergence.

h3. Configuring Sun Convergence

This section describes how to configure Sun Convergence by using the {{init-config}} command.

# Change to the directory where you installed the Convergence then run the configuration utility, for example:
{noformat}
cd /opt/sun/comms/iwc/sbin
./init-config -nodisplay
{noformat}
# Select *Next/Enter* at the Welcome page.
# Accept the default value for the Directory to store Configuration and Data Files: {{/var/opt/sun/comms/iwc}}
If the directory does not exist, select Create Directory to create the directory.
# Configure the {{Mail}} and {{Calendar}} and {{Instant Messaging}} Services.
# The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 16 Values for Convergence configure Script*
||Option||\[Default Value\]||Enter:||
|Host Name|\[demo\]|_accept default_|
|DNS Domain Name|\[comms.beta.com\]|_accept default_|
|Application Server Install Directory|\[/opt/sun/appserver\]|_accept default_|
|Domain Directory|\[/opt/sun/appserver/domains/domain1\]|_accept default_|
|Document Root Directory|\[/opt/sun/appserver/domains/domain1/docroot\]|_accept default_|
|Server Target Name|\[server\]|_accept default_|
|Virtual Server Identifier|\[server\]|_accept default_|
|Server Instance HTTP Port|\[8080\]|*80*|
|Administration Server Port|\[4848\]|_accept default_|
|Administrator User ID|\[admin\]|_accept default_|
|Administrator Password|-|*adminpass*|
|Secure Administration Server Instance|\[yes\]|_accept default_|
|URI Path|\[/iwc\]|_accept default_|
|Enable Hosted Domain Support|\[yes\]|_accept default_|
|Directory Server LDAP URL|\[ldap://demo.comms.beta.com:389/\]|_accept default_|
|Bind DN|\[cn=Directory Manager\]|_accept default_|
|Bind Password|-|*adminpass*|
|DC Tree suffix|\[o=isp\]|_accept default_|
|Default Domain Name|\[comms.beta.com\]|_accept default_|
|Webmail Server Host Name|\[demo.comms.beta.com\]|_accept default_|
|Webmail Server Port Number|\[8990\]|_accept default_|
|Webmail Server Running In Secure Mode?|\[no\]|_accept default_|
|Webmail Admin User ID|\[admin\]|*admin@comms.beta.com*|
|Admin Password|-|*adminpass*|
|Calendar Server Host Name|\[demo.comms.beta.com\]|_accept default_|
|Calendar Server Port|\[80\]|*3080*|
|Calendar Server Running In Secure Mode?|\[no\]|_accept default_|
|Administrator User ID|\[calmaster\]|*calmaster@comms.beta.com*|
|Administrator User Password|-|*adminpass*|
|Instant Messaging Server Domain Name|\[comms.beta.com\]|_accept default_|
|Instant Messaging Server Host Name|\[demo.comms.beta.com\]|_accept default_|
|Server Port|\[5269\]|_accept default_|
|httpbind Component JID|\[demo.httpbind.comms.beta.com\]|_accept default_|
|Password|-|*adminpass*|
|Avatar Component JID|\[demo.avatar.comms.beta.com\]|_accept default_|
|Password|-|*adminpass*|
|Convergence Administrator Username|\[admin\]|_accept default_|
|Password|-|*adminpass*|
# Select *1. Configure Now* to configure Sun Convergence.
The system displays a message to remind you to restart the Application Server Instance.
# Once the configuration is completed, exit the configuration tool.
# Restart Application Server.
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# Type the master password when prompted: *{{adminpass}}*
# Continue with the next procedure.

*To Log into the Sun Convergence Client*
# In your web browser, open a URL for Sun Convergence and log in as a test user. The URL for Sun Convergence is:
{{http://}}_fully-qualified-hostname_{{:}}_app-server-port_{{/iwc}}
In this example, type:
*{nolink}http://demo.comms.beta.com:80/iwc{nolink}*
# Log in using *jdoe* and *demo* as the user ID and password.
# After verifying that you can access the Sun Convergence Client, log out.

{anchor:createusers}
h3. Creating Additional User Accounts and Groups

This section describes how to create additional users accounts and groups.

*To Create Users and Groups using CLI*

The following example shows how to create two new users ({{demo1}} and {{demo2}}) with the password {{demo}} using the Delegated Administrator command-line utility and also how to create a the mailing and calendar group (Demostaff@comms.beta.com) consisting of the newly created users.
{noformat}
cd /opt/sun/comms/da/bin
./commadmin user create -D admin -w adminpass -S mail,cal,im -H demo.comms.beta.com -B demo.comms.beta.com \
-F Demo -L One -l demo1 -W demo -d comms.beta.com -E Demo.One@comms.beta.com
./commadmin user create -D admin -w adminpass -S mail,cal,im -H demo.comms.beta.com -B demo.comms.beta.com \
-F Demo -L Two -l demo2 -W demo -d comms.beta.com -E Demo.Two@comms.beta.com
./commadmin group create -D admin -w adminpass -S mail,cal -H demo.comms.beta.com -j demo.comms.beta.com \
-G Demostaff -d comms.beta.com -E Demostaff@comms.beta.com -o jdoe -m demo1 -m demo2
{noformat}

*To Use the Delegated Administrator GUI to Create Users*

An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator web-based GUI. The high-level steps for creating users with Delegated Administrator are:

# The first time you use the Delegated Administrator GUI, you must add service packs to the organization that contains your users:
#* In your web browser, open the URL for Delegated Administrator.
In this example, type:
*{nolink}http://demo.comms.beta.com:80/da{nolink}*
#* Log in using *admin* as the Login ID and *adminpass* as the Password.
#* Click the check box next to comms.beta.com organization, then click the {{Allocate Service Package}} button.
#* The Allocate Service Package window appears with a list of service packages organized within a set of three pages. Near the top of this list is a Compare button.
#* To the right of this button is a button that maps the three pages into a single view. Click the Single Page button.
#* Select the desired service packages then click Next. The {{mailcalendarimsample}} service package is appropriate for this example, since this package enables the mail, calendar and instant messaging services.
#* Accept the Mail Service defaults, then click {{Next}}.
{info:title=Note}
If the Preferred Mail Host value is not set to the mail server host name {{demo.comms.beta.com}} in the Mail Service Details screen, close the window, log out of the Delegated Administrator GUI and return to the start of these steps.
{info}
#* If you chose a service package that contains Calendar, type the Calendar Host *{{demo.comms.beta.com}}* and *{{Yes}}* for Anonymous Login. Then click {{Next}}.
#* Select the quantity of each service pack desired then click {{Next}}. A quantity of 100 is appropriate for this example.
#* Review your choices and click {{Finish}} to create the service packages.
#* Once the service packs have been allocated for the domain, you can add users to the domain.
# Click the domain link. That is, click the {{comms.beta.com}} link
# Click the {{New}} button to create a new user within this domain. The New User window should appear.
# Type a First Name (such as *{{Demo}}*), a Last Name (such as *{{Five}}*), a Display Name (such as *{{Demo Five}}*), then click Next.
# You do not need to type postal information. Click {{Next}} again.
# Select a service pack for this user (as added earlier), for example, {{mailcalendarimsample}}, then click {{Next}}.
# Type the email address, for example, *{{Demo.Five@comms.beta.com}}*. The Mail Delivery Option should be Local Inbox. Leave the remaining fields blank then click {{Next}}.
# For the Calendar Service Details page, select your preferred timezone, then click {{Next}}.
# For the IM Service Details page, leave the User Roster field blank and click {{Next}}.
# Type the Login ID and Password then click Next. In this example, Login ID is {{demo5}} and password is {{demo}}.
# Verify the user information then click {{Finish}} to create the user.
{toc-zone}

h2. Enabling service start-up on boot

The following guide steps through the process of enabling Communication Suite 6 services to start automatically on boot and stop automatically on shut-down.

[CommSuite6U2:Communication Suite 6 Update 2 Start and Stop Scripts (Linux)]

{anchor:hostedconfig}
h2. Hosted domain configuration and creation

Hosted Domains, or Virtual Domains as they are also referred to, is a mechanism used to administrate and deliver services for users, groups and resources within a unique name-space. Each hosted domain can have different domain-level preferences, different Convergence customizations and be administrated within Delegated Administrator by different user accounts if required.

In a hosted domain installation, each domain shares the same instance of Messaging Server, Instant Messaging Server, Calendar Server, Convergence etc. This approach greatly reduces any overhead associated with using multiple hosted domains on a single server.

h4. Create new hosted domain using Delegated Administrator

During the installation and configuration of Communication Suite 6 update 2, an initial Default Domain of {{comms.beta.com}} is created. The creation of additional hosted domains can be achieved using either the Delegated Administrator CLI {{commadmin}} utility or the Delegated Administrator GUI interface.

*Delegated Administrator CLI*
Run the following command sequence to create the new hosted domain {{hosted.domain.com}} using the Delegated Administrator command-line utility.
{noformat}
cd /opt/sun/comms/da/bin/
./commadmin domain create -D admin -w adminpass -d hosted.domain.com -S mail,cal,im \
-H demo.comms.beta.com -B demo.comms.beta.com
{noformat}

*Delegated Administrator GUI*

Follow these steps to create the new hosted domain {{hosted.domain.com}} using the Delegated Administrator GUI interface.
# In your web browser, open the URL for Delegated Administrator.
In this example, type:
*{nolink}http://demo.comms.beta.com:80/da{nolink}*
# Log in using *admin* as the Login ID and *adminpass* as the Password.
# Click on the {{New Organization}} button. The {{New Organization}} window should then appear.
# In the Organization Information step, enter the new hosted domain {{hosted.domain.com}} in the Organization Name field then click the {{Next}} button.
# You do not need to type Contact Information. Click {{Next}} again.
# In the Account Information step, enter the new hosted domain {{hosted.domain.com}} again then click {{Next}}.
# At this point you will assign Service Packages to the domain using these steps:
#* To the right of this button is a button that maps the three pages into a single view. Click the Single Page button.
#* Select the desired service packages then click Next. The {{mailcalendarimsample}} service package is appropriate for this example, since this package enables the mail, calendar and instant messaging services.
#* Accept the Mail Service defaults, then click {{Next}}.
{info:title=Note}
If the Preferred Mail Host value is not set to the mail server host name {{demo.comms.beta.com}} in the Mail Service Details screen, close the window, log out of the Delegated Administrator GUI and return to the start of these steps.
{info}
#* If you chose a service package that contains Calendar, type the Calendar Host *{{demo.comms.beta.com}}* and *{{Yes}}* for Anonymous Login. Then click {{Next}}.
#* Select the quantity of each service pack desired then click {{Next}}. A quantity of 100 is appropriate for this example.
#* Review your choices and click {{Finish}} to create the service packages.
#* Once the service packs have been allocated for the domain, you can continue.
# Verify the new hosted domain information then click {{Finish}} to create the domain.

h4. Configure Convergence for the new hosted domain

Each new hosted domain must be manually registered with the Convergence Instant Messaging gateway so that users in this domain are able to access the Instant Messaging interface within Convergence.

# Edit {{/opt/sun/comms/iwc/config/httpbind.conf}} with your preferred editor
# Add the new domain to {{default.domains}} option. For example if your new hosted domain was {{hosted.domain.com}} your {{defaults.domain}} configuration line would resemble the following:
{noformat}
default.domains=comms.beta.com hosted.domain.com
{noformat}
# Restart Application Server.
{noformat}
cd /opt/sun/appserver/bin
./asadmin stop-domain domain1
./asadmin start-domain domain1
{noformat}
# Type the master password when prompted: *{{adminpass}}*

h4. Add new users to new hosted domain

Refer to the [Creating Additional User Accounts and Groups|#createusers] steps. Substitute in the newly created hosted domain name {{hosted.domain.com}} for every instance of the {{comms.beta.com}} domain in the steps.

Users in the newly created hosted domain log into the Convergence and UWC/Communications Express interface using the {{uid@hosted-domain-name}} format in the user login field.

{anchor:tuningtips}
h2. Single host installation tuning tips

* Use memory-mapped tmpfs file system for temporary server files

Redhat Enterprise Linux 4 by default provides the {{/dev/shm}} memory-mapped temporary file system:
{noformat}
[root@comms sbin]# df -k /dev/shm
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 387596 121488 266108 32% /dev/shm
{noformat}

Messaging Server, Directory Server and Instant Messaging server can all be configured to relocate temporary files to a memory-mapped file-system to reduce the number of I/O operations that are recorded to permanent storage.

*Messaging Server*
# Relocate the mboxlist temporary database files to the temporary file-system.
{noformat}
cd /opt/sun/comms/messaging/bin
./configutil -o store.dbtmpdir -v /dev/shm/msg-demo/
{noformat}
# Restart Messaging Server
{noformat}
cd /opt/sun/comms/messaging/bin
./stop-msg
./start-msg
{noformat}

*Directory Server*
Relocate the directory server temporary database files to the temporary file-system.
# Stop directory server
{noformat}
cd /var/opt/sun/directory/dsins1/
./stop-slapd
{noformat}
# Edit {{/var/opt/sun/directory/dsins1/config/dse.ldif}}
{noformat}
replace:
nsslapd-db-home-directory: /var/opt/sun/directory/dsins1/db

with:
nsslapd-db-home-directory: /dev/shm/slapd-demo/
{noformat}
# Start Directory Server
{noformat}
cd /var/opt/sun/directory/dsins1/
./start-slapd
{noformat}

*Instant Messaging Server*
Relocate the Instant Messaging server temporary "scratch" files to the temporary file-system.
# Stop the Instant Messaging Server
{noformat}
cd /opt/sun/comms/im/sbin
./imadmin stop
{noformat}
# Edit {{/opt/sun/comms/im/config/iim.conf}} and add the following line:
{noformat}
iim_server.scratch_directory = "/dev/shm/iim-demo/"
{noformat}
# Start the Instant Messaging Server
{noformat}
cd /opt/sun/comms/im/sbin
./imadmin start
{noformat}

h2. Known Issues and Limitations
* Calendar Server library path being used in preference of system library path causing applications such as Mozilla Firefox to fail to start due to library conflicts.

Bug #6758080 - "Calendar server on Linux should not use ldconfig"

Workaround: Comment out the following three lines in the {{start-cal}} script:
{noformat}
if [ $OSNAME = Linux ]; then
/sbin/ldconfig $SERVERROOT/lib
fi
{noformat}

For more information about known issues, see [Communications Suite 6 Update 2 Release Notes].