Sun Java Communications Suite 7 on a Single Host

Skip to end of metadata
Go to start of metadata

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

This deployment example describes how to install Sun Java Communications Suite 7 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 7. These instructions are not intended to act as a replacement for the individual component documentation, but to merely guide the evaluator through an initial installation.

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 Update 3
  • Sun Java System Calendar Server 6.3
  • Sun Java System Calendar Server 7
  • Sun Java System Instant Messaging 8 Update 2
  • Sun Java System Directory Server 6.3.1
  • GlassFish Enterprise Server 2.1 Patch 2 with HADB support
  • Delegated Administrator 7
  • Sun Convergence 1 Update 3
  • Sun Java Indexing and Search Service 1
  • All Shared Components

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

  • Domain name: comms.beta.com
  • Host name: 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 4848 for the GlassFish Enterprise Server admin port. If you decide to use port 3333 instead, be sure to change it everywhere 4848 occurs in the deployment example. See Table 3 for more information.

Implementation Specifications for This Example

This section describes implementation specifications for this example.

Table 1 Evaluation Host Hardware and Software Requirements

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. 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, Safari 3.1.x


Table 3 Server Configuration Information

Component Install Notes Install Location Database Location Port Name Port Number
GlassFish Enterprise Server 2.1 Installed separately. Required for Convergence /opt/SUNWappserver Not Applicable HTTP Port 80
        Admin Port 4848
        HTTPS Port 8181
Directory Server 6.3.1 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 Update 3 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
Calendar Server 6.3 Installed using Communications Installer. Additional configuration required. /opt/sun/comms/calendar/SUNWics5 /var/opt/sun/comms/calendar/SUNWics5 Calendar Server Port 3080
        LDAP Port 389
Instant Messaging 8 Update 2
Installed by using Communications Installer. Additional configuration required. /opt/sun/comms/im /var/opt/SUNWiim XMPP Port 5222
        Multiplexed XMPP Port 45222
        Admin Port 4848
        XMPP Server Port
5269
GlassFish Enterprise Server 2.1
Installed separately. Required by Calendar Server 7
/opt/SUNWappserverCS
Not applicable
HTTP Port
8080
        Admin Port
6080
        HTTPS Port
random
Calendar Server 7
Installed by using Communications Installer. Additional configuration required.
/opt/sun/comms/davserver
/var/mysql/caldav
HTTP Port
8080
        Admin Port
6080
        HTTPS
random
Java Message Queue
Installed by Communications installer. Additional configuration required.
/etc/imq
Not applicable
JMQ Port
7676
MySQL Server
Installed by Communications installer. Additional configuration required. /opt/mysql
/var/mysql/caldav
MySQL Port
3306
Convergence 1 Update 3
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
Indexing and Search Service 1
Installed by using Communications Installer. Additional configuration required.
/opt/sun/comms/jiss   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 3 hours
Total 6 hours (average)

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

Note
Communications Suite 7 is supported on Solaris OS 10. This example uses Solaris OS 10 Update 6.

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.
  2. 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. Running the Communications Installer to install Messaging Server 7 Update 3, Calendar Server 6.3, Calendar Server 7, Instant Messaging 8 Update 2, Delegated Administrator 7, Convergence 1 Update 3, and Indexing and Search Service 1
  3. Installing and configuring Directory Server 6.3 with 6.3.1 patch
  4. Installing and configuring GlassFish Enterprise Server 2.1
  5. Preparing Directory Server for Communications Suite
  6. Configuring Delegated Administrator 7 and Communications CLI
  7. Configuring Messaging Server 7 Update 3
  8. Configuring Calendar Server 6.3
  9. Configuring Instant Messaging 8 Update 2
  10. Configuring Convergence 1 Update 3
  11. Configuring Indexing and Search Service 1
  12. (Optional) Configuring Calendar Server 7
  13. Configuring users

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

Installing the Example

This section describes how to install and configure components on a single machine for evaluation purposes. Some components are configured after installation, using component configuration tools.

