7/17

4 Calendar Server Pre-Installation Tasks

This chapter describes the pre-installation tasks that you must complete before you can install Oracle Communications Calendar Server.

Pre-installation and configuration tasks include:

• Installing Java

• Installing GlassFish Server

• Installing Directory Server

• Installing the Database

Installing Java

Oracle GlassFish Server is a Java application and needs a Java environment in which to run.

The 32-bit and 64-bit JDKs require manual installation. Install both JDKs, rather than the JRE, on your front-end hosts.

To get the Java software, go to the Java SE Downloads at:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

For information about installing Java, see the Installing Java for Communications Suite documentation at:

https://wikis.oracle.com/display/CommSuite

Installing GlassFish Server

To install and configure GlassFish Server, see Oracle GlassFish Server 3.1.2 Installation Guide at:

http://docs.oracle.com/cd/E26576_01/doc.312/e24935/installing.htm#ggssq

Installing Directory Server

Calendar Server uses Oracle Directory Server Enterprise Edition to store and access LDAP data for individual users, groups, and domains.

If your site does not currently have Directory Server deployed, and you need to install it, see the Oracle Directory Server Enterprise Edition documentation at:

http://docs.oracle.com/cd/E29127_01/index.htm

Prior to installing and configuring Calendar Server, you must also prepare the Directory Server LDAP schema by running the comm_dssetup.pl script. This script, which is provided as part of the Unified Communications Suite installer, adds the necessary Communications Suite schema to the LDAP. See "Preparing Directory Server" for more information.

Some LDAP object classes in the Communications Suite schema specifically support Calendar Server. To understand the schema that is used by Calendar Server, refer to Communications Suite Schema Reference at:

https://wikis.oracle.com/display/CommSuite/Communications+Suite+Schema+Reference

The davcore.ldapattr.* configuration parameters govern the default values for LDAP attributes and object classes used by Calendar Server. Default values are set based on the Communications Suite schema. See the topic on Calendar Server configuration parameters in Calendar Server System Administrator's Guide for more information.

Installing the Database

You can use either Oracle Database or MySQL Server as the Calendar Server database (the calendar store). You cannot mix database types in a deployment.

If you have a multiple host deployment, you can install all databases and complete all database preparation before installing Calendar Server. When you configure Calendar Server by running the init-config script, you choose one to be the primary database. You then configure the other databases as described in "Configuring Calendar Server with Multiple Hosts."

Depending on your database choice, go to one of the following tasks:

• Installing and Configuring MySQL Server

• Installing and Creating an Oracle Database Instance for Calendar Server

Installing and Configuring MySQL Server

To install and configure MySQL Server:

1. Download the MySQL Server software from My Oracle Support, at:

   http://support.oracle.com

   See "Required Software" for information about supported versions of MySQL Server.

2. As root, add the new MySQL package.

   Note:

   Adding the new package on Red Hat Linux might cause the system to automatically run the mysql_upgrade command. This is fine in the context of this procedure.

   • On Solaris:

     pkgadd -d mysql-advanced-5.x.xx-solaris10-sparc-64bit.pkg
     

   • On Linux 6:

     rpm --ivv MySQL-server-advanced-5.x.xx-1.el6.x86_64.rpm
     rpm --ivv MySQL-client-advanced-5.x.xx-1.el6.x86_64.rpm
     

   Linux has two MySQL RPMs, client and server, that you must add.

3. If the MySQL /etc/my.cnf configuration file is absent, create it with the following content:

   • Solaris OS:

     [mysqld]
     basedir = /opt/mysql/mysql
     datadir = /var/mysql
     default-storage-engine = InnoDB
     character-set-server = utf8mb4
     transaction-isolation = READ-COMMITTED
     

   • Red Hat Linux or Oracle Linux:

     [mysqld]
     basedir = /usr
     datadir = /var/mysql
     default-storage-engine = InnoDB
     character-set-server = utf8mb4
     transaction-isolation = READ-COMMITTED
     

   Change the value of basedir and datadir if needed. Make sure there are no extra spaces if you cut and paste the path.

