Communications Suite on a Single Host

Skip to end of metadata
Go to start of metadata

Deployment Example: Oracle Communications Unified Communications Suite on a Single Host
Version 7 Update 3

This deployment example describes how to install Communications Suite 7 Update 3 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, instant messaging, and address book servers on the same system is not the optimal configuration, nor does it provide the best performance. This example deployment is not intended for production purposes. Use this configuration for evaluation and for training purposes only. Performance is better if you install services on separate machines. For more information on deploying Communications Suite, see Communications Suite Deployment Planning Guide.

Topics:

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 Oracle Communications Unified Communications Suite 7 Update 3 for Solaris OS 10. These instructions are not intended to act as a replacement for the individual component product documentation, but merely to guide the evaluator through an initial installation.

What Components Are Installed?

This example guides you through installing the following Communications Suite and prerequisite components:

  • Messaging Server 7 Update 4 Patch 27
  • Calendar Server 7 Update 3 Patch 9
  • Instant Messaging 9 Patch 1
  • Directory Server Enterprise Edition 11gR1
  • GlassFish Server 2.1.1 with HADB support
  • Delegated Administrator 7 Patch 6
  • Convergence 2 Patch 5
  • Indexing and Search Service 1 Update 4 Patch 15
  • MySQL 5.5.28
  • Java SE 7u11

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

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 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 or x86 64-bit
RAM 2 Gbytes or more
Disk Space 8.5 Gbytes or more free disk space for installation. As much as 5.4 Gbytes of this space is for zip files and unzipped directories. Removing zip files after unzipping them reduces the disk space requirement from 8.5 Gbytes to 6.8 Gbytes.
Software Solaris 10 OS. This example uses an installation based on Solaris OS 10 Update 10. Solaris 11 is not supported.
Users Provisioned with test users.

Table 2 Client Software Requirements

Component Platform Requirement
Browser Firefox 3.6 or later, Internet Explorer 7.x or later, Safari 5.x, Chrome

Table 3 Server Configuration Information

Component Install Notes Install Location Database Location Port Name Port Number
GlassFish Server 2.1.1 Installed separately. Required for Convergence, Delegated Administrator, and Instant Messaging.
/opt/SUNWappserver Not applicable
HTTP Port 80
        Admin Port 4848
        HTTPS Port 443
Directory Server 11gR1 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 Update 4 Installed by using Communications Installer. Additional configuration required. /opt/sun/comms/messaging64 /var/opt/sun/comms/messaging64 Webmail Port (HTTP) 8990
        SMTP Port 25
        POP Port
110
        IMAP Port 143
Instant Messaging 9 Installed by using Communications Installer. Additional configuration required. /opt/sun/comms/im /var/opt/sun/comms/im XMPP Port 5222
        Multiplexed XMPP Port 45222
        Gateway Connector Port
55222
        XMPP Server Port
5269
        Notification Server Port
47676
GlassFish Server 2.1.1
Installed separately. Required by Calendar Server 7 Update 3
/opt/SUNWappserverCS
Not applicable
HTTP Port
8080
        Admin Port
8800
        HTTPS Port
8181
MySQL Server 5.5.8
Installed separately. Required for Calendar Server 7 Update 3. /opt/mysql
/var/mysql/caldav
DB Port
3306
Calendar Server 7 Update 3
Installed by using Communications Installer. Additional configuration required.
/opt/sun/comms/davserver
/var/mysql/caldav
HTTP Port
8080
        Admin Port
8800
        HTTPS
8181
        JMQ Port
47676
GlassFish Message Queue Installed by Communications installer. Additional configuration required. /etc/imq Not applicable JMQ Port 7676
Convergence 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
Indexing and Search Service 1 Update 4
Installed by using Communications Installer. Additional configuration required.
/opt/sun/comms/jiss /var/opt/sun/comms/jiss HTTP Port
80
        Admin Port
4848
        HTTPS Port 443
        IMAP Port
