Deployment Example: Sun Java Communications Suite 7 on a Single Host (Linux)

This deployment example describes how to install Sun Java Communications Suite 7 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.

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.

Comparison to Communications Suite 6 Update 2 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.

• Communications Express removed
  • Communications Express has been replaced by Convergence.
• IMAP-IDLE now enabled by default
  • Provides improved IMAP client responsiveness (if the email client supports IMAP-IDLE)

New features for Communication Suite 7 can also be found in the Communications Suite 7 Release Notes.

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:

Installation Overview

This scenario results in a functioning deployment suited for the evaluation and testing of Sun Java Communications Suite 7 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.

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 3
• Sun Java System Calendar Server 6.3 + Patches
• Sun Java System Instant Messaging 8 Update 2
• Sun Java System Directory Server 6.3.1
• Sun GlassFish Enterprise Server 2.1 Patch 02
• Sun Java System Delegated Administrator 7.0 Patch 1
• Sun Convergence 1 Update 3
• 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.

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 for more information.

Implementation Specifications for This Example

This section describes implementation specifications for this example.

Table 1 Evaluation Host Hardware and Software Requirements

Note Communications Suite 7 is now supported with Redhat Enterprise Linux 5 update 3. Please note however that Directory Server 6.3.1 is not supported with Redhat Enterprise Linux 5.

Table 2 Client Software Requirements

Table 3 Server Configuration Information

Installation Time Estimates

The following table provides time estimates for installing this example.

Table 4 Installation Time Estimates

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

Installation Notes and Recommendations

1. Use gzip -d or gunzip to decompress the *.gz files.
2. 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

Summary of Installation and Configuration

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

1. Preparing the system for Sun Java Communications Suite
2. Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator and Convergence.
3. Installing and configuring Directory Server 6.3.1
4. Installing and configuring Glassfish 2.1
5. Deploying and enabling the Directory Server Control Center
6. Configuring Delegated Administrator and Communications CLI
7. Configuring Messaging Server
8. Configuring Calendar Server
9. Configuring Instant Messaging Server
10. Configuring Convergence

These installation steps result in a suitable deployment to evaluate and test Communications Suite 7. 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.

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.

Note Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as the root user.

This section contains the following topics:

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:

1. Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
   

   domain comms.beta.com
   nameserver 192.168.100.22
   nameserver 192.168.100.23
   nameserver 192.168.100.24
   nameserver 192.168.100.25
   

2. 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:

   10.1.82.52 demo.comms.beta.com wireless demo
   

3. 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:

   hosts: files dns nis [NOTFOUND=return]
   # OR (if NIS is not used)
   hosts: files dns
   

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.

1. In a terminal window, as root user, verify the number of file descriptors.
   ulimit -n
2. If this number is less than 16,384 you will need to increase the value.
3. 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
4. Add the following two lines to the /etc/security/limits.conf file.

   # Increase max file descriptors
   * - nofile 16384
   

5. Either reboot the system for the value to take effect or run the following command:
   sysctl -p /etc/sysctl.conf
6. In a new terminal window, as root verify the change.
   ulimit -n

To Enable Process Core Dumps

Red Hat Enterprise Linux disables process core dumps by default. Process core dumps are essential for tracing the root cause behind a process crashing. The following guide provides steps on enabling process core dumps:

How can core dumps be enabled for daemons (services) in Red Hat Enterprise Linux?

Getting the Necessary Software

To Get the Software

1. Get Communications Suite, Glassfish and Directory Server.

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.

1. Create the /tmp/CS7/ directory, move the Communication Suite 7 software (ci-7.0-0.02-Linux_x86.zip) to this directory and extract the files.

   cd /tmp/CS7
   unzip ci-7.0-0.02-Linux_x86.zip
   

2. Run the Communications Suite installer.

   ./commpkg install
   

3. Press Return to continue when prompted.
4. Review the license and type c to continue when prompted.
   You can also type s to skip the license display.
