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

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

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 6 Update 1 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 1
• Sun Java System Calendar Server 6.3 + Patches
• Sun Java System Instant Messaging 8
• Sun Java System Directory Server 6.3
• Sun Java System Application Server 9.1 Update 2
• Sun Java System Delegated Administrator 6.4 + Patches
• Sun Java System Communications Express 6.3 + Patches
• Sun Convergence 1 Update 1
• 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 Although it is technically possible to install and configure Communications Suite 6 Update 1 and dependent products on Red Hat Enterprise Linux 5, this is not currently a supported configuration. A list of known issues with installing Communications Suite 6 Update 1 onto Red Hat Enterprise Linux 5 are documented here: Red Hat Linux 5 with Communications Suite 6 Update 1.

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 for Messaging Server and Calendar 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. Installing and configuring Directory Server 6.3
3. Installing and configuring Application Server 9.1 Update 2
4. Running the Java ES installer to install Access Manager 7.1
5. Deploying and enabling the Directory Server Control Center
6. Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator, Convergence, and Communications Express
7. Configuring Delegated Administrator and Communications CLI
8. Configuring Messaging Server
9. Configuring Calendar Server
10. Configuring Communications Express
11. Configuring Instant Messaging
12. Configuring Convergence

These installation steps result in a suitable deployment to evaluate and test Communications Suite 6 Update 1. 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.
• The computer must have 2.1 GB free disk space for the zip files and zip image. Recommendation: Have the image already unzipped.

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 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 Verify Correct Java Development Kit (JDK) Version

The Java Enterprise 5 update 1 (JES5u1) installer is not able to successfully deploy Access Manager 7.1 if Java Development Kit (JDK) 1.6 or above is installed. The following command can be used to verify the currently installed release.

In a terminal window, as root run the following command.

rpm -qa jdk

Note A default installation of Red Hat Enterprise Linux 3 or 4 will return no output to this command.

If the output of the command is jdk-1.6.<version>, the JDK version will need to be downgraded prior to deploying Access Manager 7.1.

This can be achieved by downloading and installing JDK 5.0 Update 16 from the following URL:

http://java.sun.com/products/archive/j2se/5.0_16/index.html

Getting the Necessary Software

To Get the Software

1. Get the Communications Suite, Application Server, Access Manager (Sun Java Enterprise System 5 Update 1) and Directory Server.

Installing and Configuring Directory Server 6.3

To Install the Zip Version of Directory Server 6.3

1. Move the downloaded Directory Server 6.3 zip file DSEE.6.3.Linux-X86-full.tar.gz to a temporary location, such as /tmp/DSEE63.
2. Unzip the file.

   gunzip -dc DSEE.6.3.Linux-X86-full.tar.gz | tar xf -
   

3. Change to the DSEE_ZIP_Distribution directory.
4. Deploy the DSEE software to the /opt/sun/directory directory.

   ./dsee_deploy install -i /opt/sun/directory
   

5. When prompted, press Enter to continue.
6. Accept the License Agreement by typing yes when prompted.
7. 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
   

8. When prompted, type adminpass for the Directory Manager password.
9. 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"
   

10. When prompted, type y to accept the certificate.
11. When prompted, type adminpass for the Directory Manager password.
12. Continue with the next section.

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.

