Oracle® Fusion Middleware

Installation Guide for Oracle Portal, Forms, Reports and Discoverer

11g Release 1 (11.1.1)

E10421-01

May 2009

Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1)

E10421-01

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

Primary Author:  Kevin Hwang

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 Portal, Forms, Reports, and Discoverer Components

- 1.2 Installation Roadmap

- 1.3 Oracle Portal, Forms, Reports, and Discoverer Directory Structure

2 Installing Oracle Portal, Forms, Reports and Discoverer

- 2.1 Before You Begin...

- 2.1.1 System Requirements and Certification

- 2.1.2 Install Oracle Database

- 2.1.3 Create Schemas for Oracle Portal and Oracle Discoverer

- 2.1.4 Install Oracle WebLogic Server and Create the Middleware Home

- 2.1.5 Installing Oracle Internet Directory

- 2.1.6 Upgrading Oracle Web Agent (OWA) for Oracle Portal

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

- 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 Oracle Forms and Oracle Reports on Separate Servers

- 2.7 Installation Instructions

- 2.7.1 Installation Types

- 2.7.2 Installation Log Files

- 2.7.3 Starting the Installer

- 2.7.4 Inventory Screens (UNIX Only)

- 2.7.5 Installation Instructions for "Install and Configure" Install Type

- 2.7.6 Installation Instructions for "Install Only" Install Type

- 2.7.7 Manual Configuration for Oracle Discoverer (Windows Only)

- 2.8 Verifying the Installation

- 2.8.1 Verifying the Installation Logs

- 2.8.2 Verifying the Domain Server Logs

- 2.8.3 Verifying OPMN Status

- 2.8.4 Checking Browser URLs

3 Deinstalling Oracle Portal, Forms, Reports, and Discoverer

- 3.1 Deinstallation Options

- 3.2 Deinstallation Instructions

- 3.2.1 Stopping Oracle Fusion Middleware

- 3.2.2 Removing the Oracle Portal and Oracle Discoverer Schemas

- 3.2.2.1 Starting RCU

- 3.2.2.2 Instructions for Dropping the Oracle Portal and Oracle Discoverer Schemas

- 3.2.3 Removing Oracle Portal, Forms, Reports and Discoverer

- 3.2.3.1 Starting the Deinstaller

- 3.2.3.2 Deinstallation Screens and Instructions

- 3.2.4 Removing Oracle WebLogic Server

- 3.2.5 Removing Oracle JDeveloper

- 3.2.6 Removing the Oracle Home and JDeveloper Home Directories

- 3.3 Reinstallation

A Oracle Portal, Forms, Reports and Discoverer Installation Screens

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

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

- A.3 Welcome Screen

- A.4 Configuration Tool Welcome Screen

- A.5 Select Installation Type Screen

- A.6 Prerequisite Checks Screen

- A.7 Select Domain Screen

- A.8 Specify E-mail for Security Updates Screen

- A.9 Specify Installation Location Screen

- A.9.1 Install and Configure Option

- A.9.2 Install Only - Do Not Configure Option

- A.9.3 Configuration Tool Option

- A.10 Configure Components Screen

- A.11 Configure Ports Screen

- A.12 Specify Proxy Details Screen

- A.13 Specify Schema Screen

- A.14 Specify Portlet Schema Screen

- A.15 Specify Application OID Screen

- A.16 Installation Summary Screen

- A.17 Installation Summary Screen (Install Only Option)

- A.18 Installation Progress Screen

- A.19 Configuration Progress Screen

- A.20 Install Completed Screen

B Oracle Portal, Forms, Reports and Discoverer Deinstallation Screens

- B.1 Welcome Screen

- B.2 Select Deinstallation Type Screen

- B.3 Deinstall Oracle Home Screen

- B.4 Specify WebLogic Domain Detail Screen

- B.5 Select Instance or Home Screen

- B.6 Specify AS Instance Location Screen

- B.7 Deinstallation Summary (Managed Instance)

- B.8 Deinstallation Summary (Unmanaged Instance)

- B.9 Deinstall Progress Screen

- B.10 Deinstall Complete Screen

C Silent Installation

- C.1 What is a Silent Installation?

- C.2 Creating Response Files

- C.2.1 Contents of the deinstall.rsp File

- C.2.2 Contents of the configure_only.rsp File

- C.2.3 Contents of the install_only.rsp File

- C.2.4 Contents of the install_and_configure.rsp File

- C.2.5 Securing Your Silent Installation

- C.3 Pre-Installation Tasks

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

- C.3.2 Windows Users: Creating the Registry Key

- C.4 Silent Installation Instructions

- C.4.1 Sample Commands

- C.4.2 Sample Output

D Troubleshooting

- D.1 General Troubleshooting Tips

- D.2 Troubleshooting Oracle Fusion Middleware Installation

- D.2.1 Installation Log Files

- D.2.2 Configuration Log Files

- D.3 Associating Oracle Reports When Extending a Domain

- D.4 Need More Help?

Index

Preface

The Oracle Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer covers requirements, instructions, and troubleshooting tips for installing and configuring Oracle Portal, Forms, Reports and Discoverer.

Intended Audience

This guide is intended for users who are installing Oracle Fusion Middleware 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 you products will be installed. Users in 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

The Oracle Portal, Forms, Reports, and Discoverer installer will install all of these products by default. After installation, you will have the option to configure the products you want to use.

The chapter includes the following sections:

- Section 1.1, "Oracle Portal, Forms, Reports, and Discoverer Components"

- Section 1.2, "Installation Roadmap"

- Section 1.3, "Oracle Portal, Forms, Reports, and Discoverer Directory Structure"

1.1 Oracle Portal, Forms, Reports, and Discoverer Components

Oracle Portal, Forms, Reports, and Discoverer contains the following components:

- Oracle Portal
Oracle Portal allows you to view content from multiple sources on a single page.

- Oracle Forms Services
Oracle Forms Services is a part of Oracle Fusion Middleware that contains tools and services that enables you to deploy Forms applications over a network. Forms Services is a comprehensive application framework optimized to deploy Forms applications in a multi-tiered environment. It takes advantage of the ease and accessibility of the Web and elevates it from a static information-publishing mechanism to an environment capable of supporting complex applications.

- Oracle Reports
Oracle Reports enables businesses to give immediate access to information to all levels within and outside of the organization in a scalable and secure environment. Using Oracle Reports, you can rapidly develop and deploy sophisticated Web and paper reports against any data source (including an Oracle database, JDBC, XML, and text files). Leveraging J2EE technologies such as JSP and XML, you can publish your reports in a variety of formats (including HTML, XML, PDF, spreadsheet, delimited text, PostScript, and RTF) to any destination (including e-mail, Web browser, Oracle Portal, and file system) in a scalable, efficient manner. Oracle Reports consists of Oracle Reports Developer (a component of the Oracle Developer Suite) and Oracle Reports Services (a component of Oracle Fusion Middleware)

- Oracle Business Intelligence Discoverer
Oracle Discoverer is an intuitive ad-hoc query, reporting, analysis, and Web publishing set of tools that gives business users immediate access to information in databases.

For more information about these components, refer to Oracle Fusion Middleware Concepts.

1.2 Installation Roadmap

Table 1-1 describes the high-level tasks for installing and configuring Oracle Portal, Forms, Reports and Discoverer. The table also provides information on where to get more details about each task.

Table 1-1 Tasks in the Oracle Portal, Forms, Reports, and Discoverer Installation Procedure

Task

Description

Documentation

Mandatory or Optional?

Task 1 - Complete the installation planning requirements

Ensure that your system environment meets the general installation requirements for Oracle Fusion Middleware as well as Oracle Portal, Forms, Reports, and Discoverer.

For system requirements information, go to:

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

For certification information, go to:

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

Mandatory

Task 2 - Run RCU to create the necessary schemas.

Oracle Portal and Oracle Discoverer require schemas that must be installed in an Oracle database. You create and load these schemas in your database by using RCU.

Make sure you have a supported Oracle database up and running. See http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html for more information.

Instructions for creating the schema are provided in Section 2.1.3, "Create Schemas for Oracle Portal and Oracle Discoverer". You can also refer to Oracle Fusion Middleware Repository Creation Utility User's Guide.

Mandatory

Task 3 - Install Oracle WebLogic Server and create a WebLogic domain

Oracle Portal, Forms, Reports, and Discoverer require a WebLogic Domain. During the installation, you are given the option to create a new domain, or extend an existing domain.

In either case, Oracle WebLogic Server must be installed before a domain can be present on your system.

The WebLogic Server installer creates the WebLogic Server home directory within the Oracle Middleware Home directory.

Installation instructions are provided in Section 2.1.4, "Install Oracle WebLogic Server and Create the Middleware Home". You can also refer to Oracle WebLogic Server Installation Guide

For more information about the Middleware Home and WebLogic Home directories, see "Middleware Home and WebLogic Home Directories" in Oracle Fusion Middleware Installation Planning Guide.

Mandatory

Task 4 - Install Oracle Portal, Forms, Reports, and Discoverer

Use the installer to install and configure Oracle Portal, Forms, Reports, and Discoverer.

Chapter 2, "Installing Oracle Portal, Forms, Reports and Discoverer".

Mandatory

Task 5 - Configure Oracle Portal, Forms, Reports, and Discoverer

The installer gives you the option of choosing between two different install types. If you choose the Install and Configure type, you can skip this step.

If you choose the Install Software - Do Not Configure type, you must run the Configuration Tool to configure your components before you are able to use them.

Chapter 2, "Installing Oracle Portal, Forms, Reports and Discoverer".

For more information about the installation types, see Section 2.7.1, "Installation Types".

Optional

1.3 Oracle Portal, Forms, Reports, and Discoverer Directory Structure

Figure 1-1 shows the directory structure of a simple Oracle Portal, Forms, Reports, and Discoverer installation on a single host, using all of the default values.

Figure 1-1 Directory Structure of Oracle Portal, Forms, Reports, and Discoverer Installation

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

For more information about the Oracle Instance directory and system components, refer to "Oracle Fusion Middleware Concepts for All Users" in Oracle Fusion Middleware Installation Planning Guide.