5. Accept the License Agreement by typing yes when prompted.
6. Accept the default Install location: /opt/sun/comms
7. Select the following components for installation (1,2,4,5,7,8).

   1.     Messaging Server 7u3 (7.3-11.01)
   2.     Comms DSsetup 6.4 (6.4-5.05)
   4.     Instant Messaging 8u2 (8.2-02.04)
   5.     Convergence 1u3 (1.0-10.01)
   7.     Comms Delegated Administrator 7 (7.0-1.00)
   8.     Calendar Server 6.3 (6.3-19.01)
   

   The installation proceeds.

8. Press Return when prompted to continue.
9. Continue with the next section.

Installing and Configuring Directory Server 6.3.1

To Install the Zip Version of Directory Server 6.3.1

1. Move the downloaded Directory Server 6.3.1 zip file DSEE.6.3.1.Linux-X86-full.tar.gz to a temporary location, such as /tmp/DSEE63.
2. Unzip the file. This file contains the DS6.3 zip file and the DS6.3.1 patch which will be applied later.

   tar -xzf DSEE.6.3.1.Linux-X86-patch.tar.gz
   tar -xzf DSEE.6.3.Linux-X86-full.tar.gz
   

3. Deploy the DSEE6.3 software to the /opt/sun/directory directory.

   cd DSEE_ZIP_Distribution
   ./dsee_deploy install -I -i /opt/sun/directory
   

   Note If you see the message "Error: Running Directory Server instances exist. You must stop them.", re-run the above command without the "-I" option.

4. Patch the DS6.3 install to DS6.3.1

   cd /tmp/DSEE63/126751-05
   tar -xzf DSEE.6.3.1.Linux-X86-patch.tar.gz
   ./dsee_deploy install -I -i /opt/sun/directory
   

   Note If you see the message "Error: Running Directory Server instances exist. You must stop them.", re-run the above command without the "-I" option.

5. Create a new directory server instance in the /var/opt/sun/directory/dsins1 directory.

   mkdir -p /var/opt/sun/directory/
   cd /opt/sun/directory/ds6/bin
   ./dsadm create /var/opt/sun/directory/dsins1
   

6. When prompted, type adminpass for the Directory Manager password.
7. Create the user and group suffix o=isp.

   cd /opt/sun/directory/ds6/bin
   ./dsadm start /var/opt/sun/directory/dsins1
   ./dsconf create-suffix "o=isp"
   

8. When prompted, type Y to accept the certificate.
9. When prompted, type adminpass for the Directory Manager password.
10. Continue with the next section.

Installing and Configuring Glassfish 2.1 Patch 02

Glassfish 2.1 is the primary web container used by Convergence, Delegated Administrator, Access Manager, Directory Control Center, and Instant Messaging.

1. Move the downloaded Glassfish 2.1 installer sges_ee-2_1-p02-linux.bin to a temporary location, such as /tmp/GF21.
2. Launch the installer.

   cd /tmp/GF21
   chmod +x sges_ee-2_1-p02-linux.bin
   ./sges_ee-2_1-p02-linux.bin -console -javahome /usr/java/default/
   

3. When prompted, press Enter to continue.
4. 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_16]	/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

5. Select Install Now at the Ready to Install screen.
   The installer begins to install the software.
6. Start the Application Server:

   cd /opt/sun/appserver/bin
   ./asadmin start-domain domain1
   

7. When prompted, type:
   username: admin
   admin password: adminpass
   master password: adminpass
8. 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.)

   cd /opt/sun/appserver/bin
   ./asadmin login
   

9. Type admin and adminpass as the username and password when prompted.
10. 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.

1. Enable the DSCC registry.

   cd /opt/sun/directory/dscc6/bin/
   ./dsccsetup ads-create
   

