Communications Suite on a Single Host (Red Hat Linux)

Skip to end of metadata
Go to start of metadata

Deployment Example: Oracle Communications Unified Communications Suite on a Single Host (Red Hat Linux)
Version 7 Update 1

This deployment example describes how to install Communications Suite 7 Update 1 software on a single Red Hat Enterprise Linux 5 (64-bit) server for a functioning deployment. This document is intended for any evaluator, system administrator, or installation technician who wants to install and evaluate the services delivered by these components.

Note
Installing the messaging, calendar, instant messaging, and address book services on the same system is not the optimal configuration, nor does it provide the best performance. This example deployment is not intended for production purposes. Use this configuration for evaluation and for training purposes only. Performance is improved when services are deployed across multiple systems.

Comparison to Communications Suite 7 Guide

Each new release or update of Communications Suite provides additional functionality which in-turn is reflected by modifications to the Single Host install guide to make best use of this functionality.

The following is a brief overview of the changes made to the guide.

  • IMAP-IDLE configuration steps removed
    • Messaging Server enables IMAP-IDLE by default
  • Red Hat Enterprise Linux 5.3 64-bit is the default operating system
    • Directory Server 7 has added support for Red Hat Enterprise Linux 5.3
  • Calendar Server 7 (CalDAV) is installed by default
    • Convergence 2 is now able to interoperate with Calendar Server 7
    • Calendar Server 6.3 is no longer installed

New features for Communications Suite 7 Update 1 can also be found in the Communications Suite 7 Update 1 Release Notes.

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 Communications Suite 7 Update 1 on Red Hat Enterprise Linux 5.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.

What Components Are Installed?

This example guides you through installing the following Communications Suite and pre-requisite components:

  • Messaging Server 7 Update 4
  • Calendar Server 7 Update 1
  • Instant Messaging Server 8 Update 3
  • Oracle Directory Server Enterprise Edition 11gR1
  • GlassFish Enterprise Server 2.1.1 Patch 01
  • Delegated Administrator 7 Patch 3
  • Convergence 2
  • All Shared Components

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

  • Domain name: comms.beta.com
  • Host name: demo (running Red Hat Enterprise Linux 5.3 64-bit)
  • Fully qualified (external) host name: demo.comms.beta.com
  • Password: adminpass used for all passwords except the amldapuser password

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

Recommended Ports

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

Implementation Specifications for This Example

This section describes implementation specifications for this example.

Table 1 Evaluation Host Hardware and Software Requirements

Component Platform Requirement
CPU x86 64-bit
RAM 2 Gbytes or more
Disk Space 2.1 Gbytes or more free disk space for installed software. 1.5 Gbytes additional disk space may be needed for temporary storage of Communications Suite zip files.
Software Red Hat Linux Enterprise Linux 5.3 64-bit.
Users Provisioned with test users.

Table 2 Client Software Requirements

Component Platform Requirement
Browser Firefox 3.6.x, Internet Explorer 7.x, 8.x


Table 3 Server Configuration Information

Component Install Notes Install Location Database Location Port Name Port Number
Glassfish 2.1.1 Installed separately. Required for Convergence, Delegated Administrator, Instant Messaging Java Client and Calendar Server /opt/sun/appserver /opt/sun/appserver/domains/domain1 HTTP Port 80
        Admin Port 4848
        HTTPS Port 443
Directory Server 11gR1 Installed separately. /opt/sun/directory /var/opt/sun/dsins1 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/messaging /var/opt/sun/comms/messaging Webmail Port (HTTP) 8990
        SMTP Port 25
        POP Port 110
        IMAP Port 143
Instant Messaging 8 Update 3 Installed using Communications Installer. Additional configuration required. /opt/sun/comms/im /var/opt/sun/comms/im XMPP Port 5222
        Multiplexed XMPP Port 45222
        Server-to-Server Port 5269
MySQL 5.1 Installed using Communications Installer. Additional configuration required   /var/lib/mysql DB Port 3306
Calendar Server 7 Installed using Communications Installer. Additional configuration required. /opt/sun/comms/davserver /var/opt/sun/comms/davserver CalDAV Port 8686

Installation Time Estimates

The following table provides time estimates for installing this example.

Table 4 Installation Time Estimates

Activity Estimate
Install Red Hat Linux Operating System 2 hours
Install Communications Suite, Application Server and Directory Server 1 hour
Configure software 3 hours
Total 6 hours (average)

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

Installation Notes and Recommendations

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

Expected User Input

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

Table 5 Information Input During Installation

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 Communications Suite
  2. Running the Communications Suite Installer to install Messaging Server, Calendar Server, Instant Messaging, Delegated Administrator and Convergence.
  3. Installing and configuring Directory Server 11gR1
  4. Installing and configuring Glassfish 2.1.1
  5. Deploying and enabling the Directory Server Control Center
  6. Configuring Delegated Administrator and Communications CLI
  7. Configuring Messaging Server
  8. Configuring MySQL Server
  9. Configuring Calendar Server
  10. Configuring Instant Messaging Server
  11. Configuring Convergence

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

Installing the Example

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

Note
Unless otherwise indicated, all of the examples and instructions in this document assume that you are logged in as the root user.

This section contains the following topics:

Checking Installation Requirements

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

To Check System Requirements

The computer should meet the following requirements:

  • These instructions assume all actions are performed by the root user unless mentioned otherwise.
  • The computer must have 1.5 GB free disk space for the zip files and zip image.

To Check DNS