2 Installing Oracle Portal, Forms, Reports and Discoverer

This chapter describes how to install and configure Oracle Portal, Forms, Reports, and Discoverer.

The following topics are covered:

- Section 2.1, "Before You Begin..."

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

- 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 Oracle Forms and Oracle Reports on Separate Servers"

- Section 2.7, "Installation Instructions"

- Section 2.8, "Verifying the Installation"

2.1 Before You Begin...

Make sure you have read the information in this section before you begin:

- Section 2.1.1, "System Requirements and Certification"

- Section 2.1.2, "Install Oracle Database"

- Section 2.1.3, "Create Schemas for Oracle Portal and Oracle Discoverer"

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

- Section 2.1.5, "Installing Oracle Internet Directory"

- Section 2.1.6, "Upgrading Oracle Web Agent (OWA) for Oracle Portal"

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.

The system requirements document covers information such as hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches. This document is available on Oracle Technology Network (OTN):

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

2.1.2 Install Oracle Database

Installation of Oracle Portal, Forms, Reports, and Discoverer requires the availability of an Oracle database. This database must be up and running, and does not have to be on the same system where you are installing the products.

For the latest information about supported databases, visit the following URL:

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

2.1.3 Create Schemas for Oracle Portal and Oracle Discoverer

Oracle Portal and Oracle Discoverer require that certain schemas exist in the database prior to installation. You must run Repository Creation Utility (RCU) to create the schemas in the database. Follow these instructions to do so:

1. Insert the RCU CD-ROM and start RCU from the bin directory:
On UNIX:

./rcu

On Windows:

rcu.bat

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

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

Note:
On Windows systems, make sure that you do not unzip the RCU .zip file to a directory name containing spaces.

After downloading the .zip file, extract the contents to a directory of your choice, and run RCU from the RCU_HOME/bin (on UNIX) or RCU_HOME\bin (on Windows) directory with the commands shown above, where RCU_HOME is the folder where RCU was unzipped, or the drive or mount point of the CD-ROM.

2. Welcome Screen
Click Next.

3. Create Repository Screen
Click Create.

Click Next.

4. Database Connection Details Screen
Select the type of database on your system, then provide the necessary credentials for RCU to be able to connect to your database.

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. The default prefix is DEV.

Table 2-1 lists the required schemas for Oracle Portal and Oracle Discoverer:

Table 2-1 Required Schemas for Oracle Portal and Oracle Discoverer

Component

Required Schemas

Oracle Portal

prefix_PORTAL (Oracle Portal)

Oracle Portlet Producers

prefix_PORTLET (Oracle Portlet Producers)

Oracle Discoverer

prefix_DISCOVERER (Oracle Discoverer)

Oracle Portal requires the PORTLET schema. During the creation of the schemas, you may choose to de-select the PORTLET schema, at which time you will be reminded that this schema is required for Oracle Portal. If you already have a PORTLET schema created elsewhere, you may ignore this message and proceed.

Select the components whose schemas you want to install.

Note:
You must remember or make a note of these schema names and the prefix value from this screen; you will need them later when you are configuring your products. You will need to provide the schema name in the format prefix_schemaname. For example, if you used the default prefix DEV, you will supply the following schema name for the Portal schema:
DEV_PORTAL

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
Near the top of the screen, select Use same password for all schemas.

In the Password field, enter your password. Enter your password again in the Confirm Password field.

Note:
You must remember or make a note of password(s) you specify on 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 Portal, Forms, Reports, and Discoverer 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:

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

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

- wls1031_generic.jar (for all 64-bit platforms)

The 32-bit executable files are bundled with the appropriate JDK version. If you use the 64-bit installer, you will need to invoke the installer with a supported JDK for your platform. This JDK must be installed on your system before you install Oracle WebLogic Server. Refer to the Oracle Fusion Middleware certification document for a list of supported JDKs for your platform:

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.

- Examples on a 32-bit system:
On Linux:

./wls1031_linux32.bin

On Windows:

wls1031_win32.exe

- Examples on a 64-bit system:
On UNIX:

JAVA_HOME/bin/java -jar wls1031_generic.jar

or

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

On Windows:

JAVA_HOME\bin\java -jar wls1031_generic.jar

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.

3. Welcome Screen
Click Next.

4. Choose Middleware Home Directory Screen
Select Create a new Middleware Home.

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_11 and Oracle JRockit SDK 1.6.0_05. If you want to perform a Typical installation, select Typical and click Next to go to the Choose Product Installation Directories Screen.

A Custom installation gives you the choice of selecting the following components for installation:

- Core Application Server

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

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

It is recommended that you use the Sun SDK if you are installing in a development environment. Typically, this environment provides a more relaxed security configuration and enables you to auto-deploy applications. In a development environment, boot.properties is used for user names and passwords and polling is used for application deployment.

If you are installing in a production environment, it is recommended that you use the Oracle JRockit SDK. Production environments are for applications running in their final form. Full security is enabled and applications may be clustered or use other advanced features. In this mode, user names and passwords are required and polling is not used for application deployment.

Click Next.

7. Choose Product Installation Directories Screen

Specify the desired location for your WebLogic Server 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
No action is required on this screen; the installer will automatically advance to the next screen when installation is complete.

11. Installation Complete Screen
De-select Run Quickstart.

Click Done.

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

2.1.5 Installing Oracle Internet Directory

Oracle Portal requires an existing Oracle Internet Directory (OID) with Oracle Single Sign-On (SSO). If you are also installing Oracle Forms, Reports, or Discoverer, you will have the option to configure these products with an OID, but it is not mandatory.

The following OID/SSO combinations are supported:

- Oracle Internet Directory 10g (10.1.4.3) with Oracle Single Sign-On 10g (10.1.4.3)

- Oracle Internet Directory 11g (11.1.1) with Oracle Single Sign-On 10g (10.1.4.3)

If you are not able to use an existing 10g Oracle SSO server, follow this sequence of steps to add a new Oracle SSO server:

1. Install either Oracle Internet Directory 10g (10.1.4.3) or Oracle Internet Directory 11g (11.1.1) on your system.

2. Install Oracle Single Sign-On 10g (10.1.4.3) on your system in a different Oracle Home location than your Oracle Internet Directory installation.
Either during or after you install Oracle Single Sign-On, you must hook up Oracle Single Sign-On with your Oracle Internet Directory installation. For more information, see Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

If you installed Oracle Internet Directory 11g (11.1.1), you can also refer to Oracle Fusion Middleware Quick Installation Guide for Oracle Identity Management.

3. Test your Oracle Single Sign-On configuration to make sure that it is working properly.

4. Install Oracle Portal, Forms, Reports and Discoverer 11g Release 1 (11.1.1). During configuration, you will be able to hook up your installation with Oracle Single Sign-On.

2.1.6 Upgrading Oracle Web Agent (OWA) for Oracle Portal

Oracle Fusion Middleware 11g Release 1 (11.1.1) includes a new version of the Oracle Web Agent (OWA) packages. Existing packages will be updated to the new version the first time either an Oracle Portal 11g repository is installed or when an existing Oracle Portal repository is upgraded to 11g. When the OWA update takes place, packages from existing Oracle Portal schemas that reside in the same database will become invalid. The OWA update ends with an attempt to revalidate all invalid packages in all Oracle Portal schemas in the existing database instance.

For more information about upgrading OWA, refer to "Updating the Oracle Web Agent (OWA) Packages During an Oracle Portal Upgrade" in Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.

2.2 Install and Configure Java Access Bridge (Windows Only)

If you are installing on a Windows system, you have the option of installing and configuring Java Access Bridge for Section 508 Accessibility. For more information on how to do this, refer to "Install and Configure Java Access Bridge (Windows Only)" in Oracle Fusion Middleware Administrator's Guide.

The JAWS screen reader scripts for the Oracle Forms Builder are installed in the ORACLE_HOME\forms\ScreenReader directory.

2.3 Installing on DHCP Hosts

If you are installing Oracle Portal, Forms, Reports and Discoverer 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 Portal, Forms, Reports and Discoverer 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 Portal, Forms, Reports and Discoverer on a multihomed computer. A multihomed computer is associated with multiple IP addresses. This is typically achieved by having multiple network cards on the computer. Each IP address is associated with a host name; additionally, you can set up aliases for each hostname.

The installer picks up the fully qualified domain name from the first entry in /etc/hosts (on UNIX) or %SYSTEMROOT%\system32\drivers\etc\hosts (on Windows) file.

For details about WebLogic Server network configuration, refer to "Configure network connections" in Oracle Fusion Middleware Oracle WebLogic Server Administration Console Help.

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

2.6 Installing Oracle Forms and Oracle Reports on Separate Servers

If you choose to install Oracle Forms and Oracle Reports on different servers, you must perform some manual configuration in order for these two products to be able to communicate properly with each other.

The instructions for doing so are available in section 17.8.1, "Communication Between Reports and Forms When Installed on Different Instances" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.

2.7 Installation Instructions

This section contains information and instructions for installing Oracle Portal, Forms, Reports and Discoverer. The following topics are covered:

- Section 2.7.1, "Installation Types"

- Section 2.7.2, "Installation Log Files"

- Section 2.7.3, "Starting the Installer"

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

- Section 2.7.5, "Installation Instructions for "Install and Configure" Install Type"

- Section 2.7.6, "Installation Instructions for "Install Only" Install Type"

- Section 2.7.7, "Manual Configuration for Oracle Discoverer (Windows Only)"

2.7.1 Installation Types

The Oracle Portal, Forms, Reports and Discoverer installer provides two installation options:

- Installation Instructions for "Install and Configure" Install Type

- Installation Instructions for "Install Only" Install Type

The Install and Configure option installs the product binaries in an Oracle Home directory and creates and configures a working instance in an Oracle Instance directory. After this is complete, you should be able to access the Welcome Page to begin configuring and managing your products.

Instructions for this installation type are provided in Section 2.7.5, "Installation Instructions for "Install and Configure" Install Type".

The Install Software - Do Not Configure option only installs the software binaries in an Oracle Home directory. You must then manually run the Configuration Tool from your ORACLE_HOME/bin (for UNIX) or ORACLE_HOME\bin (for Windows) directory to configure your products before you can use them. This option can be used to quickly create multiple instances of the software that share a common disk.

