Oracle® Fusion Middleware

Installation Guide for Oracle Portal, Forms, Reports and Discoverer

11g Release 1 (11.1.1)

E10421-06

May 2011

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

E10421-06

Copyright © 2011, 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

2 Installing Oracle Portal, Forms, Reports and Discoverer

- 2.1 Preparing to Install

- 2.1.1 Installing and Configuring a Database and Database Schemas

- 2.1.2 Installing Oracle WebLogic Server

- 2.1.2.1 Finding Oracle WebLogic Server Installation Instructions

- 2.1.2.2 Planning Your Middleware Home Location for Oracle Reports (Windows Only)

- 2.1.2.3 Stopping Node Manager Before Installing Oracle Portal, Forms, Reports and Discoverer (Windows Only)

- 2.1.3 Oracle Fusion Middleware Support of 64-bit JDK

- 2.1.4 Installing on AIX Operating Systems

- 2.1.5 Installing Oracle Internet Directory

- 2.1.5.1 Using Your Existing Oracle Internet Directory 10g Environment

- 2.1.5.2 Upgrading Oracle Internet Directory 10g to 11g

- 2.1.5.3 Building a New Oracle Identity Management Architecture

- 2.1.5.4 Integrating Oracle Portal, Forms, Reports and Discoverer with Oracle Internet Directory

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

- 2.1.7 Installing Oracle Forms and Oracle Reports on Separate Servers

- 2.1.8 Installing in a Middleware Home with Existing Fusion Middleware Products

- 2.1.8.1 Setting the StartScriptEnabled Property for Node Manager

- 2.1.8.2 Managing Potential Port Conflicts

- 2.2 Installation Types

- 2.3 Installation Instructions

- 2.3.1 Obtaining the Software

- 2.3.2 Starting the Installer

- 2.3.2.1 Run the rootpre.sh Script on IBM AIX Operating Systems

- 2.3.2.2 Start the Installer

- 2.3.2.3 Installation Log Files

- 2.3.3 Inventory Screens (UNIX Only)

- 2.3.4 Installing and Configuring the Latest Version of Oracle Portal, Forms, Reports and Discoverer

- 2.3.4.1 Installation Instructions

- 2.3.4.2 Patching the Software

- 2.3.4.3 Configuring Your Components

- 2.3.5 Manual Configuration for Oracle Discoverer (Windows Only)

- 2.4 Verifying the Installation

- 2.4.1 Verifying the Installation Logs

- 2.4.2 Verifying the Domain Server Logs

- 2.4.3 Verifying OPMN Status

- 2.4.4 Checking Browser URLs

3 Installing Oracle Discoverer Desktop

- 3.1 Preparing to Install

- 3.2 Installation Instructions

- 3.2.1 Starting the Installer

- 3.2.2 Installation Log Files

- 3.2.3 Installation Screens and Instructions

- 3.3 Starting Your Products

4 Deinstalling Oracle Portal, Forms, Reports and Discoverer

- 4.1 Deinstallation Options

- 4.2 Deinstallation Instructions

- 4.2.1 Stopping Oracle Fusion Middleware

- 4.2.2 Removing the Oracle Portal and Oracle Discoverer Schemas

- 4.2.3 Removing Oracle Portal, Forms, Reports and Discoverer

- 4.2.3.1 Starting the Deinstaller

- 4.2.3.2 Removing Your Oracle Instances

- 4.2.3.3 Removing Your Oracle Home

- 4.2.3.4 Removing the Oracle Common Home

- 4.2.4 Manually Removing the Oracle Home Directory

- 4.2.5 Removing Oracle WebLogic Server

- 4.2.6 Removing Oracle JDeveloper

- 4.2.7 Removing the Program Groups (Windows Only)

- 4.2.8 Rebooting Your System (Windows Only)

- 4.3 Reinstallation

5 Deinstalling Oracle Discoverer Desktop

- 5.1 Deinstallation Instructions

- 5.2 Manually Removing the Oracle Home Directory

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 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 Installation Complete Screen

B Oracle Discoverer Desktop Installation Screens

- B.1 Welcome Screen

- B.2 Prerequisite Checks Screen

- B.3 Specify Installation Location Screen

- B.4 Select Components Screen

- B.5 Installation Summary Screen

- B.6 Installation Progress Screen

- B.7 Installation Completed Screen

C Oracle Portal, Forms, Reports and Discoverer Deinstallation Screens

- C.1 Welcome Screen

- C.2 Select Deinstallation Type Screen

- C.3 Deinstall Oracle Home Screen

- C.4 Specify WebLogic Domain Detail Screen

- C.5 Select Managed Instance Screen

- C.6 Specify Instance Location Screen

- C.7 Deinstallation Summary (Managed Instance)

- C.8 Deinstallation Summary (Unmanaged Instance)

- C.9 Deinstallation Progress Screen

- C.10 Deinstallation Complete Screen

D Oracle Discoverer Desktop Deinstallation Screens

- D.1 Welcome Screen

- D.2 Deinstall Oracle Home Screen

- D.3 Deinstallation Progress Screen

- D.4 Deinstallation Complete Screen

E Silent Installation and Deinstallation

- E.1 About Silent Installation and Deinstallation

- E.2 Oracle Portal, Forms, Reports and Discoverer Response Files

- E.2.1 Silent Installation Response Files

- E.2.1.1 Contents of the configure_only.rsp File

- E.2.1.2 Contents of the install_only.rsp File

- E.2.1.3 Contents of the install_and_configure.rsp File

- E.2.2 Patch Set Installer Response Files

- E.2.3 Silent Deinstallation Response Files

- E.2.3.1 Contents of the deinstall_managed_instances.rsp File

- E.2.3.2 Contents of the deinstall_unmanaged_instances.rsp File

- E.2.3.3 Contents of the deinstall_oh.rsp File

F Troubleshooting

- F.1 General Troubleshooting Tips

- F.2 Installation and Configuration Log Files

- F.2.1 Installation Log Files

- F.2.2 Configuration Log Files

- F.3 Verifying Environment Variable Lengths for Oracle Reports (Windows Only)

- F.4 Granting Access to rwbuilder

- F.5 Errors Accessing the Discoverer Plus and Discoverer Viewer URLs

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

Access to Oracle Support

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"

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

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

Note:
The configuration tool for Oracle Portal, Forms, Reports and Discoverer creates your WebLogic domain in the user_projects directory inside the Middleware home; it is not possible to create your domain outside this directory.

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

Task 1 - Prepare your environment for installation.

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

For system requirements information, go to:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

For certification information, see System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 on the Oracle Fusion Middleware Supported System Configurations page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

For interoperability and compatibility, go to Oracle Fusion Middleware Interoperability and Compatibility Guide.

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.