2. At the Choose password for Directory Service Manager option, type adminpass (the default password).
3. Edit the /opt/sun/appserver/domains/domain1/config/server.policy file to add the following required DSCC permissions:

   // Permissions for Directory Service Control Center
   grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc/-"
   {
   permission java.security.AllPermission;
   };
   

4. Access the Application Server administration console using a web-browser at the following location:
   https://fully-qualified-hostname:admin-port/
   In this example, type:
   https://demo.comms.beta.com:4848/
5. Log in by using the admin username and adminpass password.
6. 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.
7. Select the Deploy option from the Web Applications menu.
8. Select Local packaged file or directory that is accessible from the Application Server.
9. Type the full path of the DSCC war file: /opt/sun/directory/var/dscc6/dscc.war.
10. Click the OK button at the bottom of the page.
11. Log out of the Administration Console once the DSCC deployment has completed.

To Register the Directory Server Instance in DSCC

1. Access the DSCC console at the following location:
   http://fully-qualified-hostname:application-server-port/dscc
   In this example, type:
   http://demo.comms.beta.com/dscc
2. Log in by using the admin username and adminpass password.
3. Select the Directory Servers tab.
4. Select Register Existing Server... action from the More Server Actions drop-down menu.
   A new screen appears.
5. 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
6. Select the Next button to continue.
7. In the Provide Authentication Information for the Host step, type the following values:
   • User ID: root
   • Password: root-password
8. Select the Next button to continue.
9. In the Review Server Certificate step, select the Next button.

   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.

10. In the Provide Authentication Information step, type the following values:
    • Administration DN: cn=Directory Manager
    • Password: adminpass
11. Select the Next button to continue.
12. 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.
13. Log out of the DSCC interface.
14. Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.

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:

Preparing the LDAP Directory Server

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

To Apply Schema 2 to Your Directory Tree

1. Change the directory where the comm_dssetup script is located and run the script, for example:

   cd /opt/sun/comms/dssetup/sbin/
   ./comm_dssetup.pl
   

2. 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

3. Confirm your choices and type y to continue.
   The comm_dssetup script proceeds.
4. When prompted, type y to continue with the script.
5. Continue with the next section after comm_dssetup completes and the Successful Completion message is displayed.

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

1. Change to the directory where the configuration script was installed and run the script, for example:

   cd /opt/sun/comms/da/sbin
   ./config-commda -nodisplay
   

2. Select Enter in the Welcome window.
3. 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.
4. 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

5. Select 1 - Configure Now.
   The script begins to run.
6. When the panel displays "All Tasks Passed," hit enter to continue.
7. Select 2. Done to exit the Delegated Administrator Configuration wizard.
8. Modify the default domain to provide mail, calendar and IM services.

   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
   

9. Create a test user account with a username of jdoe and password of demo by using the commadmin utility:

   ./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
   

   You can create as many users as you like at this point.

10. Continue with the next procedure.

To Log in to Delegated Administrator

1. In your web browser, open a URL for Delegated Administrator.
   http://fully-qualified-hostname:app-server-port/da/
   In this example, type:
   http://demo.comms.beta.com:80/da
2. Log in using admin and adminpass as the user ID and password.
3. After verifying that you can access the Delegated Administrator GUI interface, log out.
4. Continue with the next section to configure Messaging Server

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.

/etc/init.d/sendmail stop
chkconfig --del sendmail

To Configure Messaging Server

1. Change to the directory where the Messaging Server configure script is stored, then run the script, for example:

   cd /opt/sun/comms/messaging/bin
   ./configure
   

   The Configuration Wizard appears. Read the introductory information and proceed.

2. 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:
   Path for Data and Configuration Files	[/var/opt/sun/comms/messaging]	accept default
   Messaging Server Unix user	[mailsrv]	accept default
   Messaging Server Unix group	[mail]	accept default
   Fully qualified local hostname	[demo.comms.beta.com]	accept default
   Default mail domain name	[comms.beta.com]	accept default
   Hostname for LDAP Directory Server	[localhost]	accept default
   LDAP administrator login	[cn=Directory Manager]	accept default
   LDAP administrator password	-	adminpass
   Mail address for postmaster notices	[admin@comms.beta.com]	jdoe@comms.beta.com
   Password for server administration	-	adminpass