4. If you use replication, use ROW binary logging, instead of the default STATEMENT logging, by adding the following line to the /etc/my.cnf file:

   binlog-format=ROW
   

5. Set values for cache size, max connection size, and other parameters that impact MySQL Server performance.

   For example, see the MySQL Server Tuning information in Calendar Server System Administrator's Guide.

6. Remove the log_long_format entry from the /etc/my.cnf file. Use of the log_long_format is no longer a valid configuration option in 5.5. If you do not remove it, MySQL Server does not start.

7. Start MySQL Server:

   /etc/init.d/mysql start
   

Continue with the "Installing Calendar Server" section.

Installing and Creating an Oracle Database Instance for Calendar Server

You can install an Oracle Database for Calendar Server in one of the following ways:

• Installing a New Oracle Database

• Creating a New Database From an Existing Oracle Installation

• Using an Existing Database for the Calendar Server Schema

Note:

The Oracle Database instance must be a Unicode database, that is, the database character set must be AL32UTF8. Calendar Server does not support non-Unicode database character sets.

Installing a New Oracle Database

You install and create the Oracle Database instance by using the Oracle Universal Installer.

1. Download Oracle Database from the Oracle Technology Network website at:

   http://www.oracle.com/technetwork/database/enterprise-edition/downloads/index.html

2. To install and create a new Oracle Database instance, follow the instructions in the installation guide for Oracle Database for your operating system, at:

   • Oracle Database 11g, Release 2:

     http://www.oracle.com/pls/db112/portal.portal_db?selected=11

   • Oracle Database 12:

     http://docs.oracle.com/database/121/nav/portal_11.htm

3. When installing and creating the database instance, follow these guidelines:

   • On UNIX and Linux installations, ensure that you set the directory owner, group, and permissions correctly.

   • When selecting the database character set in the Specify Database Configuration Options window, select UTF-8 AL32UTF8. Deselect the Create database with sample schema option in the Database Example section.

   • When choosing the database management method in the Select Database Management Options window, select Use Database Control for Database Management.

Continue with "Installing Calendar Server."

Creating a New Database From an Existing Oracle Installation

You create a new Oracle Database instance by using the Oracle Database Configuration Assistant (DBCA).

1. To create an Oracle Database instance, follow the instructions in the topic on creating and managing a database with DBCA in Oracle Database 2 Day DBA documentation, at:

   • Oracle Database 12c:

     http://docs.oracle.com/database/121/ADMQS/install.htm#ADMQS0232

   • Oracle Database 11g, Release 2:

     http://docs.oracle.com/cd/E11882_01/server.112/e10897/install.htm#ADMQS0232

2. When creating the database instance, follow these guidelines:

   • When choosing the template, select the default General Purpose.

   • When choosing the database management method in the Select Database Management Options window, select Use Database Control for Database Management.

   • When choosing the storage options, select File System.

   • When choosing database content, deselect the sample schema.

   • When selecting the database character set in the Specify Database Configuration Options window, select UTF-8 AL32UTF8.

Continue with "Installing Calendar Server."

Using an Existing Database for the Calendar Server Schema

You can use an existing Oracle database for the Calendar Server schema if the database is configured to use the AL32UTF8 Unicode character set. If the database uses the Unicode character set, you prepare the database for use with Calendar Server after installing Calendar Server.

You can check whether the Oracle Database instance is running with the AL32UTF8 database character set by typing the following query using Oracle SQL*Plus SQL Plus:

SELECT * FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER LIKE 'NLS_CHARACTERSET';

Examine the results.

If the query returns AL32UTF8, the database can be used for creating Calendar Server schema. Continue with "Installing Calendar Server."

If the query does not return AL32UTF8, you must either create a new database that uses AL32UTF8 or migrate the database character set to AL32UTF8. Database character set migration is usually an intricate process that requires careful planning and execution strategies. For details, consult Oracle Database Globalization Support Guide for the character set migration chapter, and documentation for Oracle Database Migration Assistant for Unicode. To create a new database instance, follow the instructions in the "Using an Existing Database for the Calendar Server Schema" section.