Communications Suite 7 Installation Scenario - Calendar Server 7

Communications Suite 7 Installation Scenario - Calendar Server 7 (CalDAV Server)

Topics:

Overview of This Scenario

The following installation information describes how to install and configure Calendar Server 7 (CalDAV Server). It assumes you have already made your architectural and design decisions. For example, it assumes that you know the total number of servers in your deployment, the number of front-end and back-end servers, and so on. If you are still in the planning or evaluating process, see the following documents:

Assumptions

This scenario shows how to install Calendar Server 7 on a separate host. It is based on the Install Calendar Server 7 leaf in the Communications Suite 7 Installation Flowchart. The scenario makes these assumptions:

  • You are deploying Communications Suite on a single host or Solaris zone, or multiple hosts or Solaris zones.
  • A Directory Server host is already installed.

Which Software Components and Downloads Do You Need?

  • Communications Suite: Calendar Server, MySQL Server (installed as a dependent product for Calendar Server)
  • Application server web container for Calendar Server: GlassFish
  • LDAP server: Directory Server

Installing and Configuring a Calendar Server 7 Deployment

The tasks to install a Calendar Server 7 deployment are as follows:

Note
If you are installing a Calendar Server 7 front end on one host and a Calendar Server 7 back end on a separate host, note the following installation differences:
  • If you don't have an existing MySQL server, install one by using the ~3 option of the Communications Suite installer.
  • Uncheck the dependency of MySQL when installing the Calendar Server 7 software.
  • Configure MySQL Server.
  • Configure Calendar Server 7.
To Check Requirements for Calendar Server 7

See Requirements for Calendar Server 7.

To Get the Software
  1. Go to Get the Software.
    From this site, download Communications Suite 7. Also download GlassFish Enterprise Server 2.1 Patch 02, and Directory Server 6.3.1, which are required for Calendar Server 7.
  2. Continue with the next task.
To Install Directory Server

See Communications Suite 7 Installation Scenario - Directory Server.

To Install and Configure GlassFish Enterprise Server 2.1 Patch 02

See Communications Suite 7 Installation Scenario - GlassFish Enterprise Server.

To Install the Calendar Server and MySQL Server Software
  1. Make sure you have met the pre-installation requirements.
  2. To install Calendar Server, run the Communications Suite installer.
    The installer is a single unified utility called commpkg. It installs (but does not configure) the Communications Suite products. commpkg does all the necessary preparation work before installing the product software on the system. Run the following command:
    ./commpkg install
    

    For more information, see commpkg install Usage.

  3. Select Calendar Server 7 and proceed with the installation.
    MySQL Server is automatically selected as a dependent product. If you need to install just MySQL Server (for a multi-host deployment with a MySQL Server back-end host), type ~option number, for example: ~3.
    The default installation directory for Calendar Server 7 is /opt/sun/comms/davserver.
  4. If the installer detects older versions of LDAP tools, you are prompted to change them.
    You must answer y, otherwise, during the initial configuration (running init-config), the ldapmodify command does not run.
    Shared component LDAPCSDK6 has a different pkg version installed
    Description: ldap c sdk 6
      Current pkg Version (SUNWldapcsdk-libs): 6.00,REV=2005.11.29.16.11
      To be installed pkg version (SUNWldapcsdk-libs): 6.00,REV=2006.12.11.00.35
      Product Version: 6.0
    Note that changing pkg versions is irreversible
    On the other hand, if you do not change it,
    some products may not work properly
    An alternative is to start over and do a multi-install using --altroot
    
    Do you wish to change pkg versions for LDAPCSDK6 [n] : y
    
    Shared component LDAPCSDK6 Tools has a different pkg version installed
    Description: ldap c sdk 6 Tools
      Current pkg Version (SUNWldapcsdk-tools): 6.00,REV=2005.11.29.16.11
      To be installed pkg version (SUNWldapcsdk-tools): 6.00,REV=2006.12.11.00.35
      Product Version: 6.0
    Note that changing pkg versions is irreversible
    On the other hand, if you do not change it,
    some products may not work properly
    An alternative is to start over and do a multi-install using --altroot
    
    Do you wish to change pkg versions for LDAPCSDK6 Tools [n] : y
    
  5. Continue with the next section.
To Initialize and Configure MySQL Server

You can either run the following steps in this section or run the config-mysql script to prepare a new MySQL installation for use with the Calendar Server 7. For more information on running the config-mysql} script, see Running the Calendar Server 7 config-mysql Script.

