This chapter provides an overview of the Oracle Communications Calendar Server installation process.
During the installation process, you install and configure the following components:
Java
Application server
Either MySQL Server or Oracle Database
Calendar Server
Calendar Server depends on Oracle Directory Server Enterprise Edition for LDAP services. If your site does not currently have Directory Server deployed and you need to install it, see the Oracle Directory Server Enterprise Edition documentation for instructions, at:
http://docs.oracle.com/cd/E29127_01/index.htm
For Calendar Server to use notifications, you must also have an email server installed, such as Oracle Communications Messaging Server.
The installation procedure follows these steps:
Plan your installation. When planning your installation, do the following:
Determine the scale of your implementation, for example, a small development system, or a large production system.
Determine how many physical machines you need, and which software components to install on each machine.
Plan the system topology, for example, how the system components connect to each other over the network.
Review system requirements. System requirements include:
Hardware requirements, such as disk space.
System software requirements, such as operating system (OS) versions and OS patch requirements.
Information requirements, such as IP addresses and host names.
Install and configure software upon which Calendar Server is dependent, including:
Java
Application server
Either MySQL Server or Oracle Database
Prepare the Directory Server schema by installing and running the most current comm_dssetup script from the Calendar Server media pack.
Install and configure Calendar Server.
(Optional) Configure additional Calendar Server front ends and back ends for a multiple host deployment.
Configure the document stores.
Perform post-installation configuration tasks.
Verify the installation.
After Calendar Server is installed, you might perform additional security-related tasks. For more information, see Calendar Server Security Guide.
You install Calendar Server in either interactive or silent mode. When you run the installer in silent mode, you are running a non-interactive session. The installation inputs are taken from the following sources:
A silent installation file
Command-line arguments
Default settings
You can use silent mode to install multiple instances of the same software component and configuration without having to manually run an interactive installation for each instance.
Only qualified personnel should install the product. You must be familiar with the UNIX operating system and the application server. You should be experienced with installing Java-related packages. Oracle recommends that an experienced database administrator install and configure database software.
Follow these guidelines:
As you install each component, for example, the Oracle database and GlassFish Server, verify that the component installed successfully before continuing the installation process.
Pay close attention to the system requirements. Before you begin installing the software, make sure your system has the required base software. In addition, ensure that you know all of the required configuration values, such as host names and port numbers.
As you create new configuration values, write them down. In some cases, you might need to re-enter configuration values later in the procedure.
Table 1-1 lists the placeholders that are used in this guide:
Table 1-1 Calendar Server Directory Placeholders
Placeholder | Directory |
---|---|
CalendarServer_home |
Specifies the installation location for the Calendar Server software. The default is /opt/sun/comms/davserver. |
InstallRoot |
Specifies the installation location for the Unified Communications Suite software. The default is /opt/sun/comms. |
GlassFish_home |
Specifies the installation location for the Oracle GlassFish Server software. The default is /opt/glassfish3/glassfish. |
WebLogic_home |
The directory in which Oracle WebLogic Server software is installed. |
GlassFish_Domain |
Oracle GlassFish Server domain in which Calendar Server is deployed. For example: GlassFish_home/domains/domain1 |
Weblogic_Domain |
Oracle WebLogic Server domain in which Calendar Server is deployed. For example, WebLogic_home/user_projects/domains/base_domain Note: In case of WebLogic Server, it must be configured with at least one Managed Server instance and the Managed Server instance must host Calendar Server. |
AppServer_Domain |
The domain of the application server in which Calendar Server is deployed. |