3. Enable IMAP IDLE

   cd /opt/sun/comms/messaging/bin
   ./configutil -o local.store.notifyplugin.enshost -v "127.0.0.1"
   ./configutil -o local.store.notifyplugin.enseventkey -v "enp://127.0.0.1/store/%M"
   ./configutil -o local.store.notifyplugin -v "lib/libibiff"
   ./configutil -o local.store.notifyplugin.noneinbox.enable -v 1
   ./configutil -o service.imap.idle -v 1
   ./configutil -o service.imap.ensidle -v 1
   ./configutil -o local.ens.enable -v 1
   

4. Start Messaging Server.

   cd /opt/sun/comms/messaging/bin
   ./start-msg
   

5. Continue with the next section to configure Calendar Server.

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

1. Change to the directory where the configuration script was installed then run the configuration script, for example:

   cd /opt/sun/comms/calendar/calendar/sbin
   ./csconfigurator.sh -nodisplay
   

2. Select Next/Enter at the Welcome page.
3. 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

4. Select Configure Now to configure Calendar Server.
5. Select 2. Done when the configuration is complete and exit the configurator.
6. Open the /opt/sun/comms/calendar/calendar/config/ics.conf file by using your preferred editor e.g. vi.
7. Set the following values to enable Calendar Server reminders:

   caldb.serveralarms = "yes"
   caldb.serveralarms.url = "enp:///ics/customalarm"
   caldb.serveralarms.contenttype = "text/xml"
   

8. Start the Calendar Server daemons, for example:

   cd /opt/sun/comms/calendar/calendar/sbin
   ./start-cal
   

9. Continue with the next section to configure Instant Messaging Server.

Configuring Instant Messaging Server

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

To Configure Instant Messaging Server

1. Change to the directory where the configuration script was installed then run the configurator script, for example:

   cd /opt/sun/comms/im/sbin
   JAVA_HOME=/usr/java/latest ./configure --nodisplay
   

2. Select Next/Enter at the Welcome page.
   The Components Selection page appears.
3. Select both Server and Client components for configuration.
4. 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]	/var/opt/sun/comms/im
   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	-	https://demo.comms.beta.com:4848/
   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]	accept default
   Enable local component	[no]	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

5. At the Configuration Summary page, select Done to exit.
6. 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:

   ! known components/agent. Add yours as needed
   !iim_server.components = "agent-calendar,httpbind,smppbind,msn_gateway,aim_gateway,yim_gateway"
   iim_server.components = "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"
   

   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.

   Enable Hosted Domain Schema 2 support by making the following changes/additions:

   ! 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"
   

7. Start the Instant Messaging server.

   cd /opt/sun/comms/im/sbin/
   ./imadmin start
   

8. Continue with the next procedure.

To Log into the Sun Instant Messaging Java Client

1. In your web browser, open the URL for the Sun IM Java Client and log in as a test user:
   http://fully-qualified-hostname:app-server-port/im
   In this example, type:
   http://demo.comms.beta.com:80/im
2. Click the "Start" button.
3. Log into the Sun Java IM client using jdoe and demo as the User Name and Password.
4. After verifying that you can access the Sun Java IM client, exit the client.

Configuring Sun Convergence

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

1. Change to the directory where you installed the Convergence then run the configuration utility, for example:

   cd /opt/sun/comms/iwc/sbin
   ./init-config -nodisplay
   

2. Select Next/Enter at the Welcome page.
3. 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.
4. Configure the Mail and Calendar and Instant Messaging Services.
5. 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

6. Select 1. Configure Now to configure Sun Convergence.
7. Once the configuration is completed, exit the configuration tool.
8. Continue with the next procedure.