The Communications Suite installer has already created a mysql group and a mysql user, and installed the MySQL Server software. The Solaris OS default base directory (basedir) is /opt/mysql/mysql. The Red Hat Linux default base directory (basedir) is /usr and the data directory (datadir)is /var/lib/mysql.

  1. Initialize the database.
    1. Remove the pre-created data, for example:
      # rm -rf /opt/mysql/mysql/data
      # rm -rf /var/lib/mysql
      
    2. Create an initial database, for example:
      # /opt/mysql/mysql/scripts/mysql_install_db --user=mysql --ldata=/var/mysql
      

      Substitute a different directory for /var/mysql if desired.

  2. Create the MySQL configuration file, /etc/my.cnf with the following content:
    Change basedir and datadir if needed. Make sure there are no extra spaces if you cut and paste the path.
    [mysqld]
    basedir = /opt/mysql/mysql
    datadir = /var/mysql
    default-storage-engine = InnoDB
    character-set-server = utf8
    
  3. Install startup script
    # cp /opt/mysql/mysql/support-files/mysql.server /etc/init.d/mysql
    
  4. Start MySQL Server.
    # /etc/init.d/mysql start
    
  5. Change the MySQL root password.
    # /opt/mysql/mysql/bin/mysqladmin -u root password '<password>'
    

    Replace 'password' with the appropriate password to use for the root user.

  6. Run the secure MySQL installation (disables remote root access, removes anonymous users, removes test databases, and so on).
    # /opt/mysql/mysql/bin/mysql_secure_installation
    
  7. Create the MySQL user and caldav database based on the sample session that follows.
    The following examples use 'caldav' as the MySQL user name and 'caldav' as the database name. You can use different names.
    Replace 'localhost' with the calendar server host name if the MySQL server is on a remote host (or use '%' for any host). Also replace 'password' with the appropriate password to use for the caldav user.
    See MySQL CREATE USER syntax.
    # /opt/mysql/mysql/bin/mysql -u root -p
    Enter password:
    mysql> CREATE DATABASE caldav CHARACTER SET = UTF8;
    mysql> CREATE USER 'caldav'@'localhost' IDENTIFIED BY 'caldav';
    mysql> SET PASSWORD FOR 'caldav'@'localhost' = PASSWORD('caldav'); 
    mysql> GRANT ALL ON caldav.* TO 'caldav'@'localhost';
    mysql> exit
    
  8. Configure MySQL to start automatically upon system reboot.
    1. Option 1:
      # ln /etc/init.d/mysql /etc/rc3.d/S99mysql
      
    2. Option 2:
      Configure MySQL to run with Solaris Management Facility (SMF).
      See the following links for information on how to configure MySQL to run with Solaris Management Facility (SMF):
  9. Continue with the next section.

Configuring Calendar Server 7

See Calendar Server 7 Initial Configuration.

Configuring Calendar Server 7 With Multiple Hosts

See Calendar Server 7 Multiple Hosts Scenarios.

Verifying the Calendar Server Configuration

See Configuring CalDAV Clients for Calendar Server 7.

Labels

caldavserver caldavserver Delete
installationscenario installationscenario Delete
guide guide Delete
ne ne Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Oct 01

    hadya says:

    When I run glassfish installer I am getting following error bramha>/var/tmp-...

    When I run glassfish installer I am getting following error

    bramha>/var/tmp-# ./sges_ee-2_1-p02-solaris-i586.bin -console
    Checking available disk space...
    Checking Java(TM) 2 Runtime Environment...
    Launching Java(TM) 2 Runtime Environment...
    Error: There are no files requiring installation.
    Deleting temporary files...
    bramha>/var/tmp-#

    bramha>/var/tmp-# java -version
    java version "1.6.0_16"
    Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
    Java HotSpot(TM) Server VM (build 14.2-b01, mixed mode)
    bramha>/var/tmp-#

    Then I went and installed sges_ee-2_1-solaris-i586-ml.bin which installed app server. I tried again I am getting error. Does this prevent me in proceeding with calendar installation

    1. Oct 02

      joesciallo says:

      hadya, First check if your GlassFish Server is up and running. For example, you...

      hadya,

      First check if your GlassFish Server is up and running. For example, you access the server:port and the administration console?
      If not, you need to first resolve that issue.

      Joe

  2. Oct 29

    sje says:

    i installed calendar server 7 from ci-7.0-0.02-SunOS_sparc.zip, however there wa...

    i installed calendar server 7 from ci-7.0-0.02-SunOS_sparc.zip, however there was no mention of mysql, or a config-mysql script. do i need to install this separately?

    1. Oct 30

      joesciallo says:

      When you choose to install CS 7 from the Comms Installer, it automatically also ...

      When you choose to install CS 7 from the Comms Installer, it automatically also installs MySQL (default install directory is /opt/mysql/mysql). You then need to follow the steps on this page to initialize and configure MySQL.

      HTH,

      Joe

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


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

Copyright 1994-2009 Sun Microsystems, Inc.
Powered by Atlassian Confluence
Sun Guidelines on Public Discourse Privacy Policy Terms of Use Trademarks Site Map Employment Investor Relations Contact