The schemas for Oracle Portal and Oracle Discoverer must be created in an Oracle database. Make sure you have a supported Oracle database up and running. See System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 on the Oracle Fusion Middleware Supported System Configurations page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Instructions for creating the schemas are provided in "Creating Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide.

Task 3 - Install Oracle WebLogic Server and create a Middleware home.

Oracle Portal, Forms, Reports and Discoverer requires a Middleware home directory. The Middleware home is created during the Oracle WebLogic Server installation.

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

To download the latest Oracle WebLogic Server, see "Product Distribution" in Oracle WebLogic Server Installation Guide.

For installation instructions, see "Running the Installation Program in Graphical Mode" in 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.

Task 4 - Install but do not configure Oracle Portal, Forms, Reports and Discoverer

Use the installer to install your products.

Choose the Install Software - Do Not Configure option on the Select Installation Type Screen.

Section 2.3.4.1, "Installation Instructions".

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

Task 5 - Update your software.

Run the Patch Set Installer to update your software to the latest version.

"Applying the Latest Oracle Fusion Middleware Patch Set" in Oracle Fusion Middleware Patching Guide.

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

Run the Configuration Tool to configure your Oracle Portal, Forms, Reports and Discoverer components.

Section 2.3.4.3, "Configuring Your Components".

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, "Preparing to Install"

- Section 2.2, "Installation Types"

- Section 2.3, "Installation Instructions"

- Section 2.4, "Verifying the Installation"

2.1 Preparing to Install

Make sure you have read "Before you Begin" in Oracle Fusion Middleware Installation Planning Guide before you install Oracle Portal, Forms, Reports and Discoverer.

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

The following topics are covered in this section:

- Section 2.1.1, "Installing and Configuring a Database and Database Schemas"

- Section 2.1.2, "Installing Oracle WebLogic Server"

- Section 2.1.3, "Oracle Fusion Middleware Support of 64-bit JDK"

- Section 2.1.5, "Installing Oracle Internet Directory"

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

- Section 2.1.7, "Installing Oracle Forms and Oracle Reports on Separate Servers"

- Section 2.1.8, "Installing in a Middleware Home with Existing Fusion Middleware Products"

2.1.1 Installing and Configuring a Database and Database Schemas

Oracle Portal and Oracle Discoverer require database schemas on an Oracle database only. For more information about installing and configuring your database, see "Install and Configure a Database" in Oracle Fusion Middleware Installation Planning Guide.

Note:
Although IBM DB2 and Microsoft SQL Server databases are supported in the latest release, the schemas for Oracle Portal and Oracle Discoverer are only supported on Oracle databases. You must create the schemas for Oracle Portal and Oracle Discoverer on a certified Oracle database.

After your database is installed and configured, you need to run the Repository Creation Utility (RCU) to create the schemas for Oracle Portal and Oracle Discoverer. For instructions, see "Creating Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide.

2.1.2 Installing Oracle WebLogic Server

Oracle Portal, Forms, Reports and Discoverer requires Oracle WebLogic Server, which creates the Middleware home directory during installation. For more information, see "Oracle Fusion Middleware Directory Structure" in Oracle Fusion Middleware Installation Planning Guide.

This section contains the following topics:

- Section 2.1.2.1, "Finding Oracle WebLogic Server Installation Instructions"

- Section 2.1.2.2, "Planning Your Middleware Home Location for Oracle Reports (Windows Only)"

- Section 2.1.2.3, "Stopping Node Manager Before Installing Oracle Portal, Forms, Reports and Discoverer (Windows Only)"

2.1.2.1 Finding Oracle WebLogic Server Installation Instructions

For instructions, see "Install an Application Server" in Oracle Fusion Middleware Installation Planning Guide.

Note:
If you choose to install WebLogic Server using the Custom installation type on the "Choose Install Type" screen, you must make sure that the following components are installed in order for Oracle Discoverer to work properly:

- UDDI and Xquery Support

- WebLogic JDBC Drivers

- Third Party JDBC Drivers

2.1.2.2 Planning Your Middleware Home Location for Oracle Reports (Windows Only)

If you are going to install Oracle Reports on a Windows operating system, make sure the path to your Middleware home directory is not too long. For more information, see Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".

2.1.2.3 Stopping Node Manager Before Installing Oracle Portal, Forms, Reports and Discoverer (Windows Only)

If you are installing Oracle Portal, Forms, Reports and Discoverer on a Microsoft Windows operating system, you must make sure that the Node Manager utility that was installed with Oracle WebLogic Server is stopped before you install your Oracle Portal, Forms, Reports and Discoverer software:

1. Verify the Oracle WebLogic Server Node Manager utility is stopped. If it is running, kill the process.

2. Determine if the nodemanager.properties file is present in the WebLogic_Home\common\nodemanager directory.

1. If the nodemanager.properties file is not present, continue installing Oracle Portal, Forms, Reports and Discoverer.

2. If the nodemanager.properties file does exist, open it and verify that the ListenPort parameter is included and that it is set. If the ListenPort parameter is not included or set, edit the nodemanager.properties file so that it is similar to the following, where NODE_MANAGER_LISTEN_PORT represents the port the Node Manager listens on, such as 5556:

ListenPort=NODE_MANAGER_LISTEN_PORT

2.1.3 Oracle Fusion Middleware Support of 64-bit JDK

If you are using a 64-bit JVM in your environment, ensure that all your Oracle Fusion Middleware components are using the 64-bit JVM. You cannot mix components using a 32-bit JVM with those using a 64-bit JVM.

Refer to the System Requirements and Supported Platforms for Oracle Fusion Middleware 11gR1 document for information on the platforms that support a 64-bit JDK. This document is available on the Oracle Fusion Middleware Supported System Configurations page:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

If your Oracle Fusion Middleware components are running in a 64-bit JVM environment, ensure that WebLogic Server is installed with the 64-bit JDK. For 32-bit JVM support, refer to the Oracle Fusion Middleware Release Notes for information on how to configure your environment for 32-bit JVM support for your platform.

2.1.4 Installing on AIX Operating Systems

If you are installing Oracle Portal, Forms, Reports and Discoverer on a certified IBM AIX operating system, you must run the

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.2.3) with Oracle Single Sign-On 10g (10.1.2.3)

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

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

Note:
Oracle Single Sign-On 10g (10.1.4.3) requires a separate Oracle home if it is installed with Oracle Internet Directory 11g Release 1 (11.1.1). However, installing Oracle Single Sign-On 10g (10.1.4.3) in a separate Oracle home from Oracle Internet Directory 10g (10.1.4.3) will make it easier for you to upgrade to Oracle Internet Directory 11g Release 1 (11.1.1) later if you choose.

