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 the application server's 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 11

SPARC, x64

See the Oracle Solaris documentation for patch information.

Oracle Linux 6, Oracle Linux 7

x64

See the Oracle 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

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

Note: Calendar Server Patch 8.0.0.4.0 is certified with Oracle Database 19c.

MySQL Server

5.5.40, 5.6.22, and 5.7.26.

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

Oracle Directory Server Enterprise Edition

Oracle Directory Server Enterprise Edition 6.x, 7, 11.x

For a fresh installation, use the latest version of Directory Server 11gR1.

Application Server

GlassFish Server 3.1.2.x

WebLogic Server 12.2.1.3.0 and 12.2.1.4.0.

Required as a web container:

For GlassFish Server, download the patch from My Oracle Support at: https://support.oracle.com

For WebLogic Server, download the generic installer from http://edelivery.oracle.com

For WebLogic Server 12.2.1.4.0, the installer is available as Oracle Fusion Middleware 12c (12.2.1.4.0) WebLogic Server and Coherence and contains fmw_12.2.1.4.0_wls.jar and fmw_12214_readme.html.

For example, for Linux Platform, you should download the V983364-01.zip package.

Supported Application Server: Oracle Communications Calendar Server 8.0.0.3.0 and previous releases were deployed on GlassFish Server, which is no longer supported by Oracle. For that reason, Calendar Server 8.0.0.4.0 and beyond are only supported on Oracle WebLogic Server. Oracle strongly recommends that you upgrade your Calendar Server environments to release 8.0.0.4.0 or higher and migrate to WebLogic Server to receive full Oracle support.

Java

For GlassFish Server, use Java 7

For WebLogic Server, use Java 8

The Java version is according to the application server that you have selected to deploy Calendar Server.

Note: You must download the latest security patch updates available for the respective Java version.

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

Calendar Server Patch 8.0.0.4.0 is certified with Convergence 3.0.2.1.0.

Connector for Microsoft Outlook

8

NA

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 client

6.0.1

Support for scheduling in iOS 4.x on iPhone, iPod touch, and iPad (iOS 8.3 is the latest version).

Lightning

1.9.1

Lightning 4.0.0.1 is the latest version.

Other standard CalDAV clients that should work include eM, Enterprise Tasks, Android CalDAV-Sync, Android CalendarSync, DAVDroid Bitfire, and Notifylink.

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 deployed on a single managed server in a WebLogic or GlassFish 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 Notes

Directory to store configuration and data files

/var/opt/sun/comms/davserver

NA

Runtime user ID under which Calendar Server runs

root

If you select GlassFish Server to deploy Calendar Server:

  • The root user must match the user that runs the GlassFish Server instance. This user is also the owner of the application data and configuration directory.

If you select WebLogic Server to deploy Calendar Server:

  • The Runtime user ID must have permission and write access to the Oracle WebLogic Server instance and configuration directory. This ID is also the owner of the application data and configuration directory.

    Refer to the "Installing and Configuring WebLogic Server" section for setting up WebLogic Server for Calendar Server.

    Note: Only non-root users can install WebLogic Server. Therefore, a non-root system user, for example, uadmin, should be created and used for installing, owning, or running the WebLogic Server instances. Ensure that the non-root user system account, which runs the WebLogic Server and the runtime user ID system account belong to the same system user group.

Runtime group to contain Calendar Server runtime user ID

bin

If you select GlassFish Server to deploy Calendar Server:

  • This group must match the group of the user that runs the GlassFish Server instance. This group is also the owner of the application data and configuration directory.

If you select WebLogic Server to deploy Calendar Server:

  • This group must match the group of the user that runs the WebLogic Server instance. This group is also the owner of the application data and configuration directory.

    For example, if the WebLogic Server instance is owned by a system user/group as uadmin/staff, the same group staff must be used here for the Runtime group.

    Note: Runtime user ID also belongs to the same system group.

Fully qualified host name of this system

FQDN of host

NA

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 for Calendar Database

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

Table 3-10 Document Store Information for Calendar Database

Information Type Default Value

The 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

Document Store Information for iSchedule Database

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

Table 3-11 Document Store Information for iSchedule Database

Information Type Default Value

The 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 iSchedule database.

ischedulebackend

The path to the iSchedule database.

/var/opt/sun/comms/davserver/db/ischedulebackend

(Remote document store only) The name of the host where the remote document store is located.

No default value.

(Remote document store only) The port number for the remote document store 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 Enabling CalDAV and CardDAV Autodiscovery in Calendar Server System Administrator's Guide.

WebLogic Server Information

Table 3-13 lists the Oracle WebLogic Server information that you provide during initial configuration.

Table 3-13 WebLogic Server Information

Information Type Description

WebLogic Server installation directory

Directory in which WebLogic Server is installed. For example, WLS_HOME/Oracle_Home

WebLogic Server domain directory

The directory in which domain directories are created.

For example: WLS_HOME/Oracle_Home/user_projects/domains/domain1

WebLogic Server document root directory

The WebLogic Server document root directory.

For example: WLS_HOME/Oracle_Home/user_projects/domains/domain1.

WebLogic Server target instance name

The name of the WebLogic Server's Managed Server target name.

For example: server1

WebLogic Server virtual server

The name of the WebLogic Server's Managed Server target name.

For example: server1

WebLogic Server administration server host

FQDN of host

Is administration server port secure

Whether Oracle WebLogic Server administration server port is running over SSL.

Default: Enabled

WebLogic Server administration server port

7001

This is the port with which you log in to WebLogic Administration Server.

Note: If you set Is administration server port secure to true, this must be the SSL port of WebLogic Administration Server.

WebLogic Server administrator user

The admin user name to log in to WebLogic Server Administration Server.

WebLogic Server administrator user password

The password to log in to WebLogic Server Administration Server.

URI path of the deployed server

https://FQDN of host:7003/davserver

Pattern should be https://FQDN of host:ManagedServer_Port context-root

ManagedServer_Port: WebLogic Server domain must be set up with at least one ManagedServer which hosts Calendar Server. You must provide the port of that Managed Server here.

Note: If you select Secure mode, ensure to enter https and the SSL port of that Managed Server instance.

context-root: The default /davserver is an example of the context to deploy Calendar Server.

For more information, refer to the Enabling CalDAV and CardDAV Autodiscovery section in Calendar Server System Administrator's Guide.

LDAP Information

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

Table 3-14 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-15 lists the email notification information that you provide during initial configuration.

Table 3-15 Notification Information

Information Type Default Value

Notification mail server host name

FQDN of host

Notification mail server port number

25