1. Move the downloaded Application Server Update 2 installer sjsas_ee-9_1_02-linux.bin to a temporary location, such as /tmp/APPSVR91U2.
2. Launch the installer.

   cd /tmp/APPSVR91U2
   chmod +x sjsas_ee-9_1_02-linux.bin
   ./sjsas_ee-9_1_02-linux.bin -console
   

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	[Install Java 2 SDK (5.0]	accept default
   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. Log in to Application Server and perform the following to save from having to type the admin user and password in the future. (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.

Installing and Configuring Access Manager 7.1

Access Manager 7.1 is included in Java ES 5.1 Update 1. Although the Java ES 5.1 Update 1 bundle also includes Directory Server and Application server, the versions provided are not as up-to-date as the versions installed in the previous steps.

1. Move the downloaded Java ES 5.1 Update 1 software (java_es-5u1-ga-linux-x86.zip) to a temporary location, such as /tmp/JES5U1.
2. Unzip the file in this directory, then launch the Java ES installer.

   cd Linux_x86
   ./installer -nodisplay
   

3. Press Enter at the Welcome page and Software License Agreement
4. Accept the licence when prompted.
5. Select: No to installing the full set of products and services.
6. Select only the following products and sub-products:
   • Access Manager 7.1
     • Access Manager Core Services
     • Access Manager Administration Console
     • Access Manager Common Domain Services
     • Access Manager SDK
   • Install Multi-lingual packages

     Note When selecting Access Manager 7.1, Directory Server 6.2 is auto-selected as a dependant component, along with the Directory Preparation Tool. This deployment example uses Directory Server 6.3, which was earlier. Thus, you can deselect Directory Server 6.2 and the Directory Preparation Tool.

7. Choose web container for Access Manager 7.1.
   Select: A compatible web container previously installed on this system.
8. Choose directory server (Directory Server)
   Select: Use Directory Server Enterprise Edition 6.2 installed on remote machine.
9. Specify Installation Directories
   Access Manager: /opt/sun
10. After the Verify System Requirements process completes, select Next/continue.
11. Select the Configure Now option.
12. Continue with the next procedure to choose Common and Web Server settings.

To Select Common Settings
Use the following table to respond to the Common Server configuration options.
Table 7 Common and Web Server Settings

To Select Access Manager Settings
Use the following table to respond to the Access Manager configuration options.
Table 8 Access Manager Settings

To Install the Identity Suite Software

1. Select Install when you are satisfied with the Ready to Install list.
   When installation is complete, the Installation Complete page is displayed.
2. Select close or ! to exit the installer.

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.
12. Restart Application Server:

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

13. When prompted, type the master password: adminpass
14. Start the DSCC registry:

    /opt/sun/directory/ds6/bin/dsadm start /opt/sun/directory/var/dscc6/dcc/ads
    

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 Server tab.
4. Select Register Existing Directory 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.

To Verify the Installation

1. Verify that you can log in to the Access Manager console as amadmin. The URL for the Access Manager console is:
   http://fully-qualified-hostname:web-server-port/amconsole
   In this example, type:
   http://wireless.comms.beta.com:8080/amconsole
   Use amadmin and adminpass as the user ID and password.
2. After verifying that you can log in to the Access Manager console, log out.
3. Verify the Application Server by typing the following URL:
   http://fully-qualified-hostname
   In this example, type:
   http://demo.comms.beta.com:80/amconsole
4. Use amadmin and adminpass as the user ID and password.
5. After verifying that you can log in to the Access Manager console, log out.
6. Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.

Installing Communications Suite Components

Deploying Communications Suite components is a two-step process. You first install the software then you configure the individual servers.

To Install the Communications Suite Software

This section describes how to install the Communications Suite software on your host.

1. Create the /tmp/JCS6U1 directory, move the Communication Suite 6 update 1 software (SunJava_CommsInstaller_Suite6u1_linux-x86.zip) to this directory and extract the files.

   cd /tmp/JCS6U1
   unzip SunJava_CommsInstaller_Suite6u1_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.

1. Accept the License Agreement by typing yes when prompted.
2. Accept the default Install location: /opt/sun/comms
3. Select the components you wish to install.

   Select the following products:
   
   1.     Messaging Server 7u1 (7.0-3.01)
   2.     Comms DSsetup 6.4 (6.4-3.01)
   3.     Comms Delegated Administrator 6.4 (6.4-3.01)
   4.     Calendar Server 6.3 (6.3-11.01)
   5.     Instant Messaging 8 (8.0-00.06)
   6.     Communications Express 6.3 (6.3-11.01)
   7.     Convergence 1u1 (1.0-4.01)
   

   This corresponds to selections 1, 2, 3, 4, 5, 6 and 7.

4. The installation script prompts for a series of options.
   You might not be prompted for all options, depending on your operating system configuration and previously
5. 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]	accept default

6. Press Return when prompted to continue.
   The installation proceeds.
7. Press Return when prompted to continue.
8. Continue with the next section.

Configuring 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 Directory

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	[/var/opt/sun/directory]	accept default
   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?	[2]	accept default
   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 Next/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:
   AM Hostname	[demo.comms.beta.com]	accept default
   AM 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
   Access Manager Base Directory	[/opt/sun/identity]	accept default
   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
   AM Top level admin	[amadmin]	accept default
   AM admin passwd	-	adminpass
   Access Manager Internal LDAP Auth Username	[amldapuser]	accept default
   AM Internal LDAP Auth Passwd for amldapuser	-	nonadminpass
   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
   Preferred Mailhost for Sample	[demo.comms.beta.com]	accept default

5. Select Configure Now.
   The script begins to run.
6. 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.
7. Select Close/Done to exit the Delegated Administrator Configuration wizard.
8. Restart the Application Server

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

9. Type the master password when prompted: adminpass
10. Modify the mail and calendar domains, and create a test user account (jdoe) by using the commadmin utility:

    cd /opt/sun/comms/da/bin/
    ./commadmin domain modify -D admin -w adminpass -X demo.comms.beta.com -n comms.beta.com \
    -p 80 -d comms.beta.com -S mail,cal -H demo.comms.beta.com
    ./commadmin user create -D admin -F John -l jdoe -L Doe -n comms.beta.com -p 80 \
    -w adminpass -W demo -X demo.comms.beta.com -S mail,cal -E jdoe@comms.beta.com \
    -H demo.comms.beta.com
    

    You can create as many users as you like at this point. Steps later in this document show how to add Presence and Instant Messaging services to those users.

11. 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 Delegated Administrator, 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/sbin
   ./configure -nodisplay
   

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

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

4. Select Configure Now.
5. When configuration is finished, Select Next/Done to continue and exit the configuration utility
6. Enable Communications Express (UWC) access to webmail server

   cd /opt/sun/comms/messaging/sbin
   ./configutil -o local.webmail.sso.uwcenabled -v 1
   ./configutil -o service.imap.maxsessions -v 1000
   

7. Start Messaging Server.

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

8. 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
   Enable Virtual Domains support	[yes]	accept default
   Virtual Domains settings: Default domain	[comms.beta.com]	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	[Yes]	accept default
   Create calmaster@aus.sun.com account	[Create it]	accept default
   Setup a Front End/Back End deployment	[no]	accept default
   Email Alarms	[Enabled]	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	[no]	accept default
   Start Calendar Server on system startup	[yes]	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	[yes]	accept default
   Archive Directory	[/var/opt/sun/comms/calendar/calendar/csdb/archive]	accept default
   Keep archives for (in days)	[Minium: 3, Maximum: 6]	accept default
   Enable Hot Backup	[yes]	accept default
   Hot Backup Directory	[/var/opt/sun/comms/calendar/calendar/csdb/hotbackup]	accept default
   Keep hot backups for (in days)	[Minium: 3, Maximum: 6]	accept default

4. Select Configure Now to configure Calendar Server.
5. Select Next/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
   ./stop-cal
   ./start-cal
   

9. Continue with the next section to configure Communications Express.

Configuring Communications Express

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

   cd /opt/sun/comms/ce/uwc/sbin
   ./config-uwc -nodisplay
   

2. Select Next/Enter at the Welcome page.
3. 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 Accept Directory to create the directory.
4. 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	[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
   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]	accept default
   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

5. Select Configure Now to configure Communications Express (UWC).
6. Select Next/Done when the configuration is complete and close the configurator.
7. Restart the Application Server

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

8. Type the master password when prompted: adminpass

To Log in to Communications Express

1. 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:
   http://demo.comms.beta.com:80/uwc
2. Log in using jdoe and demo as the user ID and password.
3. After verifying that you can access Communications Express, log out.
4. Continue with the next section to configure Instant Messaging.

Configuring Instant Messaging

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

To Configure Instant Messaging

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

   cd /opt/sun/comms/im/sbin
   ./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	[yes]	accept default
   User ID	[inetuser]	root
   Group ID	[inetgroup]	root
   Runtime Directory	[/var/opt/sun/im]	accept default
   Run with super-user permissions?	[Choose New]	accept
   Domain Name	[comms.beta.com]	accept default
   XMPP Port	[5222]	accept default
   Multiplexed XMPP Port	[45222]	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:4849/]	https://demo.comms.beta.com:4848/
   Web Administrator User Id	[admin]	accept default
   Web Administrator Password	-	adminpass
   Deploy IM HTTP Gateway	[yes]	no
   Context Root	[http://demo.comms.beta.com:8080/httpbind]	-
   Web Administration URL	[http://demos.comms.beta.com:4848/]	-
   Web Administrator User Id	[admin]	-
   Web Administrator Password	-	-
   Deploy IM IMPS Gateway	[yes]	no
   Context Root	[http://demo.comms.beta.com:80/imps]	-
   Webcontainer Path	[/opt/sun/appserver]	-
   Web Administration URL	[https://demo.comms.beta.com:4848/]	-
   Web Administrator User Id	[admin]	-
   Web Administrator Password	-	-
   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]	accept default
   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
   Start Services After Successful Configuration	[yes]	no
   Start Services When System starts	[yes]	no

5. At the Configuration Summary page, select Close/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:

   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"
   

7. Start the Instant Messaging server.

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

8. Continue with the next procedure.

To Grant IM Services for All Users in a Given Domain

You can also configure the Instant Messaging and Presence services for all users in a given domain at once by using the imadmin assign_services command, instead of manually adding the services in the Access Manager console or automatically adding the services upon user creation.

1. Run the following commands to add Instant Messaging and Presence services for all users in a given domain:

   cd /opt/sun/comms/im/sbin
   ./imadmin assign_services
   Please enter base DN: o=comms.beta.com,o=isp
   Done.
   

2. Restart the Application Server.

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

3. Type the master password when prompted: adminpass
4. Continue with the next procedure.

To Add Services to the Lower Level Organization

If you set your Organization DN to o=comms.beta.com,o=isp, you need to add Instant Messaging and Presence services to the comms.beta.com organization and configure the organization to use LDAP authentication.

1. In your web browser, open a URL for the Access Manager console and log in as amadmin. The URL for the Access Manager console is:
   http://fully-qualified-hostname:port/amconsole
   In this example, type:
   http://demo.comms.beta.com:80/amconsole
2. Log in using the user amadmin and the password adminpass.
3. Upon logging into the Access Manager Console, you see a view of all your organizations, including the comms.beta.com organization. Click the comms.beta.com link in the left pane.
   In the right pane, you see a list of General Properties.
4. Choose Services from the View menu in the left pane.
5. Click the Add button if you do not see the Instant Messaging Service and Presence Service listed in the left pane Services listing.
   • If you clicked the Add button you should see the Instant Messaging Service and Presence Service services listed in the right-pane.
   • Select these two services and click the OK button to add them.
6. Within this same comms.beta.com suborganization, click the triangle shaped properties icon next to the name of Authentication Configuration in the left pane.
   Normally, the service instance ldapService will exist and show in the right-pane. If a service instance (such as ldapService) does not exist, you will need to create one. To do so, perform the following steps. Skip these steps if the ldapService instance already exists.
   • Click the New button to define a new service instance.
   • Type the Instance Name ldap1, then click the Submit button to create the ldap1 service instance.
   • Click the ldap1 link.
   • Click the Edit link besides Authentication Configuration. A new window appears.
   • Click the Add button to add the LDAP module of this new ldap1 instance and select the LDAP Module Name from the pulldown menu.
   • The Enforcement Criteria should be REQUIRED.
   • Click OK to add the module, then click OK again to save the module properties.
   • Then click Cancel to close the window.
7. Click the triangle shaped properties icon next to Core, just below Authentication Modules in the left pane.
8. You need to select the existing ldap service instance ldapService or the newly created ldap1 service for both Administrator Authentication Configuration and Organization Authentication Configuration settings in the right pane.
9. Click Save.
10. Choose Users from the View menu in the left pane.
    A list of users is presented. You need to add the services you just registered in this suborganization to each user.
11. Click the triangle shaped property icon beside a user in the user listing in the left pane.
12. In the right pane, open the View drop-down menu and choose Services.
13. If no services are listed, click the Add button.
    A list of services appears.
14. Click the double-checked box at the top of the list of services to add all services. Then click the OK button.

    Note The minimum services that you need to add to each user are the Instant Messaging and Presence services. The Authentication Configuration service does not need to be added to each user but must be configured in each subdomain.

15. Log out of the Access Manager interface.
16. Continue with the next procedure.

To Log into Instant Messaging Java Client

1. In your web browser, open a URL for the Instant Messaging Java Client. The URL for the Instant Messaging Java Client is:
   http://fully-qualified-hostname:app-server-port/im/
   In this example, type:
   http://demo.comms.beta.com:80/im
2. Click the Start button to launch the Instant Messaging client.
3. Log in using jdoe and demo as the user ID and password.
4. After verifying that you can access the Instant Messaging client, close the client by selecting Exit from the File menu.
5. Continue with the next section to configure the Sun Convergence web interface.

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	[no]	yes
   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
   Access in SSL mode	[no]	accept default
   Webmail Admin User ID	[admin]	accept default
   Admin Password	-	adminpass
   Calendar Server Host Name	[demo.comms.beta.com]	accept default
   Calendar Server Port	[80]	3080
   Access in SSL mode	[no]	accept default
   Administrator User ID	[calmaster]	accept default
   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	[5222]	5269
   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 Configure Now to configure Sun Convergence.
   The system displays a message to remind you to restart the Application Server Instance.
7. Once the configuration is completed, exit the configuration tool.
8. Restart Application Server.

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

9. Type the master password when prompted: adminpass
10. 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 group (Demostaff@comms.beta.com) consisting of the newly created users.

cd /opt/sun/comms/da/bin
./commadmin user create -D admin -F Demo -l demo1 -L One -n comms.beta.com -p 80 -w adminpass \
-W demo -X demo.comms.beta.com -S mail,cal -E demo1@comms.beta.com -H demo.comms.beta.com
./commadmin user create -D admin -F Demo -l demo2 -L Two -n comms.beta.com -p 80 -w adminpass \
-W demo -X demo.comms.beta.com -S mail,cal -E demo2@comms.beta.com -H demo.comms.beta.com
./commadmin group create -D admin -G Demostaff -n comms.beta.com -p 80 -w adminpass \
-X demo.comms.beta.com -S mail -E Demostaff@comms.beta.com -H demo.comms.beta.com \
-o jdoe -m demo1 -m demo2

Note Creating groups using the Delegated Administrator command-line interface will guarantee that these groups will be recognized by Access Manager as LDAP groups that can be searched on using Instant Messenger. They can also be used to send email to the entire group.

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 to 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 earth and mars choices are appropriate for this example, since they have mail and calendar services enabled. Each service package has a different mail quota.
   • 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.
   • 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 in step 1 earlier), for example, mars, then click Next.
   • Type the email address, for example, demo5@comms.beta.com. The Mail Delivery Option should be Local Inbox. Leave the remaining fields blank then click Next.
   • Choose your calendar preferences, select your preferred timezone, then 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.
4. Log in to Access Manager as amadmin and verify that the Instant Messaging and Presence services have been added to the newly created user. If not, you will need to assign services to those users as explained in Add Services to the Lower Level Organization

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.

Communication Suite 6 Start and Stop Scripts (Linux)

Known Issues and Limitations

• LDAP instances are not inherited from the top level organization to the suborganization.

• 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:

if [ $OSNAME = Linux ]; then
  /sbin/ldconfig $SERVERROOT/lib
fi

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