Instructions for this installation type are provided in Section 2.7.6, "Installation Instructions for "Install Only" Install Type".

Note:
If you choose this installation type on Windows, there are manual configuration steps required for Oracle Discoverer. For more information, see Section 2.7.7, "Manual Configuration for Oracle Discoverer (Windows Only)".

2.7.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (for UNIX) or Oracle_Inventory_Location\logs (for Windows) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

- Linux: /etc/oraInst.loc

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

On Windows 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

- installdate-time-stamp.out

- installActionsdate-time-stamp.log

- installProfiledate-time-stamp.log

- oraInstalldate-time-stamp.err

- oraInstalldate-time-stamp.log

2.7.3 Starting the Installer

To start the installer, insert the CD-ROM and run the following command:

On UNIX:

./runInstaller

On Windows:

setup.exe

2.7.4 Inventory Screens (UNIX Only)

If you are installing on a UNIX system, and if this is the first time any Oracle product is being installed on your system with the Oracle Universal Installer, you will be asked to provide the location of an inventory directory. This is where the installer will set up subdirectories and maintain inventory data for each Oracle product that is installed on this system.

Follow the instructions in Table 2-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.7.5 Installation Instructions for "Install and Configure" Install Type

Follow the instructions in Table 2-3 to install and configure Oracle Portal, Forms, Reports and Discoverer.

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 Portal, Forms, Reports and Discoverer 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

Select Installation Type Screen

Always

Select Install and Configure.

Click Next to continue.

3

Prerequisite Checks Screen

Always

Click Next to continue.

4

Select Domain Screen

Always

Select whether you want to create a new domain, extend an existing domain, or expand an existing cluster.

NOTE - Only existing domains configured by the Oracle Portal, Forms, Reports, and Discoverer installer can be extended.

For more information about domains, see "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

5

Specify E-mail for Security Updates Screen

Always

If you choose to configure Oracle Configuration Manager, provide your E-mail address to be informed of the latest product issues.

Click Next to continue.

6

Specify Installation Location Screen

Always

Specify the Middleware Home, Oracle Home, and Oracle Instance locations, along with the Oracle Instance name. The Oracle Home location must be inside the Middleware Home directory.

For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

7

Configure Components Screen

Always

Select the component(s) you want to configure.

Click Next to continue.

8

Configure Ports Screen

Always

Select whether you want automatic or manual port configuration.

NOTE - If you choose to use the staticports.ini (or any custom port file), port numbers less than 1024 will not be validated by the installer. You will, however, be able to proceed with the installation.

See "Port Numbers" in Oracle Fusion Middleware Administrator's Guide for more information.

Click Next to continue.

9

Specify Proxy Details Screen

Only if Oracle Reports is selected on the Configure Components Screen.

Specify whether or not you want to use a proxy server.

Click Next to continue.

10

Specify Schema Screen

Only if Create Domain or Extend Domain are selected on the Select Domain Screen, and only if Oracle Portal or Oracle Discoverer are selected on the Configure Components Screen.

Specify the connection string to your database and Portal and Discoverer schema names and passwords.

Click Next to continue.

11

Specify Portlet Schema Screen

Only if Create Domain or Extend Domain are selected on the Select Domain Screen, and only if Oracle Portal is selected on the Configure Components Screen.

Specify the connection string to your database and Portlet schema names and passwords.

Click Next to continue.

12

Specify Application OID Screen

If any one of Oracle Portal, Forms, Reports, and Discoverer is selected on the Configure Components Screen.

Specify the connection credentials for your LDAP server.

For Oracle Portal, this screen is mandatory. For Oracle Forms, Reports, and Discoverer, configuring an LDAP server is optional.

Click Next to continue.

13

Installation Summary Screen

Always

Verify the information on this screen.

Click Install to begin the installation.

14

Installation Progress Screen

Always

If you are installing on a UNIX system, you will be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions.

15

Configuration Progress Screen

Always

None.

16

Install Completed Screen

Always

Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time.

After saving your configuration information, click Finish to dismiss the installer.

2.7.6 Installation Instructions for "Install Only" Install Type

Follow the instructions in Table 2-4 to install Oracle Portal, Forms, Reports and Discoverer.

If you need additional help with any of the installation screens, refer to Appendix A, "Oracle Portal, Forms, Reports and Discoverer Installation Screens" or click Help to access the online help.

Table 2-4 Installation Flow for Install Only Option

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Select Installation Type Screen

Select Install Software - Do Not Configure.

Click Next to continue.

3

Prerequisite Checks Screen

Click Next to continue.

4

Specify Installation Location Screen

Specify the Middleware Home and Oracle Home locations.

For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

5

Specify E-mail for Security Updates Screen

Provide your E-mail address to be informed of the latest product issues.

Click Next to continue.

6

Installation Summary Screen (Install Only Option)

Verify the information on this screen.

Click Install to begin the installation.

7

Installation Progress Screen

If you are installing on a UNIX system, you will be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions.

8

Install Completed Screen

Click Finish to dismiss the installer.

After the installation is complete, you must configure the components. This is done by running a separate configuration tool.

On UNIX systems:

ORACLE_HOME/bin/config.sh

On Windows systems:

ORACLE_HOME\bin\config.bat

Note:
Make sure the Oracle Portal, Forms, Reports, and Discoverer installer is not running; running the installer and Configuration Tool concurrently is not supported.

After you have started the Configuration Tool, follow the instructions in Table 2-5.

Table 2-5 Configuration Tool 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

Select Domain Screen

Always

Select whether you want to create a new domain, extend an existing domain, or expand an existing cluster.

NOTE - Only existing domains configured by the Oracle Portal, Forms, Reports, and Discoverer installer can be extended.

For more information about domains, see "WebLogic Server Domain" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

4

Specify E-mail for Security Updates Screen

Always

Provide your email address to be informed of the latest product issues.

Click Next to continue.

5

Specify Installation Location Screen

Always

Specify the WebLogic Server directory, Oracle Instance location, and Oracle Instance name.

For more information about these directories, see "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide.

Click Next to continue.

6

Configure Components Screen

Always

Select the component(s) you want to configure.

Click Next to continue.

7

Configure Ports Screen

Always

Select whether you want automatic or manual port configuration.

NOTE - If you choose to use the staticports.ini (or any custom port file), port numbers less than 1024 will not be validated by the installer. You will, however, be able to proceed with the installation.

See "Port Numbers" in Oracle Fusion Middleware Administrator's Guide for more information.

Click Next to continue.

8

Specify Proxy Details Screen

Only if Oracle Reports is selected on the Configure Components Screen.

Specify whether or not you want to use a proxy server.

Click Next to continue.

9

Specify Schema Screen

Only if Create Domain or Extend Domain are selected on the Select Domain Screen, and only if Oracle Portal or Oracle Discoverer are selected on the Configure Components Screen.

Specify the connection string to your database and Portal and Discoverer schema names and passwords.

Click Next to continue.

10

Specify Portlet Schema Screen

Only if Create Domain or Extend Domain are selected on the Select Domain Screen, and only if Oracle Portal is selected on the Configure Components Screen.

Specify the connection string to your database and Portlet schema names and passwords.

Click Next to continue.

11

Specify Application OID Screen

If any one of Oracle Portal, Forms, Reports, and Discoverer is selected on the Configure Components Screen.

Specify the connection credentials for your LDAP server.

For Oracle Portal, this screen is mandatory. For Oracle Forms, Reports, and Discoverer, configuring an LDAP server is optional.

Click Next to continue.

12

Installation Summary Screen

Always

Verify the information on this screen.

Click Configure to begin the configuration.

13

Configuration Progress Screen

Always

None.

14

Install Completed Screen

Always

Click Save to save your configuration information to a file. This information includes port numbers, installation directories, URLs, and component names which you may need to access at a later time.

After saving your configuration information, click Finish to dismiss the installer.

2.7.7 Manual Configuration for Oracle Discoverer (Windows Only)

If Oracle Discoverer is installed and configured using the Install Software - Do Not Configure option and Configuration Tool, some manual steps need to be performed to create the Windows registry entries for Oracle Discoverer Administrator and Oracle Discoverer Desktop. Run the following java command to do so:

java -classpath ORACLE_HOME_DIR\discoverer\lib\disco-config.jar;ORACLE_HOME_DIR\oui\jlib\OraInstaller.jar;ORACLE_HOME_DIR\opmn\lib\iasprovision.jar -D java.library.path=ORACLE_HOME_DIR\oui\lib\win32\oraInstaller.dll oracle.disco.install.config.DiscoUtil -oraclehome ORACLE_HOME_DIR -tnsadmin TNS_ADMIN_DIR

- Replace ORACLE_HOME_DIR with the full path to your Oracle Portal, Forms, Reports, and Discoverer Oracle Home directory.

- Replace TNS_ADMIN_DIR with the path to the directory where the tnsnames.ora file is located. If this file does not already exist, create it and supply the directory in place of the TNS_ADMIN_DIR variable.

- The Java class path must be set properly with the -classpath parameter.

- The java.library.path must be set to the directory containing OraInstaller.dll.

2.8 Verifying the Installation

After you have successfully run the installer and configuration wizard, you can verify the status of your installation by performing any combination of the following:

- Verifying the Installation Logs

- Verifying the Domain Server Logs

- Verifying OPMN Status

- Checking Browser URLs

2.8.1 Verifying the Installation Logs

Check for the presence of installation log files in logs directory inside your Oracle Inventory directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the ORACLE_HOME/oraInst.loc file. On Windows systems, the default location for the inventory directory is C:\Program Files\Oracle\Inventory\logs.

For more information about the installation log files, refer to Section D.2.1, "Installation Log Files".

2.8.2 Verifying the Domain Server Logs

Check the domain server logs, which are located in the servers directory inside the domain home directory. For example, on UNIX systems:

ORACLE_HOME/user_projects/domains/domain_name/servers/server_name

On Windows systems:

ORACLE_HOME\user_projects\domains\domain_name\servers\server_name

2.8.3 Verifying OPMN Status