This section contains information for the following scenarios:

- Section 2.1.5.1, "Using Your Existing Oracle Internet Directory 10g Environment"

- Section 2.1.5.2, "Upgrading Oracle Internet Directory 10g to 11g"

- Section 2.1.5.3, "Building a New Oracle Identity Management Architecture"

2.1.5.1 Using Your Existing Oracle Internet Directory 10g Environment

If you already have a supported combination of Oracle Internet Directory 10g in place, you can leave your existing architecture as-is, or you can upgrade to the latest available 11g release. In either case, you will be able to configure Oracle Portal, Forms, Reports and Discoverer with your Oracle Internet Directory and Single Sign-On configuration.

2.1.5.2 Upgrading Oracle Internet Directory 10g to 11g

To upgrade your existing Oracle Internet Directory 10g environment, see "Upgrading Your Oracle Internet Directory Environment" in Oracle Fusion Middleware Upgrade Guide for Oracle Identity Management.

2.1.5.3 Building a New Oracle Identity Management Architecture

To build a new Oracle Identity Management architecture containing Oracle Internet Directory 11g (11.1.1) with Oracle Single Sign-On 10g (10.1.4.3), refer to the following documentation:

- "How to Install SSO with Oracle Fusion Middleware 11g" (Doc ID 1069426.1) on My Oracle Support.

- "Installing Oracle Single Sign-On and Oracle Delegated Administration Services Against Oracle Internet Directory" in Oracle Fusion Middleware Installation Guide for Oracle Identity Management.

2.1.5.4 Integrating Oracle Portal, Forms, Reports and Discoverer with Oracle Internet Directory

After your Oracle Portal instance is configured, it is automatically integrated with your Oracle Internet Directory and Oracle Single Sign-On. Oracle Forms and Oracle Reports are not automatically configured. For more information, see:

- "Using Forms Services with Oracle Single Sign-On" in Oracle Fusion Middleware Forms Services Deployment Guide.

- "Configuring and Administering OracleAS Single Sign-On" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.

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.1.7 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 "Communication Between Reports and Forms When Installed on Different Instances" in Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services.

2.1.8 Installing in a Middleware Home with Existing Fusion Middleware Products

This section contains important information if you are installing Oracle Portal, Forms, Reports and Discoverer into a Middleware home directory that already contains a Fusion Middleware product.

The following topics are covered:

- Section 2.1.8.1, "Setting the StartScriptEnabled Property for Node Manager"

- Section 2.1.8.2, "Managing Potential Port Conflicts"

2.1.8.1 Setting the StartScriptEnabled Property for Node Manager

To properly set the StartScriptEnabled property:

1. Navigate to the WebLogic_Home/common/nodemanager (on UNIX operating systems) or WebLogic_Home\common\nodemanager (on Windows operating systems) directory.

2. Edit the nodemanager.properties file and set the StartScriptEnabled property as follows:

StartScriptEnabled=true

3. Restart Node Manager.

2.1.8.2 Managing Potential Port Conflicts

The potential for port conflicts exists when you are installing Oracle Portal, Forms, Reports and Discoverer into a Middleware home with existing Fusion Middleware products, and the existing Oracle instance and WebLogic domain are shut down when you arrive at the Configure Ports Screen during your installation.

If you choose Automatic Port Configuration, the ports in your domain are allocated from a default range of port numbers. If your existing Oracle instances and domain are running, the configuration tool recognizes which ports are already actively in use and will avoid allocating these ports to the Oracle instance and domain you are currently creating with your installation.

However, if your existing instances and domains are shut down, the configuration tool will assume that the initial default port numbers are available and will assign these port numbers to the instance and domain you are creating.

In such cases, conflicts with the following ports can arise:

- The OPMN local and remote port values.

- The WebLogic Domain Administration Server port value.

These port conflicts mean that OPMN and WebLogic Administration Server can only start for one of the configurations under the Middleware home.

To proactively prevent this problem, you should leave your existing Oracle instances and WebLogic Domain up and running as you install your software and create your new Oracle instance and domain. The configuration tool will recognize which ports are already in use and will avoid allocating these ports to your new Oracle instance and WebLogic Domain.

Alternatively, you can select Specify Ports using Configuration File on the Configure Ports Screen and manually keep track of your port numbers in a staticports.ini file.

2.2 Installation Types

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

- Install and Configure
This option installs the product binaries in an Oracle home directory and creates and configures a working instance in an Oracle instance directory. The common product binaries are also copied to the oracle_common directory. After this is complete, you should be able to begin configuring and managing your products using the Administration Console or Enterprise Manager.

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

- Install Software - Do Not Configure
This option only installs the software binaries in an Oracle home directory and the common product binaries in the oracle_common directory. You must then manually run the Configuration Tool from your ORACLE_HOME/bin (on UNIX operating systems) or ORACLE_HOME\bin (on Windows operating systems) 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.

To install the latest Oracle Portal, Forms, Reports and Discoverer software, you must choose the Install Software - Do Not Configure installation type, as described in Section 1.2, "Installation Roadmap".

2.3 Installation Instructions

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

- Section 2.3.1, "Obtaining the Software"

- Section 2.3.2, "Starting the Installer"

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

- Section 2.3.4, "Installing and Configuring the Latest Version of Oracle Portal, Forms, Reports and Discoverer"

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

2.3.1 Obtaining the Software

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

Select one of the download locations and download "Portal, Forms, Reports and Discoverer." This will be saved to your system as a .zip archive file.

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

2.3.2 Starting the Installer

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

2.3.2.1 Run the rootpre.sh Script on IBM AIX Operating Systems

If you are installing on an IBM AIX operating system, you must run the rootpre.sh script from the Disk1 directory before you start the installer.

2.3.2.2 Start the Installer

On UNIX operating systems:

cd unpacked_archive_directory/Disk1
./runInstaller

On Windows operating systems:

cd unpacked_archive_directory\Disk1
setup.exe

If you are installing on an HP-UX system with a PA-RISC processor, you must specify the location of a JRE on your system as follows:

./runInstaller -jreLoc JRE_LOCATION

Refer to the Oracle Fusion Middleware Certification document to see the JDKs supported for your system:

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

2.3.2.3 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. Refer to Section F.2.1, "Installation Log Files" for more information about the log files and their contents.

2.3.3 Inventory Screens (UNIX Only)

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

Follow the instructions in Table 2-1 to configure the inventory directory information. For more help, select the screen name in the table below, or click the Help button in the GUI.

Table 2-1 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.

If you do not wish to use the Oracle central inventory, you can create a file called oraInst.loc and in this file, include the full path of the inventory directory of your choice in the oraInst.loc file. Then, you can start the installer and point to the oraInst.loc file. For example, on UNIX operating systems:

