3 Calendar Server System Requirements

This chapter describes the hardware, operating system, software, and database requirements for installing Oracle Communications Calendar Server.

Software Requirements

Calendar Server is installed on an Oracle GlassFish Server domain. It uses either Oracle Database or MySQL Server for data storage.

Supported Operating Systems

Table 3-1 lists operating systems that support Calendar Server.

Table 3-1 Supported Operating Systems

Operating System	CPU	Required Patches
Oracle Solaris 10 and 11	SPARC, x64	See the Oracle Solaris documentation for patch information.
Oracle Linux 6 and Red Hat Enterprise Linux 6 64-bit	x64	See the Oracle Linux and Red Hat Enterprise Linux documentation for patch information.

Required Software

Table 3-2 lists the database software choices for Calendar Server.

Table 3-2 Database Requirements

Product Version

Product	Version
Oracle Database	11g Release 2, 12c To upgrade to Oracle Database 12c from Oracle Database 11g, see Oracle Database Upgrade Guide at: `https://docs.oracle.com/database/121/UPGRD/toc.htm`
MySQL Server	5.5.32, 5.6 To upgrade to MySQL Server 5.6 from MySQL Server 5.5, see "Upgrading from MySQL 5.5 to 5.6" at: `http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html`

Oracle Database

11g Release 2, 12c

To upgrade to Oracle Database 12c from Oracle Database 11g, see Oracle Database Upgrade Guide at:

https://docs.oracle.com/database/121/UPGRD/toc.htm

MySQL Server

5.5.32, 5.6

To upgrade to MySQL Server 5.6 from MySQL Server 5.5, see "Upgrading from MySQL 5.5 to 5.6" at:

http://dev.mysql.com/doc/refman/5.6/en/upgrading-from-previous-series.html

Note:

You cannot mix database types in a deployment.

Table 3-3 lists other software required for installing and running Calendar Server.

Table 3-3 Software Requirements

Product Version Notes

Product	Version	Notes
Oracle Directory Server Enterprise Edition	6.x, 7, 11gR1 Patch Set 2 (11.1.1.7.0)	If doing a fresh installation, use 11gR1.
Oracle GlassFish Server	3.1.2.x	Required as the web container. Download the patch from My Oracle Support at: `https://support.oracle.com`
Java	7	Be sure to install the latest security update.

Oracle Directory Server Enterprise Edition

6.x, 7, 11gR1 Patch Set 2 (11.1.1.7.0)

If doing a fresh installation, use 11gR1.

Oracle GlassFish Server

3.1.2.x

Required as the web container. Download the patch from My Oracle Support at:

https://support.oracle.com

Java

Be sure to install the latest security update.

Client Requirements

Calendar Server supports any standard CalDAV client. Table 3-4 shows which clients were tested with Calendar Server.

Table 3-4 Calendar Server Clients

Client	Minimum Version	Notes
Convergence	2 (Patch 6), testing done with Convergence 3	None.
Connector for Microsoft Outlook	8	None.
Apple iCal	6	iCal 3 comes bundled with Mac OS 10.5, testing done with Apple iCal 6.0. (As newer versions become available, they are tested. It is recommended to use these new versions.)
Apple iPhone OS calendar cleitn	6.0.1	Support for scheduling in iOS 4.x on iPhone, iPod touch, and iPad (iOS 7 is the latest version).
Lightning	1.9.1	Lightning 1.9.1 is the latest version.
eM	Not applicable	Desktop client for Window (.NET) that supports CalDAV access. This client has not officially been tested by Oracle. In general, any CalDAV compliant client should work.
Enterprise Tasks	Not applicable	eTask is a business applications for the iPhone and iPod touch that uses the CalDAV protocol to view, edit, create, delete, and sync your tasks on the CalDAV server.
Android CalDAV-Sync	Not applicable	CalDAV-Sync is a CalDav client for Android to synchronize events. Testing done with CalDAV sync client version 0.3.3 and Task Client version 1.0.3.
NotifyLink	4.7	Depending on the device, might require version 4.7 or 4.8.

Hardware Requirements

The number and configuration of the systems that you employ for your Calendar Server installation depends on the scale and the kind of deployment you have planned.

Note:

The sizing estimates in this section assume proper application configuration and tuning, in a manner consistent with leading practices of Oracle Communications consulting and performance engineering. This information is provided for informational purposes only and is not intended to be, nor shall it be construed as a commitment to deliver Oracle programs or services. This document shall not form the basis for any type of binding representation by Oracle and shall not be construed as containing express or implied warranties of any kind. You understand that information contained in this document will not be a part of any agreement for Oracle programs and services. Business parameters and operating environments vary substantially from customer to customer and as such not all factors, which may impact sizing, have been accounted for in this documentation.

Table 3-5 provides the minimum hardware requirements for Calendar Server installed on a single managed server in a GlassFish Server domain.

Table 3-5 Minimum Hardware Requirements