Run the opmnctl status command from the INSTANCE_HOME/bin (for UNIX) or INSTANCE_HOME\bin (for Windows) directory in your instance home location. The example below shows the output on a UNIX system:

> ./opmnctl status

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |     pid | status
---------------------------------+--------------------+---------+---------
emagent_asinst_1                 | EMAGENT            |   11849 | Alive
wc1                              | WebCache-admin     |   11333 | Alive
wc1                              | WebCache           |   11332 | Alive
ohs1                             | OHS                |   11207 | Alive

This information shows the components configured for this installation. The status "Alive" means the component is up and running.

You can also run the opmnctl status -l command to obtain a list of ports used by the components. The example below shows the output on a UNIX system:

> ./opmnctl status -l

Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
ias-component                    | process-type       |     pid | status   |        uid |  memused |    uptime | ports
---------------------------------+--------------------+---------+----------+------------+----------+-----------+------
emagent_asinst_1                 | EMAGENT            |   11849 | Alive    | 1133259606 |     4204 |   0:09:38 | N/A
wc1                              | WebCache-admin     |   11333 | Alive    | 1133259605 |    43736 |   0:15:35 | http_admin:8091
wc1                              | WebCache           |   11332 | Alive    | 1133259604 |    63940 |   0:15:35 | http_stat:8092,http_invalidation:8093,https_listen:8094,http_listen:8090
ohs1                             | OHS                |   11207 | Alive    | 1133259603 |    50744 |   0:15:43 | https:8889,https:8890,http:8888

2.8.4 Checking Browser URLs

The Install Completed Screen contains URLs that can be used to access your installed and configured products, as shown in Table 2-6:

Table 2-6 Oracle Portal, Forms, Reports, and Discoverer Product URLs

Product or Component

URL

Administration Server Console

http://host:port/console

Enterprise Manager Console

http://host:port/em

Enterprise Manager Agent

http://host:port/emd/main

Oracle Portal

http://host:port/portal/pls/portal

Oracle Forms

http://host:port/forms/frmservlet

Oracle Reports

http://host:port/reports/rwservlet

Oracle Discoverer Viewer

http://host:port/discoverer/viewer

3 Deinstalling Oracle Portal, Forms, Reports, and Discoverer

This chapter describes how to remove Oracle Portal, Forms, Reports, and Discoverer 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 chapter will ensure that the software is properly removed. See Section 3.3, "Reinstallation" for more information.

The following topics are covered:

- Section 3.1, "Deinstallation Options"

- Section 3.2, "Deinstallation Instructions"

- Section 3.3, "Reinstallation"

3.1 Deinstallation Options

The Oracle Portal, Forms, Reports and Discoverer deinstaller gives you the following software removal options:

- Deinstall Oracle Home
This option removes everything under the Oracle Home from which the deinstaller is started. Be sure that no system components are using the Oracle Home you want to remove.

- Deinstall ASInstances managed by WebLogic Domain
This options removes instances of your system components that are managed by a WebLogic domain. You will need to specify credentials to access your WebLogic domain.

- Deinstall Unmanaged ASInstances
This option removes instances of your system components not associated with a WebLogic domain.

3.2 Deinstallation Instructions

This section contains information and instructions for removing Oracle Portal, Forms, Reports and Discoverer. This procedure involves the following:

- Stopping Oracle Fusion Middleware

- Removing the Oracle Portal and Oracle Discoverer Schemas

- Removing Oracle Portal, Forms, Reports and Discoverer

- Removing Oracle WebLogic Server

- Removing Oracle JDeveloper

- Removing the Oracle Home and JDeveloper Home Directories

3.2.1 Stopping Oracle Fusion Middleware

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

1. Stop all system components using the following opmnctl command. Make sure the ORACLE_HOME environment variable is set to the Oracle Home directory from your Application Developer installation.

opmnctl stopall

2. Stop all Java components using WLST:

stopApplication(appName)

For example, to stop Oracle Directory Integration Platform (DIP):

stopApplication("DIP")

3. Stop the WebLogic Managed Servers.
On UNIX:

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

On Windows:

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

4. Stop WebLogic Administration Server.
On UNIX:

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

On Windows:

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

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.

3.2.2 Removing the Oracle Portal and Oracle Discoverer Schemas

Run the Repository Creation Utility (RCU) to drop the Oracle Portal and Oracle Discoverer schemas from your database.

3.2.2.1 Starting RCU

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

On UNIX:

./rcu

On Windows:

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) or rcuHome\bin (on Windows) directory on your system.

3.2.2.2 Instructions for Dropping the Oracle Portal and Oracle Discoverer Schemas

Follow the instructions below to drop the 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 Oracle Portal and Oracle Discoverer schemas. See Section 2.1.3, "Create Schemas for Oracle Portal and Oracle Discoverer" 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.

3.2.3 Removing Oracle Portal, Forms, Reports and Discoverer

Follow the instructions in this section to deinstall Oracle Portal, Forms, Reports and Discoverer.

3.2.3.1 Starting the Deinstaller

Go to the ORACLE_HOME/oui/bin (for UNIX) or ORACLE_HOME\oui\bin (for Windows) directory and start the deinstaller.

On UNIX:

./runInstaller.sh -deinstall

On Windows:

setup.exe -deinstall

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

3.2.3.2 Deinstallation Screens and Instructions

Follow the instructions in this Table 3-1 to deinstall Oracle Portal, Forms, Reports, and Discoverer.

Table 3-1 Deinstallation Flow

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Select Deinstallation Type Screen

Select the type of installation you want to perform.

- If you select Deinstall Oracle Home, perform Steps 3-5 in the Deinstall Oracle Home section of this table.

- If you select Deinstall ASInstances managed by WebLogic Domain, perform Steps 3-7 in the Deinstall AS Instances managed by WebLogic Domain section of this table.

- If you select Deinstall unmanaged ASInstances, perform Steps 3-6 in the Deinstall Unmanaged AS Instances section of this table.

Deinstall Oracle Home

3

Deinstall Oracle Home Screen

Verify the Oracle Home directory that is about the be deinstalled.

Click Deinstall to continue.

4

Deinstall Progress Screen

This screen shows the progress and status of the deinstallation.

5

Deinstall Complete Screen

Click Finish to dismiss the screen.

Deinstall AS Instances managed by WebLogic Domain

3

Specify WebLogic Domain Detail Screen

Specify the credentials of your WebLogic Domain.

Click Next to continue.

4

Select Instance or Home Screen

Select the Oracle Home or Oracle Instance you want to deinstall.

Click Next to continue.

5

Deinstallation Summary (Managed Instance)

Verify the information on this screen.

Click Deinstall to continue.

6

Deinstall Progress Screen

This screen shows the progress and status of the deinstallation.

7

Deinstall Complete Screen

Click Finish to dismiss the screen.

Deinstall Unmanaged AS Instances

3

Specify AS Instance Location Screen

Specify the location of your unmanaged Oracle Instance.

Click Next to continue.

4

Deinstallation Summary (Unmanaged Instance)

Verify the information on this screen.

Click Deinstall to continue.

5

Deinstall Progress Screen

This screen shows the progress and status of the deinstallation.

6

Deinstall Complete Screen

Click Finish to dismiss the screen.

3.2.4 Removing Oracle WebLogic Server

To deinstall Oracle WebLogic Server:

1. Start the deinstaller from the WebLogic_Home/uninstall (for UNIX) or WebLogic_Home\uninstall (for Windows) 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.

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

3.2.6 Removing the Oracle Home and JDeveloper Home Directories

Manually remove the Oracle Home directory and all sub-directories. For example, if your Oracle Home directory was /home/Oracle/Middleware/Oracle_Portal on a UNIX system:

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

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

Repeat this procedure for your Oracle JDeveloper installation directories, as the deinstaller removes the software but not all of the installation directories. Before doing so, make sure you save any projects that you do not want to delete.

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

- Oracle Portal 11g - Home1

- Oracle WebLogic

3.3 Reinstallation

The installer does not allow reinstallation of Oracle Portal, Forms, Reports, and Discoverer in a directory that already contains an Oracle instance. To reinstall Oracle Portal, Forms, Reports, and Discoverer in the same directory as before, you must follow the instructions in this chapter to deinstall the software, then follow the instructions in Chapter 2, "Installing Oracle Portal, Forms, Reports and Discoverer" to reinstall the software.

A Oracle Portal, Forms, Reports and Discoverer Installation Screens

This appendix contains screenshots and descriptions for all of the Oracle Portal, Forms, Reports and Discoverer installation screens:

- Specify Inventory Directory Screen (UNIX Only)

- Inventory Location Confirmation Screen (UNIX Only)

- Welcome Screen

- Configuration Tool Welcome Screen

- Select Installation Type Screen

- Prerequisite Checks Screen

- Select Domain Screen

- Specify E-mail for Security Updates Screen

- Specify Installation Location Screen

- Configure Components Screen

- Configure Ports Screen

- Specify Proxy Details Screen

- Specify Schema Screen

- Specify Portlet Schema Screen

- Specify Application OID Screen

- Installation Summary Screen

- Installation Summary Screen (Install Only Option)

- Installation Progress Screen

- Configuration Progress Screen

- Install Completed Screen

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.

Click OK to continue.

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.

Click OK to continue.

A.3 Welcome Screen

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

Before continuing, make sure that you have created the necessary schemas for the products you want to install, and that you have also installed and configured WebLogic Server. For more information, refer to Section 2.1, "Before You Begin...".

Click Next to continue.

A.4 Configuration Tool Welcome Screen

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

Before continuing, make sure that you have created the necessary schemas for the products you want to install, and that you have also installed and configured WebLogic Server.

Click Next to continue.

A.5 Select Installation Type Screen

Select the type of installation you want to perform.

- Install and Configure
Select this option to have the installer create an Oracle Home directory where the software will be installed, and an Oracle Instance directory where a working instance of the software will be created.

After the installation is complete, you can modify the configured instance using Enterprise Manager or WebLogic Server Administration Console.

- Install Software - Do Not Configure
Select this option to have the installer create an Oracle Home directory where the software will be installed. After the installation, you must run the Configuration Tool separately to configure a working instance.

Click Next to continue.