./runInstaller -invPtrLoc location_of_oraInst.loc_file

On Windows operating systems:

setup.exe -invPtrLoc location_of_oraInst.loc_file

2.3.4 Installing and Configuring the Latest Version of Oracle Portal, Forms, Reports and Discoverer

Follow the instructions in this section to install and configure the latest Oracle Portal, Forms, Reports and Discoverer software.

2.3.4.1 Installation Instructions

Follow the instructions in Table 2-2 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-2 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 Security Updates Screen

Provide your E-mail address if you want to be informed of the latest product issues by E-mail.

Provide your E-mail address and My Oracle Support password if you want to be informed of the latest product issues through the My Oracle Support web site.

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 operating system, you may be asked to run the ORACLE_HOME/oracleRoot.sh script to set up the proper file and directory permissions.

Click Next to continue.

8

Installation Complete Screen

Click Finish to dismiss the installer.

2.3.4.2 Patching the Software

After the installation is complete, you must run the Patch Set Installer for Oracle Portal, Forms, Reports and Discoverer to update your software to the latest version.

For instructions, go to "Applying the Latest Oracle Fusion Middleware Patch Set" in Oracle Fusion Middleware Patching Guide.

After you have patched your software to the latest version, you are ready to configure your components. Go to Section 2.3.4.3, "Configuring Your Components" for instructions.

2.3.4.3 Configuring Your Components

Run the Configuration Tool to create your WebLogic Domain and configure your components.

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

Table 2-3 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 - If you are creating a WebLogic domain, the domain will be created under the user_projects directory inside the Middleware home; it is not possible to create the domain outside this directory.

NOTE - If you are extending a domain, 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 Security Updates Screen

Always

Provide your E-mail address if you want to be informed of the latest product issues by E-mail.

Provide your E-mail address and My Oracle Support password if you want to be informed of the latest product issues through the My Oracle Support web site.

Click Next to continue.

5

Specify Installation Location Screen

Always

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

If you are in a scenario where you are extending a domain or expanding a cluster involving remote machines, you must make sure that the Middleware home and Oracle home directory structures are identical on all the machines.

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. You will be asked to run the oracleRoot.sh script on the Installation Summary Screen. You will only be asked to do this if you are running the Configuration Tool separately (you have already installed the software).

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

Click Next to continue.

14

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

When configuration is complete, go to Section 2.4, "Verifying the Installation".

2.3.5 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 -Djava.library.path=ORACLE_HOME_DIR\oui\lib\win32 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.4 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.4.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 F.2.1, "Installation Log Files".

2.4.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.4.3 Verifying OPMN Status

Run the opmnctl status command from the INSTANCE_HOME/bin (on UNIX operating systems) or INSTANCE_HOME\bin (on Windows operating systems) 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.4.4 Checking Browser URLs

The Installation Complete Screen contains URLs that can be used to access your installed and configured products, as shown in Table 2-4:

Table 2-4 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 Installing Oracle Discoverer Desktop

This chapter describes how to install Oracle Discoverer Desktop.

In Oracle Application Server 10g releases, Oracle Discoverer Desktop and Discoverer Administrator were included as part of the Oracle Developer's Suite. In Oracle Fusion Middleware 11g, these products are included with Oracle Portal, Forms, Reports and Discoverer.

Now, Oracle Discoverer Desktop and Discoverer Administrator are available separately with their own installer so that you can install these products more quickly. Oracle WebLogic Server and database schemas are not required for either product.

Note:
The separate installer is only available on Microsoft Windows operating systems.

The following topics are covered in this chapter:

- Section 3.1, "Preparing to Install"

- Section 3.2, "Installation Instructions"

- Section 3.3, "Starting Your Products"

3.1 Preparing to Install

Make sure you have read the System Requirements and Certification documentation to verify that your system meets the necessary minimum requirements:

- Oracle Fusion Middleware System Requirements and Specifications:

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

This document contains information related to hardware and software requirements, minimum disk space and memory requirements, and required system libraries, packages, or patches.

- Oracle Fusion Middleware Certification

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

This document contains information related to supported installation types, platforms, operating systems, databases, JDKs, and third-party products.

3.2 Installation Instructions

When you run the installer, Application Developer is installed onto your system. After the product is installed, you must run the Configuration Wizard to configure Application Developer.

This section contains the following topics:

- Section 3.2.1, "Starting the Installer"

- Section 3.2.2, "Installation Log Files"

- Section 3.2.3, "Installation Screens and Instructions"

3.2.1 Starting the Installer

To start the installer, insert the product CD-ROM. If your system is not configured for autorun, find and execute the setup.exe file.

3.2.2 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location\logs directory. Refer to Section F.2.1, "Installation Log Files" for more information about the log files and their contents.

3.2.3 Installation Screens and Instructions

Follow the instructions in Table 3-1 to install Oracle Discoverer Desktop and Discoverer Administrator.

If you need additional help with any of the installation screens, refer to Appendix B, "Oracle Discoverer Desktop Installation Screens" or click Help to access the online help.

Table 3-1 Installation Screens

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Prerequisite Checks Screen

Click Next to continue.

3

Specify Installation Location Screen

Specify the directory where you want to install the software. This directory is your Oracle home directory:

- If you specify an existing directory, make sure the directory is empty.

- If you specify a new directory, the installer will create the directory for you.

Click Next to continue.

4

Select Components Screen

Select the products you want to install.

Click Next to continue.

5

Installation Summary Screen

Verify the installation about to be performed.

Click Install to continue.

6

Installation Progress Screen

This screen shows the progress of the installation.

When the process is 100% complete, click Next to continue.

7

Installation Completed Screen

Click Finish to dismiss the screen.

3.3 Starting Your Products

After the installation is complete, you can start your software.

To run Oracle Discoverer Desktop, go to the Start menu and select All Programs > Oracle Discoverer Desktop and Admin - Home 1 > Oracle Discoverer Desktop.

To run Oracle Discoverer Administrator, go to the Start menu and select All Programs > Oracle Discoverer Desktop and Admin - Home 1 > Oracle Discoverer Administrator.

4 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 4.3, "Reinstallation" for more information.

Note:
If you need to remove a particular product component, you must remove the entire domain containing the component. It is not possible to remove a single product from a domain containing multiple products.

The following topics are covered:

- Section 4.1, "Deinstallation Options"

- Section 4.2, "Deinstallation Instructions"

- Section 4.3, "Reinstallation"

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

4.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 Program Groups (Windows Only)

- Rebooting Your System (Windows Only)

4.2.1 Stopping Oracle Fusion Middleware

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

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.

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

See "Dropping Schemas" in Oracle Fusion Middleware Repository Creation Utility User's Guide for instructions.

