Sun Java Communications Suite 6 Update 2 on a Single Host

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

This deployment example describes how to install Sun Java Communications Suite 6 Update 2 software on one computer for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.
{info:title=Note}Installing the back-end messaging, calendar, 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 better if you install services on separate machines.{info}

{toc:minLevel=2|maxLevel=2}

h2. About This Deployment Example

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

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

h3. Installation Overview

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

h4. What Components Are Installed?

This example guides you through installing the following Communications Suite and Java Enterprise System components:

* Sun Java System Messaging Server 7.0 Update 2
* Sun Java System Calendar Server 6.3.1
* Sun Java System Instant Messaging 8 Update 1
* Sun Java System Directory Server 6.3
* Sun Java System Access Manager 7.1
* Sun Java System Application Server 9.1 Update 2 with HADB support
* Sun Java System Web Server 7.0 Update 1
* Sun Java System Delegated Administrator 7
* Sun Java System Communications Express 6.3
* Sun Convergence 1 Update 2
* All Shared Components

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

* Domain name: {{comms.beta.com}}
* Host name: {{wireless}} (running Solaris OS 10)
* Fully qualified (external) host name: {{wireless.comms.beta.com}}
* Password: {{adminpass}} used for all passwords except the {{amldapuser}} password

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

h4. Recommended Ports

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

h3. Implementation Specifications for This Example

This section describes implementation specifications for this example.

*Table 1 Evaluation Host Hardware and Software Requirements*
|| Component || Platform Requirement ||
| CPU | SPARC |
| RAM | 2 Gbytes or more |
| Disk Space | 2.2 Gbytes or more free disk space for installed software. 2.1 Gbytes additional disk space may be needed for temporary storage of Communications Suite zip files. |
| Software | Solaris 10 OS Update 6. Note: Communications Suite is supported on both Solaris OS 9 and 10. Java Enterprise System software is also supported on Solaris OS 9 and 10. This example uses an installation based on Solaris OS 10 Update 6. |
| Users | Provisioned with test users. |

*Table 2 Client Software Requirements*
|| Component || Platform Requirement ||
| Browser | Firefox 2.0.0.11 or later, Internet Explorer 7.x or later |

{anchor:Table3}

*Table 3 Server Configuration Information*
|| Component || Install Notes || Install Location || Database Location || Port Name || Port Number ||
| Application Server 9.1 Update 2 with HADB support | Installed separately. Required for Convergence | /opt/SUNWappserver | Not Applicable | HTTP Port | 80 |
| | | | | Admin Port | 4848 |
| | | | | HTTPS Port | 8181 |
| Directory Server 6.3 | Installed separately. This version is not included with Identity Management Suite. | /opt/SUNWdsee | /var/opt/SUNWdsee | Directory Server Port | 389 |
| | | | | LDAP Port | 389 |
| | | | | SSL Port | 636 |
| Messaging Server 7.0 Update2 | Installed by using Communications Installer. Additional configuration required. | /opt/sun/comms/messaging64 | /var/opt/sun/comms/messaging64 | Webmail Port (HTTP) | 2080 |
| | | | | SMTP Port | 25 |
| | | | | POP Port | 110 |
| | | | | IMAP Port | 143 |
| Web Server 7.0 Update 1\\ | Installed with Java ES 5 Update 1 or Identity Management Suite. Required for Access Manager and Delegated Administrator | /opt/SUNWwbsvr7 | /var/opt/SUNWwbsvr7 | Web Port | 8080 |
| | | | | Admin Port | 8800 |
| | | | | SSL Admin Port | 8989 |
| Calendar Server 6.3.1 | Installed using Communications Installer. Additional configuration required. | /opt/sun/comms/calendar | /opt/sun/comms/calendar | Calendar Server Port | 3080 |
| | | | | LDAP Port | 389 |
| Instant Messaging 8 Update 1\\ | Installed by using Communications Installer. Additional configuration required. | /opt/sun/comms/im | /var/opt/SUNWiim | XMPP Port | 5222 |
| | | | | Multiplexed XMPP Port | 45222 |
| | | | | Admin Port | 8989 |
| | | | | XMPP Server Port \\ | 5269 |
| Communications Express 6.3 | Installed by using Communications Installer. Additional configuration required. | /opt/sun/comms/ce | /var/opt/sun/comms/ce | Port | 8080 |
| Convergence 1 Update 2\\ | Installed by using Communications Installer. Additional configuration required. | /opt/sun/comms/iwc\\ | /var/opt/sun/comms/iwc\\ | Server Instance HTTP Port\\ | 80\\ |
| | | | | Administration Server Port\\ | 4848\\ |

h3. Installation Time Estimates

The following table provides time estimates for installing this example.

*Table 4 Installation Time Estimates*
|| Activity || Estimate ||
| Install Solaris OS | 2 hours |
| Install Communications Suite and Java ES software | 1 hours |
| Configure software | 2 hours |
| Total | 5 hours (average) |

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

h3. Installation Notes and Recommendations

# With Solaris OS 9 and 10, ftp might not work for certain accounts.

These accounts are listed in {{/etc/ftpd/ftpusers}}. Just remove the account from this list (for example, {{root}}) and you will be able to ftp as that user.
# Use {{gzip \-d}} or {{gunzip}} to decompress the {{\*gz}} files.

*Expected User Input*

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

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

h3. Summary of Installation and Configuration

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

# Preparing the system for Sun Java Communications Suite
# Installing and configuring Application Server 9.1
# Installing and configuring Directory Server 6.3
# Running the Identity Suite installer and selecting the necessary components required by the Java Communications Suite (Web Server and Access Manager)
# Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Communications Express, and Delegated Administrator
# Configuring Delegated Administrator and Communications CLI
# Configuring Messaging Server
# Configuring Calendar Server
# Configuring Instant Messaging
# Installing and Configuring Convergence
# Configuring Communications Express
# Configuring a user

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

h2. Installing the Example

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

h3. Checking Installation Requirements

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

*To Check System Requirements*

The computer should meet the following requirements:

* These instructions assume all actions are performed by the {{root}} user.
* 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:

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

h3. Getting the Necessary Software

*To Get the Software*
# [Get the Communications Suite, Application Server, and Identity Suite software|Get the Software].

h3. Installing and Configuring Application Server, Directory Server, Access Manager, and Web Server

Sun Java System Application Server 9.1 Update 2 is the primary web container used by Convergence. At the time this document was initially written, Application Server did not support Access Manager, so the recommendation was to install a separate Web Server to support Access Manager. Things have changed since then. If you want to install Convergence and Access Manager in the same web container, you must install the Application Server with HADB support (even though you do not need to enable HADB). Convergence and Access Manager do not need to be installed in the same web container, but if you want SSO to exist between Convergence and another application, you must install either Access Manager or the Access Manager SDK in the same web container as Convergence. This installation example has no need to provide SSO between Convergence and another application. Hence, it uses separate web containers for Access Manager and Convergence.