A.6 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 errors or warnings and continue with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

When you are finished, click Next to continue.

A.7 Select Domain Screen

Use this screen to create a new WebLogic domain, extend an existing domain, or expand a cluster. For more information about these concepts, refer to the Oracle Fusion Middleware Installation Planning Guide.

Specify the following to create a new WebLogic domain:

- User Name
Specify the user name. The default user name is weblogic.

- User Password
Specify the user password. Valid passwords are 5 to 30 characters long, must begin with an alphabetic character, use only alphanumeric, underscore (_), dollar ($) or pound (#) characters and include at least one number.

- Confirm Password
Enter the same user password again.

- Domain Name
Specify the name of the domain you want to create. Domain names may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters.

If an existing domain is detected, you will have the option of extending the existing domain to add the products and services you are installing. To extend an existing domain, select Extend Domain and specify the following:

Note:
Only existing domains configured by the Oracle Portal, Forms, Reports, and Discoverer installer can be extended.

- Host Name
Specify the name of the machine where the domain is located.

- Port
Specify the port number on the host where the domain can be accessed.

- User Name
Specify the user name. The default user name is weblogic.

- User Password
Specify the user password. Valid passwords are 5 to 30 characters long, must begin with an alphabetic character, use only alphanumeric, underscore (_), dollar ($) or pound (#) characters and include at least one number.

You can also choose Expand Cluster to add managed servers for high availability and replication. Provide the following credentials:

- Host Name
Specify the name of the machine where the cluster is located.

- Port
Specify the port number on the host where the cluster can be accessed.

- User Name
Specify the user name. The default user name is weblogic.

- User Password
Specify the user password. Valid passwords are 5 to 30 characters long, must begin with an alphabetic character, use only alphanumeric, underscore (_), dollar ($) or pound (#) characters and include at least one number.

Click Next to continue.

A.8 Specify E-mail for Security Updates Screen

Enter your E-mail address if you want to receive the latest product information and security updates. If you have a My Oracle account and wish to receive updates via this mechanism, select I wish to receive security updates via My Oracle Support, then enter your account password.

If you do not wish to register for Oracle Configuration Manager, leave all the fields on this screen blank. You will be prompted to confirm your selection with the following screen:

Click Yes to confirm that you do not want to install Oracle Configuration Manager.

When you are finished, click Next to continue.

A.9 Specify Installation Location Screen

The contents of this screen differ depending on how you access this screen. There are three possibilities:

- You selected Install and Configure on the Select Installation Type Screen.
If this is the case, go to Section A.9.1, "Install and Configure Option".

- You selected Install Software - Do Not Configure on the Select Installation Type Screen.
If this is the case, go to Section A.9.2, "Install Only - Do Not Configure Option".

- You ran the Configuration Tool from the ORACLE_HOME/bin (on UNIX) or ORACLE_HOME\bin (on Windows) directory.
If this is the case, go to Section A.9.3, "Configuration Tool Option".

Refer to "Oracle Fusion Middleware Directory Structure and Concepts" in Oracle Fusion Middleware Installation Planning Guide for more information about these directories.

After you are finished supplying the various installation locations, click Next to continue.

A.9.1 Install and Configure Option

If you selected the Install and Configure option on the Select Installation Type Screen, specify the following installation locations:

- Oracle Middleware Home Location
The absolute path to the directory where WebLogic Server was installed.

- Oracle Home Directory
The directory name for your Oracle Home:

- You can specify a directory that already exists; this must be 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).

- You can specify a pre-existing Oracle Home directory (for example, you are reinstalling the software into an existing Oracle Home that was created from a previous installation that was incomplete).

- You can specify the name of a new directory that will be created for you inside the Middleware Home.

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

Note:
This installation directory will be referred to as ORACLE_HOME throughout the remainder of this document.

- WebLogic Server Location
The directory name for your WebLogic Server Home. This directory will automatically be created inside the Middleware Home. The default name for this directory is wlserver_10.3.

- Oracle Instance Location
The absolute path to the directory where your Oracle Instance will reside. This is where application configuration files reside and where the application process runs from. Runtime components write only to this location.

- Oracle Instance Name
Specify the unique name of your Oracle Instance. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be 4 to 30 characters in length.

A.9.2 Install Only - Do Not Configure Option

If you selected the Install Software - Do Not Configure option on the Select Installation Type Screen, you specify the following installation locations:

- Oracle Middleware Home
The absolute path to the directory where WebLogic Server was installed.

- Oracle Home Directory
The directory name for your Oracle Home:

- You can specify a directory that already exists; this must be 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).

- You can specify a pre-existing Oracle Home directory (for example, you are reinstalling the software into an existing Oracle Home that was created from a previous installation that was incomplete).

- You can specify the name of a new directory that will be created for you inside the Middleware Home.

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

Note:
This installation directory will be referred to as ORACLE_HOME throughout the remainder of this document.

A.9.3 Configuration Tool Option

If you are running the Configuration Tool from the $ORACLE_HOME/bin directory, specify the following installation locations:

- WebLogic Server Location
The absolute path to the directory where WebLogic Server was installed.

- Oracle Instance Location
The absolute path to the directory where your Oracle Instance will reside. This is where application configuration files reside and where the application process runs from. Runtime components write only to this location.

- Oracle Instance Name
Specify the unique name of your Oracle Instance. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be 4 to 30 characters in length.

A.10 Configure Components Screen

This screen shows the products and components that are available for configuration. What appears on this screen depends on what you selected on the Select Domain Screen:

- If you selected Create Domain on the Select Domain Screen, all components in the Oracle Portal, Forms, Reports, and Discoverer suite of products will appear on this screen.

- If you selected Extend Domain on the Select Domain Screen, only those components that do not already exist in the domain will be available on this screen, in order for you to add functionality and services to your existing domain.

- If you selected Expand Cluster on the Select Domain Screen, only those components that already exist in the domain will be available on this screen, in order for you to perform your replication for high availability.

Select the component(s) you want to configure. Notice in the bottom pane that there is prerequisite information depending on which component(s) you select. Be sure you read this information carefully before you continue.

Select Clustered if you want to be able to extend your domain or expand the cluster at some later point in time for the selected components. If this is a stand-alone installation on a single machine, then you can de-select this option.

Click Next to continue.

A.11 Configure Ports Screen

Select Auto Port Configuration if you want the installer to automatically assign the default ports to the components. For a list of default port numbers, refer to Oracle Fusion Middleware Administrator's Guide.

Select Specify Ports Using Configuration File if you have already created a port configuration file that specifies the port numbers that you want to use for each component. Enter the full part and filename of this file in the Filename field, or click Browse to locate an existing file on your system.

A default file called staticports.ini is provided in the Disk1/stage/Response directory on the CD-ROM. You can use this file as a template to create your own custom ports file.

Note:
If you choose to use the staticports.ini (or any custom port file), port numbers less than 1024 will not be validated by the installer. You will, however, be able to proceed with the installation.
See "Port Numbers" in Oracle Fusion Middleware Administrator's Guide for more information.

After providing the location and name of a valid file, click View/Edit File to view or edit the contents of the file.

Click Next to continue.

A.12 Specify Proxy Details Screen

This screen is only visible if Oracle Reports was selected on the Configure Components Screen.

If your computer is located behind a firewall you may need to route outgoing HTTP connections through a proxy server. If you have a direct connection to the Internet or if you do not wish to configure a proxy server at this time, click Next.

If you are configuring a proxy server, you must provide the following information:

- HTTP Proxy Host
Enter the host name of your proxy server.

- HTTP Proxy Port
Enter the port number of your proxy server.

- Bypass proxy for address
Enter addresses for which the proxy server should be bypassed. Use commas (,) to separate multiple entries. Domains may be listed using asterisk (*). For example:

*.us.oracle.com,*.in.oracle.com

Click Next to continue.

A.13 Specify Schema Screen

This screen is only visible if Server Components was selected on the Configure Components Screen.

Provide the database connection details and schema information for the Portal and Discoverer, whichever was selected on the Configure Components Screen.

In the Database Connect String field, specify the connection credentials to your database in the following format:

hostname:port:servicename

In the table, specify the name and password for the schema(s).

Click Next to continue.

A.14 Specify Portlet Schema Screen

This screen is only visible if Oracle Portal was selected on the Configure Components Screen, and your database contains 11g Release 1 (11.1.1) schemas. If your database contains schema from 10g Release 2 (10.1.2) or earlier, you will not see this screen.

In the table, specify the name and password for the Portlet schema.

Click Next to continue.

A.15 Specify Application OID Screen

If you selected Oracle Portal on the Configure Components Screen, you must provide credentials to connect to an Internet Directory server that is up and running. Specify the following credentials:

- Hostname
Enter the host name of your LDAP server.

- Port
Enter the port number of your LDAP server. If you do not know the port number, you can run the netstat -an command from the command line to see the port numbers currently being used.

- User Name
Enter an existing LDAP user name with superuser privileges. The default user name is cn=orcladmin.

- Password
Enter the LDAP user password.

If you did not select Oracle Portal on the Configure Components Screen, and you want to configure your component to use an existing Internet Directory server, select Use Application Level Identity Store and enter the credentials to connect to the server.

Select Configure the LDAP Server in secure mode to configure the LDAP server in secure mode. Be sure to specify the secure port number in the Port field if you select this option.

Click Next to continue.

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

A.17 Installation Summary Screen (Install Only Option)

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.

A.18 Installation Progress Screen

This screen shows you the progress of the installation.

If you are installing on a UNIX system, you may be asked to run the ORACLE_HOME/oracleRoot.sh script as root user before the installation is completed:

This script sets up the proper permissions for the files and directories being installed.

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.19 Configuration Progress Screen

This screen shows you the progress of the component configuration.

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 and warning messages and continue with the installation, click Continue.

Click Abort to stop prerequisite checking for all components.

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

A.20 Install Completed Screen

This screen summarizes the installation that was just completed.

The end of the summary information on this screen contains the various URLs to access the Administration Console as well as your installed products. You should write these URLs down so you can access your products later.

Note:
This summary information does not appear on the Installation Complete screen if you chose Install Software - Do Not Configure on the Select Installation Type Screen.

Or, you can click Save to save your configuration information to a file. This information includes port numbers, installation directories, disk space usage, URLs, and component names which you may need at a later time.

Click Finish to dismiss the screen.

B Oracle Portal, Forms, Reports and Discoverer Deinstallation Screens

This appendix contains screenshots and descriptions for all of the Oracle Portal, Forms, Reports and Discoverer deinstallation screens:

- Welcome Screen

- Select Deinstallation Type Screen

- Deinstall Oracle Home Screen

- Specify WebLogic Domain Detail Screen

- Select Instance or Home Screen

- Specify AS Instance Location Screen

- Deinstallation Summary (Managed Instance)

- Deinstallation Summary (Unmanaged Instance)

- Deinstall Progress Screen

- Deinstall Complete Screen

B.1 Welcome Screen

The Welcome screen is the first screen you see when the deinstaller is started.

Click Next to continue.

B.2 Select Deinstallation Type Screen

Select the type of deinstallation you want to perform:

- Deinstall Oracle Home
Select this option to deinstall all binaries in the specified Oracle Home directory (the directory from which you started the deinstaller).

- Deinstall ASInstances managed by WebLogic Domain
Select this option to deinstall a specific Oracle Instance and its system components that are registered to a WebLogic Domain.

- Deinstall Unmanaged ASInstances
Select this option to deinstall all unmanaged Oracle Instances and their system components.

Click Next to continue.

B.3 Deinstall Oracle Home Screen

This screen only appears if you selected Deinstall Oracle Home on the Select Deinstallation Type 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.

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

B.4 Specify WebLogic Domain Detail Screen

This screen only appears if you selected Deinstall ASInstances managed by WebLogic Domain on the Select Deinstallation Type Screen.

Specify the WebLogic Domain credentials:

- WebLogic Home
The absolute path to your WebLogic Home directory. If you are unsure where this directory is located, click Browse to find the directory on your system.

- Domain Host Name
The name of the machine on which the WebLogic Domain is running.

- Domain Port No
Listen port number of the domain. The default port number is 7001.

- User Name
The WebLogic Domain user name.

- Password
The password of the WebLogic Domain user.

Click Next to continue.

B.5 Select Instance or Home Screen

This screen only appears if you selected Deinstall ASInstances managed by WebLogic Domain on the Select Deinstallation Type Screen.

Select the Oracle Home or Oracle Instance you want to deinstall. If you select an Oracle Home directory with multiple instances, all instances inside the Oracle Home will be deinstalled.

Click Next to continue.

B.6 Specify AS Instance Location Screen

This screen only appears if you selected Deinstall Unmanaged ASInstances on the Select Deinstallation Type Screen.

Specify the full path to your Oracle Instance directory. If you are unsure, click Browse to find this directory on your system.

Click Next to continue.

B.7 Deinstallation Summary (Managed Instance)

This screen shows you the instance you are about to deinstall.

Verify that this is correct, then click Deinstall to begin the deinstallation.

B.8 Deinstallation Summary (Unmanaged Instance)

This screen shows you the instance you are about to deinstall.

Verify that this is correct, then click Deinstall to begin the deinstallation.

B.9 Deinstall Progress Screen

This screen shows you the progress of the deinstallation.

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

B.10 Deinstall Complete Screen

This screen summarizes the deinstallation that was just completed.

Click Finish to dismiss the screen.

C Silent Installation

This appendix describes how to install Oracle Portal, Forms, Reports, and Discoverer from the command line in silent mode. This appendix contains the following topics:

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

- Section C.2, "Creating Response Files"

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

- Section C.4, "Silent Installation Instructions"

C.1 What is a Silent Installation?

Silent installation eliminates the need to monitor the Oracle Portal, Forms, Reports, and Discoverer installation because no graphical output is displayed and no input by the user is required.

Silent installation of Oracle Portal, Forms, Reports, and Discoverer 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 Portal, Forms, Reports, and Discoverer you must create the oraInst.loc file before starting. Please refer to Section C.3.1, "UNIX Users: Creating the oraInst.loc File" for more information.
Following installation of Oracle Portal, Forms, Reports, and Discoverer, 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 Portal, Forms, Reports, and Discoverer, you must create the registry keys before starting. Registry key creation is described in Section C.3.2, "Windows Users: Creating the Registry Key"

C.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 C-1 lists the response files provided in the Disk1/stage/Response directory on the installation CD-ROM:

Table C-1 Oracle Portal, Forms, Reports and Discoverer Installation and Configuration Response File Templates

Template

Description

deinstall.rsp

This is the template response file that should be used if you want to do a silent deinstallation.

See Section C.2.1, "Contents of the deinstall.rsp File" to view the contents of this file.

configure_only.rsp

This is the template response file that should be used if you have already installed the software on your system, and now need to configure the products to either create or extend a domain.

The equivalent using the GUI would be to run the config.sh (for UNIX) or config.bat (for Windows) script from the ORACLE_HOME/bin (for UNIX) or ORACLE_HOME\bin (for Windows) directory.

See Section C.2.2, "Contents of the configure_only.rsp File" to view the contents of this file.

install_only.rsp

This is the template response file that should be used if you only want to install the software on your system.

The equivalent using the GUI would be selecting Install Software - Do Not Configure option on the Select Installation Type Screen.

See Section C.2.3, "Contents of the install_only.rsp File" to view the contents of this file.

install_and_configure.rsp

This is the template response file that should be used if you want to install and configure the software on your system.

The equivalent using the GUI would be selecting Install and Configure option on the Select Installation Type Screen.

See Section C.2.4, "Contents of the install_and_configure.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.

C.2.1 Contents of the deinstall.rsp File

This section shows the contents of the Disk1/stage/Response/deinstall.rsp response file:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#
OH_HOME_DEINSTALL=false

#
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=true

#
UNMANAGED_ASINSTANCE_DEINSTALL=false

#
DEINSTALL_IN_ASINSTANCE_MODE=true

#
DEINSTALL INSTANCE LIST=

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

#
MIDDLEWARE_HOME=

#
WEBLOGIC_HOME=

#
DOMAIN_HOST_NAME=

#
DOMAIN_PORT_NO=7001

#
DOMAIN_USER_NAME=weblogic

#
DOMAIN_USER_PASSWORD=

#
MANAGED_INSTANCE_LIST=

C.2.2 Contents of the configure_only.rsp File

This section shows the contents of the Disk1/stage/Response/configure_only.rsp response file:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Set this to true if you want to create a new domain, all other required variables need to be provided. If this is set to true then variables "EXTEND_DOMAIN" and "EXPAND_CLUSTER" must be set to false, since the variables are mutually exclusive.
CREATE_DOMAIN=true

#Set this to true if you want to extend an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_DOMAIN" and "EXPAND_CLUSTER" must be set to false, since the variables are mutually exclusive.
EXTEND_DOMAIN=false

#Set this to true if you want to expand a cluster in an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_DOMAIN" and "EXTEND_DOMAIN" must be set to false, since the variables are mutually exclusive.
EXPAND_CLUSTER=false

#Write the name of the domain you want to create. Domain name may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters.
DOMAIN_NAME=

#Write the name of the host to which you want to connect. It should have an already existing domain configured.
DOMAIN_HOSTNAME=

#Give the port number at which the host should be connected.
DOMAIN_PORT=

#Give an administrator user name for the domain if you are creating a new one otherwise give the administrator user name for the domain configured at the host.
ADMIN_USER_NAME=weblogic

#Give an administrator password for the domain if you are creating a new one otherwise give the administrator password for the domain configured at the host.
ADMIN_PASSWORD=

#Write the administrator password again to confirm.
ADMIN_CONFIRM_PASSWORD=

#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=

#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=

#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=false

#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=true
#Provide the Proxy Host
PROXY_HOST=

#Provide the Proxy Port
PROXY_PORT=

#Provide the Proxy Username
PROXY_USER=

#Provide the Proxy Password
PROXY_PWD=

#Give the complete path to a valid Middleware Home with WebLogic Server installed.
MW_HOME=

#Give the complete path to a valid WebLogic Server Home for the corresponding Middleware Home entered.
WL_HOME=

#Give the complete path for an Oracle Home to be created. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character.
ORACLE_HOME=

#Give the complete path for an Oracle Instance directory to be created. This is the location where the software configuration files and runtime processes will reside.
INSTANCE_HOME=

#Give a name for Oracle Instance corresponding to the Instance Home. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be from 4 to 30 characters in length.
INSTANCE_NAME=asinst_1

#Set this to true if you want the configuration wizard to assign the ports automatically.
AUTOMATIC_PORT_DETECT=true

#Give the location for the file containing the list of static ports if you manually want to assign ports.
STATICPORT INI FILE LOCATION=

#Set this to true if you do not want to use proxy.
DO NOT USE PROXY SETTINGS=true

#Set this to true if you do want to use proxy.
ENABLE PROXY=false

#Give the host name for proxy settings.
PROXY HOST NAME=

#Give the port for proxy settings.
PROXY PORT NO=

#Give the bypass addresses for proxy settings.
PROXY BY PASS ADDRESS=
#Give the connection string to establish a connection to a database.
DATABASE_CONNECTION_STRING=

#Set this to true if you want to register Discoverer Schema, schema name and password details need to be provided.
REGISTER_DISCOVERER_SCHEMA=true

#Give the Discoverer Schema Name.
DISCOVERER_SCHEMA_NAME=

#Give the Portal Schema Name.
PORTAL_SCHEMA_NAME=

#Give the Discoverer Schema Password.
DISCOVERER_SCHEMA_PASSWORD=

#Give the Portal Schema Password.
PORTAL_SCHEMA_PASSWORD=

#Set this to true if you want to register Portlet Schema, schema name and password details need to be provided.
REGISTER_PORTLET_SCHEMA=true

#Give the Portlet Schema Name.
PORTLET_SCHEMA_NAME=

#Give the Portlet Schema Password.
PORTLET_SCHEMA_PASSWORD=

#Set this to true if you want to use Application OID. It has to be true you are configuring Oracle Portal.
USE_OID=true

#Give the Application OID hostname.
OID_HOST=

#Give the Application OID port.
OID_PORT=

#Give the Application OID user name.
OID_USERNAME=cn=orcladmin

#Give the Application OID password.
OID_PASSWORD=

#Set this to true if you want to use Application OID in SSL mode.
OID_USE_SSL=false

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]
#Set this to true if you want to configure Oracle Portal. "CONFIGURE_WEBCACHE" and "CONFIGURE_OHS" must also be set to true then as Oracle Portal Configuration is dependent on them.
CONFIGURE_PORTAL=true

