Installation Guide

Task Overview

This chapter provides a high level description of the process of installing and configuring Oracle Communications Services Gatekeeper. Subsequent chapters describe the specific steps required to use each type of installation and configuration tools in detail.

Setting up Oracle Communications Services Gatekeeper is a four step process. You must:

Check Network/Hardware Setup

Before you can install Oracle Communications Services Gatekeeper, you must gather a certain amount of information about your system. You need to know:

The network names or IP addresses of the machines on which you are going to install
The directory on each machine which will serve as your BEA Home directory. This directory serves as a repository for common files that are used by all Oracle Communications products installed on the same machine.

The files in the BEA Home directory are essential to ensuring that Oracle Communications software operates correctly on your system. They:

Facilitate checking of cross-product dependencies during installation
Facilitate Service Pack installation

The directory on each machine which will serve as your Product Installation Directory. Usually this is a subdirectory of the BEA Home directory. The product installation directory contains all the software components that will be used in configuring the Oracle Communications Services Gatekeeper domains. The default directory is $BEAhome\ocsg_4.1.
If you are going to install the Oracle Communications Services Gatekeeper Platform Development Studio, the machine’s Eclipse Plugin directory.
The password you are going to use for the Administration User. The default password is “weblogic”, which should be used during the initial setup and configuration period.

Install Software

Installing Oracle Communications Services Gatekeeper generally requires that three separate components be copied to your hardware:

The platform container, Oracle WebLogic Server
The Oracle Communications Services Gatekeeper software, including container services and communication services applications
The Oracle Communications Services Gatekeeper Platform Development Studio software

Each of these components is copied to its appropriate places when you run the Oracle Communications Services Gatekeeper installer. There are three main installer modes available:

Graphical-mode (GUI-based)

Note:

If you want to run graphical-mode installation, the console attached to the machine on which you are installing the software must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX/Linux systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.

Console (interactive text-based)
Silent mode (uses an XML file instead of user-entered responses)

The specifics of each of these installers are covered in Installing Oracle Communications Services Gatekeeper. You need to do this for each machine in your installation.

Note:

It is recommended that you install Oracle Communications Services Gatekeeper on the local disk of each server in your setup, as in Figure 5-1.

Figure 5-1 The Recommended Install Pattern

If all of your servers can access a shared file system, it is possible to install Oracle Communications Services Gatekeeper only there (see Figure 5-2), but this is not recommended, for performance reasons.

Figure 5-2 Possible, but not recommended

Configure the WebLogic Server Domain for Oracle Communications Services Gatekeeper

Configuring the domain for WebLogic Server for use in Oracle Communications Services Gatekeeper installations can be accomplished using one of two available tools:

The Configuration Wizard, using either the GUI-based version or the interactive console version.

Note:

If you want to run graphical-mode configuration, the console attached to the machine on which you are configuring the domain must support a Java-based GUI. All consoles for Windows systems support Java-based GUIs, but not all consoles for UNIX/Linux systems do. If you attempt to start the installation program in graphical mode on a system that cannot support a graphical display, the installation program automatically starts console-mode installation.

The command-line scripting tool (WebLogic Scripting Tool) and provided scripts.

Note:

The WebLogic Scripting Tool (WLST) is a command-line scripting interface that system administrators and operators use to monitor and manage WebLogic Server instances and domains. The WLST scripting environment is based on the Java scripting interpreter, Jython. For more information on WLST, see Oracle WebLogic Server WebLogic Scripting Tool at http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/.

Oracle Communications Services Gatekeeper ships with five default configuration templates:

Basic HA configuration
Domain with Access and Network Clusters
Domain with Access and Network Clusters with Oracle RAC Configuration
Basic Oracle Communications Services Gatekeeper Domain
OCSG OSB Integration Configuration

These templates contain the basic information for setting up various common installation selections. However in all cases, some aspects of the domain may need to be adjusted during the domain configuring process. The entire process is covered in Configuring the Domain for Oracle Communications Services Gatekeeper.

Complete Post-Installation

Once installation is complete and your domain has been set up, you must:

Complete a few post-installation tasks
Configure the installed Oracle Communications Services Gatekeeper itself

These are covered in Completing Post-Installation.

For Further Information

To learn more about installing WebLogic Server products in general, and about the installer program in particular in regard to WebLogic Server, see Oracle WebLogic Server Installation Guide at http://download.oracle.com/docs/cd/E12840_01/common/docs103/install/index.html.