Component	Requirement
Disk Space	Approximately 20 MB required for Calendar Server software.
RAM	8 GB

Information Requirements

During the Calendar Server installation, you must enter values for configuration items such as host names and port numbers. This section describes the information that you must provide during the installation and initial configuration process.

Calendar Server Information

Table 3-6 lists the Calendar Server information that you provide during initial configuration.

Table 3-6 Calendar Server Information

Information Type	Default Value	Comments
Directory to store configuration and data files	/var/opt/sun/comms/davserver	No comments.
Runtime user ID under which Calendar Server runs	root	This user must match the user that runs the Glassfish Server instance. It is also the owner of the application data and configuration directory.
Runtime group to contain Calendar Server runtime user ID	bin	This group must match the group of the user that runs the Glassfish Server instance. It is also the owner of the application data and configuration directory.
Fully qualified host name of this system	FQDN of host	No comments.

Database Information

Table 3-7 lists the database information that you provide during initial configuration.

Table 3-7 Back-End Database Information

Information Type	Default Value
The type of Calendar Server database. Possible values are either mysql or oracle.	mysql

MySQL Server Database Information

Table 3-8 lists the database information that you provide during initial configuration if you choose MySQL Server as the database.

Table 3-8 MySQL Server Database Information

Information Type	Default Value
MySQL database server host name	FQDN of host
MySQL database server port number	3306
Calendar Server database user	caldav
Calendar Server database user password	No default value.
Calendar Server database name	caldav
iSchedule database name	ischedule

Oracle Database Information

Table 3-9 lists the database information that you provide during initial configuration if you choose Oracle as the database.

Table 3-9 Oracle Database Information

Information Type	Default Value
Oracle database server host name	FQDN of host
Oracle database server port number	1521
Oracle service name	orcl.domain_name_of_host
Calendar Server database user	caldav
iSchedule database name	ischedule
Calendar Server database user password	No default value.

Document Store Information

Table 3-10 lists the document store information that you provide during initial configuration.

Table 3-10 Document Store Information

Information Type	Default Value
The back-end document store type. Possible values are local, dbdocstore, or remote. A value of dbdocstore is possible only for Oracle Database.	local
The name of the Calendar Server back end with which the document store is associated.	defaultbackend
The path to the Calendar Server document store.	/var/opt/sun/comms/davserver/db
(Remote document store only) The name of the host where the remote Calendar Server document store is located.	No default value.
(Remote document store only) The port number for the remote Calendar Server document store.	8008

iSchedule Database Information

Table 3-11 lists the iSchedule database information that you provide during initial configuration.

Table 3-11 iSchedule Database Information

Information Type	Default Value
The iSchedule database type. Possible values are local, dbdocstore, or remote. A value of dbdocstore is possible only for Oracle Database.	local
The name of the iSchedule database.	ischedulebackend
The path to the iSchedule database.	/var/opt/sun/comms/davserver/db/ischedulebackend
(Remote iSchedule database only) The name of the host where the remote iSchedule database is located.	No default value.
(Remote iSchedule database only) The port number for the remote iSchedule database host.	8008

GlassFish Server Information

Table 3-12 lists the GlassFish Server information that you provide during initial configuration.

Table 3-12 GlassFish Server Information

Information Type	Default Value
GlassFish Server installation directory	/opt/glassfish3/glassfish
GlassFish Server domain directory	/opt/glassfish3/glassfish/domains/domain1
GlassFish Server document root directory	/opt/glassfish3/glassfish/domains/domain1/docroot
GlassFish Server target instance name	server
GlassFish Server virtual server	server
GlassFish Server administration server host	FQDN of host
GlassFish Server administration server port	4848
Is administration server port secure	true (yes)
GlassFish Server administrator user	admin
GlassFish Server administrator user password	No default value.
URI path of the deployed server	https://FQDN of host:443/ (root directory) For information about using a .well-known URI, such that access to / (root) or /.well-known/caldav/ is redirected to the /dav/principals/ URI, see the topic on setting up CalDAV autodiscovery in Calendar Server System Administrator's Guide.

LDAP Information

Table 3-13 lists the LDAP information that you provide during initial configuration.

Table 3-13 LDAP Information

Information Type	Default Value
User/Group LDAP URL	ldaps://FQDN of host:636
User/Group directory manager distinguished name (DN)	cn=Directory Manager
Directory manager password	No default value.
LDAP unique ID attribute	davuniqueid
User/Group default domain	The name of the domain in the directory user/group tree where user and group objects reside.
Default organization distinguished name (DN)	This value is generated based on the previous value and the user/group suffix of the Directory Server.
Calendar Server administrator user	calmaster
Calendar Server administrator user password	No default value.

Notification Information

Table 3-14 lists the email notification information that you provide during initial configuration.

Table 3-14 Notification Information

Information Type	Default Value
Notification mail server host name	FQDN of host
Notification mail server port number	25