Oracle® Fusion Middleware

Installation Guide for Oracle WebCenter

11g Release 1 (11.1.1)

E12001-02

November 2009

Oracle Fusion Middleware Installation Guide for Oracle WebCenter 11g Release 1 (11.1.1)

E12001-02

Copyright © 2009 Oracle and/or its affiliates. All rights reserved.

Primary Author:  Kevin Hwang

Contributing Author:  Savita Thakur

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Intended Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Installation Overview

- 1.1 Oracle WebCenter Components

- 1.2 Oracle WebCenter Installation Roadmap

- 1.3 Oracle WebCenter Directory Structure

2 Installing Oracle WebCenter

- 2.1 Preparing to Install

- 2.1.1 System Requirements and Certification

- 2.1.2 Check for Supported Database

- 2.1.3 Create Schemas for Oracle WebCenter

- 2.1.4 Install Oracle WebLogic Server and Create the Middleware Home

- 2.1.5 Install and Configure Java Access Bridge (Windows Only)

- 2.1.6 Know your HTTP Server Web Address

- 2.2 Installing Oracle JDeveloper

- 2.3 Installing on DHCP Hosts

- 2.3.1 For UNIX Platforms

- 2.3.2 For Windows x86 Platforms

- 2.3.3 Installing a Loopback Adapter (Windows Only)

- 2.3.4 Removing a Loopback Adapter (Windows Only)

- 2.4 Installing on a Non-Networked Computer

- 2.5 Installing on a Multihomed Computer

- 2.6 Installing WebCenter Back-End Applications

- 2.7 Using Custom Port Numbers

- 2.8 Installing Oracle WebCenter

- 2.8.1 Starting the Installer

- 2.8.2 Installation Log Files

- 2.8.3 Inventory Screens (UNIX Only)

- 2.8.4 Installation Screens and Instructions

3 Configuring Oracle WebCenter

- 3.1 Configuration Instructions

- 3.1.1 Running the Configuration Wizard with an Oracle RAC Database

- 3.1.2 Starting the Oracle Fusion Middleware Configuration Wizard

- 3.1.3 Creating a Configuration Log File

- 3.1.4 Creating a New Domain

- 3.1.5 Extending an Existing Domain

- 3.1.6 Configuration Wizard Optional Configuration Screens

- 3.1.6.1 Administration Server Options

- 3.1.6.2 Managed Servers, Clusters, and Machines Options

- 3.1.6.3 Deployments and Services Options

- 3.1.6.4 JMS File Store Options

- 3.1.6.5 RDBMS Security Store Options

- 3.2 Working with Oracle WebCenter Components

4 Preparing Back-End Components for WebCenter Services

- 4.1 Introduction to WebCenter Services

- 4.2 Back-End Requirements for the Instant Messaging and Presence (IMP) Service

- 4.2.1 Communication Server - Installation

- 4.2.2 Communication Server - Configuration and Integration

- 4.3 Back-End Requirements for Content Integration and the Documents Service

- 4.3.1 Oracle Content Server Requirements

- 4.3.1.1 Oracle Content Server - Prerequisites

- 4.3.1.2 Oracle Content Server - Installation

- 4.3.1.3 Oracle Content Server - Configuration

- 4.3.1.4 Oracle Content Server - Integration

- 4.3.2 Oracle Portal Installation

- 4.3.2.1 Oracle Portal - Installation

- 4.3.2.2 Oracle Portal - Integration

- 4.4 Back-End Requirements for the Mail Service

- 4.5 Back-End Requirements for the Search Service

- 4.5.1 Oracle SES - Installation

- 4.5.2 Oracle SES - Integration

- 4.6 Back-End Requirements for the Worklist Service

- 4.7 Back-End Requirements for WebCenter Spaces Workflows

- 4.7.1 Oracle SOA Suite - Installation

- 4.7.2 Oracle SOA Server - Workflow Deployment

- 4.7.2.1 Deploying sca_CommunityWorkflows.jar

- 4.7.2.2 Deploying WebCenterWorklistDetailApp.ear

- 4.7.3 Oracle SOA and Oracle WebCenter - WS-Security Configuration

- 4.7.4 Oracle WebCenter - BPEL Server Connection Setup

- 4.8 Configuring an External LDAP-Based Identity Store

5 Deinstalling Oracle WebCenter

- 5.1 Deinstallation Instructions

- 5.1.1 Stopping Oracle Fusion Middleware

- 5.1.2 Removing Oracle WebCenter Schemas

- 5.1.2.1 Starting RCU

- 5.1.2.2 Instructions for Dropping the WebCenter Schemas

- 5.1.3 Removing Oracle Universal Content Management

- 5.1.4 Removing Oracle WebCenter

- 5.1.4.1 Removing the WebCenter Oracle Home

- 5.1.4.2 Removing the Oracle Common Home

- 5.1.5 Removing Oracle WebLogic Server

- 5.1.6 Removing Oracle JDeveloper

- 5.1.7 Removing the Program Groups (Windows Only)

- 5.2 Reinstallation

A Oracle WebCenter Installation Screens

- A.1 Specify Inventory Directory Screen (UNIX Only)

- A.2 Inventory Location Confirmation Screen (UNIX Only)

- A.3 Welcome Screen

- A.4 Prerequisite Checks Screen

- A.5 Specify Installation Location Screen

- A.6 Specify UCM Configuration Options Screen

- A.7 Specify UCM Database Details Screen

- A.8 Installation Summary Screen

- A.9 Installation Progress Screen

- A.10 Specify UCM Installer Directory Screen

- A.11 UCM Installation Progress Screen

- A.12 Installation Completed Screen

B Oracle WebCenter Configuration Screens

- B.1 Welcome Screen

- B.2 Select a WebLogic Domain Directory Screen

- B.3 Select Domain Source Screen

- B.4 Select Extension Source Screen

- B.5 Specify Domain Name and Location Screen

- B.6 Configure Administrator Username and Password Screen

- B.7 Configure Server Start Mode and JDK Screen

- B.8 Configure JDBC Component Schema Screen

- B.9 Test Component Schema Screen

- B.10 Select Optional Configuration Screen

- B.11 Configure Administration Server Screen

- B.12 Configure Managed Servers Screen

- B.13 Configure Clusters Screen

- B.14 Assign Servers to Clusters Screen

- B.15 Create HTTP Proxy Applications Screen

- B.16 Configure Machines Screen

- B.17 Assign Servers to Machines Screen

- B.18 Target Deployments to Servers or Clusters Screen

- B.19 Target Services to Servers or Clusters Screen

- B.20 Configure JMS File Stores Screen

- B.21 Configure RDBMS Security Store Database Screen

- B.22 Configuration Summary Screen

- B.23 Creating Domain Screen

- B.24 Extending Domain Screen

C Oracle WebCenter Deinstallation Screens

- C.1 Welcome Screen

- C.2 Deinstall Oracle Home Screen

- C.3 Deinstall Progress Screen

- C.4 Deinstall Completed Screen

D Silent Installation

- D.1 What is a Silent Installation?

- D.2 Creating Response Files

- D.2.1 Contents of the oracle.as.webcenter.top.Custom.rsp File

- D.2.2 Contents of the sampleResponse.rsp File

- D.2.3 Securing Your Silent Installation

- D.3 Pre-Installation Tasks

- D.3.1 UNIX Users: Creating the oraInst.loc File

- D.3.2 Windows Users: Creating the Registry Key

- D.4 Silent Installation Instructions

- D.4.1 Sample Commands

- D.4.2 Sample Output

- D.5 Silent De-Installation

E Troubleshooting

- E.1 General Troubleshooting Tips

- E.2 Troubleshooting Oracle Fusion Middleware Installation

- E.2.1 Installation Log Files

- E.2.2 Configuration Log Files

- E.3 Keeping Track of Your JRE Location

- E.4 Need More Help?

Index

Preface

The Oracle Fusion Middleware Installation Guide for Oracle WebCenter provides information and instructions for installing, configuring, and troubleshooting Oracle WebCenter.

Intended Audience

This guide is intended for users who are installing Oracle WebCenter for the first time and are comfortable running some system administration operations, such as creating users and groups, adding users to groups, and installing operating system patches on the computer where your products will be installed. Users on UNIX systems who are installing need root access to run some scripts.

Documentation Accessibility

Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.

Accessibility of Code Examples in Documentation

Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.

Accessibility of Links to External Web Sites in Documentation

This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.

Deaf/Hard of Hearing Access to Oracle Support Services

To reach Oracle Support Services, use a telecommunications relay service (TRS) to call Oracle Support at 1.800.223.1711. An Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process. Information about TRS is available at http://www.fcc.gov/cgb/consumerfacts/trs.html, and a list of phone numbers is available at http://www.fcc.gov/cgb/dro/trsphonebk.html.

Related Documents

For additional information, see the following manuals:

- Oracle Fusion Middleware Administrator's Guide

- Oracle Fusion Middleware Concepts

- Oracle Fusion Middleware High Availability Guide

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Installation Overview

Oracle WebCenter is a component of Oracle Fusion Middleware. This chapter provides an overview of Oracle WebCenter and outlines the tasks that a Fusion Middleware administrator must perform to install Oracle WebCenter and get it up and running.

This chapter includes the following sections:

- Section 1.1, "Oracle WebCenter Components"

- Section 1.2, "Oracle WebCenter Installation Roadmap"

- Section 1.3, "Oracle WebCenter Directory Structure"

1.1 Oracle WebCenter Components

Oracle WebCenter combines the standards-based, declarative development of Java Server Faces (JSF), the flexibility and power of portals, and a set of integrated WebCenter Services to boost end-user productivity. With the set of components offered through Oracle WebCenter, you can create social applications, enterprise portals, composite applications, and Internet/Intranet web sites.

Oracle WebCenter contains the following components:

- Oracle WebCenter Framework
Provides the ability to embed portlets, content, and customizable components into WebCenter applications.

Oracle WebCenter Framework is automatically installed when you install Oracle WebCenter.

- Oracle WebCenter Spaces
Offers a single, integrated, web-based environment for social networking, communication, and personal productivity through a robust set of services and applications.

Configuring this component is optional.

- Oracle WebCenter Portlets
Supports deployment and execution of both standards-based portlets (JSR 168 and WSRP 1.0 and 2.0) and traditional Oracle PDK-Java based portlets. Includes the following preconfigured portlet producers: OmniPortlet, Web Clipping, Rich Text Portlet, WSRP Parameter Form Portlet, sample WSRP portlet producers, and sample PDK-Java portlet producers.

Configuring this component is optional.

- Oracle WebCenter Discussions
Supports integration of discussion forums and announcements into WebCenter applications.

Configuring this component is optional.

- Oracle WebCenter Wiki and Blog Server
Supports integration of wikis and blogs into WebCenter applications. Also supports features that enable application users to create their own wikis and blogs.

Configuring this component is optional.

- Oracle Content Server
Provides a flexible, secure, centralized, web-based repository that manages all phases of the content lifecycle: from creation and approval, to publishing, searching, expiration, and archival or disposition.

Configuring this component is optional.

1.2 Oracle WebCenter Installation Roadmap

Table 1-1 describes the high-level tasks for installing and configuring Oracle WebCenter, and specifies whether these tasks are mandatory or optional. The table also includes documentation links that you can access to get more details about each task.

Table 1-1 Oracle WebCenter Installation Procedure

Task

Description

Mandatory/Optional?

Documentation

Task 1 - Prepare your system environment for installation

Ensure that your system environment meets the general installation requirements for Oracle Fusion Middleware, Oracle WebCenter, and Repository Creation Utility (RCU).

Mandatory

For information about:

- System requirements, see http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

- Certification information, see http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

- Other installation requirements, see Section 2.1, "Preparing to Install."

Task 2 - Create WebCenter schemas

Oracle WebCenter components require schemas that must be installed in a supported Oracle database or a supported non-Oracle database like Microsoft SQL Server. Prepare a database for WebCenter schemas, then use RCU to create schemas.

Mandatory

For information, see:

- Section 2.1.2, "Check for Supported Database"

- Section 2.1.3, "Create Schemas for Oracle WebCenter"

Task 3 - Install Oracle WebLogic Server

Oracle WebCenter runs on Oracle WebLogic Server.

Install Oracle WebLogic Server. The installer creates a Middleware home directory, and, beneath it, a WebLogic Server home directory, as shown in Figure 1-1.

Mandatory

For information, see Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home."

See Also:

- Oracle WebLogic Server Installation Guide

- "Middleware Home and WebLogic Home Directories" in the Oracle Fusion Middleware Installation Planning Guide

Task 4 - Install Oracle WebCenter

Use the WebCenter installer to install Oracle WebCenter. Within the Middleware home directory, the installer creates a WebCenter Oracle home directory and the oracle_common home directory, as shown in Figure 1-1.

The installer lays down the binaries for various WebCenter products, like WebCenter Spaces and Oracle WebCenter Discussions.

Note: The WebCenter installer gives you the option to install and configure Oracle Content Server 10.1.3.5.1. You can choose to install Oracle Content Server while installing Oracle WebCenter, or later, by performing a standalone installation. Regardless of when you install Oracle Content Server, before doing so you must ensure that Oracle HTTP Server is already installed.

Mandatory

For information about installing Oracle WebCenter, see Section 2.8, "Installing Oracle WebCenter."

Task 5 - Configure Oracle WebCenter

Run the Oracle Fusion Middleware Configuration Wizard to create and configure a domain for Oracle WebCenter and choose the components you want to install.

The installer creates the user_projects/domain and user_projects/applications directories, both of which contain a WebCenter domain directory.

The WebCenter domain directory in the domains directory contains the Administration Server and several Managed Servers, depending on the components you choose to install.

After the WebCenter domain is created, you can extend it later if you want to add more components to the domain.

Mandatory

For information, see Chapter 3, "Configuring Oracle WebCenter."

Task 6 - Start the Administration Server and managed servers

To start Oracle WebCenter, you must first start the Administration Server.

To start working with any Oracle WebCenter component, you must start the Managed Server to which that component is deployed. You can then access the component's URL and configure the component according to your requirements.

Mandatory

For information about:

- Starting the Administration Server, see the "Starting the Administration Server" section in the Oracle Fusion Middleware Installation Guide for Application Developer.

- Starting Managed Servers and working with WebCenter components, see Section 3.2, "Working with Oracle WebCenter Components."

Task 7 - Install and configure back-end components for WebCenter Services

Developers and applications users can integrate WebCenter Services into WebCenter applications. Certain services, such as Documents, rely on back-end components, such as Oracle Content Server. To provide for service integration into WebCenter applications, you must install and configure the required back-end components.

WebCenter Spaces provides several prebuilt workflows for group space membership notifications, group space subscription requests, and so on. To enable them, you must install and configure a Business Process Execution Language (BPEL) server.

Optional

For information, see Chapter 4, "Preparing Back-End Components for WebCenter Services."

Task 8 - Install and configure an external LDAP-based identity store

By default, Oracle WebCenter uses Oracle WebLogic Server's embedded LDAP identity store. Although secure, the out-of-the-box embedded LDAP may not scale appropriately for large enterprise production environments.

To manage the identities of users across diverse servers and enable single sign-on across applications, you can install and configure an external LDAP-based identity store.

Optional

For information, see Section 4.8, "Configuring an External LDAP-Based Identity Store."

1.3 Oracle WebCenter Directory Structure

Figure 1-1 shows the directory structure of an Oracle WebCenter installation. It also lists the high-level mandatory installation tasks described in Table 1-1.

Figure 1-1 Directory Structure of Oracle WebCenter Installation

When you install Oracle WebLogic Server, the installer creates a WebLogic Server home directory under the Middleware home directory. During Oracle WebCenter installation, the installer creates a WebCenter Oracle home directory and the oracle_common home directory, which contains WebCenter binaries and supporting files.

When you create a WebCenter domain, the configuration wizard creates the user_projects/domains and user_projects/applications directories, both of which contain a WebCenter domain directory. The WebCenter domain directory in the domains directory contains the Administration Server and several Managed Servers that host the various WebCenter components. Based on the component that you choose to install, the configuration wizard may create the following managed servers:

- WLS_Spaces - Hosts Oracle WebCenter Spaces

- WLS_Portlet - Hosts Oracle WebCenter Portlets

- WLS_Services - Hosts Oracle WebCenter Discussions and Oracle WebCenter Wiki and Blog Server

2 Installing Oracle WebCenter

This chapter describes how to install Oracle WebCenter 11g Release 1 (11.1.1).

The following topics are covered:

- Section 2.1, "Preparing to Install"

- Section 2.2, "Installing Oracle JDeveloper"

- Section 2.3, "Installing on DHCP Hosts"

- Section 2.4, "Installing on a Non-Networked Computer"

- Section 2.5, "Installing on a Multihomed Computer"

- Section 2.6, "Installing WebCenter Back-End Applications"

- Section 2.7, "Using Custom Port Numbers"

- Section 2.8, "Installing Oracle WebCenter"

2.1 Preparing to Install

Make sure you have read the information in this section before you install Oracle WebCenter:

- Section 2.1.1, "System Requirements and Certification"

- Section 2.1.2, "Check for Supported Database"

- Section 2.1.3, "Create Schemas for Oracle WebCenter"

- Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home"

- Section 2.1.5, "Install and Configure Java Access Bridge (Windows Only)"

- Section 2.1.6, "Know your HTTP Server Web Address"

2.1.1 System Requirements and Certification

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. Both of these documents are available on Oracle Technology Network (OTN).

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:

http://www.oracle.com/technology/software/products/ias/files/fusion_requirements.htm

The certification document covers supported installation types, platforms, operating systems, databases, JDKs, and third-party products:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

Note:
If you are installing the 32-bit version of the product, the system on which you are installing must also be a supported 32-bit system. Installing a 32-bit version of the product on a 64-bit system is not supported.

2.1.2 Check for Supported Database

Installation of Oracle WebCenter requires the availability of a 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:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2.1.3 Create Schemas for Oracle WebCenter

Oracle WebCenter requires 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:

Note:
If you are creating the schemas in a Microsoft SQL Server database, a database instance must be created prior to running RCU. The MDS schema has some specific requirements; see "Creating a Database-Based Metadata Repository" in Oracle Fusion Middleware Administrator's Guide for more information.
In addition, the MDS schema requires a database with case sensitive collation, while Oracle Content Server 10g requires a database instance with case insensitive collation.

If you wish to install Oracle Content Server 10g on a SQL Server database, you will need to create two database instances (one with case sensitive collation and one with case insensitive collation) and run RCU twice: once to install the Oracle Content Server 10g schemas into the database instance with case insensitive collation, and a second time to install all of the other WebCenter schemas into the database instance with case sensitive collation.

1. Insert the RCU CD-ROM and start RCU from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory:
On UNIX operating systems:

./rcu

On Windows operating systems:

rcu.bat

You can also download a .zip file containing RCU from Oracle Technology Network (OTN):

http://www.oracle.com/technology/

After downloading the .zip file, extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX operating systems) or RCU_HOME\bin (on Windows operating systems) 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 .zip file to a directory name containing spaces.

2. Welcome Screen
Click Next.

3. Create Repository Screen
Select Create.

Click Next.

4. Database Connection Details Screen
Provide the necessary credentials for RCU to be able to connect to your Oracle database:

- Host Name: Specify the name of the machine on which your database resides in the format host.domain.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 DB_NAME and DB_DOMAIN parameters.

