3 Common Installation Tasks

This chapter describes some common tasks that should be performed prior to beginning any Oracle Fusion Middleware installation.

The following topics are covered:

3.1 Before You Begin

This section contains important information that you should read before you begin to install or upgrade your system:

3.1.1 Review System Requirements and Specifications

Before performing any upgrade or installation you should read the system requirements 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, database schema requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches:


3.1.2 Review Certification Information

Before performing any upgrade or installation you should read the "Oracle Fusion Middleware Supported System Configurations" document. This document contains certification information related to supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers, adapters, IPv6, JDKs, and third-party products. It is located on the following page:


3.1.3 Review Interoperability and Compatibility

Before performing any upgrade or installation you should read Oracle Fusion Middleware Interoperability and Compatibility Guide. This document contains important information regarding the ability of Oracle Fusion Middleware products to function with previous versions of other Oracle Fusion Middleware, Oracle, or third-party products. This information is applicable to both new Oracle Fusion Middleware users and existing users who are upgrading their existing environment.

3.1.4 Read and Understand Oracle Fusion Middleware Concepts

If you are new to Oracle Fusion Middleware, you should read Chapter 2, "Understanding Oracle Fusion Middleware Concepts and Directory Structure" to familiarize yourself with some of the concepts and terminology you will encounter. You should also be familiar with the concepts described in Oracle Fusion Middleware Concepts before proceeding with an installation or upgrade.

3.1.5 Obtain the Oracle Fusion Middleware Software

Depending on your specific needs, there are multiple places where you can obtain Oracle Fusion Middleware software. For details, see "Task 4: Select an Oracle Fusion Middleware Software Download Site" in the Oracle Fusion Middleware Download, Installation, and Configuration ReadMe:


3.1.6 Install an Application Server