143
        JMQ Port
7676
        Directory Server Port
389

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, GlassFish Server and Directory Server 1 hour
Configure software 3 hours
Total 6 hours (average)

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

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

Installation Notes and Recommendations

  1. Use gzip -d or gunzip to decompress the *.gz files.
  2. Use unzip to decompress the *.zip files.

Expected User Input

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

Table 5 Information Input During Installation

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.
<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 Communications Suite
  2. Running the Communications Installer to install the Communications Suite component software
  3. Installing and Configuring Directory Server
  4. Installing Java (which is no longer shipped as part of the Communications Suite bundle)
  5. Installing and Configuring GlassFish Server
  6. Preparing Directory Server for Communications Suite
  7. Configuring Delegated Administrator and Communications CLI
  8. Configuring Messaging Server
  9. Installing and configuring MySQL Server
  10. Configuring Calendar Server 7
  11. Configuring Instant Messaging
  12. Configuring Indexing and Search Service
  13. Configuring Convergence
  14. Configuring users

These installation steps result in a suitable deployment to evaluate and test Communications Suite 7 Update 3. 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. These instructions assume all actions are performed by the root user.

To Check System Requirements

  • Make sure that the computer meets the requirements specified in Table 1.

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

  • Get the Software from the Communications Suite 7 Update 3 download site.
  • See Communications Suite Component Patches for more current component product patches that have become available since Communications Suite 7 Update 3 shipped. If more current patches are available, use the appropriate patch procedure.

Installing Communications Suite Components

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

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

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:

To Disable sendmail

  • Prior to configuring Messaging Server, use the following procedures to kill the sendmail process and prevent it from starting during bootup.
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 Update 3 Software

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

To Install the Communications Suite Software

  1. Create a /temp/UCS directory, move the Communications Suite 7 Update 3 software zip file (V37040-01.zip) to this directory and extract the files.
  2. Run the Communications Suite installer, which is in the root of the directory in which you unzipped the file.
  3. Accept the License Agreement by typing Yes if prompted.
  4. Accept the default Install location: /opt/sun/comms
  5. Select the following components for installation:
    • Messaging Server (64bit) 7u4 (7.4-27.01)
    • Comms DSsetup 6.4 (6.4-24.03)
    • Calendar Server 7u3 (7.3-9.03)
    • Instant Messaging 9 (9.0-01.18)
    • Convergence 2 (2.0-5.01)
    • Indexing and Search Service 1u4 (1.4-15.8802)
    • Comms Delegated Administrator 7 (7.0-6.00)
      This corresponds to selections 1, 2, 3, 4, 5, 6, 7.
  6. 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 6 Values for NSS, Message Queue, and Service Tags Options
    Option [Default Value] Enter:
    Change pkg versions for Service Tags [n] y
    Change pkg versions for NSS/NSPR/JSS [n] y
    Change pkg versions for Message Queue [n] y
    Change pkg versions for Message Queue Localization [n] y
  7. Press Return when prompted to continue.
    The installation proceeds.
  8. Press Return when prompted to continue.
  9. Continue with the next section.

Installing and Configuring Directory Server

Directory Server 11gR1 (7.0.1, also known as ODSSEE11g) is the preferred version. Before you proceed, make sure that you get the Directory Server 11gR1 software from the Oracle Software Delivery Cloud. See Dependent Component Product Software for download instructions.

  1. Check for the existence of the /opt/SUNWdsee directory.
    If this directory does not exist, type the following command to create the directory:
  2. Move the downloaded Directory Server zip file V25760-01.zip to a temporary location, such as /temp/DS, then unzip the file, change to the distribution directory, and unzip the installation file into the /opt/SUNWdsee directory.

    The installation installs the Directory Server software in the specified location, /opt/SUNWdsee.

  3. Create your Directory Server instance.
  4. When prompted, type adminpass for the Directory Manager password.
  5. Start the Directory Server instance.
  6. Create the user and group suffix o=isp.
  7. When prompted, type Y to accept the certificate.
  8. When prompted, type adminpass for the Directory Manager password.
  9. Start the Directory Server instance.
  10. Continue with the next section.