For Oracle RAC databases, specify the service name of one of the nodes in this field. For example: sales.mydomain.com.

- Username: Specify the name of a user with DBA or SYSDBA privileges. The default user name with SYSDBA privileges is SYS.

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

If you are using a Microsoft SQL Server database, provide the following credentials:

- Unicode Support: Select Yes or No from the drop-down list.

- Server Name: Enter the host name, IP address, or complete server name in host\server format of the server where your database is running..

- Port: Specify the database listener port number.

- Database Name: Specify the name of your database.

- Username: Specify the name of a user with DBA or SYSDBA privileges.

- Password: Specify the password for your database user.

Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

5. Select Components Screen
Near the top of the screen, select Create a New Prefix. If you are the only user of the database instance, you may use the default prefix DEV. If you are sharing the database instance with other Oracle Fusion Middleware users, refer to Oracle Fusion Middleware Repository Creation Utility User's Guide for more information about prefixes.

Click the plus sign (+) icon next to WebCenter Suite to view all the schemas in this category. Select the necessary schemas for the product(s) you want to install. If the schema has dependencies, the dependencies are automatically selected for you (see Table 2-1).

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 prefix_schemaname. For example, if you used the default prefix DEV, you will supply the following schema name for the MDS schema:
DEV_MDS

Table 2-1 Required Schemas for Oracle WebCenter Components

Component

Schema Owner

Selected Schemas (Dependencies)

WebCenter Spaces

WEBCENTER

prefix_MDS (Metadata Services)

Portlet Producers

PORTLET

None.

Discussions

DISCUSSIONS

None.

Discussions Crawler

DISCUSSIONS_CRAWLER

prefix_DISCUSSIONS (Oracle Discussions)

Wiki and Blogs

WIKI

None.

Oracle Content Server 10g

OCSERVER

None.

If you need a schema for your custom WebCenter application, create a few schema using the WebCenter Spaces prefix_WEBCENTER schema as a template (for example, if the schema DEV_WEBCENTER already exists in your database, you can create a new schema called CUST_WEBCENTER).

Click Next. A "Checking Prerequisites" screen will appear. After the checking is complete with no errors, click OK to dismiss the screen.

6. Schema Passwords Screen
There are three ways to specify schema passwords on this 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.

Click Next.

7. Map Tablespaces Screen
Click Next. A "Creating Tablespaces" screen will appear. After the tablespaces are created with no errors, click OK to dismiss the screen.

8. Summary Screen
Click Create. A "CREATE" screen will appear. After the schemas are created with no errors, click OK to dismiss the screen.

9. Completion Summary Screen
Click Close.

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

2.1.4 Install Oracle WebLogic Server and Create the Middleware Home

Oracle WebCenter requires an Oracle WebLogic Server on your system. If you do not already have one, follow the instructions in this section to install Oracle WebLogic Server.

1. Insert the Oracle WebLogic Server CD-ROM or download the installer from the following URL:

http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html

You are looking for the following executable files:

- wls1032_linux32.bin (for 32-bit Linux systems)

- wls1032_win32.exe (for 32-bit Windows systems)

- wls1032_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:

http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

2. Run your installer file directly from the CD-ROM, or copy the file to your local system and run it locally.
Some notes for running the installer:

- Before running the installer, set the DISPLAY environment variable on your system.

- Replace 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, use the -d64 flag when using 32/64-bit hybrid JDK's (such as the HP JDK for HP-UX and SUN JDK for Solaris SPARC).
Execute JAVA_HOME/bin/java -version (or JAVA_HOME/bin/java -d64 -version on 32/64-bit hybrid JDKs) to ensure that your JAVA_HOME refers to a 64-bit JDK.

To run the installer on a 32-bit Linux operating system:

./wls1032_linux32.bin

To run the installer on 32-bit Windows operating systems:

wls1032_win32.exe

To run the installer on 64-bit UNIX operating systems:

JAVA_HOME/bin/java -jar wls1032_generic.jar

or

JAVA_HOME/bin/java -d64 -jar wls1032_generic.jar

To run the installer on 64-bit Windows operating systems:

JAVA_HOME\bin\java -jar wls1032_generic.jar

3. Welcome Screen
Click Next.

4. Choose Middleware Home Directory Screen
Select Create a new Middleware Home to create a new Middleware Home directory.

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.

Click Next.

5. Register for Security Updates Screen
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.

Click Next.

6. Choose Install Type Screen
A Typical installation includes all Oracle WebLogic Server components by default. It also includes both Sun SDK 1.6.0_14 and Oracle JRockit SDK 1.6.0_14. 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

- Administration Console

- 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:

1. Choose Products and Components Screen
Select the products you want to install.

Note:
In order to be configured properly, Oracle WebCenter requires that Configuration Wizard and Upgrade Framework is selected.

2. JDK Selection Screen
Select the JDKs you want to install.

Oracle recommends 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, Oracle recommends 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.

Click Next.

7. Choose Product Installation Directories Screen

Specify the desired location for your WebLogic Server Home directory. The default location is wlserver_10.3 inside your Middleware Home directory.

For more information about the WebLogic Home directory, refer to "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

Click Next.

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

Click Next.

9. Installation Summary Screen
Click Next.

10. Installation Progress Screen
Click Next.

11. Installation Complete Screen
De-select Run Quickstart.

Click Done.

For more information about installing Oracle WebLogic Server, refer to Oracle WebLogic Server Installation Guide.

2.1.5 Install and Configure Java Access Bridge (Windows Only)

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

2.1.6 Know your HTTP Server Web Address

If you plan to install Oracle Universal Content Management (UCM) as part of the WebCenter installation, you should know your the address and port number of your HTTP server. An HTTP server is required and must be up and running if you choose to install Oracle UCM.

If your HTTP server is running in a UNIX system, you can find your HTTP server port number by opening the /etc/services file and searching for the string "HTTP."

On Windows systems, you can use the netstat command from your DOS prompt to see the ports that are being used on your system.

For more information, see Section 4.3.1.2, "Oracle Content Server - Installation".

2.2 Installing Oracle JDeveloper

Oracle JDeveloper is a free integrated development environment (IDE) for building Web service-oriented 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.

With WebCenter extensions and Oracle JDeveloper installed, you can write custom WebCenter applications to add services like linking, tagging, and discussions, along with a way for business users to create and customize pages.

If you want to install Oracle JDeveloper, refer to Oracle Fusion Middleware Installation Guide for Oracle JDeveloper.

2.3 Installing on DHCP Hosts

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

2.3.1 For UNIX Platforms

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:

/bin/ping hostname.domainname

2.3.2 For Windows x86 Platforms

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

2.3.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)
10.10.10.10

2. Subnet mask: Enter 255.255.255.0.

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.

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

2.4 Installing on a Non-Networked Computer

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

2.5 Installing on a Multihomed Computer

You can install Oracle WebCenter 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.

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.

2.6 Installing WebCenter Back-End Applications

In addition to WebCenter Spaces, Portlet Producers, Oracle Discussions, Oracle Wiki and Blogs, 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 4, "Preparing Back-End Components for WebCenter Services" for more information.

2.7 Using Custom Port Numbers

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.

For more information, refer to Chapter 3, "Configuring Oracle WebCenter".

Fore more information about port numbers, refer to "Port Numbers" in Oracle Fusion Middleware Administrator's Guide.

2.8 Installing Oracle WebCenter

The Oracle WebCenter products (WebCenter Framework, WebCenter Spaces, WebCenter Portlets, WebCenter Discussions, WebCenter Wiki and Blog Server, and optionally Oracle Universal Content Manager) are installed onto your system by default. 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:

- Section 2.8.1, "Starting the Installer"

- Section 2.8.2, "Installation Log Files"

- Section 2.8.3, "Inventory Screens (UNIX Only)"

- Section 2.8.4, "Installation Screens and Instructions"

