1 Instant Messaging Server Installation Overview

This chapter provides an overview of the Oracle Communications Instant Messaging Server installation process.

Overview of Instant Messaging Server Installed Components

During the installation process, you install and configure the following components:

• Java

• Instant Messaging Server

Instant Messaging Server depends on Oracle Communications 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 Instant Messaging Server to use notifications offline, you must have an email server installed, such as Oracle Communications Messaging Server. For Instant Messaging Server to use the calendar agent, you must have Oracle Communications Calendar Server installed. See the Messaging Server and Calendar Server documentation for information on installing those products.

Overview of the Instant Messaging Server Installation Procedure

The installation procedure follows these steps:

1. 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.

2. 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.

3. Install and configure software upon which Instant Messaging Server is dependent, including Java.

4. Prepare the Directory Server schema by installing and running the most current comm_dssetup script from the Communications Suite distribution.

5. Install and configure Instant Messaging Server.

6. Perform post-installation configuration tasks.

7. Verify the installation.

After Instant Messaging Server is installed, you might perform additional security-related tasks, such as configuring Secure Sockets Layer (SSL) communications between Instant Messaging Server front ends and back ends. For more information, see Instant Messaging Server Security Guide.

Instant Messaging Server Installation Options

You install Instant Messaging Server by running the Unified Communications Suite installer in either interactive or silent mode. When you run the Communications Suite 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.

For more information, see the topic on installing Communications Suite in silent mode in Unified Communications Suite Installation Guide at:

https://wikis.oracle.com/display/CommSuite/Installing+Communications+Suite+7.0.6+in+Silent+Mode

Ensuring a Successful Instant Messaging Server Installation

Only qualified personnel should install the product. You must be familiar with the UNIX operating system. You should be experienced with installing Java-related packages.

Follow these guidelines:

• As you install each component, for example, 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.

Directory Placeholders Used in This Guide

Table 1-1 lists the placeholders that are used in this guide:

Table 1-1 Instant Messaging Server Directory Placeholders

Placeholder	Directory
InstantMessaging_home	Specifies the installation location for the Instant Messaging Server software. The default for both Solaris and Linux is /opt/sun/comms/im.
InstantMessaging_cfg	Specifies the installation location for the configuration directory. The default for Solaris is /etc/opt/sun/comms/im/default/config. The default for Linux is /etc/opt/sun/im/default/config.
InstantMessaging_database	Specifies the location for the database directory, if you are using a file-based property store. The default for both Solaris and Linux is /var/opt/sun/im/default/db.
InstantMessaging_runtime	Specifies the location for the configurable directory for the files generated by the server at runtime. The default for both Solaris and Linux is /var/opt/sun/im/default.