Verify that DNS is running and configured properly:

  1. Make sure that the /etc/resolv.conf file has name server entries with the IP addresses of valid name servers. For example:
    domain comms.beta.com
    nameserver 192.168.100.22
    nameserver 192.168.100.23
    nameserver 192.168.100.24
    nameserver 192.168.100.25
    
  2. Make sure that the /etc/hosts file has an entry for the fully qualified host name of the server. This fully qualified host name should be listed before the non fully qualified host name. For example:
    10.1.82.52 demo.comms.beta.com wireless demo
    
  3. Make sure that the /etc/nsswitch.conf file is configured to use files first to resolve host names. The hosts line in the nsswitch.conf file should list files first in its entry:
    hosts: files dns nis [NOTFOUND=return]
    # OR (if NIS is not used)
    hosts: files dns
    

To Check for Sufficient Number of File-Descriptors

The default installation of Red Hat Enterprise Linux 5.3 uses 1,024 file descriptors, which is insufficient for the correct operation of Communications Suite 7 Update 1. A Communications Suite 7 Update 1 system needs the maximum file descriptors set to 16,384.

  1. In a terminal window, as root user, verify the number of file descriptors.
    ulimit -n
  2. If this number is less than 16,384 you will need to increase the value.
  3. To change the number of file descriptors, add the following to the /etc/sysctl.conf file. Or, if the parameter is already set, increase the value to 16384.
    fs.file-max = 16384
  4. Add the following two lines to the /etc/security/limits.conf file.
    # Increase max file descriptors
    * - nofile 16384
    
    Note
    Be careful when editing configuration files to not introduce extra spaces and lines, as this could cause errors. If you do accidentally type extra spaces, try copying existing lines and then overwriting them (by pasting) to get rid of any extra spaces. Using a text editor that displays hidden characters can also help.
  5. Either reboot the system for the value to take effect or run the following command:
    sysctl -p /etc/sysctl.conf
  6. In a new terminal window, as root verify the change.
    ulimit -n

To Enable Process Core Dumps

Red Hat Enterprise Linux disables process core dumps by default. Process core dumps are essential for tracing the root cause behind a process crashing. The following guide provides steps on enabling process core dumps:

How can core dumps be enabled for daemons (services) in Red Hat Enterprise Linux?

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 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 later when configuring Messaging Server.

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

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:

Installing Communications Suite 7 Update 1 Software

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

  1. Create the /tmp/CS7U1/ directory, move the Communications Suite 7 software (CommsR7u1-linux_x86.zip) to this directory and extract the files.
    cd /tmp/CS7U1
    unzip CommsR7u1-linux_x86.zip
    
  2. Run the Communications Suite installer.
    ./commpkg install
    
  3. Press Return to continue when prompted.
  4. Review the license and type c to continue when prompted.
    You can also type s to skip the license display.
  5. Accept the License Agreement by typing yes when prompted.
  6. Accept the default Install location: /opt/sun/comms
  7. Select the following components for installation (1,2,3,4,5,7,).
    2.     Messaging Server (64bit) 7u4 (7.4-18.01)
    3.     Comms DSsetup 6.4 (6.4-6.03)
    4.     Calendar Server (CALDAV) 7u1 (7.1-1.11)
    5.     Instant Messaging 8u3 (8.3-03.10)
    6.     Convergence 2 (2.0-0.06)
    8.     Comms Delegated Administrator 7 (7.0-3.00)
    

    The installation proceeds.

  8. Press Return when prompted to continue.
  9. Continue with the next section.

Installing and Configuring Directory Server 11gR1

To Install the Zip Version of Directory Server 11gR1

  1. Move the downloaded Directory Server 7 zip file V21900-01.zip to a temporary location, such as /tmp/DSEE11gR1.
  2. Unzip the file.
    unzip V21900-01.zip
    
  3. Deploy the DSEE 11gR1 software to the /opt/sun/directory directory.
    cd ODSEE_ZIP_Distribution
    unzip sun-dsee7.zip
    mv dsee7/ /opt/sun/directory
    
  4. Create a new directory server instance in the /var/opt/sun/directory/dsins1 directory.
    mkdir -p /var/opt/sun/directory/
    cd /opt/sun/directory/bin
    ./dsadm create /var/opt/sun/directory/dsins1
    
  5. When prompted, type adminpass for the Directory Manager password.
  6. Create the user and group suffix o=isp.
    cd /opt/sun/directory/bin
    ./dsadm start /var/opt/sun/directory/dsins1
    ./dsconf create-suffix "o=isp"
    
  7. When prompted, type Y to accept the certificate.
  8. When prompted, type adminpass for the Directory Manager password.
  9. Continue with the next section.

Installing and Configuring Glassfish 2.1.1

