Sun Java Communications Suite 6 Update 2 on a Single Host

Skip to end of metadata
Go to start of metadata

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.

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.

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

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.

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

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

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

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.

Installation Notes and Recommendations

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

  1. 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 ".").

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 Application Server 9.1
  3. Installing and configuring Directory Server 6.3
  4. Running the Identity Suite installer and selecting the necessary components required by the Java Communications Suite (Web Server and Access Manager)
  5. Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Communications Express, and Delegated Administrator
  6. Configuring Delegated Administrator and Communications CLI
  7. Configuring Messaging Server
  8. Configuring Calendar Server
  9. Configuring Instant Messaging
  10. Installing and Configuring Convergence
  11. Configuring Communications Express
  12. 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.

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

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 wireless.comms.beta.com wireless loghost
    
  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
    

Getting the Necessary Software

To Get the Software

  1. Get the Communications Suite, Application Server, and Identity Suite software.

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.

  1. 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:
    # java -version
    

    The shell returns results that look similar to the following:
    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)
    
  2. Create the /tmp/APPSVR91U2 directory, copy the Application Server 9.1 Update 2 bits to this directory, then launch the installer.
    # cd /tmp/APPSVR91U2
    # chmod +x *
    # ./sjsas_ee-9_1_02-solaris-sparc.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] 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
  5. Start the Application Server:
    # /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
    
    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.
  6. Create the /tmp/DS directory and copy the Directory Server 6.3 bits to this directory. Uncompress them and then run the installer.
    # 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
    
  7. Press Enter to Continue when prompted.
  8. Accept the License Agreement by typing yes when prompted.
    The installation proceeds and installs the Directory Server bits in the specified location /opt/SUNWdsee.
  9. Create your Directory Server instance.
    # mkdir /var/opt/SUNWdsee
    # cd /opt/SUNWdsee/ds6/bin
    # ./dsadm create -p 389 -P 636 /var/opt/SUNWdsee/dsins1
    
  10. Choose the Directory Manager password: adminpass
  11. Confirm the Directory Manager password: adminpass
  12. Start your Directory Server instance.
    # ./dsadm start /var/opt/SUNWdsee/dsins1
    
  13. Create the root suffix o=isp by using the dsconf command:
    ./dsconf create-suffix -h hostname -p 389 o=ispIn this example, type:
    # ./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.
    
  14. Accept the Certificate and type adminpass as the cn=Directory Manager password.
    Type "Y" to accept, "y" to accept just once, "n" to refuse, "d" for more : Y
    Enter "cn=Directory Manager" password: adminpass
    
  15. Create the /tmp/JIS5 directory and unzip Identity Suite bits in this directory. Then run the Java ES installer.
    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.

    # cd java_es-5u1-identsuite
    # cd Solaris_sparc
    # ./installer &
    

  16. Click Next at the Welcome page.
  17. Accept the license.
    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.

    If you happen to be installing Identity Suite on Solaris OS 9, you can skip steps 18-28 and immediately proceed to step 29.

  18. Click the Upgrade existing software radio button and click Next to continue.
  19. 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.
  20. Click Next to upgrade shared components.
  21. The installer verifies system requirements. When done, click Next.
  22. At the "Ready to Upgrade" window, click Next.
  23. Deselect the registration checkbox, then click Install.
    The upgrade proceeds. When the installation is complete, the Installation Complete page is displayed.
  24. Click Close to exit the installer.
  25. Restart the Java ES installer to install the remaining Identity Suite components.
    # ./installer &
    
  26. Click Next at the Welcome page.
  27. Accept the license.
  28. In the "Choose to Upgrade or Install" window, select the "Install new software" radio button, then click Next to continue.
  29. 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.
  30. 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.
  31. 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.
  32. 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.
  33. Specify Installation Directories.
    Locations:
    Access Manager: /opt (creates /opt/SUNWam)
    Web Server: /opt (creates /opt/SUNWwbsvr7)
    Web Server Instance: /var/opt/SUNWwbsvr7
  34. Accept the target directories for each product and click Next.
  35. The installer verifies system requirements. When done, click Next.
  36. Choose Configure Now, then click Next.
  37. 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.

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

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

  1. 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.
  2. When installation is complete, the Installation Complete page is displayed. Click Close to exit the installer.

To Verify the Installation

  1. Start Web Server:
    cd /var/opt/SUNWwbsvr7/admin-server/bin
    ./stopserv
    ./startserv
    cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
    ./stopserv
    ./startserv
    

    The Web Server can take a while to start.
  2. 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/amconsoleIn this example, type:http://wireless.comms.beta.com:8080/amconsole
    Use amadmin and adminpass as the user ID and password.
  3. After verifying that you can log in to the Access Manager console, log out.
  4. Verify the Application Server by typing the following URL:
    http://fully-qualified-hostnameIn this example, type:http://wireless.comms.beta.com
  5. Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.

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:
    ./commpkg uninstall
    
  • To uninstall Identity Suite:
    cd /var/sadm/prod/SUNWident-entsys5u1i/bin
    ./uninstall
    

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:

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

groupadd mail
useradd -u 7633 -g mail -d /export/home/mailsrv -m mailsrv

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,
# useradd -u 7633 -g mail -d /export/home/mailsrv2 -m mailsrv2

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:
    svcadm disable sendmail
    

    For Solaris OS 8 and 9:
    ps -ef | grep sendmail
    kill -9 sendmail_pid
    cd /etc/rc2.d
    mv S88sendmail save.S88sendmail
    

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

  1. 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.
    # cd /tmp/JCS6
    # ./commpkg install
    
  2. Press RETURN to continue when prompted
  3. Review the license and type c to continue when prompted.
    You can also type s to skip the license display.
  4. Accept the License Agreement by typing yes when prompted.
  5. Accept the default Install location: /opt/sun/comms
  6. 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.
  7. 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
  8. Press RETURN when prompted to continue.
  9. Installation Proceeds.
  10. Press RETURN when prompted to continue.

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. Chance the directory where the comm_dssetup script is located and run the script, for example:
    cd /opt/sun/comms/dssetup/sbin
    /usr/bin/perl 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 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
  3. Confirm your choices and type y to continue.
    The comm_dssetup proceeds.
  4. 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.

Configuring Delegated Administrator and Communications CLI