4.2.3 Removing Oracle Portal, Forms, Reports and Discoverer

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

4.2.3.1 Starting the Deinstaller

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

On UNIX operating systems:

./runInstaller.sh -deinstall

On Windows operating systems:

setup.exe -deinstall

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

4.2.3.2 Removing Your Oracle Instances

All managed and unmanaged Oracle Instances must be removed from the system before you remove the Oracle Home. Follow the instructions in this Table 4-1 to remove your managed Oracle Instances (these are instances that are associated with a WebLogic Domain):

Note:
To remove a managed instance, the Administration Server must be up and running.

Note:
If you want to remove an Oracle instance which is registered with a WebLogic domain, make sure to launch the deinstaller from Oracle Home directory that is associated with the Oracle instance you are removing.
The deinstaller will list all instances associated with same WebLogic domain; make sure you choose to remove the instances that are associated with the Oracle Home from where you launched the deinstaller only.

Table 4-1 Removing Managed Oracle Instances

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Select Deinstallation Type Screen

Select Deinstall ASInstances managed by WebLogic Domain.

Click Next to continue.

3

Specify WebLogic Domain Detail Screen

Specify the credentials of your WebLogic Domain.

Click Next to continue.

4

Select Managed Instance Screen

Select the managed 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

Deinstallation Progress Screen

This screen shows the progress and status of the deinstallation.

7

Deinstallation Complete Screen

Click Finish to dismiss the screen.

Follow the instructions in this Table 4-2 to remove your unmanaged Oracle Instances (these are stand-alone instances that are not associated with a WebLogic Domain):

Table 4-2 Removing Unmanaged Oracle Instances

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Select Deinstallation Type Screen

Select Deinstall unmanaged ASInstances.

Click Next to continue.

3

Specify 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

Deinstallation Progress Screen

This screen shows the progress and status of the deinstallation.

6

Deinstallation Complete Screen

Click Finish to dismiss the screen.

4.2.3.3 Removing Your Oracle Home

After all managed and unmanaged Oracle Instances have been removed, start the deinstaller again (Section 4.2.3.1, "Starting the Deinstaller") and follow the instructions in Table 4-3 to remove your Oracle home.

Table 4-3 Removing Your Oracle Home

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Select Deinstallation Type Screen

Select Deinstall Oracle Home.

Click Next to continue.

3

Deinstall Oracle Home Screen

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

Click Deinstall to continue.

On the Warning screen, select whether or not you want the deinstaller to remove the Oracle home directory in addition to removing the software.

Click Yes to have the deinstaller remove the software and Oracle home, No to remove only the software, or Cancel to return to the previous screen.

If you select No, go to Section 4.2.4, "Manually Removing the Oracle Home Directory" for instructions on how to manually remove your Oracle home directory.

4

Deinstallation Progress Screen

This screen shows the progress and status of the deinstallation.

5

Deinstallation Complete Screen

Click Finish to dismiss the screen.

4.2.3.4 Removing the Oracle Common Home

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

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

The deinstaller requires the location of a Java Runtime Environment (JRE) on your system. When you installed Oracle WebLogic Server, a JRE was installed on your system. You can use this location (the location of the jre directory) to start the installer. The default location for the JRE is MW_HOME/jdk160_18 (on UNIX operating systems) or MW_HOME\jdk160_18 (on Windows operating systems), where MW_HOME is the Middleware Home directory.

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

On UNIX operating systems:

./runInstaller -deinstall -jreLoc JRE_LOCATION

On Windows operating systems:

setup.exe -deinstall -jreLoc JRE_LOCATION

You must specify the absolute path to your JRE_LOCATION; relative paths will not work.

After the deinstaller is started, follow the instructions in Table 4-3 to remove the Oracle Common home.

4.2.4 Manually Removing the Oracle Home Directory

If you selected No on the warning screen during deinstallation, you must manually remove your Oracle home directory and any sub-directories. For example, if your Oracle Common home directory was /home/Oracle/Middleware/oracle_common on a UNIX operating system:

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

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

4.2.5 Removing Oracle WebLogic Server

Refer to "Uninstalling the Software" in Oracle WebLogic Server Installation Guide for instructions on how to remove Oracle WebLogic Server.

After this is finished, you must manually remove the Middleware home directory. For example, if your Middleware home directory was /home/Oracle/Middleware on a UNIX operating system:

> cd /home/Oracle
> rm -rf Middleware

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

4.2.6 Removing Oracle JDeveloper

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

4.2.7 Removing the Program Groups (Windows Only)

On Windows operating 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.4.0

- Oracle Portal 11g - Home1

- Oracle WebLogic

4.2.8 Rebooting Your System (Windows Only)

On Windows operating systems, you should reboot your computer after you have finished removing all your programs to ensure proper cleanup.

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

1. Follow the instructions in Section 4.2.3.2, "Removing Your Oracle Instances"to remove all Oracle instances from the directory.

2. Follow the instructions in Chapter 2, "Installing Oracle Portal, Forms, Reports and Discoverer" to reinstall the software.

5 Deinstalling Oracle Discoverer Desktop

This chapter describes how to remove Oracle Discoverer Desktop.

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.

5.1 Deinstallation Instructions

To remove Oracle Discoverer Desktop from your system, start the deinstaller by going to the Start menu and selecting All Programs > Oracle Discoverer Desktop and Admin - Home 1 > Uninstall Oracle Discoverer Desktop and Admin.

Follow the instructions in Table 5-1 to remove Oracle Discoverer Desktop and Discoverer Administrator.

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

Table 5-1 Deinstallation Screens

No.

Screen

Description and Action Required

1

Welcome Screen

Click Next to continue.

2

Deinstall Oracle Home Screen

Verify the Oracle home you are about to remove.

Click Deinstall to continue.

On the Warning screen, select whether or not you want the deinstaller to remove the Oracle home directory in addition to removing the software.

Click Yes to have the deinstaller remove the software and Oracle home, No to remove only the software, or Cancel to return to the previous screen.

If you select No, go to Section 5.2, "Manually Removing the Oracle Home Directory" for instructions on how to manually remove your Oracle home directory.

3

Deinstallation Progress Screen

This screen shows the progress and status of the deinstallation.

4

Deinstallation Complete Screen

Click Finish to dismiss the screen.

5.2 Manually Removing the Oracle Home Directory

If you selected No on the warning screen during deinstallation, you must manually remove your Oracle home directory and any sub-directories.

For example, if your Oracle home directory was C:\Oracle\Middleware\as_1, use a file manager window and navigate to the C:\Oracle\Middleware directory, then right-click on the as_1 folder and select Delete.

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

- Installation Complete 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, "Preparing to Install".

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.

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.

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.

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:

Note:
The WebLogic domain will be created in the user_projects directory inside the Middleware home; it is not possible to create the domain outside this directory.

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

A.8 Specify 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, uncheck the I wish to receive security updates via My Oracle Support box and 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 register for security updates.

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 operating systems) or ORACLE_HOME\bin (on Windows operating systems) 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.

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

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.

If you are installing Oracle Reports on a Windows operating system, make sure the path to your Middleware home directory is not too long. For more information, see Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".

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

If you are installing Oracle Reports on a Windows operating system, make sure the path to your Middleware home directory is not too long. For more information, see Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".

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

- 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 (on UNIX operating systems) or ORACLE_HOME\bin (on Windows operating systems) directory, specify the following installation locations:

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

If you are installing Oracle Reports on a Windows operating system, make sure the path to your Middleware home directory is not too long. For more information, see Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)".

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

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.

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

A.13 Specify Schema Screen

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

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

hostname:port:servicename

If you are configuring Oracle Portal, supply the Portal schema name and password that was used to create the PORTAL schema using Repository Creation Utility (RCU):

- Portal Schema
Specify the name of your Oracle Portal schema. Use the format prefix_PORTAL.

- Portal Schema Password
Specify the password for your Oracle Portal schema.

If you are configuring Oracle Discoverer, supply the Discoverer schema name and password that was used to create the DISCOVERER schema using Repository Creation Utility (RCU):

- Discoverer Schema
Specify the name of your Oracle Discoverer schema. Use the format prefix_DISCOVERER.

- Discoverer Schema Password
Specify the password for your Oracle Discoverer schema.

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.

Supply the Portlet schema name and password that was used to create the PORTLET schema using Repository Creation Utility (RCU):

- Portlet Schema
Specify the name of your Oracle Portlet schema. Use the format prefix_PORTLET.

- Portlet Schema Password
Specify the password for your Oracle Portlet schema.

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.

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 Installation Complete 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 Discoverer Desktop Installation Screens

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

- Welcome Screen

- Prerequisite Checks Screen

- Specify Installation Location Screen

- Select Components Screen

- Installation Summary Screen

- Installation Progress Screen

- Installation Completed Screen

B.1 Welcome Screen

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

B.2 Prerequisite Checks Screen

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

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

Click Abort to stop prerequisite checking for all components.

B.3 Specify Installation Location Screen

Specify the location where you want to install the software. This is your Oracle home directory. All software binaries will reside in this directory, and no runtime process can write to this directory.

- If you specify an existing directory, make sure the directory is empty.

- If you specify a new directory, the installer will create the directory for you.

Make sure that your directory paths are valid and do not contain double backslashes (\\).

B.4 Select Components Screen

Select the components you want to install.

B.5 Installation Summary Screen

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

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

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

B.6 Installation Progress Screen

This screen shows you the progress of the installation.

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

B.7 Installation Completed Screen

This screen summarizes the installation that was just completed.

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

C 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 Managed Instance Screen

- Specify Instance Location Screen

- Deinstallation Summary (Managed Instance)

- Deinstallation Summary (Unmanaged Instance)

- Deinstallation Progress Screen

- Deinstallation Complete Screen

C.1 Welcome Screen

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

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

C.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 Oracle home, then click Deinstall.

The following warning screen will appear:

Click Yes to remove the software and the Oracle home directory from which the deinstaller was started.

Click No to remove the software but do not remove the Oracle home directory.

Click Cancel to return to the previous screen.

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

C.5 Select Managed Instance Screen

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

Select the managed instance you want to deinstall. Select LocalHost if you want to select all instances.

Your instances must be up and running before they can be deinstalled.

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

C.7 Deinstallation Summary (Managed Instance)

This screen shows you the instance(s) you are about to deinstall.

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 deinstallation from the command line.

C.8 Deinstallation Summary (Unmanaged Instance)

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

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 deinstallation from the command line.

C.9 Deinstallation Progress Screen

This screen shows you the progress of the deinstallation.

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

C.10 Deinstallation Complete Screen

This screen summarizes the deinstallation that was just completed.

D Oracle Discoverer Desktop Deinstallation Screens

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

- Welcome Screen

- Deinstall Oracle Home Screen

- Deinstallation Progress Screen

- Deinstallation Complete Screen

D.1 Welcome Screen

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

D.2 Deinstall Oracle Home Screen

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

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

The following warning screen will appear:

Click Yes to remove the software and the Oracle home directory from which the deinstaller was started.

Click No to remove the software but do not remove the Oracle home directory.

Click Cancel to return to the previous screen.

D.3 Deinstallation Progress Screen

This screen shows the progress of the deinstallation.

D.4 Deinstallation Complete Screen

This screen summarizes the deinstallation that was just completed.

Click Finish to dismiss the screen.

E Silent Installation and Deinstallation

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

- Section E.1, "About Silent Installation and Deinstallation"

- Section E.2, "Oracle Portal, Forms, Reports and Discoverer Response Files"

E.1 About Silent Installation and Deinstallation

For information about silent installation and deinstallation, refer to "Silent Installation and Deinstallation" in Oracle Fusion Middleware Installation Planning Guide.

E.2 Oracle Portal, Forms, Reports and Discoverer 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

Oracle recommends creating your response file by first 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.

This section contains the following:

- Silent Installation Response Files

- Patch Set Installer Response Files

- Silent Deinstallation Response Files

E.2.1 Silent Installation Response Files

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

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

Template

Description

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 (on UNIX operating systems) or config.bat (on Windows operating systems) script from the ORACLE_HOME/bin (on UNIX operating systems) or ORACLE_HOME\bin (on Windows operating systems) directory.

See Section E.2.1.1, "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 E.2.1.2, "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 E.2.1.3, "Contents of the install_and_configure.rsp File" to view the contents of this file.

E.2.1.1 Contents of the configure_only.rsp File

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