Note
Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as 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

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.
    svcadm disable sendmail
    
Note
If end users (or system utilities, for example, cron) send messages through sendmail clients, you can configure Messaging Server to work with those clients over protocol. Users can continue to use the UNIX sendmail client. See Handling sendmail Clients.

Installing Communications Suite 7 Software

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

To Install the Communications Suite Software

  1. Create a /tmp/JCS7 directory, unzip the Communications Suite 7 software zip file in this directory, then run the Communications Suite 7 Installer.
    # cd /tmp/JCS7
    # ./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 following components for installation.
    • Messaging Server (64bit) 7u3 (7.3-11.01)
    • Comms DSsetup 6.4 (6.4-5.05)
    • Calendar Server 7 (7.0-0.26)
    • Instant Messaging 8u2 (8.2-02.04)
    • Convergence 1u3 (1.0-10.01)
    • Indexing and Search Service 1 (1.0-32.01)
    • Comms Delegated Administrator 7 (7.0-1.00)
    • Calendar Server 6.3 (6.3-19.01)
      This corresponds to selections 1, 2, 3, 4, 5, 6, 7, and 10.
  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.
    The installation Proceeds.
  9. You are reminded to set a password for the MySQL root USER.
    You do this later if you decide to install Calendar Server 7.
  10. Press RETURN when prompted to continue.

Installing and Configuring Directory Server

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. Before you proceed, make sure that you have both the Directory Server 6.3 software and the Directory Server 6.3.1 patch.

  1. Create the /tmp/DS directory and copy the Directory Server 6.3 bits to this directory. Uncompress and untar the Directory Server 6.3 bits then run the installer.
  2. Press Enter to continue when prompted.
  3. Accept the License Agreement by typing yes when prompted.
    The installation proceeds and installs the Directory Server bits in the specified location /opt/SUNWdsee.
    Note
    If the installation does not proceed because thet cacao port 11162 is in use, shut down cacao then run the dsse_deploy command again:
  4. Create your Directory Server instance.
  5. Start your Directory Server instance.
  6. Test your Directory Server instance.
  7. Create the root suffix o=isp by using the dsconf command:
    ./dsconf create-suffix -h hostname -p 389 o=isp
    In this example, type:
  8. Accept the Certificate and type adminpass as the cn=Directory Manager password.
  9. Before applying the Directory Server 6.3.1 patch, stop your Directory Server instance.
  10. Create the /tmp/DS/Patch subdirectory and copy the Directory Server 6.3.1 patch to this directory. Uncompress and untar them. Then run the installer.
  11. Press the Enter key to continue when prompted.
  12. Accept the License Agreement by typing yes when prompted.
    The installation proceeds and installs the Directory Server patch in the specified location /opt/SUNWdsee.
  13. Start your Directory Server instance.
  14. Confirm your Directory Server instance has been upgraded to Directory Server 6.3.1.

Installing and Configuring GlassFish Enterprise Server