# Prior to installing Application Server 9.1 Update 2, check the Java version on the system. Application Server requires at least Java 1.5.0. Solaris 10 Update 6 ships with version 1.5.0_16, which is fine for Convergence. To check your version type the following command:
{noformat:nopanel=true}
# java -version
{noformat}
The shell returns results that look similar to the following:
{noformat:nopanel=true}
java version "1.5.0_16"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_16-b02)
Java HotSpot(TM) Client VM (build 1.5.0_16-b02, mixed mode, sharing)
{noformat}
# Create the {{/tmp/APPSVR91U2}} directory, copy the Application Server 9.1 Update 2 bits to this directory, then launch the installer.
{noformat:nopanel=true}
# cd /tmp/APPSVR91U2
# chmod +x *
# ./sjsas_ee-9_1_02-solaris-sparc.bin -console
{noformat}
# When prompted, press Enter to continue.
# Accept the License Agreement by typing *yes* when prompted.
The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 6 Application Server Settings*
|| Option || \[Default Value\] || Enter: ||
| Installation Directory | \[/opt/SUNWappserver\] | _accept default_ |
| Create Directory or Choose New | Create Directory | _accept default_ |
| Install Node Agent | \[yes\] | *no* |
| 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\] | _accept default_ |
| Install or reuse Java 2 SDK | \[Install\] | *Reuse* (as long as correct version) |
| Path to Java 2 SDK 5.0 or greater | \[/usr/jdk/instances/jdk1.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\] | _accept default_ |
| Enable Updatecenter client | \[yes\] | _accept default_ |
| Upgrade from previous AS version | \[no\] | _accept default_ |
# Start the Application Server:
{noformat:nopanel=true}
# /opt/SUNWappserver/bin/asadmin start-domain domain1
Starting Domain domain1, please wait.
Log redirected to /opt/SUNWappserver/domains/domain1/logs/server.log.
Please enter the admin user name>admin
Please enter the admin password>adminpass
Please enter the master password>adminpass
{noformat}
{info:title=Note}
Directory Server 6.3 is the preferred version since the previous version (shipped with the Identity Suite 5 Update 1) had issues that could potentially cause database integrity problems. For evaluations, you could use the Directory Server 6.2 version shipped with the Identity Suite. However, this example illustrates how to install and configure Directory Server 6.3 in lieu of Directory Server 6.2.
{info}
# Create the {{/tmp/DS}} directory and copy the Directory Server 6.3 bits to this directory. Uncompress them and then run the installer.
{noformat:nopanel=true}
# mkdir /tmp/DS
# cp DSEE.6.3.Solaris-Sparc-full.tar.gz /tmp/DS
# cd /tmp/DS
# gzip -dc DSEE.6.3.Solaris-Sparc-full.tar.gz | tar xvf -
# cd DSEE_ZIP_Distribution
# ./dsee_deploy install -i /opt/SUNWdsee
{noformat}
# Press Enter to Continue when prompted.
# Accept the License Agreement by typing {{{*}yes{*}}} when prompted.
The installation proceeds and installs the Directory Server bits in the specified location {{/opt/SUNWdsee}}.
# Create your Directory Server instance.
{noformat:nopanel=true}
# mkdir /var/opt/SUNWdsee
# cd /opt/SUNWdsee/ds6/bin
# ./dsadm create -p 389 -P 636 /var/opt/SUNWdsee/dsins1
{noformat}
# Choose the Directory Manager password: {{{*}adminpass{*}}}
# Confirm the Directory Manager password: {{{*}adminpass{*}}}
# Start your Directory Server instance.
{noformat:nopanel=true}
# ./dsadm start /var/opt/SUNWdsee/dsins1
{noformat}
# Create the root suffix {{o=isp}} by using the {{dsconf}} command:
{{./dsconf create-suffix \-h}} _hostname_ {{\-p 389 o=isp{}}}In this example, type:
{noformat:nopanel=true}
# ./dsconf create-suffix -h wireless -p 389 o=isp
Certificate "CN=wireless, CN=636, CN=Directory Server, O=Sun Microsystems" presented by the server is not trusted.
{noformat}
# Accept the Certificate and type {{{*}adminpass{*}}} as the {{cn=Directory Manager}} password.
{noformat:nopanel=true}
Type "Y" to accept, "y" to accept just once, "n" to refuse, "d" for more : Y
Enter "cn=Directory Manager" password: adminpass
{noformat}
# Create the {{/tmp/JIS5}} directory and unzip Identity Suite bits in this directory. Then run the Java ES installer.
{info:title=Note}
This example uses Identity Suite 5 Update 1 to install only Access Manager and a Web Container, which are required components for Communications Suite. Download Identity Suite instead of the entire Java Enterprise System Suite to save on size. However, if you already have Java Enterprise System 5 Update 1, you can use that as well. The steps may differ slightly from those provided below.
{info}
{noformat:nopanel=true}
# cd java_es-5u1-identsuite
# cd Solaris_sparc
# ./installer &
{noformat}
# Click Next at the Welcome page.
# Accept the license.
{info:title=Note}
Earlier Solaris OS 10 versions install an earlier version of Message Queue (and possibly other software). You might need to upgrade this product prior to installing Identity Suite software. If the Java ES installer detects that your system has an earlier version of a product, it might display an option to Upgrade Existing Software. If you are presented with this option, continue with step 18 below. If you are not presented with this option, skip to step 29. If you are presented with the upgrade option, select the item to be upgraded and run the Java ES installer to upgrade the component. After the installer upgrades the component (or components), you can quit the installer then restart it to install the remaining Identity Suite components. Then repeat the the applicable previous steps.
{info}
If you happen to be installing Identity Suite on Solaris OS 9, you can skip steps 18-28 and immediately proceed to step 29.
# Click the Upgrade existing software radio button and click Next to continue.
# Select the following products, then click Next.
#* Sun Java System Message Queue 3.7 UR1
#* All Shared Components
#* Note: Also select the checkbox for multilingual packages if desired.
# Click Next to upgrade shared components.
# The installer verifies system requirements. When done, click Next.
# At the "Ready to Upgrade" window, click Next.
# Deselect the registration checkbox, then click Install.
The upgrade proceeds. When the installation is complete, the Installation Complete page is displayed.
# Click Close to exit the installer.
# Restart the Java ES installer to install the remaining Identity Suite components.
{noformat:nopanel=true}
# ./installer &
{noformat}
# Click Next at the Welcome page.
# Accept the license.
# In the "Choose to Upgrade or Install" window, select the "Install new software" radio button, then click Next to continue.
# Select the following products, then click Next.
#* Web Server 7.0 Update 1
#* Access Manager 7.1 (Choose only the required software. You do not need the Client SDK, Distributed Auth UI, or Session Failover client.)
#* All Shared Components
#* Note: Directory Server might be selected by default. You must deselect this product since Directory Server 6.3 has already been installed. As a result, Directory Preparation Tool 6.4 is automatically deselected as well.
#* Note: Select the checkbox for multilingual packages if desired.
# In the dependency checking phase, it is noted that Access Manager requires Directory Server. You will be prompted to install Directory Server Enterprise Edition 6.2 locally or use Directory Server Enterprise Edition 6.2 installed on a remote machine. You must choose the Remote option since you do not want to overwrite your existing version of Directory Server.
# Some versions of Solaris require that the Java SE SDK be upgraded prior to installation. If you are prompted to upgrade the Java SE SDK, choose the default selection to automatically upgrade the SDK to the version included with the installer. Then click Next to continue.
# If you skipped several previous steps because you installed Solaris OS 9 or a component upgrade was not required on Solaris OS 10, you are required to upgrade the shared components now and you can click Next. If you installed Solaris OS 10 and you already upgraded the shared components when you upgraded the Message Queue component, you should have already completed this step and you can proceed to the next step.
# Specify Installation Directories.
Locations:
Access Manager: {{/opt}} (creates {{/opt/SUNWam}})
Web Server: {{/opt}} (creates {{/opt/SUNWwbsvr7}})
Web Server Instance: {{/var/opt/SUNWwbsvr7}}
# Accept the target directories for each product and click Next.
# The installer verifies system requirements. When done, click Next.
# Choose Configure Now, then click Next.
# Continue with the next procedure to choose Common and Web Server settings.