Glassfish 2.1.1 is the primary web container used by Convergence, Delegated Administrator, Directory Service Control Center, and Instant Messaging.

  1. Move the downloaded Glassfish 2.1.1 installer sges_ee-2_1_1-linux-ml.bin to a temporary location, such as /tmp/GF211.
  2. Launch the installer.
    cd /tmp/GF211
    chmod u+x ./sges_ee-2_1_1-linux-ml.bin
    ./sges_ee-2_1_1-linux-ml.bin -console -javahome /usr/java/default/
    
  3. When prompted, press Enter to continue.
  4. Accept the License Agreement by typing yes when prompted.
    The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 6 Application Server Settings
    Option [Default Value] Enter:
    Installation Directory [/opt/SUNWappserver] /opt/sun/appserver
    Create Directory or Choose New Create Directory accept default
    Install Node Agent [yes] accept default
    Install High Availability Database Server [no] accept default
    Install Load Balancing Plugin [no] accept default
    Install Domain Administration Server [yes] accept default
    Install Sample Applications [yes] no
    Java Configuration [1. Install Java 2 SDK (5.0)] 2. Reuse existing Java 2 SDK
    Existing JDK Location [/usr/java/jdk1.6.0_20] /usr/java/latest
    Admin User [admin] accept default
    Admin User's Password adminpass
    Master Password for SSL Certificate adminpass
    Admin Port [4848] accept default
    HTTP Port [8080] 80
    HTTPS Port [8181] 443
    Enable Updatecenter client [yes] no
    Upgrade from previous AS version [no] accept default
  5. Select Install Now at the Ready to Install screen.
    The installer begins to install the software.
  6. Edit the /opt/sun/appserver/domains/domain1/config/domain.xml file to change the Java Message Queue (JMQ) port from 7676 to 37676
    change:
        <jms-host admin-password="admin" admin-user-name="admin" host="demo.comms.beta.com" name="default_JMS_host" port="7676"/>
    

    to:

        <jms-host admin-password="admin" admin-user-name="admin" host="demo.comms.beta.com" name="default_JMS_host" port="37676"/>
    
    Note
    By default, Glassfish Application 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 the Application Server:
    cd /opt/sun/appserver/bin
    ./asadmin start-domain domain1
    
  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 they don't need to be provided each time Application Server is started. (You must still type the master password.)
    cd /opt/sun/appserver/bin
    ./asadmin login
    
  10. Type admin and adminpass as the username and password when prompted.
  11. Continue with the next section.
Be sure to add the GlassFish Server administrative port (4848) to your firewall configuration. Otherwise, you cannot access the GlassFish Server console from a host located outside the firewall.

To Deploy and Enable Directory Server Control Center (DSCC)

The Directory Server Control Center is a web-based GUI used to configure and administer Directory Server instances.

  1. Enable the DSCC registry.
    cd /opt/sun/directory/bin/
    ./dsccsetup initialize
    
  2. When prompted, press Enter to continue.
  3. Accept the License Agreement.
  4. At the Choose password for Directory Service Manager prompt, type adminpass (the default password).
  5. Edit the /opt/sun/appserver/domains/domain1/config/server.policy file to add the following required DSCC permissions:
  6. Restart Application Server.
    cd /opt/sun/appserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    
  7. Type the master password when prompted: adminpass
  8. Access the Application Server administration console using a web-browser at the following location:
    https://fully-qualified-hostname:admin-port/
    In this example, type:
    https://demo.comms.beta.com:4848/
  9. Log in by using the admin username and adminpass password.
  10. To deploy application from the dscc7.war file, select Applications then Web Applications from the left-hand menu in the Administration Console.
  11. Select the Deploy option from the Web Applications menu.
  12. Select Local packaged file or directory that is accessible from the Application Server.
  13. Type the full path of the DSCC war file: /opt/sun/directory/var/dscc7.war.
  14. Click the OK button at the bottom of the page.
  15. Log out of the Administration Console once the DSCC deployment has completed.

To Register the existing Directory Server Instance in DSCC

  1. Add the Directory Server Instance to DSCC
    cd /opt/sun/directory/bin
    ./dsccreg add-server /var/opt/sun/directory/dsins1
    
  2. Type the DSCC administrator's password when prompted: adminpass
  3. Type the "cn=Directory Manager" password when prompted: adminpass
  4. At the prompt advising that Directory Server will be restarted, enter: y

To Access the Directory Server Instance in DSCC

  1. Access the DSCC console at the following location:
    http://_fully-qualified-hostname_:_application-server-port_/dscc7
    In this example, type:
    *http://demo.comms.beta.com/dscc7*
  2. Log in by using the admin username and adminpass password.
  3. Log out of the DSCC interface.
  4. Proceed to Installing Communications Suite Components for instructions on how to install and configure Communications Suite components.

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 LDAP Directory Server

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