[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

E.2.1.2 Contents of the install_only.rsp File

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

[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]

E.2.1.3 Contents of the install_and_configure.rsp File

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

[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

E.2.2 Patch Set Installer Response Files

This section describes the classic_patch_install.rsp response file provided in the Disk1/stage/Response (on UNIX operating systems) or Disk1\stage\Response (on Windows operating systems) directory where you downloaded and extracted the Patch Set Installer archive file. This response file is designed for use in situations where you are updating an existing Oracle Portal, Forms, Reports and Discoverer Oracle home.

The contents of the Disk1/stage/Response/classic_patch_install.rsp response file on a UNIX system is shown below:

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

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

#Provide existing Middleware Home location.
MIDDLEWARE_HOME=/scratch/Middleware

#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=<SECURE VALUE>

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

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

#
CONFIG_WIZARD_RESPONSE_FILE_LOCATION=0

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

The parameters you should set in this file are:

- ORACLE_HOME. Specify the full path to your Oracle home directory.

- MIDDLEWARE_HOME. Specify the full path to your Middleware home directory.

- Decide whether or not you want to configure Oracle Configuration Manager for automatic software and security updates.
If you do not want to configure Oracle Configuration Manager, set DECLINE_SECURITY_UPDATES to true.

If you want to configure Oracle Configuration Manager, set SECURITY_UPDATES_VIA_MYORACLESUPPORT to true. Doing so also requires that you set the MYORACLESUPPORT_USERNAME and MYORACLESUPPORT_PASSWORD parameters with your My Oracle Support user name and password, respectively.

For more information about Oracle Configuration Manager, see "Installing Oracle Configuration Manager" in the Oracle Fusion Middleware Installation Planning Guide.

E.2.3 Silent Deinstallation Response Files

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

Table E-2 Oracle Portal, Forms, Reports and Discoverer Deinstallation Response File Templates

Template

Description

deinstall_managed_instance.rsp

This is the template response file that should be used if you have configured managed instances on your system. These managed instances must be removed before you remove the Oracle home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall ASInstances managed by WebLogic Domain option on the Select Deinstallation Type Screen.

See Section E.2.3.1, "Contents of the deinstall_managed_instances.rsp File" to view the contents of this file.

deinstall_unmanaged_instance.rsp

This is the template response file that should be used if you have configured unmanaged instances on your system. These unmanaged instances must be removed before you remove the Oracle Home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall Unmanaged ASInstances option on the Select Deinstallation Type Screen.

See Section E.2.3.2, "Contents of the deinstall_unmanaged_instances.rsp File" to view the contents of this file.

deinstall_oh.rsp

This is the template response file that should be used if you have already removed all managed and unmanaged instances that use this Oracle Home, and now you are ready to remove the Oracle Home.

The equivalent using the GUI would be starting the deinstaller and selecting the Deinstall Oracle Home option on the Select Deinstallation Type Screen.

See Section E.2.3.3, "Contents of the deinstall_oh.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 deinstaller GUI, then clicking Save on the Deinstallation Summary (Managed Instance) 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 deinstallation on other systems, or modify it as needed.

E.2.3.1 Contents of the deinstall_managed_instances.rsp File

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

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Identifies if the Instance deinstallation is valid or not
DEINSTALL_IN_ASINSTANCE_MODE=true

#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=false

#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=true

#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=false

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

#Specify the Domain Host Name
DOMAIN_HOST_NAME=localhost.domain

#Specify the Domain Port Number
DOMAIN_PORT_NO=7001

#Specify the Domain User Name
DOMAIN_USER_NAME=weblogic

#Specify the Domain Password
DOMAIN_USER_PASSWORD=<SECURE PASSWORD>

#Specify the list of Instance to be deinstalled in the following format. InstanceName^LocationOfInstance$InstanceName^LocationOfInstance
MANAGED_INSTANCE_LIST=asinst_1^C:\wls1\asinst_1$

E.2.3.2 Contents of the deinstall_unmanaged_instances.rsp File

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

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Identifies if the Instance deinstallation is valid or not
DEINSTALL_IN_ASINSTANCE_MODE=true

#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=false

#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=false

#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=true

#Specify the path of the Un-managed Instance
ASINSTANCE_LOCATION_TEXTFIELD=c:\Oracle\Middleware\asinst_1

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

E.2.3.3 Contents of the deinstall_oh.rsp File

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

[ENGINE]

#DO NOT CHANGE THIS.
Response File Version=1.0.0.0.0

[GENERIC]

#Identifies if the Instance deinstallation is valid or not
DEINSTALL_IN_ASINSTANCE_MODE=true

#Specify true for Oracle Home deinstall
OH_HOME_DEINSTALL=true

#Specify true for Managed Instance deinstall
DOMAIN_MANAGED_ASINSTANCE_DEINSTALL=false

#Specify true for Un-managed Instance deinstall
UNMANAGED_ASINSTANCE_DEINSTALL=false

[SYSTEM]

[APPLICATIONS]

[RELATIONSHIPS]

F 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 F.1, "General Troubleshooting Tips"

- Section F.2, "Installation and Configuration Log Files"

- Section F.3, "Verifying Environment Variable Lengths for Oracle Reports (Windows Only)"

- Section F.4, "Granting Access to rwbuilder"

- Section F.5, "Errors Accessing the Discoverer Plus and Discoverer Viewer URLs"

- Section F.6, "Need More Help?"

F.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 the System Requirements and Specifications document:

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

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

3. Correct the issue that caused the error.

4. Restart the installation.

F.2 Installation and Configuration Log Files

This section contains information about the log files that are created when running the Oracle Portal, Forms, Reports and Discoverer installer and the Configuration Wizard. Log files contain information that can help you troubleshoot problems with your installation or configuration.

F.2.1 Installation Log Files

The installer writes logs files to the Oracle_Inventory_Location/log (on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windows operating systems) directory. On UNIX 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
This is the main log file.

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

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

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

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

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

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

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

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

F.2.2 Configuration Log Files

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

On UNIX operating systems:

% ./config.sh -log=log_filename

On Windows operating systems:

G:\ config.cmd -log=log_filename

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

F.3 Verifying Environment Variable Lengths for Oracle Reports (Windows Only)

If an environment variable used by startManagedWebLogic.cmd (for example, PATH or CLASSPATH) contains too many characters, Oracle Reports will generate errors when you try to start its Managed Server.

To work around this issue, you can try to convert all directory names longer than eight characters to the Windows short name format. For example, C:\Oracle11g\Middleware can be converted to C:\Oracle~1\Middle~1 wherever you define your environment variables that use this path.

You can also reinstall Oracle WebLogic Server to a location where the directory path is shorter than its current location.

For more information about the character limits of the environment variables on your Windows system, refer Article 830473 on the Microsoft Support website (http://support.microsoft.com/kb/830473), or refer to your operating system documentation.

F.4 Granting Access to rwbuilder

A user who installed the Oracle Reports components can access them, by default. If you want to allow other users to run rwbuilder:

1. Change the permissions of the following files.
On Linux x86 operating systems:

chmod 750 ORACLE_HOME/bin
chmod 750 ORACLE_HOME/bin/rwbuilder
chmod 750 COMMON_COMPONENTS_HOME/modules/oracle.dms_11.1.1/*.jar
chmod 750 COMMON_COMPONENTS_HOME/modules/oracle.odl_11.1.1/*.jar
chmod 750 ORACLE_INSTANCE
chmod 750 ORACLE_INSTANCE/bin
chmod 750 ORACLE_INSTANCE/config
chmod 750 ORACLE_INSTANCE/config/reports
chmod 750 ORACLE_INSTANCE/config/reports/bin
chmod 750 ORACLE_INSTANCE/config/reports/bin/*
chmod 750 ORACLE_INSTANCE/config/FRComponent
chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent
chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools
chmod 750 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/*
chmod 770 ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/rwbuilder.conf
chmod 750 ORACLE_INSTANCE/reports
chmod 750 ORACLE_INSTANCE/reports/reports_install.properties
chmod 750 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/
chmod 770 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_version/
chmod 770 DOMAIN_HOME/servers/WLS_REPORTS/tmp/_WL_user/reports_version/<random_name>/war
chmod 750 directory_mentioned_in_REPORTS_TMP

On Windows operating systems, right-click on the folder, select Properties, then modify the security settings as necessary.

2. Change the location of the log files so that users will have both read and write access. Modify the PATH property of the runtime_trace_handler and zrcclient_trace_handler parameters in the ORACLE_INSTANCE/config/ReportsToolsComponent/ReportsTools/logging.xml (on Linux x86 operating systems) or ORACLE_INSTANCE\config\ReportsToolsComponent\ReportsTools\logging.xml (on Windows operating systems) file.

F.5 Errors Accessing the Discoverer Plus and Discoverer Viewer URLs

During the configuration process, if the database that contains the prefix_DISCOVERER schema is shut down between the "Create ASInstance" and "Deploy Discoverer" steps, the configuration process will be completed successfully despite the database being down. However, you will not be able to access the Discoverer Plus and Discoverer Viewer URLs.

The following errors can be found in the log file:

connection error.
- error while creating the session, check for other errors.
- oracle.discoiv.connections.ConnectionStoreException:
@ weblogic.common.resourcepool.ResourceDisabledException: Pool
@ examplehost.exampledomain.com_SPS3NT_DISCOVERER_PS is disabled,
cannot allocate resources to applications..

In this situation, you should do the following:

1. Start the database.

2. Restart the Oracle Discoverer instance.

3. Restart the WLS_DISCO Managed Server.

4. Restart the Administration Server.

F.6 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: https://support.oracle.com)

If you do not find a solution for your problem, open a service request.

Index
A  B  C  D  E  G  I  L  M  N  O  P  R  S  T  U  V  W

Numerics

64-big JDK support, 2.1.3

A

accessibility software, Java Access Bridge, A

Administration Console, 2.2

B

browser URLs, 2.4.4

C

cluster

expanding, A.7

configuration log files, F.2.2 Configuration Tool, 2.2

location, 2.2

running, 2.3.4.3

configuring a proxy, A.12 createCentralInventory.sh script, A.2 creating a WebLogic Domain, A.7 creating response files, E.2

D

database schemas

creating for Oracle Portal and Oracle Discoverer, 2.1.1

default port numbers, A.11 deinstallation options, 4.1 deinstallation types, 4.1, C.2 deinstalling Oracle Discoverer Desktop, D deinstalling Oracle Portal, Forms, Reports and Discoverer, C documentation conventions, Preface dropping the schemas, 4.2.2

E

Enterprise Manager, 2.2

expanding a cluster, A.7

extending a WebLogic Domain, A.7

G

granting access to RWbuilder, F.4

I

install type

selecting, A.5

installation directory structure, 1.2 installation instructions, 2, 2.3, 3

Application Developer

installation instructions, 3.2

installation location

specifying, A.9

installation log files, 2.3.2.3, 3.2.2, F.2.1 installation overview, 1 installation roadmap, 1.2 installation types, 2.2 inventory screens, 2.3.3

L

log files, 3.2.2

for configuration, F.2.2

for installation, 2.3.2.3, F.2.1

M

Middleware Home, A.9.1

My Oracle account, A.8

My Oracle Support, F.6

N

non-interactive installations, E

O

OPMN status, 2.4.3

opmnctl command, 2.4.3

Oracle Business Intelligence Discoverer, 1.1

overview, 1.1

Oracle Configuration Manager, A.8 Oracle Discoverer

manual configuration, 2.3.5

Oracle Discoverer Desktop

deinstallation screens, D

deinstalling, 5, D

installation log files, 3.2.2

installing, 3

specifying the installation location, B.3

starting, 3.3

Oracle Forms Services, 1.1

overview, 1.1

Oracle Fusion Middleware

stopping, 4.2.1

Oracle Home, A.9.1 Oracle home

manually removing, 5.2

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

installing, 2.1.5

Oracle Inventory, 2.3.3

custom inventory location, 2.3.3

Oracle Inventory location, A.1 Oracle JDeveloper

removing, 4.2.6

Oracle Portal, 1.1

overview, 1.1

Oracle Portal, Forms, Reports and Discoverer

deinstallation screens, C

deinstalling, 4, C

directory structure, 1.2

installation instructions, 2.3

installation overview, 1

installing in a Middleware home where another Fusion Middleware product already exists, 2.1.8

installing on separate servers, 2.1.7

products overview, 1.1

reinstalling, 4.3

silent installation, E

types of installation, 2.2

verifying the installation, 2.4

Oracle Reports, 1.1

services, 1.1

Oracle Single Sign-On (SSO)

installing, 2.1.5

Oracle Technology Network, F.1 Oracle Web Agent (OWA)

upgrading for Oracle Portal, 2.1.6

Oracle WebLogic Server

installing, 2.1.2

removing, 4.2.5

oracleRoot.sh script, 2.3.4.3 oraInst.loc file, 2.3.3, F.2.1 oraInventory directory, A.1 overview of installation, 1

P

Patch Set Installer, 2.3.4.2

port configuration, A.11

proxy

configuring, A.12

R

receiving security updates, A.8

reinstalling Oracle Portal, Forms, Reports and Discoverer, 4.3

removing Oracle JDeveloper, 4.2.6

removing Oracle WebLogic Server, 4.2.5

response file

creating, A.16, C.7, C.8, E.2

roadmap for installation, 1.2 root access, Preface RWbuilder

granting access to, F.4

S

saving your deinstallation information, C.7, C.8

saving your installation and configuration information, A.16

schema

specifying, A.13

schemas

dropping, 4.2.2

security updates

signing up for, A.8

silent installation, E, E.1 specifying schema, A.13 starting the deinstaller, 4.2.3.1

on Windows systems, 4.2.3.1

staticports.ini file, A.11 stopping Oracle Fusion Middleware, 4.2.1 support of 64-bit JDK, 2.1.3

T

troubleshooting, F

types of deinstallation, 4.1, C.2

U

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

URLs to help verify installation, 2.4.4

V

verifying the installation, 2.4

W

WebLogic Domain

creating, A.7

extending, A.7

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.