*To Select Common and Web Server Settings*

This installation assumes the use of Sun Java System Web Server. You can choose an alternate web container but that is beyond the scope of this document.

# In the Account Preferences Panel, you are asked whether or not you want to use your UserID and Password information for all administrator accounts, or if you want to provide administrator account information for each component.
Choose the All Administrator Accounts option and type admin for the Administrator User ID and adminpass for the Administrator Password then click Next.
# The installation script prompts for a series of options. The following table shows how to respond to the Common and Web Server configuration options.

*Table 7 Common and Web Server Settings*
|| Option || \[Default Value\] || Enter: ||
| *Common Server Settings* | | |
| Host Name | \[wireless\] | _accept default_ |
| DNS Domain Name | \[comms.beta.com\] | _accept default_ |
| Host IP Address | Machine IP address | *Verify correct address* |
| System User | \[root\] | _accept default_ |
| System Group | \[root\] | _accept default_ |
| *Web Server Settings* | | |
| Type of configuration | \[Configure Administration Instance as Server\] | _accept default_ |
| Start servers after system startup | unchecked | _accept default_ |
| Server Host | \[wireless.comms.beta.com\] | _accept default_ |
| Admin Server SSL port | \[8989\] | _accept default_ |
| Admin Server HTTP port | \[8800\] | _accept default_ |
| Admin runtime user id | \[root\] | _accept default_ |
| Web Server Name | \[wireless.comms.beta.com\] | _accept default_ |
| HTTP Port | \[81\] | *8080* |
| Web server runtime UNIX User ID | \[webservd\] | *root* (See Note below) |
| Document root directory | \[/var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/docs\] | _accept default_ |
{info:title=Note}
To take advantage of Instant Messaging with Access Manager, Instant Messaging must be run as {{root}}. If you want to make use of the new IMPS feature and the httpbind gateway in Instant Messaging, Web Server must have access to the Instant Messaging configuration files and log directory. You could either run Web Server as a separate user and then manually change the permissions in the Instant Messaging directories or you could run Web Server as the same user as the Instant Messaging user, which in this case is {{root}}. In the future, the Instant Messaging configurator should perform all the necessary permission changes so that you don't need to run Web Server as {{root}}.
{info}

*To Select Access Manager Settings*
* The following table shows how to respond to the Access Manager configuration options.

*Table 9 Access Manager Settings*
|| Option || \[Default Value\] || Enter: ||
| Install type | \[Legacy Mode\](version 6.x style) | _accept default_ |
| Admin User ID | \[amadmin\] | _accept default_ |
| Administrator Password | \- | *adminpass* |
| LDAP User ID | \[amldapuser\] | _accept default_ |
| LDAP Password | \- | *nonadminpass* |
| Password Encryption Key | \[87dfjkauefjkdafdadf...\] | _accept default_ |
| Access Manager Deployment Container Options | \[Sun Java System Web Server\] | *Choose Sun Java System Web Server* |
| Host Name | \[wireless.comms.beta.com\] | *wireless.comms.beta.com* |
| Services Deployment URI | \[amserver\] | _accept default_ |
| Common Domain Deployment URI | \[amcommon\] | _accept default_ |
| Cookie Domain | \[.beta.com\] | *.comms.beta.com* |
| Password Deployment URI | \[ampassword\] | _accept default_ |
| Console Protocol | \[HTTP\] | _accept default_ |
| Access Manager Console | \[Deploy new console\] | _accept default_ |
| Console Deployment URI | \[amconsole\] | _accept default_ |
| Console Host Name | \[wireless.comms.beta.com\] | _accept default_ |
| Console Port | \[8080\] | _accept default_ |
| Directory Server Host | \- | *wireless.comms.beta.com* |
| Directory Server Port | \[389\] | _accept default_ |
| Directory Root Suffix | \[dc=comms,dc=beta,dc=com\] | *o=isp* |
| Directory Manager DN | \[cn=Directory Manager\] | _accept default_ |
| Directory Manager Password | \- | *adminpass* |
| Directory Server provisioned with user data? | \[No\] | _accept default_ |

*To Install the Identity Suite Software*
# Click Install when you are satisfied with the Ready to Install list.
Because of the number of components selected, the installation process can be lengthy.
# When installation is complete, the Installation Complete page is displayed. Click Close to exit the installer.

*To Verify the Installation*

