|Oracle® Communications Service Broker Installation Guide
Part Number E15181-01
This chapter gives an overview of the installation process and things to consider when installing Oracle Communications Service Broker:
An Oracle home is a directory into which Oracle software is installed.
Oracle home is defined in an environment variable. The Oracle Universal Installer supports the installation of several active Oracle home directories on the same host.
Oracle home has a name and a path associated with the name, which you specify during installation:
The name identifies the program group associated with a particular home and the Oracle services installed on this home. The Oracle home name must be between 1 to 127 characters long, and can include only alphanumeric characters and underscores.
The path is the full path to an Oracle home directory where products are installed.
In the Service Broker documentation, the Oracle home directory is referred to as Oracle_home.
Oracle recommends that you designate an Oracle home location that is an empty or non-existing directory.
An Oracle home inventory, or local inventory, contains only information relevant to a particular Oracle home. An Oracle home inventory is present in an
inventory directory inside each Oracle_home directory.
The Oracle Central Inventory includes installation logs corresponding to all installations performed on a particular host. The installation logs for an installation are identified by the timestamp in the log file names. The location of the Oracle Central Inventory is defined in the following files:
You can install Service Broker by using a graphical user interface (GUI) or by using a command-shell script with response files, known as installing in silent mode.
You can use the GUI to walk through the installation by providing information in the dialog boxes when prompted. This method is useful when installing a small number of Processing and Signaling Servers in different setups on a small number of hosts.
If your system does not have a GUI, you must use the installer in silent mode. This method is most useful when installing multiple Processing or Signaling Servers on multiple hosts. By using the response files, you can also automate the installation of a server or an Administration Console.
A JDK must be installed on every host that runs a Processing or Signaling Server, a stand-alone Administration Console, or the Web Administration Console server.
The installation package comes with two JDKs:
You can also choose to reuse a supported JDK that is already installed on your server.
See "Software Requirements" for a list of supported JDKs, including details on versions.
All configuration data and OSGi bundles are located in a domain configuration directory for each Processing and Signaling Domain. Each domain configuration directory needs to be accessed by all respective Processing or Signaling Servers, all standalone Administration Consoles, and the Web Administration Console servers.
The Administration Console requires read and write access to the domain configurations. The Processing and Signaling Servers require only read access to the domain configurations.
The Administration Console and the Processing and Signaling Servers can access the domain configuration directory by way of a shared file system or a Web server:
If you use the shared file-system, set up all servers so that they can access the domain configuration directory.
If you use a Web server, set up the Web server with read access to the domain configuration directory and map the directory to a URL.
To set up either of these methods, follow the instructions in the documentation for your operating system or your Web server.
The Administration Console is installed using the Oracle Universal Installer for Service Broker.
The installer installs all components necessary to run the stand-alone Administration Console and the Web Administration Console server.
The Administration Console can be installed and run from any machine that has access to the Processing Servers and Signaling Servers and to the domain configuration directories.
You can have as many Administration Consoles installed as you wish. Run the installer on each server where you want to run the stand-alone Administration Console or the Web Administration Console server. See "Installing Oracle Communications Service Broker" for instructions.
A production system should always be deployed as a set of at least two servers per domain. Each server should be installed on a dedicated physical server.
See "System Requirements" for a information about supported platforms for production-level deployments.
A Processing Server or Signaling Server is installed using the Oracle Universal Installer for Service Broker. Run the installer for each server you need to install. See "Installing Oracle Communications Service Broker" for instruction.
You can use a test and evaluation system to familiarize yourself with Service Broker, to test integration, and for training purposes. A test and evaluation system does not have the same requirements for redundancy and high-availability as a production-level system.
Never use a test and evaluation system in production.
See "System Requirements" for information about supported platforms for test and evaluation systems.
A test and evaluation system can be:
A single-instance system, where both the Processing and Signaling Domains are set up on a single server.
A multi-server system, where a set of Processing or Signaling Servers is installed on the same physical machine.
For this type of system, you run the installer to install a single server. You then add additional servers by copying the server directory that was created by the installer.
The Administration Console may be installed on the same physical machine as the servers. Use the same Oracle home for both the servers and the Administration Console if you install both on the same machine.
See "Installing Oracle Communications Service Broker" for instructions on installing an Administration Console and a server.