Installing Java

Java is no longer bundled with the Oracle Communications Unified Communications Suite installer starting with Communications Suite version 7 Update 3. For production deployments, you must manually install both the 32-bit and 64-bit JDKs for Communications Suite. This deployment example uses only Java SE SDK Version 7u11 (or later). You can also use Java SE 6 Update 37 or later, but this example uses Java SE 7.

Note
GlassFish 2.x does not officially support JDK 7 but Communications Suite components support JDK 6 or 7. To simplify matters, this deployment example uses only JDK 7. Using JDK 7 in GlassFish 2.x is fine to support evaluations but is not recommended for production deployments. For production deployments, install JDK 6 for GlassFish and JDK 7 for the rest of the components.

At the time of this writing, you can download Java from http://www.oracle.com/technetwork/java/javase/downloads/index.html. Download the JDK, not the JRE. Download both the 32- and 64-bit versions. You can find these by clicking the JDK "Download" button for the Java Platform. Select the gzipped tar file (ending in tar.gz). Do not select the compressed tar file ending in tar.Z.

This deployment example uses jdk-7u11-solaris-sparc.tar.gz (32-bit version) and jdk-7u11-solaris-sparcv9.tar.gz (64-bit version).

After downloading the 32- and 64-bit versions of Java, install them as follows:

  1. Copy the 32- and 64-bit versions of Java to the /usr/jdk directory and unzip them.
  2. Untar the files to install Java.
  3. Relink the symbolic link "latest" to point to the new version of Java.
  4. Change the /usr/java link to point to the correct JDK version.
  5. Verify you have correctly set up Java.

    The shell returns results that look similar to the following:

    java version "1.7.0_11"
    Java(TM) SE Runtime Environment (build 1.7.0_11-b21)
    Java HotSpot(TM) Server VM (build 23.6-b04, mixed mode)
    
  6. Continue with the next section.

Installing and Configuring GlassFish Server

GlassFish Enterprise Server with HADB Version 2.1.1 Patch 19 (v2.1 Patch33) is the primary web container used by Convergence and the Indexing and Search Service.

Prior to installing the GlassFish Server, check the Java version on your host. GlassFish Server requires at least Java 1.6.0. Solaris 10 Update 6 ships with version 1.5.0_16, which is not sufficient for Unified Communications Suite components.

  • Use the following command to check your Java version.

    The shell returns results that look similar to the following:

    java version "1.7.0_11"
    Java(TM) SE Runtime Environment (build 1.7.0_11-b21)
    Java HotSpot(TM) Client VM (build 23.6-b04, mixed mode)
    

    If the version is not 1.7.0, make sure that /usr/java links to /usr/jdk/jdk1.7.0_11, and that /usr/jdk/latest links to jdk1.7.0_11. (You should have already performed these steps when installing and configuring Java.)

To Install GlassFish Server

  1. Create the /temp/Glassfish directory and copy GlassFish Enterprise Server 2.1.1 Patch 19 to this directory, then run the installer.
  2. When prompted, press Enter to continue.
  3. 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 7 GlassFish 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 New or Reuse existing Java 2 SDK [Install Java 2 SDK] Reuse existing Java 2 SDK
    Path to Java 2 SDK Version 1.5.0 or greater [/usr/jdk/jdk1.7.0_11] accept default
    Admin User [admin] accept default
    Admin User's Password adminpass
    Master Password for SSL Certificate adminpass
    Admin Port [4848] accept default
    HTTP Port [8080] 80
    HTTPS Port [8181] 443
    Enable Updatecenter client [yes] no
    Upgrade from previous AS version [no] accept default
  4. Select 1. Install Now.
    The installation proceeds.
  5. When the installation completes, press Return to exit.
  6. Edit the /opt/SUNWappserver/domains/domain1/config/domain.xml file to change the Java Message Queue (JMQ) port from 7676 to 37676. Look for a line similar to the following:
    jms-host name="default_JMS_host" host="wireless.comms.beta.com" port="7676"
    

    Change the port to 37676, save and exit the file.

    Note
    By default, GlassFish 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 of the GlassFish JMQ instance uses to avoid any future conflict.
  7. Start GlassFish Server:
  8. When prompted, type:
    username: admin
    admin password: adminpass
    master password: adminpass
  9. Perform the following steps to save the admin username and password so that you do not need to provide them each time GlassFish Server is started. (You must still type the master password.)
  10. Type admin and adminpass as the username and password when prompted.
  11. Continue with the next task.

