|Oracle® Fusion Middleware Installation Guide for Oracle SOA Suite
11g Release 1 (11.1.1)
Part Number E13925-01
See Section 2.7, "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:
Make sure you have read the information in this section before you install Oracle Fusion Middleware SOA Suite:
Before performing any installation you should read the system requirements and certification documentation to ensure that your environment meets the minimum installation requirements for the products you are installing.
The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. This document is available on Oracle Technology Network (OTN):
Installation of Oracle SOA Suite requires the availability of an Oracle database. This database must be up and running, and does not have to be on the same system where you are installing the products.
For the latest information about supported databases, visit the following URL:
If you are using an SSL-enabled database, you must make some manual changes in order for your installation to work properly. See Section E.5, "Using Data Sources with an SSL-Enabled Database" for more information.
Oracle SOA Suite and Oracle BAM require that certain schemas exist in the database prior to installation. You must run Repository Creation Utility (RCU) to create the schemas in the database. Follow these instructions to do so:
After downloading the
.zip file, extract the contents to a directory of your choice, and run RCU from the
/bin (on UNIX) or
\bin (on Windows) directory with the commands shown above, where
RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD-ROM.
Note:On Windows systems, make sure that you do not extract the RCU
.zipfile to a directory name containing spaces.
Create Repository Screen
Database Connection Details Screen
Host Name: Specify the name of the machine on which your database resides in the format
.com. For Oracle RAC databases, specify the Virtual IP name or one of the node names as the host name.
Port: Specify the database listener port number. The default port number for Oracle databases is 1521.
Database Name: Specify the service name for the database. Typically, the service name is the same as the global database name.
If you are unsure what the service name for your database is, you can obtain it from the
SERVICE_NAMES parameter in the database's initialization parameter file. If the initialization parameter file does not contain the
SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the
For Oracle RAC databases, specify the service name of one of the nodes in this field. For example:
Username: Specify the name of a user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is
Password: Specify the password for your database user.
Role: Select the database user's role from the drop-down list. The
SYS user requires the SYSDBA role.
Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.
Select Components Screen
Table 2-1 lists the required schemas for Oracle SOA Suite products:
Table 2-1 Required Schemas for Oracle SOA Suite Products
Oracle SOA Suite
Select the components whose schemas you want to install.
Note:You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your products. You will need to provide the schema name in the format
schemaname. For example, if you used the default prefix
DEV, you will supply the following schema name for the MDS schema:
Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.
Schema Passwords Screen
Select Use same password for all schemas if you want to use a single password for all schemas and their auxiliary schemas. In the Password field, enter your password. Enter your password again in the Confirm Password field.
Select Use main schema passwords for auxiliary schemas if you want to specify different passwords for the main schemas, but still have the same password used for their respective auxiliary schemas. If you select this option, only the main schemas will be visible in the table. For each schema, you must enter each schema's password in the Password column in the table, and enter the same password in the Confirm Password column.
Select Specify different passwords for all schemas if you want to specify unique passwords for the main schemas and auxiliary schemas. If you select this option, all main schemas and auxiliary schemas will be visible in the table. For each schema and auxiliary schema, you must enter the password in the Password column in the table, and enter the same password in the Confirm Password column.
Note:You must remember or make a note of the password(s) from this screen; you will need them later when you are configuring your products.
Map Tablespaces Screen
Click Create. A "CREATE" screen will appear. After the schemas are created with no errors, click OK to dismiss the screen.
Completion Summary Screen
For detailed information about using RCU, refer to Oracle Repository Creation Utility User's Guide.
Insert the Oracle WebLogic Server CD-ROM or download the installer from the following URL:
You are looking for the following executable files:
wls1031_linux32.bin (for 32-bit Linux systems)
wls1031_win32.exe (for 32-bit Windows systems)
wls1031_generic.jar (for all 64-bit platforms)
The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:
Examples on a 32-bit system:
Examples on a 64-bit system:
JAVA_HOME/bin/java -jar wls1031_generic.jar
JAVA_HOME/bin/java -d64 -jar wls1031_generic.jar
JAVA_HOME\bin\java -jar wls1031_generic.jar
JAVA_HOME\bin\java -d64 -jar wls1031_generic.jar
Some notes for running the installer:
Before running the installer, set the
DISPLAY environment variable on your system.
JAVA_HOME with the installation location of the supported JDK you installed for your platform.
If you are installing a 64-bit Oracle WebLogic Server on a 64-bit platform:
-d64 flag when using 32/64-bit hybrid JDK's (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).
java -version (or
java -d64 -version on 32/64-bit hybrid JDKs) command to ensure that your
JAVA_HOME refers to a 64-bit JDK.
Choose Middleware Home Directory Screen
Specify the desired location of your new Middleware Home directory. If this directory already exists on your system, it must be an empty directory. If this directory does not already exist, then it will be created for you.
For more information about the Middleware Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.
Select whether or not you want to receive the latest product and security updates. If you choose not to receive anything, you will be asked to verify your selection before continuing.
A Typical installation includes all Oracle WebLogic Server components by default. It also includes both Sun SDK 1.6.0_11 and Oracle JRockit SDK 1.6.0_05. If you want to perform a Typical installation, select Typical and click Next to go to the Choose Product Installation Directories Screen.
A Custom installation gives you the choice of selecting the following components for installation:
Core Application Server
Configuration Wizard and Upgrade Framework
Web 2.0 HTTP Pub-Sub Server
WebLogic JDBC Drivers
Third Party JDBC Drivers
WebLogic Server Clients
WebLogic Web Server Plugins
UDDI and Xquery Support
Server Examples (not selected by default)
If you want to perform a Custom installation, select Custom. You will see the following two screens:
Choose Products and Components Screen
Select the products you want to install.
Note:In order to be configured properly, Oracle SOA Suite requires that Configuration Wizard and Upgrade Framework is selected.
Select the JDKs you want to install.
It is recommended that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment,
boot.properties is used for user names and passwords and polling is used for application deployment.
If you are installing in a production environment, it is recommended that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment.
Choose Product Installation Directories Screen
For more information about the WebLogic Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.
Choose Shortcut Location (Windows only)
If you are installing on a Windows system, you will be asked to specify a location where you would like Windows to create a shortcut to Oracle products.
Installation Summary Screen
Installation Progress Screen
Installation Complete Screen
De-select Run Quickstart.
For more information about installing Oracle WebLogic Server, refer to Oracle WebLogic Server Installation Guide.
If you are installing on a Windows system, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. For more information on how to do this, refer to "Install and Configure Java Access Bridge (Windows Only)" in Oracle Fusion Middleware Administrator's Guide.
Your operating system configuration can influence the behavior of characters supported by Oracle SOA Suite.
On a UNIX operating system, it is highly recommended that you enable Unicode support by setting the
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.
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.
If you are installing Oracle SOA Suite on a DHCP host, you must follow the configuration steps in this section for your platform.
On UNIX systems, configure the host to resolve hostnames to the loopback IP address by modifying the
/etc/hosts file to contain the following entries:
127.0.0.1 hostname.domainname hostname 127.0.0.1 localhost.localdomain localhost
After doing so, check that the hostname resolves to the loopback IP address by entering the following command:
On Windows systems, install a loopback adapter on the DHCP server (see Section 2.2.3, "Installing a Loopback Adapter (Windows Only)"). This assigns a local IP address to your computer.
After installing the adapter, add a line to the
%SYSTEMROOT%\system32\drivers\etc\hosts file with the following format, immediately after the
IP_address hostname.domainname hostname
IP_address with the local IP address of the loopback adapter.
To install a loopback adapter on Windows 2003 or Windows XP:
Open the Windows Control Panel.
Windows 2003: Select Start > Control Panel > Add Hardware.
Windows XP: Select Start > Control Panel, then double-click Add Hardware.
In the "Welcome" window, click Next.
In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.
In the "The following hardware is already installed on your computer" window, in the list of installed hardware, select Add a new hardware device, then click Next.
In the "The wizard can help you install other hardware" window, select Install the hardware that I manually select from a list, then click Next.
In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.
In the "Select Network Adapter" window, make the following selections:
Network Adapter: Microsoft Loopback Adapter
In the "The wizard is ready to install your hardware" window, click Next.
In the "Completing the Add Hardware Wizard" window, click Finish.
If you are using Windows 2003, restart your computer.
Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.
Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.
On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.
In the "Properties" dialog box, click Use the following IP address and do the following:
IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the following non-routable addresses:
192.168.x.x (x is any value between 1 and 255) 10.10.10.10
Subnet mask: Enter
Record the values you entered, which you will need later in this procedure.
Leave all other fields empty.
In the "Local Area Connection 2 Properties" dialog, click OK.
Close Network Connections.
Restart the computer.
Start the System Control panel.
Windows 2003: Select Start > Control Panel > System.
Windows XP: Select Start > Control Panel, then double-click System.
In the "Hardware" tab, click Device Manager.
In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.
Right-click Microsoft Loopback Adapter and select Uninstall.
You can install Oracle SOA Suite on a non-networked computer, such as a laptop. Because a non-networked computer has no access to other computers, you have to install all the components that you need on the computer.
In addition, you must follow the instructions in Section 2.2, "Installing on DHCP Hosts" to install a loopback adapter and modify the
hosts file on your system.
You can install Oracle SOA Suite on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.
The installer picks up the fully qualified domain name from the first entry in
/etc/hosts (on UNIX) or
%SYSTEMROOT%\system32\drivers\etc\hosts (on Windows) file.
For details about WebLogic Server network configuration, refer to "Configure network connections" in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.
For specific network configuration of a system component, refer to the individual component's configuration documentation.
By default, the servers that are created in each domain use the same set of port numbers (for example, the Administration Server uses port 7001). If you want to use custom port numbers, you can change the port number when you run the Oracle Fusion Middleware Configuration Wizard:
The Administration Server port number can be changed on the Configure Administration Server Screen.
The port number for all managed servers in your domain can be changed on the Configure Managed Servers Screen.
If you install multiple instances of Oracle SOA Suite on your system, you must make sure that all of your managed servers use different port numbers, as shown in Figure 2-1:
Figure 2-1 Multiple Instances of Oracle SOA Suite on a Single System
For more information, refer to Chapter 3, "Configuring Oracle SOA Suite".
This section contains the following topics:
The installer requires the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server, Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home"), 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
/jdk160_11 (for UNIX) or
\jdk160_11 (for Windows), 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. Refer to Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home" for more information.
Note:Starting the installer as
rootuser is not supported.
On UNIX systems:
> ./runInstaller -jreLoc JRE_LOCATION
On Windows systems:
D:\ setup.exe -jreLoc JRE_LOCATION
Note:Specify the absolute path to your
JRE_LOCATION; relative paths are not supported.
If no JRE location is specified, you will be prompted to provide the location of your JRE before the installer is started:
[> ./runInstaller Platform is Linux X86 32 bit 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 60229 MB Passed Checking swap space: must be greater than 512 MB. Actual 1013 MB Passed Checking monitor: must be configured to display at least 256 colors. Actual 256 Passed Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-01_02-45-07PM. 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.
The installer writes logs files to the
/log (for UNIX) or
\logs (for Windows) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the SOA_ORACLE_HOME
/oraInst.loc file. On Windows systems, the default location for the inventory directory is
The following install log files are written to the log directory:
If you start the installer with the
-printtime parameter, the
.log file is created in the same directory.
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-2 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-2 Inventory Directory and Group Screens
|No.||Screen||Description and Action Required|
Click OK to continue.
Click OK to continue.
Follow the instructions in Table 2-3 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-3 Installation Flow for Install and Configure Option (Common Screens)
|No.||Screen||When Does This Screen Appear?||Description and Action Required|
Click Next to continue.
Click Next to continue.
Specify Oracle Middleware Home and Oracle Home locations.
Click Next to continue.
Verify the installation about to be performed.
Click Install to continue.
This screen shows the progress of the installation.
Click Finish to dismiss the screen.
After the installation is complete., you must configure your products before you can begin using them. Go to Chapter 3, "Configuring Oracle SOA Suite".
Oracle SOA Suite is not automatically installed with Oracle JDeveloper. Before you can create a SOA application and project, you must download the SOA Suite extension for Oracle JDeveloper (file name
soa-jdev-extension.zip) from the Oracle Technology Network (
http://www.oracle.com/technology/) and import it into Oracle JDeveloper.
For instructions on downloading and installing SOA Suite extension for JDeveloper, see Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.