The GlassFish Enterprise Server 2.1 patch 2 with HADB is the primary web container used by Convergence and Indexing and Search Service.

  1. Prior to installing GlassFish Enterprise Server, check the Java version on the system. GlassFish Enterprise Server requires at least Java 1.6.0. Solaris OS 10 Update 6 ships with version 1.5.0_16, which is not sufficient for Instant Messaging and other Communications Suite components. To check your version type the following command:

    If the version is not at least 1.6.0, check to make sure that /usr/java and /usr/jdk/latest link to jdk1.6.0_16.

  2. Create the /tmp/GLASSFISH directory, copy the GlassFish Enterprise Server 2.1 Patch 2 bits to this directory, then launch the installer.
  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 GlassFish Enterprise 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 1.5.0 or greater [/usr/jdk/instances/jdk1.6.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. The installation proceeds.
  6. Change the JMQ port from 7676 to 37676 to avoid any future conflict with the JMQ instance that will be used by Indexing and Search Service.
    Note
    By default, GlassFish Enterprise Server starts a bundled instance of JMQ on port 7676. This port assignment conflicts with the instance of JMQ used by Indexing and Search Service. For this reason, you need to change the port that the GlassFish instance uses to avoid any future conflict.
  7. Start the GlassFish Enterprise Server:
  8. Continue with the next task.

To Verify GlassFish Enterprise Server

  • In your web browser, open a URL for GlassFish Enterprise Server. The URL is:
    http://fully-qualified-hostnameIn this example, type: http://wireless.comms.beta.com

Configuring Components

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

This section contains the following topics:

Preparing the Directory

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

To Apply Schema 2 to Your Directory Tree

  1. Change to the directory where the comm_dssetup script is located and run the script, for example:
  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? [1] 2
    Confirm Schema Type
    [n]
    y
    Update the schema files? [yes] accept default
    Configure new indexes? [yes] accept default
    Reindex new indexes? [yes] accept default
  3. Confirm your choices and type y to continue.
    The comm_dssetup 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. Set the JAVA_HOME environment variable.
    For example, if you are running csh, type:
  2. Change to the directory where the configuration script was installed and run the script, for example:
  3. Click Next in the Welcome window.
  4. Accept the default for the Directory to store Configuration and Data Files: /var/opt/sun/comms/da.
    If the directory does not exist, click Create Directory to create the directory.
  5. 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] 80
    Default Domain [comms.beta.com] accept default
    Default SSL Port [443] accept default
    Web Container [Web Server 6.x] App Server 8.x and up
    Install Root Directory (for DA Console) [/opt/SUNWappserver/appserver] /opt/SUNWappserver
    Domain Directory
    [/var/opt/SUNWappserver/domains/domain1]
    /opt/SUNWappserver/domains/domain1
    Domain Root Directory [/var/opt/SUNWappserver/domains/domain1/docroot]
    /opt/SUNWappserver/domains/domain1/docroot
    Server Target Name [server] accept default
    Virtual Server Identifier [server] accept default
    Server Instance HTTP Port [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [checked] Checked (secure)
    Default Domain Separator [@] accept default
    Access Mode Direct LDAP accept default
    Web Container (DA Server)
    [Web Server 6.x] App Server 8.x and up
    Install Directory (for DA Server) [/opt/SUNWappserver/appserver]
    /opt/SUNWappserver
    Domain Directory [/var/opt/SUNWappserver/domains/domain1]
    /opt/SUNWappserver/domains/domain1
    Document Root Directory
    [/var/opt/SUNWappserver/domains/domain1/docroot]
    /opt/SUNWappserver/domains/domain1/docroot
    Server Target Name
    [server] accept default
    Virtual Server Identifier [server] accept default
    Server Instance HTTP Port [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [checked] Checked (secure)
    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
    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
  6. Click Configure Now.
    The script begins to run.
  7. When the panel displays "All Tasks Passed," click Next to continue.
    Two warnings appear: one reminds you to restart the GlassFish Enterprise Server; the other reminds you to enable the mail and calendar services in the domain. The next steps complete these steps.
  8. Click Close to exit the Delegated Administrator Configuration wizard.
  9. Restart the GlassFish Enterprise Server.
  10. 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 -n comms.beta.com -d comms.beta.com -S mail,cal,im -H wireless.comms.beta.com -B wireless.comms.beta.com
    /opt/sun/comms/da/bin/commadmin user create -D admin -F John -l jdoe -L Doe -n comms.beta.com -w adminpass -W demo -S mail,cal,im -E jdoe@comms.beta.com -H wireless.comms.beta.com -B wireless.comms.beta.com
    
    /opt/sun/comms/da/bin/commadmin user create -D admin -F Calendar -l calmaster -L Master -n comms.beta.com -w adminpass -W adminpass -S mail,cal -E calmaster@comms.beta.com -H wireless.comms.beta.com -B wireless.comms.beta.com
    
    /opt/sun/comms/da/bin/commadmin user create -D admin -F Calendar7 -l calmaster7 -L Master -n comms.beta.com -w adminpass -W adminpass -S mail,cal -E calmaster7@comms.beta.com -H wireless.comms.beta.com -B wireless.comms.beta.com
    
    You can create as many users as you like at this point.

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:app-server-port/da/DA/Login
    In this example, type: http://wireless.comms.beta.com/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:

    The Configuration Wizard appears. Read the introductory information and proceed by clicking Next.

  2. Verify the following:
  • Directory to store config/data files: [/var/opt/sun/comms/messaging64]
  • Name of the mail server Unix user: username [mailsrv]
    You might need to change to mailsrv2 if this was the actual user created previously.
  • Fully qualified host name of messaging server, FQHN: [wireless.comms.beta.com]
  1. 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:
    Default Mail Domain Name
    [comms.beta.com] accept default
    Hostname for LDAP Directory Server [localhost] wireless.comms.beta.com
    LDAP Administrator Login [cn=Directory Manager] accept default
    Password
    - adminpass
    Postmaster email address [admin@comms.beta.com] foo@wireless.comms.beta.com
    Password for Server Administration - adminpass
  2. The Messaging Server configuration proceeds.
    You might receive an error about the address foo not being in the mail domain. You can ignore this error or you can create such a user if you want.
  3. Configure the webmail port.
  4. Start Messaging Server:
  5. Continue with the next section to configure Calendar Server 6.3.

Configuring Calendar Server 6.3

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

  1. Change to the directory where the configuration script was installed then run the configuration script, for example:
  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.
  7. Remove the comments from the following values to enable Calendar Server alarms:
  8. Consider changing the following values:
  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:
  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:

      to America/Los_Angeles (or your preferred time zone).

  12. Start the Calendar Server daemons, for example:
  13. 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:

    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] accept default
    Use AM for Policy
    [no]
    accept default
    Wher to Store IM User Data
    [On the file system]
    In the directory
    Runtime User ID [inetuser] accept default
    Runtime Group ID [inetgroup] accept default
    Runtime Directory [/var/opt/SUNWiim] accept default
    Create User ID
    [Choose New]
    Create User ID
    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:80/im*
    Enable Audio [no] yes
    Webcontainer Path -- /opt/SUNWappserver
    Web Administration URL -- *https://wireless.comms.beta.com:4848/*
    Web Administrator User Id [admin] accept default
    Web Administrator Password -- adminpass
    Deploy IM HTTP Gateway [yes] no
    Deploy IM IMPS Gateway [yes] accept default
    Context Root [http://wireless.comms.beta.com:80/imps] *http://wireless.comms.beta.com:80/imps*
    Webcontainer Path [/opt/SUNWappserver] accept default
    Web Administration URL [https://wireless.comms.beta.com:4848/] 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
  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.

    You will add the new httpbind and avatar component JIDs to this file by making the following changes/additions:

  6. Edit the iim.conf file to enable Hosted Domain Schema 2 support.
  7. Start the Instant Messaging server.
    For example:
  8. 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.
  9. 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.jnlp
    In this example, type: http://wireless.comms.beta.com/im/en/im.jnlp
  2. Continue with the next section to configure Sun Convergence.

Configuring Sun Convergence

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

  1. Run the Convergence configuration script.
  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
    GlassFish Enterprise 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/iwc
    In this example, type: http://wireless.comms.beta.com/iwc

Configuring Indexing and Search Service 1

  1. Enable the NTP service for the Messaging Server and Indexing and Search Service host machine.
  2. Configure the IMQ broker on Messaging Server.

    The following changes will most likely be necessary:

  3. Check for the existence of the /var/imq/instances/imqbroker/props/config.properties file. If it does not exist, start the IMQ broker to generate it.
  4. Edit the following information at the bottom of the /var/imq/instances/imqbroker/props/config.properties file.
  5. Restart the IMQ broker to pick up the changes.
  6. Create the JMQ user by using the imqusermgr command.
  7. Reset the default account passwords.
  8. Set the local.store.notifyplugin configutil parameter to include a JMQ notification named index.

    If no response is returned, execute the following command:

  9. Configure the index JMQ notification plugin by using the configutil command.
  10. Restart Messaging Server, and verify that the JMQ index plugin is working.
  11. Verify that the IMQ broker started up cleanly.
  12. Verify that the Messaging Server has producers connected to INDEXMS.
  13. Prepare the Messaging Server to forward IMAP SEARCH queries to Indexing and Search Service.
  14. Restart Messaging Server.

    Change directories to where the configuration script was installed and run the configuration script:

    The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 17 Values for Indexing and Search configure Script

    Option [Default Value] Enter
    Fully qualified domain name of system (hostname) -- wireless.comms.beta.com
    User under which all JISS services will run (iss.user) [jiss] accept default
    Group under which all JISS services will run (iss.group) [jiss] accept default
    Location of Java (java.home) [/usr/jdk/latest] accept default
    User/Group Directory Server format (mail.ldap) [none] ldap://wireless.comms.beta.com:389
    User/Group Base DN format (mail.basedn) [none] o=isp
    User/Group Default Domain (mail.defaultdomain) [none] comms.beta.com
    User/Group Directory Manager DM (mail.searchbind) [cn=Directory Manager] accept default
    User/Group Directory Manager password (mail.searchbind.password) [none] adminpass
    Messaging Server store hostname (mail.server) [none] wireless.comms.beta.com
    Comma-delimited list of mail server IPs (mail.server.ip) [none] Enter IP address of wireless.comms.beta.com such as 192.18.49.94
    Read-only store admin username (mail.imap.admin.username) [indexeradmin] accept default
    Read-only store admin password (mail.imap.admin.password) [none] adminpass
    Messaging Server IMAP port (mail.imap.port) [143] accept default
    Messaging Server JMQ broker (mail.imq) [none] wireless.comms.beta.com:7676
    JMQ notification user (mail.imq.user) [jmquser] accept default
    JMQ notification user's password (mail.imq.password) [none] adminpass
    Directory location of the appserver (appserv.dir) [/opt/SUNWappserver] accept default
    Appserver web port (appserv.web.port) [8080] 80
    Appserver admin port (appserv.admin.port) [4848] accept default
    Appserver admin user (appserv.admin.user) [admin] accept default
    Appserver admin user's password (appserv.admin.password) [none] adminpass
    JISS JMQ broker hostname (imq.host) [none] wireless.comms.beta.com
    JISS JMQ broker port (imq.port) [7676] accept default
    Username for JISS JMQ broker (iss.imq.user) [jmquser] accept default
    Password for JISS JMQ user (iss.imq.password) [none] adminpass
    Password for admin user on JISS JMQ broker (iss.imq.admin.password) [none] adminpass
    JISS Directory Server host (ldap) [none] wireless.comms.beta.com
    JISS Directory Server port (ldap.port) [389] accept default
    JISS Directory Manager DN format (java.naming.security.principal) [cn=Directory Manager] accept default
    JISS Directory Server password (ldap.password) [none] adminpass
    Storeui access method (iss.storeui.access.method) [disk] accept default
  15. Bootstrap existing users to create their index by using the following command:
  16. Test that search works.
    Type the URL of the Search UIs in your browser and log in as a user.
  17. Configure Messaging Server to use Indexing and Search Service:
  18. Configure Convergence to use Indexing and Search Service:
  19. Increase processor threads to support Convergence and Indexing and Search Service in the same web container.
    Note
    This example sets the processor threads to 8. The actual number should be twice the number of CPUs or virtual CPUs. Thus, if the number of CPUs or virtual CPUs is 4, the thread count should be set to 8. If the number of virtual CPUs is 128, the thread count should be set to 256. The find the number of CPUs or virtual CPUs on your host, use the mpstat command.
  20. Restart the GlassFish Enterprise Server.

(Optional) Configuring Calendar Server 7

  1. Install a second instance of Glassfish that runs on port 8080.
  2. 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 18 Values for Calendar Server7 configure Script
    Option [Default Value] Enter
    Installation Directory [/opt/SUNWappserver] /opt/SUNWappserverCS
    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 New or Reuse existing Java 2 SDK [Install Java 2 SDK] Reuse existing (as long as correct version)
    Path to Java 2 SDK Version 1.5.0 or greater [/usr/jdk/instances/jdk1.6.0] accept default
    Admin User [admin] accept default
    Admin User's Password -- adminpass
    Master Password (for SSL Certificate) -- adminpass
    Admin Port [38295] 6080
    HTTP Port [38292] 8080
    HTTPS Port [38298] accept default
    Enable Updatecenter client [yes] accept default
    Upgrade from previous AS version [no] accept default

    The installation proceeds.

  3. Start the GlassFish Enterprise Server.
  4. Set up the MySQL database for Calendar Server 7:
  5. Create the /etc/my.cnf file with the following content.
  6. Install the MySQL startup script.
  7. Start MySQL.
  8. Change the MySQL root password and remove test databases.
  9. Answer "y" to all questions except "Change the root password."
    No need to change the root password since this was already done. The mysql_secure_installation script:
    • Removes anonymous users
    • Disallows root login remotely
    • Removes test database and access to it
    • Reloads privilege tables
  10. Create the MySQL user and caldav database.
  11. Configure MySQL to start automatically upon reboot.
  12. Set the JAVA_HOME environment variable.
    For example, if you ar running csh:
  13. Change directories to where the configuration script was installed and run the Calendar Server 7 configuration script:
  14. Click Next at the Welcome page.
  15. Directory to store configuration and data files [/var/opt/sun/comms/davserver]
  16. Configure Sun Java System Calendar Server 7.
    The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 19 Values for Calendar Server 7 configure Script
    Option [Default Value] Enter
    Host Name [wireless] accept default
    DNS Domain Name [comms.beta.com] accept default
    MySQL Server Host Name [localhost] accept default
    MySQL Server Port Number [3306] accept default
    MySQL Database User ID [caldav] accept default
    MySQL Database User Password -- adminpass
    Calendar Database Name [caldav] accept default
    Application Server Install Directory [/opt/SUNWappserver] /opt/SUNWappserverCS
    Application Server Domain Directory [/opt/SUNWappserverCS/domains/domain1] accept default
    Application Server Document Root Directory [/opt/SUNWappserverCS/domains/domain1/docroot] accept default
    Appserver Instance Name [server] accept default
    Virtual Server Identifier [server] accept default
    Instance HTTP Port [8080] 8080
    Administration Server Port [4848] 6080
    Administrator User ID [admin] accept default
    Administrator Password -- adminpass
    Secure Administration Server Instance checked accept default (Is Secure)
    URI Path [/] /davserver
    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
    SMTP Server Host Name [wireless.comms.beta.com] accept default
    SMTP Server Port Number [25] accept default
    Calendar Administrator User ID [calmaster] calmaster7
    Calendar Administrator User Password -- adminpass
  17. Click the "Configure Now" button to configure Calendar Server 7.
  18. After the configuration is complete, click Next to continue.
  19. Click Next to continue.
  20. Click Close to quit the Calendar Server configuration wizard.
  21. Restart the GlassFish Enterprise Server.

(Optional) Configuring Clients for Use with Calendar Server 7

To configure clients to use with Calendar Server 7, see Configuring CalDAV Clients. Use the following URLs when configuring clients for this example:

This example assumes that the default URI is /davserver.

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 Communications Services products.

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.

  1. Run the following Delegated Administrator commands.
    # /opt/sun/comms/da/bin/commadmin user create -D admin -F Demo -l demo1 -L One -n comms.beta.com -w adminpass -W demo -S mail,cal,im -E demo1@comms.beta.com -H wireless.comms.beta.com -B 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 80 -w adminpass -W demo -S mail,cal,im -E demo2@comms.beta.com -H wireless.comms.beta.com -B wireless.comms.beta.com
    
    # /opt/sun/comms/da/bin/commadmin group create -D admin -G Demostaff -n comms.beta.com -w adminpass -S mail -E Demostaff@comms.beta.com -H wireless.comms.beta.com -o calmaster -m demo1 -m demo2
    
  2. Bootstrap the users you just created to create their index by using the following commands:
    Note
    Creating groups using the Delegated Administrator command-line interface will guarantee that these groups will be recognized 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.

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 GlassFish Enterprise Server.
  3. The first time you use Delegated Administrator, you must add service packs to the organization that contains your users:
  4. Log in as admin. 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. If you want to include Instant Messaging, choose the mailcalendarimsample package. 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 No 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.
    • If you selected a service package that includes Instant Messaging, you can leave the "User Roster" entry box blank.
    • 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.

Known Issues and Limitations

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

Labels:
installing installing Delete
example example Delete
commsuite commsuite Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Dec 16, 2009

    There may be an error in the calendar csconfigurator

    1. cd /opt/sun/comms/calendar/SUNWics5/cal/sbin
    2. ./csconfigurator.sh -nodisplay
      /usr/jdk/jdk1.5.0_21/bin/java -cp /opt/sun/comms/calendar/SUNWics5/cal/share/lib:/opt/sun/comms/calendar/SUNWics5/cal/share -Djava.library.path=/opt/sun/comms/calendar/SUNWics5/cal/lib configure -nodisplay
      Exception in thread "Thread-0" java.lang.InternalError: Can't connect to X11 window server using '192.168.0.13:3.0' as the value of the DISPLAY variable.
      at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
      at sun.awt.X11GraphicsEnvironment.access$000(X11GraphicsEnvironment.java:53)
      at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:142)
      at java.security.AccessController.doPrivileged(Native Method)
      at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:131)
      at java.lang.Class.forName0(Native Method)
      at java.lang.Class.forName(Class.java:164)
      at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:68)
      at sun.awt.motif.MToolkit.<clinit>(MToolkit.java:93)
      at java.lang.Class.forName0(Native Method)
      at java.lang.Class.forName(Class.java:164)
      at java.awt.Toolkit$2.run(Toolkit.java:821)
      at java.security.AccessController.doPrivileged(Native Method)
      at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:804)
      at javax.swing.UIManager.initialize(UIManager.java:1262)
      at javax.swing.UIManager.maybeInitialize(UIManager.java:1245)
      at javax.swing.UIManager.getUI(UIManager.java:851)
      at javax.swing.JPanel.updateUI(JPanel.java:104)
      at javax.swing.JPanel.<init>(JPanel.java:64)
      at javax.swing.JPanel.<init>(JPanel.java:87)
      at javax.swing.JPanel.<init>(JPanel.java:95)
      at com.sun.wizards.core.WizardComponent.<init>(WizardComponent.java:152)
      at com.sun.wizards.core.WizardComposite.<init>(WizardComposite.java:76)
      at com.sun.wizards.core.WizardTreeManager.createWizardPanel(WizardTreeManager.java:887)
      at com.sun.wizards.core.WizardTreeManager.<init>(WizardTreeManager.java:324)
      at com.sun.wizards.core.CommandLineConsole.run(CommandLineConsole.java:75)
      at java.lang.Thread.run(Thread.java:595)
      Unsuccessful installer exit status of: 0

    //

    1. java -version
      java version "1.6.0_16"
      Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
      Java HotSpot(TM) Client VM (build 14.2-b01, mixed mode, sharing)
    2. echo $JAVA_HOME
      /usr/jdk/latest
      root@sav037> ls -l /usr/jdk/latest
      lrwxrwxrwx 1 root other 11 Dec 15 14:38 /usr/jdk/latest -> jdk1.6.0_16

    Options recognized by the Sun Java System Calendar Configure Wizard:
    -nodisplay Run configurator in text only (non graphical) mode
    -noconsole don't display non graphical text. Used with
    nodisplay option for silent installs.
    -novalidate no text field validation checking
    -saveState [statefile] save state of configurator input
    -state [statefile] use the statefile for setting input values

    -debug general debug info from Sun Java System Calendar Server Configuration Wizard
    -debugMessage output debugging information, includes errors and warnings
    -debugWarning output warning message, includes errors
    -debugError output error messages, on by default

    1. Dec 17, 2009

      dvz-fhbo:

      Per one of our Calendar engineers:

      This appears to be a problem only when the DISPLAY environment variable is set. The problem seems to be in cnpsdk, which the Calendar configurator uses. As a workaround, try unsetting the DISPLAY environment variable, for example:

      bash$unset DISPLAY

      Joe

  2. Dec 21, 2009

    Hi joe,

    Can you specify which value in /opt/SUNWappserver/domains/domain1/domain.xml file should change? I have two entries.

    1. <jms-host name="default_JMS_host" host="testmail.test.com" port="7676" admin -user-name="admin" admin-password="admin"/>

    2. <system-property name="JMS_PROVIDER_PORT" value="37676"/>

    Thanks.

  3. Jan 08, 2010

    Did anyone configure Sun Java Mobile Communication on a single host (in this context Comms7 and mysql)?

    Thanks,
    Robert

  4. Jan 26, 2010

    Why Calendar Server 7 is being deployed using a second instance of GlassFish server? Can't one deploy it using a separate domain of the same server instance (asadmin create-domain ...)?

    Thanks,
    D.

    1. Jan 26, 2010

      d-v-k,

      Per the Sun person who developed this scenario:

      You can install in the original instance but you must be sure to specify a separate URI such as davserver, or something similar. (Don't use the default URI). Also, CalDAV uses the bundled instance of JMS that comes with GlassFish, so if something else is using it, there could be some configuration issues that you need to address.

      Joe

  5. Mar 14, 2010

    Got a problem on this:

    1. /opt/sun/comms/da/bin/commadmin domain modify -D admin -w adminpass -n comms.beta.com -d comms.beta.com -S mail,cal,im -H wireless.comms.beta.com -B wireless.comms.beta.com
      incorrect current password
      Invalid value for login ID: admin
      Invalid value for login password
      Invalid value for login domain: comms.beta.com
    1. Mar 15, 2010

      First, the obvious: This example assumes that the password for the admin ID is "adminpass". Is that what you chose to use?

      Joe

      1. Mar 15, 2010

        everything in this example was followed.

        Thanks

        1. Mar 16, 2010

          In that case, I suggest asking your question on the Message Server forum: http://forums.sun.com/forum.jspa?forumID=708

          • Joe
  6. Mar 20, 2010

    After following this guide, I found that the 'Attachments' in Convergnece provided by indexing and search service do not always load. The correct attachments show up but the image does not load, the circulating loading bar goes on forever. It can't be a configuration mistake because sometimes after restarting the application server, they do load.

    I how now increased the processing threads in application server to 12. So far so good. Perhaps the guide could elaborate on why it should be increased to 8, with other applications running on the appserver, perhaps it should be more than 8.

    #./asadmin set server.http-service.request-processing.thread-count=12

    1. Mar 22, 2010

      Here's what I found out:

      It should be set to 2x the number of CPUs on the system.

      The number of cores determine how many requests to the ISS backend from Convergence server can take place in parallel. When ISS is deployed in the same web container, the number of processing threads needs to be double that number, since it must cover both the connection from the frontend (Convergence server) and the connection to the backend (ISS storeui).

      Joe

  7. Apr 20, 2010

    Hi Guys,

    do you know why IE is so much slower than Firefox to finish loading the convergence page ?

    we can see at the bottom of IE how the elements (ex.. 30 items remaining) are loading and with Firefox there isn't delay at all.

    is there a solution or reason for this?

    Note: I'm using the latest SCS 7, and it was the same case with SCS 6.

    thanks a lot
    CA

    1. Apr 20, 2010

      KenGra,

      Try posting at the Messaging Server software forum. You'll get a better response there.

      Regards,

      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.