To Verify GlassFish Server

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

    You should see the Server is Running web page.

Configuring Communications Suite Components

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

This section contains the following topics:

Preparing the 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.pl script is located and run the script, for example:
  2. Type y to continue.
    The script prompts for a series of options. The following table shows how to respond to the prompts.
    Table 8 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.pl script proceeds.
  4. When prompted, type y to continue with the script.
    Continue with the next section after comm_dssetup.pl 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:
    If you are running sh or bash, 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 9 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] accept default
    Domain Directory
    [/opt/SUNWappserver/domains/domain1] accept default
    Domain 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 [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [checked] accept default
    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]
    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 [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [checked] 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
    Organization DN [o=comms.beta.com,o=isp] accept default
    Top Level Admin for Default Organization [admin] accept default
    Password - adminpass
    Load Sample Service Packages [Y] accept default
    Load Sample Organizations [Y] n
    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 Server; the other reminds you to enable the mail, calendar, and instant messaging services in the domain. Steps 9 and 10 restart GlassFish Server and enable the services.
  8. Click Close to exit the Delegated Administrator Configuration wizard.
  9. Restart GlassFish Server.
  10. Modify the mail, calendar, and instant messaging domains, and create users by using the commadmin utility:

    The commadmin user create steps create an end-user, jdoe, and the Calendar Server administrative user, calmaster. Continue to 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
    In this example, type:
    http://wireless.comms.beta.com/da
    
  2. Log in using admin and adminpass as the user ID and password.
  3. After verifying that you can access Delegated Administrator, log out.
  4. Continue with the next section.

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

  2. Verify the following:
    • Accept the default for the Directory to store Configuration and 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]
  3. The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 10 Values for Messaging Server configure Script
    Option [Default Value] Enter:
    Default Mail Domain Name
    [comms.beta.com] accept default
    Hostname for LDAP Directory Server [] wireless.comms.beta.com
    LDAP Administrator Login [cn=Directory Manager] accept default
    Password
    - adminpass
    Postmaster email address [admin@comms.beta.com] jdoe@comms.beta.com
    Password for Server Administration - adminpass
  4. The Messaging Server configuration proceeds.
  5. Start Messaging Server:
  6. Continue with the next section.

Configuring Calendar Server 7

Configuring Calendar Server 7 consists of installing a second instance of GlassFish Server and installing MySQL.

Topics in this section:

To Install a Second Instance of GlassFish Server

  1. Install a second instance of GlassFish that runs on port 8080.
  2. Press Enter to continue when prompted.
  3. 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 11 Values for Calendar Server 7 Update 3 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/jdk1.7.0_11] accept default
    Admin User [admin] accept default
    Admin User's Password -- adminpass
    Master Password (for SSL Certificate) -- adminpass
    Admin Port [38295] 8800
    HTTP Port [38292] 8080
    HTTPS Port [38298] 8181
    Enable Updatecenter client [yes] accept default
    Upgrade from previous AS version [no] accept default
  4. Confirm that you would like to "Install Now" when prompted.
    The installation proceeds.
  5. Edit the domain.xml file to change the JMQ port from 7676 to 47676.
  6. Change port 7676 to 47676, save and exit the file.
  7. Start the GlassFish Server.
  8. Continue with the next section.

