2 Installing Oracle SOA Suite and Oracle Business Process Management Suite

This chapter describes how to install the Oracle SOA Suite run-time components.

See Section 2.4, "Installing Oracle SOA Suite Design-Time Components" for information about installing Oracle JDeveloper and installing the Oracle SOA Suite extensions in Oracle JDeveloper. These extensions provide the functionality and online documentation for designing SOA composite applications.

The following topics are covered in this chapter:

2.1 Preparing to Install

Before continuing, make sure you have completed tasks 1 - 3 in Table 1-1 in Section 1.2, "Oracle SOA Suite Installation Roadmap".

2.1.1 Enabling Unicode Support

Your operating system configuration can influence the behavior of characters supported by Oracle SOA Suite.

On a UNIX operating system, Oracle highly recommends that you enable Unicode support by setting the LANG and LC_ALL environment variables to a locale with the UTF-8 character set. This enables the operating system to process any character in Unicode. SOA technologies are based on Unicode.

If the operating system is configured to use a non-UTF-8 encoding, SOA components may function in an unexpected way. For example, a non-ASCII file name can make the file inaccessible and cause an error. Oracle does not support problems caused by operating system constraints.

In a design-time environment, if you are using Oracle JDeveloper, select Tools -> Preferences -> Environment -> Encoding -> UTF-8 to enable Unicode support.

2.1.2 Synchronizing Clocks When Working with Clusters

Oracle SOA uses Quartz, which is an open source job-scheduling framework. When you are setting up clusters on multiple systems, Quartz requires that the clocks on all the systems be synced up. For more information, refer to the following URL:


Also refer to the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite and Oracle Fusion Middleware High Availability Guide for more information about clustering in advanced topologies.

2.2 Installation Instructions

Oracle BAM and Oracle SOA Suite are both installed onto your system by default. After the products are installed, you must run the Configuration Wizard to configure the product(s) of your choice.

This section contains the following topics:

2.2.1 Starting the Installer

The installer requires the location of a Java Runtime Environment (JRE) on your system.


When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MW_HOME/jdk160_18 (on UNIX operating systems) or MW_HOME\jdk160_18 (on Windows operating systems), where MW_HOME is the Middleware Home directory.

On 64-bit platforms, the JRE location is the JAVA_HOME you used to install Oracle WebLogic Server.

For more information, refer to Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

On UNIX operating systems:

> ./runInstaller -jreLoc JRE_LOCATION


Starting the installer as root user is not supported.

On Windows operating systems:

D:\ setup.exe -jreLoc JRE_LOCATION

You must specify the absolute path to your JRE_LOCATION; relative paths are not supported.


You must also specify the JRE_LOCATION in the same manner if you are installing Oracle SOA Suite on a 64-bit UNIX or Windows operating system with a 32-bit JDK.

If no JRE location is specified, you will be prompted to provide the location of your JRE before the installer is started:

[> ./runInstaller 
Starting Oracle Universal Installer...
Checking if CPU speed is above 300 MHz.    Actual 2999 MHz    Passed
Checking Temp space: must be greater than 150 MB.   Actual 66070 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 4047 MB    Passed
Checking monitor: must be configured to display at least 256 colors.    Actual 256    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2010-02-23_10-57-58AM. Please wait ...
Please specify JRE/JDK location ( Ex. /home/jre ), <location>/bin/java should exist :

Specify the absolute path to the JRE on your system before you continue.

2.2.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section D.2.1, "Installation Log Files" for more information about the log files and their contents.

2.2.3 Inventory Screens (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 2-1 to configure the inventory directory information. For more help, click on the screen name in the table below, or click the Help button in the GUI.

Table 2-1 Inventory Directory and Group Screens

No. Screen Description and Action Required


Specify Inventory Directory Screen (UNIX Only)

Specify the Oracle inventory directory and group permissions for that directory. The group must have write permissions to the Oracle inventory directory.

Click OK to continue.


Inventory Location Confirmation Screen (UNIX Only)

Run the createCentralInventory.sh script as root.

Click OK to continue.

2.2.4 Installation Screens and Instructions

Follow the instructions in Table 2-2 to install the Oracle SOA Suite components.

If you need additional help with any of the installation screens, refer to Appendix A, "Oracle SOA Suite Installation Screens" or click Help to access the online help.

Table 2-2 Installation Flow for Oracle SOA Suite

No. Screen Description and Action Required


Welcome Screen

Click Next to continue.


Prerequisite Checks Screen

Click Next to continue.


Specify Installation Location Screen

Specify Oracle Middleware home and Oracle home locations.

The Oracle Common home (oracle_common) directory will automatically be created inside the Middleware home; do not use oracle_common as the name of your Oracle home directory.

Click Next to continue.


Installation Summary Screen

Verify the installation about to be performed.

Click Install to continue.


Installation Progress Screen

This screen shows the progress of the installation.

When the progress shows 100% complete, click Next to continue.


Installation Complete Screen

Click Finish to dismiss the screen.

2.3 Patching your Software and Installing Oracle Business Process Management Suite

The next step is to patch your Oracle SOA Suite software to the latest version by running the Patch Installer for Oracle SOA Suite. The Patch Installer for Oracle SOA Suite will also install the Oracle Business Process Management Suite software onto your system.

For instructions, see "Applying the Latest Oracle Fusion Middleware Patch Set with the Patch Set Installers" in Oracle Fusion Middleware Patching Guide.

After this is complete, you are ready to run the Configuration Wizard to configure your domain for Oracle SOA Suite, including Oracle Business Process Management Suite. Go to Chapter 3, "Configuring Oracle SOA Suite and Oracle Business Process Management Suite" for instructions.

2.4 Installing Oracle SOA Suite Design-Time Components

Oracle SOA Suite is not automatically installed with Oracle JDeveloper. Before you can create a SOA application and project, you must install the SOA Suite extension for JDeveloper.

For instructions on installing SOA Suite extension for JDeveloper, see Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.