#Set this to true if you want to configure Oracle Forms
CONFIGURE_FORMS=true

#Set this to true if you want to configure Oracle Reports
CONFIGURE_REPORTS=true

#Set this to true if you want to configure Oracle Discoverer. "CONFIGURE_OHS" must also be set to true then as Oracle Discoverer Configuration is dependent on it.
CONFIGURE_DISCO=true

#Set this to true if you want to configure Oracle Forms Builder. "CONFIGURE_FORMS" must also be set to true then as Oracle Forms Builder Configuration is dependent on it.
CONFIGURE_FORMS_BUILDER=false

#Set this to true if you want to configure Oracle Reports Builder. "CONFIGURE_REPORTS" must also be set to true then as Oracle Reports Builder Configuration is dependent on it.
CONFIGURE_REPORTS_BUILDER=false

#Set this to true if you want to configure Oracle HTTP Server.
CONFIGURE_OHS=true

#Set this to true if you want to configure Oracle Webcache. "CONFIGURE_OHS" must also be set to true then as Oracle Webcahce Configuration is dependent on it.
CONFIGURE_WEBCACHE=true

#Set this to true if you want to configure Oracle Enterprise Manager.
ENTERPRISE_MANAGEMENT=true

#Set this to true if you want to create a cluster for the selected applications
CREATE_CLUSTERED=true