To Install MySQL Database

You should have already downloaded the MySQL Database PKG version for Solaris 10 SPARC (64-bit) from edelivery.oracle.com and unzipped the image to use it with the following steps. This example uses MySQL Advanced Server (Commercial sun4u) 5.5.28. For download instructions, see Get the Software.

  1. Make a temporary directory for the MySQL package and copy it to that directory.
  2. Create a mysql group and user.
  3. Add the MySQL package to the system.
  4. Install the packages into the default directory /opt/mysql.
  5. Set up the MySQL database for Calendar Server 7:
  6. Create the /etc/my.cnf file with the following content.
  7. Install the MySQL startup script if not already present. (First check to make sure that /etc/init.d/mysql does not already exist. If not, perform the following command.)
  8. Start MySQL.
  9. Change the MySQL root password and remove test databases.
  10. Answer "y" to all questions except "Change the root password."
    You do not need to change the root password because you have already done so. The mysql_secure_installation script:
    • Removes anonymous users
    • Disallows root login remotely
    • Removes test database and access to it
    • Reloads privilege tables
  11. Create the MySQL user and caldav database.
  12. Configure MySQL to start automatically upon reboot.
    1. Check for a symbolic link to S99mysql.
    2. If there is no S99mysql, create a symbolic link.
  13. Make sure that you are root user.
  14. Set the JAVA_HOME environment variable.
    For example, if you are running csh:
  15. Change directories to where the configuration script was installed and run the Calendar Server 7 configuration script:
  16. Click Next at the Welcome page.
  17. Accept the default for the Directory to store Configuration and Data Files: /var/opt/sun/comms/davserver
  18. Configure Calendar Server 7.
    The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 12 Values for Calendar Server 7 Update 3 configure Script
    Option [Default Value] Enter
    Host Name [wireless] accept default
    DNS Domain Name [comms.beta.com] accept default
    MySQL or Oracle Database [MySQL] 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
    iSchedule Database Name [ischedule] accept default
    Directory to Store Documents [/var/opt/sun/comms/davserver/db] 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] 8800
    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
    LDAP Unique ID Attribute [davuniqueid] accept default
    Default Domain Name [comms.beta.com] accept default
    Organization DN [o=comms.beta.com,o=isp] accept default
    SMTP Server Host Name [wireless.comms.beta.com] accept default
    SMTP Server Port Number [25] accept default
    Calendar Administrator User ID [calmaster] accept default
    Calendar Administrator User Password -- adminpass
  19. Click the "Configure Now" button to configure Calendar Server 7.
  20. After the configuration is complete, click Next to continue.
  21. Click Next to continue.
  22. Click Close to quit the Calendar Server configuration wizard.
  23. Restart GlassFish Server.
  24. Configure a Lightning client to use this new server.
    The Calendar Server URL format for your test user is:
    http://<fully-qualified-server-name>:8080/davserver/dav/home/<username>/calendar/
    

    For example:

    http://wireless.comms.beta.com:8080/davserver/dav/home/jdoe/calendar/
    

    Alternatively, you can configure Apple iCal to access this calendar. The server URI is as follows:

    http://<fully-qualified-server-name>:8080/davserver/dav/principals/<username>/
    

    For example:

    http://wireless.comms.beta.com:8080/davserver/dav/principals/jdoe/
    
  25. To enable subscription to other user's calendars in your own domain, create an ACI file with the following contents, making sure that the ACI fits within a single line:
    dn: o=isp
    changetype: modify
    add: aci
    aci: (target="ldap:///($dn),o=isp")
    (targetattr!="userPassword")
    (targetfilter=(|(objectClass=icscalendaruser)(objectclass=icscalendarresource)))
    (version 3.0; acl "CS User search access to all users and resources in own domain - product=davserver,class=install,num=3,version=1";
    allow (read,search)
    userdn="ldap:///[$dn],o=isp??sub?(objectclass=icscalendaruser)";)
    
  26. Run the ldapmodify command on this ACI file (named acifile in this example).
  27. Continue with the next section.

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.
  3. Hit Enter whenever prompted whether to go back to the previous panel.
    The configuration wizard prompts for a series of options.
  4. 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 13 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
    Where 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/sun/comms/im] 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
    Gateway Connector Port [55222] accept default
    XMPP Server Port [5269] accept default
    Disable Server (enable only multiplexor) [no] accept default
    Enable SSL [yes] no
    LDAP Host Name [wireless.comms.beta.com] accept default
    LDAP Port Number [389] accept default
    SSL Enabled [no]
    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 IM HTTP Gateway [yes] no
    Deploy IM IMPS Gateway
    [yes] no
    Enable Calendar Agent
    [no] yes
    Enable local component
    [no] yes
    Select type of notification
    [JMQ] accept default
    XMPP server Hostname [wireless.comms.beta.com] accept default
    XMPP server port [5269] accept default
    JMQ Username
    [] guest
    JMQ Password
    -- guest
    Notification Server Hostname [localhost]
    wireless.comms.beta.com
    Notification Server Port [7676]
    47676
    Topic
    [DavNotificationTopic]
    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
    Enable Facebook Gateway [no] accept default
    Start Services After Successful Configuration [yes] no
    Start Services When System starts [yes] no

    The Instant Messaging configuration begins.

  5. When the configuration is complete, at the Configuration Summary page, select Done to exit.
  6. To configure Instant Messaging Server for integration with Convergence, first make a backup copy of the configuration:
  7. Next, add the new httpbind and avatar component JIDs to this configuration by running the following commands:
    Note
    The httpbind.jid and avatar.jid strings are in the form host.httpbind.domain and host.avatar.domain respectively as this is the value auto-generated during the upcoming Convergence configuration stage.
  8. Enable Hosted Domain Schema 2 and listener prop support by making the following changes:
  9. Start the Instant Messaging server.
  10. 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.
  11. Continue with the next section.