All Oracle Fusion Middleware products (except for Oracle Web Tier) require the presence of an application server on your system. All Oracle Fusion Middleware products support Oracle WebLogic Server as the application server. Beginning with 11g Release 1 (, the following products also support IBM WebSphere as the application server:

  • Oracle Application Developer

  • Oracle SOA Suite and Business Process Management Suite

All Oracle Fusion Middleware products (including Oracle Web Tier) must be installed inside a Middleware home directory. If you choose to install Oracle WebLogic Server, the installer creates a Middleware home directory for you. If you choose to install IBM WebSphere as your application server, you must manually create a separate Middleware home directory, in which you can install your Oracle Fusion Middleware products.

For more information about the installation directory structure, see Section 2.2, "Oracle Fusion Middleware Directory Structure".

To determine the version of Oracle WebLogic Server or IBM WebSphere required for your installation, refer to the "Oracle Fusion Middleware Supported System Configurations" document on the following page:


For instructions on how to install Oracle WebLogic Server, see "Running the Installation Program in Graphical Mode" in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.

For instructions on how to install IBM WebSphere, see Oracle Fusion Middleware Third-Party Application Server Guide.

3.1.7 Install and Configure a Database

Some Oracle Fusion Middleware products, such as Oracle SOA Suite and Oracle WebCenter, require an metadata repository with schemas before those products can be successfully configured. To create or update schemas in a database, use the Repository Creation Utility (RCU).


It is recommended that all metadata repositories reside on a database at the same site as the products to minimize network latency issues.

For more information about managing metadata repositories, refer to "Managing the Oracle Metadata Repository" in Oracle Fusion Middleware Administrator's Guide.

For more information about running RCU, refer to Oracle Fusion Middleware Repository Creation Utility User's Guide.

3.1.8 Create Operating System Users for IBM DB2 Databases

If you are not using an IBM DB2 database, you can skip this section.

IBM DB2 databases authenticates its database users using equivalent operating system users. Therefore, prior to running RCU, one operating system user must be created on the database host for each schema. The operating system user name must match the schema owner name and must contain only lowercase letters; no all-uppercase or mixed-case names are allowed. For example, if you plan to create a schema named DEV_MDS using RCU, then the operating system user must be named dev_mds (all lowercase letters).

You can create the operating system user with the following command (this example creates the operating system user dev_mds and assigns the password welcome1):

/usr/sbin/useradd dev_mds -p welcome1 -d /scratch/dev_mds

Refer to your system documentation for more information.

3.2 Installing Oracle Configuration Manager

During installation, you will be asked whether or not you want to configure your system to automatically check for security (Specify Security Updates screen) and software (Install Software Updates screen) updates. Electing to do so installs Oracle Configuration Manager on your system.

Oracle Configuration Manager continuously tracks key Oracle and system details, providing essential data to help you manage and service your configurations. Collected data is sent via HTTPS to Oracle Support, which maintains a secure view of each configuration. My Oracle Support then provides system health checks, patch advice, and other valuable information about your Oracle products. Configuration manager does NOT collect application data, such as user passwords.

For more information, log into or create a My Oracle Support account at https://support.oracle.com/, then click on the Collector tab.

3.3 Understanding Installation and Configuration Privileges and Users

This section contains the following:

3.3.1 Installation and Configuration Privileges

The user who installs a Fusion Middleware product owns and has read, write, and execute privileges on the binary files installed in the Oracle home. Other users in the operating system group have only read and execute privileges (no write privileges). This means they cannot write to the files, but they can use the installed binaries in the Oracle home to configure a domain or set of Fusion Middleware products.

During configuration, the files generated by the configuration process are owned by the user who ran the Configuration Wizard. The user who ran the Configuration Wizard has read, write, and execute privilege on those files. Other users in the operating system group can read and execute the files, but they do not have write privileges.

These defaults are set with the assumption that all the administrators are in the same group. Multiple administrators in that group will be configuring domains and products from a common set of Middleware homes and Oracle homes.

3.3.2 Installing as a Non-Default User on UNIX Operating Systems

On UNIX operating systems, the installation of Fusion Middleware products is owned and controlled as a known user (for example, "oracle"). The file permissions associated with this installation are configured to ensure the highest level of security possible, which by default are 700 (meaning all files are owned and accessible by the owner only).

Changing the default permissions settings will reduce the security of the installation and possibly your system. Therefore, making such a change is not recommended. If access to particular files or executables is required by other users, the UNIX sudo command (or other similar command) should be considered in lieu of changing file permissions.

Refer to your UNIX operating system Administrator's Guide or contact your operating system vendor if you need further assistance.

3.4 Installing and Configuring Java Access Bridge (Windows Only)

If you are installing on a Windows operating 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.

3.5 Installing on DHCP Hosts

If you are installing your Oracle Fusion Middleware product on a DHCP host, you must follow the configuration steps in this section for your platform.

3.5.1 For Linux x86 Platforms

On Linux x86 operating systems, configure the host to resolve host names to the loopback IP address by modifying the /etc/hosts file to contain the following entries: hostname.domainname hostname localhost.localdomain localhost

After doing so, check that the host name resolves to the loopback IP address by entering the following command:

/bin/ping hostname.domainname

3.5.2 For Windows x86 Platforms

On Windows operating systems, install a loopback adapter on the DHCP server (see Section 3.5.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 localhost line:

IP_address   hostname.domainname   hostname

Replace IP_address with the local IP address of the loopback adapter.

3.5.3 Installing a Loopback Adapter (Windows Only)

To install a loopback adapter on Windows 2003 or Windows XP:

  1. Open the Windows Control Panel.

    Windows 2003: Select Start > Control Panel > Add Hardware.

    Windows XP: Select Start > Control Panel, then double-click Add Hardware.

  2. In the "Welcome" window, click Next.

  3. In the "Is the hardware connected?" window, select Yes, I have already connected the hardware, then click Next.

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

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

  6. In the "From the list of hardware types, select the type of hardware you are installing" window, select Network adapters, then click Next.

  7. In the "Select Network Adapter" window, make the following selections:

    • Manufacturer: Microsoft

    • Network Adapter: Microsoft Loopback Adapter

  8. Click Next.

  9. In the "The wizard is ready to install your hardware" window, click Next.

  10. In the "Completing the Add Hardware Wizard" window, click Finish.

  11. If you are using Windows 2003, restart your computer.

  12. Right-click My Network Places on the desktop and choose Properties. This displays the Network Connections Control Panel.

  13. Right-click the connection that was just created. This is usually named "Local Area Connection 2". Choose Properties.

  14. On the "General" tab, select Internet Protocol (TCP/IP), then click Properties.

  15. In the "Properties" dialog box, click Use the following IP address and do the following:

    1. 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)
    2. Subnet mask: Enter

    3. Record the values you entered, which you will need later in this procedure.

    4. Leave all other fields empty.

    5. Click OK.

  16. In the "Local Area Connection 2 Properties" dialog, click OK.

  17. Close Network Connections.

  18. Restart the computer.

3.5.4 Removing a Loopback Adapter (Windows Only)

To remove a loopback adapter on Windows 2003 or Windows XP:

  1. Start the System Control panel.

    Windows 2003: Select Start > Control Panel > System.

    Windows XP: Select Start > Control Panel, then double-click System.

  2. In the "Hardware" tab, click Device Manager.

  3. In the "Device Manager" window, expand Network adapters. You should see Microsoft Loopback Adapter.

  4. Right-click Microsoft Loopback Adapter and select Uninstall.

  5. Click OK.

3.6 Installing on a Non-Networked Computer

You can install your Oracle Fusion Middleware product 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 3.5, "Installing on DHCP Hosts" to install a loopback adapter and modify the hosts file on your system.

3.7 Installing on a Multihomed Computer

You can install your Oracle Fusion Middleware product 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 operating systems) or %SYSTEMROOT%\system32\drivers\etc\hosts (on Windows operating systems) file. So if your file looks like the following: localhost.localdomain localhost
10.222.333.444 examplehost1.example.com examplehost1
20.222.333.444 examplehost2.example.com examplehost2

