2.1 Preparing to Install

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.

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.

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:

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

Note:

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.

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.

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.

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.