# Start Web Server:
{noformat:nopanel=true}
cd /var/opt/SUNWwbsvr7/admin-server/bin
./stopserv
./startserv
cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
./stopserv
./startserv
{noformat}
The Web Server can take a while to start.
# 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:{nolink}*[http://wireless.comms.beta.com:8080/amconsole]*{nolink}
Use {{amadmin}} and {{adminpass}} as the user ID and password.
# After verifying that you can log in to the Access Manager console, log out.
# Verify the Application Server by typing the following URL:
{{http://}}{_}fully-qualified-hostname{_}In this example, type:{nolink}*[http://wireless.comms.beta.com]*{nolink}
# Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.

h3. Uninstalling the Components

After you complete your evaluation, you can to remove the components that you installed:
* To uninstall Communications Suite 6 Update 2 components:
{noformat:nopanel=true}
./commpkg uninstall
{noformat}
* To uninstall Identity Suite:
{noformat:nopanel=true}
cd /var/sadm/prod/SUNWident-entsys5u1i/bin
./uninstall
{noformat}

{toc-zone}

h2. Installing Communications Suite Components

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

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

h3. Before You Begin

Before you configure the Communications Suite software, you need to create the {{mailsrv}} user and disable the {{sendmail}} process. The {{mailsrv}} user is used to configure Messaging Server.

* Messaging Server requires a mail server user, which must exist before you can finish the installation. You can skip this step, because the group and user are created during the configuration time. However, you might want to create the {{mailsrv}} user yourself as shown below. For this installation, use the {{useradd}} command to create a user with username {{mailsrv}} and group {{mail}}. You use this ID in Step 2 in the [Configuring Messaging Server|#Step2] section.

Type the following commands to create the user {{mailsrv}} with a user ID of {{7633}}, a group ID of {{mail}}, and a user home directory of {{/export/home/mailsrv}}. (These commands assume that the {{/export/home}} directory already exists.)
{noformat:nopanel=true}
groupadd mail
useradd -u 7633 -g mail -d /export/home/mailsrv -m mailsrv
{noformat}
Note: if the {{mailsrv}} user is already in use, this could be an indication that {{mailsrv}} is not a local user as required by the Messaging Server. Messaging Server requires a local user and group and not one defined in a naming service such as NIS. You should create a different user such as {{mailsrv2}} but be sure to change the reference to that user when prompted for the mail server username.
For example,
{noformat:nopanel=true}
# useradd -u 7633 -g mail -d /export/home/mailsrv2 -m mailsrv2
{noformat}

*To Disable sendmail*
* Prior to configuring Messaging Server, use the following procedures to kill the {{sendmail}} process and prevent it from starting during bootup.
For Solaris OS 10:
{noformat:nopanel=true}
svcadm disable sendmail
{noformat}
For Solaris OS 8 and 9:
{noformat:nopanel=true}
ps -ef | grep sendmail
kill -9 sendmail_pid
cd /etc/rc2.d
mv S88sendmail save.S88sendmail
{noformat}

h3. Installing Communications Suite 6 Update 2 Software

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

*To Install the Communications Suite Software*

# Create a {{/tmp/JCS6}} directory, unzip the Communications Suite 6 Update 2 software zip file in this directory, then run the Communications Suite 6 Update 2 Installer.
{noformat:nopanel=true}
# cd /tmp/JCS6
# ./commpkg install
{noformat}
# Press RETURN to continue when prompted
# Review the license and type *c* to continue when prompted.
You can also type *s* to skip the license display.
# Accept the License Agreement by typing *yes* when prompted.
# Accept the default Install location: {{/opt/sun/comms}}
# Select the components you wish to install.
Select the following products:
#* Messaging Server (64bit) 7u2 (7.2-7.02)
#* Comms DSsetup 6.4 (6.4-4.04)
#* Comms Delegated Administrator 7 (7.0-0.00)
#* Calendar Server 6.3 (6.3-15.01)
#* Instant Messaging 8u1 (8.1-01.03)
#* Communications Express 6.3 (6.3-13.01)
#* Convergence 1u2 (1.0-7.01)
This corresponds to selections 2, 3, 4, 5, 6, 7, and 11.
# The installation script prompts for a series of options. You might not be prompted for all options, depending on your system.
The following table shows how to respond to the configuration options:
*Table 10 Values for NSS, Java Help Runtime, Message Queue, and Service Tags Options*
|| Option || \[Default Value\] || Enter: ||
| Change pkg versions for NSS/NSPR/JSS | \[n\] | *y* |
| Change pkg versions for Service Tags | \[n\] | *y* |
| Change pkg versions for Message Queue | \[n\] | *y* |
# Press RETURN when prompted to continue.
# Installation Proceeds.
# Press RETURN when prompted to continue.
{toc-zone}

h2. Configuring Components

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

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

h3. Preparing the Directory

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

*To Apply Schema 2 to Your Directory Tree*
# Chance the directory where the {{comm_dssetup}} script is located and run the script, for example:
{noformat:nopanel=true}
cd /opt/sun/comms/dssetup/sbin
/usr/bin/perl comm_dssetup.pl
{noformat}
# Type *y* to continue.
The perl script prompts for a series of options. The following table shows how to respond to the prompts.
*Table 11 Values for comm_dssetup.pl Script*
|| Option || \[Default Value\] || Enter: ||
| Directory server root | \[/var/opt/SUNWdsee/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 |
# Confirm your choices and type *y* to continue.
The {{comm_dssetup}} proceeds.
# When prompted, type *y* to continue with the script.
Continue with the next step after {{comm_dssetup}} completes and the Successful Completion message is displayed.

h3. Configuring Delegated Administrator and Communications CLI

This section describes configuring Delegated Administrator console and utility, which provide user management.

*To Configure Delegated Administrator*
# Change to the directory where the configuration script was installed and run the script, for example:
{noformat:nopanel=true}
cd /opt/sun/comms/da/sbin
./config-commda
{noformat}
# Click Next in the Welcome window.
# Accept the default for the Directory to store Configuration and Data Files: {{/var/opt/sun/comms/da{}}}If the directory does not exist, click Create Directory to create the directory.
# Install Delegated Administrator Utility, Console, and Server.
The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 12 Values for config-commda Script*
|| Option || \[Default Value\] || Enter: ||
| DA Server Hostname | \[wireless.comms.beta.com\] | _accept default_ |
| DA Server Port\\ | \[8080\] | *8080* |
| Default Domain | \[comms.beta.com\] | _accept default_ |
| Default SSL Port | \[443\] | _accept default_ |
| Web Container | \[Web Server 6.x\] | *Web Server 7.x* |
| Install Root Directory (for DA Console) | \[/opt/SUNWwbsvr7\] | _accept default_ |
| Instance Root Directory | \[/var/opt/SUNWwbsvr7\] | _accept default_ |
| Server Instance Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| Virtual Server Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| Web Server HTTP Port | \[80\] | *8080* |
| Administration Server Port | \[8800\] | _accept default_ |
| Administrator User ID | \[admin\] | _accept default_ |
| Administrator Password | \- | *adminpass* |
| Secure Administration Server Instance? | \[unchecked\] | _accept default_ |
| Default Domain Separator | \[@\] | _accept default_ |
| Access Mode | Direct LDAP | *Access Manager* |
| Access Manager Base Directory | \[/opt/SUNWam\] | _accept default_ |
| Install Root Directory (for DA Server) | \[/opt/SUNWwbsvr7\] | _accept default_ |
| Instance Root Directory | \[/var/opt/SUNWwbsvr7\] | _accept default_ |
| Server Instance Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| Virtual Server Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| Web Server HTTP Port | \[80\] | *8080* |
| Administration Server Port | \[8800\] | _accept default_ |
| Administrator User ID | \[admin\] | _accept default_ |
| Administrator Password | \- | *adminpass* |
| Secure Administration Server Instance? | \[unchecked\] | _accept default_ |
| URL of Directory Server | \[ldap://wireless.comms.beta.com:389\] | _accept default_ |
| Bind As | \[cn=Directory Manager\] | _accept default_ |
| Password | \- | _adminpass_ |
| LDAP Username | \[daAdmin\] \\ | _accept default_ |
| LDAP 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\] | *o=comms.beta.com,o=isp* |
| Top Level Admin for Default Organization | \[admin\] | _accept default_ |
| Password | \- | *adminpass* |
| Load Sample Service Packages | \- | *Yes* (Checked) |
| Load Sample Organizations | \- | *Yes* (Checked) |
| Preferred Mailhost for Sample | \[wireless.comms.beta.com\] | _accept default_ |
# Click Configure Now.
The script begins to run.
# When the panel displays "All Tasks Passed," click Next to continue.
Two warnings appear: one reminds you to restart the Web Server; the other reminds you to enable the mail and calendar services in the domain. The next steps complete these steps.
# Click Close to exit the Delegated Administrator Configuration wizard.
# Restart the Web Server.
{noformat:nopanel=true}
cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
./stopserv
./startserv
{noformat}
# Modify the mail and calendar domains, and create users by using the {{commadmin}} utility:
{noformat:nopanel=true}
/opt/sun/comms/da/bin/commadmin domain modify -D admin -w adminpass -X wireless.comms.beta.com -n comms.beta.com -p 8080 -d comms.beta.com -S mail,cal -H wireless.comms.beta.com

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

/opt/sun/comms/da/bin/commadmin user create -D admin -F Calendar -l calmaster -L Master -n comms.beta.com -p 8080 -w adminpass -W adminpass -X wireless.comms.beta.com -S mail,cal -E calmaster@comms.beta.com -H wireless.comms.beta.com
{noformat}
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.

*To Log in to Delegated Administrator*
# In your web browser, open a URL for Delegated Administrator. The URL for Delegated Administrator is:
{{http://}}{_}fully-qualified-hostname{_}{{:}}{_}web-server-port{_}{{/da/DA/Login{}}}In this example, type:{nolink}*[http://wireless.comms.beta.com:8080/da/DA/Login]*{nolink}
# Log in using {{admin}} and {{adminpass}} as the user ID and password.
# After verifying that you can access Delegated Administrator, log out.
# Continue with the next section.

h3. Configuring Messaging Server

This section describes configuring Messaging Server.

*To Configure Messaging Server*
# Change to the directory where the Messaging Server {{configure}} script is stored, then run the script, for example:
{noformat:nopanel=true}
cd /opt/sun/comms/messaging64/sbin
./configure
{noformat}
The Configuration Wizard appears. Read the introductory information and proceed by clicking Next.
# Verify the following:{anchor:Step2}
#* Fully qualified host name of messaging server, FQHN: \[wireless.comms.beta.com\]
#* Directory to store config/data files: \[/var/opt/sun/comms/messaging64\]
#* Install MTA, Message Store, and Webmail Server: No need to install multiplexor.
#* Name of the mail server Unix user: username \[mailsrv\]
You might need to change to {{mailsrv2}} if this was the actual user created previously.
#* Name of Unix group: group \[mail\]
# The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 13 Values for Messaging Server configure Script*
|| Option || \[Default Value\] || Enter: ||
| User/Group Server Ldap | \[ldap://wireless.comms.beta.com:389\] | _accept default_ |
| Bind As | \[cn=Directory Manager\] | _accept default_ |
| Password | \- | *adminpass* |
| Postmaster email address | \- | *foo@wireless.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_ |
# Click Next, then click Configure Now.
You might receive an error about the Webmail port being in use. Click OK to acknowledge this message. The configuration begins.
# When configuration is finished, click Next to continue, then click Close to exit
{info:title=Note}
You might observe a failure such that not all the messaging configuration tasks have passed. If this is the case, rerun the Messaging Server configuration script by repeating all the previous steps in the To Configure Messaging Server section. When prompted for the directory in which to store configuration or data files, use the same directory as before. A popup window will state that this directory already exists. Click Accept Anyway to verify that the same directory will be used.
{info}
# Configure the webmail port.
{{/opt/sun/comms/messaging64/bin/configutil \-o service.http.port \-v 2080}}
# Start Messaging Server:
{noformat:nopanel=true}
/opt/sun/comms/messaging64/bin/stop-msg
/opt/sun/comms/messaging64/bin/start-msg
{noformat}
# Continue with the next section to configure Calendar Server.

h3. Configuring Calendar Server

This section shows you how to run the Calendar Server configuration script and how to verify the Calendar Server configuration.
# Change to the directory where the configuration script was installed then run the configuration script, for example:
{noformat:nopanel=true}
cd /opt/sun/comms/calendar/SUNWics5/cal/sbin
./csconfigurator.sh
{noformat}
# Click Next at the Welcome page.
The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 14 Values for Calendar Server csconfigure Script*
|| Option || \[Default Value\] || Enter: ||
| LDAP Server Host Name | \[wireless.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 | checked | _accept default_ |
| Virtual Domains settings: Default domain | \[comms.beta.com\] | _accept default_ |
| Calendar Administrator Username | \[calmaster\] | _accept default_ |
| Calendar Administrator Password | \- | *adminpass* |
| Calendar Administrator Email address | \[calmaster@comms.beta.com\] | _accept default_ |
| Site administrator | \[Yes\] | _accept default_ |
| Setup a Front End/Back End deployment | unchecked | _accept default_ |
| Email Alarms | \[Enabled\] | _accept default_ |
| Administrator Email Address | \[calmaster@comms.beta.com\] | _accept default_ |
| SMTP Host Name | \[wireless.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 | unchecked | _accept default_ |
| Start Calendar Server on system startup | checked | *Uncheck* |
| Config Directory | \[/etc/opt/sun/comms/calendar/SUNWics5/config\] | _accept default_ |
| Database Directory | \[/var/opt/sun/comms/calendar/SUNWics5/csdb\] | _accept default_ |
| Attachment Store Directory | \[/var/opt/sun/comms/calendar/SUNWics5/astore\] | _accept default_ |
| Logs Directory | \[/var/opt/sun/comms/calendar/SUNWics5/logs\] | _accept default_ |
| Temporary Files Directory | \[/var/opt/sun/comms/calendar/SUNWics5/tmp\] | _accept default_ |
| Enable Archive | Checked | _accept default_ |
| Archive Directory | \[/var/opt/sun/comms/calendar/SUNWics5/csdb/archive\] | _accept default_ |
| Enable Hot Backup | Checked | _accept default_ |
| Hot Backup Directory | \[/var/opt/sun/comms/calendar/SUNWics5/csdb/hotbackup\] | _accept default_ |
| Keep archives for (in days) | \[Minium: 3, Maximum: 6\] | _accept default_ |
| Keep hot backups for (in days) | \[Minium: 3, Maximum: 6\] | _accept default_ |
| Same as archive checkbox | Checked | _accept default_ |
# Click Configure Now to configure Calendar Server.
# Click Next when the configuration is complete.
# Click Details to verify that all packages configured correctly. Click Close to exit the configurator.
# Edit the {{ics.conf}} file to set calendar alarms and other default preferences.
{noformat:nopanel=true}
cd /etc/opt/sun/comms/calendar/SUNWics5/config
cp ics.conf ics.conf.orig
vi ics.conf
{noformat}
# Remove the comments from the following values to enable Calendar Server alarms:
{noformat:nopanel=true}
caldb.serveralarms.url = "enp:///ics/customalarm"
caldb.serveralarms.contenttype = "text/xml"
{noformat}
# Consider changing the following values:
{noformat:nopanel=true}
calstore.default.timezoneID = "America/Los_Angeles"
service.calendarsearch.ldap = "no"
service.http.ui.enable = "y"
service.http.renderhtml = "yes"
{noformat}
# Change the Calendar ACL:
From
{{calstore.calendar.default.acl = "@@o^a^r^g;@@o^c^wdeic^g;@^a^fs^g;@^c^\^g;@^p^r^g"}}to
{{calstore.calendar.default.acl = "@@o^a^r^g;@@o^c^wdeic^g;@^a^rfs^g;@^c^\^g;@^p^r^g"}}
# (Optional) If you changed the {{calstore.default.timezoneID}} in the {{ics.conf}} file, make the following edit to the {{/opt/sun/comms/calendar/SUNWics5/cal/html/en/default_user_prefs.xml}} file:
{noformat:nopanel=true}
<userpref name="icsTimeZone" default_value="America/Los_Angeles" />
{noformat}
# (Optional) To change the default time zone in Delegated Admininstrator, edit the {{DomainCalendarService.xml}} and {{UserCalendarService.xml}} files in the {{/opt/sun/comms/da/lib/services}} directory.
These files control users' default time zones created by using Delegated Administrator.
#* In these files, change the value of the time zone:
{noformat:nopanel=true}
America/Denver

{noformat}
to America/Los_Angeles (or your preferred time zone).
#* Run the following commands to delete and reload the service schemas.
{noformat:nopanel=true}
/opt/SUNWam/bin/amadmin -u amadmin -w adminpass -r DomainCalendarService
/opt/SUNWam/bin/amadmin -u amadmin -w adminpass -s /opt/sun/comms/da/lib/services/DomainCalendarService.xml
/opt/SUNWam/bin/amadmin -u amadmin -w adminpass -r UserCalendarService
/opt/SUNWam/bin/amadmin -u amadmin -w adminpass -s /opt/sun/comms/da/lib/services/UserCalendarService.xml
{noformat}
# Start the Calendar Server daemons, for example:
{noformat:nopanel=true}
cd /opt/sun/comms/calendar/SUNWics5/cal/sbin
./stop-cal
./start-cal
{noformat}
# Restart your Web container, for example:
{noformat:nopanel=true}
cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
./stopserv
./startserv
{noformat}
# Continue with the next section to configure Instant Messaging.

h3. Configuring Instant Messaging

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

*To Configure Instant Messaging*
# Change to the directory where the configuration script was installed then run the configurator script.
For example:
{noformat:nopanel=true}
cd /opt/sun/comms/im/sbin
./configure
{noformat}
The Components Selection page appears.
# Verify that both Server components and Client components are selected for configuration, then click Return to continue.
The configuration wizard prompts for a series of options.
# Respond to the series of options as follows.
After each question, you are prompted if you want to go back to previous panel. Always accept the default answer of {{no}} unless you need to make a change to a previous answer.
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 | *yes* |
| Runtime User ID | \[inetuser\] See [Note|#Note]. | *root* |
| Runtime Group ID | \[inetgroup\] See [Note|#Note]. | *root* |
| Runtime Directory | \[/var/opt/SUNWiim\] | _accept default_ |
| Create Runtime Directory | \[Choose New\] | *Create Directory* |
| 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 | \[wireless.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 | \[wireless.comms.beta.com\] | _accept default_ |
| Enable Email Archiving | \[yes\] | _accept default_ |
| Deploy Messenger Resources | \[yes\] | _accept default_ |
| Codebase | \[http://wireless.comms.beta.com:80/im\] | *\[http://wireless.comms.beta.com:8080/im\]* |
| Enable Audio | \[no\] | *yes* |
| Webcontainer Path | \-\- | */opt/SUNWwbsvr7* |
| Web Administration URL | \-\- | *\[https://wireless.comms.beta.com:8989/\]* |
| Web Administrator User Id | \[admin\] | _accept default_ |
| Web Administrator Password | \-\- | *adminpass* |
| Deploy IM HTTP Gateway | \[yes\] | *no* |
| Deploy IM IMPS Gateway | \[yes\] | _accept default_ |
| Context Root | \[http://wireless.comms.beta.com:8080/imps\] | *\[http://wireless.comms.beta.com:8080/imps\]* |
| Webcontainer Path | /opt/SUNWwbsvr7 | */opt/SUNWwbsvr7* |
| Web Administration URL | \[https://wireless.comms.beta.com:8989/\] | _accept default_ |
| Web Administrator User Id | \[admin\] | _accept default_ |
| Web Administrator Password | \-\- | *adminpass* |
| Enable Calendar Agent | \[no\] | *yes* |
| Enable local component | \[no\] | *yes* |
| XMPP server Hostname | \[wireless.comms.beta.com\] | _accept default_ |
| XMPP server port | \[5269\] | _accept default_ |
| Notification Server Hostname | \-\- | *wireless.comms.beta.com* |
| Notification Server Port | \[57997\] | _accept default_ |
| Calendar alarm URL | \[enp:///ics/customalarm\] | _accept default_ |
| Enable SMS Gateway | \[no\] | _accept default_ |
| Enable local component | \[no\] | _accept default_ |
| Enable MSN Gateway | \[no\] | _accept default_ |
| Enable local component | \[no\] | _accept default_ |
| Enable AIM Gateway | \[no\] | _accept default_ |
| Enable local component | \[no\] | _accept default_ |
| Enable YIM Gateway | \[no\] | _accept default_ |
| Enable local component | \[no\] | _accept default_ |
| Start Services After Successful Configuration | \[yes\] | *no* |
| Start Services When System starts | \[yes\] | *no* |
{anchor:Note}
{info:title=Note}
Access Manager requires that you install and run Instant Messaging services as {{root}}. You will see a pop-up that running as {{root}} is not recommended. For this evaluation, accept the super-user setting.
{info}
# The Instant Messaging configuration begins.
It could take a while to complete the configuration. When the configuration is complete, continue to the next step.
# Edit the iim.conf file to prepare for the new Communications Client.
{noformat:nopanel=true}
# cd /etc/opt/SUNWiim/default/config
# cp iim.conf iim.conf.orig
# vi iim.conf
{noformat}
You will add the new httpbind and avatar component JIDs to this file by making the following changes/additions:
{noformat:nopanel=true}
iim_server.components = "agent-calendar,httpbind,smppbind,msn_gateway,aim_gateway,yim_gateway,avatar"
iim_agent.enable = "true"

! httpbind component (HTTP/XMPP Gateway)
! ======================================

iim_agent.httpbind.enable = "true"
httpbind.jid = "wireless.httpbind.comms.beta.com"
httpbind.password = "adminpass"

! avatar component
! ======================================
iim_agent.avatar.enable = "true"
avatar.jid = "wireless.avatar.comms.beta.com"
avatar.password = "adminpass"
{noformat}
# Start the Instant Messaging server.
For example:
{noformat:nopanel=true}
# /opt/sun/comms/im/sbin/imadmin start
{noformat}
# If you choose to monitor the SMF logs, they are located in the {{/var/svc/log}} directory. The log name is {{application-sunim:default.log}}.
# Continue with the next section.

*To Log in to Instant Messaging*
# In your web browser, open a URL for Instant Messaging. The URL for Instant Messaging is:
{{http://}}{_}fully-qualified-hostname{_}{{:}}{_}port{_}{{/im/en/im.jnlp{}}}In this example, type:{nolink}*[http://wireless.comms.beta.com:8080/im/en/im.jnlp]*{nolink}
{info:title=Note}
If you cannot log in to Instant Messaging as a user, you might need to manually add the Instant Messaging and Presence Services to the user. See [To Add Services to the Lower Level Organization|#AddSvsLLOrg] for more information.
{info}

h3. Configuring Access Manager

The following procedures enable Access Manager authentication with Instant Messaging, and enable the Instant Messaging services for all users.

*To Log In to Access Manager*
# 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:{nolink}*[http://wireless.comms.beta.com:8080/amconsole]*{nolink}
# Log in as {{amadmin}}.
The password is {{adminpass}}.

{anchor:AddSvsLLOrg}

*To Add Services to the Lower Level Organization*
If you set your Organization DN to {{o=comms.beta.com,o=isp}} you will need to add IM and Presence services to the comms.beta.com organization. Once these services have been added to the suborg, you must add the necessary services to each user in this suborg.
{info:title=Note}
Previously, you created a set of users with the {{commadmin}} command. These users exist in the {{comms.beta.com}} organization. At this point, there are no Services defined for these users. You need to register the services with these users for them to be able to log in to Instant Messaging.
{info}
# Upon logging into the Access Manager Console, you see a view of all your organizations, including the {{comms.beta.com}} organization. Click the link to {{comms.beta.com}}.
# In the right pane, you see a list of General Properties. One of these properties is Domain Name. Verify the Instant Messaging domain name that you specified during the Instant Messaging configuration.
In this example, the domain name is {{comms.beta.com}}. If the field is blank, type the domain name then click the Save button.
# Choose Services from the View menu in the left pane.
# Click the Add button.
# Either click the individual services to add to this organization, or click the box at the top of the list that shows two checkboxes. This selects all the services. Upon selecting all the services, click the OK button to add all the services to the suborganization.
# Within this same suborganization, click the properties icon next to the name of Authentication Configuration. Normally, the service instance "ldapService" will exist. If a service instance (such as ldapService") does not exist, you will need to create one. To do so, perform the following steps. Note that if the ldapService instance already exists you may skip these steps:
#* Click the New button to define a new service instance.
#* Type the Instance Name *ldap1*, then click the Submit button.
The {{ldap1}} service instance is created.
#* Click the ldap1 link.
#* Click Edit 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.
{info:title=Note}
If the LDAP module name is missing in the pulldown menu, complete the next step (of assigning {{ldap1}} to the Core service). Then exit the Access Manager console and restart Web Server. After logging into the Access Manager Console, try again to add the LDAP module and LDAP should appear.
{info}
# Click the properties icon next to Core, just below Authentication Modules.
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.
# Click Save.
# 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.
# Click the property icon beside a user.
# In the right pane, open the View drop-down menu and choose Services.
No services are listed.
# Click the Add button.
A list of services appears.
# Click the double-checked box at the top of the list of services to add all services. Then click the OK button.
{info:title=Note}
The minimum services that you need to add to each user are the IM and Presence services. The Authentication Configuration service does not need to be added to each user but must be configured in each subdomain.
{info}

*To Configure User Services*

# In the right pane, scroll down until you see Required Services.
# Add the following services by typing the name of the service in the entry box and clicking Add.
#* SunIM
#* SunPresence
# Add any other services you choose.
# Click Save.

*To Configure User Services for All Users in a Given Domain*

You can also configure the IM 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.

# Run the following commands to add IM and Presence services for all users in a given domain:
{noformat:nopanel=true}
cd /opt/sun/comms/im/sbin
./imadmin assign_services
Please enter base DN:
o=comms.beta.com,o=isp
Assigning IM and Presence services to users under baseDN: o=comms.beta.com,o=isp ...
Done.
{noformat}
# Restart the web container.
{noformat:nopanel=true}
cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
./stopserv
./startserv
{noformat}

{toc-zone}

h2. Configuring Sun Convergence

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

# Run the Convergence configuration script.
{noformat:nopanel=true}
cd /opt/sun/comms/iwc/sbin
./init-config
{noformat}
# Read the Software Requirements and click Next to continue.
# Directory to store Configuration and Data Files \[/var/opt/sun/comms/iwc\]
The Components Selection page appears.
# Verify that Mail Service, Calendar Service, and Instant Messaging Service are selected for configuration, then click Next to continue.
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 | \[wireless\] | _accept default_ |
| DNS Domain Name | \[comms.beta.com\] | _accept default_ |
| Application Server Install Directory | \[/opt/SUNWappserver\] | _accept default_ |
| Domain Directory | \[/opt/SUNWappserver/domains/domain1\] | _accept default_ |
| Document Root Directory | \[/opt/SUNWappserver/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 | Checked | *Checked* |
| URI Path | \[iwc\] | _accept default_ |
| Enable Hosted Domain Support | checked | _accept default_ |
| Directory Server LDAP URL | \[ldap://wireless.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 | \[wireless.comms.beta.com\] | _accept default_ |
| Webmail Server Port Number | \[8990\] | *2080* |
| Access in SSL mode | unchecked | _accept default (Not secure)_ |
| Webmail Admin User ID | \[admin\] | _accept default_ |
| Admin Password | \- | *adminpass* |
| Calendar Server Host Name | \[wireless.comms.beta.com\] | _accept default_ |
| Calendar Server Port | \[80\] | *3080* |
| Access in SSL mode | unchecked | _accept default (Not secure)_ |
| 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 | \[wireless.comms.beta.com\] | _accept default_ |
| Server Port | \[5269\] | _accept default_ |
| httpbind Component JID | \[wireless.httpbind.comms.beta.com\] | _accept default_ |
| Password | \- | *adminpass* |
| Avatar Component JID | \[wireless.avatar.comms.beta.com\] | _accept default_ |
| Password | \- | *adminpass* |
| Convergence Administrator Username | \[admin\] | _accept default_ |
| Password | \- | *adminpass* |
# Click Configure Now to configure Sun Convergence.
# Click Next when the configuration is complete.
# Click Next to continue.
# Click Close to quit the Sun Convergence configuration wizard.
# 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{_}{{/iwc{}}}In this example, type:{nolink}\*[http://wireless.comms.beta.com/iwc]\*{nolink}

h2. Configuring Communications Express (Optional)

# Go to the directory where the configuration script was installed.
{noformat}
cd /opt/sun/comms/ce/sbin
{noformat}
# Run the Communications Express configurator script:
{noformat}
./config-uwc
{noformat}
# Click Next at the Welcome page.
# Accept the directory to store configuration and data files: \[/var/opt/sun/comms/ce\]
# Install Mail and Calendar Components.
# The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
*Table 17 Values for the Communications Express config-uwc Script*
|| Option || \[Default Value\] || Enter: ||
| Host Name | \[wireless\] | _accept default_ |
| DNS Domain Name | \[comms.beta.com\] | _accept default_ |
| Web Container | \[Web Server\] | _accept default_ |
| Server Root Directory | \[/opt/SUNWwbsvr7\] | _accept default_ |
| Config Root Directory | \[/var/opt/SUNWwbsvr7\] | _accept default_ |
| Server Instance Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| Virtual Server Identifier | \[wireless.comms.beta.com\] | _accept default_ |
| HTTP Port | \[80\] | *8080* |
| Administration Server Port | \[8800\] | _accept default_ |
| Administrator User ID | \[admin\] | accept default |
| Administrator Password | \- | *adminpass* |
| Secure Administration Server Instance | \[Unchecked\] | _accept default_ |
| Web Container User ID | \[root\] | _accept default_ |
| Web Container Group IP | \[root\] | _accept default_ |
| URI Path | \[/uwc\] | _accept default_ |
| Enable Hosted Domain Support | \[Checked\] | *Checked (Yes)* |
| Directory Server LDAP URL | \[ldap://wireless.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_ |
| Enable Access Manager for Single Sign-On | \[Unchecked\] | _accept default_ (Not enabled) |
| Webmail Server Host Name | \[wireless.comms.beta.com\] | _accept default_ |
| Webmail Server Port Number | \- | *2080* (See Note 1) |
| Enable login in secure mode | \[Unchecked\] | _accept default_ (Not secure) |
| Webmail Server SSL Port Number | \- | Leave blank |
| Webmail Admin UserID | \- | *admin* |
| Admin Password | \- | *adminpass* |
| Calendar Server Hostname | \[wireless.comms.beta.com\] | _accept default_ |
| Calendar Server Port | \[9004\] | *3080* |
| Calendar Administrator User ID | \[calmaster\] | _accept default_ |
| Calendar Administrator User Password | \- | *adminpass* |
| URL of PAB Directory Server | \[ldap://wireless.comms.beta.com:389\] | _accept default_ |
| Bind As | \[cn=Directory Manager\] | _accept default_ |
| Bind Password | \- | *adminpass* |
*Note 1:* After selecting a Webmail Port Number, a popup might occur stating that it is unable to connect to _hostname{_}{{:2080}}. Accept this port anyway. In other cases a popup may occur reminding you to enable Communications Express Webmail. Click OK to dismiss any popup that might occur.
# Click Configure Now to configure Communications Express.
# After the configuration is complete, click Next to continue.
The system displays a message to restart the Web Server Instance. Click OK to dismiss the message.
# Click Next to continue.
# Click Close to quit the Communications Express configurator.
# Enable UWC Webmail.
{noformat}
cd /opt/sun/comms/messaging64/sbin
./configutil -o local.webmail.sso.uwcenabled -v 1
./stop-msg
./start-msg
{noformat}
# Restart Web Server.
{noformat}
cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
./stopserv
./startserv
{noformat}
# In your web browser, open a URL for Communications Express and log in as a test user. The URL for Communications Express is:
{{http://}}{_}fully-qualified-hostname{_}{{:8080/uwc{}}}In this example, type:{nolink}*[http://wireless.comms.beta.com:8080/uwc]*{nolink}

h2. Creating Additional User Accounts and Groups

This section describes how to create additional users accounts and groups. Users and groups created in this fashion work with both Communications Services products and Portal Server (if you add Portal Server to this deployment at a later date).

*To Create Users and Groups*
* The following example shows how to create users using the Delegated Administrator command-line utility and also how to create a group consisting of the users created.
{noformat:nopanel=true}
/opt/sun/comms/da/bin/commadmin user create -D admin -F Demo -l demo1 -L One -n comms.beta.com -p 8080 -w adminpass -W demo -X wireless.comms.beta.com -S mail,cal -E demo1@comms.beta.com -H wireless.comms.beta.com

/opt/sun/comms/da/bin/commadmin user create -D admin -F Demo -l demo2 -L Two -n comms.beta.com -p 8080 -w adminpass -W demo -X wireless.comms.beta.com -S mail,cal -E demo2@comms.beta.com -H wireless.comms.beta.com

/opt/sun/comms/da/bin/commadmin group create -D admin -G Demostaff -n comms.beta.com -p 8080 -w adminpass -X wireless.comms.beta.com -S mail -E Demostaff@comms.beta.com -H wireless.comms.beta.com -o calmaster -m demo1 -m demo2
{noformat}
{info:title=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.
{info}
*To Use Delegated Administrator to Create Users*
An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator console. The high-level steps to create users with Delegated Administrator console are the following:
* Creating the user
* Using Access Manager to add Services to those user accounts (if necessary)

Prior to using Delegated Administrator, check the {{resource.properties}} file to make sure users will be created using options consistent with your usage. Because this example uses a hosted domain scenario, you do not need to edit this file to make changes. If you do want to make changes, perform the following steps.
# Change to the {{/var/opt/sun/comms/da/WEB-INF/classes/sun/comm/cli/server/servlet}} directory and edit the {{resource.properties file.}}\#\* The default settings for {{servicepackage}} refresh rates are:
{noformat}
servicepackage-ttlhours=5
servicepackage-ttlminutes=0
{noformat}
These parameters establish the time between service packages refreshes. In this demo scenario, service packages do not change very often so there is no need to refresh them every five minutes. Instead, change the rate to refresh service packages every five hours. Making this change improves Delegated Administrator performance. If you later decide to change the refresh rate to 20 hours, set {{servicepackage-ttlhours}} to 20, that is, {{servicepackage-ttlhours=5}}.
#* The default setting for calender ID type is set using the {{switch-caltype}} variable as follows:
{noformat}
switch-caltype=hosted
{noformat}
The caltype can be either {{hosted}} or {{legacy}}. When {{caltype}} is set to {{hosted}}, users that are created through Delegated Administrator are created as _uid_@_domain_ rather than _uid_.
# If you make any changes to the {{resource.properties}} file, restart the Web Server.
# The first time you use Delegated Administrator, you must add service packs to the organization that contains your users:
#* In your web browser, open the URL for Delegated Administrator.
In this example, type:{nolink}*[http://wireless.comms.beta.com:8080/da/DA/Login]*{nolink}
Log in as {{amadmin}}. The password is {{adminpass}}.
#* 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}}, {{mars}}, {{mercury}}, and {{venus}} 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.
#* If you chose a service package that contains Calendar, type the Calendar Host {{{*}wireless.comms.beta.com{*}}} and {{{*}Yes{*}}} for Anonymous Login. Then click Next.
#* Select the quantity of each service pack desired then click Next.
A quantity of 100 is appropriate for this example.
#* Review your choices and click Finish to create the service packages.
Once the service packs have been allocated for the domain, you can add users to the domain.
#* Click the domain link. That is, click {{comms.beta.com}}.
#* Click the New button to create a new user within this domain.
#* 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, for example, {{earth}}, 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.
# Log in to Access Manager as {{amadmin}} and verify that the IM 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 [To Add Services to the Lower Level Organization|#AddSvsLLOrg].

h2. Known Issues and Limitations

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