examplehost1.example.com would be picked for configuration.

For specific network configuration of a system component, refer to the individual component's configuration documentation.

3.8 Checking Your Hosts File Entries for OPMN

If you are installing an Oracle Fusion Middleware product that also installs Oracle Process Manager and Notification Server (OPMN), you must make sure the installation system has valid entries in the hosts (/etc/hosts on UNIX systems and C:\windows\system32\drivers\etc\hosts on Microsoft Windows systems) file. You must make sure that the IP address is valid and corresponds to the network setup on the system.

You can check your system's IP address and host name as follows:

On UNIX operating systems:

ipconfig -a

On Microsoft Windows operating systems:

ipconfig /all

The IP address and corresponding host name in your hosts file must match the IP address and host name you get from the ipconfig command. Otherwise, the opmn.xml file will contain incorrect configuration information, and OPMN will not start.

3.9 Recovering From a Partial or Interrupted Installation

Should your installation process be interrupted prior to completion, the result is likely an incomplete and non-functional partial installation. If this occurs, the recommended approach is to attempt to uninstall the previous installation. If that is successful, you can re-install normally, otherwise you should re-install into a new Middleware home.

3.10 Creating and Starting Managed Servers on a Remote Machine

To create and start a Managed Server in a WebLogic domain on a remote machine, complete the following steps:

  • Use the pack command located in the WebLogic_Home/common/bin (on UNIX operating systems) or WebLogic_Home\common\bin (on Microsoft Windows operating systems) directory to create a Managed Server template that contains a subset of the files in a domain that are required to create a Managed Server domain directory hierarchy on a remote machine.

    The -managed={true|false} parameter of the pack command specifies whether the template is to be used to create Managed Servers on remote machines.

  • Use the unpack command located in the WebLogic_Home/common/bin (on UNIX operating systems) or WebLogic_Home\common\bin (on Windows operating systems) directory to create the Managed Server domain directory on the remote machine.

For more information, see the "Creating and Starting a Managed Server on a Remote Machine" in Oracle Fusion Middleware Creating Templates and Domains Using the Pack and Unpack Commands.