To Apply Schema 2 to Your Directory Tree

  1. Change the directory where the comm_dssetup script is located and run the script, for example:
    cd /opt/sun/comms/dssetup/sbin/
    ./comm_dssetup.pl
    
  2. Type y to continue.
    The perl script prompts for a series of options. The following table shows how to respond to the prompts.
    Table 7 Values for comm_dssetup.pl Script
    Option [Default Value] Enter:
    Directory server root [/opt/sun/directory/var/dscc6/dcc] /var/opt/sun/directory
    Directory server instance [dsins1] accept default
    Directory Manager DN [cn=Directory Manager] accept default
    Directory Manager Password - adminpass
    Use directory server for users/groups [yes] accept default
    Users/Groups base suffix [o=isp] accept default
    Schema type? [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 script proceeds.
  4. When prompted, type y to continue with the script.
  5. Continue with the next section after comm_dssetup completes and the Successful Completion message is displayed.

Configuring Delegated Administrator and Communications CLI

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

To Configure Delegated Administrator

  1. Change to the directory where the configuration script was installed and run the script, for example:
    cd /opt/sun/comms/da/sbin
    ./config-commda -nodisplay
    
  2. Select Enter in the Welcome window.
  3. Accept the default, /var/opt/sun/comms/da, for the Directory to store Configuration and Data Files:
    If the directory does not exist, select Create Directory to create the directory.
  4. Install Delegated Administrator Utility, Console, and Server.
    The installation script prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 8 Values for config-commda Script
    Option [Default Value] Enter:
    DA Web-Container Hostname [demo.comms.beta.com] accept default
    DA Web-Container Port [8080] 80
    Default Domain [comms.beta.com] accept default
    Default SSL Port [443] accept default
    Web Container [Web Server 6.x/WEB] APP8
    Install Directory (for DA Console) [/opt/sun/appserver] accept default
    Domain Directory [/var/opt/sun/appserver/domains/domain1] /opt/sun/appserver/domains/domain1
    Doc Root Directory [/var/opt/sun/appserver/domains/domain1/docroot] /opt/sun/appserver/domains/domain1/docroot
    Server Target Name [server] accept default
    Virtual Server Identifier [server] accept default
    Server Instance HTTP Port [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [yes] accept default
    Default Domain Separator [@] accept default
    Directory Server Interface [DL] accept default
    Web Container [Web Server 6.x/WEB] APP8
    Install Directory (for DA Server) [/opt/sun/appserver] accept default
    Domain Directory [/var/opt/sun/appserver/domains/domain1] /opt/sun/appserver/domains/domain1
    Doc Root Directory [/var/opt/sun/appserver/domains/domain1/docroot] /opt/sun/appserver/domains/domain1/docroot
    Server Target Name [server] accept default
    Virtual Server Identifier [server] accept default
    Server Instance HTTP Port [80] accept default
    Administration Server Port [4849] 4848
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance? [yes] accept default
    URL of Directory Server [ldap://demo.comms.beta.com:389] accept default
    Bind As [cn=Directory Manager] accept default
    Password - adminpass
    Internal LDAP user (daAdmin) 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 [yes] accept default
    Load Sample Organizations [yes] no
  5. Select 1 - Configure Now.
    The script begins to run.
  6. When the panel displays "All Tasks Passed," hit enter to continue.
  7. Select 2. Done to exit the Delegated Administrator Configuration wizard.
  8. Modify the default domain to provide mail, calendar and IM services.
    cd /opt/sun/comms/da/bin/
    ./commadmin domain modify -D admin -w adminpass -d comms.beta.com -S mail,cal,im \
    -H demo.comms.beta.com -B demo.comms.beta.com
    
  9. Create a test user account with a username of jdoe and password of demo by using the commadmin utility:
    ./commadmin user create -D admin -w adminpass -S mail,cal,im -H demo.comms.beta.com -B demo.comms.beta.com \
    -F John -L Doe -l jdoe -W demo -d comms.beta.com -E jdoe@comms.beta.com
    

    You can create as many users as you like at this point.

  10. Continue with the next procedure.

To Log in to Delegated Administrator

  1. In your web browser, open a URL for Delegated Administrator.
    http://_fully-qualified-hostname_:_app-server-port_/da/
    In this example, type:
    *http://demo.comms.beta.com:80/da*
  2. Log in using admin and adminpass as the user ID and password.
  3. After verifying that you can access the Delegated Administrator GUI interface, log out.
  4. Continue with the next section to configure Messaging Server

Configuring Messaging Server

This section describes configuring Messaging Server.

To Configure Messaging Server

  1. Change to the directory where the Messaging Server configure script is stored, then run the script, for example:
    cd /opt/sun/comms/messaging64/bin
    ./configure
    

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

  2. The installation script prompts for a series of options.
    The following table shows how to respond to the configuration options:
    Table 9 Values for Messaging Server configure Script
    Option [Default Value] Enter:
    Path for Data and Configuration Files [/var/opt/sun/comms/messaging64] accept default
    Messaging Server Unix user [mailsrv] accept default
    Messaging Server Unix group [mail] accept default
    Fully qualified local hostname [demo.comms.beta.com] accept default
    Default mail domain name [comms.beta.com] accept default
    Hostname for LDAP Directory Server [localhost] accept default
    LDAP administrator login [cn=Directory Manager] accept default
    LDAP administrator password - adminpass
    Mail address for postmaster notices [admin@comms.beta.com] jdoe@comms.beta.com
    Password for server administration - adminpass
  3. Start Messaging Server.
    cd /opt/sun/comms/messaging64/bin
    ./start-msg
    
  4. Continue with the next section to configure Calendar Server.

Configuring MySQL Server

CalDAV server stores calendar data in a MySQL 5.1 database. This section steps through the configuration of the MySQL database so that it can be used by the CalDAV server software.

  1. Create the /etc/my.cnf MySQL configuration file.
    [mysqld]
    basedir = /usr
    datadir = /var/lib/mysql
    default-storage-engine = InnoDB
    character-set-server = utf8
    
  2. Set ownership of /etc/my.cnf
    chown mysql:mysql /etc/my.cnf
    
  3. Configure MySQL Root password
    /usr/bin/mysqladmin -u root password adminpass
    /usr/bin/mysqladmin -u root -h demo.comms.beta.com password adminpass
    
  4. Secure MySQL install by running the /usr/bin/mysql_secure_installation command.
    The following table shows how to respond to the configuration options:
    Table 10 MySQL Secure Installation Settings
    Option [Default Value] Enter:
    Current password for root - adminpass
    Change the root password [Y] n
    Remove anonymous users [Y] accept default
    Disallow root login remotely [Y] accept default
    Remove test database and access to it [Y] accept default
    Reload privilege tables now [Y] accept default
  5. Create MySQL user and CalDAV server database
    /usr/bin/mysql -u root -p
    Enter password: adminpass
    mysql> CREATE DATABASE caldav CHARACTER SET = UTF8;
    mysql> CREATE USER 'caldav'@'localhost' IDENTIFIED BY 'adminpass';
    mysql> GRANT ALL ON caldav.* TO 'caldav'@'localhost';
    mysql> exit
    
  6. Enable MySQL on boot
    chkconfig --add mysql
    

Configuring Calendar Server

  1. Run the Calendar Server configuration wizard
    cd /opt/sun/comms/davserver/sbin/
    ./init-config -nodisplay
    
  2. The installation script prompts for a series of options.
    The following table shows how to respond to the configuration options:
    Table 11 CalDAV Settings
    Option [Default Value] Enter:
    Configuration and data files directory [/var/opt/sun/comms/davserver] accept default
    Components to be configured [Oracle Communications Calendar Server] accept default
    Host Name [demo] accept default
    DNS Domain Name [comms.beta.com] accept default
    MySQL Server Host Name [localhost] accept default
    MySQL Server Port Number [3306] accept default
    Database User ID [caldav] accept default
    Database User Password - adminpass
    Calendar Database Name [caldav] accept default
    Document Files Directory [/var/opt/sun/comms/davserver/db] accept default
    Application Server Install Directory [/opt/sun/appserver] accept default
    Application Server Domain Directory [/opt/sun/appserver/domains/domain1] accept default
    Application Server Document Root Directory [/opt/sun/appserver/domains/domain1/docroot] accept default
    Application Server Instance Name [server] accept default
    Virtual Server Identifier [server] accept default
    Application Server Instance HTTP Port [8080] 80
    Administration Server Port [4848] accept default
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Administration Server instance running in the secure mode [yes] accept default
    URI Path for Sun Java Calendar Server 7 [/] /davserver
    Ldap URL [ldap://demo.comms.beta.com:389] accept default
    Bind DN [cn=Directory Manager] accept default
    Bind Password - adminpass
    DC Tree Suffix [o=isp] accept default
    Default Domain Name [comms.beta.com] accept default
    Organization DN [o=comms.beta.com,o=isp] accept default
    SMTP Server Host Name [demo.comms.beta.com] accept default
    SMTP Server Port Number [25] accept default
    Administrator User ID [calmaster] accept default
    Administrator Password - adminpass
  3. Select Configure Now to configure Calendar Server.
  4. Select Next when the configuration program completes.
  5. Continue with the next section to configure Instant Messaging Server.

Testing Calendar accounts

The CalDAV server has an account-browser. This can be used to verify that the account is functional and provides various other details for the account. The account-browser can be accessed at the following location:

http://_fully-qualified-hostname_:_app-server-port_/davserver/browse/h/_domain_/_username_/calendar/

For example, to access the jdoe user account details use the following URL:

*http://demo.comms.beta.com/davserver/browse/h/comms.beta.com/jdoe/calendar/*

CalDAV clients can be configured to access the CalDAV server by using the following URL:

http://_fully-qualified-hostname_:_app-server-port_/davserver/dav/h/_domain_/_username_/calendar/

For example, to access the jdoe user account use the following URL:

*http://demo.comms.beta.com/davserver/dav/h/comms.beta.com/jdoe/calendar/*

Additional information on configuring CalDAV clients can be found here in the Configuring CalDAV Clients for Calendar Server 7 documentation.

Configuring Instant Messaging Server

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

To Configure Instant Messaging Server

  1. Change to the directory where the configuration script was installed then run the configurator script, for example:
    cd /opt/sun/comms/im/sbin
    ./configure --nodisplay
    
  2. Select Next/Enter at the Welcome page.
    The Components Selection page appears.
  3. Select both Server and Client components for configuration.
  4. The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 12 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
    IM User Properties store location [1. On the file system] 2. In the directory
    User ID [inetuser] accept default
    Group ID [inetgroup] accept default
    Runtime Directory [/var/opt/sun/im] /var/opt/sun/comms/im
    Create User ID? [2. Choose New] 1. Create User ID
    Create Directory? [2. Choose New] 1. 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 [demo.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 [demo.comms.beta.com] accept default
    Enable Email Archiving [yes] accept default
    Deploy Messenger Resources [yes] accept default
    Codebase [http://demo.comms.beta.com:80/im] accept default
    Enable Audio [no] yes
    Webcontainer Path - /opt/sun/appserver
    Web Administration URL - *https://demo.comms.beta.com:4848/*
    Web Administrator User Id [admin] accept default
    Web Administrator Password - adminpass
    Deploy IM HTTP Gateway [yes] no
    Deploy IM IMPS Gateway [yes] no
    Enable Calendar Agent [no] accept default
    Enable local component [no] 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
  5. At the Configuration Summary page, select Done to exit.
  6. Edit the /opt/sun/comms/im/config/iim.conf file using your preferred editor, e.g. vi, to prepare for the Convergence web-interface.
    Add the new httpbind and avatar component JIDs to this file by making the following changes/additions:
    ! known components/agent. Add yours as needed
    !iim_server.components = "agent-calendar,httpbind,smppbind,msn_gateway,aim_gateway,yim_gateway"
    iim_server.components = "agent-calendar,httpbind,smppbind,msn_gateway,aim_gateway,yim_gateway,avatar"
    iim_agent.enable = "true"
    
    ! httpbind component (HTTP/XMPP Gateway)
    ! ======================================
    iim_agent.httpbind.enable = "true"
    httpbind.jid = "demo.httpbind.comms.beta.com"
    httpbind.password = "adminpass"
    
    ! avatar component
    ! ======================================
    iim_agent.avatar.enable = "true"
    avatar.jid = "demo.avatar.comms.beta.com"
    avatar.password = "adminpass"
    
    Note
    The httpbind.jid and avatar.jid strings are in the form <host>.httpbind.<domain> and <host>.avatar.<domain> respectively as this will be the value auto-generated during upcoming Convergence configuration stage.

    Enable Hosted Domain Schema 2 support by making the following changes/additions:

    ! whether to use Identity Server for policy storage, default to no (iim_ldap)
    !iim.policy.modules = "iim_ldap"
    iim.policy.modules = "iim_ldap_schema2"
    iim_ldap.schema2.domain_config_root = "o=isp"
    
  7. Start the Instant Messaging server.
    cd /opt/sun/comms/im/sbin/
    ./imadmin start
    
  8. Continue with the next procedure.

To Log into the Sun Instant Messaging Java Client

  1. In your web browser, open the URL for the Sun IM Java Client and log in as a test user:
    http://fully-qualified-hostname:app-server-port/im
    In this example, type:
    *http://demo.comms.beta.com:80/im*
  2. Click the "Start" button.
  3. Log into the Sun Java IM client using jdoe and demo as the User Name and Password.
  4. After verifying that you can access the Sun Java IM client, exit the client.

Configuring Sun Convergence

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

  1. Change to the directory where you installed the Convergence then run the configuration utility, for example:
    cd /opt/sun/comms/iwc/sbin
    ./init-config -nodisplay
    
  2. Select Next/Enter at the Welcome page.
  3. Accept the default value for the Directory to store Configuration and Data Files: /var/opt/sun/comms/iwc
    If the directory does not exist, select Create Directory to create the directory.
  4. Configure the Mail, Calendar and Instant Messaging Services.
  5. The configuration wizard prompts for a series of options. The following table shows how to respond to the configuration options:
    Table 13 Values for Convergence configure Script
    Option [Default Value] Enter:
    Host Name [demo] accept default
    DNS Domain Name [comms.beta.com] accept default
    Application Server Install Directory [/opt/sun/appserver] accept default
    Domain Directory [/opt/sun/appserver/domains/domain1] accept default
    Document Root Directory [/opt/sun/appserver/domains/domain1/docroot] accept default
    Server Target Name [server] accept default
    Virtual Server Identifier [server] accept default
    Server Instance HTTP Port [8080] 80
    Administration Server Port [4848] accept default
    Administrator User ID [admin] accept default
    Administrator Password - adminpass
    Secure Administration Server Instance [yes] accept default
    URI Path [/iwc] accept default
    Enable Hosted Domain Support [yes] accept default
    Directory Server LDAP URL [ldap://demo.comms.beta.com:389/] accept default
    Bind DN [cn=Directory Manager] accept default
    Bind Password - adminpass
    DC Tree suffix [o=isp] accept default
    Default Domain Name [comms.beta.com] accept default
    Webmail Server Host Name [demo.comms.beta.com] accept default
    Webmail Server Port Number [8990] accept default
    Webmail Server Running In Secure Mode? [no] accept default
    Webmail Server Admin User ID [admin] admin@comms.beta.com
    Webmail Server Admin Password - adminpass
    Calendar Server Version [7] accept default
    Calendar Server Host Name [demo.comms.beta.com] accept default
    Calendar Server Port Number [80] accept default
    Calendar Server Running In Secure Mode? [no] accept default
    Calendar Server Service URI [/davserver/wcap] accept default
    Calendar Server Admin User ID [calmaster] calmaster@comms.beta.com
    Calendar Server Admin Password - adminpass
    Instant Messaging Server Domain Name [comms.beta.com] accept default
    Instant Messaging Server Host Name [demo.comms.beta.com] accept default
    Server Port [5269] accept default
    httpbind Component JID [demo.httpbind.comms.beta.com] accept default
    Password - adminpass
    Avatar Component JID [demo.avatar.comms.beta.com] accept default
    Password - adminpass
    Convergence Administrator Username [admin] accept default
    Password - adminpass
  6. Select 1. Configure Now to configure Sun Convergence.
  7. Once the configuration is completed, exit the configuration tool.
  8. Continue with the next procedure.
  1. Restart Application Server.
    cd /opt/sun/appserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    

To Log into the Sun Convergence Client

  1. In your web browser, open a URL for Sun Convergence and log in as a test user. The URL for Sun Convergence is:
    http://fully-qualified-hostname:app-server-port/iwc
    In this example, type:
    *http://demo.comms.beta.com:80/iwc*
  2. Log in using jdoe and demo as the user ID and password.
  3. After verifying that you can access the Sun Convergence Client, log out.

Creating Additional User Accounts and Groups

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

To Create Users and Groups using CLI

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

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

To Use the Delegated Administrator GUI to Create Users

An alternative to using the Delegated Administrator command-line utility to create users is to use the Delegated Administrator web-based GUI. The high-level steps for creating users with Delegated Administrator are:

  1. The first time you use the Delegated Administrator GUI, you must add service packs to the organization that contains your users:
    • In your web browser, open the URL for Delegated Administrator.
      In this example, type:
      *http://demo.comms.beta.com:80/da*
    • Log in using admin as the Login ID and adminpass as the Password.
    • Click the check box next to comms.beta.com organization, then click the Allocate Service Package button.
    • The Allocate Service Package window appears with a list of service packages organized within a set of three pages. Near the top of this list is a Compare button.
    • To the right of this button is a button that maps the three pages into a single view. Click the Single Page button.
    • Select the desired service packages then click Next. The mailcalendarimsample service package is appropriate for this example, since this package enables the mail, calendar and instant messaging services.
    • Accept the Mail Service defaults, then click Next.
      Note
      If the Preferred Mail Host value is not set to the mail server host name demo.comms.beta.com in the Mail Service Details screen, close the window, log out of the Delegated Administrator GUI and return to the start of these steps.
    • If you chose a service package that contains Calendar, type the Calendar Host demo.comms.beta.com and Yes for Anonymous Login. Then click Next.
    • Select the quantity of each service pack desired then click Next. A quantity of 100 is appropriate for this example.
    • Review your choices and click Finish to create the service packages.
    • Once the service packs have been allocated for the domain, you can add users to the domain.
  2. Click the domain link. That is, click the comms.beta.com link
  3. Click the New button to create a new user within this domain. The New User window should appear.
  4. Type a First Name (such as Demo), a Last Name (such as Five), a Display Name (such as Demo Five), then click Next.
  5. You do not need to type postal information. Click Next again.
  6. Select a service pack for this user (as added earlier), for example, mailcalendarimsample, then click Next.
  7. Type the email address, for example, Demo.Five@comms.beta.com. The Mail Delivery Option should be Local Inbox. Leave the remaining fields blank then click Next.
  8. For the Calendar Service Details page, select your preferred timezone, then click Next.
  9. For the IM Service Details page, leave the User Roster field blank and click Next.
  10. Type the Login ID and Password then click Next. In this example, Login ID is demo5 and password is demo.
  11. Verify the user information then click Finish to create the user.

Enabling service start-up on boot

The following guide steps through the process of enabling Communications Suite 7 Update 1 services to start automatically on boot and stop automatically on shut-down.

Communications Suite 7 Update 1 Start and Stop Scripts (Linux)

Hosted domain configuration and creation

Hosted Domains, or Virtual Domains as they are also referred to, is a mechanism used to administrate and deliver services for users, groups and resources within a unique name-space. Each hosted domain can have different domain-level preferences, different Convergence customizations and be administrated within Delegated Administrator by different user accounts if required.

In a hosted domain installation, each domain shares the same instance of Messaging Server, Instant Messaging Server, Calendar Server, Convergence etc. This approach greatly reduces any overhead associated with using multiple hosted domains on a single server.

Create new hosted domain using Delegated Administrator

During the installation and configuration of Communications Suite 7 Update 1, an initial Default Domain of comms.beta.com is created. The creation of additional hosted domains can be achieved using either the Delegated Administrator CLI commadmin utility or the Delegated Administrator GUI interface.

Delegated Administrator CLI
Run the following command sequence to create the new hosted domain hosted.domain.com using the Delegated Administrator command-line utility.

cd /opt/sun/comms/da/bin/
./commadmin domain create -D admin -w adminpass -d hosted.domain.com -S mail,cal,im \
-H demo.comms.beta.com -B demo.comms.beta.com

Delegated Administrator GUI

Follow these steps to create the new hosted domain hosted.domain.com using the Delegated Administrator GUI interface.

  1. In your web browser, open the URL for Delegated Administrator.
    In this example, type:
    *http://demo.comms.beta.com:80/da*
  2. Log in using admin as the Login ID and adminpass as the Password.
  3. Click on the New Organization button. The New Organization window should then appear.
  4. In the Organization Information step, enter the new hosted domain hosted.domain.com in the Organization Name field then click the Next button.
  5. You do not need to type Contact Information. Click Next again.
  6. In the Account Information step, enter the new hosted domain hosted.domain.com again then click Next.
  7. At this point you will assign Service Packages to the domain using these steps:
    • 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 mailcalendarimsample service package is appropriate for this example, since this package enables the mail, calendar and instant messaging services.
    • Accept the Mail Service defaults, then click Next.
      Note
      If the Preferred Mail Host value is not set to the mail server host name demo.comms.beta.com in the Mail Service Details screen, close the window, log out of the Delegated Administrator GUI and return to the start of these steps.
    • If you chose a service package that contains Calendar, type the Calendar Host demo.comms.beta.com and Yes for Anonymous Login. Then click Next.
    • Select the quantity of each service pack desired then click Next. A quantity of 100 is appropriate for this example.
    • Review your choices and click Finish to create the service packages.
    • Once the service packs have been allocated for the domain, you can continue.
  8. Verify the new hosted domain information then click Finish to create the domain.

Configure Convergence for the new hosted domain

Each new hosted domain must be manually registered with the Convergence Instant Messaging gateway so that users in this domain are able to access the Instant Messaging interface within Convergence.

  1. Edit /opt/sun/comms/iwc/config/httpbind.conf with your preferred editor
  2. Add the new domain to default.domains option. For example if your new hosted domain was hosted.domain.com your defaults.domain configuration line would resemble the following:
    default.domains=comms.beta.com hosted.domain.com
    
  3. Restart Application Server.
    cd /opt/sun/appserver/bin
    ./asadmin stop-domain domain1
    ./asadmin start-domain domain1
    
  4. Type the master password when prompted: adminpass

Add new users to new hosted domain

Refer to the Creating Additional User Accounts and Groups steps. Substitute in the newly created hosted domain name hosted.domain.com for every instance of the comms.beta.com domain in the steps.

Users in the newly created hosted domain log into the Convergence and UWC/Communications Express interface using the uid@hosted-domain-name format in the user login field.

Single host installation tuning tips

  • Use memory-mapped tmpfs file system for temporary server files

Red Hat Enterprise Linux 5 by default provides the /dev/shm memory-mapped temporary file system:

[root@comms sbin]# df -k /dev/shm
Filesystem           1K-blocks      Used Available Use% Mounted on
tmpfs                   387596    121488    266108  32% /dev/shm

Messaging Server, Directory Server and Instant Messaging server can all be configured to relocate temporary files to a memory-mapped file-system to reduce the number of I/O operations that are recorded to permanent storage.

Messaging Server

  1. Relocate the mboxlist temporary database files to the temporary file-system.
    cd /opt/sun/comms/messaging64/bin
    ./configutil -o store.dbtmpdir -v /dev/shm/msg-demo/
    
  2. Restart Messaging Server
    cd /opt/sun/comms/messaging64/bin
    ./stop-msg
    ./start-msg
    

Directory Server
Relocate the directory server temporary database files to the temporary file-system.

  1. Stop directory server
    cd /opt/sun/directory/bin
    ./dsadm stop /var/opt/sun/directory/dsins1/
    
  2. Edit /var/opt/sun/directory/dsins1/config/dse.ldif
    replace:
    nsslapd-db-home-directory: /var/opt/sun/directory/dsins1/db
    
    with:
    nsslapd-db-home-directory: /dev/shm/slapd-demo/
    
  3. Start Directory Server
    cd /opt/sun/directory/bin
    ./dsadm start /var/opt/sun/directory/dsins1/
    

Instant Messaging Server
Relocate the Instant Messaging server temporary "scratch" files to the temporary file-system.

  1. Stop the Instant Messaging Server
    cd /opt/sun/comms/im/sbin
    ./imadmin stop
    
  2. Edit /opt/sun/comms/im/config/iim.conf and add the following line:
    iim_server.scratch_directory = "/dev/shm/iim-demo/"
    
  3. Start the Instant Messaging Server
    cd /opt/sun/comms/im/sbin
    ./imadmin start
    

Known Issues and Limitations

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

Labels:
installing installing Delete
calendarserver calendarserver Delete
linux linux Delete
messagingserver messagingserver Delete
directoryserver directoryserver Delete
convergence convergence Delete
caldavserver caldavserver Delete
example example Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Jan 16, 2014

    Hi,

    I am trying to setup this suite in redhat 64-bit linux environment. I am facing issues while configuring Glassfish server. In the process it asks for admin username and when I give some name I am getting the following error. Could someone please help me. Thanks in advance. The error stacktrace is here :

    Exception in thread "Thread-4" java.lang.UnsatisfiedLinkError: /tmp/sges_xmKotb/package/libPassword.so: /tmp/sges_xmKotb/package/libPassword.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)
            at java.lang.ClassLoader$NativeLibrary.load(Native Method)
            at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750)
            at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675)
            at java.lang.Runtime.loadLibrary0(Runtime.java:840)
            at java.lang.System.loadLibrary(System.java:1047)
            at com.sun.enterprise.installer.utilities.PasswordUtil.<clinit>(PasswordUtil.java:29)
            at com.sun.enterprise.installer.dialogs.NewConfigInfoPanel.consoleInteraction(NewConfigInfoPanel.java:1194)
            at com.sun.wizards.core.IteratorLayout.cliConsoleInteraction(IteratorLayout.java:786)
            at com.sun.wizards.core.AutonextController.displayPanel(AutonextController.java:562)
            at com.sun.wizards.core.AutonextController.setCurrentPanel(AutonextController.java:486)
            at com.sun.wizards.core.IteratorLayout.setCurrentLeaf(IteratorLayout.java:618)
            at com.sun.wizards.core.IteratorLayout.next(IteratorLayout.java:982)
            at com.sun.wizards.core.WizardTreeManager.actualNextButtonPressed(WizardTreeManager.java:1344)
            at com.sun.wizards.core.WizardTreeManager.nextButtonPressed(WizardTreeManager.java:1371)
            at com.sun.wizards.core.IteratorLayout.run(IteratorLayout.java:861)
            at java.lang.Thread.run(Thread.java:679)
    Deleting temporary files...
    Exception in thread "Thread-4" java.lang.UnsatisfiedLinkError: /tmp/sges_xmKotb/package/libPassword.so: /tmp/sges_xmKotb/package/libPassword.so: wrong ELF class: ELFCLASS32 (Possible cause: architecture word width mismatch)

            at java.lang.ClassLoader$NativeLibrary.load(Native Method)

            at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1750)

            at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1675)

            at java.lang.Runtime.loadLibrary0(Runtime.java:840)

            at java.lang.System.loadLibrary(System.java:1047)

            at com.sun.enterprise.installer.utilities.PasswordUtil.<clinit>(PasswordUtil.java:29)

            at com.sun.enterprise.installer.dialogs.NewConfigInfoPanel.consoleInteraction(NewConfigInfoPanel.java:1194)

            at com.sun.wizards.core.IteratorLayout.cliConsoleInteraction(IteratorLayout.java:786)

            at com.sun.wizards.core.AutonextController.displayPanel(AutonextController.java:562)

            at com.sun.wizards.core.AutonextController.setCurrentPanel(AutonextController.java:486)

            at com.sun.wizards.core.IteratorLayout.setCurrentLeaf(IteratorLayout.java:618)

            at com.sun.wizards.core.IteratorLayout.next(IteratorLayout.java:982)

            at com.sun.wizards.core.WizardTreeManager.actualNextButtonPressed(WizardTreeManager.java:1344)

            at com.sun.wizards.core.WizardTreeManager.nextButtonPressed(WizardTreeManager.java:1371)

            at com.sun.wizards.core.IteratorLayout.run(IteratorLayout.java:861)

            at java.lang.Thread.run(Thread.java:679)

    Deleting temporary files...

    1. Jan 16, 2014

      This document is now out of date. See Communications Suite on a Single Host (Linux) to install UCS 7.0.5. Also, make sure that the version of RHL you are using is supported. See Operating System Requirements.

      If the problem persists, please either try opening up a call if you have a support contract or try posting your question to the UCS software forum, here: https://communities.oracle.com/portal/server.pt/community/unified_communications_suite/

      Regards,

      Joe

  2. Jan 16, 2014

    hey Joesciallo,

    thanks alot. Will make try with this

    Best Wishes,

    Vamshi

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.