This section describes configuring Delegated Administrator console and utility, which provide user 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
    
  2. Click Next in the Welcome window.
  3. Accept the default for the Directory to store Configuration and Data Files: /var/opt/sun/comms/daIf the directory does not exist, click 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 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
  5. Click 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 Web Server; the other reminds you to enable the mail and calendar services in the domain. The next steps complete these steps.
  7. Click Close to exit the Delegated Administrator Configuration wizard.
  8. Restart the Web Server.
    cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
    ./stopserv
    ./startserv
    
  9. Modify the mail and calendar domains, and create users by using the commadmin utility:
    /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
    

    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

  1. 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/LoginIn this example, type:http://wireless.comms.beta.com:8080/da/DA/Login
  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.

Configuring Messaging Server

This section describes configuring Messaging Server.

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/messaging64/sbin
    ./configure
    

    The Configuration Wizard appears. Read the introductory information and proceed by clicking Next.
  2. Verify the following:
    • 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]
  3. 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
  4. 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.
  5. When configuration is finished, click Next to continue, then click Close to exit
    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.
  6. Configure the webmail port.
    /opt/sun/comms/messaging64/bin/configutil -o service.http.port -v 2080
  7. Start Messaging Server:
    /opt/sun/comms/messaging64/bin/stop-msg
    /opt/sun/comms/messaging64/bin/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.

  1. Change to the directory where the configuration script was installed then run the configuration script, for example:
    cd /opt/sun/comms/calendar/SUNWics5/cal/sbin
    ./csconfigurator.sh
    
  2. 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
  3. Click Configure Now to configure Calendar Server.
  4. Click Next when the configuration is complete.
  5. Click Details to verify that all packages configured correctly. Click Close to exit the configurator.
  6. Edit the ics.conf file to set calendar alarms and other default preferences.
    cd /etc/opt/sun/comms/calendar/SUNWics5/config
    cp ics.conf ics.conf.orig
    vi ics.conf
    
  7. Remove the comments from the following values to enable Calendar Server alarms:
    caldb.serveralarms.url = "enp:///ics/customalarm"
    caldb.serveralarms.contenttype = "text/xml"
    
  8. Consider changing the following values:
    calstore.default.timezoneID = "America/Los_Angeles"
    service.calendarsearch.ldap = "no"
    service.http.ui.enable = "y"
    service.http.renderhtml = "yes"
    
  9. 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"
  10. (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:
    <userpref name="icsTimeZone" default_value="America/Los_Angeles" />
    
  11. (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:
      America/Denver
      
      

      to America/Los_Angeles (or your preferred time zone).
    • Run the following commands to delete and reload the service schemas.
      /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
      
  12. Start the Calendar Server daemons, for example:
    cd /opt/sun/comms/calendar/SUNWics5/cal/sbin
    ./stop-cal
    ./start-cal
    
  13. Restart your Web container, for example:
    cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
    ./stopserv
    ./startserv
    
  14. 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
    

    The Components Selection page appears.
  2. 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.
  3. 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. root
    Runtime Group ID [inetgroup] See 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

    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.
  4. The Instant Messaging configuration begins.
    It could take a while to complete the configuration. When the configuration is complete, continue to the next step.
  5. Edit the iim.conf file to prepare for the new Communications Client.
    # cd /etc/opt/SUNWiim/default/config
    # cp iim.conf iim.conf.orig
    # vi iim.conf
    

    You will add the new httpbind and avatar component JIDs to this file by making the following changes/additions:
    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"
    
  6. Start the Instant Messaging server.
    For example:
    # /opt/sun/comms/im/sbin/imadmin start
    
  7. 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.
  8. Continue with the next section.

To Log in to Instant Messaging

  1. In your web browser, open a URL for Instant Messaging. The URL for Instant Messaging is:
    http://fully-qualified-hostname:port/im/en/im.jnlpIn this example, type:http://wireless.comms.beta.com:8080/im/en/im.jnlp
    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 for more information.

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

  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/amconsoleIn this example, type:http://wireless.comms.beta.com:8080/amconsole
  2. Log in as amadmin.
    The password is adminpass.

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.

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.
  1. 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.
  2. 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.
  3. Choose Services from the View menu in the left pane.
  4. Click the Add button.
  5. 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.
  6. 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.
      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.
  7. 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.
  8. Click Save.
  9. 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.
  10. Click the property icon beside a user.
  11. In the right pane, open the View drop-down menu and choose Services.
    No services are listed.
  12. Click the Add button.
    A list of services appears.
  13. 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 IM and Presence services. The Authentication Configuration service does not need to be added to each user but must be configured in each subdomain.

To Configure User Services
Use this procedure if you want Access Manager services to automatically be added upon user creation. This is useful if you want the Instant Messaging, Presence, and Portal services to be automatically created for each user you create through Delegated Administrator (either the command-line utility or console).

Caution
Try this on a test system first to verify that you don't have subsequent performance issues.
  1. In the Access Manager console, from within the comms.beta.com organization, select the Service Configuration tab.
  2. Click the properties icon beside Administration service.
  3. In the right pane, scroll down until you see Required Services.
  4. Add the following services by typing the name of the service in the entry box and clicking Add.
    • SunIM
    • SunPresence
  5. Add any other services you choose.
  6. 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.

  1. Run the following commands to add IM 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
    Assigning IM and Presence services to users under baseDN: o=comms.beta.com,o=isp ...
    Done.
    
  2. Restart the web container.
    cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
    ./stopserv
    ./startserv
    

Configuring Sun Convergence

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

  1. Run the Convergence configuration script.
    cd /opt/sun/comms/iwc/sbin
    ./init-config
    
  2. Read the Software Requirements and click Next to continue.
  3. Directory to store Configuration and Data Files [/var/opt/sun/comms/iwc]
    The Components Selection page appears.
  4. 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
  5. Click Configure Now to configure Sun Convergence.
  6. Click Next when the configuration is complete.
  7. Click Next to continue.
  8. Click Close to quit the Sun Convergence configuration wizard.
  9. 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/iwcIn this example, type:*http://wireless.comms.beta.com/iwc*

Configuring Communications Express (Optional)

  1. Go to the directory where the configuration script was installed.
    cd /opt/sun/comms/ce/sbin
    
  2. Run the Communications Express configurator script:
    ./config-uwc
    
  3. Click Next at the Welcome page.
  4. Accept the directory to store configuration and data files: [/var/opt/sun/comms/ce]
  5. Install Mail and Calendar Components.
  6. 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.

  7. Click Configure Now to configure Communications Express.
  8. 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.
  9. Click Next to continue.
  10. Click Close to quit the Communications Express configurator.
  11. Enable UWC Webmail.
    cd /opt/sun/comms/messaging64/sbin
    ./configutil -o local.webmail.sso.uwcenabled -v 1
    ./stop-msg
    ./start-msg
    
  12. Restart Web Server.
    cd /var/opt/SUNWwbsvr7/https-wireless.comms.beta.com/bin
    ./stopserv
    ./startserv
    
  13. 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/uwcIn this example, type:http://wireless.comms.beta.com:8080/uwc

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

  1. 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:
    servicepackage-ttlhours=5
    servicepackage-ttlminutes=0
    

    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:
      switch-caltype=hosted
      

      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.

  2. If you make any changes to the resource.properties file, restart the Web Server.
  3. 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:http://wireless.comms.beta.com:8080/da/DA/Login
      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.
  4. 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.

Known Issues and Limitations

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

Labels:
example example Delete
installing installing Delete
calendarserver calendarserver Delete
messagingserver messagingserver Delete
directoryserver directoryserver Delete
convergence convergence Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Feb 13, 2008

    On the point "Preparing the Directory" talking about directory server, there is the table of values. The first entry has no different between default and entry value ¿?

    Directory server root
    [/var/opt/SUNWdsee/dsins1] /var/opt/SUNWdsee/dsins1

    1. Feb 13, 2008

      Good catch. Changed to "accept default."

  2. Feb 21, 2008

    Hi,
    I´m reading the document and ...
    Maybe on the point "Uninstalling the Components"
    We could add something like
    Use the Gui in order to uninstall identification suite with
    #cd /var/sadm/prod/SUNWident-entsys5u1i/bin
    #./uninstall
    To uninstall Comm6 components
    ./commpkg uninstall

    Maybe is not on the scope of this document but could help a little bit.

    1. Feb 21, 2008

      Addressed in doc.

  3. Feb 21, 2008

    On the part "Installing Communications Suite 6 Software"
    on the table of the Point 11, I just done my 3 try to install the soft and I haven´t been asked by the all options but the java help runtime one.

    1. Feb 21, 2008

      I'm guessing that the options displayed are dependent on the state of the system. Added text in doc.

  4. Feb 21, 2008

    On the point "Configuring Delegated Administrator and Communications CLI"
    After the configuration by GUI, we need to launch a command to modify the mail and calendar domains.
    The PATH "/opt/SUNWcomm/bin/commadmin" doesn't exist its located at /opt/sun/comms/da/bin/commadmin

    On the next point "To Log in to Delegated Administrator" the URL doesn't specify the port 8080 and its necessary because the DA has been deployed on the web server 7 that its working on that port. On the port 80 its the application server 9.1 and the example URL doesn't work.

    1. Feb 21, 2008

      Fixed both path to commadmin and missing port in URL.

  5. Feb 21, 2008

    On the point "Configuring Calendar Server"
    Cheeking the parameter table the "Calendar Administrator Email address" default when installing appears like root@XXX.XX not like calmaster@XXX.XXX should be changed?

    1. Feb 21, 2008

      We'll need to recheck this. Don't doubt that you are seeing it, but we want to confirm.

  6. Feb 21, 2008

    The communication express is not on the scope of this document, but it could be a good idea, meanwhile communication center its not launched, to say that we can use the "COMM 5 Single host doc" to install it and configure it. With a link to the doc on docs.sun.com. What do you think?

    1. Feb 28, 2008

      Hirva,

      Your idea is not in the scope of this document. There are too many differences now between the old doc for Communications Suite 5 and this new one for Communications Suite 6 to just link to the old doc.

      If you take exactly the same defaults as specified in the Communications Suite 5 doc you will get an unusable deployment. For instance in R5 the messaging port was 8080 but now in R6 it is 2080. Mixing parts of R5 into R6 instructions verbatim will cause problems.

  7. Feb 29, 2008

    Directory Server version as installed by JES5u1 is 6.2, not 6.0

    Also, i don't think this statement is true : "Currently, Application Server 9.1 Update 1 does not support Access Manager."

    This can be removed as QA has successfully deployed, and tested with, Access Manager in App Srvr 9.1u1.

  8. Feb 29, 2008

    Mags,
    I incorporated your comments above.

  9. Mar 03, 2008

    Hi,
    Now Comunication center its part of the beta, and the way to install it talk about a icw.zip file that it doesnt exist. All the software can be find at /opt/sun/comms/iwc.
    Should we launch "/opt/sun/comms/iwc/install" or "/opt/sun/comms/iwc/sbin/init-config" in order to completed the installation?

  10. Mar 03, 2008

    On Table 15 "Values for Instant Messaging configure Script"

    Context Root http://wireless.comms.beta.com:80/httpbind accept default

    maybe its

    http://wireless.comms.beta.com:8080/httpbind???

    anyway if its unchecked it doesn't matter

    1. Mar 05, 2008

      Hirva,

      Right, it doesn't matter. As the items are unchecked, those components will not be installed so you do not change their values.

  11. Mar 03, 2008

    Hirva,

    Checking on your above two comments.

  12. Mar 12, 2008

    Under Configuring Communication Center

    The comment  http://wikis.sun.com/display/CommSuite/Communication+Center+1.0+Initial+Configurationhttp://wikis.sun.com/display/CommSuite/Communication+Center+1.0+Initial+Configuration(http://wikis.sun.com/display/CommSuite/Communication+Center+1.0+Initial+Configuration) applies as well to this document.

    This line:

    Is actually /opt/SUNWappserver/domains/domain1/applications/j2ee-modules/Communication_Center/WEB-INF/config
    This location is not available/created until after you run /opt/sun/comms/iwc/sbin/init-config to configure the IWC instance

    Are the manual editing directions for configuration.xml, credentials.xml, and httpbind.conf still
    valid as it seems that init-config takes care of this?

    This section:

    What impact/guideline is there for setting acceptor-threads from 1 to 2 (i.e. CPU, core, something else, etc)?

    Also, the item mentions Comet support (not sure what this is):

     Is this item still valid (is it needed? is it not needed? what app server issue is it referencing and is it resolved?)

    The single user guide lists not checking Deploy IM Http Gateway and Deploy IM IMPS Gateway in the IM configure script options table. 

    Under what circumstances would someone want to check these options, particularly the IM IMPS Gateway as this appears to be something new to JCS 6? 

    1. Mar 12, 2008

      Nate - Checking into your questions. Will post when I've got answers.

      1. Mar 12, 2008

        One answer:

        Q. Are the manual editing directions for configuration.xml, credentials.xml, and httpbind.conf still valid as it seems that init-config takes care of this?

        A. No, init-config should take care of this. I'll be updating this document to reflect that.

      2. Mar 12, 2008

        Another answer:

        Q. Also, the item mentions Comet support (not sure what this is):

        SKIP THIS COMETSUPPORT STEP UNTIL the APPSERVER ISSUE is RESOLVED.
        Also to this same http-listener block add the folowing line just before the end tag:


        </http-listener>
        <property name="cometSupport" value="true"/>

        Is this item still valid (is it needed? is it not needed? what app server issue is it referencing and is it resolved?)

        A. Comet is a technology to provide scalability for the IM service. It is not available in the C6 Beta, so for now, we are just noting it in the doc.

      3. Mar 13, 2008

        One more answer.

        Q. What impact/guideline is there for setting acceptor-threads from 1 to 2 (i.e. CPU, core, something else, etc)?

        A. Per a Comms engineer:
        "I set the acceptor-threads to 2. My deployment doesn't check the HTTP gateway because I am using Communication Center in my deployment so there is no need for it because Communication Center deploys a gateway. You could choose to deploy the IM IMPS gateway if you wanted to enable mobile IM clients (running on IMPS capable phones) to communicate to our IM server. You would enable this if you wanted to evaluate this feature and your server was accessible from the open Internet. If your server is not on the open Internet, you could use phone simulators to evaluate this feature. In the future, it is very possible that we will change the procedure to enable IMPS in this single host doc.

        1. Mar 13, 2008

          That makes sense, thank you for the clarifications

  13. Mar 26, 2008

    The IM Server configuration table is missing an element:

    Deploy Messenger Resources - checked accept default
    Codebase - http://wireless.comms.beta.com:8080/im
    Web Administration URL - https://wireless.comms.beta.com:8989/

    Should include Webcontainer Path /opt/SUNWwbsvr7 between Codebase and Web Administration URL

    By default my installation shows /usr which causes IM to not deploy to JWS (no obvious errors are thrown on this).

    The workaround is to either set Webcontainer Path (or pay attention, ha!) to the root of your JWS binary installation (/opt/SUNWwbsvr7 by default) or manually point JWS at IM:

    • http://yourJWShost:8800
    • login as JWS admin user
    • On the right hand side of the screen choose 'Add Web Application'
    • The path will be /opt/sun/comms/im/html
    • The URI will be /im
    • Click OK
    • Deploy via the link on the upper right hand side of the screen next to the Java icon
    • Click Deploy
    1. Mar 31, 2008

      As usual, thanks Nate. I'll be updating this doc this week so your info will come in handly.

      • Joe
  14. Apr 01, 2008

    This is a procedural clarification question/comment with regard to 'Configuring Access Manager' with respect to IM Server.

    I ran into this particular issue because I'm not sure I understand the usage case for imadmin assign_services versus 'To Add Services to the Lower Level Organization'.

    In a new installation I may have o=isp and o=comms.beta.com,o=isp

    Is it correct to say that one uses the imadmin assign_services method when the following is true:

    • Users are already in the LDAP directory and we with to give them the ability to use IM Server
    • We are not concerned with allowing future newly created users the same rights necessarily (i.e. no Delegated Administration connection to allow this to automatically happen)

    The procedure under 'To Add Services to the Lower Level Organization' seems to be used for the following:

    • Users are not already in the LDAP directory (i.e. a new installation)
    • We want new users added via Delegated Administrator to inherit the ability to use IM automatically

    If a user runs both procedures an error may be generated when setting up and configuring Communication Center using init-config:

    dn: o=isp
    sunPreferredDomain:comms.beta.com

    This is created when using the 'To Add Services to the Lower Level Organization' directions and after imadmin assign_services has already been used

    dn: o=comms.beta.com,o=isp
    sunPreferredDomain:comms.beta.com

    Probably created using imadmin assign_services, possibly by an earlier JCS component such as Calendar or Messaging Server

    The former item (o=isp level) can cause an error where a user is not able to login to the mshttpd process on the Messaging Server when running init-config to configure Communication Center.

    This is true even though mshttpd is running on the Messaging Server and the user has provided the correct credentials.

    The fix is to remove sunPreferredDomain from the o=isp level and then run init-config again.

  15. May 01, 2008

    Directory Server 6.2 has a pretty significant database corruption bug. You don't even know you have it until you shutdown and start backup again. Backups are also corrupted.

    DS 6.3 fixes the issue the corruption problem.

    So is COMs 6 shipping with 6.2 or 6.3?

    It might be a good idea to change 6.2 docs to 6.3.

    1. May 01, 2008

      DSEE, Access Manager, and Java Web Server come from JES 5.1 update 1, however DSEE is version 6.2 with JES 5.1u1

      You can install DSEE 6.2 and upgrade to 6.3: http://www.sun.com/software/products/directory_srvr_ee/get_dsee_download.jsp

      I broke down the patch dependencies from one of my installations.

      The patches should be installed in single user mode.

      Patch listing is based on Solaris 10 update 4 so YMMV

      SPARC - 125276-07 is the DSEE patch, install after the following are installed:

      119254-53
      119810-05
      123893-04
      125358-06
      125378-05
      125444-11
      125952-07
      120900-14
      125369-13
      125476-02
      127111-11

      x64 - 125278-07 is the DSEE patch, install after the following are installed:

      119044-03
      121334-02
      119255-53
      119811-05
      123896-04
      125359-06
      125379-05
      125446-11
      125953-07
      120901-03
      125370-06
      127112-11

    2. May 01, 2008

      Karl,

      We're aware of this issue. I'm trying to find out what the answer is at this point. I will post what I find out.

      Thanks,

      • Joe
  16. May 01, 2008

    It would also be nice to have a version of this document showing how to deploy everything securely (ssl/tls) from frontend to backend.

    That being said, this is an awesome document!

    1. May 01, 2008

      Karl,

      Thanks for the kudos. Glad you liked the doc.

      I'm working on a Comms multi-host deployment example right now with one of our SMEs. This will be available in the near future. We have SSL as a "nice to have" for that doc. Will see if we can get it in.

      • Joe
      1. May 02, 2008

        I'm looking forward to the multihost example. Our company of 500 employees are going to be deploying COMs.

        It looks like we are going to deploy it in the following way.

        Front End Server

        App Server
        Convergence
        Mail Sever

        Calendar server
        Messaging Server
        Directory Proxy Server
        BackEnd Server

        Directory Server (Already exists for us)
        Delegated Administrator Server
        We may deploy another webserver on our DMZ for external access.

        My head is spinning thinking of all the SSL/TLS that will need to be setup.

  17. May 05, 2008

    If your "intranet" sitting behind a DMZ is sufficiently secure, you may consider placing Convergence in "DMZ" (as well as your web server) and the communications between Convergence and other servers do not use SSL. This could reduce your configuration and maintenance chores
    greatly. The load balancers can also offload SSL improving the performance dramatically. The Sun Java System Messaging Server 6.3 Deployment Planning Guide is a good source of other ideas on
    Security hardening.

     
      HTTPS
        |
    ------------
    Load Balancer
    SSL offloaded
    ------------
       DMZ
    Convergence
    ------------
       | |
      non-SSL
       | |
       V V
    -----------
    CS, IM, MS
    -----------
    

    Sarma

  18. Aug 02, 2008

    Like the article, could have done with this when I setup JCS 5.

    Having a problem accessing the Access Manger console (http://myserver.com:8080/amconsole). The application server works, and the webserver works, both 'admin-server' and 'https-myserver.com' start with no errors but the console will not display. I have followed the guide as closely as possible (using dsee 6.3). I wonder if it's because I'm running on SXCE (build 94), although I've had no errors during install.

    My other question is, is it possible to deploy JCS on a single host whilst allowing the webserver to run on port 80? I had JCS 5 working with comms express and still able to put my own website on port 80. Haven't got this solution working yet but it appears application server is using port 80 instead.

    1. Aug 03, 2008

      >> Like the article, could have done with this when I setup JCS 5.

      This article is actually based on the Comm-Suite-5 single-host-install guide (http://docs.sun.com/app/docs/doc/820-0086) which in turn was based on the JES4 single host install guide (http://dlc.sun.com/pdf/819-4879/819-4879.pdf).

      >> Having a problem accessing the Access Manger console (http://myserver.com:8080/amconsole). The
      >> application server works, and the webserver works, both 'admin-server' and 'https-myserver.com'
      >> start with no errors but the console will not display. I have followed the guide as closely as
      >> possible (using dsee 6.3). I wonder if it's because I'm running on SXCE (build 94), although I've
      >> had no errors during install.

      Solaris Express is definitely not a supported (nor tested) OS for Communication Suite 6. Please re-attempt your installation on Solaris 10 update 4 or 5 and see if the problem persists.

      >> My other question is, is it possible to deploy JCS on a single host whilst allowing the
      >> webserver to run on port 80?

      Yes this is possible. You would need to modify the relevant port configurations in the guide to match.

      >> I had JCS 5 working with comms express and still able to put my own
      >> website on port 80. Haven't got this solution working yet but it appears application server is
      >> using port 80 instead.

      Application Server is used for end-user web-client access (Convergence) therefore it was configured to use the most convenient port for this role (80). Future revisions of this guide may in fact do away entirely with webserver and instead use Application Server only.

      1. Aug 12, 2008

        Didn't know that there was a JCS5 single host guide, must have been harder to find before. At least it's on the download page now so no excuses for not finding it now.

        I have managed to get it all installed now and convergence is AWESOME! Only problem is, the instant messaging doesn't load into convergence, it works by itself (http://www.example.com/im) but in convergence the Buddy List stays at "Connecting..." and firefox status bar reads "Waiting for www.example.com". I have been extremely careful to follow the guide exactly, even re-installed the suite from scratch, still the same. Strange thing is that on my original install attempt it did work at one point but no settings were changed. It was just after I added a contact to buddy list and had the contact approve it. Not managed to get convergence IM panel working since.

        Further feedback: these products are great but damn hard to install and setup. I wish for an easier (bundled) installer for JCS 6, with DSEE6.3 and other updates better integrated. I currently have two cacao SMF's, one is disabled, it all works (except convergence IM) but is at least a bit disconcerting.

        1. Aug 12, 2008

          Ethoms:

          Glad to hear that this guide was useful.

          re: your IM problem, wonder if this could be the issue, which we know is an issue with the VMware image:

          http://wikis.sun.com/display/CommSuite/Using+the+Sun+Java+Communications+Suite+6+VMware+Image#UsingtheSunJavaCommunicationsSuite6VMwareImage-KnownIssues

          Understood that Comms is not the most friendly in terms of initial install/config. I think we're looking at an easier way to get an eval deployment up and running. The VMware image might be useful in this respect as well, if you haven't seen it:

          http://wikis.sun.com/display/CommSuite/Using+the+Sun+Java+Communications+Suite+6+VMware+Image

          1. Aug 15, 2008

            Thanks for the known issues link but this information is in the above walkthrough so I already have correct settings here.

            I have also changed the httpbind and avatar passwords in httpbind.conf (/opt/sun/comms/iwc/config/httpbind.conf) to be clear text instead of the encrypted ones that where filled in by installation scripts. They now match exactly.

            I think this is where my problem lies, output from httpbind log (/var/opt/sun/comms/iwc/logs/httpbind.log):

            [14 Aug 2008 23:17:15,741] ERROR httpbind [main] Missing native library key in web.xml : httpbind.library.checkpermission
            [14 Aug 2008 23:17:31,697] ERROR httpbind [main] Error opening stream to server: www.example.com : 5222

            I can telnet 5222 so I know it's running, but which web.xml is "Missing native library key". I can't find anything in google regarding "httpbind.library.checkpermission" and the following command (searches for the string in all web.xml files) returns nothing:

            #for i in `find / -name web.xml`; do cat $i | grep httpbind.library.checkpermission; done

            Is there a good troubleshooting resource? What about a good forum to post help regarding convergence issues? Thanks, Euan.

              1. Aug 31, 2008

                I'm still having problems with IM in convergence. I've changed the port in httpbind.conf to 5269 and I get the same error in httpbind.log.

                IM works fine by itself, just a convergence issue, constant "Connecting..." in the IM side panel.

                Below are the logs httpbind.log and xmppd.log.

                Any help is much appreciated.

                httpbind.log:

                xmppd.log:

                1. Aug 31, 2008

                  OK, I got it fixed. Everything now seems to work well. I forced enterprise system components to use Java SE 1.6.0 like this:

                  To be honest I've hacked the installation a bit to get it working on SXCE (build 95) on my test server. I know it's not supported but I don't need support on my test server. Once I've suitably impressed the right people (AKA my bosses) I have every intention of sticking it on Sun server with Solaris 10. The reason I insist on SXCE for testing is that it has latest ZFS and I want to make use of it's exiting new features.

                  Unfortunately zfs on Solaris 10 and SXCE are incompatable. SXCE has quite a lot of new features/ improvements.

                  When will the Sun Java System be supported on OpenSolaris, IPS is the way to go, is Solaris 11 coming anytime soon?

                  You can pass the info on to the dev team that it works great under SXCE, I just had to:

                  1.) Trick latest Cacao package version into thinking it was older one (JES5u1 installation)
                  2.) Create links to ldapsearch (and possibly others in same bin folder) after installing DSEE 6.3 using this command: #for i in `find /opt/SUNWdsee/dsrk6/bin -type f -print`; do ln -s $i /opt/SUNWdsee/dsee6/bin; done
                  3.) After installation, force use of JDK1.6.0 as mentioned above.

                  Thanks for all your help Joe!!

  19. Aug 06, 2008

    I'm confused about the following IM passwords:
    httpbind.password = "adminpass"
    avatar.password = "adminpass"

    I've changed the passwords in the doc as I go.

    Are you setting the httpbind and avatar passwords here? Or are the previously set?

    1. Aug 06, 2008

      I have always found this to be confusing.

      For example:

      httpbind.jid = "hostname1.httpbind.your.domain"
      httpbind.password = "foobar"
      avatar.jid = "hostname1.httpbind.your.domain"
      avatar.password = "foobar"
      

      The JID is arbitrary in that it is not a DNS name but a string that you assign so that IM can talk to Convergence.

      By the same token, the JID password is also arbitrary, however, the value needs to match up with what you will tell Convergence as you configure it.

  20. Mar 04, 2009

    Karl & Nate--
    On the page, Completing the Sun Convergence Installation: Initial Configuration, have a look at the section, Configure IM Components to Enable Communication with the Instant Messaging Server. In particular, look at the heading, About the Httpbind Component JID and Avatar Component JID.

    Hope this helps.

  21. Aug 13, 2008

    I'm getting the following error when installing SUN IM:

    Registering services with Access Manager... failed.
    Starting Services ... skipped.
    The install log also gives:

    Running external command: /usr/bin/pkginfo SUNWascmnse
    Err: ERROR: information for "SUNWascmnse" was not found
    The webserver is running as root.

    It's possible that it's already registered since this is the 2nd time I installed IM. How can I check that?

    1. Aug 13, 2008

      Karl,

      I'll try and get an answer for you. Stay tuned.

      • Joe
  22. Aug 15, 2008

    Hi Karl,
    Was your AM server up and running while you ran IM configurator,if your AM server is not up you will get the "Registering services with access Manager..failed" message

    To check if services are already assigned,You can login to amconsole,select the organization,select Services from View drop down list and check if the "Instant Messaging Service" and "Presence Service" is assigned.

    HTH,
    Swetha

    1. Aug 15, 2008

      Swetha,

      I don't see the "Instant Messaging Service" and "Presence Service" in AM. ./configure dums this to the console:
      exist exception - AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
      Check AMConfig.properties for the following properties
      com.sun.identity.agents.app.username
      com.iplanet.am.service.password
      exist exception - AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
      Check AMConfig.properties for the following properties
      com.sun.identity.agents.app.username
      com.iplanet.am.service.password
      add exception - AdminTokenAction: FATAL ERROR: Cannot obtain Application SSO token.
      Check AMConfig.properties for the following properties
      com.sun.identity.agents.app.username
      com.iplanet.am.service.password

      As far as i understand, the AM server runs on top of SUN Webserver 7.0.

      Also, the SUNIM configure didn't ask me for AM credentials. Which seems odd to me.

      Karl

      1. Aug 18, 2008

        Karl,

        Our one of our IM experts suggests the following:
        1. The httpbind.library.checkpermission error can be ignored, it does not affect functionality.
        2. It may be better to have httpbind configured to connect to the IM server directly on port 5269, rather than the IM multiplexor on port 5222.
        3. Providing relevant snippets of xmppd.log would help.
        4. Is IM working at all? Is it possible to connect using any other client (other than convergence)?

        • Joe
        1. Aug 18, 2008

          Joe,

          Could it be that you were responding to ethoms.

          I have placed a service call in regards to my issue. Hopefully this can get resolved in a timely fashion.

          Karl

          1. Aug 18, 2008

            Karl,

            Yes, I meant to reply to ethoms. Thanks for pointing that out.

            • Joe
  23. Aug 15, 2008

    Karl,

    Yes you are right amserver runs in your web container.
    SUNIM configure does not ask for AM credentials,it asks your Directory Server credentials through which it can talk to AM.
    I hope you have installed AM,DS and IM on the same machine,if not if you have remote AM server you need to have AM SDK installed on the machine where IM is installed.
    Was your web container running while you ran IM configurator ?

    Swetha

    1. Aug 15, 2008

      AM, DS and IM are on the same machine. The web container was running.

      DS is running on port 1389. I wonder if the AM portion of the configure is hard coded to use 389 even though I specified 1389.

      1. Aug 15, 2008

        I dont think it is an issue with IM.I suspect it's issue with AM,you could check out the AM debug logs.Try restarting
        webcontainer and then run IM configurator

        1. Aug 15, 2008

          do you mean the logs in /var/opt/SUNWam/logs

          1. Aug 15, 2008

            No the logs in /var/opt/SUNWam/debug

  24. Oct 15, 2008

    Hi,
    During Calendar Server configuration if we modify "ics.conf" in order to use another local than "en", would it work look for config at install_dir_cal/config/any_language ? I mean modify the values of:
    caldb.smtpmsgfmtdir =

    1. Oct 15, 2008

      Hirva,

      Per one of our Calendar experts: "This config specifies the language directory to be used for mail format files for event notification etc. The default is "en", but you can change this config to use another language that is present in config directory."

      Joe

  25. Oct 16, 2008

    Thanks for this amazing guide. I came across a problem I want to share looking for help:

    Step 15 mentions to install "java_es-5u1-identsuite"

    That files does NOT exist anymore. The available option is the above but sadly has a very buggy installer:

    bash-3.00# ls -l
    total 932754
    rw-rr- 1 ebartok other 477322286 Oct 16 13:38 java_es-5-identsuite-ga-solaris-sparc.zip

    Does this package do the trick ?

    thanks,

    1. Oct 17, 2008

      fabiomiranda:

      Are you looking for the Identity Suite zip file? You need to get it from the Identity download site, not the Comms download site. The Identity download site is at:

      The http://www.sun.com/software/products/identity/offerings.jsp site

      One you get the zip file, "java_es-5-identsuite-ga-solaris-sparc.zip" and unzip you should have a directory that says "java_es-5u1-identsuite".

      Joe

  26. Oct 22, 2008

    My system have 1000 mail box with 100MB for each user.

    With this guide mail boxes will be store in /var/opt/sun/comms/messaging64 ?

    I want to confirm because my storage mount to /data so I can change Database location of Messaging Server 7.0 to /data/opt/comms/messaging64.

    Regards,
    Thai Nguyen

    1. Oct 23, 2008

      Thai:

      One of the first questions during the messaging server configuration is the directory to store the data and config files. By default this is /var/opt/sun/comms/messaging64 or /var/opt/sun/comms/messaging (depending on if you are using 32-bit or 64-bit versions). If you prefer an alternate location, you would enter your preferred directory path at this time.

      • Joe
  27. Oct 30, 2008

    Thanks joesciallo.

    After configure Communication Express the Mail tab does not appear in CE:

    • local.webmail.sso.uwcenabled -->set to 1 already:

    root@mail2 # ./configutil |grep local.webmail.sso.uwcenabled
    local.webmail.sso.uwcenabled = 1

    • web port set to 2080 already:
      service.http.port = 2080
    • Port 2080 open already:

    root@mail2 # netstat -a |grep 2080
    .2080 *. 0 0 49152 0 LISTEN
    root@mail2 #

    Is there any advice for me to resolve this problem?

    Thanks & Regards,
    Thai Nguyen

    1. Nov 03, 2008

      Thai,

      I'll check w/ our experts and get back to you. You could also try posing this question on the Messaging Server forum that is regularly monitored by Sun Comms support folks: http://forums.sun.com/forum.jspa?forumID=708

      Joe

      1. Nov 03, 2008

        FYI, I just ran through the steps in this document for installing and configuring CE and I was successful in getting the CE UI to be configured for all tabs. So there must be some mis-configuration going on.

        1. Nov 03, 2008

          Thai,

          The usual cause of the mail tab not appearing in CE is when local.webmail.sso.uwcenabled has not been set to 1. It sounds like you have this correct but double-check to be sure.

          Next, enable CE logging and then check the uwc.log file for any mail related error messages. Also, check the Messaging Server http.log file to see whether there is any errors there. For example, see if you have any admin username/password setting errors.

          Joe

  28. Nov 02, 2008

    Hi everybody at Comms Community,

    I hope, here is the right place to place this record. If not, I´ll be happy to get tips.

    We are a small group of individuals (Java developer, Internet and Linux specialist), located in Germany.
    Our decision is to learn Comms (by use of Sun online resources) and deploy it to 2 small organizations (a NPO and a non-profit high school, with 20 / 50 system-users). Then we will establish an IT company to perform professionally medium-sized deployment of Comms (up to 200 system-users) incl. training and support.
    In further step we will develop a new Comms´s service (for fixed and mobile clients), integrated with Convergence, which can reach broad range of organizations.

    I ´m well aware, that all these tasks are not easy but we already started the work.

    *                                                                               **

    Since 3 days I´m busy with the Comms wiki and product homepage at SDN to locate resources and information, necessary for learning and first test-deployment using Single Host deployment on Solaris 10 / X64 platform. So I got some questions and need your help to go on.

    About Solaris OS: (We are very new to Solaris but will use it instead Red Hat Linux)

    1.- Solaris 10 Update 4: Where to download it ? (if it is not the same as Solaris 10 10/08)

    2.- Do we have to pay license for Solaris? We want to use a free Solaris binary distribution.

    3.- For Test-Installation: Single Host deployment on Solaris 10 / X64 vs. Solaris 10 / Sparc platform: Any difference between them? What is to care?

    Others
    4.- Does Application Server 9.1 U1 have an integrated Java System Web Server inside?

    5.- What is NSS?, Where can I read about it?

    We will contribute the result of our deployment to community, make it easier to newcomer to get started with this very valuable software system.

    Thank you in advance,
    Asghar

    1. Nov 03, 2008

      ashghar33:

      Welcome aboard. Please do keep us informed of your progress on your Comms deployment. You might also find these resources helpful for answering Comms questions:

      Forums

      The E-Mail, Calendar, and Collaboration Forums serve the Sun Java Communications Suite community, and are continually monitored for feedback and issue resolution.

      Messaging Server, Calendar Server, and Instant Messaging Forums

      If you like, go directly to one of the component product forums:

      • Sun Java System Messaging Server Forum
      • Sun Java System Calendar Server Forum
      • Sun Java System Instant Messaging Forum

      Note: Anyone can browse through the forum, but if you want to post a question or respons, you need to sign in by using your Sun Developer Network Online Account ID.

      Email Aliases

      Info-iMS Mailing List
      Info-iMS@Arnold.com is the independent discussion forum for those individuals interested in the Sun Java Enterprise System, Sun ONE, and iPlanet communication and directory software products. These products include the iPlanet Messaging Server, Sun ONE Messaging Server, Sun ONE Calendar Server, Sun ONE Instant Messager, Sun ONE Directory Server, and Sun Java System components: Messaging Server, Calendar Server, Instant Messaging, and Directory Server. (The forum is named "Info-iMS" for historical reasons.) The discussion forum is an Internet mailing list with associated archives.

      • Subscribe to the Info-iMS mailing list
      • View the Info-iMS archives

      re: your questions, I'll ask our experts and get back to you.

      Joe 

    2. Nov 03, 2008

      ashghar33,

      Replies to your questions.

      Joe

      1.- Solaris 10 Update 4: Where to download it ? (if it is not the same as Solaris 10 10/08)

      You can use any Solaris 10 Update 4 or later. Solaris 10 10/08 is Update 6 which is perfectly fine to use.

      2.- Do we have to pay license for Solaris? We want to use a free Solaris binary distribution.

      Sorry, can't say for Solaris.

      3.- For Test-Installation: Single Host deployment on Solaris 10 / X64 vs. Solaris 10 / Sparc platform: Any difference between them? What is to care?

      There should be no difference in the operation of Comms Suite between x86 and SPARC platforms. The only differences are the names of certain binaries and zip files.

      4.- Does Application Server 9.1 U1 have an integrated Java System Web Server inside?

      The Application Server has an integrated web container but it is not the same as the Sun Java System Web Server.

      5.- What is NSS?, Where can I read about it?

      NSS – Network Security Services. A set of libraries for client and server security developed by Netscape. You can read more about it at http://en.wikipedia.org/wiki/Network_Security_Services

      1. Nov 06, 2008

        Hello Joe,

        Thank you for help.

        The first deployment of comms 6 on Solaris 10 Update 4 (X64 platform) is done and works, but not completely.
        I was not able to install the Convergence, because comm-installer asks for a newer version of comm_dssetup.pl. I downloaded it via Solaris Update service, but not able to install it (because of failed verification of signature). Also I must learn more about Solaris. That is what I will do during next time.
        Than remove completely comms and other required software products (AS, DS, AM and Web server) and try again.
        As you mentioned, I feel, it´s better to use the Solaris 10 update 6 (10/08).

        Asghar

      2. Nov 09, 2008

        Hi Joe,

        I installed Solaris 10 Update 6 (10/08) and comms 6 on a no-name PC with 2 GB RAM and AMD dual CPU and it runs perfectly. All services are available now.
        Im using different domain and host name as those used in single host deployment.

        For initial tests I used 2 clients driven by Solaris and Win XP, having UK and Germany as set locale respectively. Convergence automatically detects the set locale of native platform and configure itself correctly. Great!
        The comms is really a pretty suite.

        Thank you to Sun and comms commu.
        Asghar

        1. Nov 10, 2008

          Good to hear Asghar.

          Joe

  29. Nov 06, 2008

    After installing the access manager, I try to go to http://fully-qualified-hostname:web-server-port/amconsole to verify the installation but I get an error instead of a login page that reads "Authentication service is not initialized".
    Directory server is definitely running.
    I have an error in the webserver logs that reads:
    failure (27061): for host 192.168.100.62 trying to GET /amserver/UI/Login, service-j2ee reports: StandardWrapperValve[LoginServlet]: PWC1406: Servlet.service() for servlet LoginServlet threw exception
    Can anyone help me get past this error?
    Many thanks

    1. Nov 06, 2008

      Just also noticed that when I start the webserver I get this error:
      failure: Webmodule[/amserver]StandardWrapper.Throwable
      java.lang.NullPointerException

      It's probably worth me mentioning that I didn't follow the directory suffix creation exactly as in the example - instead I created a differently named suffix and imported our old directory data into it.

      1. Nov 06, 2008

        stainlesssteelrat:

        The name of the directory suffix shouldn't matter, but the new name must be substituted consistently whereever it shows o=isp. So you should double-check that throughout. Also, the default Application Server port is 8080 and the Web Server port is also 8080. If you did not set the Application Server port to 80, you will certainly run into problems when starting Web Server.

        Stop Application Server and then start Web Server and see if the problem goes away. If it does, that means both services are using the same port.

        • Joe
  30. Nov 06, 2008

    Note for Getting Problems Addressed and Resolved

    In the future, please use the comments feature on this page to address specific issues with this document. For questions concerning problems with your deployment, please use either the Sun Messaging Server forum (http://forums.sun.com/forum.jspa?forumID=708) or open a support call with Sun.

    Thanks,

    Joe

  31. Nov 12, 2008

    At the install Identity Suite step, and also if you try it with java enterprise suite, it is impossible to complete the installer with out installing the outdated version of the directory server and the outdated version of the application server even when selecting the remote option. The validating phase fails and there is no apparent way to circumvent it.

  32. Nov 25, 2008

    Excellent guide, I already have Java Communications Suite 6 Working (of course with the help of this guide ), but, I have a Leak Memory problems with imapd process.
    I have the server with 30 imapd process, 30 mshttpd process, and 30 pop process running to balance the load of the users.
    All work fine when I access via browser(Chrome,Firefox), too when I access it with the traditional clients IMAP (Outlook, ThunderBird,etc).

    The problem is that if one user want to copy(no t just view) locally all your emails, the imapd process eat more than 3GB of RAM and the system is getting slower.
    The solution is:

    1. kill -9 <PID_imapd>
      I think that this problem is a bug but I dont know what is the patch.
      May you help me? Any idea?

    My system is:
    A X2100 with one socket AMD Opteron 2600Mhz, 8GB RAM, 2 x disks 750GB in mirror with Solaris Volume Manager, Soalris 10 HW 10/08.

    Thanks.

    Jaime

  33. Nov 30, 2008

    Thanks a lot for this tutorial. I have now everything up and running. But there's this small thing. When I log into Convergence, I have this Buddy list on the right side and it just says "connecting...". Here's a screenshot: http://tmp.valiyev.net/convergence.png

    I have tested IM by running the java client and it worked. Do you know how I can fix this?

    1. Nov 30, 2008

      For questions concerning problems with your deployment, please use either the Sun Messaging Server forum (http://forums.sun.com/forum.jspa?forumID=708) or open a support call with Sun.

      Regards,

      Shane.

  34. Sep 24, 2009

    which one is correct?

    Link http://wikis.sun.com/display/CommSuite6/Sun+Java+Communications+Suite+6+on+a+Single+Host says to change 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^fs^g;@c^g;@^p^r^g" (A)

    Link http://wikis.sun.com/display/CommSuite6U2/Sun+Java+Communications+Suite+6+Update+2+on+a+Single+Host says to change 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" (B)

    Is there a TYPO in the (B)? see carefully.. @c^ ?
    what is the correct ACL to change to?

    -vezee

  35. Oct 28, 2009

    Hi

    I have installed communication suite 6 update 2 on Solaris 10 Sparc in single host. In the default domain i added 100 earth service package.
    when I am trying to add 1 package of this type to one user of this organization it gives me service for this user exceeds allocation maximum.
    Is this becouse communication suite 6 is without license or is something wrong in my installation?

    Regards,
    TikaAmc

    1. Oct 28, 2009

      TikaAmc:

      For questions concerning problems with your deployment, please use either the Sun Messaging Server forum (http://forums.sun.com/forum.jspa?forumID=708) or open a support call with Sun.

      Joe

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.