Configuring Indexing and Search Service

  1. Enable the NTP service for the Messaging Server and ISS host machine.
    1. Check if the NTP service is enabled.
    2. If the NTP service is disabled, enable it as follows then verify that the service is running.
  2. Configure the IMQ broker by editing the imqbrokerd.conf file.
  3. Type in the following configuration. (It is possible that the file already contains some of this information.)
    AUTOSTART=YES
    ARGS=-vmargs -Xmx1024m
    RESTART=YES
    
  4. 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.
  5. Edit the /var/imq/instances/imqbroker/props/config.properties file.
  6. At the bottom of this file, make sure the following lines are included:
    imq.portmapper.backlog=-1
    imq.destination.DMQ.truncateBody=true
    imq.autocreate.reaptime=7200
    imq.autocreate.destination.maxNumProducers=-1
    imq.autocreate.destination.limitBehavior=REMOVE_OLDEST
    imq.jms.max_threads=2000
    

    For an explanation of these changes, see Message Queue Broker config.properties Changes for Indexing and Search Service.

  7. After making these changes, save and exit the file.
  8. Restart the IMQ broker to pick up the changes.
  9. Create the JMQ user by using the imqusermgr command.
  10. Reset the default admin account password.
  11. Set the local.store.notifyplugin configutil parameter to include a JMQ notification named index.

    If a response is returned, such as lib/libibiff$ms-internal$, prepend the new JMQ notification to existing one, for example:

    If no response is returned, execute the following command:

  12. Configure the index JMQ notification plugin by using the configutil command.
  13. Restart Messaging Server and verify that the JMQ index plugin is working.

    You should see entries similar to these:

    [18/Dec/2012:15:11:02 -0700] mailhost imapd[19507]: General Notice: jmqNotify plugin loaded: index
    [18/Dec/2012:15:11:02 -0700] mailhost imapd[19507]: General Notice: jmqnotify: connecting index
    [18/Dec/2012:15:11:07 -0700] mailhost imapd[19507]: General Notice: jmqnotify: index connected
    [18/Dec/2012:15:11:07 -0700] mailhost imapd[19507]: General Warning: Oracle Communications Messaging Server IMAP4 7u4-27.13 (7.4-27.01) 64bit (built Nov 30 2012) starting up
    

  14. Verify that the IMQ broker started up cleanly.

    You should see entries similar to these:

    ----------
    [18/Dec/2012:15:11:06 PDT] [B1065]: Accepting: jmquser@127.0.0.1:33167->jms:32832. Count: service=1 broker=1
    [18/Dec/2012:15:11:09 PDT] [B1065]: Accepting: jmquser@127.0.0.1:33174->jms:32832. Count: service=2 broker=2
    [18/Dec/2012:15:11:11 PDT] [B1065]: Accepting: jmquser@127.0.0.1:33181->jms:32832. Count: service=3 broker=3
    
  15. Verify that the Messaging Server has producers connected to INDEXMS.
  16. Prepare the Messaging Server to forward IMAP SEARCH queries to Indexing and Search Service.
  17. Restart Messaging Server.
  18. Change directories to where the configuration script was installed and run the ISS configuration script:

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

    Option [Default Value] Enter
    Cluster configuration (iss.cluster.install) [standalone] accept default
    Fully qualified domain name of system (hostname) -- wireless.comms.beta.com
    Instance name of the installation for an indexing node, for example, iss1 (instance.name) [none] iss1
    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 to store the Lucene indexes (iss.store.dir) [/var/opt/sun/comms/jiss/index] accept default
    Location of attachment data (iss.data.dir) [/var/opt/sun/comms/jiss/attach] accept default
    Location of JISS log files (iss.log.dir) [/var/opt/sun/comms/jiss/logs] accept default
    Location of Java (java.home) [/usr/jdk/latest] accept default
    User/Group Directory Server format (mail.ldap) [none] wireless.comms.beta.com:389
    User/Group Base DN format (mail.basedn) [none] o=isp (normally autodetected)
    Schema Level (mail.schemalevel) [none] 2 (normally autodetected)
    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
    Deploy the SearchUI web application (appserv.searchui.enabled) [false] true
    JISS JMQ broker hostname(s) list, that is host:7676,host2:7677 (imq.host) [none] wireless.comms.beta.com:7676
    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
    File based or Directory Server based JNDI lookups (jndi.type) [none] ldap
    JISS Directory Server host list host:port,host2:port2 (ldap.host) [none] wireless.comms.beta.com:389
    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
    Watcher service enabled on this host (iss.watcher.enabled) [false] accept default
  19. Restart GlassFish Server.
  20. Bootstrap existing users to create their index by using the following issadmin.sh --bootstrap command.
    cd /opt/sun/comms/jiss/bin
    ./issadmin.sh --bootstrap --user <username> --host <hostname> --runoptimizer true
    

    In this example, type the following command:

  21. Test that search works by typing the URL of the Search UIs in your browser and log in as a user.
    • The URL for the Restful service is: http://fully-qualified-server-name/rest
      For this example, type:
      http://wireless.comms.beta.com/rest
      
    • The URL for the Searchui is: http://fully-qualified-server-name/searchui
      For this example, type:
      http://wireless.comms.beta.com/searchui
      
    • In each case, log in as user jdoe. The password is demo.
  22. Configure Messaging Server to send searches to Indexing and Search Service:
  23. Increase the number of GlassFish request processing threads to support Convergence and Indexing and Search Service in the same web container.
    1. Find the number of CPUs on the system.
    2. Use that number to increase GlassFish processing threads.
    3. When prompted, type the admin user and adminpass password.
      Please enter the admin user name: admin
      Please enter the admin password: adminpass
      
  24. Configure ISS to autoprovision, autobootstrap, and autosync users.
    1. Change to the jiss/etc directory, make a copy of the jiss.conf file, then edit the file.
    2. Set the following configuration parameters:
      iss.autoprovision.enabled = true
      iss.indexsvc.periodic.autosync.enabled = true
      iss.indexsvc.periodic.autobootstrap.enabled = true
      iss.indexsvc.periodic.autosync.count = 2
      
      Note
      Set the iss.indexsvc.periodic.autosync.count parameter to the number of user accounts that should be synced every five minutes. If you want to ensure an autosync every 12 hours for each user in a 288 user deployment, you can set this value as shown.
  25. Refresh ISS.
  26. Restart GlassFish Server.
  27. Continue with the next section.