2.8.1 Starting the Installer

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 MW_HOME/jdk160_14_R27.6.4-18 (on UNIX systems) or MW_HOME\jdk160_14_R27.6.4-18 (on Windows 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. Refer to Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home" for more information.

When you provide the JRE_LOCATION you must specify an absolute path; relative paths will not work.

On UNIX operating systems:

> ./runInstaller -jreLoc JRE_LOCATION

On Windows operating systems:

D:\ setup.exe -jreLoc JRE_LOCATION

Note:
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 WebCenter on a 64-bit platform 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
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 500 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.

2.8.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 E.2.1, "Installation Log Files" for more information about the log files and their contents.

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

1

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.

2

Inventory Location Confirmation Screen (UNIX Only)

Run the createCentralInventory.sh script as root.

Click OK to continue.

2.8.4 Installation Screens and Instructions

Follow the instructions in Table 2-3 to install Oracle WebCenter.

Note:
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 to access the online help.

Table 2-3 Installation Flow

No.

Screen

When Does This Screen Appear?

Description and Action Required

1

Welcome Screen

Always

Click Next to continue.

2

Prerequisite Checks Screen

Always

Click Next to continue.

3

Specify Installation Location Screen

Always

Specify the 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.

4

Specify UCM Configuration Options Screen

Always

Select whether or not you want to install Oracle UCM.

If you do, click Next to continue.

If not, skip to Installation Summary Screen.

5

Specify UCM Database Details Screen

Only if you selected Install and Configure Oracle Universal Content Management on the Specify UCM Configuration Options Screen.

Specify the connection details to your database with the OCSERVER schema.

Click Next to continue.

6

Installation Summary Screen

Always

Verify the information on this screen.

Click Install to begin the installation.

7

Installation Progress Screen

Always

This screen shows the progress of the installation.

Click Next to continue.

If you chose not to install Oracle UCM, skip to Installation Completed Screen.

8

Specify UCM Installer Directory Screen

Only if you selected Install and Configure Oracle Universal Content Management on the Specify UCM Configuration Options Screen.

Specify the location to the UCM installer.

Click Next to continue.

9

UCM Installation Progress Screen

Only if you selected Install and Configure Oracle Universal Content Management on the Specify UCM Configuration Options Screen.

This screen shows the progress of the Oracle UCM installation.

Click Next to continue.

10

Installation Completed Screen

Always

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

3 Configuring Oracle WebCenter

This chapter describes how to configure Oracle WebCenter after the components have already been installed.

The following topics are covered:

- Section 3.1, "Configuration Instructions"

- Section 3.2, "Working with Oracle WebCenter Components"

3.1 Configuration Instructions

After the installation is complete, you can configure the components using the Oracle Fusion Middleware Configuration Wizard.

If this is a new installation and you need to create a new domain, follow the instructions in Section 3.1.4, "Creating a New Domain". You can also run the Configuration Wizard to extend an existing domain, as described in Section 3.1.5, "Extending an Existing Domain".

If you need additional help with any of the configuration screens, refer to Appendix B, "Oracle WebCenter Configuration Screens" or click Help to access the online help.

3.1.1 Running the Configuration Wizard with an Oracle RAC Database

If you are running the Configuration Wizard with a backend Oracle RAC database, Oracle recommends that you keep all the RAC instances configured for the service to be up and running . This will ensure that JDBC validation checks are reliable and minimize the possibility of accidental mis-configuration.

For more information, refer to Oracle Fusion Middleware High Availability Guide.

3.1.2 Starting the Oracle Fusion Middleware Configuration Wizard

Start the Configuration Wizard from the WebCenter_ORACLE_HOME/common/bin (on UNIX operating systems) or WebCenter_ORACLE_HOME\common\bin (on Windows operating systems) directory.

On UNIX operating systems:

./config.sh

On Windows operating systems:

config.cmd

If this is a new installation and you need to create a new WebLogic domain, follow the instructions in Section 3.1.4, "Creating a New Domain". You can also run the Configuration Wizard to extend an existing WebLogic domain, as described in Section 3.1.5, "Extending an Existing Domain".

If you are using a 32-bit operating system, Oracle JRockit SDK is installed as part of the Oracle WebLogic installation (see Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home"). This is the JDK that the Configuration Wizard will use by default. If you want to invoke the Configuration Wizard with the Sun JDK, do the following prior to starting the Configuration Wizard:

1. Set the JAVA_HOME environment variable to the location of the Sun JDK. For example, you can set it to the Sun JDK that was installed with Oracle WebLogic Server in the MW_HOME/jdk160_14_R27.6.4-18 (on UNIX operating systems) or MW_HOME\jdk160_14_R27.6.4-18 (on Windows operating systems) directory.

2. Set the JAVA_VENDOR environment variable to "Sun."

3.1.3 Creating a Configuration Log File

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX operating systems:

./config.sh -log=log_filename

On Windows operating systems:

config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the WebCenter_ORACLE_HOME/common/bin (on UNIX operating systems) or WebCenter_ORACLE_HOME\common\bin (on Windows operating systems) directory.

3.1.4 Creating a New Domain

Follow the instructions in Table 3-1 to create a new domain.

Table 3-1 Configuration Flow for Creating a New Domain

No.

Screen

Description and Action Required

1

Welcome Screen

Select Create a new WebLogic Domain.

Click Next to continue.

2

Select Domain Source Screen

Select the components for which you want to create this domain.

Click Next to continue.

3

Specify Domain Name and Location Screen

Specify the name and location of the domain you are creating.

Click Next to continue.

4

Configure Administrator Username and Password Screen

Specify a user and password for the Administrator role.

NOTE - The domain administrator you create for Oracle WebCenter is also the administrator for WebCenter Spaces, Oracle WebCenter Discussions, and Oracle WebCenter Wiki and Blogs Server. You can choose to grant domain administrative rights for these WebCenter components to a different user. For information about granting the administrator role to a nondefault user for:

- WebCenter Spaces, see "Granting the WebCenter Spaces Administrator Role to a WebCenter Spaces User" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

- Oracle WebCenter Discussions, see "Granting Administrator Role for Oracle WebCenter Discussions Server" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

- Oracle WebCenter Wiki and Blog Server, see the "Managing Users and Roles" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Click Next to continue.

5

Configure Server Start Mode and JDK Screen

Select the WebLogic domain startup mode and the JDK to be used for the domain.

Click Next to continue.

6

Configure JDBC Component Schema Screen

Configure your JDBC component schema. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Click Next to continue.

7

Test Component Schema Screen

Test and verify the connections to your component schema.

Click Next to continue.

8

Select Optional Configuration Screen

Select the category or categories for which you want to make additional configuration changes (you may or may not see all of the following options, depending on your selections on the Select Domain Source Screen:

- If you select Administration Server, see Section 3.1.6.1, "Administration Server Options".

- If you select Managed Servers, Clusters and Machines, see Section 3.1.6.2, "Managed Servers, Clusters, and Machines Options".

- If you select Deployments and Services, see Section 3.1.6.3, "Deployments and Services Options".

- If you select JMS File Store, see Section 3.1.6.4, "JMS File Store Options".

- If you select RDBMS Security Store, see Section 3.1.6.5, "RDBMS Security Store Options".

If you choose not to select anything on this screen, skip to the Configuration Summary Screen.

Click Next to continue.

9

Configuration Summary Screen

Review the contents of your domain.

Click Create to continue.

10

Creating Domain Screen

Click Done when finished.

3.1.5 Extending an Existing Domain

While creating your WebCenter domain, if you chose not to configure any of the following components, you can add them later by extending your domain: Oracle WebCenter Spaces, Oracle WebCenter Portlets, Oracle WebCenter Discussion Server, and Oracle WebCenter Wiki and Blogs Server. If this is a first time configuration or you do not want to add more components, you can skip this section and move to the next section.

Follow the instructions in Table 3-2 to extend an existing domain.

Note:
Before proceeding, make sure that schemas exist in your database for the components you are configuring when you extend the domain. For example, if you are planning to extend the domain and configure Oracle WebCenter Discussion Server, then make sure the DISCUSSIONS schema exists in your Oracle database before you continue.

Table 3-2 Configuration Flow for Extending an Existing Domain

No.

Screen

Description and Action Required

1

Welcome Screen

Select Extend an exisitng WebLogic Domain.

Click Next to continue.

2

Select a WebLogic Domain Directory Screen

Select the WebLogic directory containing the domain you are extending.

Click Next to continue.

3

Select Extension Source Screen

Select the source from which this domain will be extended.

Click Next to continue.

4

Configure JDBC Component Schema Screen

Configure your JDBC component schema. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Click Next to continue.

5

Test Component Schema Screen

Test and verify the connections to your component schema.

Click Next to continue.

6

Select Optional Configuration Screen

Select the category or categories for which you want to make additional configuration changes (you may or may not see all of the following options, depending on your selections on the Select Extension Source Screen:

- If you select Administration Server, see Section 3.1.6.1, "Administration Server Options".

- If you select Managed Servers, Clusters and Machines, see Section 3.1.6.2, "Managed Servers, Clusters, and Machines Options".

- If you select Deployments and Services, see Section 3.1.6.3, "Deployments and Services Options".

- If you select JMS File Store, see Section 3.1.6.4, "JMS File Store Options".

- If you select RDBMS Security Store, see Section 3.1.6.5, "RDBMS Security Store Options".

If you choose not to select anything on this screen, skip to the Configuration Summary Screen.

Click Next to continue.

7

Configuration Summary Screen

Review the contents of your domain.

Click Extend to continue.

8

Creating Domain Screen

Click Done when finished.

3.1.6 Configuration Wizard Optional Configuration Screens

The Select Optional Configuration Screen gives you the following advanced configuration options:

- Administration Server Options

- Managed Servers, Clusters, and Machines Options

- Deployments and Services Options

- JMS File Store Options

- RDBMS Security Store Options

3.1.6.1 Administration Server Options

If you select Administration Server on the Select Optional Configuration Screen, you will see the Configure Administration Server Screen. This screen enables you to customize your Administration Server settings, such as the server name, port number, and secure connection settings.

3.1.6.2 Managed Servers, Clusters, and Machines Options

If you select Managed Servers, Clusters, and Machines on the Select Optional Configuration Screen, you will see the screens described in Table 3-3:

Table 3-3 Managed Servers, Clusters, and Machines Advanced Settings Screens

No.

Screen

Description and Action Required

1

Configure Managed Servers Screen

Add new managed servers, or edit and delete existing managed servers.

Click Next to continue.

2

Configure Clusters Screen

Create clusters if you are installing in a high availability environment. For more information, refer to Oracle Fusion Middleware High Availability Guide.

Click Next to continue.

3

Assign Servers to Clusters Screen

Assign your managed servers to a cluster in your domain.

Click Next to continue.

4

Create HTTP Proxy Applications Screen

Select whether or not you want a configure an HTTP proxy server for your cluster.

Click Next to continue.

5

Configure Machines Screen

Configure the machines that will host the managed servers.

Click Next to continue.

6

Assign Servers to Machines Screen

Assign each managed server to the machine on which it runs.

Click Next to continue.

3.1.6.3 Deployments and Services Options

If you select Deployments and Services on the Select Optional Configuration Screen, you will see the screens described in Table 3-4.

The Configuration Wizard automatically takes care of all necessary deployment and services targeting. You should not have to change anything on these screens unless specifically directed to do so. Typically, this will happen in an enterprise deployment configuration. For more information, see Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter.

Table 3-4 Deployments and Services Advanced Settings Screens

No.

Screen

Description and Action Required

1

Target Deployments to Servers or Clusters Screen

Target your deployments to servers or clusters.

Click Next to continue.

2

Target Services to Servers or Clusters Screen

Target your services to servers or clusters.

Click Next to continue.

3.1.6.4 JMS File Store Options

If you select JMS File Store on the Select Optional Configuration Screen, you will see the Configure JMS File Stores Screen. This screen enables you to configure the names, location, and write policy for your file stores.

3.1.6.5 RDBMS Security Store Options

If you select RDBMS Security Store on the Select Optional Configuration Screen, you will see the Configure RDBMS Security Store Database Screen. This screen enables you to configure an external relational database management system (RDBMS) as a data store for various security providers.

3.2 Working with Oracle WebCenter Components

After creating or extending a domain, you must configure Oracle WebCenter components to prepare them to work with Oracle WebCenter. Depending on the WebCenter component you want to use, perform the tasks listed in Table 3-5.

For information about configuring Oracle Content Server, see Section 4.3.1, "Oracle Content Server Requirements".

Table 3-5 Configuring Oracle WebCenter Components

Component

Task Description

Documentation

Oracle WebCenter Spaces

If you want to access WebCenter Spaces, first start the WLS_Spaces managed server. Then, access the following URL and log on as an administrator:

http://host:port/webcenter

Where, host:port refers to the host name and port number of the system where Oracle WebCenter is installed. By default, Oracle WebCenter is installed on port 8888.

For information about getting started with Oracle WebCenter Spaces, see the "Getting WebCenter Spaces Up and Running" chapter in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For more information about starting and stopping managed servers, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

Oracle WebCenter Portlets

To work with the preconfigured portlets available in Oracle WebCenter, you must:

1. Start the WLS_Portlet managed server.

2. Register the required portlet producers to enable application developers or users to add portlets to applciation pages.

If you want to access preconfigured portlets producer, use any of the following URLs depending on the portlet producer you wish to access:

- Rich Text portlet

http://host:port/richtextportlet/

- WSRP Tools

http://host:port/wsrp-tools/

- OmniPortlet and Web Clipping portlets

http://host:port/portalTools

Where, host:port refers to the host name and port number of the system where Oracle WebCenter Portlets is installed. By default, Oracle WebCenter Portlets is installed on port 8889.

For information about:

- Starting and stopping managed servers, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

- Registering, editing, deleting, and deploying portlet producers, see the "Managing Portlet Producers" chapter in Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Oracle WebCenter Discussions

To prepare Oracle WebCenter Discussions to work with Oracle WebCenter, perform the following tasks:

1. Start the managed server WLS_Services.

2. Configure Oracle WebCenter Discussions for Web Services Security (WS-Security) to prepare the server for custom WebCenter applications.

3. Register connections to Oracle WebCenter Discussions.

You can access Oracle WebCenter Discussions by using the following URL:

http://host:port/owc_discussions

Where, host:port refers to the host name and port number of the system where Oracle WebCenter Discussions is installed. By default, Oracle WebCenter Discussions is installed on port 8890.

Note: You cannot start or stop Oracle WebCenter Discussions from Oracle WebLogic Server Administrator Console. To start or stop the discussion server, you must start or stop the WLS_Services managed server where Oracle WebCenter Discussions is deployed.

For information about:

- Starting and stopping managed servers, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

- Configuring WS-Security, see the "Configuring the Discussions Server for a Simple Topology" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

- Registering connections, see the "Managing the Announcements and Discussions Services" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Oracle WebCenter Wiki and Blog Server

To prepare Oracle WebCenter Wiki and Blog Server to work with Oracle WebCenter, perform the following tasks:

1. Start the managed server WLS_Services.

2. Register connections to Oracle WebCenter Wiki and Blog Server.

You can access Oracle WebCenter Wiki and Blog Server by using the following URL format:

http://host:port/owc_wiki

Where, host:port refers to the host name and port number of the system where Oracle WebCenter Wiki and Blog Server is installed. By default, this server is installed on port 8890. The owc_wiki refers to the Oracle WebCenter Wiki and Blog Server deployment directory.

For information about:

- Starting and stopping managed servers, see "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

- Registering connections, see the "Managing the Wiki and Blog Services" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4 Preparing Back-End Components for WebCenter Services

Oracle WebCenter provides a set of WebCenter Services that expose social networking and personal productivity features for inclusion in custom WebCenter application, as well as use within the WebCenter Spaces application. Some of these services, such as Worklist and Search, rely on back-end components. This chapter describes the tasks required to install such back-end components and integrate them with Oracle WebCenter. The chapter also describes the tasks involved in configuring an external LDAP-based identity store.

This chapter includes the following sections:

- Section 4.1, "Introduction to WebCenter Services"

- Section 4.2, "Back-End Requirements for the Instant Messaging and Presence (IMP) Service"

- Section 4.3, "Back-End Requirements for Content Integration and the Documents Service"

- Section 4.4, "Back-End Requirements for the Mail Service"

- Section 4.5, "Back-End Requirements for the Search Service"

- Section 4.6, "Back-End Requirements for the Worklist Service"

- Section 4.7, "Back-End Requirements for WebCenter Spaces Workflows"

- Section 4.8, "Configuring an External LDAP-Based Identity Store"

4.1 Introduction to WebCenter Services

WebCenter Services help to create a dynamic and interactive environment for users through various services. These services can be integrated into WebCenter applications - both custom WebCenter applications and WebCenter Spaces applications. If a service relies on a back-end component, you must perform the following task to enable users to integrate that service into an application:

- Install the required back-end component

- Configure the back-end component, if required

- Set up a connection to the back-end component

Table 4-1 describes WebCenter Services and lists the back-end component, if any, required for each service.

Note:
Many of the WebCenter Services listed in Table 4-1 rely only on a database for their functionality, as opposed to a separate back-end product. To integrate such services into your WebCenter applications, you must ensure that a supported database is available with the required schemas. For information about:

- Supported databases, refer to the following link:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html

- Installing a database and creating schemas, see Chapter 2, "Installing Oracle WebCenter."

The Wiki and Blog services rely on Oracle WebCenter Wiki and Blog Server, and the Discussions and Announcements services rely on Oracle WebCenter Discussions. You can choose to install these servers either while installing Oracle WebCenter or later by extending your WebCenter domain. For information about:

- Installing these servers, see Chapter 3, "Configuring Oracle WebCenter."

- Configuring these servers, see Section 3.2, "Working with Oracle WebCenter Components."

Table 4-1 Back-End Requirements for WebCenter Services

Service

Description

Back-End Components Required

Announcements

Enables users to post, personalize, and manage announcements.

Oracle WebCenter Discussions and a supported database containing the MDS schema

Blog

Enables blogging functionality within the context of an application.

Oracle WebCenter Wiki and Blog Server

Discussions

Provides the ability to create and participate in threaded discussions

Oracle WebCenter Discussions and a supported database containing the MDS schema

Documents

Provides content management and storage capabilities, including content upload, file and folder creation and management, file check out, versioning, and so on.

A content repository such as Oracle Content Server 10.1.3.5.1 or Oracle Portal 11g, and a supported database containing the MDS schema

Note: For WebCenter Spaces, you must use Oracle Content Server as the default content repository.

Events

Provides group calendars through which users can schedule meetings, appointments, and any other type of team get-together.

Note: This service is available only in Oracle WebCenter Spaces.

A supported database containing MDS and WEBCENTER schemas

Instant Messaging and Presence (IMP)

Provides the ability to observe the online presence status of other authenticated users (whether online, offline, busy, or idle) and to contact them instantly.

Microsoft Live Communication Server 2005 and a supported database containing the MDS schema

Links

Provides the ability to view, access, and associate related information; for example, you can link to a solution document from a discussion thread.

A supported database, containing MDS and WEBCENTER schemas

Lists

Enables users to create, publish, and manage lists.

Note: This service is available only in Oracle WebCenter Spaces.

A supported database containing MDS and WEBCENTER schemas

Mail

Provides easy integration with IMAP and SMTP mail servers to enable users to perform simple mail functions such as viewing, reading, creating, and deleting messages, creating messages with attachments, and replying to or forwarding existing messages.

A mail server based on IMAP4 and SMTP, such as Microsoft Exchange Server 2003, and a supported database containing the MDS schema

Notes

Provides the ability to "jot down" and retain quick bits of personally relevant information.

Note: This service is available only in Oracle WebCenter Spaces.

A supported database containing MDS and WEBCENTER schemas

People Connections

Provides online social networking tools for creating, interacting with, and tracking the activities of one's enterprise connections.

A supported database containing MDS and WEBCENTER schemas

Recent Activities

Provides a summary view of recent changes to documents, discussions, and announcements.

A supported database containing the MDS schema

RSS

Provides the ability to publish content from other WebCenter Services and external sources as news feeds in RSS 2.0 and Atom 1.0 formats.

A supported database containing the MDS schema

Search

Provides the ability to search tags, services, an application, or an entire site. WebCenter searches can be extended to external content repositories by connecting WebCenter applications to Oracle Secure Enterprise Search (Oracle SES).

Oracle SES 10.1.8.2, updated with Oracle SES 10.1.8.3 and Oracle SES 10.1.8.4 patch sets, and a supported database containing the MDS schema

Tags

Provides the ability to assign one or more personally relevant keywords to a given page or document, making those items more easily discoverable in search results.

A supported database containing MDS and WEBCENTER schemas

Wiki

Provides the ability for geographically diverse teams to originate and collaborate on web documents.

Oracle WebCenter Wiki and Blog Server

Worklist

Provides a personal, at-a-glance view of business processes that require attention. These can include a request for document review and other types of business process that come directly from enterprise applications.

Business Process Execution Language (BPEL) server, and a supported database containing the MDS schema

4.2 Back-End Requirements for the Instant Messaging and Presence (IMP) Service

The Instant Messaging and Presence (IMP) service relies on a back-end communication server. Oracle WebCenter is certified with Microsoft Live Communications Server 2005, and can be integrated with SIP-based communication servers.

Note:
The IMP service can also be integrated with Oracle WebLogic Communications Services (OWLCS) 11g. However, OWLCS 11g is available for development and evaluation purpose only. You can download it from Oracle Technology Network (OTN) at:
http://www.oracle.com/technology/software/products/owlcs/index.html

This section contains the following subsections:

- Section 4.2.1, "Communication Server - Installation"

- Section 4.2.2, "Communication Server - Configuration and Integration"

4.2.1 Communication Server - Installation

For information about installing Microsoft Live Communications Server 2005, refer to the relevant Microsoft documentation. To use Microsoft Live Communications Server 2005 as the communication server for the IMP service, you must first deploy the Oracle RTC web services for Microsoft Live Communications Server 2005. For information, see the "LCS - Configuration" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

To use a SIP-based communication server, refer to its product documentation for server installation and configuration.

4.2.2 Communication Server - Configuration and Integration

If an LDAP-based identity store is not used for your Oracle WebCenter environment, then you must create WebCenter users on your communication server. For information about creating users on a communication server, refer to your communication server's product documentation.

After installing and configuring your communication server, you must set up connections to the communication server to enable IMP service integration into WebCenter applications. For information about how you can set up connections for the IMP service for WebCenter Spaces applications and any other WebCenter application deployed to a managed server, see the "Setting Up Connections for the Instant Messaging and Presence Service" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up connections for the IMP service within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Instant Messaging and Presence Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.3 Back-End Requirements for Content Integration and the Documents Service

The Documents service and content integration capabilities of Oracle WebCenter enable application developers to integrate content into their applications from local file systems and external content repositories. Oracle WebCenter supports content integration with the following external repositories:

- Oracle Content Server 10.1.3.5.1

- Oracle Portal 11g

Note:
You may configure WebCenter Spaces to use Oracle Content Server or Oracle Portal as external content repositories. However, WebCenter Spaces requires Oracle Content Server to be the default repository to enable the personal folder and group space folder functionality.

This section contains the following subsections:

- Section 4.3.1, "Oracle Content Server Requirements"

- Section 4.3.2, "Oracle Portal Installation"

4.3.1 Oracle Content Server Requirements

Table 4-2 describes the tasks that you must perform to use Oracle Content Server as an external repository for WebCenter applications.

Table 4-2 Tasks for Preparing Oracle Content Server as an External Repository

Task

Mandatory/Optional?

Documentation

1. Create the OCSERVER schema for Oracle Content Server

Mandatory

For information, see Section 4.3.1.1, "Oracle Content Server - Prerequisites."

2. Install Oracle HTTP Server

Mandatory

For information, see Section 4.3.1.1, "Oracle Content Server - Prerequisites."

3. Install Oracle Content Server

Mandatory

For information, see Section 4.3.1.2, "Oracle Content Server - Installation."

4. Configure Oracle Content Server to use an LDAP-based identity store

Mandatory

For information, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

5. Set up a connection to Oracle Content Server for your WebCenter applications

Mandatory

For information, see Section 4.3.1.4, "Oracle Content Server - Integration."

6. Configure Oracle Content Server to work with Oracle HTTP Server

Mandatory

For information, see Section 4.3.1.3, "Oracle Content Server - Configuration."

7. Enable full-text searching and indexing

Optional

For information, see the "Enabling Full-Text Searching and Indexing" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

8. Configure Secure Sockets Layer (SSL)

Optional

For information, see the "Configuring Secure Sockets Layer (SSL)" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

This section contains the following subsections:

- Section 4.3.1.1, "Oracle Content Server - Prerequisites"

- Section 4.3.1.2, "Oracle Content Server - Installation"

- Section 4.3.1.3, "Oracle Content Server - Configuration"

- Section 4.3.1.4, "Oracle Content Server - Integration"

4.3.1.1 Oracle Content Server - Prerequisites

Before installing Oracle Content Server, you must perform the following tasks:

- Create the OCSERVER schema for Oracle Content Server by using RCU. For information, see Section 2.1.3, "Create Schemas for Oracle WebCenter."

- Install Oracle HTTP Server. Oracle Content Server and Oracle HTTP Server must be installed on the same system. For information about installing Oracle HTTP Server, see the Oracle Fusion Middleware Installation Guide for Web Tier.

4.3.1.2 Oracle Content Server - Installation

You can install Oracle Content Server by using either of the following approaches:

- During Oracle WebCenter installation. Oracle Content Server installation is integrated with Oracle WebCenter installation. Therefore, you can choose to install Oracle Content Server 10.1.3.5.1 while installing Oracle WebCenter. For information, see Section 2.8, "Installing Oracle WebCenter."

- Through a standalone installation. You may want to choose this option if you need to install Oracle Content Server on a different system than the one on which Oracle WebCenter is installed.

To install Oracle Content Server separately:

1. Install Oracle Content Server 10.1.3.3.3 from the Oracle Universal Content Management (UCM) media shipped with Oracle WebCenter.
For information about the installation procedure, see the Content Server Installation Guide for Microsoft Windows or the Content Server Installation Guide for UNIX available here:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

2. Run the WebCenter configuration script, wc_contentserverconfig to upgrade Oracle Content Server 10.1.3.3.3 and prepare it to work with Oracle WebCenter. This script is available in the root directory of the UCM media shipped with Oracle WebCenter.
The wc_contentserverconfig configuration script installs the following:

- Oracle Content Server 10.1.3.5.1

- Folders_g 10.1.3.5.1 component

- WcConfigure component

The WcConfigure component performs the following tasks to configure Oracle Content Server for Oracle WebCenter:

- Sets configuration values for UseAccounts and IsAutoNumber to true and for AutoNumberPrefix to IDC_Name, if not set already.

- Updates, if necessary, the JDBC password and its encoding from ClearText to Intradoc.

- Adds the document type DOCUMENT.

- Configures folders so that dDocType and dSecurityGroup are inherited, and the system default information is set as follows: dDocType=DOCUMENT and dSecurityGroup=Public.

- Sets EnableIdcProfileField=1. This entry makes the server create a new metadata field named xIdcProfile and configure the field to use a view of profile trigger values called ProfileTriggerValues. The server then sets the profile trigger to the xIdcProfile metadata field, if not already set.

To run the wc_contentserverconfig WebCenter configuration script:

1. Navigate to the webcenter-conf directory, which is in the root directory of the UCM media shipped with Oracle WebCenter.

2. Run the following command:
On UNIX:

./wc_contentserverconfig.sh content_server_dir path_to_source_directory

Where, content_server_dir refers to the Oracle Content Server 10.1.3.3.3 installation directory and path_to_source_directory refers to the webcenter-conf directory on the UCM media.

For example:

./wc_contentserverconfig.sh /myproducts/ucm /myproducts/ucmmedia/webcenter-conf

On Windows:

wc_contentserverconfig.cmd content_server_dir path_to_source_directory

3. Restart Oracle Content Server Admin Server and Oracle Content Server.
On UNIX:

- To restart Admin Server: Run content_server_dir/admin/etc/idcadmin_restart

- To restart Oracle Content Server: Run content_server_dir/etc/idcserver_restart
Where, content_server_dir refers to the Oracle Content Server installation directory.

For information about how to start, stop, or restart Oracle Content Server, see the Content Server Installation Guide for UNIX available here:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

On Windows:

- To restart Admin Server: If Admin Server is running as a Windows service, you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and Services. Then, right-click the applicable IDC Content Admin Service service and choose Restart.

- To restart Oracle Content Server: If Oracle Content Server is running as a Windows service, you can restart the service by choosing Start, Settings, Control Panel, Administrative Tools, and Services. Then, right-click the applicable IDC Content Service service and choose Restart.
If Oracle Content Server is running as an application, you can restart the server by simply closing the Oracle Content Server window and starting it again.

For information about how to start, stop, or restart Oracle Content Server, see the Content Server Installation Guide for Microsoft Windows available here:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

4.3.1.3 Oracle Content Server - Configuration

If you choose to use Oracle Content Server as your external content repository, you must configure it with an LDAP-based identity store. For identity propagation, Oracle Content Server and Oracle WebCenter must use the same LDAP identity store. You can optionally configure Oracle Content Server for full-text search support. It is recommended that you use the OracleTextSearch option for enabling full-text search. To provide additional security for connections between WebCenter applications or components, you can enable Secure Sockets Layer (SSL) on Oracle Content Server.

For information about configuring Oracle Content Server, see the "Oracle Content Server - Configuration" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

You must configure Oracle Content Server to work with Oracle HTTP Server. Oracle HTTP Server configuration enables you to manage Oracle Content Server through a browser or add content on the server through WebDAV. This section describes how to configure Oracle Content Server to work with Oracle HTTP Server.

Note:
Oracle Content Server and Oracle HTTP Server must be installed on the same system.

To configure Oracle Content Server to work with Oracle HTTP Server:

1. Shut down Oracle Content Server and the Admin Server, if running:
To stop Oracle Content Server, run this command:

content_server_dir/etc/idcserver_stop

To stop the Admin Server, run this command:

content_server_dir/admin/etc/idcadmin_stop

2. In the config.cfg file, add the SocketHostAddressSecurityFilter entry, if not already present. The file is located in the content_server_dir/config directory. Set the entry to a pipe-delimited list of all hosts allowed to access Oracle Content Server.
For example:

SocketHostAddressSecurityFilter=127.0.0.1 | allowed_host_IP

Where: allowed_host_IP refers to IP addresses of all hosts allowed to connect to Oracle Content Server through a TCP socket port. This must include the network IP address of the server on which Oracle Content Server is installed.

3. Edit the content_server_dir/admin/bin/intradoc.cfg file to add the SocketHostAddressSecurityFilter entry if the entry is not there in the file. See step 2 for values of this entry.

4. Restart Oracle Content Server and Admin Server.

To configure Oracle HTTP Server for Oracle Content Server:

1. Open the httpd.conf file. This file is available at the following path:

OHS_ORACLE_HOME/instances/instance_name/config/OHS/ohs_name/httpd.conf

Where:

- OHS_ORACLE_HOME is the Oracle HTTP Server installation directory

- instance_name is the instance where Oracle HTTP Server is running

- ohs_name is the server name of Oracle HTTP Server

2. Add the following entry to the httpd.conf file of Oracle HTTP Server:
include content_server_dir/data/users/apache22/apache.conf

3. Restart Oracle Content Server.

4. Restart Oracle HTTP Server.
For example, you can use the following command:

OHS_ORACLE_HOME/instances/instance_name/bin/opmnctl stopall /opmnctl startall

4.3.1.4 Oracle Content Server - Integration

After configuring Oracle Content Server, you must set up content repository connections to the server to enable integration of the Documents service into your WebCenter applications. For information about how you can register content repositories and manage connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Managing Content Repositories" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up content repository connections within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Documents Service" and "Integrating Content" chapters in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.3.2 Oracle Portal Installation

Oracle Portal offers a complete and integrated framework for building, deploying, and managing enterprise portals.

This section contains the following subsections:

- Section 4.3.2.1, "Oracle Portal - Installation"

- Section 4.3.2.2, "Oracle Portal - Integration"

4.3.2.1 Oracle Portal - Installation

You must install Oracle Portal 11g to use it as a content repository for your Oracle WebCenter applications. For information about how to install Oracle Portal 11g, see Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.

4.3.2.2 Oracle Portal - Integration

After installing Oracle Portal, you must set up content repository connections to use Oracle Portal. For information about how you can register content repositories and manage connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Managing Content Repositories" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up content repository connections within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Documents Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.4 Back-End Requirements for the Mail Service

The Mail service relies on a mail server, such as Microsoft Exchange Server 2003, that supports IMAP4 and SMTP protocols. To install a mail server, refer to the documentation of the required product.

To enable WebCenter users to access the Mail service from within a WebCenter application, it is essential that users created on the mail server correspond with the users created in Oracle WebCenter's identity store. For information about adding users on a mail server, refer to the product documentation of your server. For more information about adding users to an identity store, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

After setting up a mail server, you must create a connection to it. For information about how you can register mail servers and set up connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Setting Up Connections for the Mail Service" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up connections for the Mail service within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Mail Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.5 Back-End Requirements for the Search Service

To search for content created by other WebCenter Services within Oracle WebCenter applications, the Search service does not require any separate back-end installation. However, you can extend WebCenter searches to include external content repositories by using Oracle Secure Enterprise Search (Oracle SES). Oracle SES provides a crawler-based service that can search a multitude of sources, structured and unstructured, in a variety of file formats, indexed or real-time.

This section contains the following subsections:

- Section 4.5.1, "Oracle SES - Installation"

- Section 4.5.2, "Oracle SES - Integration"

4.5.1 Oracle SES - Installation

To install Oracle SES:

1. Install Oracle SES 10.1.8.2.
For information about how to install Oracle SES 10.1.8.2, refer to the Oracle Secure Enterprise Online Documentation Library 10g Release 1 (10.1.8.2) available here on OTN:

http://www.oracle.com/technology/documentation/ses.html

2. Install the Oracle SES 10.1.8.4 patch set.
To do this, download the Automated Release Update (ARU) 10634423 from http://support.oracle.com.

3. Install the Oracle SES XML(RSS) Connector 10.1.8.4.3 patch set.
To do this, download the ARU 11876570 from http://support.oracle.com.

4.5.2 Oracle SES - Integration

After installing Oracle SES, you must create a connection to it. For information about how you can register Oracle SES connections for WebCenter Spaces and any other WebCenter application deployed to a managed server, see the "Setting Up Connections for the Search Service" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up connections for the Search service within Oracle JDeveloper and include Oracle SES search results in WebCenter search results, see the "Integrating the Search Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

4.6 Back-End Requirements for the Worklist Service

The Worklist service relies on a Business Process Execution Language (BPEL) server that is provided by Oracle SOA Suite.

To make the Worklist service available, you must install Oracle SOA Suite. For information about how to install Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite.

After installing Oracle SOA Suite, you must set up connections to the BPEL server to enable integration of the Worklist service into WebCenter applications. No further configuration is required on Oracle SOA or Oracle WebCenter. For information about how you can configure BPEL connections for WebCenter Spaces and custom WebCenter applications deployed to a managed server, see the "Setting Up Connections for the Worklist Service" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

For information about how developers can set up BPEL connections within Oracle JDeveloper while building and testing new custom WebCenter applications, see the "Integrating the Worklist Service" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

Note:
For WebCenter users to be able store and retrieve tasks from a BPEL server, it is essential that their user names exist in the identity stores used by WebCenter applications and the BPEL server. You can achieve this by creating identical user names in both the identity stores or by using a shared LDAP-based identity store for Single Sign-On (SSO) authentication.
SSO authentication enable users to log in once and seamlessly navigate between WebCenter applications and BPEL applications without having to log in to each application separately. For information about LDAP and SSO configuration, see the "Managing Security" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.7 Back-End Requirements for WebCenter Spaces Workflows

WebCenter Spaces provides several prebuilt workflows that handle group space membership notifications, group space subscription requests, and so on. WebCenter Spaces workflows rely on the BPEL server that is provided by Oracle SOA Suite. Table 4-3 describes the tasks that you must perform to enable workflow functionality in WebCenter Spaces.

Table 4-3 Tasks for Enabling WebCenter Spaces Workflows

Task

Mandatory/Optional?

Documentation

1. Install Oracle SOA Suite

Mandatory

For information, see Section 4.7.1, "Oracle SOA Suite - Installation."

2. Deploy WebCenter Spaces workflows to Oracle SOA by deploying sca_CommunityWorkflows.jar and WebCenterWorklistDetailApp.ear

Mandatory

For information, see Section 4.7.2, "Oracle SOA Server - Workflow Deployment."

3. Configure WS-Security to secure Web Service calls between Oracle SOA and Oracle WebCenter

Mandatory

For information, see Section 4.7.3, "Oracle SOA and Oracle WebCenter - WS-Security Configuration."

4. Register a connection with the BPEL server

Mandatory

For information, see Section 4.7.4, "Oracle WebCenter - BPEL Server Connection Setup."

Note:
For WebCenter users to be able store and retrieve tasks from a BPEL server, it is essential that their user names exist in the identity stores used by WebCenter applications and the BPEL server. You can achieve this by creating identical user names in both the identity stores or by using a shared LDAP-based identity store for Single Sign-On (SSO) authentication.
SSO authentication enables users to log in once and seamlessly navigate between WebCenter applications and BPEL applications without having to log in to each application separately. For information about LDAP and SSO configuration, see the "Managing Security" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

This section contains the following subsections:

- Section 4.7.1, "Oracle SOA Suite - Installation"

- Section 4.7.2, "Oracle SOA Server - Workflow Deployment"

- Section 4.7.3, "Oracle SOA and Oracle WebCenter - WS-Security Configuration"

- Section 4.7.4, "Oracle WebCenter - BPEL Server Connection Setup"

4.7.1 Oracle SOA Suite - Installation

To support workflows, WebCenter Spaces relies on the BPEL server included with Oracle SOA Suite. For information about how to install Oracle SOA Suite, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite.

4.7.2 Oracle SOA Server - Workflow Deployment

WebCenter Spaces workflows are deployed to an Oracle SOA server. To prepare a SOA server for workflows, you must deploy the following files to the server:

- sca_CommunityWorkflows.jar, this application contains the workflow logic that determines the task flows to be generated and API to be invoked. This composite is located at the following path in your Oracle SOA installation:
SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows.jar

Where, SOA_ORACLE_HOME refers to the Oracle SOA installation directory.

- WebCenterWorklistDetailApp.ear, this application contains task detail pages that provide the user interface elements for workflows. The application is located at the following path in your Oracle SOA installation:
SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear

4.7.2.1 Deploying sca_CommunityWorkflows.jar

You can deploy sca_CommunityWorkflows.jar by using any of the following methods based on your preference:

- Oracle WebLogic Scripting Tool (WLST)
For information, see the "Oracle SOA Suite Custom WLST Commands" chapter in the Oracle Fusion Middleware WebLogic Scripting Tool Command Reference.

- Ant
For information, see the "Deploying SOA Composite Applications" chapter in the Oracle Fusion Middleware Developer's Guide for Oracle SOA Suite.

- Oracle Enterprise Manager Fusion Middleware Control
This section describes how to deploy the JAR by using Fusion Middleware Control.

To deploy the sca_CommunityWorkflows.jar by using Fusion Middleware Control:

1. To start Fusion Middleware Control, enter the URL in the following format in your web browser:

http://host_name.domain_name:port_number/em

For example: http://myhost.example.com:7001/em

2. Enter the Oracle Fusion Middleware administrator user name and password and click Login.
Only the Fusion Middleware administrator can log on to Fusion Middleware Control. The default user name for the administrator user is weblogic. This is the account you can use to log on to Fusion Middleware Control for the first time.

3. Under WebLogic Domain in the navigation panel on left, right-click your SOA domain, select SOA Deployment, and then Deploy. (Figure 4-1)

Figure 4-1 Deploying the Composite to a SOA Managed Server

4. On the Select Archive page, enter the path to sca_CommunityWorkflows.jar. (Figure 4-2)
You can find this application at the following location in your Oracle SOA installation:

SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_CommunityWorkflows.jar

Figure 4-2 Deploying the Composite - Select Archive Page

5. Click Next.

6. On the Select Target page, select the Managed Server to which you want to deploy the SOA composite application. (Figure 4-3)

Figure 4-3 Deploying the Composite - Select Target Page

7. Click Next.

8. On the Confirmation page, select Deploy as default revision. (Figure 4-4)

Figure 4-4 Deploying the Composite - Confirmation Page

9. Click Deploy.
After the composite is successfully deployed, it is listed under your Oracle SOA Managed Server. (Figure 4-5)

Figure 4-5 Composite Deployed to an Oracle SOA Managed Server

For more information about deploying, redeploying, and undeploying SOA applications, see the "Deploying SOA Composite Applications" chapter in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

4.7.2.2 Deploying WebCenterWorklistDetailApp.ear

To deploy the WebCenterWorklistDetailApp.ear application, you can either use WLST or Fusion Middleware Control.

For information about deploying Java EE applications by using WLST, see the "Deploying Applications" chapter in the Oracle Fusion Middleware Administrator's Guide.

To deploy WebCenterWorklistDetailApp.ear by using Fusion Middleware Control:

1. Log on to Fusion Middleware Control as an administrator.

2. Under WebLogic Domain, right-click the SOA domain, select Application Deployment, and then select Deploy.

3. On the Select Archive page, enter the path to WebCenterWorklistDetailApp.ear. (Figure 4-6)
You can find the application at the following location in your Oracle SOA installation:

SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear

Figure 4-6 Specifying the Path to WebCenterWorklistDetailApp.ear

4. On the Select Target page, select the Oracle SOA managed server to which you want to deploy the application. (Figure 4-7)

Figure 4-7 Selecting Target Server

5. Click Next.

6. On the Application Attributes page, click Next. (Figure 4-8)

Figure 4-8 Specifying Application Attributes

7. On the Deployment Settings page, click Deploy. (Figure 4-9)

Figure 4-9 Deploying WebCenterWorklistDetailApp.ear

After the composite is successfully deployed, a confirmation message is displayed and the application is shown in the Application Deployments tab in Fusion Middleware Control.

Figure 4-10 Deployed EAR Application

4.7.3 Oracle SOA and Oracle WebCenter - WS-Security Configuration

WebCenter Spaces Web services, deployed to Oracle WebCenter, facilitate communication between WebCenter Spaces and the SOA server. You must secure these Web service calls. To do this, set up WS-Security on the SOA server and WebCenter Spaces.

For information, see the "Configuring WS-Security" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.7.4 Oracle WebCenter - BPEL Server Connection Setup

If you want to use WebCenter Spaces workflows, you must create a connection to the BPEL server provided by Oracle SOA Suite.

To configure a connection for WebCenter Spaces workflows:

1. Register a BPEL server connection with the SOA server instance on which WebCenter Spaces workflows are deployed. For information, see the "Registering Worklist Connections" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Note:
You can configure the Worklist service and WebCenter Spaces workflows to either share the same BPEL server connection or use separate connections.
In Oracle Enterprise Manager Fusion Middleware Control, you register a BPEL server connection by adding a Worklist connection. By default, this connection is configured to be used both by the Worklist service and the WebCenter Spaces application. There is no separate option available for adding a BPEL server connection for WebCenter Spaces.

2. Select the BPEL server connection for WebCenter Spaces workflows in WebCenter Spaces. For information, see the "Specifying the BPEL Server Hosting WebCenter Spaces Workflows" sections in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

4.8 Configuring an External LDAP-Based Identity Store

By default, WebCenter applications use Oracle WebLogic Server's embedded LDAP identity store for storing user accounts and groups, and an XML file-based policy store for storing policy grants. Although secure, the embedded LDAP identity store is not a "production-class" store and should be replaced with an external LDAP-based identity store, such as Oracle Internet Directory, for enterprise production environments. Further, the default XML file-based policy store can be used only for single-node WebCenter configurations. For multi-node configurations, you must reassociate the policy and credential store with an external LDAP-based identity store.

Table 4-4 describes the tasks that you must perform to configure an external LDAP-based identity store for Oracle WebCenter.

Table 4-4 Tasks for Configuring an External LDAP-Based Identity Store

Task

Description

Mandatory/Optional?

1. Install an external LDAP-based identity store

Install an external LDAP-based identity store such as Oracle Internet Directory.

For information about how to install Oracle Identity Management, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

Mandatory

2. Configure Oracle WebCenter identity store to use the external LDAP

Reassociate the identity store with an external LDAP, rather than the default embedded LDAP.

For information, see the "Configuring the Identity Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Mandatory

3. Configure the policy and credential stores

Reassociate Oracle WebCenter's policy store and credential store with an external LDAP.

For information, see the "Configuring the Policy and Credential Store" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Mandatory

You can configure WebCenter Spaces as well as WebCenter Services back-ends to use a shared external LDAP-based identity store. If you wish to configure a shared external LDAP-based identify store, perform the tasks listed in Table 4-4, then those listed in Table 4-5.

Note:
If you want to configure a shared external LDAP-based identity store, then WebCenter Spaces applications and all the back-end components configured for your WebCenter Services must use the same external LDAP-based identity store.

Table 4-5 lists the back-end components for various WebCenter Services and specifies the out-of-the-box identity store support available for these components. Table 4-5 also describes whether additional configuration is required for any back-end component if a shared external LDAP-based identity store is used.

Table 4-5 Configuring Back-End Components for a Shared External LDAP-Based Identity Store

Back-End Component

Out-Of-The-Box Support

Additional Configuration Requirement

Oracle WebCenter Discussions

Embedded LDAP store

No additional configuration required.

Oracle WebCenter Wiki and Blog Server

Embedded LDAP store

No additional configuration required.

Oracle Content Server

Database

Configure the Oracle Content Server to use the same external LDAP-based identity store as Oracle WebCenter.

For information, see the "Oracle Content Server - Configuration" section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

Oracle SES

None

Configure Oracle SES to use the same external LDAP-based identity store as Oracle WebCenter.

For information about configuring LDAP in Oracle SES, see the "Security in Oracle Secure Enterprise Search" chapter in the Oracle Secure Enterprise Search Administrator's Guide. This guide is available in the Oracle Secure Enterprise Search Online Documentation Library 10g Release 1 (10.1.8.2) available here on OTN:

http://www.oracle.com/technology/documentation/ses.html

Oracle SOA Suite (BPEL server)

Embedded LDAP store

Configure Oracle SOA Suite to use the same external LDAP-based identity store as Oracle WebCenter. For information about:

- Configuring LDAP authentication providers, see the "Configuring Authentication Providers" chapter in the Oracle Fusion Middleware Securing Oracle WebLogic Server.

- Listing Oracle Internet Directory as the first authentication provider, see the "Listing Oracle Internet Directory as the First Authentication Provider" section in the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.

5 Deinstalling Oracle WebCenter

This section describes how to remove Oracle WebCenter and related products from your system.

You should always use the instructions provided in this chapter for removing the software. If you try to remove the software manually, you may experience problems when you try to reinstall the software again at a later time. Following the procedures in this section will ensure that the software is properly removed.

The following topics are covered:

- Section 5.1, "Deinstallation Instructions"

- Section 5.2, "Reinstallation"

5.1 Deinstallation Instructions

Follow the instructions in this section to remove Oracle WebCenter and related software from your system. The following tasks should be completed:

- Stopping Oracle Fusion Middleware

- Removing Oracle WebCenter Schemas

- Removing Oracle Universal Content Management

- Removing Oracle WebCenter

- Removing Oracle WebLogic Server

- Removing Oracle JDeveloper

- Removing the Program Groups (Windows Only)

5.1.1 Stopping Oracle Fusion Middleware

Before deinstalling Oracle Fusion Middleware software components, you should stop all servers and processes.

1. Stop the WebLogic Managed Servers.
On UNIX operating systems:

MW_HOME/user_projects/domains/domain_name/bin/stopManagedWeblogic.sh managed_server_nanme admin_url username password

On Windows operating systems:

MW_HOME\user_projects\domains\domain_name\bin\stopManagedWeblogic.cmd managed_server_nanme admin_url username password

2. Stop WebLogic Administration Server.
On UNIX operating systems:

MW_HOME/user_projects/domains/domain_name/bin/stopWeblogic.sh username password admin_url

On Windows operating systems:

MW_HOME\user_projects\domains\domain_name\bin\stopWeblogic.cmd username password admin_url

For both commands, specify the admin_url using the following format:

http://admin_server_host.admin_server_domain:admin_server_port

For more information about starting and stopping Oracle Fusion Middleware, refer to "Starting and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's Guide.

5.1.2 Removing Oracle WebCenter Schemas

Run the Repository Creation Utility (RCU) to drop the WebCenter schemas from your database.

5.1.2.1 Starting RCU

Insert the RCU CD-ROM and start RCU from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory:

On UNIX operating systems:

./rcu

On Windows operating systems:

rcu.bat

If you download the RCU .zip file from OTN, then you can also start RCU as shown above from the rcuHome/bin (on UNIX operating systems) or rcuHome\bin (on Windows operating systems) directory on your system.

5.1.2.2 Instructions for Dropping the WebCenter Schemas

Follow the instructions below to drop the WebCenter schemas:

1. Welcome Screen
Click Next.

2. Create Repository Screen
Select Drop.

Click Next.

3. Database Connection Details Screen
Provide the following credentials to connect to your Oracle database. These are the same credentials you provided on this screen when you created the WebCenter schemas. See Section 2.1.3, "Create Schemas for Oracle WebCenter" for more information.

Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Database Connection Details Screen. Fix the error messages and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

4. Select Components Screen
Select the prefix and schemas you want to drop from the repository.

Click Next. A "Checking Prerequisites" screen will appear. If there are errors, some details about the error will be displayed on the Select Components Screen. Fix the error messages and click Next again.

After the checking is complete with no errors, click OK to dismiss the screen.

5. Summary Screen
Click Drop. A "DROP" screen will appear. If there are errors, some details about the error will be displayed on the Summary Screen. Fix the error messages and click Next again.

After the schemas are dropped with no errors, click OK to dismiss the screen.

6. Completion Summary Screen
Click Close.

5.1.3 Removing Oracle Universal Content Management

If you installed Oracle UCM as part of the Oracle WebCenter installation, then you can skip this section.

If you installed Oracle UCM separately from the Oracle WebCenter installation, you must first remove this software separately from the Oracle WebCenter software before you remove Oracle WebCenter. Instructions for doing so can be found in Content Server Installation Guide for Microsoft Windows and Content Server Installation Guide for UNIX at the following URL:

http://download.oracle.com/docs/cd/E10316_01/owc.htm

After you remove Oracle UCM, you can them proceed with the deinstallation of Oracle WebCenter.

5.1.4 Removing Oracle WebCenter

Deinstalling Oracle WebCenter involves removing the WebCenter Oracle Home and the Oracle Common Home directories.

The deinstaller will attempt to remove the Oracle Home from which it was started. This procedure will not remove any WebLogic domains that you have created - it only removes the software in the Oracle Home.

Before you choose to remove any Oracle Home, make sure that it is not in use by an existing domain, and also make sure you stop all running processes that use this Oracle Home. After you remove the software, you will no longer be able to use your WebLogic domain.

5.1.4.1 Removing the WebCenter Oracle Home

To start the deinstaller, navigate to the WebCenter_ORACLE_HOME/oui/bin (on UNIX operating systems) or WebCenter_ORACLE_HOME\oui\bin (on Windows operating systems) directory and start the deinstaller.

On UNIX operating systems:

./runInstaller.sh -deinstall -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -deinstall -jreLoc JRE_LOCATION

Note:
Specify the absolute path to your JRE_LOCATION; relative paths are not supported.

Follow the instructions in Table 5-1 to deinstall Oracle WebCenter.

If you need additional help with any of the deinstallation screens, refer to Appendix C, "Oracle WebCenter Deinstallation Screens" or click Help to access the online help.

Table 5-1 Deinstallation Flow

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Deinstall Oracle Home Screen

Verify the Oracle Home you are about to deinstall.

Click Deinstall to continue.

3

Deinstall Progress Screen

This screen shows the progress and status of the deinstallation.

4

Deinstall Completed Screen

Click Finish to dismiss the screen.

After this is done, you must manually remove the WebCenter Oracle Home directory and all sub-directories. For example, if your WebCenter Oracle Home directory was /home/Oracle/Middleware/Oracle_WC1 on a UNIX operating system:

> cd /home/Oracle/Middleware
> rm -rf Oracle_WC1

On a Windows operating system, if your WebCenter Oracle Home directory was C:\Oracle\Middleware\Oracle_WC1, use a file manager window and navigate to the C:\Oracle\Middleware directory, then right-click on the Oracle_WC1 folder and select Delete.

5.1.4.2 Removing the Oracle Common Home

This section describes how to remove the oracle_common directory. This directory contains its own deinstaller in oui/bin (on UNIX operating systems) or oui\bin (on Windows operating systems), just like any other Oracle Home directory.

To start the deinstaller, navigate to the MW_HOME/oracle_common/oui/bin (on UNIX operating systems) or MW_HOME\oracle_common\oui\bin (on Windows operating systems) directory and start the deinstaller.

On UNIX operating systems:

./runInstaller -deinstall -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -deinstall -jreLoc JRE_LOCATION

Note:
Specify the absolute path to your JRE_LOCATION; relative paths are not supported.

After the deinstaller is started, follow the instructions in Table 5-1 to remove the Oracle Common Home.

5.1.5 Removing Oracle WebLogic Server

To remove Oracle WebLogic Server:

1. Start the deinstaller from the WebLogic_Home/uninstall (on UNIX operating systems) or WebLogic_Home\uninstall (on Windows operating systems) directory. You specified the location of the WebLogic Home directory on the Choose Product Installation Directories Screen in Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home".
On UNIX systems:

./uninstall.sh

On Windows systems:

uninstall.cmd

On Windows systems, you can also start the deinstaller from the Start menu by selecting Programs > Oracle WebLogic > Uninstall Oracle WebLogic.

2. Welcome Screen
Click Next.

3. Choose Components Screen
By default, all components are selected.

Click Next.

4. Uninstalling WebLogic Platform Screen
Click Done.

After this is done, you must manually remove the Middleware Home directory and all sub-directories. For example, if your Middleware Home directory was /home/Oracle/Middleware on a UNIX operating system:

> cd /home/Oracle
> rm -rf Middleware

On a Windows operating system, if your Middleware Home directory was C:\Oracle\Middleware, use a file manager window and navigate to the C:\Oracle directory, then right-click on the Middleware folder and select Delete.

5.1.6 Removing Oracle JDeveloper

If you have installed Oracle JDeveloper on your system, refer to Oracle Fusion Middleware Installation Guide for Oracle JDeveloper for instructions on how to remove this software from your system.

5.1.7 Removing the Program Groups (Windows Only)

On Windows systems, you must also manually remove the program groups from the Start Menu\Programs folder. As an example (the folder names and program group names on your system may be different), you might remove the following from C:\Documents and Settings\All Users\Start Menu\Programs:

- Oracle Fusion Middleware 11.1.1.2.0

- Oracle WebCenter 11g - Home1

- Oracle WebLogic

5.2 Reinstallation

The installer does not allow reinstallation of an Oracle WebCenter instance in a directory that already contains an Oracle WebCenter instance. To reinstall Oracle WebCenter in the same directory, you have to deinstall and then install it.

A Oracle WebCenter Installation Screens

This appendix contains screenshots and descriptions for all of the Oracle WebCenter installation screens:

- Specify Inventory Directory Screen (UNIX Only)

- Inventory Location Confirmation Screen (UNIX Only)

- Welcome Screen

- Prerequisite Checks Screen

- Specify Installation Location Screen

- Specify UCM Configuration Options Screen

- Specify UCM Database Details Screen

- Installation Summary Screen

- Installation Progress Screen

- Specify UCM Installer Directory Screen

- UCM Installation Progress Screen

- Installation Completed Screen

Installation screens and instructions for WebCenter back-end components can be found in Chapter 4, "Preparing Back-End Components for WebCenter Services".

A.1 Specify Inventory Directory Screen (UNIX Only)

This screen appears for UNIX systems only; if this is your first Oracle installation on this host, you must specify the location of the inventory directory. This inventory directory is used by the installer to keep track of all Oracle products installed on the computer.

The default inventory location is User_Home/oraInventory.

In the Operating System Group name field, select the group whose members you want to grant access to the inventory directory; all members of this group will be able to install products on this machine.

A.2 Inventory Location Confirmation Screen (UNIX Only)

This screen appears for UNIX systems only; you are asked to run the inventory_directory/createCentralInventory.sh script as root.

If you do not have root access on this machine but wish to continue with the installation, select Continue installation with local inventory.

A.3 Welcome Screen

The Welcome screen is displayed each time you start the installer.

A.4 Prerequisite Checks Screen

If there is a problem, a short error message appears in the bottom portion of the screen. Fix the error and click Retry to try again.

If you want to ignore the error or warning messages and continue with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

A.5 Specify Installation Location Screen

In the Oracle Middleware Home field, specify the absolute path to your existing Oracle Middleware Home directory. If you do not know the full path to your Middleware Home, you can click Browse to select an existing directory in your system.

In the Oracle Home Directory field, specify the directory inside the Oracle Middleware Home where you want to install your products:

- If you specify a directory that already exists, it must be either:

- An empty directory inside the Oracle Middleware Home (for example, you have created an empty directory inside the Middleware Home in advance of this installation and should specify this directory here).

- An existing Oracle Home directory (for example, you are adding Oracle Universal Content Management to an existing WebCenter Oracle Home directory).

- If you specify a new directory, it will be created inside the Oracle Middleware Home.

If you are performing an installation on a Windows operating system, be sure that your directory paths are valid and do not contain double backslashes (\\).

The Oracle Home directory is where your products will be installed. All software binaries will reside in this directory, and no runtime process can write to this directory.

Note:
For the remainder of this document, this directory will be referred to as your WebCenter Oracle Home to avoid any confusion with the Oracle Home directories of other Oracle Fusion Middleware products. For more information about Oracle Home directories, refer to "Oracle Home Directory" in Oracle Fusion Middleware Installation Planning Guide.

A.6 Specify UCM Configuration Options Screen

Select Install and Configure Oracle Universal Content Management if you want to install Oracle UCM.

Note:
If you are using a Microsoft SQL Server database, do not select Install and Configure Oracle Universal Content Management on this screen. Oracle UCM can be configured to run on SQL Server, but should be installed separately.

Note:
By default, version 10g (10.1.3.5.1) is installed on your system. If you already have a previous version of Oracle UCM installed on your system, you must apply the patch tp upgrade to version 10.1.3.5.1 in order to get Oracle UCM working with Oracle WebCenter.

Specify the following information:

- Content Server Port
The Content Server comes as part of Oracle UCM and performs content management tasks. Enter the port number that will be used to connect to the Content Server. The default is 4444.

- Content Server Admin Port
Oracle UCM also comes with an Administration Server that handles administrative tasks. Enter the port number that will be used to connect to the Administration Server. The default is 4440.

- Web Server HTTP Address
Oracle UCM must also be installed on a machine with an existing HTTP server. The web server address is the URL used to access Content Server, including the relative root specific to Content Server. For example, if you install Content Server on a web server with the HTTP address of http://www.yourcompany.com and you want to use ucm as the relative root, you would specify http://www.yourcompany.com/ucm/ as the HTTP address in this field. The address must be in the format:

http://host:port/webroot

For secure connections:

https://host:ssl_port/webroot

A.7 Specify UCM Database Details Screen

Specify the connection details to your Oracle database containing the OCSERVER schema:

- Database Connect String
Enter the hostname, port number, and service name of your Oracle database. Use the following format:

host.port.servicename

Note:
Support for Oracle RAC databases is not available out-of-the-box. You must configure your Oracle RAC database after Oracle UCM is installed.
Refer to "Reconfiguring the Content Server to Support RAC" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter for more information.

The default port number for Oracle Databases is 1521.

The service name is typically 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 DB_NAME and DB_DOMAIN parameters.

- Schema Username
Enter the name of your Content Server schema in the following format:

prefix_schemaname

You would have provided this information on the Select Components Screen when creating your schemas using Repository Creation Utility (RCU). For more information, refer to Section 2.1.3, "Create Schemas for Oracle WebCenter".

- Schema Password
Enter the password for your schema. You would have provided this information on the Schema Passwords Screen when creating your schemas using Repository Creation Utility (RCU). For more information, refer to Section 2.1.3, "Create Schemas for Oracle WebCenter".

A.8 Installation Summary Screen

Review the information on this screen, and click Install to begin the installation. The operations summarized on this page will be performed when you click Install.

If you want to make any changes to the configuration before starting the installation, use the navigation pane and select the topic you want to edit.

If you want to save this configuration to a text file, click Save. This file can be used later if you choose to perform the same installation from the command line. See Appendix D, "Silent Installation" for more information.

A.9 Installation Progress Screen

This screen shows you the progress of the installation.

If you want to quit before the installation is completed, click Cancel. Doing so will result in a partial installation; the portion of the software that was installed on your system before you click Cancel will remain on your system, and you will have to remove it manually.

A.10 Specify UCM Installer Directory Screen

Provide the location of the Oracle UCM installer. This is the directory under which the install/UCM/ContentServer/platform (on UNIX systems) or install\UCM\ContentServer\platform (on Windows systems) exists.

On UNIX systems, this directory is typically products/ContentServer on the installation DVD. If you extracted the contents of the installation DVD to your local disk, then you should point to products/ContentServer in the directory on your disk where you extracted the software. For example:

/tmp/webcenter/install/products/ContentServer

On Windows systems, this directory is typically products\ContentServer on the installation DVD. If you extracted the contents of the installation DVD to your local disk, then you should point to products\ContentServer in the directory on your disk where you extracted the software. For example:

C:\TMP\Install\products\ContentServer

Note:
For this location, you cannot specify a Universal Naming Convention (UNC) path, such as \\server\content\ContentServer.
Instead, you must map this network path to a drive, and then provide the mapped drive as the installation location. For example, using either the NET SHARE command or Tools > Map Network Drive from Windows Explorer, you could map the M:\ drive to the \\server\content directory, then provide the installation location as M:\ContentServer.

A.11 UCM Installation Progress Screen

This screen shows you the progress of the Oracle UCM installation.

If you want to quit before the installation is completed, click Cancel. Doing so will result in a partial installation; the portion of the software that was installed on your system before you click Cancel will remain on your system, and you will have to remove it manually.

A.12 Installation Completed Screen

This screen summarizes the installation that was just completed.

If you want to save this summary information to a text file for future reference, click Save.

B Oracle WebCenter Configuration Screens

This appendix contains screenshots and descriptions for all of the Oracle WebCenter configuration screens:

- Welcome Screen

- Select a WebLogic Domain Directory Screen

- Select Domain Source Screen

- Select Extension Source Screen

- Specify Domain Name and Location Screen

- Configure Administrator Username and Password Screen

- Configure Server Start Mode and JDK Screen

- Configure JDBC Component Schema Screen

- Test Component Schema Screen

- Select Optional Configuration Screen

- Configure Administration Server Screen

- Configure Managed Servers Screen

- Configure Clusters Screen

- Assign Servers to Clusters Screen

- Create HTTP Proxy Applications Screen

- Configure Machines Screen

- Assign Servers to Machines Screen

- Target Deployments to Servers or Clusters Screen

- Target Services to Servers or Clusters Screen

- Configure RDBMS Security Store Database Screen

- Configuration Summary Screen

- Creating Domain Screen

- Extending Domain Screen

B.1 Welcome Screen

The Welcome screen is displayed each time you start the Configuration Wizard.

Select Create a new WebLogic domain to create a new WebLogic domain in your projects directory.

Select Extend an existing WebLogic domain if you want to add applications and services, or to override existing database access (JDBC) and messaging (JMS) settings.

B.2 Select a WebLogic Domain Directory Screen

This screen only appears if selected Extend an existing WebLogic domain on the Welcome Screen.

Select the WebLogic directory containing the domain you are extending.

B.3 Select Domain Source Screen

This screen only appears if selected Create a new WebLogic domain on the Welcome Screen.

Select the source from which you want to create your new domain.

Select Generate a domain configured automatically to support the following products to create your domain to support selected products. Then, select the products for which you want support.

Select Base this domain on an existing template to create your domain based on an existing domain template. Click Browse to navigate your directories to find an existing template.

B.4 Select Extension Source Screen

This screen only appears if selected Extend an existing WebLogic domain on the Welcome Screen.

Select the source from which you want to extend your domain.

Select Extend my domain automatically to support the following added products to extend your domain to support selected products. Then, select the products for which you want support.

Select Extend my domain using an existing extension template to extend your domain based on an existing extension template. Click Browse to navigate your directories to find an existing template.

B.5 Specify Domain Name and Location Screen

Specify the following information for the domain you are creating:

- Domain name
The name of the domain you want to create. The default name is base_domain.

- Domain Location
The absolute path to the directory where this domain should be created. The default location is MW_HOME/user_projects/domains (on UNIX operating systems) or MW_HOME\user_projects\domains (on Windows operating systems).

Note:
On Windows machines, be sure to include the drive letter when you specify the domain location.

- Application Location
The absolute path to the directory where applications created in this domain should reside. The default location is MW_HOME/user_projects/applications (on UNIX operating systems) or MW_HOME\user_projects\applications (on Windows operating systems).

Note:
On Windows machines, be sure to include the drive letter when you specify the application location.

B.6 Configure Administrator Username and Password Screen

Create a user that will be assigned to the Administrator role. This user is the default administrator used to start development mode servers.

Note:
The domain administrator you create for Oracle WebCenter is also the administrator for WebCenter Spaces, Oracle WebCenter Discussions, and Oracle WebCenter Wiki and Blogs Server. You can choose to grant domain administrative rights for these WebCenter components to a different user. For information about granting the administrator role to a nondefault user for:

- WebCenter Spaces, see "Granting the WebCenter Spaces Administrator Role to a WebCenter Spaces User" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

- Oracle WebCenter Discussions, see "Granting Administrator Role for Oracle WebCenter Discussions Server" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

- User name
Specify the administrator name. The default name is weblogic.

- User password
Specify the password for the administrator. The password must be at least eight characters long and contain at least one number.

- Confirm user password
Re-enter the administrator password.

- Description
Enter a description for the user. This field is optional.

B.7 Configure Server Start Mode and JDK Screen

In the WebLogic Domain Startup Mode section, select one of the following startup modes:

- Development Mode
Development mode should be used while you are developing your applications. Development mode uses a relaxed security configuration and enables you to auto-deploy applications. In this mode, boot.properties is used for username and passwords and polling is used for application deployment.

- Production Mode
Production mode shouldbe used when your application is running in its final form. A production domain uses full security and may use clusters or other advanced features. In this mode, usernames and passwords are required and polling is not used for application deployment.

In the JDK Selection section, select the recommended JDK for your startup mode from the list of available JDKs, or select Other JDK and click Browse to find another JDK on your system. The recommended JDKs are described in the text for each mode in the WebLogic Domain Startup Mode section.

B.8 Configure JDBC Component Schema Screen

Configure the schema owner and password for each component schema listed on this screen. Changes to any of the fields on this screen are applied to all selected component schema in the table.

For example, if all of your schemas reside on the same database, select all of the schemas in the table, then specify the appropriate database values for the schemas (DBMS/Service, Host Name, and Port).

If, for example, you hare a different password for each schema, then you must select each schema individually and specify the password for the selected schema only.

Review the table on this screen and identify which fields you need to modify:

- Vendor
Select the vendor for your database from the drop-down list.

- Driver
Select the driver type from the drop-down list.

- Schema Owner
Specify the schema owner for the schema. This schema owner was assigned when you created the schema using RCU.

- Password
Specify the password for the schema. You specified this password when creating the schema using RCU.

- DBMS/Service
Specify the service name for your database. This is the database on which the schema resides.

- Host Name
Specify the name of the machine where your database is running.

- Port
Specify the database listen port number.

B.9 Test Component Schema Screen

Verify that the connections to your data sources are successful.

B.10 Select Optional Configuration Screen

Select any category for which you want to perform custom or advanced configuration. Note that selection of any of these categories is optional, and your domain will be created or extended if you choose not to customize any of these categories.

- Administration Server
Select this to edit your Administration Server settings. You will be able to:

- Change the name of your Administration Server (default is AdminServer).

- Specify custom port numbers.

- Configure the Administration Server to accept SSL connections.

- Managed Servers, Clusters and Machines
Select this to add or delete managed servers, clusters, and machines. You can also modify the settings of any existing server, cluster, or machine.

For more information about these concepts, refer to "Oracle Fusion Middleware Concepts for All Users" in Oracle Fusion Middleware Installation Planning Guide.

- Deployments and Services
Select this to customize how deployments and services are targeted to machines and clusters.

Typically, these screens do not need to be modified unless specifically told to do so. For more information, refer to Oracle Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter.

- JMS File Store
Select this to customize your JMS file store settings.

- RDBMS Security Store
Select this if you want to configure an external relational database management system (RDBMS) as a data store for various security providers.

B.11 Configure Administration Server Screen

The Administration Server is the primary tool used to manage a WebLogic Server domain.

One WebLogic Server instance in each domain is configured as the Administration Server. If you have multiple WebLogic Server instances, then all the other instances are referred to as Managed Servers. In a domain with only one WebLogic Server instance, that instance functions both as Administration Server and Managed Server.

- Name
Specify the name of your Administration Server. The default name is AdminServer.

- Listen Address
Use the drop-down list to select an address or range of addresses that the Administration Server will listen to for events. The default selection is All Local Addresses.

- Listen Port
Specify the listen port number. The default port number is 7001.

Select SSL enabled if you want your Administration Server to accept SSL connections. Be sure to specify the SSL Listen Port if you select the SSL enabled option.

B.12 Configure Managed Servers Screen

A managed server is an instance of WebLogic Server used to host enterprise applications. A typical production environment has at least one managed server, which is managed by the Administration Server.

Use this screen to add or delete managed servers; click Add to add a managed server. To delete a managed server, select the server name and click Delete.

Note:
Deleting one of the default managed servers (WLS_Spaces, WLS_Portlet, or WLS_Services) is not recommended.

For each managed server, specify:

- Name
Name of the managed server. Each server within the domain must have a unique name. The server name is not used as part of the URL for applications that are deployed on the server. It is for your identification purposes only.

- Listen Address
Enter an IP address or DNS name if you want to limit the number of valid addresses for a server instance. Otherwise, URLs to the server can specify any of the host computer's IP address, any DNS name that maps to one of the IP addresses, or the localhost string.

- Listen Port
Enter the port number from which you want to access the server instance. If you run multiple server instances on a single computer, each server must use its own listen port.

- SSL Listen Port
Enter the port number from which you want to access the server instance for SSL connections - this column is only active if the corresponding SSL enabled checkbox in the same row is selected.

Click Switch Display to see the managed server information in tabs rather than in a table.

B.13 Configure Clusters Screen

A cluster consists of multiple managed server instances working together to provide increased scalability and reliability.

Use this screen to add or delete clusters; click Add to add a cluster. To delete a cluster, select the cluster name and click Delete.

For each cluster, specify:

- Name
Name of the cluster.

- Cluster messaging mode
If you are creating a cluster within a new WebLogic Server environment, Oracle recommends that you use the Unicast messaging type.

If you are creating a cluster within an existing WebLogic Server environment or you need to ensure backward compatibility with older versions of WebLogic Server, you must use the Multicast messaging type. This enables multiple applications to subscribe to a given IP address and port number and listen for messages.

Select "multicast" or "unicast" from the drop-down list. If you select "multicast" you must also provide:

- Multicast address
A multicast address is an IP address in the range from 224.0.0.0 to 239.255.255.255. The valid range is from 224.0.0.0 to 239.255.255.255. The default value used by WebLogic Server is 239.192.0.0. You should avoid using multicast addresses in the range x.0.0.1. This address must be unique to this cluster and should not be shared by other applications.

- Multicast port
The multicast port is used by cluster members to communicate with each other. Valid values are between 1 and 65535.

- Cluster address
Address of the cluster.

Click Switch Display to see the cluster information in tabs rather than in a table.

B.14 Assign Servers to Clusters Screen

Use this screen to assign each managed server to a cluster in the domain.

B.15 Create HTTP Proxy Applications Screen

An HTTP proxy server proxies requests from a web server to WebLogic Server instances in a cluster, and provides load balancing and failover for the proxied HTTP requests.

If you want to proxy requests for a cluster, select Create HTTP Proxy next to the cluster name, then select a proxy server from the drop-down list in the "Proxy Server" field.

B.16 Configure Machines Screen

A machine is the logical representation of the computer that hosts one or more WebLogic Server instances. Each Managed Server must be assigned to a machine. The Administration Server and Node Manager are used to manage the machines defined on this screen.

If you are creating a new machine on a non-UNIX operating system, specify the following:

- Name
Name of the machine. This name is used to identify the machine within the WebLogic Server domain; it does not have to correspond to the machine's network name.

- Node manager listen address
Enter the DNS name or IP address on which the Node Manager listens.

- Node manager listen port
Enter the port number on which the Node Manager listens for incoming requests.

For UNIX machine, click the "Unix Machine" tab and specify the following:

- Name
Name of the machine. This name is used to identify the machine within the WebLogic Server domain; it does not have to correspond to the machine's network name.

- Post bind GID enabled and Post bind GID
Select Post bind GID enabled to specify a non-privileged group account under which the server instance runs, then enter the group in the Post bind GID column. The default group is nobody, which is a standard UNIX group ID that provides the least possible privileges. In a production environment, Oracle recommends that you create a group account specifically for running instances of WebLogic Server.

- Post bind UID enabled and Post bind UID
Select Post bind UID enabled to specify a non-privileged user account under which the server instance runs, then enter the user in the Post bind UID column. The default user is nobody, which is a standard UNIX account that provides the least possible privileges. In a production environment, Oracle recommends that you create a user account specifically for running instances of WebLogic Server.

- Node manager listen address
Enter the DNS name or IP address on which the Node Manager listens.

- Mode manager listen port
Enter the port number on which the Node Manager listens for incoming requests.

B.17 Assign Servers to Machines Screen

Use this screen to assign each WebLogic Server instance to the corresponding machine on which it runs.

B.18 Target Deployments to Servers or Clusters Screen

This screen enables you to target your deployments to servers or clusters. Doing so enables WebLogic Server to serve the deployment to clients.

The Configuration Wizard automatically takes care of all necessary deployment targeting. You should not have to change anything on this screen unless specifically directed to do so. For more information, refer to "Target Deployments to Clusters or Servers" in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard.

In the left pane, select the server or cluster. Then, select the deployment in the right pane that you want to target to the selected server or cluster. The "Target" column in the right pane shows you the servers and clusters to which each deployment is targeted.

B.19 Target Services to Servers or Clusters Screen

Use this screen to target your services (for example, JMS, JDBC, startup and shutdown classes) to servers or clusters. Doing so enables your applications to use these services.

The Configuration Wizard automatically takes care of all necessary services targeting. You should not have to change anything on this screen unless specifically directed to do so. For more information, refer to "Target Services to Clusters or Servers" in Oracle WebLogic Server Creating WebLogic Domains Using the Configuration Wizard.

In the left pane, select the server or cluster. Then, select the service in the right pane that you want to target to the selected server or cluster. The "Target" column in the right pane shows you the servers and clusters to which each service is targeted.

B.20 Configure JMS File Stores Screen

Edit the configuration information for the JMS file stores, which are used to store persistent messages and durable subscribers.

- Name
Alphanumeric (no spaces) name of your JMS file store. Each JMS file store configuration in your WebLogic environment must have a unique name, regardless of the domain or cluster in which it resides.

- Directory
Directory where the JMS file store is located.

- Synchronous write policy
Use the drop-down list to select one of the following for each file store:

- Cache-Flush
Transactions cannot complete until all of their writes have been flushed down to disk. This policy is reliable and scales well as the number of simultaneous users increases.

- Direct-Write
File store writes are written directly to disk. This policy is supported on Solaris and Windows. If this policy is set on an unsupported platform, the file store automatically uses the Cache-Flush policy instead.

- Disabled
Transactions are complete as soon as their writes are cached in memory, instead of waiting for the writes to successfully reach the disk. This policy is the fastest, but the least reliable (that is, transactionally safe). It can be much faster than the other policies, but power outages or operating system failures can cause lost or duplicate messages.

B.21 Configure RDBMS Security Store Database Screen

To make changes on this screen, select a database type from the drop-down list in the "Database Type" field. Then, select the appropriate driver in the "Driver" field.

Provide the following credentials for the selected database:

- DBMS SID
The service ID of your database; this is usually the same as the global ID.

- DBMS Host
The name of the machine on which the database is running.

- DBMS Port
The listen port number of the database.

- User Name
The user name to access the database.

- User Password
The password for the database user.

- Confirm User Password
Re-enter the password for the database user.

Click Test Connection to make sure that the connection to your database is valid.

Click Next to continue.

B.22 Configuration Summary Screen

Verify the information on this screen. In the Summary View field, select a category from the drop-down list to view information about that category:

- Deployment
Shows the deployments that will be configured in each cluster and server. You can click on the name of a deployment to view detailed information about the selected deployment.

- Application
Shows the applications that will be configured in each cluster and server. You can click on the name of an application to view detailed information about the selected application.

- Service
Shows the services that will be configured in each cluster and server. You can click on the name of a service to view detailed information about the selected service.

- Cluster
Shows the clusters that will be configured in this domain and the servers that will be configured in each cluster. You can click on each server name to view information specific to that server.

- Machine
Shows the machines that will be configured in this domain and the servers that will be configured in each machine. You can click on each server name to view information specific to that server.

Use the Previous button if you want to return to a previous screen to alter some portion of the configuration.

If everything is correct, click Create.

B.23 Creating Domain Screen

This screen shows the progress of the domain creation.

When it is finished, click Done to dismiss the window.

B.24 Extending Domain Screen

This screen shows the progress of the domain creation.

When it is finished, click Done to dismiss the window.

C Oracle WebCenter Deinstallation Screens

This appendix contains screenshots and descriptions for all of the Oracle WebCenter deinstallation screens:

- Welcome Screen

- Deinstall Oracle Home Screen

- Deinstall Progress Screen

- Deinstall Completed Screen

C.1 Welcome Screen

The Welcome screen is displayed each time you start the deinstaller.

Click Next to continue.

C.2 Deinstall Oracle Home Screen

This screen shows the Oracle Home directory that is about to be deinstalled. This is the Oracle Home directory from which the deinstaller was started.

Note:
Before you choose to remove this Oracle Home, make sure that it is not in use by an existing domain.

Verify that this is the correct directory, then click Deinstall to continue.

C.3 Deinstall Progress Screen

This screen shows you the progress of the deinstallation.

If you want to quit before the deinstallation is completed, click Cancel.

C.4 Deinstall Completed Screen

This screen summarizes the deinstallation that was just completed.

Click Finish to dismiss the screen.

D Silent Installation

This appendix describes how to install Oracle WebCenter from the command line in silent mode. This appendix contains the following topics:

- Section D.1, "What is a Silent Installation?"

- Section D.2, "Creating Response Files"

- Section D.3, "Pre-Installation Tasks"

- Section D.4, "Silent Installation Instructions"

- Section D.5, "Silent De-Installation"

D.1 What is a Silent Installation?

Silent installation eliminates the need to monitor the Oracle WebCenter installation because no graphical output is displayed and no input by the user is required.

Silent installation of Oracle WebCenter is accomplished by supplying the installer with a response file and using the -silent flag on the command line. The response file is a text file containing variables and parameter values which provide answers to the installer prompts.

Note:
For UNIX users, if this is a first time installation of Oracle WebCenter, you must create the oraInst.loc file before starting. Please refer to Section D.3.1, "UNIX Users: Creating the oraInst.loc File" for more information.
Following installation of Oracle WebCenter, you need to run the root.sh script as the root user. The root.sh script detects settings of environment variables and enables you to enter the full path of the local bin directory.

Note:
For Windows users, if this is a first time installation of Oracle WebCenter, you must create the registry keys before starting. Registry key creation is described in Section D.3.2, "Windows Users: Creating the Registry Key"

D.2 Creating Response Files

Before doing a silent installation, you must provide information specific to your installation in a response file. The installer will fail if you attempt an installation using a response file that is not configured correctly. Response files are text files that you can create or edit in a text editor

Table D-1 lists the response files provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory on the installation CD-ROM:

Table D-1 Oracle WebCenter Installation and Configuration Response File Templates

Template

Description

oracle.as.webcenter.top.Custom.rsp

This is the template response file that should be used if you want to install and configure Oracle WebCenter products. The GUI equivalent would be installing the software and then running the Configuration Wizard to create or extend your WebLogic domain and configure your Oracle WebCenter products.

To complete this template, you must provide a valid value for each field containing <Value Required>. See Section D.2.1, "Contents of the oracle.as.webcenter.top.Custom.rsp File" to view the contents of this file.

sampleResponse.rsp

This is the template response file that should be used if you want to install the Oracle WebCenter software only. You will still need to run the Configuration Wizard separately to create or extend your WebLogic domain and configure Oracle WebCenter products.

The only parameters you need to specify in this file are ORACLE_HOME and MIDDLEWARE_HOME. See Section D.2.2, "Contents of the sampleResponse.rsp File" to view the contents of this file.

In addition to these pre-existing response files, you can create your own response file by running the install GUI, then clicking Save on the Installation Summary Screen. You will be prompted for a name and location where you want to create this response file. After it is created, you can use it exactly as-is to replicate the installation on other systems, or modify it as needed.

D.2.1 Contents of the oracle.as.webcenter.top.Custom.rsp File

This section shows the contents of the Disk1/stage/Response/oracle.as.webcenter.top.Custom.rsp response file on a UNIX system:

####################################################################
## Copyright (c) 1999, 2009 Oracle. All rights reserved.          ##
##                                                                ##
## Specify values for the variables listed below to customize     ##
## your installation.                                             ##
##                                                                ##
## Each variable is associated with a comment. The comment        ##
## identifies the variable type.                                  ##
##                                                                ##
## Please specify the values in the following format:             ##
##                                                                ##
##         Type         Example                                   ##
##         String       "Sample Value"                            ##
##         Boolean      True or False                             ##
##         Number       1000                                      ##
##         StringList   {"String value 1","String Value 2"}       ##
##                                                                ##
## The values that are given as <Value Required> need to be       ##
## specified for a silent installation to be successful.          ##
##                                                                ##
##                                                                ##
## This response file is generated by Oracle Software             ##
## Packager.                                                      ##
####################################################################

RESPONSEFILE_VERSION=2.2.1.0.0

#-------------------------------------------------------------------------------
#Name       : UNIX_GROUP_NAME
#Datatype   : String
#Description: Unix group to be set for the inventory directory. Valid only in Unix platforms.
#Example: UNIX_GROUP_NAME = "install"
#-------------------------------------------------------------------------------
UNIX_GROUP_NAME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : FROM_LOCATION
#Datatype   : String
#Description: Complete path to the products.xml.
#Example: FROM_LOCATION = "../stage/products.xml"
#-------------------------------------------------------------------------------
FROM_LOCATION="../stage/products.xml"

#-------------------------------------------------------------------------------
#Name       : FROM_LOCATION_CD_LABEL
#Datatype   : String
#Description: This variable should only be used in multi-CD installations. It includes the label of the compact disk where the file "products.xml" exists. The label can be found in the file "disk.label" in the same directory as products.xml.
#Example: FROM_LOCATION_CD_LABEL = "CD Label"
#-------------------------------------------------------------------------------
FROM_LOCATION_CD_LABEL=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOME
#Datatype   : String
#Description: Complete path of the Oracle Home.
#Example: ORACLE_HOME = "C:\OHOME1"
#-------------------------------------------------------------------------------
ORACLE_HOME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : ORACLE_BASE
#Datatype   : String
#Description: Complete path of the Oracle Base.
#Example: ORACLE_BASE =
#-------------------------------------------------------------------------------
ORACLE_BASE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOME_NAME
#Datatype   : String
#Description: Oracle Home Name. Used in creating folders and services.
#Example: ORACLE_HOME_NAME = "OHOME1"
#-------------------------------------------------------------------------------
ORACLE_HOME_NAME="OHOME1"

#-------------------------------------------------------------------------------
#Name       : SHOW_WELCOME_PAGE
#Datatype   : Boolean
#Description: Set to true if the Welcome page in OUI needs to be shown.
#Example: SHOW_WELCOME_PAGE = false
#-------------------------------------------------------------------------------
SHOW_WELCOME_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SUPPRESS_BUGLIST_WARNING
#Datatype   : Boolean
#Description: Set to true if the Welcome page in OUI needs to be shown.
#Example: SUPPRESS_BUGLIST_WARNING = false
#-------------------------------------------------------------------------------
SUPPRESS_BUGLIST_WARNING=false

#-------------------------------------------------------------------------------
#Name       : SHOW_NODE_SELECTION_PAGE
#Datatype   : Boolean
#Description: Set to true if the node selection page in OUI needs to be shown.
#Example: SHOW_NODE_SELECTION_PAGE = false
#-------------------------------------------------------------------------------
SHOW_NODE_SELECTION_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SHOW_CUSTOM_TREE_PAGE
#Datatype   : Boolean
#Description: Set to true if the custom tree page in OUI needs to be shown.
#Use this page to select or de-select dependencies. This page appears only in a custom install type.
#Example: SHOW_CUSTOM_TREE_PAGE = false
#-------------------------------------------------------------------------------
SHOW_CUSTOM_TREE_PAGE=false
#-------------------------------------------------------------------------------
#Name       : SHOW_COMPONENT_LOCATIONS_PAGE
#Datatype   : Boolean
#Description: Set to true if the component locations page in OUI needs to be shown.
#This page only appears if there are products whose installed directory can be changed.
#If you set this to false you will prevent the user from being able to specify alternate directories.
#Example: SHOW_COMPONENT_LOCATIONS_PAGE = false
#-------------------------------------------------------------------------------
SHOW_COMPONENT_LOCATIONS_PAGE=false

#-------------------------------------------------------------------------------
#Name       : SHOW_SUMMARY_PAGE
#Datatype   : Boolean
#Description: Set to true if the summary page in OUI needs to be shown.
#The summary page shows the list of components that will be installed in this session.
#Example: SHOW_SUMMARY_PAGE = true
#-------------------------------------------------------------------------------
SHOW_SUMMARY_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_INSTALL_PROGRESS_PAGE
#Datatype   : Boolean
#Description: Set to true if the install progress page in OUI needs to be shown.
#This page shows the current status in the installation. The current status includes the product being installed and the file being copied.
#Example: SHOW_INSTALL_PROGRESS_PAGE = true
#-------------------------------------------------------------------------------
SHOW_INSTALL_PROGRESS_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_REQUIRED_CONFIG_TOOL_PAGE
#Datatype   : Boolean
#Description: Set to true if the required config assistants page in OUI needs to be shown.
#This page shows the list of required configuration assistants that are part of this installation.
#It shows the status of each assistant, including any failures with detailed information on why it failed.
#Example: SHOW_REQUIRED_CONFIG_TOOL_PAGE = true
#-------------------------------------------------------------------------------
SHOW_REQUIRED_CONFIG_TOOL_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_CONFIG_TOOL_PAGE
#Datatype   : Boolean
#Description: Set to true if the config assistants page in OUI needs to be shown.
#This page shows the list of configuration assistants that are part of this installation and are configured to launch automatically.
#It shows the status of each assistant, including any failures with detailed information on why it failed.
#Example: SHOW_CONFIG_TOOL_PAGE = true
#-------------------------------------------------------------------------------
SHOW_CONFIG_TOOL_PAGE=true
#-------------------------------------------------------------------------------
#Name       : SHOW_RELEASE_NOTES
#Datatype   : Boolean
#Description: Set to true if the release notes of this installation need to be shown at the end of installation.
#This dialog is launchable from the End of Installation page and shows the list of release notes available for the products just installed.
# This also requires the variable SHOW_END_SESSION_PAGE variable to be set to true.
#Example: SHOW_RELEASE_NOTES = true
#-------------------------------------------------------------------------------
SHOW_RELEASE_NOTES=true

#-------------------------------------------------------------------------------
#Name       : SHOW_ROOTSH_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if the Confirmation dialog asking to run the root.sh script in OUI needs to be shown.
#Valid only for Unix platforms.
#Example: SHOW_ROOTSH_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_ROOTSH_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : SHOW_END_SESSION_PAGE
#Datatype   : Boolean
#Description: Set to true if the end of session page in OUI needs to be shown.
#This page shows if the installation is successful or not.
#Example: SHOW_END_SESSION_PAGE = true
#-------------------------------------------------------------------------------
SHOW_END_SESSION_PAGE=true

#-------------------------------------------------------------------------------
#Name       : SHOW_EXIT_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if the confirmation when exiting OUI needs to be shown.
#Example: SHOW_EXIT_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_EXIT_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION
#Datatype   : Boolean
#Description: Set to true to allow users to go back to the File Locations page for another installation. This flag also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
#Example: NEXT_SESSION = true
#-------------------------------------------------------------------------------
NEXT_SESSION=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION_ON_FAIL
#Datatype   : Boolean
#Description: Set to true to allow users to invoke another session even if current install session has failed. This flag is only relevant if NEXT_SESSION is set to true.
#Example: NEXT_SESSION_ON_FAIL = true
#-------------------------------------------------------------------------------
NEXT_SESSION_ON_FAIL=true

#-------------------------------------------------------------------------------
#Name       : NEXT_SESSION_RESPONSE
#Datatype   : String
#Description: Set to true to allow users to go back to the File Locations page for another installation. This flag also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
#Example: NEXT_SESSION_RESPONSE = "nextinstall.rsp"
#-------------------------------------------------------------------------------
NEXT_SESSION_RESPONSE=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : DEINSTALL_LIST
#Datatype   : StringList
#Description: List of components to be deinstalled during a deinstall session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.as.webcenter.top, 11.0.0.0.0 : Oracle WebCenter Suite 11g 11.0.0.0.0
#Example: DEINSTALL_LIST = {"oracle.as.webcenter.top","11.0.0.0.0"}
#-------------------------------------------------------------------------------
DEINSTALL_LIST={"oracle.as.webcenter.top","11.0.0.0.0"}

#-------------------------------------------------------------------------------
#Name       : SHOW_DEINSTALL_CONFIRMATION
#Datatype   : Boolean
#Description: Set to true if deinstall confimation is needed during a deinstall session.
#Example: SHOW_DEINSTALL_CONFIRMATION = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_CONFIRMATION=true

#-------------------------------------------------------------------------------
#Name       : SHOW_DEINSTALL_PROGRESS
#Datatype   : Boolean
#Description: Set to true if deinstall progress is needed during a deinstall session.
#Example: SHOW_DEINSTALL_PROGRESS = true
#-------------------------------------------------------------------------------
SHOW_DEINSTALL_PROGRESS=true

#-------------------------------------------------------------------------------
#Name       : CLUSTER_NODES
#Datatype   : StringList
#Description: This variable represents the cluster node names selected by the user for installation.
#Example: CLUSTER_NODES = {"node1"}
#-------------------------------------------------------------------------------
CLUSTER_NODES=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : REMOTE_NODES
#Datatype   : StringList
#Description: This variable represents the remote node names on which installation is carried out.
#Example: REMOTE_NODES =
#-------------------------------------------------------------------------------
REMOTE_NODES=<Value Required>
#-------------------------------------------------------------------------------
#Name       : LOCAL_NODE
#Datatype   : String
#Description: This variable represents the local node.
#Example: LOCAL_NODE =
#-------------------------------------------------------------------------------
LOCAL_NODE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : RESTART_SYSTEM
#Datatype   : Boolean
#Description: Set to true to allow automatic restart of the system, if set to false then installer will exit without restarting, no exit confirmation dialog is shown
#Example: RESTART_SYSTEM = false
#-------------------------------------------------------------------------------
RESTART_SYSTEM=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : RESTART_REMOTE_SYSTEM
#Datatype   : Boolean
#Description: Set to true to allow automatic restart of the remote systems, if set to false then installer will not restart the remote systems, no exit confirmation dialog is shown
#Example: RESTART_REMOTE_SYSTEM = false
#-------------------------------------------------------------------------------
RESTART_REMOTE_SYSTEM=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : ORACLE_HOSTNAME
#Datatype   : String
#Description: This variable holds the hostname of the system as set by the user.
#Example: ORACLE_HOSTNAME =
#-------------------------------------------------------------------------------
ORACLE_HOSTNAME=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : REMOVE_HOMES
#Datatype   : StringList
#Description: List of the homes to be removed during a deinstall session. Each home is represented by its full path.
#Example: REMOVE_HOMES = {<full_path_of_home1>,<full_path_of_home2>, ...}
#-------------------------------------------------------------------------------
REMOVE_HOMES=<Value Unspecified>

#-------------------------------------------------------------------------------
#Name       : SHOW_XML_PREREQ_PAGE
#Datatype   : Boolean
#Description: This variable determines whether or not to show the prereq page.
#Example: SHOW_XML_PREREQ_PAGE = true
#-------------------------------------------------------------------------------
SHOW_XML_PREREQ_PAGE=true
#-------------------------------------------------------------------------------
#Name       : SHOW_END_OF_INSTALL_MSGS
#Datatype   : Boolean
#Description: Set to true if the text on end of install screen is to be shown. The text is always available under <Oracle Home>/install/readme.txt.
#Example: SHOW_END_OF_INSTALL_MSGS = true
#-------------------------------------------------------------------------------
SHOW_END_OF_INSTALL_MSGS=true

#-------------------------------------------------------------------------------
#Name       : ACCEPT_LICENSE_AGREEMENT
#Datatype   : Boolean
#Description: By setting this variable to true, you are accepting the license agreement. This variable is used only for silent installations.
#Example: ACCEPT_LICENSE_AGREEMENT = true
#-------------------------------------------------------------------------------
ACCEPT_LICENSE_AGREEMENT=true

#-------------------------------------------------------------------------------
#Name       : METALINK_LOCATION
#Datatype   : String
#Description: This variable represents the Oracle metalink location.
#Example: METALINK_LOCATION =
#-------------------------------------------------------------------------------
METALINK_LOCATION=<Value Required>

#-------------------------------------------------------------------------------
#Name       : METALINK_USERNAME
#Datatype   : String
#Description: This variable represents the Oracle metalink user name.
#Example: METALINK_USERNAME =
#-------------------------------------------------------------------------------
METALINK_USERNAME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : MYORACLESUPPORT_USERNAME
#Datatype   : String
#Description: This variable represents the Oracle metalink user name.
#Example: MYORACLESUPPORT_USERNAME =
#-------------------------------------------------------------------------------
MYORACLESUPPORT_USERNAME=<Value Required>

#-------------------------------------------------------------------------------
#Name       : METALINK_PASSWORD
#Datatype   : String
#Description: This variable represents the corresponding Oracle metalink password.
#Example: METALINK_PASSWORD =
#-------------------------------------------------------------------------------
METALINK_PASSWORD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : MYORACLESUPPORT_PASSWORD
#Datatype   : String
#Description: This variable represents the corresponding Oracle metalink password.
#Example: MYORACLESUPPORT_PASSWORD =
#-------------------------------------------------------------------------------
MYORACLESUPPORT_PASSWORD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_HOST
#Datatype   : String
#Description: The proxy host  used to connect to Oracle metalink.
#Example: PROXY_HOST =
#-------------------------------------------------------------------------------
PROXY_HOST=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_PORT
#Datatype   : String
#Description: The proxy port used to connect to Oracle metalink.
#Example: PROXY_PORT =
#-------------------------------------------------------------------------------
PROXY_PORT=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_REALM
#Datatype   : String
#Description: The realm for the proxy used to connect to Oracle metalink.
#Example: PROXY_REALM =
#-------------------------------------------------------------------------------
PROXY_REALM=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_USER
#Datatype   : String
#Description: The username for the proxy  used to connect to Oracle metalink.
#Example: PROXY_USER =
#-------------------------------------------------------------------------------
PROXY_USER=<Value Required>

#-------------------------------------------------------------------------------
#Name       : PROXY_PWD
#Datatype   : String
#Description: The password for the proxy  used to connect to Oracle metalink.
#Example: PROXY_PWD =
#-------------------------------------------------------------------------------
PROXY_PWD=<Value Required>

#-------------------------------------------------------------------------------
#Name       : DONT_PROXY_FOR
#Datatype   : String
#Description: The dont proxy for list.
#Example: DONT_PROXY_FOR =
#-------------------------------------------------------------------------------
DONT_PROXY_FOR=<Value Required>

#-------------------------------------------------------------------------------
#Name       : DECLINE_SECURITY_UPDATES
#Datatype   : Boolean
#Description: OUI Session variable set to decline from receiving the security updates
#Example: DECLINE_SECURITY_UPDATES =
#-------------------------------------------------------------------------------
DECLINE_SECURITY_UPDATES=<Value Required>
#-------------------------------------------------------------------------------
#Name       : COLLECTOR_RESPONSE_FILE
#Datatype   : String
#Description: OUI Session variable used to provide the OCM response file location
#Example: COLLECTOR_RESPONSE_FILE =
#-------------------------------------------------------------------------------
COLLECTOR_RESPONSE_FILE=<Value Required>

#-------------------------------------------------------------------------------
#Name       : SECURITY_UPDATES_VIA_METALINK
#Datatype   : Boolean
#Description: OUI Session variable used to set if the security updates should be received via Metalink details
#Example: SECURITY_UPDATES_VIA_METALINK =
#-------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_METALINK=<Value Required>

#-------------------------------------------------------------------------------
#Name       : SECURITY_UPDATES_VIA_MYORACLESUPPORT
#Datatype   : Boolean
#Description: OUI Session variable used to set if the security updates should be received via Metalink details
#Example: SECURITY_UPDATES_VIA_MYORACLESUPPORT =
#-------------------------------------------------------------------------------
SECURITY_UPDATES_VIA_MYORACLESUPPORT=<Value Required>

#-------------------------------------------------------------------------------
#Name       : TOPLEVEL_COMPONENT
#Datatype   : StringList
#Description: The top level component to be installed in the current session.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.as.webcenter.top, 11.0.0.0.0 : Oracle WebCenter Suite 11g 11.0.0.0.0
#Example: TOPLEVEL_COMPONENT = {"oracle.as.webcenter.top","11.0.0.0.0"}
#-------------------------------------------------------------------------------
TOPLEVEL_COMPONENT={"oracle.as.webcenter.top","11.0.0.0.0"}

#-------------------------------------------------------------------------------
#Name       : SHOW_SPLASH_SCREEN
#Datatype   : Boolean
#Description: Set to true if the initial splash screen in OUI needs to be shown.
#Example: SHOW_SPLASH_SCREEN =
#-------------------------------------------------------------------------------
SHOW_SPLASH_SCREEN=true
#-------------------------------------------------------------------------------
#Name       : SELECTED_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    fr,   : French
#    ar,   : Arabic
#    bn,   : Bengali
#    pt_BR,   : Brazilian Portuguese
#    bg,   : Bulgarian
#    fr_CA,   : Canadian French
#    ca,   : Catalan
#    hr,   : Croatian
#    cs,   : Czech
#    da,   : Danish
#    nl,   : Dutch
#    ar_EG,   : Egyptian
#    en_GB,   : English (United Kingdom)
#    et,   : Estonian
#    fi,   : Finnish
#    de,   : German
#    el,   : Greek
#    iw,   : Hebrew
#    hu,   : Hungarian
#    is,   : Icelandic
#    in,   : Indonesian
#    it,   : Italian
#    ja,   : Japanese
#    ko,   : Korean
#    es,   : Latin American Spanish
#    lv,   : Latvian
#    lt,   : Lithuanian
#    ms,   : Malay
#    es_MX,   : Mexican Spanish
#    no,   : Norwegian
#    pl,   : Polish
#    pt,   : Portuguese
#    ro,   : Romanian
#    ru,   : Russian
#    zh_CN,   : Simplified Chinese
#    sk,   : Slovak
#    sl,   : Slovenian
#    es_ES,   : Spanish
#    sv,   : Swedish
#    th,   : Thai
#    zh_TW,   : Traditional Chinese
#    tr,   : Turkish
#    uk,   : Ukrainian
#    vi,   : Vietnamese
#Example: SELECTED_LANGUAGES = {"en"}
#-------------------------------------------------------------------------------
#SELECTED_LANGUAGES={"en"}
#-------------------------------------------------------------------------------
#Name       : COMPONENT_LANGUAGES
#Datatype   : StringList
#Description: Languages in which the components will be installed.
#The following choices are available. The value should contain only one of these choices.
#The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
#    en,   : English
#    fr,   : French
#    ar,   : Arabic
#    bn,   : Bengali
#    pt_BR,   : Brazilian Portuguese
#    bg,   : Bulgarian
#    fr_CA,   : Canadian French
#    ca,   : Catalan
#    hr,   : Croatian
#    cs,   : Czech
#    da,   : Danish
#    nl,   : Dutch
#    ar_EG,   : Egyptian
#    en_GB,   : English (United Kingdom)
#    et,   : Estonian
#    fi,   : Finnish
#    de,   : German
#    el,   : Greek
#    iw,   : Hebrew
#    hu,   : Hungarian
#    is,   : Icelandic
#    in,   : Indonesian
#    it,   : Italian
#    ja,   : Japanese
#    ko,   : Korean
#    es,   : Latin American Spanish
#    lv,   : Latvian
#    lt,   : Lithuanian
#    ms,   : Malay
#    es_MX,   : Mexican Spanish
#    no,   : Norwegian
#    pl,   : Polish
#    pt,   : Portuguese
#    ro,   : Romanian
#    ru,   : Russian
#    zh_CN,   : Simplified Chinese
#    sk,   : Slovak
#    sl,   : Slovenian
#    es_ES,   : Spanish
#    sv,   : Swedish
#    th,   : Thai
#    zh_TW,   : Traditional Chinese
#    tr,   : Turkish
#    uk,   : Ukrainian
#    vi,   : Vietnamese
#Example: COMPONENT_LANGUAGES = {"en"}
#Component  : oracle.as.webcenter.top
#-------------------------------------------------------------------------------
COMPONENT_LANGUAGES={"en"}

#-------------------------------------------------------------------------------
#Name       : DEPENDENCY_LIST
#Datatype   : StringList
#Description: List of dependees that need to be installed along with this product.
#The following choices are available. The value can contain any combination of these choices.
#The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
#    oracle.sysman.common.core, 10.2.0.1.0 : Enterprise Manager Common Core Files 11.1.0.2.0
#Example: DEPENDENCY_LIST = {"oracle.sysman.common.core:10.2.0.1.0"}
#Component  : oracle.sysman.common
#-------------------------------------------------------------------------------

DEPENDENCY_LIST={ "oracle.sysman.common.core:11.1.0.2.0" }

D.2.2 Contents of the sampleResponse.rsp File

This section shows the contents of the Disk1/stage/Response/sampleResponse.rsp response file on a UNIX system:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Provide the Oracle Home location. The location has to be the immediate child under the specified Middleware Home location. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. The total length has to be less than or equal to 128 characters. The location has to be an empty directory or a valid WebCenter Oracle Home.
ORACLE_HOME=/home/middleware/Oracle_WC1

#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/home/middleware

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

D.2.3 Securing Your Silent Installation

Your response files contain certain passwords required by the installer. To minimize security issues regarding these passwords in the response file, follow these guidelines:

- Set the permissions on the response files so that they are readable only by the operating system user who will be performing the silent installation.

- If possible, remove the response files from the system after the silent installation is completed.

D.3 Pre-Installation Tasks

This section covers the pre-installation tasks that may be required before you are able to perform a silent installation.

The following topics are covered:

- Section D.3.1, "UNIX Users: Creating the oraInst.loc File"

- Section D.3.2, "Windows Users: Creating the Registry Key"

D.3.1 UNIX Users: Creating the oraInst.loc File

The Oracle inventory directory is used by the installer to keep track of all Oracle products installed on the computer. The inventory directory is stored in a file called oraInst.loc. If this file does not already exist on your system, you must create it before starting a silent installation. This file is used by the installer.

1. Log in as the root user.

prompt> su

2. Using a text editor such as vi or emacs, create the oraInst.loc file in the directory of your choice. The contents of the file consist of the following two lines:

inventory_loc=oui_inventory_directory
inst_group=oui_install_group

Replace oui_inventory_directory with the full path to the directory where you want the installer to create the inventory directory. Then, replace oui_install_group with the name of the group whose members have write permissions to this directory.

3. Exit from the root user.

# exit

D.3.2 Windows Users: Creating the Registry Key

If you have not installed Oracle WebCenter on your computer, then you need to create the following Registry key and value:

HKEY_LOCAL_MACHINE / SOFTWARE / Oracle / inst_loc = [inventory_directory]

Replace Inventory_Directory with the full path to your installer files. For example:

C:Program Files\Oracle\Inventory

D.4 Silent Installation Instructions

The syntax for running the installer from the command line on UNIX systems is shown below:

runInstaller [-mode] [-options] [(<CommandLinevariable=Value>)*]

On Windows systems:

setup.exe [-mode] [-options] [(<CommandLinevariable=Value>)*]

Table D-2 Installer Command Line Parameters

Parameter

Description

Installation Modes - Only One Mode Can be Specified

-i

-install

Launches the installer in GUI mode. This is the default mode and is used if no mode is specified on the command line.

-silent

Install in silent mode. The installer must be passed either a response file or command line variable value pairs.

-d

-deinstall

Launches the installer in GUI mode for deinstallation.

-p

-prerequisite

Launches the installer in GUI mode but only checks the prerequisites. No software is installed.

-v

-validate

Launches the installer in GUI mode and performs all prerequisite and validation checking, but does not install any software.

-sv

-silentvalidate

Performs all prerequisite and validation checking in silent mode. You must pass the installer either a response file or a series of command line variable value pairs.

Installation Options

-help

--help

--usage

Displays the usage parameters for the runInstaller command.

-invPtrLoc file

Pointer to the inventory location file. Replace file with the full path and name of the oraInst.loc file.

-response file

-responseFile file

Pointer to the response file. Replace file with the full path and name of the response file.

-jreLoc location

Pointer to the location where Java Runtime Environment (JRE) is installed. Replace location with the full path to the jre directory where your JRE is installed.

-logLevel level

Specify the level of logging performed by the installer; all messages with a lower priority than the specified level will be recorded. Valid levels are:

- severe

- warning

- info

- config

- fine

- finer

- finest

-debug

Obtain debug information from the installer.

-force

Allow the silent installation to proceed in a non-empty directory.

-printdiskusage

Log debugging information pertaining to disk usage.

-printmemory

Log debugging information pertaining to memory usage.

-printtime

Log debugging information pertaining to time usage. This command causes the timeTakentimestamp.log file to be created.

-waitforcompletion

Windows only - the installer will wait for completion instead of spawning the Java engine and exiting.

-noconsole

Messages will not be displayed to the console window.

-ignoreSysPrereqs

Ignore the results of the system prerequisite checks and continue with the installation.

-executeSysPrereqs

Execute the system prerequisite checks only, then exit.

-paramFile file

Specify the full path to the oraparam.ini file. This file is the initialization file for the installer. The default location of this file is Disk1/install/platform.

-novalidation

Disables all validation checking performed by the installer.

-nodefaultinput

For the GUI install, several screens have information or default values pre-populated. Specifying this option disables this behavior so that no information or values are pre-populated.

Command Line Variables

Installer Variables

Installer variables are specified using varName=value. For example:

ORACLE_HOME=/scratch/jdoe/Oracle/Middleware/Oracle_WC1

Session Variables

Session variables are specified using session:varName=value.

Component Variables

Component variables are specified using session:compInternalName:[Version:]varName=value.

D.4.1 Sample Commands

If this is the first time you are installing on your system (meaning there is no pre-existing Oracle Inventory location), use the following command to perform a silent installation on UNIX systems:

./runInstaller -silent -response file -invPtrLoc file

On Windows systems:

setup.exe -silent -response file -invPtrLoc file

Below is a full example of this command for UNIX systems:

./runInstaller -silent -response /home/jdoe/response/devWC.rsp -invPtrLoc /home/jdoe/oraInst.loc

On Windows:

setup.exe -silent -response C:\home\Oracle\samples\jdoe\response\devWC.rsp -invPtrLoc c:\home\Oracle\oraInst.loc

If you have already installed an Oracle product on your system and do not need to specify an inventory location, then you can use a command similar to the following on UNIX systems:

./runInstaller -silent -response file

On Windows systems:

setup.exe -silent -response file

Below is a full example of this command on a UNIX system:

./runInstaller -silent -response /home/jdoe/response/devWC.rsp

On Windows:

setup.exe -silent -response c:\home\Oracle\samples\jdoe\devWC.rsp

D.4.2 Sample Output

Below is a sample output from a silent install using the sampleResponse.rsp template on a UNIX system:

$ ./runInstaller -jreLoc /home/jdoe/Oracle/Middleware/jdk160_14_R27.6.4-18/ -silent -response /home/jdoe/sampleResponse.rsp
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 69669 MB    Passed
Checking swap space: must be greater than 512 MB.   Actual 1395 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-03_10-49-20PM. Please wait ...[jdoe@dadvmn0789 Disk1]$ Log: /home/jdoe/oraInventory/logs/install2009-04-03_10-49-20PM.log
Copyright Â© 1999, 2009, Oracle and/or its affiliates. All rights reserved.
Reading response file..
Expected result: One of enterprise-4,enterprise-5,redhat-4,redhat-5,SuSE-10
Actual Result: enterprise-4
Check complete. The overall result of this check is: Passed
CertifiedVersions Check: Success.
Checking for gcc-3.4.3-22.1; found gcc-3.4.6-10.0.1-i386.       Passed
Checking for gcc-c++-3.4.3-22.1; found gcc-c++-3.4.6-10.0.1-i386.       Passed
Checking for openmotif21-2.1.30-11.RHEL4.4 ; found openmotif21-2.1.30-11.0.1.RHEL4.6-i386.      Passed
Checking for setarch-1.6-1; found setarch-1.6-1-i386.   Passed
Checking for pdksh-5.2.14-30; found pdksh-5.2.14-30.6-i386.     Passed
Checking for sysstat-5.0.5-1; found sysstat-5.0.5-19.el4-i386.  Passed
Checking for gnome-libs-1:1.4.1.2.90-44.1; found gnome-libs-1:1.4.1.2.90-44.2-i386.     Passed
Checking for libstdc++-3.4.3-22.1 ; found libstdc++-3.4.6-10.0.1-i386.  Passed
Checking for libstdc++-devel-3.4.3-22.1; found libstdc++-devel-3.4.6-10.0.1-i386.       Passed
Checking for compat-libstdc++-296-2.96-132.7.2; found compat-libstdc++-296-2.96-132.7.2-i386.   Passed
Checking for compat-db-4.1.25-9; found compat-db-4.1.25-9-i386. Passed
Checking for control-center-2.8.0-12; found control-center-1:2.8.0-12.rhel4.5-i386.     Passed
Checking for glibc-common-2.3.4-2.9; found glibc-common-2.3.4-2.41-i386.        Passed
Checking for binutils-2.15.92.0.2-13; found binutils-2.15.92.0.2-25-i386.       Passed
Checking for make-1:3.80-5; found make-1:3.80-7.EL4-i386.       Passed
Checking for xscreensaver-4.18-5.rhel4.2; found xscreensaver-1:4.18-5.rhel4.14.0.1-i386.        Passed
Check complete. The overall result of this check is: Passed
Packages Check: Success.
Checking for VERSION=2.6.9; found VERSION=2.6.9-78.0.0.0.1.ELxenU.      Passed
Checking for hardnofiles=4096; found hardnofiles=4096.  Passed
Checking for softnofiles=4096; found softnofiles=4096.  Passed
Check complete. The overall result of this check is: Passed
Kernel Check: Success.
Expected result: ATLEAST=2.3.4-2.19
Actual Result: 2.3.4-2.41
Check complete. The overall result of this check is: Passed
GLIBC Check: Success.
Expected result: 922MB
Actual Result: 4000MB
Check complete. The overall result of this check is: Passed
TotalMemory Check: Success.
Verifying data......
Copying Files...
-----------20%----------40%----------60%----------80%--------100%

The installation of Oracle WebCenter Suite 11g completed successfully.

D.5 Silent De-Installation

You can also de-install the software on your system by using the -d or -deinstall parameter from the command line.

On UNIX systems:

./runInstaller -silent -deinstall -response file

On Windows systems:

setup.exe -silent -deinstall -response file

E Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle WebCenter. It contains the following sections:

- Section E.1, "General Troubleshooting Tips"

- Section E.2, "Troubleshooting Oracle Fusion Middleware Installation"

- Section E.3, "Keeping Track of Your JRE Location"

- Section E.4, "Need More Help?"

E.1 General Troubleshooting Tips

If you encounter an error during installation:

- Read the Oracle Fusion Middleware Release Notes for the latest updates. The most current version of the release notes is available on Oracle Technology Network (http://www.oracle.com/technology/documentation).

- Verify that your computer meets the requirements specified in Section 2.1.1, "System Requirements and Certification".

- If you entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen.

- If an error occurred while the installer is copying or linking files:

1. Note the error and review the installation log files.

2. Remove the failed installation by following the steps in Chapter 5, "Deinstalling Oracle WebCenter".

3. Correct the issue that caused the error.

4. Restart the installation.

E.2 Troubleshooting Oracle Fusion Middleware Installation

This section contains solutions to common problems that you might encounter when installing Oracle Fusion Middleware. The following topics are covered:

- Section E.2.1, "Installation Log Files"

- Section E.2.2, "Configuration Log Files"

E.2.1 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. On UNIX operating systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

- Linux: /etc/oraInst.loc

- HP-UX and Solaris: /var/opt/oracle/oraInst.loc

On Windows operating systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

The following install log files are written to the log directory:

- installdate-time-stamp.log
This is the main log ifle.

- installdate-time-stamp.out
This log file contains the output and error streams during the installation.

- installActionsdate-time-stamp.log
This file is used by tbe installer GUI to keep track of internal information.

- installProfiledate-time-stamp.log
This log file contains the overall statistics like time taken to complete the installation, as well as configuration, memory and CPU details.

- oraInstalldate-time-stamp.log
This log file contains the output stream of the copy session.

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log and timedate-time-stamp.log files are created in the same directory:

- timeTakendate-time-stamp.log
This file contains information for the amout of time taken to move between screens (applicable for GUI installations only).

- timedate-time-stamp.log
This file contains time information for the copy session.

If you start the installer with the -printmemory parameter, the memorydate-time-stamp.log file is created. This file contains memory usage information for the copy session.

E.2.2 Configuration Log Files

To create a log file of your configuration session, start the Configuration Wizard with the -log option, as shown below:

On UNIX operating systems:

% ./config.sh -log=log_filename

On Windows operating systems:

G:\ config.cmd -log=log_filename

If you specify an absolute path with your log_filename then your log file will be created there. If you only specify a file name with no path, then the log files are created in the WebCenter_ORACLE_HOME/common/bin (on UNIX operating systems) or WebCenter_ORACLE_HOME\common\bin (on Windows operating systems) directory.

E.3 Keeping Track of Your JRE Location

The JRE location used by the installer is stored in the WebCenter_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or WebCenter_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file. This file is used by OPatch and Oracle Universal Installer (OUI) to determine the location of your preferred JRE.

It is possible to change the location of your JRE (for example, the JRE directory is moved out of the Middleware Home). If this happens, you will get an error message when trying to run OPatch or OUI since the JRE location can no longer be found. If this happens, you can do one of the following:

- Edit the WebCenter_ORACLE_HOME/oui/oraparam.ini (on UNIX operating systems) or WebCenter_ORACLE_HOME\oui\oraparam.ini (on Windows operating systems) file to point to the new JRE location.

- Use the -jreLoc command line option to point to the new JRE location. See Section 2.8.1, "Starting the Installer" for more information.

E.4 Need More Help?

If this appendix does not solve the problem you encountered, try these other sources:

- Oracle Fusion Middleware Release Notes, available on the Oracle Technology Network (http://www.oracle.com/technology/documentation)

- My Oracle Support (formerly OracleMetaLink: http://metalink.oracle.com)

If you do not find a solution for your problem, open a service request.

Index
A  B  C  D  H  I  J  L  M  O  P  R  S  T  W

A

accessibility software, Java Access Bridge, A

Administration Server

configuring, 3.1.6.1

listen address, B.11

listen port, B.11

name, B.11

stopping, 5.1.1

application location, B.5 assigning managed servers to clusters, B.14 assigning managed servers to machines, B.17

B

back-end applications for Oracle WebCenter, 2.6

BPEL server

installing Oracle SOA Suite, 4.7.1

WebCenter Spaces workflows

back-end requirements, 4.7

deploying, 4.7.2

Worklist service requirements, 4.6

C

certification information, 2.1.1

clusters

assigning managed server to, B.14

configuring, 3.1.6.2, B.13

targeting deployments to, B.18

component schema

configuring, 3.1.4

configuration log files, 3.1.3, E.2.2 configuration screens, B

help for, 3.1

Configuration Wizard

configuring JMS file stores, B.20

See Oracle Fusion Middleware Configuration Wizard

starting with Sun JDK, 3.1.2

configuring a UNIX machine, B.16 configuring clusters, 3.1.6.2 configuring deployments and services, 3.1.6.3 configuring HTTP proxy server, B.15 configuring JMS file store, 3.1.6.4 configuring machines, 3.1.6.2, B.16 configuring managed servers, 3.1.6.2, B.12 configuring Oracle WebCenter, B configuring RDBMS security store, 3.1.6.5 configuring the Administration Server, 3.1.6.1 connections, 4.5.2 createCentralInventory.sh script, 2.8.3, A.2 creating a new domain, 3.1.4 creating registry keys, D.1 creating schemas for Oracle WebCenter, 2.1.3 creating the Middleware home directory, 2.1.4 custom port numbers, 2.7

D

database required for installation, 2.1.2

deinstallation screens, C

deinstalling Oracle WebCenter, 5

deployments

configuring, 3.1.6.3

targeting to servers or clusters, B.18

development mode, B.7 DHCP host, 2.3 directory structure of installation, 1.3 documentation conventions, Preface Documents service

back-end requirements, 4.3

Oracle Content Server

connections, 4.3.1.4

Oracle Portal

connections, 4.3.2.2

requirements, 4.3.2

domain

See WebLogic Domain

domain location, B.5 domain name, B.5

H

HTTP proxy server, B.15

HTTP server web address, 2.1.6

I

IMP service

back-end requirements, 4.2

communication server installation, 4.2.1

connections, 4.2.2

installation directory structure, 1.3 installation instructions, 2.8 installation log files, 2.8.2, E.2.1 installation overview, 1 installation roadmap, 1.2 installer

running as root user, 2.8.4

installing on a multihomed computer, 2.5 installing Oracle WebCenter, 2 installing Oracle WebLogic Server, 2.1.4 Instant Messaging and Presence service

See IMP service

J

Java Access Bridge

installing and configuring, 2.1.5

Java Runtime Environment (JRE)

location of, 2.8.1

JDK selection, 2.1.4 JMS file store

configuring, 3.1.6.4, B.20

L

LDAP

about, 4.8

location of configuration log files, 3.1.3 log files, 2.8.2

for installation, E.2.1

loopback adapter

installing for Microsoft Windows, 2.3.3

removing for Microsoft Windows, 2.3.4

M

machines

configuring, 3.1.6.2, B.16

Mail service

back-end requirements, 4.4

connections, 4.4

user credential requirements, 4.4

managed servers

assigning to clusters, B.14

assigning to machines, B.17

configuring, 3.1.6.2, B.12

created during installation, 1.3

stopping, 5.1.1

targeting deployments to, B.18

Microsoft SQL Server database

connecting with RCU, 2.1.3

Microsoft Windows shortcut for Oracle WebLogic Server, 2.1.4 Middleware home directory

creating, 2.1.4

specifying location, 2.8.4

multihomed computer, 2.5

O

Oracle Content Server

about, 1.1

configuring, 4.3.1.3

configuring LDAP, 4.8

connections, 4.3.1.4

installation prerequisites, 4.3.1.1

installing separately from Oracle WebCenter, 4.3.1.2

restarting, 4.3.1.2

running wc_contentserverconfig, 4.3.1.2

Oracle database

connecting with RCU, 2.1.3

Oracle Fusion Middleware

stopping, 5.1.1

Oracle Fusion Middleware Configuration Wizard, 3.1

assigning managed servers to clusters, B.14

assigning managed servers to machines, B.17

configuration screens, B

configuration summary, B.22

configuring clusters, B.13

configuring component schema, B.8

configuring machines, B.16

configuring managed servers, B.12

configuring RDBMS security store, B.21

configuring the Administration Server, B.11

log files, 3.1.3

selecting the domain source, B.3

selecting the extension source, B.4

specifying the domain name and location, B.5

starting, 3.1.2

targeting deployments, B.18

targeting services, B.19

testing component schema, B.9

Oracle Home

specifying, A.5

Oracle home directory

specifying the location, 2.8.4

Oracle HTTP Server

HTTP server web address, 2.1.6

Oracle Inventory

specifying group permissions, 2.8.3, A.1

specifying location, 2.8.3

specifying the location, A.1

Oracle Inventory location, A.1 Oracle JDeveloper

installing, 2.2

removing, 5.1.6

Oracle Middleware Home

specifying, A.5

Oracle Portal

connections, 4.3.2.2

installing, 4.3.2.1

Oracle RTC web services for Microsoft Live Communications Server 2005, 4.2.1 Oracle Secure Enterprise Search

installing, 4.5.1

LDAP configuration, 4.8

Oracle SOA Suite

deploying workflows, 4.7.2

installing, 4.7.1

LDAP configuration, 4.8

Oracle Universal Content Management

installing, 2.8.4, A.6

removing, 5.1.3

specifying the content server admin port, A.6

specifying the content server port, A.6

specifying the database details, A.7

specifying the Oracle UCM installer location, A.10

specifying the web server HTTP address, A.6

Oracle WebCenter

certification information, 2.1.1

components, 1.1

configuration log files, 3.1.3, E.2.2

configuring, 3, B

creating schemas for, 2.1.3

creating the Middleware home directory, 2.1.4

custom port numbers, 2.7

deinstalling, 5

directory structure, 1.3

installation instructions, 2.8

installation log files, 2.8.2

installation overview, 1

installing, 2

installing back-end applications, 2.6

installing on a multihomed computer, 2.5

installing on DHCP host, 2.3

installing Oracle WebLogic Server, 2.1.4

managed servers created during installation, 1.3

reinstallation, 5.2

required schemas, 2.1.3

setting schema passwords, 2.1.3

silent installation, D

starting the deinstaller, 5.1.4.1

starting the installer, 2.8.1

system requirements, 2.1.1

troubleshooting, E

WebLogic Server Home directory, 2.1.4

working with components, 3.2

Oracle WebCenter Discussions

LDAP configuration, 4.8

Oracle WebCenter Portlets, 1.1 Oracle WebCenter Spaces

about, 1.1

content repository requirement, 4.3

workflows, 4.7

Oracle WebCenter Wiki and Blog Server

LDAP configuration, 4.8

Oracle WebLogic Server, 2.1.4

download location, 2.1.4

home directory, 2.1.4

installation type, 2.1.4

JDK selection, 2.1.4

Microsoft Windows shortcut, 2.1.4

removing, 5.1.5

start modes, B.7

starting the installer, 2.1.4

oraInst.loc file, D.1, E.2.1 overview of installation, 1

P

port numbers, 2.7

Post bind GID, B.16

Post bind UID, B.16

production mode, B.7

R

RBDMS security store

configuring, 3.1.6.5

RCU (Repository Creation Utility)

downloading, 2.1.3

setting schema passwords, 2.1.3

starting, 2.1.3, 5.1.2.1

RDBMS security store

configuring, B.21

registry keys, D.1 reinstallation, 5.2 removing Oracle JDeveloper, 5.1.6 removing Oracle WebLogic Server, 5.1.5 Repository Creation Utility

connecting to Microsoft SQL Server database, 2.1.3

connecting to Oracle database, 2.1.3

See RCU

response files, D.1

how to create, D.2

samples, D.2

roadmap for installation, 1.2 root access, Preface root.sh script, D.1

S

sample output for silent installation, D.4.2

sample silent installation commands, D.4.1

sca_CommunityWorkflows.jar file

about, 4.7.2

deploying, 4.7.2.1

deploying using Oracle Enterprise Manager, 4.7.2.1

file location, 4.7.2

schemas

dropping, 5.1.2

Search service

back-end requirements, 4.5

connections, 4.5.2

installing Oracle SES, 4.5.1

services

configuring, 3.1.6.3

setting schema passwords using RCU, 2.1.3 silent de-installation, D.5 silent installation, D

command line parameters, D.4

sample commands, D.4.1

sample output, D.4.2

specifying the application location, B.5 specifying the domain location, B.5 specifying the domain name, B.5 specifying the Oracle Middleware Home, A.5 start modes, B.7 starting RCU (Repository Creation Utility), 5.1.2.1 starting the installer, 2.8.1 starting the Oracle Fusion Middleware Configuration Wizard, 3.1.2 starting the Oracle WebCenter deinstaller, 5.1.4.1 stopping managed servers, 5.1.1 stopping Oracle Fusion Middleware, 5.1.1 stopping the Administration Server, 5.1.1 system requirements, 2.1.1

T

targeting services to servers or clusters, B.19

troubleshooting, E

W

wc_contentserverconfig WebCenter configuration script, 4.3.1.2

WcConfigure component, 4.3.1.2

WebCenter Services

about, 4.1

back-end component requirements, 4.1

Documents service and content integration, 4.3

IMP service, 4.2

Mail service, 4.4

Search service, 4.5

Worklist service, 4.6

database requirement, 4.1 WEBCENTER schema, 4.1 WebCenter Spaces workflows

back-end requirements, 4.7

deploying, 4.7.2

installing Oracle SOA Suite, 4.7.1

WebCenterWorklistDetailApp.ear file

about, 4.7.2

deploying using Oracle Enterprise Manager, 4.7.2.2

deploying using WLST, 4.7.2.2

file location, 4.7.2

WebLogic Domain

configuring the administrator, B.6

creating, 3.1.4

extending, 3.1.5

specifying the name and location, B.5

WebLogic Server Home directory, 2.1.4 Worklist service

back-end requirements, 4.6

connections, 4.6

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.