To Log into the Sun Convergence Client

1. 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:
   http://demo.comms.beta.com:80/iwc
2. Log in using jdoe and demo as the user ID and password.
3. After verifying that you can access the Sun Convergence Client, log out.

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.

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

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:

1. 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:
     http://demo.comms.beta.com:80/da
   • 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.

     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.

   • 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.
2. Click the domain link. That is, click the comms.beta.com link
3. Click the New button to create a new user within this domain. The New User window should appear.
4. Type a First Name (such as Demo), a Last Name (such as Five), a Display Name (such as Demo Five), then click Next.
5. You do not need to type postal information. Click Next again.
6. Select a service pack for this user (as added earlier), for example, mailcalendarimsample, then click Next.
7. 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.
8. For the Calendar Service Details page, select your preferred timezone, then click Next.
9. For the IM Service Details page, leave the User Roster field blank and click Next.
10. Type the Login ID and Password then click Next. In this example, Login ID is demo5 and password is demo.
11. Verify the user information then click Finish to create the user.

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.

Communications Suite 7 Start and Stop Scripts (Linux)

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.

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.

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

Delegated Administrator GUI

Follow these steps to create the new hosted domain hosted.domain.com using the Delegated Administrator GUI interface.

1. In your web browser, open the URL for Delegated Administrator.
   In this example, type:
   http://demo.comms.beta.com:80/da
2. Log in using admin as the Login ID and adminpass as the Password.
3. Click on the New Organization button. The New Organization window should then appear.
4. In the Organization Information step, enter the new hosted domain hosted.domain.com in the Organization Name field then click the Next button.
5. You do not need to type Contact Information. Click Next again.
6. In the Account Information step, enter the new hosted domain hosted.domain.com again then click Next.
7. 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.

     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.

   • 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.
8. Verify the new hosted domain information then click Finish to create the domain.

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.

1. Edit /opt/sun/comms/iwc/config/httpbind.conf with your preferred editor
2. 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:

   default.domains=comms.beta.com hosted.domain.com
   

3. Restart Application Server.

   cd /opt/sun/appserver/bin
   ./asadmin stop-domain domain1
   ./asadmin start-domain domain1
   

4. Type the master password when prompted: adminpass

Add new users to new hosted domain

Refer to the Creating Additional User Accounts and Groups 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.

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:

[root@comms sbin]# df -k /dev/shm
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   387596    121488    266108  32% /dev/shm

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

1. Relocate the mboxlist temporary database files to the temporary file-system.

   cd /opt/sun/comms/messaging/bin
   ./configutil -o store.dbtmpdir -v /dev/shm/msg-demo/
   

2. Restart Messaging Server

   cd /opt/sun/comms/messaging/bin
   ./stop-msg
   ./start-msg
   

Directory Server
Relocate the directory server temporary database files to the temporary file-system.

1. Stop directory server

   cd /var/opt/sun/directory/dsins1/
   ./stop-slapd
   

2. Edit /var/opt/sun/directory/dsins1/config/dse.ldif

   replace:
   nsslapd-db-home-directory: /var/opt/sun/directory/dsins1/db
   
   with:
   nsslapd-db-home-directory: /dev/shm/slapd-demo/
   

3. Start Directory Server

   cd /var/opt/sun/directory/dsins1/
   ./start-slapd
   

Instant Messaging Server
Relocate the Instant Messaging server temporary "scratch" files to the temporary file-system.

1. Stop the Instant Messaging Server

   cd /opt/sun/comms/im/sbin
   ./imadmin stop
   

2. Edit /opt/sun/comms/im/config/iim.conf and add the following line:

   iim_server.scratch_directory = "/dev/shm/iim-demo/"
   

3. Start the Instant Messaging Server

   cd /opt/sun/comms/im/sbin
   ./imadmin start
   

Known Issues and Limitations

For more information about known issues, see Communications Suite 7 Release Notes.