Configuring Convergence

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

  1. Become the root user in the root directory
  2. Set the JAVA_HOME environment variable.
    For example, to set it for the C shell (csh):
  3. Run the Convergence configuration script.
  4. Read the Software Requirements and click Next to continue.
  5. Accept the default for the Directory to store Configuration and Data Files: /var/opt/sun/comms/iwc
    The Components Selection page appears.
  6. 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 15 Values for Convergence configure Script
    Option [Default Value] Enter:
    Host Name [wireless] accept default
    DNS Domain Name [comms.beta.com] accept default
    GlassFish 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
    Application Server Instance 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] accept default
    Webmail Admin User ID [admin] accept default
    Admin Password - adminpass
    Calendar Server Version
    [7]
    accept default
    Calendar Server Host Name [wireless.comms.beta.com] accept default
    Calendar Server Port [80] 8080
    Calendar server running in secure mode [unchecked] accept default (Not secure)
    Service URI
    [/davserver/wcap] accept default
    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
  7. Click Configure Now to configure Convergence.
  8. Click Next when the configuration is complete.
  9. Click Next to continue.
  10. Click Close to quit the Convergence configuration wizard.
  11. Configure Convergence to use Indexing and Search Service:
  12. Restart GlassFish Server.
  13. In your web browser, open a URL for Convergence and log in as a test user.
    The URL for Convergence is:
    http://fully-qualified-hostname/iwc
    In this example, type:
    http://wireless.comms.beta.com/iwc
    