C.2.3 Contents of the install_only.rsp File

This section shows the contents of the Disk1/stage/Response/install_only.rsp response file:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Set this to true if installation and configuration need to be done, all other required variables need to be provided. Variable "INSTALL AND CONFIGURE LATER TYPE" must be set to false if this is set to true as the variables are mutually exclusive
INSTALL AND CONFIGURE TYPE=false

#Set this to true if only Software only installation need to be done. If this is set to true then variable "INSTALL AND CONFIGURE TYPE" must be set to false, since the variables are mutually exclusive.
INSTALL AND CONFIGURE LATER TYPE=true

#Give the complete path for an Oracle Home to be created. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character.
ORACLE_HOME=

#Write the complete path to a valid Middleware Home.
MW_HOME=

#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=

#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=

#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=false

#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=true

#Provide the Proxy Host
PROXY_HOST=

#Provide the Proxy Port
PROXY_PORT=

#Provide the Proxy Username
PROXY_USER=

#Provide the Proxy Password
PROXY_PWD=

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

C.2.4 Contents of the install_and_configure.rsp File

This section shows the contents of the Disk1/stage/Response/install_and_configure.rsp response file:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Set this to true if installation and configuration need to be done, all other required variables need to be provided. Variable "INSTALL AND CONFIGURE LATER TYPE" must be set to false if this is set to true as the variables are mutually exclusive
INSTALL AND CONFIGURE TYPE=true

#Set this to true if only Software only installation need to be done. If this is set to true then variable "INSTALL AND CONFIGURE TYPE" must be set to false, since the variables are mutually exclusive.
INSTALL AND CONFIGURE LATER TYPE=false

#Set this to true if you want to create a new domain, all other required variables need to be provided. If this is set to true then variables "EXTEND_DOMAIN" and "EXPAND_CLUSTER" must be set to false, since the variables are mutually exclusive.
CREATE_DOMAIN=true

#Set this to true if you want to extend an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_DOMAIN" and "EXPAND_CLUSTER" must be set to false, since the variables are mutually exclusive.
EXTEND_DOMAIN=false

#Set this to true if you want to expand a cluster in an already existing domain, all other required variables need to be provided. If this is set to true then variables "CREATE_DOMAIN" and "EXTEND_DOMAIN" must be set to false, since the variables are mutually exclusive.
EXPAND_CLUSTER=false

#Write the name of the domain you want to create. Domain name may only contain alphanumeric characters, or the underscore (_) or hyphen (-) characters.
DOMAIN_NAME=

#Write the name of the host to which you want to connect. It should have an already existing domain configured.
DOMAIN_HOSTNAME=

#Give the port number at which the host should be connected.
DOMAIN_PORT=

#Give an administrator user name for the domain if you are creating a new one otherwise give the administrator user name for the domain configured at the host.
ADMIN_USER_NAME=weblogic

#Give an administrator password for the domain if you are creating a new one otherwise give the administrator password for the domain configured at the host.
ADMIN_PASSWORD=

#Write the administrator password again to confirm.
ADMIN_CONFIRM_PASSWORD=

#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=

#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=false

#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=true

#Provide the Proxy Host
PROXY_HOST=

#Provide the Proxy Port
PROXY_PORT=

#Provide the Proxy Username
PROXY_USER=

#Provide the Proxy Password
PROXY_PWD=

#Give the complete path to a valid Middleware Home with WebLogic Server installed.
MW_HOME=

#Give the complete path to a valid WebLogic Server Home for the corresponding Middleware Home entered.
WL_HOME=

#Give the complete path for an Oracle Instance directory to be created. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character.
ORACLE_HOME=

#Give the complete path for an Oracle Instance directory to be created. This is the location where the software configuration files and runtime processes will reside.
INSTANCE_HOME=

#Give a name for Oracle Instance corresponding to the Instance Home. The Oracle Instance name may only contain alphanumeric and underscore (_) characters, it must begin with an alphabetic (a-z or A-Z) character, and must be from 4 to 30 characters in length.
INSTANCE_NAME=asinst_1

#Set this to true if you want the configuration wizard to assign the ports automatically.
AUTOMATIC_PORT_DETECT=true

#Give the location for the file containing the list of static ports if you manually want to assign ports.
STATICPORT INI FILE LOCATION=

#Set this to true if you do not want to use proxy.
DO NOT USE PROXY SETTINGS=true

#Set this to true if you do want to use proxy.
ENABLE PROXY=false

#Give the host name for proxy settings.
PROXY HOST NAME=

#Give the port for proxy settings.
PROXY PORT NO=
#Give the bypass addresses for proxy settings.
PROXY BY PASS ADDRESS=

#Give the connection string to establish a connection to a database.
DATABASE_CONNECTION_STRING=

#Set this to true if you want to register Discoverer Schema, schema name and password details need to be provided.
REGISTER_DISCOVERER_SCHEMA=true

#Give the Discoverer Schema Name.
DISCOVERER_SCHEMA_NAME=

#Give the Portal Schema Name.
PORTAL_SCHEMA_NAME=

#Give the Discoverer Schema Password.
DISCOVERER_SCHEMA_PASSWORD=

#Give the Portal Schema Password.
PORTAL_SCHEMA_PASSWORD=

#Set this to true if you want to register Portlet Schema, schema name and password details need to be provided.
REGISTER_PORTLET_SCHEMA=true

#Give the Portlet Schema Name.
PORTLET_SCHEMA_NAME=

#Give the Portlet Schema Password.
PORTLET_SCHEMA_PASSWORD=

#Set this to true if you want to use Application OID. It has to be true you are configuring Oracle Portal.
USE_OID=true

#Give the Application OID hostname.
OID_HOST=

#Give the Application OID port.
OID_PORT=

#Give the Application OID user name.
OID_USERNAME=cn=orcladmin

#Give the Application OID password.
OID_PASSWORD=

#Set this to true if you want to use Application OID in SSL mode.
OID_USE_SSL=false

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]
#Set this to true if you want to configure Oracle Portal. "CONFIGURE_WEBCACHE" and "CONFIGURE_OHS" must also be set to true then as Oracle Portal Configuration is dependent on them.
CONFIGURE_PORTAL=true

#Set this to true if you want to configure Oracle Forms
CONFIGURE_FORMS=true

#Set this to true if you want to configure Oracle Reports
CONFIGURE_REPORTS=true

#Set this to true if you want to configure Oracle Discoverer. "CONFIGURE_OHS" must also be set to true then as Oracle Discoverer Configuration is dependent on it.
CONFIGURE_DISCO=true

#Set this to true if you want to configure Oracle Forms Builder. "CONFIGURE_FORMS" must also be set to true then as Oracle Forms Builder Configuration is dependent on it.
CONFIGURE_FORMS_BUILDER=false

#Set this to true if you want to configure Oracle Reports Builder. "CONFIGURE_REPORTS" must also be set to true then as Oracle Reports Builder Configuration is dependent on it.
CONFIGURE_REPORTS_BUILDER=false

#Set this to true if you want to configure Oracle HTTP Server.
CONFIGURE_OHS=true

#Set this to true if you want to configure Oracle Webcache. "CONFIGURE_OHS" must also be set to true then as Oracle Webcahce Configuration is dependent on it.
CONFIGURE_WEBCACHE=true

#Set this to true if you want to configure Oracle Enterprise Manager.
ENTERPRISE_MANAGEMENT=true

#Set this to true if you want to create a cluster for the selected applications
CREATE_CLUSTERED=true

C.2.5 Securing Your Silent Installation

Your response files contain certain passwords required by the installer. To find the places in the response file where passwords are required, search for the password string and replace the corresponding <Value Required> string with the actual password. These passwords are stored in the response file clear text format. 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.

C.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 C.3.1, "UNIX Users: Creating the oraInst.loc File"

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

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

C.3.2 Windows Users: Creating the Registry Key

If you have not installed Oracle Portal, Forms, Reports, and Discoverer 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

C.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 C-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=/home/Oracle/Middleware/as_1

Session Variables

Session variables are specified using session:varName=value.

Component Variables

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

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

> ./runInstaller -silent -response file -invPtrLoc file

Below is a full example of this command:

> ./runInstaller -silent -response /home/jdoe/response/oracle.classicwls.top.Custom.rsp -invPtrLoc /home/jdoe/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:

> ./runInstaller -silent -response file

Below is a full example of this command:

> ./runInstaller -silent -response /home/jdoe/response/oracle.classicwls.top.Custom.rsp

C.4.2 Sample Output

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

Platform is Linux X86 32 bit
Starting Oracle Universal Installer...

Checking Temp space: must be greater than 80 MB.   Actual 66993 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 4030 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2009-04-29_12-59-35PM. Please wait ...[kh
wang@dadvmn0789 Disk1]$ Log: /scratch/khwang/oraInventory/logs/install2009-04-29_12-59-35PM.log
Copyright Â© 1982, 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
Checking for openmotif-2.2.3; found openmotif-2.2.3-10.2.el4-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 Portal, Forms, Reports and Discoverer 11g completed successfully.

D Troubleshooting

This appendix describes solutions to common problems that you might encounter when installing Oracle Portal, Forms, Reports, and Discoverer. It contains the following sections:

- Section D.1, "General Troubleshooting Tips"

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

- Section D.3, "Associating Oracle Reports When Extending a Domain"

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

D.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 3, "Deinstalling Oracle Portal, Forms, Reports, and Discoverer".

3. Correct the issue that caused the error.

4. Restart the installation.

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

D.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (for UNIX) or Oracle_Inventory_Location\logs (for Windows) directory. On UNIX systems, if you do not know the location of your Oracle Inventory directory, you can find it in the oraInst.loc file in the following directories (default locations):

- Linux: /etc/oraInst.loc

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

On Windows 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

- installdate-time-stamp.out

- installActionsdate-time-stamp.log

- installProfiledate-time-stamp.log

- oraInstalldate-time-stamp.err

- oraInstalldate-time-stamp.log

If you start the installer with the -printtime parameter, the timeTakendate-time-stamp.log file is created in the same directory.

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

% ./config.sh -log=log_filename

On Windows:

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 ORACLE_HOME/common/bin (for UNIX) or ORACLE_HOME\common\bin (for Windows) directory.

D.3 Associating Oracle Reports When Extending a Domain

For security reasons, Oracle Reports is installed with permissions that enable only the installer to use it. However, there are instances when other users in the group would need access to Oracle Reports (for example, if you extend the domain and add Oracle Portal). Follow the steps below to modify the permissions for additional users.

1. Change the permissions in the following directories to allow read and write access for the desired user (on UNIX systems, use the chmod 750 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary):

- ORACLE_HOME/bin

- ORACLE_HOME/bin/rwbuilder

- ORACLE_INSTANCE

- ORACLE_INSTANCE/bin

- ORACLE_INSTANCE/config

- ORACLE_INSTANCE/config/FRComponent

- ORACLE_INSTANCE/bin/config/ReportsToolsComponent

- ORACLE_INSTANCE/bin/config/ReportsToolsComponent/ReportsTools

2. Change the permissions of the ORACLE_INSTANCE/bin/config/ReportsToolsComponent/ReportsTools/rwbuilder.conf file to give read, write, and execute permissions to the desired user (on UNIX systems, use the chmod 770 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

3. Change the permissions of the DOMAIN_HOME/servers/WLS_REPORTS/stage directory to give read and write permissions to the desired user (on UNIX systems, use the chmod 750 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

4. Change the permissions of the DOMAIN_HOME/servers/WLS_REPORTS/stage/reports/reports/web.war file to give read, write, and execute permissions to the desired user (on UNIX systems, use the chmod 770 command; on Windows systems, right-click on the folder and select Properties, then modify the security settings as necessary).

5. In the ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/logging.xml file, change the location of the log files so that the desired user will have read and write privileges. Edit the PATH property of runtime_trace_handler and zrcclient_trace_handler.

D.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  E  I  J  L  M  N  O  P  R  S  T  U  V  W

A

accessibility

Java Access Bridge, 2.2

accessibility software, Java Access Bridge, A Administration Server

stopping, 3.2.1

B

browser URLs, 2.8.4

C

certification information, 2.1.1

cluster

expanding, A.7

clusters

expanding, 2.7.5

configuration log files, D.2.2 Configuration Tool, 2.7.1

location, 2.7.1

running, 2.7.6

configuring a proxy, A.12 configuring ports, 2.7.5 createCentralInventory.sh script, A.2 creating a WebLogic Domain, 2.7.5, A.7 creating schemas for Oracle Portal and Oracle Discoverer, 2.1.3 creating the registry key, C.1

D

default port numbers, A.11

deinstallation options, 3.1

deinstallation types, 3.1, B.2

deinstalling Oracle Portal, Forms, Reports and Discoverer, B

development environment, 2.1.4

DHCP host, 2.3

documentation conventions, Preface

domains

See WebLogic Domains

downloading RCU, 2.1.3 dropping the schemas, 3.2.2

E

expanding a cluster, 2.7.5, A.7

extending a WebLogic Domain, 2.7.5, A.7

associating Oracle Reports, D.3

I

install type

selecting, A.5

installation directory structure, 1.3 installation instructions, 2, 2.7 installation location

specifying, A.9

installation log files, 2.7.2, D.2.1 installation overview, 1 installation roadmap, 1.2 installation types, 2.7.1 installing on a multihomed computer, 2.5 installing Oracle WebLogic Server, 2.1.4 inventory screens, 2.7.4

J

Java Access Bridge, 2.2

Java components

stopping, 3.2.1

JDeveloper Home

removing, 3.2.6

JDKs, 2.1.4

L

log files

for configuration, D.2.2

for installation, 2.7.2, D.2.1

loopback adapter

installing for Windows, 2.3.3

removing for Windows, 2.3.4

M

managed servers

stopping, 3.2.1

mapping tablespaces in RCU, 2.1.3 Middleware Home, A.9.1 Middleware Home directory

creating the Middleware Home directory, 2.1.4

specifying the location of, 2.1.4

multihomed computer, 2.5 My Oracle account, A.8 My Oracle Support, D.4

N

non-interactive installations, C

O

OPMN status, 2.8.3

opmnctl command, 2.8.3

Oracle Business Intelligence Discoverer, 1.1

overview, 1.1

Oracle Configuration Manager, 2.7.5, A.8 Oracle database, 2.1.2 Oracle Discoverer

creating schemas, 2.1.3

manual configuration, 2.7.7

required schemas, 2.1.3

Oracle Forms Services, 1.1

overview, 1.1

Oracle Fusion Middleware

stopping, 3.2.1

Oracle Home, 2.7.5, A.9.1

removing, 3.2.6

Oracle Instance, 2.7.5 Oracle Instance location, A.9.1 Oracle Instance name, A.9.1 Oracle Internet Directory (OID)

installing, 2.1.5

Oracle Inventory, 2.7.4

finding the default location on UNIX systems, 2.7.2

finding the default location on Windows systems, 2.7.2

Oracle Inventory location, A.1 Oracle JDeveloper

removing, 3.2.5

Oracle Portal, 1.1

creating schemas, 2.1.3

overview, 1.1

required schemas, 2.1.3

Oracle Portal, Forms, Reports and Discoverer

certification information, 2.1.1

creating schemas, 2.1.3

creating the Middleware Home directory, 2.1.4

creating the WebLogic Home directory, 2.1.4

deinstallation screens, B

deinstalling, 3, B

directory structure, 1.3

installation instructions, 2.7

installation overview, 1

installing on a multihomed computer, 2.5

installing on DHCP host, 2.3

installing on separate servers, 2.6

installing Oracle WebLogic Server, 2.1.4

JDKs, 2.1.4

products overview, 1.1

reinstalling, 3.3

required schemas, 2.1.3

silent installation, C

system requirements, 2.1.1

types of installation, 2.7.1

verifying the installation, 2.8

Oracle Reports, 1.1

services, 1.1

Oracle Single Sign-On (SSO)

installing, 2.1.5

Oracle Technology Network, 2.1.3, D.1 Oracle Web Agent (OWA)

upgrading for Oracle Portal, 2.1.6

Oracle WebLogic Server, 2.1.4

download location, 2.1.4

installer file name, 2.1.4

removing, 3.2.4

starting the installer, 2.1.4

oracleRoot.sh script, 2.7.5 oraInst.loc file, 2.7.2, C.1, D.2.1 oraInventory directory, A.1 overview of installation, 1

P

port configuration, 2.7.5, A.11

production environment, 2.1.4

proxy

configuring, A.12

R

receiving security updates, A.8

registry key

creating, C.1

reinstalling Oracle Portal, Forms, Reports and Discoverer, 3.3 removing Oracle JDeveloper, 3.2.5 removing Oracle WebLogic Server, 3.2.4 removing the JDeveloper Home directory, 3.2.6 removing the Oracle Home directory, 3.2.6 Repository Creation Utility

downloading, 2.1.3

mapping tablespaces, 2.1.3

starting, 2.1.3, 3.2.2.1

required schemas, 2.1.3 response file

creating, A.16

response files, C.1, C.2

creating, C.2

pre-existing, C.2

roadmap for installation, 1.2 root access, Preface root.sh script, C.1

S

saving configuration information, 2.7.5

saving your installation and configuration information, A.16

schema

specifying, A.13

schemas

dropping, 3.2.2

securing, C.2.5 securing your silent installation, C.2.5 security updates

signing up for, A.8

silent installation, C, C.1, C.2.5

sample commands, C.4.1

sample output, C.4.2

specifying schema, A.13 starting RCU, 2.1.3, 3.2.2.1 starting the deinstaller, 3.2.3.1

on Windows systems, 3.2.3.1

starting the installer, 2.7.3 staticports.ini file, 2.7.5, A.11 stopping Java components, 3.2.1 stopping managed servers, 3.2.1 stopping Oracle Fusion Middleware, 3.2.1 stopping system components, 3.2.1 stopping the Administration Server, 3.2.1 system components

stopping, 3.2.1

system requirements, 2.1.1

T

troubleshooting, D

types of deinstallation, 3.1, B.2

U

upgrading Oracle Web Agent (OWA) for Oracle Portal, 2.1.6

URLs to help verify installation, 2.8.4

V

verifying the installation, 2.8

W

WebLogic Domain

creating, 2.7.5, A.7

extending, 2.7.5, A.7

WebLogic Home directory, 2.1.4 WebLogic Server directory, A.9.1

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.