2 Installing Oracle WebCenter

This chapter describes how to install Oracle WebCenter.

The following topics are covered:

2.1 Preparing to Install

Before you begin, make sure you have completed tasks 1 - 4 listed in Table 1-1 in Chapter 1, "Installation Overview".

2.2 Installing Oracle WebCenter

By default, all Oracle WebCenter components (see Section 1.1, "Oracle WebCenter Components" for a complete list) are installed onto your system. After the products are installed, you can run the Oracle Fusion Middleware Configuration Wizard to configure the product(s) of your choice.

This section contains the following topics:


If you want to install Oracle WebCenter and also Oracle Portal, Forms, Reports and Discoverer on your system, you must create a separate Middleware home for each product. Oracle WebCenter and Oracle Portal, Forms, Reports and Discoverer cannot be installed in the same Middleware home directory.

2.2.1 Obtaining the Software

See "Obtain the Oracle Fusion Middleware Software" in Oracle Fusion Middleware Installation Planning Guide for information on where to obtain the software.

Select one of the download locations and download "Oracle WebCenter." This will be saved to your system as a .zip archive file.

After you download the archive file, unpack the archive file into a directory of your choice on the machine where you will be performing the installation.

2.2.2 Starting the Installer

To start the installer, go to the directory where you unpacked the archive file and switch to the Disk1 directory.

On UNIX operating systems:

cd unpacked_archive_directory/Disk1
./runInstaller -jreLoc JRE_LOCATION

On Windows operating systems:

cd unpacked_archive_directory\Disk1
setup.exe -jreLoc JRE_LOCATION

The installer requires the full path to the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server, a JRE was installed on your system in the jdk160_21 directory inside the Middleware home. You can use this location as the JRE_LOCATION to start the installer.

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

If you do not specify the JRE location with the -jreLoc option, you will be prompted to provide the location of your JRE before the installer is started. For example, on a UNIX operating system:

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.


If you are installing Oracle WebCenter on a 64-bit UNIX or Windows operating system with a 32-bit JDK, you must specify the JRE_LOCATION using the -jreLoc option from the command line. The option to provide your JRE_LOCATION at the prompt is not supported in such cases, and the installer will not start.

2.2.3 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.4 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 details, click on the screen name in the table, 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.5 Installation Screens and Instructions

Table 2-2 lists the screens displayed in Oracle Universal Installer. Follow the instructions in Table 2-2 to install Oracle WebCenter. For details about a screen, click the screen name in the table.


Running the installer as root user is not supported.

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

Table 2-2 Oracle WebCenter Installation Screens in Oracle Universal Installer

No. Screen Description and Action Required


Welcome Screen

Click Next to continue.


Install Software Updates Screen

Select the method you want to use to receive software updates.

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.


Application Server Screen

Select the application server and specify its location.

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

After the installation is complete, you must configure your products before you can begin using them. Go to Chapter 3, "Configuring Oracle WebCenter".

2.3 Installing Oracle JDeveloper

Oracle JDeveloper is a free integrated development environment (IDE) for building Web service-oriented applications, including WebCenter Portal applications, using industry standards for Java, XML, SQL, and Web Services. It supports the complete development life cycle with integrated features for modeling, coding, debugging, testing, profiling, tuning, and deploying applications.

JDeveloper works in tandem with popular open-source frameworks and tools with built-in features for Struts, Ant, JUnit, XDoclets, and CVS, and includes an Extensions SDK that lets developers add capabilities to, and customize, the development environment.

To build WebCenter Portal applications using JDeveloper, users must install the WebCenter extension bundle. The WebCenter extension bundle is a JDeveloper add-in that provides the complete set of WebCenter capabilities and features to the JDeveloper Studio Edition. For information about obtaining and installing Oracle JDeveloper, see the Oracle JDeveloper page on OTN at the following URL:



When you install Oracle JDeveloper on a Windows operating system, be sure that you choose a directory that does not contain spaces. For example, do not use C:\My Home as the installation directory for Oracle JDeveloper. Pages in WebCenter Portal applications are not rendered if there is a space in the path to the installation directory of Oracle JDeveloper.

For information about installing the WebCenter extension bundle, see the section "Installing the WebCenter Extension Bundle" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.


Oracle strongly recommends that you set an environment variable for the user home directory (used by JDeveloper to store the runtime files) that is referenced by JDeveloper. By setting this variable, you can avoid receiving long path name errors that are known to occur in some circumstances.

For detailed instructions on setting this variable on Windows, Linux, UNIX, and Mac OS X operating systems, see "Setting the User Home Directory" in Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.

2.4 Installing WebCenter Back-End Components

In addition to WebCenter Spaces, Portlet Producers, Oracle Discussions, and optionally Oracle Universal Content Manager, you can integrate several other WebCenter Web 2.0 Services into your applications. Some WebCenter Web 2.0 Services, such as Documents, rely on back-end components, such as Oracle Content Server. Similarly, Worklist relies on Oracle BPEL Process Manager which is available as part of Oracle SOA Suite. To integrate such services into your applications, you must install the required back-end components.

Refer to Chapter 5, "Preparing Back-End Components for WebCenter Services" for more information.