At this point, you have completed installing and configuring the single host deployment example. You should now try out the system by conducting tasks such as:

  • Creating users
  • Logging in as various users and using email, calendaring, instant messaging, and address book functions
  • Getting familiar with Communications Suite services and architecture

For more information on these topics, see the documentation at the Communications Suite wiki.

Creating Additional User Accounts and Groups

This section describes how to create additional users accounts and groups.

To Create Users and Groups using the CLI

The following example shows how to create two new users (demo1 and demo2) with the password demo using the Delegated Administrator command-line utility and also how to create a mailing and calendar group (Demostaff@comms.beta.com) consisting of the newly created users.

  1. Run the following Delegated Administrator commands.
    /opt/sun/comms/da/bin/commadmin user create -D admin -F Demo -l demo1 -L One -d comms.beta.com -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 -d comms.beta.com -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 -d comms.beta.com -S mail -E Demostaff@comms.beta.com -H wireless.comms.beta.com -o calmaster -m demo1 -m demo2 
    
    Bootstrap the users you just added to create their index by using the following commands:
    Note
    Creating groups by using the Delegated Administrator command-line interface guarantees that these groups will be recognized as LDAP groups that Instant Messenger can search for. They can also be used to send email to the entire group.

To Use the Delegated Administrator GUI to Create Users

An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator web-based GUI.

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 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/da/DA/Login
      
  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, because 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 the Release Notes.

Labels:
convergence convergence Delete
messagingserver messagingserver Delete
caldavserver caldavserver Delete
commsuite commsuite Delete
directoryserver directoryserver Delete
installing installing Delete
calendarserver calendarserver Delete
example example Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

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.