Installation Developer Suite 10g

Oracle Developer Suite
Installation Guide 10g (9.0.4) for Windows, Linux, Solaris, and HP-UX
Part No. B10579-02
March 2004
Oracle Developer Suite Installation Guide 10g (9.0.4) for Windows, Linux, Solaris, and HP-UX Part No. B10579-02 Copyright 2003, 2004 Oracle. All rights reserved. Primary Author: Joe Malin Poh Lee Tan
Contributing Author:
Contributors: Steven Anderson, Carolyn Bruse, Orlando Cordero, Craig DeNamur, Avrom Faderman, Kerstin Goldsmith, Jay Hauser, Kurt Heiss, Yuki Hirano, Christine Jacobs, Madhavi Jain, Derek Jones, Thomas Jose, Lypp-tek Khoo-Ellis, Shaun Lin, Robin Merrin, Mike Moon, Kathyrn Munn, Kavita Nayer, Andy Page, Santosh Poonen, Mercy Polson, Rajesh Ramachandran, Frank Rovitto, Theresa Robertson, Bill Ruppel, Yvette Salmon, Julia Stein, Jeremy Williams, Paul Wright The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States 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, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065 The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third-party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Perspective for Java licensed from Three D Graphics, Inc. Copyright 1997, 2000, Three D Graphics, Inc.
Contents
Send Us Your Comments ........................................................................................................................ ix Preface ................................................................................................................................................................. xi
Intended Audience...................................................................................................................................... xi Documentation Accessibility ..................................................................................................................... xi Structure ...................................................................................................................................................... xii Related Documents .................................................................................................................................... xii Conventions ............................................................................................................................................... xiii
Installation Concepts
1.1 1.2 1.3 1.4 1.4.1 1.4.2 1.4.3 1.4.4 1.4.5 1.4.6 1.4.7 1.4.8 Oracle Developer Suite Installation Overview ....................................................................... 1-1 About the Installation Process .................................................................................................. 1-2 About Installing Oracle Developer Suite Components......................................................... 1-3 Whats New in the Installation ................................................................................................. 1-3 Installation from DVD is Now Available......................................................................... 1-4 Solaris 6 and 7 No Longer Supported............................................................................... 1-4 SuSE SLES-7 No Longer Supported.................................................................................. 1-4 New Operating System Patches Required ....................................................................... 1-4 Space in /var/tmp No Longer Required During Installation (Linux, Solaris, and HP-UX Only) ........................................................................................................................ 1-4 More Prerequisite Checks................................................................................................... 1-4 Configuration Assistant Enhancements ........................................................................... 1-5 Removed Restrictions.......................................................................................................... 1-5
Getting Started
2.1 2.2 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.4 2.5 2.6 Hardware Requirements............................................................................................................ Operating Environments Supported........................................................................................ Operating Environment Software Requirements................................................................... Windows Operating Environment.................................................................................... Solaris Operating Environment for Sun SPARC workstations..................................... HP-UX Operating Environment ........................................................................................ Linux Operating Environment .......................................................................................... Certified Software ....................................................................................................................... Online Documentation Requirements ..................................................................................... Coexistence in One Oracle Home ............................................................................................. 2-1 2-3 2-4 2-4 2-4 2-6 2-8 2-8 2-9 2-9
iii
2.6.1 Oracle Home Considerations ............................................................................................. 2-9 2.6.2 Performing Multiple Installations of Oracle Developer Suite.................................... 2-10 2.6.3 Oracle Developer Suite Installation and Oracle Databases ........................................ 2-10 2.7 Directories Used by the Installer ........................................................................................... 2-11 2.8 Preinstallation Tasks................................................................................................................ 2-11 2.8.1 General Checklist.............................................................................................................. 2-12 2.8.2 Setting the Locale.............................................................................................................. 2-12 2.8.3 Using Assistive Technologies (Windows only)............................................................ 2-13 2.8.4 Installing Java Access Bridge (Windows only) ............................................................ 2-13 2.8.5 Setting Environment Variables (Linux, Solaris, and HP-UX only) ........................... 2-14 2.8.5.1 ORACLE_HOME....................................................................................................... 2-14 2.8.5.1.1 Preventing Conflicts With Other Oracle Homes ........................................... 2-14 2.8.5.2 DISPLAY ..................................................................................................................... 2-14 2.8.5.3 TMP ............................................................................................................................. 2-15 2.8.5.4 TNS_ADMIN.............................................................................................................. 2-15 2.8.6 Creating Linux, Solaris, and HP-UX Accounts and Groups ...................................... 2-15 2.8.6.1 Group Name for the Installer Inventory ................................................................ 2-15 2.8.6.2 User for Oracle Software .......................................................................................... 2-16 2.8.7 Completing Component-specific Preinstallation Tasks.............................................. 2-16 2.8.7.1 Oracle Software Configuration Manager............................................................... 2-16 2.8.8 Information Needed During Installation ...................................................................... 2-17 2.8.9 Migration or Upgrading .................................................................................................. 2-17 2.9 Preparing to Start the Installer ............................................................................................... 2-17 2.9.1 About Oracle Universal Installer.................................................................................... 2-17 2.9.2 Installer Prerequisite Checks........................................................................................... 2-18 2.9.3 The Installer Inventory Directory................................................................................... 2-19 2.9.4 Starting the Installer ......................................................................................................... 2-19 2.9.4.1 For Windows users.................................................................................................... 2-20 2.9.4.1.1 Windows System Files Installation.................................................................. 2-20 2.9.4.2 For Linux, Solaris, and HP-UX users...................................................................... 2-21 2.9.4.2.1 Mounting CD-ROMs and DVDs to Solaris..................................................... 2-21 2.9.4.2.2 Mounting CD-ROMs and DVDs to HP-UX.................................................... 2-22 2.9.4.2.3 Mounting CD-ROMs and DVDs to Linux ...................................................... 2-23 2.9.4.2.4 Running the Installer ......................................................................................... 2-24 2.9.4.3 Running the Installer in Silent or Non-Interactive Mode .................................... 2-24
Installation
3.1 Installing Oracle Developer Suite............................................................................................. 3-1 3.2 Postinstallation Tasks ................................................................................................................. 3-7 3.2.1 General Checklist................................................................................................................. 3-7 3.2.1.1 Updates .......................................................................................................................... 3-7 3.2.1.2 NLS ................................................................................................................................. 3-8 3.2.1.2.1 Component Languages......................................................................................... 3-8 3.2.1.2.2 Additional Fonts.................................................................................................... 3-8 3.2.1.3 TNS Names.................................................................................................................... 3-9 3.2.1.4 Port Numbers ................................................................................................................ 3-9 3.2.1.5 OC4J Instance for Oracle Developer Suite ............................................................. 3-10
iv
3.2.1.6 3.2.2 3.2.2.1 3.2.2.1.1 3.2.2.1.2 3.2.2.1.3 3.2.2.1.4 3.2.2.1.5 3.2.2.1.6 3.2.2.1.7 3.2.2.1.8 3.2.2.2 3.2.2.2.1 3.2.2.2.2 3.2.2.2.3 3.2.2.3 3.2.2.4 3.2.2.5 3.2.2.6 3.2.2.7 3.2.3 3.2.3.1 3.2.3.2 3.2.3.3 3.2.3.3.1 3.2.3.3.2 3.2.3.4 3.2.3.5 3.2.3.6 3.2.4
Assistive Technologies (Windows only) ................................................................ Completing Component-specific Postinstallation Tasks ............................................ Oracle9i JDeveloper................................................................................................... Migrating User Settings from Previous Releases........................................... Enabling JDeveloper Extensions ...................................................................... Enabling Source Code Control (Windows only) ........................................... Font Problems on Linux, Solaris, and HP-UX Computers........................... Hosting Documentation .................................................................................... Using JDeveloper in a Terminal Server/Multiuser Environment .............. Using OC4J in non-embedded mode with JDeveloper................................. Using Assistive Technologies with JDeveloper (Windows only) ............... Oracle Business Intelligence Beans ......................................................................... Database Considerations................................................................................... Preparing an Oracle9i Release 2 Database for Use with BI Beans............... Additional Tasks ................................................................................................ Oracle Reports Developer ........................................................................................ Oracle Discoverer Administrator............................................................................ Oracle Forms Developer........................................................................................... Oracle Software Configuration Manager (Oracle SCM) ...................................... Oracle Designer.......................................................................................................... Starting a Component ...................................................................................................... Oracle9i JDeveloper and Oracle Business Intelligence Beans ............................. Oracle Reports Developer ........................................................................................ Oracle Discoverer ...................................................................................................... Oracle Discoverer Administrator..................................................................... Oracle Discoverer Desktop ............................................................................... Oracle Forms Developer........................................................................................... Oracle Software Configuration Manager (Oracle SCM) ...................................... Oracle Designer.......................................................................................................... Additional Documentation .............................................................................................
3-10 3-11 3-11 3-11 3-11 3-12 3-12 3-13 3-13 3-16 3-17 3-17 3-17 3-18 3-19 3-20 3-21 3-21 3-22 3-22 3-23 3-23 3-23 3-23 3-23 3-24 3-24 3-24 3-25 3-25
Deinstallation and Reinstallation

4.1 4.1.1 4.2 Deinstallation............................................................................................................................... 4-1 Deinstalling Using the Installer ......................................................................................... 4-1 Reinstallation ............................................................................................................................... 4-3
Upgrade Notes
A.1 A.2 A.2.1 A.2.2 A.3 A.3.1 A.3.2 A.4 A.5 Oracle Developer Suite.............................................................................................................. Oracle9i JDeveloper ................................................................................................................... Migrating JDeveloper User Settings from Release 9.0.2 to Release 9.0.4.................... Additional Migration Issues ............................................................................................. Oracle Business Intelligence Beans.......................................................................................... Migrating Oracle BI Beans Projects from Release 9.0.2 to Release 9.0.4 ..................... Migrating Oracle BI Beans Projects from Release 9.0.3 to Release 9.0.4 ..................... Oracle Reports Developer......................................................................................................... Oracle Discoverer Administrator ............................................................................................ A-1 A-2 A-2 A-3 A-3 A-3 A-6 A-7 A-8
A.6 A.7 A.8 A.9
Oracle Forms Developer ........................................................................................................... Oracle Software Configuration Manager ............................................................................... Oracle Designer .......................................................................................................................... Additional Documentation.......................................................................................................
A-8 A-8 A-9 A-9
Components
B.1 B.1.1 B.1.2 B.1.3 B.1.3.1 B.1.4 B.1.5 B.2 B.3 B.4 B.5 B.6 B.7 Oracle9i JDeveloper ................................................................................................................... Supported Deployment Environments ........................................................................... Oracle on the Web............................................................................................................... Oracle Business Intelligence Beans .................................................................................. Deployment Requirements ........................................................................................ UIX ........................................................................................................................................ Bali ........................................................................................................................................ Oracle Reports Developer......................................................................................................... Oracle Discoverer Administrator ............................................................................................ Oracle Forms Developer ........................................................................................................... Oracle Software Configuration Manager ............................................................................... Oracle Designer .......................................................................................................................... Additional Documentation....................................................................................................... B-1 B-2 B-3 B-3 B-3 B-5 B-5 B-5 B-5 B-6 B-6 B-6 B-6
Installing the Documentation Library

C.1 C.2 C.2.1 C.2.2 C.3 C.3.1 Documentation Library Titles .................................................................................................. Installing the Documentation Library .................................................................................... File Copy Installation Method .......................................................................................... Installer Method.................................................................................................................. Viewing the Documentation Library ...................................................................................... Viewing the Release Notes from Disk ............................................................................. C-1 C-2 C-2 C-3 C-4 C-4
Silent and Non-Interactive Install

D.1 D.1.1 D.1.2 D.2 D.3 D.4 D.4.1 D.4.1.1 D.4.1.2 D.4.1.3 D.4.1.4 D.5 D.5.1 D.5.2 D.6 Introduction ................................................................................................................................ Silent Installation ................................................................................................................ Non-Interactive Installation .............................................................................................. Requirements.............................................................................................................................. Preinstallation............................................................................................................................. Working with Response Files................................................................................................... Example Response Files for Oracle Developer Suite Installations .............................. Business Intelligence (Windows only) ..................................................................... Complete Install (Windows) ...................................................................................... Complete Install (Linux, Solaris, and HP-UX) ........................................................ Using Response Files on HP-UX ............................................................................... Starting the Installation ............................................................................................................. Starting the Installer for a Silent Installation .................................................................. Starting the Installer for a Non-Interactive Installation ................................................ Postinstallation ........................................................................................................................... D-1 D-1 D-2 D-2 D-2 D-3 D-3 D-4 D-4 D-5 D-6 D-6 D-6 D-6 D-6
vi
Troubleshooting
E.1 E.1.1 E.1.2 E.2 E.3 E.3.1 E.3.2 E.3.3 E.3.4 Before You Begin........................................................................................................................ Verify Hardware and Pre-installation Requirements ................................................... Read the Release Notes ...................................................................................................... Troubleshooting the Installation.............................................................................................. Troubleshooting Oracle Developer Suite Configuration Assistants .................................. Determining Configuration Assistant Execution Status ............................................... Fixing Configuration Assistant Failures.......................................................................... Handling Fatal Errors......................................................................................................... Oracle Developer Suite Configuration Assistant Descriptions.................................... E-1 E-1 E-2 E-2 E-3 E-3 E-4 E-4 E-5
Index
vii
viii
Send Us Your Comments

Oracle Developer Suite Installation Guide, 10g (9.0.4) for Windows, Linux, Solaris, and HP-UX
Part No. B10579-02
Oracle welcomes your comments and suggestions on the quality and usefulness of this publication. Your input is an important part of the information used for revision.

Did you find any errors? Is the information clearly presented? Do you need more information? If so, where? Are the examples correct? Do you need more examples? What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, please indicate the title and part number of the documentation and the chapter, section, and page number (if available). You can send comments to us in the following ways:

Electronic mail: devsuitedocs_us@oracle.com FAX: 1-650-633-3846. Attn: Oracle Developer Suite Documentation Manager Postal service: Oracle Corporation Oracle Developer Suite Documentation 200 Oracle Parkway, Mailstop 2op11 Redwood Shores, CA 94065 U.S.A
If you would like a reply, please give your name, address, telephone number, and electronic mail address (optional). If you have problems with the software, please contact your local Oracle Support Services.
ix
Preface
This guide describes the installation process for Oracle Developer Suite 10g (9.0.4) (formerly Oracle9i Developer Suite) on Windows, Linux, Solaris, and HP-UX. This preface contains these topics:

Intended Audience Documentation Accessibility Structure Related Documents Conventions
Intended Audience
This installation guide is intended for developers, database administrators, and others responsible for installing Oracle products. You should be familiar with client/server architecture and relationships, and database concepts.
Documentation Accessibility
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. 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. Standards will continue to evolve over time, and Oracle Corporation 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 additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
Accessibility of Code Examples in Documentation JAWS, a Windows screen reader, 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, JAWS may not always read a line of text that consists solely of a bracket or brace.
xi
Accessibility of Links to External Web Sites in Documentation This documentation
may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.
Structure
This guide contains: Chapter 1, "Installation Concepts" This chapter provides an overview of the installation and the available installation options. Chapter 2, "Getting Started" This chapter lists the Oracle Developer Suite hardware and software requirements. It also lists preinstallation tasks that you must perform before installing. Chapter 3, "Installation" This chapter guides you through the installation and postinstallation steps. Chapter 4, "Deinstallation and Reinstallation" This chapter guides you through deinstallation and reinstallation. Appendix A, "Upgrade Notes" This appendix contains information about migrating or upgrading from earlier versions of Oracle Developer Suite components. Appendix B, "Components" This appendix provides brief descriptions of the Oracle Developer Suite components. Appendix C, "Installing the Documentation Library" This appendix describes the contents of the Oracle Developer Suite Documentation Library and provides instructions for installing and viewing the documentation. Appendix D, "Silent and Non-Interactive Install" This appendix contains information about installing Oracle Developer Suite using silent install and non-interactive installation. Appendix E, "Troubleshooting" This appendix lists some methods for troubleshooting your installation.
Related Documents
For more information, see these Oracle resources:

Oracle Developer Suite Documentation Library Oracle Developer Suite Platform Specific Documentation on the Oracle Developer Suite Disk 1 CD-ROM, the Oracle Developer Suite Documentation Library CD-ROM, or the Oracle Developer Suite DVD.
You can purchase printed documentation in the Oracle Store at http://oraclestore.oracle.com/
xii
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at http://otn.oracle.com/membership If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at http://otn.oracle.com/documentation
Conventions
The following conventions are also used in this manual:
Convention . . . ... Meaning Vertical ellipsis points in an example mean that information not directly related to the example has been omitted. Horizontal ellipsis points in statements or commands mean that parts of the statement or command not directly related to the example have been omitted Brackets enclose optional clauses from which you can choose one or none. Boldface type in text indicates a term defined in the text, the glossary, or in both locations. Italic typeface indicates book titles or emphasis. Lowercase monospace typeface indicates executables, file names, directory names, and sample user-supplied elements. Such elements include computer and database names, net service names, and connect identifiers, as well as user-supplied database objects and structures, column names, packages and classes, user names and roles, program units, and parameter values. Note: Some programmatic elements use a mixture of UPPERCASE and lowercase. Enter these elements as shown. boldface code italicized code CODE (UPPERCASE monospace or fixed-width font) Boldface monospace typeface indicates text that you enter in response to a command line prompt. Italicized code indicates placeholder text that you need to replace with an appropriate value Uppercase monospace typeface indicates elements supplied by the system. Such elements include parameters, privileges, datatypes, RMAN keywords, SQL keywords, SQL*Plus or utility commands, packages and methods, as well as system-supplied column names, database objects and structures, usernames, and roles.
[] boldface text Italics code (lowercase monospace or fixed-width font)
xiii
xiv
1
This chapter provides conceptual information about installing Oracle Developer Suite and describes the install options available. The topics include:

Oracle Developer Suite Installation Overview About the Installation Process About Installing Oracle Developer Suite Components Whats New in the Installation
1.1 Oracle Developer Suite Installation Overview

The Oracle Developer Suite product installation has the following options:
J2EE Development: Provides a lightweight installation that allows you to develop Java and Enterprise Edition (J2EE) applications using Java, HTML, XML, and SQL. This option includes testing capability with Oracle Application Server Containers for J2EE (OC4J), and allows you to extend applications with business intelligence using Oracle Business Intelligence Beans (hereinafter referred to as "Oracle BI Beans"). Business Intelligence: (Windows only) Provides development tools that allow you to extend transactional applications with business intelligence. This option includes relevant Oracle Application Server runtime services and testing capability with OC4J. Rapid Application Development: (Windows only) Provides the J2EE Development components and the development tools that allow you to rapidly build Oracle Reports-based and Oracle Forms-based applications. This option also provides a software configuration management tool and a toolset for designing and generating databases and multi-tier applications. It also includes relevant Oracle Application Server runtime services and testing capability with OC4J. Complete: For Windows, this option provides all Oracle Developer Suite components. For Linux x86, Solaris, and HP-UX, it provides the J2EE Development components and the development tools for building Oracle Reports-based and Oracle Forms-based applications.
The Oracle Developer Suite hardware and software requirements are listed in Chapter 2, "Getting Started". Step-by-step installation instructions are provided in Chapter 3, "Installation". Descriptions of individual Oracle Developer Suite components are provided in Appendix B, "Components".
1-1
About the Installation Process
Table 11 lists the Oracle Developer Suite Windows install options, and the components that are installed with each option. Table 12 lists the Oracle Developer Suite install options for Linux, Solaris, and HP-UX, and the components that are installed with each option.
Table 11 Oracle Developer Suite Install Options and Components (Windows) J2EE Development YES Business Intelligence no Rapid Application Development YES
Component Oracle9i JDeveloper(9.0. 4) (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) Oracle Reports Developer Oracle Discoverer Administrator (formerly Discoverer Administration Edition) including Oracle Discoverer Desktop Oracle Forms Developer Oracle Software Configuration Manager Oracle Designer
Complete YES
no no
YES YES
YES no
YES YES
no no no
no no no
YES YES YES
YES YES YES
Table 12 HP-UX)
Oracle Developer Suite Install Options and Components (Linux, Solaris, and J2EE Development YES Complete YES
Component1 Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) Oracle Reports Oracle Forms
1
no no
YES YES
To provide complete Oracle Developer Suite functionality, the Linux, Solaris, and HP-UX distribution pack includes the full Windows distribution pack as well.
1.2 About the Installation Process

The Oracle Developer Suite installation process has the following phases:
Preinstallation: Perform preinstallation tasks before installing Oracle Developer Suite, and then start Oracle Universal Installer to begin installation. See Section 2.8, "Preinstallation Tasks" and Section 2.9, "Preparing to Start the Installer" for details. Installation: Follow the instructions given by the installer to install Oracle Developer Suite. See Chapter 3, "Installation" for details.
1-2
Installation Guide
Whats New in the Installation
Postinstallation: Perform postinstallation and configuration tasks after successfully installing Oracle Developer Suite. See Section 3.2, "Postinstallation Tasks" for details.
Note: If you are migrating or upgrading from a previous version,
make sure you review Appendix A, "Upgrade Notes" before you start your installation.
1.3 About Installing Oracle Developer Suite Components

Oracle Universal Installer installs the Oracle Developer Suite components with default configuration values, and also configures basic network elements required for accessing local or remote server products. Oracle Developer Suite does not require a separate Oracle Application Server (OracleAS) installation to run or test applications. Depending on the options you select, the Oracle Developer Suite installation provides relevant OracleAS runtime services (OC4J, Oracle Application Server Forms Services, and Oracle Application Server Reports Services) for testing applications. However, Oracle recommends that you also test your applications in the actual deployment environments. Some Oracle Developer Suite component features require specific OracleAS components. For information about an individual components requirements, see the components chapter in Appendix B, "Components". During installation, you are asked to provide an Oracle home name and path. For information about the coexistence of Oracle products in one Oracle home directory, and guidelines for installing multiple Oracle products on one computer, see Section 2.6, "Coexistence in One Oracle Home".
1.4 Whats New in the Installation

This section describes new features in the installation. This section is mostly useful to users who have installed Oracle9i Developer Suite (Oracle9iDS) Release 2 (9.0.2). To see a list of new features in the product itself, visit the Oracle Technology Network site (http://otn.oracle.com). The topics include:

Section 1.4.1, "Installation from DVD is Now Available" Section 1.4.2, "Solaris 6 and 7 No Longer Supported" Section 1.4.3, "SuSE SLES-7 No Longer Supported" Section 1.4.4, "New Operating System Patches Required" Section 1.4.5, "Space in /var/tmp No Longer Required During Installation (Linux, Solaris, and HP-UX Only)" Section 1.4.6, "More Prerequisite Checks" Section 1.4.7, "Configuration Assistant Enhancements" Section 1.4.8, "Removed Restrictions"
1-3
1.4.1 Installation from DVD is Now Available

Oracle Developer Suite and Oracle Developer Suite Documentation Library are now available on a DVD-ROM disk. They are also still available on CD-ROMs. A benefit of installing from the DVD is that you do not have to swap disks during installation, which is something you have to do if you are installing from CD-ROM.
1.4.2 Solaris 6 and 7 No Longer Supported

Oracle Developer Suite 10g (9.0.4) is certified to run on Solaris 8 (2.8) and Solaris 9 (2.9). Oracle Developer Suite 10g (9.0.4) does not support Solaris 7 (2.7), Solaris 6 (2.6) or earlier versions of the Solaris operating environment.
1.4.3 SuSE SLES-7 No Longer Supported

SuSE Linux SLES-7, which was supported in Oracle9i Developer Suite Release 2 (9.0.2), is not supported in Oracle Developer Suite 10g (9.0.4).
Note: For a list of all the supported Linux x86 supported
distributions and versions, please refer to Table 28, " Linux x86 Operating Environment Software Requirements".
1.4.4 New Operating System Patches Required

Oracle9iDS Release 2 (9.0.2) shipped with Java SDK 1.3.1. Oracle Developer Suite 10g (9.0.4) ships with Java SDK 1.4.1 for all platforms except Linux and HP-UX. For Linux, Java SDK 1.4.2 is included. The HP-UX version of Oracle Developer Suite does not contain a Java SDK. You need to download and install the SDK before you install Oracle Developer Suite. To find out which version of the HP Java SDK you need, see Table 27, " HP-UX Operating Environment Software Requirements". For instructions on downloading the HP Java SDK, see Section 2.8.1, "General Checklist". These new versions of the Java SDK may require new and updated patches for the supported operating systems. See Section 2.3, "Operating Environment Software Requirements" for a list of required patches.
1.4.5 Space in /var/tmp No Longer Required During Installation (Linux, Solaris, and HP-UX Only)
In the Linux, Solaris, and HP-UX version of Oracle Developer Suite 10g (9.0.4), the installer no longer requires any disk space in the /var/tmp directory. Some components may still write to /var/tmp while they are running.
1.4.6 More Prerequisite Checks

In Oracle Developer Suite 10g (9.0.4), the installer performs more prerequisite checks to ensure that your computer meets the minimum requirements. See Section 2.9.2, "Installer Prerequisite Checks" for a list of the checks.
1-4
Installation Guide
1.4.7 Configuration Assistant Enhancements

The Configuration Assistants now have these features:

The assistants now write log files to a central location. The assistants now write more understandable messages to the log files.
For more information about these features, see Section E.3, "Troubleshooting Oracle Developer Suite Configuration Assistants".
1.4.8 Removed Restrictions

The following restriction in Oracle9i Developer Suite Release 2 (9.0.2) has been removed:
X Windows is no longer required for silent or non-interactive installations. It is still required for interactive installations (Linux, Solaris, and HP-UX only).
1-5
1-6
Installation Guide
2
Getting Started
This chapter describes the Oracle Developer Suite and Oracle Developer Suite Documentation Library hardware and software requirements. The topics include:

Hardware Requirements Operating Environments Supported Operating Environment Software Requirements Certified Software Online Documentation Requirements Coexistence in One Oracle Home Directories Used by the Installer Preinstallation Tasks Preparing to Start the Installer
2.1 Hardware Requirements

Table 21 contains the basic hardware requirements for Oracle Developer Suite.
Table 21 Oracle Developer Suite Hardware Requirements Requirements One of the following:

Hardware Item CPU
A Pentium or compatible processor (500 MHz recommended) A SPARC processor (200 MHz recommended) An HP PA-RISC 64-bit processor (300 MHz recommended)
Memory
128 MB 1
Getting Started
2-1
Hardware Requirements
Table 21 (Cont.) Oracle Developer Suite Hardware Requirements Hardware Item Disk Space 2 Requirements J2EE Development

Windows: 508 MB Solaris: 528 MB HP-UX: 1.1 GB3 Linux: 600 MB 636 MB 943 MB Windows - 943 MB Solaris - 865 MB HP-UX: 1.6 GB3 Linux: 850 MB Windows: 384 MB Linux, Solaris, HP-UX: 500 MB
Business Intelligence (Windows only)
Rapid Application Development (Windows only)
Complete

Total Pagefile Size, TMP, or Swap Space4 Video

1
The computer must be capable of displaying a minimum of 256 colors.
Minimum required to install. This is not the minimum for all Oracle Developer Suite components. See Table 22 for individual component memory requirements. Disk space required for installing English language only. The actual disk space required depends on the languages selected for installation. Additional temporary disk space of 50 MB, typically on the C drive, is also required. The disk space requirement for HP-UX is larger than for other operating environments because both 32-bit and 64-bit Oracle client side libraries for HP-UX are installed. If you are using Oracle9i JDeveloper in a multiuser Linux, Solaris, or HP-UX environment, you should use 1 GB swap space.
Table 22 contains the memory requirements for each Oracle Developer Suite component.
Table 22 Memory Requirements for Oracle Developer Suite Components Memory

Component Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) Oracle Reports Developer
Minimum: 256 MB Recommended: 512 MB Minimum: 128 MB Recommended: 256 MB Minimum: 128 MB Recommended: 256 MB
Oracle Discoverer Administrator
Oracle Discoverer Desktop Oracle Forms Developer
128 MB

Minimum: 128 MB Recommended: 256 MB
Oracle Software Configuration Manager Oracle Designer
256 MB 256 MB
2-2
Installation Guide
Operating Environments Supported
2.2 Operating Environments Supported

Oracle Developer Suite is available for the Microsoft Windows NT/2000/XP Professional, Sun Solaris, HP PA-RISC HP-UX (64-bit), and Linux x86 operating environments. Table 23 lists the operating environments and the Oracle Developer Suite components that are installed with each environment.
Note: In this document, the term "Linux" refers to Linux x86
operating environments.
Table 23
Operating Environments and Oracle Developer Suite Components NT/2000/XP Professional YES Solaris YES Linux YES HP-UX YES
Component Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) Oracle Reports Developer Oracle Discoverer Administrator (formerly Discoverer Administration Edition) including Oracle Discoverer Desktop Oracle Forms Developer Oracle Software Configuration Manager Oracle Designer
YES YES
YES no
YES no
YES no
YES YES YES
YES no no
YES no no
YES no no
Linux, Solaris, and HP-UX Notes:
Oracle9i Developer Suite Release 2 (9.0.2) for Linux, Solaris, and HP-UX included the full Windows distribution pack. The Windows distribution pack for Oracle Developer Suite 10g (9.0.4) may not be in the initial Linux, Solaris, and HP-UX release pack. You will receive it when it becomes available; meanwhile, you will be able to download it from Oracle Technology Network (http://otn.oracle.com). The following Linux, Solaris, and HP-UX desktops have been certified for JDeveloper:

Solaris/CDE HP-UX/CDE HP-UX/VUE Linux/GNOME Linux/KDE2
Getting Started
2-3
Operating Environment Software Requirements
2.3 Operating Environment Software Requirements

This section lists the operating environment requirements for Windows, Linux, Solaris, and HP-UX.
2.3.1 Windows Operating Environment

Table 24 contains the Windows operating environment software requirements for Oracle Developer Suite.
Table 24 Oracle Developer Suite Windows Software Requirements Requirement

Software Item Windows Operating Environment
Microsoft Windows NT 4.0 with Service Pack 6a Microsoft Windows 2000 Service Pack 3 or greater Microsoft Windows XP Professional Edition Service Pack 1 or greater
Note: Newer versions of Windows allow you to use a system
drive other than C. This guide refers to the system drive as the "system default drive." You are not limited to using C as the system default drive. Most examples in this guide use C as the system default drive.
2.3.2 Solaris Operating Environment for Sun SPARC workstations

For Solaris running on Sun SPARC workstations, Oracle Developer Suite requires either Solaris 8 (2.8) or Solaris 9 (2.9). Table 25 contains the Solaris patchset requirements for Oracle Developer Suite. You can download the patches from http://sunsolve.sun.com/pub-cgi/show.pl?target=patches/J2SE.
Note: Oracle9i JDeveloper running on Solaris requires the CDE windows manager.
2-4
Installation Guide
Table 25
Solaris Operating Environment Patchset Requirements Requirement

Software Item Solaris 8 (2.8)
108652-74: X11 6.4.1: Xsun 108921-17: CDE 1.4: dtwm 108940-57: Motif 1.2.7 and 2.1.1: Runtime library patch 112003-03 Unable to load fontset in 64-bit Solaris 8 iso-1 or iso-15 108773-18: IIIM and X input & output method 112138-01: usr/bin/domainname patch 111310-01 /usr/lib/libdhcpagent.so.1 109147-26 linker 111308-04 /usr/lib/libmtmalloc.so.1 112438-02 /kernel/drv/random 108434-13: 32-bit shared library patch for C++ 111111-03 /usr/bin/nawk 112396-02 /usr/bin/fgrep 110386-03 RBAC Feature 111023-02 /kernel/fs/mntfs, /kernel/fs/sparcv9/mntfs 108987-13 Patch for patchadd and patchrm 108528-24: kernel update 108989-02 /usr/kernel/sys/acctctl , /usr/kernel/sys/exacctsys 108993-26 LDAP2 client, libc, libthread and libnsl libraries 113096-03: X11 6.6.1: OWconfig 112785-26 X11 6.6.1: Xsun
Solaris 9 (2.9)
Table 26 contains the Solaris 8 (2.8) and Solaris 9 (2.9) package requirements for Oracle Developer Suite. To verify that an operating system package is installed on your computer, run the pkginfo command with the name of the package. Do this for each package listed. The syntax for pkginfo is: pkginfo package_name For example: prompt>pkginfo SUNWarc If your computer is missing a package, contact your system administrator.
Getting Started
2-5
Table 26
Solaris Operating Environment Package Requirements Requirement

Software Item Solaris 8 (2.8)
SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt SUNWi1cs SUNWi15cs SUNWarc SUNWbtool SUNWhea SUNWlibm SUNWlibms SUNWsprot SUNWsprox SUNWtoo SUNWi1of SUNWxwfnt SUNWi1cs SUNWi15cs
Solaris 9 (2.9)
2.3.3 HP-UX Operating Environment

For the HP PA-RISC HP-UX (64-bit) operating environment, Oracle Developer Suite requires either version 11.00 or version 11.11. Table 27 contains the HP-UX operating environment software requirements for Oracle Developer Suite. You can download the HP-UX operating environment patches from http://itresourcecenter.hp.com.
Table 27 HP-UX Operating Environment Software Requirements Requirement

Software Item HP-UX Operating Environment
HP PA-RISC HP-UX 11.00 (64-bit) HP PA-RISC HP-UX 11.11 (64-bit)
2-6
Installation Guide
Table 27 (Cont.) HP-UX Operating Environment Software Requirements Software Item HP-UX 11.00 Patches Requirement

Sept 2002 Quality Pack (QPK1100 B.11.00.58.5) PHKL_27813 PHSS_26559 Required HP-UX 11.00 patches for Java 2 SDK 1.4.1.05 for PA-RISC (which can be found at http://www.hp.com/products1/unix/java/patches/ index.html, or http://www.hp.com/products1/unix/java/java2/ sdkrte14/downloads/index.html) HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC X11MotifDevKit (B.11.00.01 or higher) Dec 2001 Consolidate Patches (Dec01GQPK11i_Aux_Patch B.03.02.06) PHKL_25212 PHKL_25506 PHKL_27091 PHKL_28267 PHNE_28089 PHSS_24638 PHSS_26263 PHSS_26792 PHSS_26793 Required HP-UX 11.11 patches for Java 2 SDK 1.4.1.05 for PA-RISC (which can be found at http://www.hp.com/products1/unix/java/patches/ index.html, or http://www.hp.com/products1/unix/java/java2/ sdkrte14/downloads/index.html) HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC X11MotifDevKit (B.11.11.01 or higher)
HP-UX 11.00 Software and Packages HP-UX 11.11 Patches
HP-UX 11.11 Software and Packages
Getting Started
2-7
Certified Software
2.3.4 Linux Operating Environment

Table 28 contains the Linux x86 operating environment software requirements for Oracle Developer Suite. For more information on Red Hat Linux patches, see http://www.redhat.com. For more information on United Linux patches, see http://www.unitedlinux.com.
Table 28 Linux x86 Operating Environment Software Requirements Requirement

Software Item Linux x86 Operating Environment
Red Hat Enterprise Linux AS 2.1 Red Hat Enterprise Linux ES 2.1 United Linux 1.0
Red Hat Linux Operating System Patches Red Hat Linux Operating System Software and Packages
Kernel Errata 25 (2.4.9-e.25)
gcc-2.96 pdksh-5.2.14 openmotif-2.1.30 XFree86-4.1.0
United Linux Operating System Patches United Linux Operating System Software and Packages
For the most current information, refer to the Oracle Developer Suite 10g Release Notes Addendum, which is available at Oracle Technology Network (http://otn.oracle.com).

gcc_old-2.95 pdksh-5.2.14 openmotif-2.1.30 xf86-4.2.0
2.4 Certified Software

You can view a complete list of certified software for Oracle Developer Suite on OracleMetaLink, at http://metalink.oracle.com.
2-8
Installation Guide
Coexistence in One Oracle Home
2.5 Online Documentation Requirements

The Oracle Developer Suite Documentation Library contains online documentation in HTML and Adobe PDF formats. See Appendix C, "Installing the Documentation Library" for instructions on installing and viewing the contents of the Documentation Library. Table 29 contains the tools and disk space requirements for the Oracle Developer Suite Documentation Library.
Table 29 Item Online Readers Online Documentation Requirements Requirements Requires one of the following: HTML

Netscape Navigator 4.7 or higher Microsoft Internet Explorer 5.0 or higher Acrobat Reader 3.0 or higher Acrobat Reader+Search 3.0 or higher Acrobat Exchange 3.0 or higher PDFViewer Web browser plug-in 1.0 or higher
PDF

Disk Space
130 MB
2.6 Coexistence in One Oracle Home

This section provides information about the coexistence of Oracle products in one Oracle home, and guidelines for installing multiple Oracle products on one computer.
2.6.1 Oracle Home Considerations

Your Oracle home is the top-level directory in which you install Oracle software.
Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with its previous versions (Oracle9iDS Release 2 (9.0.2) or Oracle Internet Developer Suite Release 1.0.2.x). Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with any Oracle databases, including Oracle9i Database Release 2. Oracle Developer Suite 10g (9.0.4) cannot share the same Oracle home with a Oracle Application Server Forms and Reports Services 10g standalone server instance.
Getting Started
2-9
Coexistence in One Oracle Home
Oracle Developer Suite 10g (9.0.4) can coexist in the same Oracle home with any installation of Oracle Application Server 10g (9.0.4), with the exception of Oracle Application Server Infrastructure.
Note: This does not apply to any other version of Oracle Application Server.
For Linux, Solaris, and HP-UX only: If there are existing Oracle homes set on the computer where you are installing Oracle Developer Suite, refer to Section 2.8.5.1.1, "Preventing Conflicts With Other Oracle Homes".
In this guide, directory paths may contain the placeholder text oracle_home, which represents the path to your actual Oracle home directory.
Note: If you install Oracle Developer Suite 10g (9.0.4) and Oracle
Application Server 10g (9.0.4) to the same Oracle home, do not try to start Oracle Application Server Containers for J2EE (OC4J) on port 8888 from oracle_home\j2ee\home. If you do, the OC4J instance will fail.
2.6.2 Performing Multiple Installations of Oracle Developer Suite

The following guidelines apply to installing multiple instances of Oracle Developer Suite 10g (9.0.4) on the same computer. The guidelines also apply to installing Oracle Developer Suite 10g (9.0.4) on a computer that has existing installations of Oracle9iDS or Oracle Internet Developer Suite:
1. 2. 3. 4.
Make sure you reboot the computer after you install Oracle Developer Suite the first time. Make sure you have sufficient disk space to handle all of your installations. See Table 21 to determine the disk space requirements. Install subsequent instances into a different Oracle home from the previous one. Reboot the computer after the last installation is completed (Windows only).
2.6.3 Oracle Developer Suite Installation and Oracle Databases

Note: Oracle Developer Suite can not share an Oracle home with an Oracle database.
When you install Oracle Developer Suite, and you have either already installed an Oracle database on the same computer, or plan to install an Oracle database on the same computer:
Make sure you have sufficient disk space to handle both installations. See the specific Oracle database installation guide and Table 21 in this guide to determine the total disk space requirements. Windows only: If you have not installed the Oracle database, install it first, and then reboot the computer after the database installation is completed.
2-10
Installation Guide
Preinstallation Tasks
Install Oracle Developer Suite into a different Oracle home from the Oracle database. Windows only: Reboot the computer after you have installed Oracle Developer Suite.
2.7 Directories Used by the Installer

The installer writes files to the following directories:
Table 210 Directory Oracle home directory Directories Used by the Installer Description This directory contains Oracle Developer Suite files. You specify this directory when you install Oracle Developer Suite. For more information, see Section 2.6.1, "Oracle Home Considerations". The installer uses this directory to keep track of Oracle products that are installed on the computer. In subsequent installations, the installer uses the same inventory directory. For more information, see Section 2.9.3, "The Installer Inventory Directory". This directory contains information about locations of Oracle homes on your Linux, Solaris, or HP-UX computer. For more information, see Section 2.9.3, "The Installer Inventory Directory". Note: On a Windows computer, this information is stored in the Windows Registry. The installer writes files needed only during installation to a temporary directory. By default, the temporary directory is /tmp. To specify a different directory, set the TMP environment variable. The installer writes files needed only during installation to a temporary directory. The installer uses the directory specified in the %TEMP% system environment variable.
Inventory directory
Linux, Solaris, and HP-UX only: /var/opt/oracle or /etc directories. Linux, Solaris, and HP-UX only: /tmp directory Windows only: temp directory
2.8 Preinstallation Tasks

Before installing Oracle Developer Suite, review the Oracle Developer Suite release notes. The release notes are available in the Oracle Developer Suite Documentation Library. To view the release notes, see Section C.3.1, "Viewing the Release Notes from Disk". The latest release notes and release notes addendum are also available on Oracle Technology Network at http://otn.oracle.com The preinstallation tasks for Oracle Developer Suite are divided into the following parts:

General Checklist Setting the Locale Using Assistive Technologies (Windows only) Installing Java Access Bridge (Windows only)
Getting Started 2-11
Setting Environment Variables (Linux, Solaris, and HP-UX only) Creating Linux, Solaris, and HP-UX Accounts and Groups Completing Component-specific Preinstallation Tasks Information Needed During Installation Migration or Upgrading
2.8.1 General Checklist

1.
HP-UX only:
a.
Download the HP Java 2 SDK 1.4.1 (version 1.4.1.05 or higher) for PA-RISC (for HP-UX 11.00 or HP-UX 11.11, depending on your operating system version) from http://www.hp.com/products1/unix/java/java2/sdkrte14/ index.html. Install the SDK.
b. 2.
If you have Windows NT, 2000, or XP Professional, ensure that you are logged on to your computer as a member of the Administrators group. On Linux, Solaris, or HP-UX, ensure that you are not logged in as the root user; otherwise, you will not be able to run the installer. See Section 2.8.6, "Creating Linux, Solaris, and HP-UX Accounts and Groups" for more information. Ensure that your PATH,CLASSPATH,LD_LIBRARY_PATH(Linux, Solaris, and HP-UX only), and SHLIB_PATH (HP-UX only) environment variable values do not exceed 1,024 characters. Variable values greater than 1,204 characters will generate errors such as "Word too long" during installation. Stop all Oracle services or Oracle processes, and close all other open applications.
2.8.2 Setting the Locale

The installer user interface language is based on settings in the Java Virtual Machine (JVM) locale, which is based on the operating environment locale. To run the installer with a particular locale, set your operating environments locale before you start the installer. The installer supports the locale languages listed in Table 211:
Table 211 Language English French German Italian Japanese Korean Brazilian Portuguese Languages Displayable by the Installer ISO-639 Language Code en fr de it ja ko pt_BR
2-12
Installation Guide
Table 211 Language
(Cont.) Languages Displayable by the Installer ISO-639 Language Code zh_CN zh_TW
Simplified Chinese Traditional Chinese
If your locale is not listed in this table, the installer appears in English.
2.8.3 Using Assistive Technologies (Windows only)

If you use assistive technologies such as screen readers to work with Java-based applications and applets, run access_setup.bat before starting your screen reader. The file access_setup.bat is located on your CD-ROM Disk 1, or on your DVD:
Media CD-ROM DVD Location of File \install\win32 \developer_suite\install\win32
2.8.4 Installing Java Access Bridge (Windows only)

If you use assistive technologies such as screen readers to work with Java-based applications and applets, the Windows-based computer where you are installing Oracle Developer Suite must have Sun's Java Access Bridge installed in all the Java virtual machine locations on the computer. The installer installs files for JDK/JRE 1.4.1 and JDK/JRE 1.1.8 on your computer, but it will install Java Access Bridge 1.0.3 files in the JDK/JRE 1.4.1 location only. If you use assistive technologies, you should perform one of the following steps:
If you dont have JDK/JRE 1.1.8 installed on your computer: Proceed with your installation. After you have finished installing Oracle Developer Suite, ensure that you have Java Access Bridge 1.0.3 installed in all your JDK/JRE locations. This will ensure that all your applications that require assistive technologies work correctly.
If you do have JDK/JRE 1.1.8 on your computer: You must install the production version of Java Access Bridge 1.0.2 in the JDK/JRE 1.1.8 location on your computer before you install Oracle Developer Suite. To download and install Java Access Bridge 1.0.2:
1.
Download the zip file for Java Access Bridge 1.0.2 from http://java.sun.com/products/accessbridge/. Refer to the Java Access Bridge documentation available from the web site for installation instructions and other information.
2. 3.
After downloading the file, extract the contents to a folder; for example, accessbridge_home. Install Java Access Bridge by running install.exe from the accessbridge_home\installer folder, where accessbridge_home is the folder you created in the previous step.
4.
Confirm that you want to install the Java Access Bridge into each of the Java virtual machines displayed in the dialog.
Note: Do not install Java Access Bridge 1.0.2 into a Java virtual
machine with a version higher than 1.1.18.

5.
Click OK when you see the Installation Completed message.
2.8.5 Setting Environment Variables (Linux, Solaris, and HP-UX only)

The tasks in this section are required on Linux, Solaris, and HP-UX platforms only.
2.8.5.1 ORACLE_HOME
2.8.5.1.1
Preventing Conflicts With Other Oracle Homes
To prevent a conflict between the software in an existing Oracle home and the Oracle Developer Suite installation, you must remove all references to the existing Oracle home in your environment. Follow these steps to remove these references.
1.
Unset your existing Oracle home variable by using the following command.
Bourne/Korn shell prompt> ORACLE_HOME=; export ORACLE_HOME
C shell prompt> unsetenv ORACLE_HOME
2.
In your PATH, CLASSPATH,LD_LIBRARY_PATH, and SHLIB_PATH (HP-UX only) environment variables, remove any references to the environment variable ORACLE_HOME.
2.8.5.2 DISPLAY
Setting the DISPLAY environment variable allows you to run the installer remotely and view the installer UI from your local computer. On the remote computer, set DISPLAY to the system name or IP address of your local computer.
Note: A PC X emulator can be used to run the install if it supports
a PseudoColor color model or PseudoColor visual. Set the PC X emulator to use a PseudoColor visual, and then start the installer. Refer to the X emulator documentation for instructions on how to change the color model or visual settings.
2-14
Installation Guide
If you get an Xlib error similar to "Failed to connect to server", "Connection refused by server", or "Can't open display" when starting the installer, then run the following commands on your local computer:
Shell Types C shell Bourne or Korn shell
On the remote computer prompt> setenv DISPLAY hostname:0.0 prompt> DISPLAY=hostname:0.0; export DISPLAY
On your local computer prompt> xhost + server_name prompt> xhost + server_name
2.8.5.3 TMP
During installation, the installer uses a temporary directory for swap space. You must ensure that this directory meets the hardware requirements listed in Table 21 before you start your installation. The installation may fail if you do not have sufficient space. The installer checks for the TMP environment variable to locate the temporary directory. If this environment variable does not exist, then the installer uses the /tmp directory. The following are instructions for setting the TMP environment variable.
C shell prompt> setenv TMP full_path Bourne/Korn shell prompt> TMP=full_path; export TMP
2.8.5.4 TNS_ADMIN
TNS_ADMIN points to the directory where network configuration files are stored. If TNS_ADMIN is set to an existing directory on your computer, you will have conflicts between that directory and the directory where the Oracle Developer Suite network configuration files are created. You will also have conflicts if the configuration files are in a common directory outside of the Oracle home for your other Oracle products. For example, your computer may use /var/opt/oracle/tnsnames.ora for database aliases. To prevent conflicts between the network configuration files for different Oracle products, copy the existing configuration files from either the existing TNS_ADMIN directory or the common directory to the other products oracle_ home/network/admin and unset TNS_ADMIN using the following command:
C shell prompt> unsetenv TNS_ADMIN Bourne/Korn shell prompt> TNS_ADMIN=;export TNS_ADMIN
2.8.6 Creating Linux, Solaris, and HP-UX Accounts and Groups

The tasks in this section are required on Linux, Solaris, and HP-UX platforms only.
2.8.6.1 Group Name for the Installer Inventory

Create a group that has read and write access to the oraInventory directory. The installer uses the oraInventory directory to keep track of the Oracle products installed on a computer. You can allow a user to install Oracle products to the computer by giving it write access to oraInventory. To do this, make all the users members of the same group. This guide refers to the group as the devsuitegrp group.
Use a an operating environment utility to create the group. For example:

On Solaris, use the admintool or groupadd utility. On HP-UX, use the SAM utility. On Linux x86, use /usr/sbin/groupadd and/usr/sbin/useradd.
These utilities are described in your operating environment documentation. The devsuitegrp group will own the installer's oraInventory directory. Any user account that runs an Oracle installation must be a member of the devsuitegrp group.
2.8.6.2 User for Oracle Software

If this is the first time you are installing Oracle software on this computer, Oracle recommends that you start by creating a new user. Use this user specifically for installing and administering Oracle software. Create the user with the properties listed in Table 212.
Table 212 Variable name Group Identifier Home directory Oracle Account Properties Property Choose any name This guide uses the name oracle. The devsuitegrp group. Choose a home directory consistent with other user home directories. The home directory of the oracle account does not have to be the same as the Oracle home directory. The default shell can be either the C, Bourne, or Korn shell.
Login Shell
Note: Use this user only for installing and maintaining Oracle
software. Never use it for purposes unrelated to the installer. Do not use root for the Oracle user.
2.8.7 Completing Component-specific Preinstallation Tasks

Components that are not listed here have no component-specific preinstallation tasks.
2.8.7.1 Oracle Software Configuration Manager

There are no specific preinstallation requirements. However, to effectively use Software Configuration Manager, Oracle recommends that you review the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client.
2-16
Installation Guide
Preparing to Start the Installer
2.8.8 Information Needed During Installation

The installer guides you through the installation screens. Depending on your operating environment and the installation options you select, you will need the information listed in Table 213.
Table 213 Item Oracle home name and path for Oracle Developer Suite 1 Information Needed During Installation Installation Type All (Windows, Linux, Solaris, and HP-UX) Example Name: DevSuiteHome Path: C:\DevSuiteHome or /private/DevSuiteHome Linux, Solaris, and HP-UX group name Outgoing mail server name All (Linux, Solaris, and HP-UX only) Business Intelligence, Rapid Application Development, Complete (all platforms). Used only by Oracle Application Server Reports Services. All (HP-UX only) devsuitegrp mysmtp01.mycorp.com
Java SDK directory

1
/opt/java/java.1.4.1
See Section 2.6.1, "Oracle Home Considerations" for more details.
2.8.9 Migration or Upgrading

Review Appendix A, "Upgrade Notes" if you are migrating or upgrading from:

Oracle9iDS Release 2 (9.0.2) Oracle Internet Developer Suite release 1, version 1.0.2.x (the former version of Oracle9i Developer Suite) A 9.0.3 or earlier version of any Oracle Developer Suite component (for instance, Oracle JDeveloper, Oracle Repository, and so forth)
2.9 Preparing to Start the Installer

This section introduces Oracle Universal Installer and provides you information that you should know before you start the installation.
2.9.1 About Oracle Universal Installer

Oracle Developer Suite uses Oracle Universal Installer to install components and to configure environment variables. The installer guides you through each step of the installation process. Oracle Universal Installer automates the tasks of:
Providing installation options for products, based on the target computers operating environment Detecting pre-set environment variables and configuration settings Setting environment variables and configuration during installation Deinstalling products
2.9.2 Installer Prerequisite Checks

The installer does an automatic prerequisite check on your computer before starting the installation. The following tables list the prerequisite checks that the installer performs. Table 214 lists the automatic prerequisite checks for Windows:
Table 214 Installer Prerequisite Checks for Windows See Also Table 21, " Oracle Developer Suite Hardware Requirements"
Prerequisite Checks Verify the computer can display a minimum of 256 colors Verify the minimum CPU speed Verify the operating system requirements
Table 21, " Oracle Developer Suite Hardware Requirements"
Table 23, " Operating Environments and Oracle Developer Suite Components" Table 24, " Oracle Developer Suite Windows Software Requirements"
Table 215 lists the automatic prerequisite checks for Solaris on Sun SPARC computers:
Table 215 Installer Prerequisite Checks for Solaris See Also Table 21, " Oracle Developer Suite Hardware Requirements"
Prerequisite Checks Verify the computer can display a minimum of 256 colors Verify that the minimum swap space is available Verify the minimum CPU speed Verify Operating System requirements
Table 21, " Oracle Developer Suite Hardware Requirements" Table 21, " Oracle Developer Suite Hardware Requirements"
Table 23, " Operating Environments and Oracle Developer Suite Components" Table 25, " Solaris Operating Environment Patchset Requirements" Table 26, " Solaris Operating Environment Package Requirements"
Table 216 lists the automatic prerequisite checks for Linux x86:
Table 216 Installer Prerequisite Checks for Linux See Also Table 21, " Oracle Developer Suite Hardware Requirements" Table 21, " Oracle Developer Suite Hardware Requirements"
Prerequisite Checks Verify that the minimum swap space is available Verify the minimum CPU speed Verify Operating System requirements
Table 23, " Operating Environments and Oracle Developer Suite Components" Table 28, " Linux x86 Operating Environment Software Requirements"
2-18
Installation Guide
Table 217 lists the automatic prerequisite checks for HP-UX:

Table 217 Installer Prerequisite Checks for HP-UX See Also Table 21, " Oracle Developer Suite Hardware Requirements" Table 21, " Oracle Developer Suite Hardware Requirements"
Prerequisite Checks Verify that the minimum swap space is available Verify the minimum CPU speed Verify Operating System requirements
Table 23, " Operating Environments and Oracle Developer Suite Components" Table 27, " HP-UX Operating Environment Software Requirements"
2.9.3 The Installer Inventory Directory

The installer creates the inventory directory the first time it runs on your computer. The inventory directory keeps a record of the products that the installer has installed, as well as other installation information. If you have previously installed Oracle products on your computer, then you may already have an inventory directory. Please review the following information about the inventory directory:
Do not delete or alter the inventory directory or its contents. Doing so can prevent the installer from locating products that you have installed on your computer. For Windows, the installer automatically creates the inventory directory as system_default_drive:\Program Files\Oracle\Inventory when you install the first Oracle product on your computer. The value of system_default_drive is normally "C:", and is set in the Windows Registry. For Linux, Solaris, and HP-UX, the default directory location is listed in the file /var/opt/oracle/oraInst.loc (/etc/oraInst.loc on Linux). The first time you install an Oracle product on your computer, the installer prompts you for an existing directory to use as the inventory directory. The installer then creates oraInst.loc and lists your inventory directory in it. If you specify a Linux, Solaris, or HP-UX group name during installation, you are granting any user that belongs to that group the permission to write to the oraInventory directory. Later on, if another user attempts to run the installer, then they must have user-level permission to write to the oraInventory directory, or they must belong to the group you specified. If they do not have permission, then the installation fails.
The installer writes a log of its actions to a file in the directory system_default_drive:\Program Files\Oracle\Inventory\logs (Windows) or inventory_location/logs (Linux, Solaris, and HP-UX). The log file name has the form installActionsyear-date_time.log.
2.9.4 Starting the Installer

Follow these instructions to start the installer:
2.9.4.1 For Windows users

Note: If you encounter a Windows System Files error during
installation, click OK to close the error dialog. Then follow the instructions for running the Windows System Files installation later in this section.
1. 2.
Stop all Oracle services such as an Oracle database. CD-ROM:Insert the Oracle Developer Suite CD-ROM labeled "Disk 1" into your computers CD-ROM drive. DVD: Insert the Oracle Developer Suite DVD labeled "Oracle Developer Suite and Documentation" into your computers DVD drive.
3.
CD-ROM: If you are not using the autorun feature, locate the program setup.exe in the root directory of the CD-ROM. Start the installer by running this program. DVD: If your are not using the autorun feature, locate the program setup.exe in the directory \developer_suite under the root directory of the DVD. Start the installer by running this program.
4. 5.
If you are using the autorun feature, the installer will start automatically. Click Install Oracle Developer Suite to start your installation. For users of Windows assistive technologies: To disable the autorun feature, hold down the Shift key after inserting the CD-ROM or DVD. Alternatively, if the autorun window appears, press ALT-F4 to close the window. Then do one of the following:
a.
CD-ROM: To install Oracle Developer Suite, locate the program setup.exe in the root directory of the CD-ROM. Start the installer by running this program. DVD: To install Oracle Developer Suite, locate the program setup.exe in the directory \developer_suite under the root directory of the DVD. Start the installer by running this program.
b. c.
To browse the CD-ROM or DVD contents, use Windows Explorer. To learn about Oracle Developer Suite, point your browser to the file \doc\welcome\index.htm on the CD-ROM, or \developer_suite\ doc\welcome\index.htm on the DVD.
Proceed to Section 3.1, "Installing Oracle Developer Suite" to continue. 2.9.4.1.1 Windows System Files Installation
Oracle Developer Suite requires several files to be present in your Windows system directory. During the Oracle Developer Suite installation, files already present on your computer are examined to ensure that they meet the requirements for Oracle Developer Suite. If a file is not present or is present but outdated, the installer installs the required file. If an outdated file is in use by another process at the time of installation, then the installer will stop and display an error dialog. This is because Windows needs to restart for the updated file to take effect. The installer cannot automatically shut down and then start up again after a system restart.
2-20
Installation Guide
Oracle Developer Suite includes a supplementary installation for the required Windows system files. This installation will automatically reboot the computer if necessary when it is finished. If you encounter the Windows System Files error during the Oracle Developer Suite installation, click OK to close the error dialog, then use the following instructions to start the Windows System Files installation. You cannot proceed with the Oracle Developer Suite installation if you do not run the Windows System Files installation. To start the Windows System Files installation:
1. 2. 3.
Click Exit to quit the installer. Change to the root directory on the CD-ROM, or to the directory \developer_ suite under the root directory of the DVD. Run wsf.exe. The Windows System Files installer is controlled by script that attempts to find an existing Oracle home. If the installer does not find one, it displays a File Locations dialog. Choose your Oracle home from the dialog. Windows restarts automatically, if it is required; otherwise, the Windows System Files installation ends without displaying the Installation Finished dialog.
4.
After Windows restarts, or when the Windows System Files installation finishes, restart the Oracle Developer Suite installation.
2.9.4.2 For Linux, Solaris, and HP-UX users

Note: You need access to the root account.
For operating environments that do not support automatic mounting, you must manually mount the installation CD-ROM or DVD. You must have root privileges to mount or unmount a CD-ROM or DVD. Be sure to unmount a CD-ROM or DVD before removing it from the drive.
Note: The Oracle Developer Suite installation CD-ROM is in
RockRidge format. The Oracle Developer Suite and Documentation DVD is in DVD-ROM format. To mount the installation CD-ROM or DVD:
1. 2.
Stop all Oracle processes such as the Oracle database. Read the section for your operating environment to get detailed mounting instructions:

Mounting CD-ROMs and DVDs to Solaris Mounting CD-ROMs and DVDs to HP-UX Mounting CD-ROMs and DVDs to Linux Mounting CD-ROMs and DVDs to Solaris
2.9.4.2.1
If your computer is set up for auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive.
If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually. Follow these steps to mount the CD-ROM or DVD manually:
1. 2. 3.
Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into the drive. Log in as the root user. Ensure that you have a mount point directory for the CD-ROM or DVD. For example, you can create the directory /cdrom: # mkdir /cdrom
4.
Mount the CD-ROM or DVD drive to the mount point directory. For example, if your mount point directory is /cdrom, enter the following command: # mount -r -F hsfs device_name /cdrom
5. 6.
Log out as the root user. Proceed to Section 2.9.4.2.4, "Running the Installer". Mounting CD-ROMs and DVDs to HP-UX
2.9.4.2.2
If your computer is set up for auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive. If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually.
Note: Before executing any of the following steps, consult the man
pages for pfs_fstab, pfs_mount, pfs_mountd, and pfsd. Follow these steps to mount the CD-ROM or DVD manually:
1. 2.
Log in as the root user. Use the following command to determine the CD-ROM or DVD device_file: # ioscan -fun -C disk
3.
If there is not already an entry in the /etc/pfs_fstab file for your CD-ROM or DVD device_file, you must add one. As the root user, use a text editor to add a line to the /etc/pfs_fstab file following this format:
device_file mount_point filesystem_type options frequency pass
Example:
/dev/dsk/c5t2d0 /SD_CDROM pfs-rrip ro 0 0
Note: This example assumes the existence of an empty
/mnt/cdrom directory. If one does not exist, create it.

4.
Enter the following commands: # nohup /usr/sbin/pfs_mountd & # nohup /usr/sbin/pfsd &
2-22
Installation Guide
5.
Insert the Oracle Developer Suite Disk 1 CD-ROM or Oracle Developer Suite and Documentation DVD into your drive and mount the CD-ROM by entering the following command: # /usr/sbin/pfs_mount /SD_CDROM
6. 7.
Log out as the root user. Proceed to Section 2.9.4.2.4, "Running the Installer". Mounting CD-ROMs and DVDs to Linux
2.9.4.2.3
If your computer is set up for CD-ROM or DVD auto mounting, then the CD-ROM or DVD is mounted automatically to the directory specified in your auto mount configuration when you insert the disk into the drive. If your computer is not set up for auto mounting, then you must mount the CD-ROM or DVD manually. Follow these steps to mount the CD-ROM or DVD manually:
1. 2. 3.
Insert the Oracle Developer Suite Disk 1 CD-ROM or the Oracle Developer Suite and Documentation DVD into your drive. Log in as the root user. Ensure that you have a mount point directory for the CD-ROM or DVD. For example, you can create the directory /mnt/cdrom: # mkdir /mnt/cdrom
4.
Ensure that the following line for /dev/cdrom is in /etc/fstab: /dev/cdrom /mnt/cdrom iso9660 noauto,owner,kudzu,ro 0 0
Note: The file /etc/fstab must contain this line exactly as it
appears in the text. Replace any other form of the line with the line in the text.
5.
Mount the CD-ROM or DVD drive to the mount point directory by entering the following command: # /bin/mount /mnt/cdrom This command mounts the CD-ROM or DVD to the mount point directory /mnt/cdrom.
6. 7.
Log out as the root user. Proceed to Section 2.9.4.2.4, "Running the Installer".
2.9.4.2.4
Running the Installer
After you mount the installation CD-ROM or DVD, you can start the installer. To start the installer from the CD-ROM or DVD:
Note: Be sure you are not logged in as the root user when you start the installer. If you are, you will receive an error message and the installer will stop.
1. 2.
Log in with the user that you created for installing Oracle products (see Section 2.8.6.2, "User for Oracle Software"). Change to a directory other than the mount point directory or its subdirectories. For example, if your mount point directory is /mnt/cdrom, change to a directory other than /mnt/cdrom or its subdirectories. CD-ROM: Start the installer by entering: prompt> mount_point_directory/runInstaller DVD: Start the installer by entering: prompt> mount_point_directory/developer_suite/runInstaller
3.
This starts the installer. Proceed to Section 3.1, "Installing Oracle Developer Suite" for further instructions.
2.9.4.3 Running the Installer in Silent or Non-Interactive Mode

See Appendix D, "Silent and Non-Interactive Install"
2-24
Installation Guide
3
Installation
Before you proceed with your installation, make sure you have reviewed and performed the preinstallation tasks described in Chapter 2, "Getting Started". This chapter provides detailed installation steps and basic postinstallation tasks. The topics include:

Installing Oracle Developer Suite Postinstallation Tasks
3.1 Installing Oracle Developer Suite

For instructions on starting the installer, see Section 2.9.4, "Starting the Installer".
Note:
(For Windows only) If you encounter a Windows System Files error during installation, click OK to close the error dialog. Then follow the instructions in Section 2.9.4.1.1, "Windows System Files Installation". The installer appears in the language specified in the current locale.
The installer first does automatic prerequisite checks. These run in a command line window which appears before the installer displays the Welcome screen. If a prerequisite check fails, the installer displays an error message and then stops. Section 2.9.2, "Installer Prerequisite Checks" describes the installers automatic prerequisite checks.
Installation
3-1
Installing Oracle Developer Suite
Next, the installer displays the Welcome screen.

1.
Review the Welcome screen and click Next. The Welcome screen provides information about Oracle Universal Installer. The following function buttons appear on the Welcome screen and all installation screens that follow it:
Help: Click this to access detailed information about the functionality of each screen. Installed Products: Click this to view currently installed products and deinstall products. Back: Click this to return to the previous screen. This button is disabled on the Welcome screen. Next: Click this to move to the next screen. This button may be disabled on some screens. Install: Click this to begin installing the files
Note: This function button is disabled until you reach the
Summary screen.
Cancel: Click this to quit the installation process and exit the installer.
The Welcome screen has two additional buttons. They are:

Deinstall Products: Click this to deinstall individual products or all products. About Oracle Universal Installer: Click this to view the version of the installer you are using.
For more detailed information about the Installed Products and Deinstall Products options, see Section 4.1.1, "Deinstalling Using the Installer".
2.
If this is the first time you have installed an Oracle product on this computer, the installer creates the inventory directory for installation-related files (see Section 2.9.3, "The Installer Inventory Directory" for more information about this directory). The creation process differs between Windows, Linux, Solaris, and HP-UX:
Windows: The installer creates the directory system_default_drive\Program Files\Oracle\Inventory, where system_default_drive is the drive where you installed Windows, usually C. Linux, Solaris, and HP-UX: The Specify Inventory Directory screen appears. You must enter an existing directory as the location for the inventory directory. For example, you might use /private1/oraInventory. To navigate through the file system to select the inventory directory, use the Browse button. To continue the installation process, click OK.
3-2
Installation Guide
3.
For Linux, Solaris, and HP-UX only: (First time installation) At the UNIX Group Name screen, enter a group name. The UNIX Group Name screen only appears when you run the installer for the first time on a computer. You use this screen to specify a group that has permission to read from and write to the inventory directory. For more information, refer to Section 2.8.6, "Creating Linux, Solaris, and HP-UX Accounts and Groups". Unix Group Name: Enter the group name. This group should have read and write access to the inventory directory. The user that you are using to run the installer should be a member of this group. When you have finished, click Next to continue.
4.
For Linux, Solaris, and HP-UX only: The installer displays a screen that prompts you to run the shell script orainstRoot.sh. You must run this script with root privileges. You may need to execute the shell script by typing "./" before orainstRoot.sh. The screen lists the location of the shell script file. The script creates pointers to the components as the installer installs them in the computer so that they can be identified later in the installation procedure. The script creates the file /var/opt/oracle/oraInst.loc (/etc/oraInst.loc on Linux), which provides a pointer to your inventory directory. After you have run the script, return to this screen and click Continue to continue.
5.
At the Specify File Locations screen, verify the source and destination paths and enter or select an Oracle home name. The Specify File Locations screen lets you enter the full path for the source and destination locations for your installation.
Source: This is the full path to the products.jar file from which the product will be installed. The installer detects and uses the default values of the products.jar file of the installation program. Do not change the path. Destination: This is the name and full path to the Oracle home where the product will be installed. You may use the default name and path provided or select another name. See Section 2.6.1, "Oracle Home Considerations" if you need more information.
Note: The Oracle home path must be a real, absolute path. It
cannot contain environment variable names or spaces. Do not install Oracle Developer Suite into an existing: Oracle9iDS Release 2 (9.0.2) home directory. Oracle Internet Developer Suite home directory (former version of Oracle Developer Suite) Oracle Database home directory (including Oracle8i and Oracle9i)
For more information about Oracle homes, see Section 2.6, "Coexistence in One Oracle Home".
Browse: To navigate through the file system to find source and destination locations, use the Browse button.
Installation
3-3
When you have finished entering the information, click Next to continue.
6.
If the computer you are installing on is part of a hardware cluster, the Specify Hardware Cluster Installation Mode screen may appear. Choose the option Single Node or Cold Failover Cluster Installation, which performs the installation on the current install node only (The Active Failover Cluster Installation option is not supported in this release). At the Select Installation Types screen, select the type of installation you want to perform and the product languages to install. The available install options are:
7.
J2EE Development: Select this option to install Oracle9i JDeveloper and its subcomponents (Oracle Business Intelligence Beans, UIX, Bali, and XDK), and Oracle Application Server Containers for J2EE (OC4J). This option configures OC4J as the default listener for testing purposes. Business Intelligence: (Windows only) Select this option to install Oracle Discoverer Administrator (including Oracle Discoverer Desktop), and Oracle Reports Developer. This option also installs OC4J and Oracle Application Server Reports Services, and configures OC4J as the default listener for testing purposes.
Note: Oracle BI Beans is a component of JDeveloper. To use
Oracle BI Beans, install the J2EE Development option as well.
Rapid Application Development: (Windows only) Select this option to install Oracle Forms Developer, Oracle Designer, Oracle Software Configuration Manager, Oracle Reports Developer, and Oracle9i JDeveloper. This option also installs OC4J, Oracle Application Server Reports Services, and Oracle Application Server Forms Services, and configures OC4J as the default listener for testing purposes. Complete: Select this option to install all Oracle Developer Suite components. Not all components are available on Linux, Solaris, and HP-UX. See Table 23, " Operating Environments and Oracle Developer Suite Components" for the Oracle Developer Suite components that are installed on Linux, Solaris, and HP-UX. Product Languages: To select the languages that Oracle Developer Suite will run in, click the Product Languages button to display the Language Selection screen. You can install multiple languages and then switch between languages by changing the NLS_LANG environment variable. At runtime, if translations are available for the language specified in NLS_LANG, the component will display in the specified language, otherwise the product will run in English. At the Language Selection screen, select the languages you want the installed product to run in. If you are running the installer in a locale that uses English, only English will be selected. If you are running the installer in a locale that uses another language, English and the locales default language will be selected. The Language Selection screen lets you select multiple languages to be installed. Do the selection by shuttling languages from the Available Languages list to the Selected Languages list. To do this: Select a language or languages from the Available Languages list. To select more than one language, select one language and then hold down the CTRL key and select additional languages. Note that selecting
3-4
Installation Guide
languages here does not affect the language of the installation program itself. After making your selections, click the right arrow button to move the selected languages to the Selected Languages list. To select all the languages, click the double right arrow button. To deselect a language, click the language and click the left arrow button to move the selected language back to the Available Languages list. To deselect all the languages, click the double left arrow button. When you have finished selecting languages, click OK to continue.
When you have selected the type of installation you want to perform, and you have selected the product languages you want, click Next to continue.
8.
For all installation types except J2EE, the installer displays the Provide Outgoing Mail Server Information screen. This screen lets you enter a name for the outgoing mail server that Oracle Application Server Reports Services (Reports Services) uses to distribute reports and send job success notifications via e-mail. An example of a outgoing mail server name is mysmtp01.mycorp.com. If you do not wish to use this feature, leave the name blank. When you have finished, click Next to continue.
9.
HP-UX only: At the Choose JDK Home Directory screen, enter the full path to the HP Java 2 SDK 1.4.1 directory. Then click Next to continue.
Note: The HP-UX version of Oracle Developer Suite does not
include a Java SDK. You must install the Java SDK yourself before you start an Oracle Developer Suite installation. For the HP Java SDK requirements, see Table 27, " HP-UX Operating Environment Software Requirements". For instructions on obtaining and installing the HP Java SDK, see Section 2.8.1, "General Checklist".
10. Verify the information in the Summary screen and click Install to begin installing
the files. The Summary screen lets you review the selections you have made before the actual installation starts. The Summary list includes the source and destination locations, installation type, product languages, space requirements, and the components to be installed. To make changes to any of the selections, click Back to return to the appropriate screen.
Note: Insufficient disk space is indicated in red under Space
Requirements.
11. The Install screen appears and the installer begins copying the required files for
Oracle Developer Suite. Monitor the progress of the installation. The Install screen appears while the product is installing. Installation operations include executing actions such as file copy and linking, and execution decision points and calculations. At the Install screen, you can:
Monitor the installation process.

Installation 3-5
See the full path of the installation log. For more information about the installation log, see Section 2.9.3, "The Installer Inventory Directory". Click Stop Installation... to discontinue the installation process. You can then choose to stop the installation of the entire product (default) or an individual component. Oracle recommends that you stop the entire product installation. If you choose to stop the installation of an individual component, associated components in the product may not function properly.
12. The Configuration Assistants screen may appear while the Oracle Net
Configuration Assistant is running. This assistant configures basic network components and creates the tnsnames.ora and sqlnet.ora files for you. The Oracle Net Configuration Assistant tool is started by the installer. Click Help on the Oracle Net Configuration Assistant Welcome screen if you need information on how to use the tool. Once you are finished with this screen, click Next to continue.
Note: The configuration assistant may run in silent mode, which
means that its UI will not be visible while it is running. The UI may also appear only briefly before the assistant finishes. If the UI appears and the installation pauses, the assistant has encountered an error. At the Configuration Assistants screen, you can:

Monitor the configuration process. Click Stop to quit a configuration tool. View the configuration settings that have been made by a configuration tool. Click a configuration tool name to display the configuration details in the display window. Click Retry to execute the configuration tool again, if the tool failed to complete the configuration successfully.
For users of Windows assistive technologies: If you are using assistive technologies and you encounter a problem with the screen reader at this stage of the installation, follow these instructions:
a.
Press ALT-F4 to cancel the Net Configuration Assistant, then exit the installer. This does not affect the Oracle Developer Suite installation; it only stops the Net Configuration Assistant tool. Install Java Access Bridge 1.0.2 into the JRE 1.1.8 location on your computer. See Section 2.8.4, "Installing Java Access Bridge (Windows only)" for information on downloading and installing Java Access Bridge 1.0.2. Set the following environment variable if it has not been set:
ORACLE_OEM_CLASSPATH=program_drive:\Program Files\Oracle\jre\1.1.8\ lib\access-bridge.jar;program_drive:\Program Files\Oracle\jre\1.1.8\ lib\jaccess.jar
b.
c.
where program_drive is the drive that contains the directory Program Files.
3-6
Installation Guide
Postinstallation Tasks
d. e.
Restart your screen reader. Restart the Net Configuration Assistant tool on the Windows Start Menu as follows: Start > Programs > Oracle - oracle_home> Configuration and Migration Tools > Net Configuration Assistant
13. If the installer is still displaying the Configuration Assistants screen, click Next to
continue.
14. After installing the product, the installer displays the End of Installation screen.
To exit the installation program, click Exit. A message dialog appears, prompting you to confirm that you want to exit the installation program. Click Yes to exit; click No to continue with the installation program. After successfully installing the product, proceed to Section 3.2, "Postinstallation Tasks" for further instructions.
3.2 Postinstallation Tasks

The postinstallation tasks for Oracle Developer Suite are divided into the following parts:

General Checklist Completing Component-specific Postinstallation Tasks Starting a Component Additional Documentation
Note: Unless otherwise differentiated, oracle_home denotes the Oracle Developer Suite home directory you used during installation.
3.2.1 General Checklist

Review the following general postinstallation checklist and perform the tasks that apply to your installation and environment.
3.2.1.1 Updates
Once you have completed your installation, you should check for the latest certification and software updates on OracleMetalink (http://metalink.oracle.com). OracleMetalink provides access to technical information and assistance from Oracle Support Services, including information about:

product availability certification product alerts bug information patches technical solutions service request logging
Installation
3-7
Oracle Technology Network (http://otn.oracle.com) also provides services and resources that developers can use to build, test, and deploy applications using Oracle products and industry-standard technologies.
3.2.1.2 NLS
You may have to perform some postinstallation tasks to enable NLS support for the components you have installed. 3.2.1.2.1 Component Languages
You can display an Oracle Developer Suite components user interface in any language you selected during installation. To do this, you set the NLS_LANG environment variable. NLS_LANG controls the language, territory dependent conventions, and character set used by the component. Until you change NLS_LANG to a different value, all Oracle Developer Suite components will use its settings. NLS_LANG has three parts: language, territory, and character set. They are set with the format <language>_<territory>.<character_set> For example, the value Japanese_Japan.JA16EUC sets NLS_LANG so that components run in Japanese, use Japanese cultural conventions, and use the EUC character set for data manipulation. Refer to the Oracle Application Server 10g Globalization Guide (included in the Oracle Application Server Documentation Library) for more documentation about NLS_ LANG. 3.2.1.2.2 Additional Fonts
When you choose a set of product languages during installation, the installer automatically installs fonts so that the JDK can display the languages correctly. The fonts are installed in the directory oracle_home/jdk/jre/lib/fonts. Later, you may need to display text in a language that you did not choose during installation. If you are using a Java-dependent component, such as Oracle9i JDeveloper, UIX, or Oracle Reports Developer, you will not have the font that Java needs. To fix this, you can install the font manually. The following Table 31 describes the fonts that are included with Oracle Developer Suite.
Table 31 Filename ALBANWTJ.TTF ALBANWTK.TTF ALBANWTS.TTF ALBANWTT.TTF ALBANYWT.TTF NLS Fonts included with Oracle Developer Suite Description Albany WT Japanese font Albany WT Korean font Albany WT Simplified Chinese font Albany WT Traditional Chinese font Albany WT font for non-English languages other than Japanese, Chinese, or Korean.
3-8
Installation Guide
To install a font, choose the appropriate font name from the table, then install it by performing the following steps:
1.
CD-ROM: Mount the Oracle Developer Suite CD-ROM labeled Disk 2. For instructions on how to mount the CD-ROM for your platform, see Section 2.9.4, "Starting the Installer". DVD: Mount the Oracle Developer Suite DVD labeled "Oracle Developer Suite and Documentation." For instructions on how to mount the DVD for your platform, see Section 2.9.4, "Starting the Installer".
2. 3.
If the installer starts up, close it. You will not use it to install the fonts. CD-ROM: Navigate to the root directory of the CD-ROM, then navigate to the subdirectory /extras/fonts. DVD: Navigate to the root directory of the DVD, then navigate to the subdirectory /developer_suite/extras/fonts.
4.
Copy the font file to oracle_home/jdk/jre/lib/fonts.
3.2.1.3 TNS Names

Depending on the installation type selected, the tnsnames.ora and sqlnet.ora files may be installed in the oracle_home\network\admin directory (Windows) or oracle_home/network/admin directory (Linux, Solaris, and HP-UX). You can update the files manually using a text editor, or use the configuration tool, Oracle Net Configuration Assistant. For more information about the configuration tool, refer to the manuals Oracle9i Net Services Administrators Guide or Net8 Administrators Guide in the Oracle database documentation library.
3.2.1.4 Port Numbers

The installer automatically assigns ports to Oracle Developer Suite components that require them. If the installer detects a port conflict while installing a component, it chooses an alternate port in the port number range allocated to the component. After installation, the installer creates a file that shows the port assignments it has made. You should review the port assignments to make sure that they are acceptable. The port assignment file is called portlist.ini. It is located in the oracle_ home\install directory (Windows) or oracle_home/install directory (Linux, Solaris, and HP-UX). This file lists component entries as "port name = port value". For example: Oracle Java Object Cache port = 7000 Oracle Intelligent Agent = 1748, 1754, 1808, 1809 Table 32 lists the default port numbers for each component, and the port number range that the installer uses if it detects a conflict:
Table 32 Port Numbers Default Port Number

Components OC4J for Oracle Forms and Oracle Reports testing
Port Number Range 8888-8907 23910-23929 9240-9259 8888-8907
HTTP Listener: 8888 RMI: 23910 JMS: 9240 HTTP Listener: 8888
OC4J for JDeveloper testing
Installation
3-9
If you choose an installation type that installs both OC4J instances, then the installer sets port numbers that do not conflict with each other or with other port numbers.
3.2.1.5 OC4J Instance for Oracle Developer Suite
To start and stop Oracle Developer Suite OC4J instances for Oracle Forms and Oracle Reports testing, do the following:
Linux, Solaris, and HP-UX: use the scripts located in the oracle_ home/j2ee/DevSuite directory: startinst.sh stopinst.sh
Windows: use the scripts located in the oracle_home\j2ee\DevSuite directory: startinst.bat stopinst.bat
or use the Start Menu to access the scripts, using one of the following: Start > Programs > Oracle Developer Suite - oracle_home > Forms Developer Start > Programs > Oracle Developer Suite - oracle_home> Reports Developer and then choosing Start OC4J Instance to start an OC4J instance Shutdown OC4J Instance to stop an OC4J instance
3.2.1.6 Assistive Technologies (Windows only)

If you use assistive technologies such as screen readers to work with Java-based applications and applets, the Windows-based computer where you have installed Oracle Developer Suite must have Sun's Java Access Bridge installed in all the Java virtual machine locations on the computer. The installer installs files for JDK/JRE 1.4.1 and JDK/JRE 1.1.18 on your computer, but only installs Java Access Bridge 1.0.3 files in the JDK/JRE 1.4.1 location. For assistive technologies to work with Oracle Developer Suite components that have JDK/JRE 1.1.8 dependencies, you must install the production version of Java Access Bridge 1.0.2 in the JDK/JRE 1.1.8 location as well. See Section 2.8.4, "Installing Java Access Bridge (Windows only)" for instructions. Then use the steps below to make sure the Java Access Bridge files are set up properly. To verify that Java Access Bridge files are installed: These instructions assume that you have downloaded the Java Access Bridge 1.0.2 zip file, extracted the contents of the zip file into a temporary directory named accessbridge_home, and installed Java Access Bridge 1.0.2. (See Section 2.8.4, "Installing Java Access Bridge (Windows only)" for more information.)
1. 2.
Ensure that the .jar files access-bridge.jar and jaccess.jar are added to the folder Program Files\Oracle\jre\1.1.8\lib. Ensure that two .DLL files, JavaAccessBridge.dll and WindowsAccessBridge.dll, are added to the folder Winnt\System32. This ensures that the files are in the system path.
3-10
Installation Guide
3.
Ensure that the .jar files, access-bridge.jar and jaccess-1_3.jar, are added to the folder oracle_home\jdk\jre\lib\ext. If necessary, copy them from accessbridge_home\installer\installerFiles. Ensure that two .DLL files, JavaAccessBridge.dll and WindowsAccessBridge.dll, are added to the folder oracle_ home\jdk\jre\lib\ext. If necessary, copy them from accessbridge_home\installer\installerFiles. Ensure that the PATH environment variable has been updated to include the directory where the .DLL files are installed, oracle_home\jdk\jre\lib\ ext. Ensure that the ORACLE_OEM_CLASSPATH environment variable has been updated to include the directory where the Access Bridge files are installed for JRE 1.1.8:
ORACLE_OEM_CLASSPATH=program_drive:\Program Files\Oracle\jre\1.1.8\lib\ access-bridge.jar;program_drive:\Program Files\Oracle\jre\1.1.8\lib\ jaccess.jar
4.
5.
6.
where program_drive is the drive that contains the directory Program Files.
7.
Ensure that the file accessibility.properties is in the folders oracle_ home\jdk\jre\lib and Program Files\Oracle\jre\1.3.1\lib. If necessary, copy the file from accessbridge_home\installer\installerFiles.
8.
Ensure that the file accessibility.properties includes the following line:

assistive_technologies=com.sun.java.accessibility.AccessBridge
3.2.2 Completing Component-specific Postinstallation Tasks

Review the component-specific postinstallation checklist and perform any required tasks.
3.2.2.1 Oracle9i JDeveloper

To effectively use JDeveloper, follow the instructions in this section. For information about supported deployment environments, see Section B.1, "Oracle9i JDeveloper". 3.2.2.1.1 Migrating User Settings from Previous Releases
You can migrate user settings from the production release of JDeveloper (9.0.2) to JDeveloper (9.0.4). To learn how to do this, see Section A.2.1, "Migrating JDeveloper User Settings from Release 9.0.2 to Release 9.0.4". Oracle does not support direct migration from Oracle JDeveloper version 3.2.3 to 9.0.4. 3.2.2.1.2 Enabling JDeveloper Extensions
Before you can use an extension in JDeveloper, you first need to download it from OTN. The following extensions are available:

JUnit WebDAV iSQL*Plus
Installation 3-11
To automatically download and install an extension:

1. 2. 3.
Start JDeveloper. From the main menu, select Help > Check for Updates... This menu option lists extensions that you don't have and newer versions of ones you have. Select and install the extensions you want.
To manually download an extension:

1. 2. 3.
Go to the OTN page for JDeveloper (9.0.4) extensions, http://otn.oracle.com/software/products/jdev/content.html. Select an extension. Follow the instructions to download the zip file.
To manually install an extension:

1. 2. 3. 4.
Shutdown any instances of JDeveloper that are currently running on your computer. Verify if there are additional installation instructions in the extension archive. Unzip the downloaded zip file into the directory oracle_home\jdev\lib\ext. Restart JDeveloper. After you restart, you will be able to use the extension.
For more information about JDeveloper extensions, see the JDeveloper online help. 3.2.2.1.3 Enabling Source Code Control (Windows only)
A connection to an Oracle Software Configuration Manager (Oracle SCM) repository is required to perform source code control using Oracle SCM from JDeveloper. The repository resides within an Oracle database and must be precreated. Install the Rapid Application Development or Complete option, then use the Repository Administration Utility in Oracle SCM to create the repository in the database. For instructions on creating the repository, see the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client. 3.2.2.1.4 Font Problems on Linux, Solaris, and HP-UX Computers
If you see an error similar to: Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific] when starting JDeveloper on a Linux, Solaris, and HP-UX computer, your JDK isn't set up to use the listed font. JDeveloper, by default, uses the information in the file font.properties included with each JDK. If this file refers to fonts that are not available on your computer, you will see the error or one like it. To fix this, you either need to install a new font, or change your font.properties file. For information on installing new fonts on your computer, contact your vendor. For information on updating the font.properties file, see your JDK vendor's documentation or Sun's Font Overview documentation at http://java.sun.com/j2se/1.3/docs/guide/intl/addingfonts.html
3-12
Installation Guide
3.2.2.1.5
Hosting Documentation
If you have set the IDE option to use hosted documentation, JDeveloper is pre-configured to use documentation hosted on OTN. The URL to the documentation set on OTN is http://otn.oracle.com/hosted_doc/jdev/jdeveloper/jdeveloper.hs Please note that when you start the hosted help system for the first time, it may take several minutes to initialize. In addition to this site, you can set up your own host for serving hosted documentation. You may want to do this if you are behind a firewall, or you find network access times slow, or if you want to add information to the JDeveloper documentation. If you want to extend the JDeveloper documentation, refer to the Oracle Help for Java (OHJ) documentation, which is included with JDeveloper. To host JDeveloper documentation:
Uncompress the jar files located in oracle_home/jdev/doc/ohj onto your web server. If you have the base install, you will have to download the documentation from OTN. Each jar should be uncompressed into its own directory. Modify the file jdeveloper.hs file to point to the correct URL for each of the subhelpsets on your server. Look at the file jdeveloper-hosted-example.xml in oracle_home/jdev/doc/ohj/ jdeveloper.jar for an example of how to configure this file.
Once you have done that, your users will have to set their copy of JDeveloper to use your new server. To do this:
1. 2. 3. 4.
From the JDeveloper main menu, select Tools > Preferences. Navigate to Documentation. Select the Use Hosted Documentation radio button. Provide the URL to the jdeveloper.hs file on your server. This URL should include the port number, even if you are using the default port (80). Using JDeveloper in a Terminal Server/Multiuser Environment
3.2.2.1.6
You can install JDeveloper in Microsoft Terminal Server or Citrix WinFrame environment, allowing many clients to access one installation of JDeveloper. In all cases, users can save their projects locally. When you install and configure JDeveloper for a multiuser environment, you need to consider usage and resources, such as number of users and power of the server, so that you can provide the best performance. Installing JDeveloper on a Citrix WinFrame Server or a Microsoft Terminal Server You need to have administrative privileges to install JDeveloper.
To install JDeveloper on a Citrix or Microsoft Server: Install JDeveloper by selecting the J2EE Development installation type as described earlier. Define the user home directory environment variable (see below).
Configuring User Home Directories in a Multiuser Environment (The following information is written for Windows, but the logic applies to Linux, Solaris, and HP-UX as well.)
Installation 3-13
Before you start JDeveloper in a terminal server environment, you must define the user home environment variable, and set its value for each user, so that JDeveloper can correctly identify individual user home directories. If the variable is not defined and set, JDeveloper uses the oracle_home\jdev as the home directory for all users. Using this directory for all users may cause unstable behavior in JDeveloper.
To define the name of the user home environment variable:

1.
Open the file oracle_home\jdev\bin\jdev.conf in a text editor. Use an editor that recognizes Linux, Solaris, and HP-UX end-of-line characters, such as WordPad. Find the entry: SetUserHomeVariable JDEV_USER_DIR This is the default variable that JDeveloper will look for at startup. As the terminal server's administrator, you may change the name of this variable to follow your computer's naming conventions.
2.
3.
Save the file. If you are using WordPad, it will warn you that it is about to save the file in text-only format. You can ignore this warning.
To set the environment variable:

Note: Every user of JDeveloper on a multiuser computer must
follow this procedure.

1. 2. 3. 4. 5.
From the Windows Start menu, choose Control Panel, then System. Select the Environment tab. Add JDEV_USER_DIR, or the name you chose in the previous procedure, as a user-level environment variable. Set its value to your home directory (e.g., N:\users\jdoe) and click OK. To check your variable setting, open a command shell and enter set You should see output similar to the following: JDEV_USER_DIR=N:\users\jdoe
6.
Launch JDeveloper. JDeveloper will ask if you would like your user home directory to be created. Select Yes.
7.
From the Help menu, choose About to verify that the value of ide.user.dir is set to your user home directory.
Configuring Terminal Server Clients for Running JDeveloper These topics assume that you have already installed a Citrix WinFrame or Microsoft Terminal Server client locally and that JDeveloper has been installed and configured by the System Administrator.
To configure a terminal server client for JDeveloper:

1. 2.
Verify that the color resolution of the terminal server client has been set to a minimum of 256 colors. This minimum resolution is required by the JDK. Log on to your terminal server.
3-14
Installation Guide
3.
Verify that the user home environment variable has been defined: Ask your System Administrator for the naming convention that is used on your computer. The default variable is JDEV_USER_DIR. Set the user home environment variable: From the Windows Start menu, choose Control Panel, then System. Click the Environment tab. Add the variable to your User Variables and click OK. For example, you can define JDEV_USER_DIR as the variable containing the path to the user's home directory. To check the correct variable settings, open a command shell and enter: set You should see output similar to the following: JDEV_USER_DIR=n:\users\jdoe
4.
5. 6. 7.
Launch JDeveloper. JDeveloper will ask if you would like your user home directory to be created. Select Yes. From the Help menu, choose About to verify that the value of ide.user.dir is set to your user home directory.
If you run JDeveloper in a multiuser environment and you see the error The system DLL ole32.dll was relocated in memory. The application will not run properly. The relocation occurred because the DLL Dynamically Allocated Memory occupied an address range reserved for Windows NT system DLLs. The vendor supplying the DLL should be contacted for a new DLL. you need to update the oracle_home\jdev\bin\jdev.conf file by adding the line: AddVMOption -Xheapbase10000000 Use an editor, such as WordPad, that recognizes Linux, Solaris, and HP-UX end-of-line characters. You may have to change the number if you still get the error when starting JDeveloper. When you save the file, WordPad will warn you that it is about to save the file in text-only format. Disregard this warning. You also need to set option with the same value in the project settings. To do this, from the Project menu, choose Default Project Settings, expand the Runner node, select Java options, and change the option. To make this setting available to all users, exit JDeveloper, log on as an administrator and then copy the file oracle_home\jdev\multi\system\DefaultWorkspace\Project1.jpr to userhome\system\DefaultWorkspace\Project1.jpr
Installation 3-15
3.2.2.1.7
Using OC4J in non-embedded mode with JDeveloper
The J2EE Development installation includes a fully functioning version of Oracle Application Server Containers for J2EE (OC4J). If you use JDeveloper to test your applications, you are using the embedded version of OC4J, and you do not have to make any modifications to your configuration. If you would like to use the same configuration for your server, you can use the version included with JDeveloper. To configure the OC4J server for non-embedded mode:
1.
At the command line, in oracle_home/j2ee/home run the command java -jar oc4j.jar -install The server will auto-unpack several jars. You will then be prompted to enter an admin password.
2.
Enter a password and press Enter. Confirm the password by typing it again and press Enter. Write down the password. You need this password to administer and stop the OC4J server.
The OC4J server is now installed and configured. You can now start the server.
Note: The administrative username is now admin, and the administrative password is the password you just entered. Use this username and password to administer and stop the server.
To start the OC4J server for use in non-embedded mode:
For Windows: In the directory oracle_home/j2ee/home, run the command: java -jar oc4j.jar admin password where password is the administrative password you created previously. Several jar files are auto-deployed and the server displays the following line:
Oracle Application Server Containers for J2EE 10g (9.0.4.0.0) initialized
For Linux, Solaris, and HP-UX: Navigate to the directory oracle_ home/jdev/bin:
To start the server, run start_oc4j: oracle_home/jdev/bin/start_oc4j
To stop the server, run tstop_oc4j: oracle_home/jdev/bin/stop_oc4j admin password
For password, use the administrative password you created previously. For more information on fine tuning the OC4J server, see the OC4J documentation in the Oracle Developer Suite Documentation Library.
Note: The server must be running when you deploy projects to it.
Using the included server will have no impact on using JDeveloper for testing and running your projects.
3-16
Installation Guide
3.2.2.1.8
Using Assistive Technologies with JDeveloper (Windows only)
First, follow the steps in Section 3.2.1.6, "Assistive Technologies (Windows only)" to make sure the Java Access Bridge files have been installed properly. Then use the following instructions to make sure JDeveloper works with Java Access Bridge:
1.
Ensure that three DLL files: JavaAccessBridge.dll, JAWTAccessBridge.dll, and WindowsAccessBridge.dll are added to the Winnt\System32 directory, as they must be in the system path in order to work with JDeveloper. If necessary, copy them from accessbridge_ home\installer\installerFiles to the directory. Modify the file jdev.conf located in the folder oracle_home\jdev\bin to uncomment the AddVMOption line as shown in the following example:
# # Prepend patches to the bootclasspath. Currently, rtpatch.jar contains a # patch that fixes the javax.swing.JTree accessibility problems. # Uncomment the line below if you need to run JDeveloper under JAWS. # AddVMOption -Xbootclasspath/p:../../jdk/jre/lib/patches/rtpatch.jar
2.
3.
It is also necessary to use Hotspot instead of OJVM to run JDeveloper. To do this, set the SetJavaVM line in the jdev.conf file as follows: SetJavaVM hotspot
4. 5.
Start your screen reader. Start JDeveloper.
The previous steps assume you are running Windows and using a Windows-based screen reader. A console window that contains error information (if any) will open first and then the main JDeveloper window will appear, once JDeveloper has started.
3.2.2.2 Oracle Business Intelligence Beans

Complete the following postinstallation tasks that are appropriate for your site. 3.2.2.2.1
Database Considerations
Oracle9i Release 2 is required for Oracle BI Beans release 9.0.4. If you have an existing BI Beans application that connects to Oracle9i Release 1 (9.0.1.x), then you must upgrade the database to Release 2 in order to use BI Beans release 9.0.4. However, the BI Beans Catalog supports either Oracle9i Release 1 (9.0.1.x) or Release 2 (9.2.0.x). Before you can connect to data in JDeveloper, the Oracle9i Release 2 database must have been installed and configured. There are three basic installation scenarios:
You are a developer, installing the database on your computer, for your personal use. You must prepare the database as described in Section 3.2.2.2.2, "Preparing an Oracle9i Release 2 Database for Use with BI Beans" and perform the additional tasks required by your site as described in Section 3.2.2.2.3, "Additional Tasks". You are a developer and are using a database that was installed and configured by your DBA. You should complete the final step of the preparation process as described in step 5 of Section 3.2.2.2.2, "Preparing an Oracle9i Release 2 Database for Use with BI Beans", to update or create new application settings in JDeveloper. Then perform the additional tasks required by your site as described in Section 3.2.2.2.3, "Additional Tasks".
Installation 3-17
You are the DBA and are installing and configuring the database for use by others. You should prepare the database as described in Section 3.2.2.2.2, "Preparing an Oracle9i Release 2 Database for Use with BI Beans". Do not perform the final step of the process.
Note that the preparation steps in JDeveloper affect the entire JDeveloper environment, including the embedded OC4J instance. 3.2.2.2.2 Preparing an Oracle9i Release 2 Database for Use with BI Beans
To run against Oracle9i Release 2, complete the following tasks:

1.
If you have not already done so, install the Enterprise Edition of the Oracle9i database, Release 2. For instructions, download the Oracle9i installation guide for the appropriate platform from Oracle Technology Network (http://otn.oracle.com). Important: When you install the database client, do not install it into the Oracle Application Server home or the Oracle Developer Suite home.
2.
If you have not already done so, on the same server download and install the appropriate Oracle9i patch sets from OracleMetaLink (http://metalink.oracle.com). To locate the patch sets to download, log onto OracleMetaLink and click Patches, then search for the appropriate patch set numbers, as described below. BI Beans supports some, but not all, of the database patch sets. Each new patch set includes improvements to OLAP functionality. Therefore, if possible, you should install the latest patch set. For the current matrix of supported patch sets, refer to the BI Beans product area on Oracle Technology Network (http://otn.oracle.com/products/bib/content.html). As of this writing, the following patch sets are supported. Choose the appropriate platform, then download and install the patch set.

2761332 -- the Oracle9i 9.2.0.3 patch set 3095277 and 3084634 -- the Oracle9i 9.2.0.4 patch set and an additional patch set required for OLAP (you must install both)
3.
Configure the database, following the configuration settings shown in Best Practices for Tabular Cube Aggregation and Query Operations. To access this document, download patch set 2529822. You must follow these configuration settings exactly to ensure that BI Beans works correctly and performs well. This document is updated as needed, so you should download a new version whenever you download a new patch set. Define the appropriate OLAP metadata, as described in the Oracle9i OLAP Release 2 - User's Guide. This book is available on Oracle Technology Network (http://otn.oracle.com/products/bi/9iolap.html). You can also refer to the Help system for the OLAP management tool of Oracle Enterprise Manager, which is the tool that you use to create the metadata. If you do not define appropriate metadata, then you will not be able to create OLAP queries. For any existing BI Designers, you must either update the application settings to specify the new OLAP data source (as described in the Help topic "Updating BI Beans Application Settings") or create a new BI Designer (as described in the Help topic "Creating a BI Designer Object").
4.
5.
3-18
Installation Guide
3.2.2.2.3
Additional Tasks
In addition to preparing the database, perform the following tasks, as appropriate for your site:
To upgrade an existing application that runs against Oracle9i Release 1, first complete the installation process for Release 2 as described in Section 3.2.2.2.2, "Preparing an Oracle9i Release 2 Database for Use with BI Beans", then complete the migration steps, as described in Section A.3, "Oracle Business Intelligence Beans". By default, JDeveloper expects the JDK to be in the ..\..\jdk directory (Windows) or in the /usr/java/jdk1.4 directory (Linux, Solaris, and HP-UX). If your JDK is not in the default location, then you must edit oracle_ home/jdev/bin/jdev.conf to change the setting of the SetJavaHome option. Oracle Developer Suite ships with the Oracle9i Release 1 JDBC drivers, but Oracle BI Beans requires the Release 2 drivers. Therefore, you must upgrade the JDBC driver files. This is necessary even if you upgraded to the Release 2 drivers in Oracle BI Beans 9.0.3. To upgrade, follow these steps:
1. 2. 3.
Start JDeveloper. Attempt to access any BI Beans object. A message appears, asking if you want to upgrade. Click Yes. The upgrade is performed automatically. The files are copied from the oracle_home/bibeans/jdbc/lib_92 directory to the oracle_ home/jdev/lib/patches directory. Restart JDeveloper for the upgrade to take effect. Notes: This change affects all your projects. However, you must also change the settings for each project, as described in Section A.3, "Oracle Business Intelligence Beans". If you want to restore the original drivers, simply delete classes12.jar, classes12dms.jar, and nls_charset12.jar from the oracle_ home/jdev/lib/patches directory.
4.
During design with JDeveloper, your analyses are saved in your project. However, if you or your end-users want to be able to share analyses and objects with other developers and end-users, then you must install and configure the BI Beans Catalog, as described in the Help topic "Installing and Configuring the BI Beans Catalog." To test your applications, you must install your chosen deployment environment. For more information, see Section B.1.3, "Oracle Business Intelligence Beans", under "Deployment Requirements". BI Beans Catalog: If you plan to use the Oracle JDBC Thick (OCI) driver to connect to the BI Beans Catalog at design time, then you must edit the jdev.conf file, as described in the JDeveloper Help topic "Reference: Connection Requirements for Oracle's Type 2 JDBC Drivers (OCI)." The jdev.conf file is in the oracle_home/jdev/bin directory. You must also ensure that the version of the Release 2 client files matches that of the JDBC driver file. That is, when you follow the instructions in the Help topic, you must reference an Oracle home that contains the Release 2 client files. For information about how to upgrade manually, consult the release notes.
Installation 3-19
3.2.2.3 Oracle Reports Developer
To enable Oracle Application Server Portal integration, see Oracle Application Server Reports Services Publishing Reports to the Web in the Oracle Developer Suite Documentation Library. If you plan to create reports of multidimensional data from Oracle Express Server, review the instructions for configuring the Express data source in the Oracle Reports Builder online help. Search for the topic "Configuring the Express Data Source." Oracle Reports Developer release notes also contain important information about preparing connections to the Oracle Express Server.
Note: Note: The Oracle Reports connection to Oracle Express
Server is not supported on HP-UX and Linux.
To start and stop Reports Services, see Oracle Application Server Reports Services Publishing Reports to the Web in the Oracle Developer Suite Documentation Library. You can change the outgoing e-mail server in the Reports Server configuration file, reports_server_name.conf, located in the oracle_home\reports\ conf directory (Windows) or oracle_home/reports/conf directory (Linux, Solaris, and HP-UX). Any reports that use the Merant JDBC drivers supplied with Oracle Application Server must be deployed with Oracle Application Server only. If you wish to deploy reports with JDBC queries against another application server, you must license the Merant drivers or use other JDBC drivers for development and deployment. To use the Merant JDBC drivers supplied with Oracle Application Server, install the J2EE and Web Cache install option of Oracle Application Server into the Oracle home where you installed Oracle Developer Suite. Then modify the oracle_ home\reports\conf\jdbcpds.conf file (Windows) or oracle_ home/reports/conf/jdbcpds.conf file (Linux, Solaris, and HP-UX) to specify the driver information of the Merant JDBC drivers. The driver information is typically the driver name, connect string format, and the driver class. For example, an entry for the Merant driver for Sybase would look like:
<driver name = "sybase-merant" sourceDatabase = "sybase" subProtocol = "merant:sybase" connectString = "jdbc:subProtocol://databaseName" class ="com.merant.datadirect.jdbc.sybase.SybaseDriver"> </driver>
where: name is any unique name by which you want to refer to a specific JDBC driver you use in Oracle Reports Developer. sourceDatabase is the name of the database you want to access. subProtocol is a driver-specific name that you can find in the driver documentation. For example, for the Merant driver to the Sybase database, subProtocol is merant:sybase and for sql-server database it is sqlserver. connectString is the format of the connect string of the driver.
3-20
Installation Guide
In the example, jdbc:subProtocol://databaseName specifies the format. class is the main Java class file name of the driver. This value is specific to each driver; you can find it in the driver documentation. For example, the driver class name for the Merant driver to the Sybase database is com.merant.datadirect.jdbc.sybase.SybaseDriver and, for sql-server database, it is com.merant.datadirect.jdbc.sqlserver.SQLServerDriver. For more information, see the chapter "Configuring and using JDBC PDS " of the Oracle Application Server Reports Services Publishing Reports to the Web manual in the Oracle Developer Suite Documentation Library. More guidelines on configuring the custom drivers are given in the oracle_home\reports\conf\jdbcpds.conf file (Windows) or oracle_home/reports/conf/jdbcpds.conf file (Linux, Solaris, and HP-UX). You can also refer to the section "JDBC PDS" in the Oracle Reports Developer online help. For Windows only: If you installed the Business Intelligence option, and you want to perform source code control with Oracle Software Configuration Manager from Oracle Reports Developer, install either the Rapid Application Development or Complete option.
3.2.2.4 Oracle Discoverer Administrator
If you have an earlier version of Discoverer Administrator (formerly Discoverer Administration Edition) on your computer, you need to upgrade the End User Layer before you can use Oracle Discoverer Administrator to perform administration tasks (unless you have version 9.0.2.53 or later, in which case no EUL upgrade is required). See Chapter 23 "Upgrading from earlier versions of Discoverer" of the Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite Documentation Library.
3.2.2.5 Oracle Forms Developer
Before you can work with Stored Java objects in Oracle Forms Developer 10g version 9.0.4 (Oracle Forms), you must install the necessary Java classes and PL/SQL package to the Oracle9i database. Follow these steps to install the Java Object support in Oracle Forms Developer:
1.
Locate the installation scripts in the oracle_home\dbs directory (Windows) or oracle_home>/dbs directory (Linux, Solaris, and HP-UX). You will need the following files to install Java Object support: dejavins.sql dejavaux.sql derefls.plb dereflb.plb dedbjava.jar
2. 3.
Run SQL*Plus from the same directory where the scripts are located. Log in as SYSTEM.
If the installation is correct, then you will see the ORA_DE_REFLECTION package (derefls.plb and dereflb.plb) under the schema SYSTEM.
Installation 3-21
See Oracle Application Server Forms Services: Deployment Guide in the Oracle Developer Suite Documentation Library for information about deploying Oracle Forms Developer applications to the Web using Oracle Application Server. See Oracle Forms Developer and Forms Services: Migrating Forms Applications from Forms6i in the Oracle Developer Suite Documentation Library for information that developers, system administrators, and DBAs need to know in order to migrate Oracle Forms Developer applications from Forms6i to Oracle Forms Developer 10g. See the Oracle Forms Developer online help for the steps you need to take to configure source control management and the debugger, if you plan to use these features. For online help updates (JAR file downloads), go to Oracle Technology Network at http://otn.oracle.com.
To configure a database for TranslationHub, use the Schema Manager. For information on using the Schema Manager, see the TranslationHub online help.
3.2.2.6 Oracle Software Configuration Manager (Oracle SCM)
Follow the instructions for installing, upgrading, or migrating a repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client. Also see Section A.7, "Oracle Software Configuration Manager". Upgrade your client before you upgrade or install your server side repository. You will avoid having to upgrade the repository twice. To upgrade, go to OracleMetaLink (http://metalink.oracle.com), navigate to product "Designer" release "Designer/Repository 9i", download the latest 9.0.4 patchset, and install it to your Oracle home. If you want to use non-English data, you need to set up Oracle Software Configuration Manager with a non-English character set. See the Oracle Application Server 10g Globalization Guide in the Oracle Application Server Documentation Library) for instructions.
3.2.2.7 Oracle Designer
You must install JInitiator on your client to run an Oracle Forms form generated with Oracle Designer. To install JInitiator, navigate to the directory oracle_ home\jinit, then run the program jinit.exe. The Oracle Designer release notes describe additional steps that you need to take in order to run generated Oracle Forms forms. Upgrade your client before you upgrade or install your server side repository. You will avoid having to upgrade the repository twice. To upgrade, go to OracleMetaLink (http://metalink.oracle.com), navigate to product "Designer" release "Designer/Repository 9i", download the latest 9.0.4 patchset, and install it to your Oracle home. Follow the instructions for installing a new repository, or upgrading or migrating an existing one, in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the Oracle SCM client. For upgrading or migrating an existing repository, see also Section A.8, "Oracle Designer".
3-22
Installation Guide
3.2.3 Starting a Component

Before you start an Oracle Developer Suite component, make sure you have completed the general and component-specific postinstallation steps described in previous sections. Also, if you are upgrading from a previous version of a component, make sure you perform the necessary upgrade steps. Each components upgrade procedure is documented in Appendix A, "Upgrade Notes". Once you have completed a components postinstallation and upgrade steps you can start the component, as follows:
3.2.3.1 Oracle9i JDeveloper and Oracle Business Intelligence Beans

Windows: To start JDeveloper, run the program oracle_ home\jdev\bin\jdevw.exe. To see a console window that displays diagnostic information, run the program oracle_home\jdev\bin\jdev.exe. Linux, Solaris, and HP-UX: To start JDeveloper, run the program oracle_ home/jdev/bin/jdev. Oracle Business Intelligence Beans is available as part of JDeveloper.
3.2.3.2 Oracle Reports Developer

Windows: To start Reports Builder, from the Taskbar choose Start > Programs > Oracle Developer Suite - oracle_home > Oracle Reports Developer > Reports Builder. Linux, Solaris, and HP-UX: To start Oracle Reports Developer, navigate to the oracle_home/bin directory, then run rwbuilder.sh.
3.2.3.3 Oracle Discoverer

Oracle Developer Suite contains two Oracle Discoverer components, Oracle Discoverer Administrator, and Oracle Discoverer Desktop. 3.2.3.3.1 Oracle Discoverer Administrator
Windows Only: To start Oracle Discoverer Administrator, follow these steps:

1.
From the Taskbar, choose Start > Programs > Oracle Developer Suite - oracle_home > Discoverer Administrator to display the Connect to Oracle Discoverer Administrator dialog.
2. 3. 4.
Enter the username of the database user with which you want to start Discoverer Administrator in the Username field Enter the password of the database user with which you want to start Discoverer in the Password field. Specify the database to connect to in the Connect field, using the following guidelines:
If you are logging onto your default Oracle database, do not enter anything in the Connect field. If you are logging onto a different Oracle database, specify the name of the database (if you not sure which name to use, contact your database administrator.)
5.
Click the Connect button to start Discoverer Administrator and connect to the database.
Installation 3-23
3.2.3.3.2
Oracle Discoverer Desktop
Windows Only: To start Oracle Discoverer Desktop, follow these steps: Note: Before you can create a new workbook or open an existing workbook in Oracle Discoverer Desktop, an End User Layer must already exist (i.e. created using Oracle Discoverer Administrator)
1.
From the Taskbar, choose Start > Programs > Oracle Developer Suite - oracle_ home > Discoverer Desktop to display the Connect to Oracle Discoverer Desktop dialog. Enter the username of the database user with which you want to start Discoverer Desktop in the Username field Enter the password of the database user with which you want to start Discoverer in the Password field. Specify the database to connect to in the Connect field, using the following guidelines:
2. 3. 4.
if you are logging onto your default Oracle database, do not enter anything in the Connect field if you are logging onto a different Oracle database, specify the name of the database (if you not sure which name to use, contact your database administrator)
5.
Click the Connect button to start Discoverer Desktop and connect to the database.
3.2.3.4 Oracle Forms Developer

Windows: To start Forms Builder, choose Start > Programs > Oracle Developer Suite oracle_home > Oracle Forms Developer > Forms Builder. Linux, Solaris, and HP-UX: To start Oracle Forms Builder, navigate to your oracle_ home/bin directory, then run f90desm.sh.
3.2.3.5 Oracle Software Configuration Manager (Oracle SCM)

Windows Only: To start Oracle Software Configuration Manager, from the Taskbar choose Start > Programs > Oracle Developer Suite - oracle_home > Software Configuration Manager. Then select one of the menu options, which are described in the following table:
Option Accessible Help Command Line Tool Reference Guide Configuration Management Overview Online Help Oracle SCM Repository Installation Guide Release Notes Repository Administration Utility Description Opens the SCM online help system in Oracle Help for Java format for accessibility Accesses documentation for the Command Line Tool Opens a software configuration management overview document Accesses the online help for SCM Opens the installation guide for the SCM server-side repository Accesses the SCM release notes Starts the tool used for repository installation, migration, and upgrade
3-24
Installation Guide
Option Repository Command Line Tool
Description Starts the tool that provides a command-line interface to the repository
Repository Object Navigator Starts the tool used for repository maintenance Use as Source Control for Forms and Reports Refer to the SCM documentation for instructions about using this option.
3.2.3.6 Oracle Designer

Windows Only: To start Oracle Designer, choose Start > Programs > Oracle Developer Suite - oracle_home > Designer > Oracle Designer.
3.2.4 Additional Documentation

All components have online help that is installed with the product. Some components provide additional documentation that is available on the Oracle Developer Suite Documentation Library CD-ROM or, for the DVD, from the subdirectory /doc_ library. For information on viewing and installing the Oracle Developer Suite Documentation Library, see Appendix C, "Installing the Documentation Library". For release notes and further component-specific information on postinstallation and configuration tasks, refer to the release notes and the component-specific administration or configuration guide in the documentation library. For Windows users, you can access release notes and Getting Started information from the Start Menu as follows:

Start > Programs > Oracle Developer Suite - oracle_home > Release Notes Start > Programs > Oracle Developer Suite - oracle_home > Documentation > Getting Started
You can also point your browser to the file oracle_home/doc/welcome/index.htm. For documentation updates, white papers, or other collateral, please visit the Oracle Technology Network at http://otn.oracle.com.
Installation 3-25
3-26
Installation Guide
4
This chapter guides you through the deinstallation and reinstallation processes for Oracle Developer Suite. They are described in the following topics:

Deinstallation Reinstallation
4.1 Deinstallation
The following section guides you through the deinstallation process.
4.1.1 Deinstalling Using the Installer

1.
For Windows, terminate all Oracle services before starting the deinstallation process. For Linux, Solaris, and HP-UX, you should kill all Oracle processes before starting the deinstallation process. Start the installer. See Section 2.9.4, "Starting the Installer", if you need instructions.
Note: The installer displays all Oracle products and components
2.
installed in all Oracle homes on this computer. You can deinstall as many products as you wish. These instructions only cover the deinstallation of Oracle Developer Suite. You cannot deinstall individual components of Oracle Developer Suite. If you select one component of Oracle Developer Suite and attempt to deinstall it, the installer will remove all of Oracle Developer Suite. Once the installer starts, it displays the Welcome screen. Click Deinstall Products. The Welcome screen provides you with two ways to deinstall products:

Deinstall Products: Click this to deinstall individual products. Installed Products: Click this to view currently installed products and deinstall products.
3.
Review the list of installed products in the Inventory screen, then select Oracle Developer Suite 10g 9.0.4.0.0. The Inventory screen appears when you click Deinstall Products on the Welcome screen, or Installed Products on any screen.
4-1
Deinstallation
Note: The "+" sign before a name indicates that there are more
components and files installed within that particular name. Click the "+" sign to view dependent components and files. The inventory screen consists of one or two tabbed panes. The Contents pane always appears. It displays the Oracle products currently installed on the computer and offers the following buttons and product information:
Location: Click this to display the full location path of the selected product or component. Show Empty Homes: Click this to toggle the display of installed products. If this checkbox is set, the display includes directory information for Oracle homes that do not currently have a product installed in them. Remove: Click this to deinstall all checked products from the Oracle home. A Confirmation screen appears. Help: Click this to access detailed information about the functionality of the Inventory screen. Save As: Click this to save the inventory list as text. A file browser dialog appears when you click Save As. Enter a file name, click Save, and the inventory list will be written to this file as text. Close: Click this to quit the Inventory screen.
The Environment pane appears on Windows platforms. It displays the path and environment variables currently set for all Oracle homes installed on this computer. It offers the following buttons and product information:
Central Inventory Location: This is directory that contains information about all the Oracle homes installed on this computer. Oracle homes list: This is a list of the Oracle homes installed on this computer. The name and directory path are listed for each Oracle home. Path: This is the current value of the Windows PATH environment variable. Apply: Click this to add Oracle home directories to the PATH environment variable. To use this, select one or more Oracle homes in the list, then click Apply to add them to the PATH variable. You can change the order in which Oracle home directories are listed in the PATH variable by using the up and down arrows at the right side of the Oracle homes list. Help: Click this to access detailed information about the functionality of the Inventory screen. Save As: Click this to save the directory information as text. A file browser dialog appears when you click Save As. Enter a file name. The complete list of Oracle homes and the value of the PATH variable will be logged into this file as text. Close: Click this to quit the Inventory screen.
4.
Write down the full location path of Oracle Developer Suite that is displayed in the Location box. You will need this information when you manually delete files and folders after the installer has completed. When you are ready to proceed, click Remove... .
5. 4-2 Installation Guide
Reinstallation
6.
At the Confirmation screen, verify your choice and click Yes. The Confirmation screen appears when you click Remove on the Inventory screen. The Confirmation screen lists all the products selected for deinstallation. Scroll down the screen to verify the list. The following buttons appear on the Confirmation screen:

Help: Click this to get help for the Confirmation screen. Yes: Click this to start deinstalling the list of selected products. No: Click this to return to the Inventory screen. The list of selected products is not removed from the Oracle home.
Click Yes to start the deinstallation.

7.
Monitor the deinstallation process. The Remove Progress Bar screen appears when you click Yes on the Confirmation screen. The installer detects and removes all the components of Oracle Developer Suite. The following button appears on the Remove Progress Bar screen:
Cancel: Click this to discontinue the deinstallation process. A message dialog appears, prompting you to confirm that you want to stop the deinstallation process. Click Yes to stop the deinstallation process; click No to continue deinstalling.
8. 9.
At the end of deinstallation, the Inventory screen appears again. Click Close to exit this screen and return to the Welcome screen. At the Welcome screen, click Cancel to exit the installer, then click Yes to confirm that you wish to exit. location you noted in the previous step, and delete the files and folders.
10. You must manually delete any remaining files and folders. Navigate to the 11. For Windows only: Reboot the computer.
You have successfully deinstalled Oracle Developer Suite.
4.2 Reinstallation
The installer lets you upgrade an existing installation of Oracle Developer Suite with additional components. To do this, start the installer again and select the install type that contains the components you want. The installer will not overwrite existing component installations. To completely reinstall Oracle Developer Suite by overwriting an existing installation, deinstall and then reinstall the product.
See Also: Section 4.1, "Deinstallation".
4-3
Reinstallation
4-4
Installation Guide
A
Upgrade Notes
This appendix provides basic information about migrating or upgrading from a previous version of Oracle Developer Suite. The following topics are included: Oracle Developer Suite Oracle Business Intelligence Beans Oracle9i JDeveloper Oracle Reports Developer Oracle Discoverer Administrator Oracle Forms Developer Oracle Software Configuration Manager Oracle Designer Additional Documentation
A.1 Oracle Developer Suite

The previous versions of Oracle Developer Suite 10g (9.0.4) were Oracle 9iDS Developer Suite Release 2 (9.0.2), and before that Oracle Internet Developer Suite version 1.0.2.4.x. Oracle Developer Suite 10g (9.0.4) uses new versions of all components, as listed in Table A1.
Table A1 Updated Oracle Developer Suite Components Release 1 Version 1.0.2.4.1 3.2.31 Release 2 (9.0.2) Version 9.0.2.x 10g (9.0.4) Version 9.0.4.x
Component Oracle9i JDeveloper (including Oracle Business Intelligence Beans, and UIX and Bali subcomponents) Oracle Reports Developer Oracle Discoverer Administrator (formerly Discoverer Administration Edition) including Oracle Discoverer Desktop Oracle Warehouse Builder Oracle Forms Developer
6i Release 2 4.1.37
9.0.2.x 9.0.2.39
9.0.4.x 9.0.4.x
2.1.1.34.11 & 9.0.2.56.0 6i Release 2, Patch 4a
9.0.2.x 9.0.2.x
N/A2 9.0.4.0.4
Upgrade Notes A-1
Oracle9i JDeveloper
Table A1
(Cont.) Updated Oracle Developer Suite Components Release 1 Version 1.0.2.4.1 N/A 6i Release 4 6i Release 4 Release 2 (9.0.2) Version 9.0.2.x3 9.0.2.80.11 9.0.2.80.11 10g (9.0.4) Version N/A 9.0.4.x 9.0.4.x
Component Oracle9i Application Server Clickstream Intelligence Oracle Software Configuration Manager Oracle Designer
1 2 3
Oracle9i Business Intelligence Beans was first released in Oracle9iDS Release 2 (9.0.2) Oracle9i Warehouse Builder Release 2 (9.0.4) is now available separately from Oracle Developer Suite. Oracle9i Application Server Clickstream Intelligence was only included in Oracle9i Developer Suite Release 2 (9.0.2).
Some components were also released individually. For example, Oracle9i JDeveloper was released as version 9.0.3, after the release of Oracle9i Developer Suite Release 2 (9.0.2). The version history for each component is documented in the components specific instructions in this guide, and also in the components release notes. To successfully migrate from Oracle Internet Developer Suite version 1.0.2.x to Oracle Developer Suite 10g (9.0.4), you must install Oracle Developer Suite into a new Oracle home. See Section 2.6, "Coexistence in One Oracle Home" for information about installing Oracle Developer Suite over the former version. After installing Oracle Developer Suite and performing the required postinstallation tasks, refer to the following subsections for migration information about each component.
A.2 Oracle9i JDeveloper

You can migrate user settings from the production release of JDeveloper 9.0.2 to JDeveloper 9.0.4. Your system settings, libraries, and connections will be migrated. Oracle does not support direct migration from version 3.2.3 to 9.0.4.
A.2.1 Migrating JDeveloper User Settings from Release 9.0.2 to Release 9.0.4
Note: Any time you use the following procedure to migrate user
settings from another installation of JDeveloper, you lose any settings that you have made in the current installation. To migrate your user settings:
1.
Start JDeveloper from a command line or shell prompt with the -migrate flag: jdev -migrate JDeveloper displays the Migrate User Settings dialog.
A-2 Installation Guide
Oracle Business Intelligence Beans
2.
Select a version of JDeveloper to migrate. If the Version dropdown list is empty, click Browse to search for a version. Select the directory previous_install_home\jdev\system (for Windows) or previous_install_home/jdev/system (for Linux, Solaris, and HP-UX), where previous_install_home is the home directory of the JDeveloper installation from which you want to migrate.
3. 4.
Select the settings and customizations you want to migrate. Oracle recommends that you select all the options. Click OK. JDeveloper migrates your user settings.
A.2.2 Additional Migration Issues

For more information about migration issues, see the topic "Ways to Migrate to Oracle9i JDeveloper (9.0.4)" in the JDeveloper online help section Getting Started with JDeveloper.
A.3 Oracle Business Intelligence Beans

If you are upgrading Oracle Business Intelligence Beans from a previous release, then you must configure your JDeveloper BI Beans projects. The procedure is slightly different if you are upgrading from release 9.0.2 than if you are upgrading from release 9.0.3.
A.3.1 Migrating Oracle BI Beans Projects from Release 9.0.2 to Release 9.0.4
To migrate projects created in release 9.0.2 to Oracle BI Beans release 9.0.4, perform the following tasks in the order shown. You must perform these steps for each project you wish to migrate:
1.
Allow JDeveloper to configure the project. Because JDeveloper 9.0.4 uses a different file format for its workspaces and projects, you must follow these steps to upgrade your existing workspaces and projects:
a. b. c.
Open the workspace within JDeveloper 9.0.4. Click Yes when prompted to upgrade the workspace. The Upgrade UIX Installables dialog box appears if you are migrating an application that uses uiXML. Choose Do Nothing. You will perform the migration manually in step 5.
2.
Configure the project to remove the ORB options. Borland Enterprise Server VisiBroker Edition is no longer required to connect to Oracle9i. To remove all ORB-related VM options, follow these steps:
a. b.
In the JDeveloper System Navigator, right-click the project node and choose Project Settings from the drop-down list. Under Development, click Runner.
Upgrade Notes A-3
c.
Delete the following Java Options: Dorg.omg.CORBA.ORBClass=com.inprise.vbroker.orb.ORB Dorg.omg.CORBA.ORBSingletonClass= com.inprise.vbroker.orb.ORB DORBdisableLocator=true
3.
Update the project settings.

Note: This step is necessary only if you have not added anything
to the project. If you have added a tag or otherwise extended the project, then these steps will have happened automatically. Oracle BI Beans projects require the Oracle9i Release 2 JDBC drivers. It you have not already done so, you must upgrade the drivers, as described in Section 3.2.2.2, "Oracle Business Intelligence Beans" under "Additional Tasks". In addition, because BI Beans no longer supports Oracle9i Release 1, you must update the OLAP library. After the drivers have been upgraded, complete these steps:
a.
While in the Project Settings dialog box with Runner selected, enter the following in the Java Options field, replacing oracle_home with the absolute path of the directory where JDeveloper is installed: -Djava.ext.dirs=oracle_home/jdev/bibeans/jdbc/lib_92
b. c. d. e. 4.
Click Libraries. Move Oracle JDBC 92 from Available Libraries to Selected Libraries. Move OLAP API 92 from Available Libraries to Selected Libraries. Click OK.
Upgrade applications that contain Oracle BI Beans servlets (Servlets only). Note: Oracle BI Beans no longer supports Apache JServ. In an application that contains a Oracle BI Beans servlet, you must update the servlet to reference the new style sheet. To do so, override the getStyleSheetName method in your BIController# class to return biaddins.xss, the name of the new style sheet. Base classes for the BI Servlet have moved. You can address this change by creating a new project and generating a new servlet or, if you prefer, you can restore the base classes to their location in 9.0.2. If you choose to do this, then you will see a number of deprecation warnings, which you can ignore. To restore the 9.0.2 base classes, follow these steps:
a. b. c. d. e. f.
Copy biservlet_902.zip from the bibeans/lib directory into the project source directory. In the JDeveloper System Navigator, select the project that contains the servlet. From the File menu, open biservlet_902.zip, which adds it to that project. In the System Navigator, right-click the project node and choose Project Settings from the drop-down list. Under Common, select Input Paths. Click Edit to edit the Java Source Path field.
g. h. i. 5.
In the Edit Java Source Path dialog box, click Add Entry. Browse to the project source directory and select biservlet_902.zip. Click Select.
Upgrade the cabo directory (HTML-client applications only). When you create an HTML project in JDeveloper, the cabo directory is created under the public_html directory. It contains the uiXML and Oracle BI Beans images, style sheet, and Javascript files, which can change between releases. To upgrade this directory, follow these steps:
a. b. c. d. e.
Navigate to the public_html directory of the project to be upgraded. Rename the cabo directory to cabo.9.0.2. In JDeveloper, create a new project in the same workspace. Select the project and, from the File menu, choose New. In the Business Intelligence category, select Servlet application. (Even if you are not upgrading a servlet, you must choose Servlet application to ensure that you are getting the latest images.) Complete the screens in the Servlet Wizard. After you specify a BI Designer, you can simply accept the defaults. When the servlet is generated, it creates a new cabo directory for the project. Navigate to the public_html directory for this new project and copy the new cabo directory to the public_html directory of the project you are upgrading from BI Beans 9.0.2. If your old directory (cabo.9.0.2) contained any other files (for example, if you created a new stylesheet or .xss file), then you must copy those files to the new cabo directory. (Optional) You can safely delete the new project that was created.
f.
g.
h.
i. 6.
Upgrade the Oracle BI Beans Catalog. Perform the following steps to upgrade your Oracle BI Beans Catalog. Important: If your existing BI Beans Catalog runs against release 8.1.7 of the Oracle database, then before performing these steps, you must upgrade the database to Oracle9i using standard database migration tools.
a. b. c.
Ensure that the environment variable JDEV_ORACLE_HOME is set to the Oracle home directory. Ensure that the environment variable JAVA_HOME is set to the directory where the JDK is installed. Use the upgrade utility to upgrade the catalog. The utility is located in the oracle_home/bibeans/bin directory. Its syntax is as follows: bi_upgradecatalog -u username -p password [-j oci8|thin] [-s servicename] | [-h hostname -po portnumber -sid sid]]
Example (using the recommended thin driver): bi_upgradecatalog -u BIBCAT -p BIBCAT -j thin -h test-lap -po 1521 -sid orcl
Upgrade Notes A-5
A.3.2 Migrating Oracle BI Beans Projects from Release 9.0.3 to Release 9.0.4
To migrate projects created in release 9.0.3 to Oracle BI Beans release 9.0.4, perform the following tasks in the order shown.You must perform these steps for each project you wish to migrate:
1.
Allow JDeveloper to configure the project. Because JDeveloper 9.0.4 uses a different file format for its workspaces and projects, you must follow these steps to upgrade your existing workspaces and projects:
a. b. c.
Open the workspace within JDeveloper 9.0.4. Click Yes when prompted to upgrade the workspace. The Upgrade UIX Installables dialog box appears if you are migrating an application that uses uiXML. Choose Do Nothing. You will perform the migration manually in step 4.
This changes the workspace and project files from the 9.0.3 format to the 9.0.4 format.
2.
Update the library used by the project (for projects that used Oracle9i Release 1). BI Beans 9.0.4 no longer supports Oracle9i Release 1. You must update the OLAP library used in your projects by performing the following steps:
a. b. c. d. e.
In the system Navigator, right-click the project node and choose Project Settings from the drop-down list. Under Development, click Libraries. Select OLAP API 92 in the list of available libraries, then click the Move button (>) to move it to the list of selected libraries. Select OLAP API 901 in the list of selected libraries, then click the Remove button (<) to remove it from the list. Do not close the dialog. Continue with the next procedure.
3.
Update the project settings.

Note: This step is necessary only if you have not added anything
to the project. If you have added a tag or otherwise extended the project, then these steps will have happened automatically. BI Beans projects require the Oracle9i Release 2 JDBC drivers. It you have not already done so, you must upgrade the drivers, as described in Section 3.2.2.2, "Oracle Business Intelligence Beans" under "Additional Tasks". Because the location of the Release 2 JDBC drivers has changed, you must upgrade to the new drivers even if you did so in release 9.0.3. After the drivers have been upgraded, you must update the Java Options for each project, as follows:
a. b.
While in the Project Settings dialog box, under Development, click Runner. Enter the following in the Java Options field, replacing oracle_home with the absolute path of the directory where JDeveloper is installed: -Djava.ext.dirs=oracle_home/jdev/bibeans/jdbc/lib_92
c.
Click Libraries.
Oracle Reports Developer
d. e. 4.
Move Oracle JDBC 92 from Available Libraries to Selected Libraries. Click OK.
Upgrade the cabo directory (HTML client applications only). When you create an HTML project in JDeveloper, the cabo directory is created under the public_html directory. It contains the uiXML and BI Beans images, style sheet, and Javascript files, which can change between releases. To upgrade this directory, follow these steps:
a. b. c. d. e.
Navigate to the public_html directory of the project to be upgraded. Rename the cabo directory to cabo.9.0.3. In JDeveloper, create a new project in the same workspace. Select the project and, from the File menu, choose New. In the Business Intelligence category, select Servlet application. (Even if you are not upgrading a servlet, you must choose Servlet application to ensure that you are getting the latest images.) Complete the screens in the Servlet Wizard. After you specify a BI Designer, you can simply accept the defaults. When the servlet is generated, it creates a new cabo directory for the project. Navigate to the public_html directory for this new project and copy the new cabo directory to the public_html directory of the project you are upgrading from BI Beans 9.0.3. If your old directory (cabo.9.0.3) contained any other files (for example, if you created a new stylesheet or .xss file), then you must copy those files to the new cabo directory. (Optional) You can safely delete the new project that was created.
f.
g.
h.
i.
A.4 Oracle Reports Developer
If you want to reuse the 6i Reports server persistent file and server configuration file, you can copy them to the Oracle Reports Server 10g 9.0.4 (Reports Server) directory. Reports Server will automatically convert your 6i files to the Reports Server 10g 9.0.4 format. To do this, copy the following files: For Windows: 6i_oracle_home\reports60\server\report_server_name.ora to 10g_oracle_home\reports\conf\report_server_name.ora 6i_oracle_home\reports60\server\report_server_name.dat to 10g_oracle_home\reports\server\report_server_name.dat
Upgrade Notes A-7
For Linux, Solaris, and HP-UX: 6i_oracle_home/reports60/server/report_server_name.ora to 10g_oracle_home/reports/conf/report_server_name.ora 6i_oracle_home/reports60/server/report_server_name.dat to 10g_oracle_home/reports/server/report_server_name.dat
After opening a .rdf file from an earlier version of Oracle Reports, you must recompile the PL/SQL. If you have installed a version of Oracle Discoverer from Oracle9iAS version 1.0.x, you will have Visibroker 3.4 running on your computer. Oracle Application Server Reports Services 10g (9.0.4) requires Visibroker 4.5, which cannot be run simultaneously with Visibroker 3.4. If you plan to install Oracle Application Server Reports Services 10g (9.0.4) onto the same computer with your older version of Oracle Discoverer, you must first shut down Visibroker 3.4. After installation, if you need to run your older version of Oracle Discoverer, you must manually stop Visibroker 4.5 and start Visibroker 3.4. Note that, when you have taken this action, you are effectively disabling the Oracle Application Server Reports Services 10g (9.0.4) component until you return to running Visibroker 4.5.
A.5 Oracle Discoverer Administrator

If you have an earlier version of Discoverer Administrator (formerly Discoverer Administration Edition) on your computer, you need to upgrade the End User Layer before you can use Oracle Discoverer Administrator to perform administration tasks (unless you have version 9.0.2.53 or later, in which case no EUL upgrade is required). To upgrade an EUL, follow the instructions in Chapter 23 "Upgrading from earlier versions of Discoverer" of the Oracle Discoverer Administrator Administration Guide in the Oracle Developer Suite Documentation Library.
A.6 Oracle Forms Developer

Review the guide Oracle Forms Developer and Forms Services: Migrating Forms Applications from Forms6i in the Oracle Developer Suite Documentation Library.
A.7 Oracle Software Configuration Manager

Oracle Software Configuration Manager was formerly Oracle Repository. Please check OracleMetalink (http://metalink.oracle.com) for any patchsets to the product "Designer", release "Designer/Repository 9i" and upgrade your client software by installing the latest 9.0.4 patchset into the existing oracle_home before you upgrade/install your server side repository. This will avoid having to upgrade the repository twice.
If you are migrating from a pre-6i repository: Install Oracle Developer Suite 10g using the Rapid Application Development or Complete install option. Follow the instructions for installing a new repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
1. 2.
Additional Documentation
3.
Follow the instructions for migrating data from an existing pre-6i repository to a new one in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client. If you are upgrading from a release 6i or later repository: Follow the instructions for upgrading a release 6i or later repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
A.8 Oracle Designer

Please check OracleMetalink (http://metalink.oracle.com) for any patchsets to the product "Designer", release "Designer/Repository 9i" and upgrade your client software by installing the latest 9.0.4 patchset into the existing Oracle home before you upgrade/install your server side repository. By doing this, you will avoid having to upgrade the repository twice.
If you are migrating from a pre-6i repository: Install Oracle Developer Suite 10g using the Rapid Application Development or Complete install option. Follow the instructions for installing a new repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client. Follow the instructions for migrating data from an existing pre-6i repository to a new one in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client. If you are upgrading from a release 6i or later repository: Follow the instructions for upgrading a release 6i or later repository in the Oracle SCM Repository Installation Guide, which is available from the Start menu of the SCM client.
1. 2. 3.
A.9 Additional Documentation

All components have online help that is installed with the product. Some components provide additional documentation that is available on the Oracle Developer Suite Documentation Library. For information on viewing and installing the Oracle Developer Suite Documentation Library, see Appendix C, "Installing the Documentation Library". For documentation updates, white papers, or other collateral, please visit the Oracle Technology Network at http://otn.oracle.com.
Upgrade Notes A-9
Additional Documentation
A-10
Installation Guide
B
Components
Oracle Developer Suite combines leading Oracle application development and business intelligence tools into a single, integrated product. Built on Internet standards such as Java and XML, the suite provides a complete and highly productive development environment for building applications for Oracle Application Server and Oracle9i Database. This appendix briefly describes the development tools available in Oracle Developer Suite. The following topics are included: Oracle9i JDeveloper Oracle Business Intelligence Beans Oracle Reports Developer Oracle Discoverer Administrator Oracle Forms Developer Oracle Software Configuration Manager Oracle Designer Additional Documentation
B.1 Oracle9i JDeveloper

Oracle9i JDeveloper is a J2EE and XML development environment with end-to-end support for developing, debugging, and deploying business applications and Web Services. To maximize developer productivity, JDeveloper provides a comprehensive set of integrated tools to support the complete development life-cycle, including the industry's fastest Java debugger and the innovative profiler and CodeCoach tools for code performance analysis and improvement. JDeveloper simplifies J2EE development by providing wizards, editors, visual design tools, and deployment tools to create high-quality, standard J2EE components including applets, JavaBeans, JavaServer Pages, servlets, and Enterprise JavaBeans. To simplify the development of scalable, high-performance J2EE applications, JDeveloper offers an open and extensible J2EE framework called Business Components for Java (BC4J). BC4J is an object-relational mapping tool that implements Sun's J2EE design patterns, allowing developers to quickly build sophisticated J2EE applications.
Components B-1
Oracle9i JDeveloper
B.1.1 Supported Deployment Environments

JDeveloper can be used to deploy applications in a variety of environments. JDeveloper is based on Sun Java SDK 1.4.1, and the applications or components that you create may be deployed on any J2EE certified platform running that SDK version. Although JDeveloper and clients developed with JDeveloper may work in other environments, this version of JDeveloper has been specifically certified for the following environments:
Browser Netscape Navigator 4.79 and higher Microsoft Internet Explorer 5.5, 6.0 Java WebStart
Application Server Oracle Application Server versions 9.0.2, 9.0.3, and 9.0.4 Oracle Application Server Containers for J2EE 2.0.0.0, 9.0.2, 9.0.3, and 9.0.4 Visibroker 4.5.1 WebLogic 6.1, 7.0 Service Pack 1 Apache Tomcat 4.1.12 JBoss 3.0.4 (with Tomcat 4.1.12)
Client Runtime Platforms (platforms for applications, WebStart, and JSPs created with JDeveloper and deployed to an appropriate Application/Database Server) Windows NT 4.0 (Service Pack 6a or higher) Linux x86, with either KDE2 or GNOME desktop HP-UX, with either CDE or VUE desktop
JDBC Oracle Thin JDBC Oracle JDBC-OCI8 Oracle Lite JDBC Sun JDBC-ODBC Bridge
Database (this lists the data sources you can connect to and develop against) Oracle9i RDBMS v9.0.1 and v9.2.0.2 Oracle8i RDBMS v8.1.7.1 and v8.1.7.2
The version of the Java Virtual Machine (JVM) included in both Netscape Navigator and Microsoft Internet Explorer is older than the 1.4.1 JVM used in JDeveloper. Therefore, user's browsers may require you to install a JVM Plug-in. You can download the plug-in from http://java.sun.com/products/plugin.
B-2 Installation Guide
Oracle9i JDeveloper
B.1.2 Oracle on the Web

Oracle provides a number of resources on the Web. These are some sites you may find helpful:
Corporate Site http://www.oracle.com/
Oracle9i JDeveloper http://www.oracle.com/ip/develop/ids/index.html?java.htm
Oracle Technology Network http://otn.oracle.com/
JDeveloper on OTN http://otn.oracle.com/products/jdev/
JDeveloper OTN discussion forum (click Discussions) http://otn.oracle.com/products/jdev/
Worldwide Customer Support http://www.oracle.com/support/
B.1.3 Oracle Business Intelligence Beans

Oracle Business Intelligence Beans is an integrated component of JDeveloper that enables developers to build applications that incorporate business intelligence capabilities. Such applications can be deployed in an HTML-client environment, where the application runs on a server and is viewed in a browser on the user's computer, or in a Java-client environment, where Java runs on the user's machine. The analysis features of BI Beans rely on the new analytic capabilities provided in the Oracle9i Database -- OLAP option. The key components of Oracle BI Beans are the following:

Presentation beans: Graph, Crosstab, and Table OLAP (data) beans: QueryBuilder, CalcBuilder, and Dimension List BI Beans Catalog and associated persistence services HTML-client applications based on business intelligence UIX components (servlets) or JSP tags
B.1.3.1 Deployment Requirements

This section describes requirements for the deployment environment. For information about deploying applications, consult the Help system. In the Table of Contents, expand the Oracle Business Intelligence Beans node, then click Deploying Applications. Data server: Oracle9i Enterprise Edition Release 2 (9.2.0.3 or higher) with the OLAP option and with all required patch sets. For a complete list of required patch sets as well as up-to-date information about which database releases are supported, consult the Oracle BI Beans product area on Oracle Technology Network (http://otn.oracle.comproducts/bib/content.html).
Components B-3
Oracle9i JDeveloper
Metadata: Appropriate metadata must be defined in the Oracle database in order to support business intelligence applications. For information about defining OLAP metadata, see the Oracle9i OLAP Services Concepts and Administration Guide, which is part of the documentation set for Oracle9i, or refer to the Help system for the OLAP management tool in Oracle Enterprise Manager, which is the tool you use to create the metadata. You can also use Oracle Warehouse Builder to create appropriate metadata. Browser: In an HTML-client application, the user's browser must support cookies. Image generation on Linux, Solaris, and HP-UX platforms: Image generation for JSP and servlet applications on Linux, Solaris, and HP-UX must run in a "headless" environment -- that is, on a computer that lacks frame buffer hardware. You must explicitly enable headless mode, as follows:
1. 2. 3.
In the JDeveloper System Navigator, right-click the project node and choose Project Settings from the drop-down list. Under Development, click Runner. Add the following Java Option: -Djava.awt.headless=true
Requirements for applications that are deployed to Oracle Application Server Oracle BI Beans uses different .jar files from those that ship with Oracle Application Server. If you want to deploy a Oracle BI Beans application to Oracle Application Server, then you must follow the procedure in Setting up a Separate OC4J Instance for a BI Beans Application, which is available from the Oracle BI Beans product area on Oracle Technology Network (http://otn.oracle.com/products/bib/content.html). Deploying to Other Web Servers Oracle Corporation supports deployment of Oracle BI Beans applications to BEA WebLogic Server. See the technical note, Deploying Applications to BEA WebLogic Server, which is available from the Oracle BI Beans product area on Oracle Technology Network (http://otn.oracle.com/products/bib/content.html). Additional technical notes that describe how to deploy to other web servers will be posted as they become available. Requirements for applications that use the BI Beans Catalog
Database: The BI Beans Catalog can use either Oracle9i Database Release 1 or Release 2. Client-side driver: Oracle JDBC Thick (OCI) driver. Recommended for better performance, especially in a multiuser environment. Also recommended for use with JDeveloper in a WAN environment. This driver is installed with Oracle9i and requires configuration. To configure the driver, you must install the Oracle9i client on the computer where BI Beans is running. You can download the Oracle9i client from Oracle Technology Network (http://otn.oracle.com), where it is available as a separate download on the main Oracle9i download page. or Oracle JDBC Thin (Pure Java) driver. Installed with Oracle9i JDeveloper; recommended for use with JDeveloper, except in a WAN environment.
B.1.4 UIX
Integrated UIX technology components in JDeveloper enable you to rapidly build HTML-based clients which utilize Servlets and JSPs. UIX is an open framework for building J2EE-compliant web applications. UIX includes Java class libraries, APIs, parsers, and other software for creating web applications with page-based navigation, such as an online shopping application. Although UIX is server-based and implemented in the Java programming language, Java is not required on the client. All you need to view a UIX application is a browser. UIX supports a variety of clients, including HTML-compliant browsers and mobile devices. The UIX technologies are located in the oracle.cabo package and its subpackages.
B.1.5 Bali
Integrated Bali technology components in JDeveloper enable you to rapidly build traditional Java-based clients such as Java applets and applications. Bali is a set of technologies that constitute a framework for building the presentation layer of your Java-based client applications. Bali technologies build upon the JFC (Java Foundation Classes) framework and provide an Oracle Look and Feel implementation. Oracle Help for Java is also available as a component for integration into any Java-based product. All of the Bali technologies are implemented in 100% Java code and located in the oracle.bali package and its subpackages.
B.2 Oracle Reports Developer

Oracle Reports Developer enables you to build and publish high-quality Web and paper reports based on dynamic data. All reports developed using Oracle Reports Developer can be deployed seamlessly on Oracle Application Server. Using Oracle Reports Developer makes publishing information easy because it allows you to access any data, and publish it in any format, and send it anywhere. For example, you can publish data from sources such as SQL databases, OLAP databases, XML feeds, and JDBC-enabled data sources. Through Oracle Application Server, you can publish your reports in a variety of widely used formats, including HTML, PDF, delimited text, RTF, PostScript, PCL, and XML. You can also extend your HTML reports pages by embedding your own data-driven Java components or Oracle Reports Developer custom JSP tags into the HTML document via a wizard interface. The use of wizards expedites major tasks in report production, while the use of report templates and a live data pre-viewer allows for easy customization of the report structure.
B.3 Oracle Discoverer Administrator

Oracle Discoverer Administrator (formerly Oracle Discoverer Administration Edition) is a tool for designing and presenting a business user oriented view of data from data warehouses, data marts, and online transaction processing systems for business professionals to access using Discoverer Plus and Discoverer Viewer (available in Oracle Application Server). The installation of Oracle Discoverer Administrator includes a copy of Oracle Discoverer Desktop. Oracle Discoverer Administrator is the only tool you need to support your Discoverer Plus, Discoverer Desktop, and Discoverer Viewer users.
Components B-5
Oracle Forms Developer
B.4 Oracle Forms Developer

Oracle Forms Developer is a rapid application development tool that provides a highly productive, end-to-end development environment for building enterprise-class, database-centric Internet applications with a rich Java interface. The integrated set of builders, re-entrant wizards, and property palettes enable you to quickly develop sophisticated, multi-lingual, and interactive forms and business logic with minimal coding effort. Applications developed using Oracle Forms Developer can be instantly deployed to the Internet using the Forms Servlet and Forms Listener Servlet, which are included with Oracle Application Server. Oracle Forms Developer includes a subcomponent to help manage the translation of Oracle Forms and Oracle Reports files into different languages. This subcomponent, called TranslationHub, is available on Windows only and enables you to make efficient, consistent translations.
B.5 Oracle Software Configuration Manager

Oracle Software Configuration Manager (Oracle SCM), formerly Oracle Repository, is a highly scalable software configuration management system for multi-developer, multi-stream software development projects of any size and complexity. The repository-based architecture manages structured and unstructured data throughout the development life-cycle. Comprehensive features of Oracle SCM include version control and version history, configuration management for component-based application architectures, and dependency management.
B.6 Oracle Designer

Oracle Designer enables you to visually model and automatically generate databases and applications that exploit the power and portability of Java and HTML user interfaces. Oracle Designer is a wizard-based, task-oriented, integrated design and generation toolset that lets you model, generate, and capture the requirements and design of n-tier Internet applications quickly, accurately, and efficiently. The robust design capture features enable you to protect your current investment by capturing all the design information for a legacy application easily.
B.7 Additional Documentation

All components have online help systems that are installed with the product. Some components provide additional documentation that is available in the Oracle Developer Suite Documentation Library. For information on viewing and installing the Oracle Developer Suite Documentation Library, see Appendix C, "Installing the Documentation Library".
C
All components provide online help systems that are installed with the product. The Oracle Developer Suite Documentation Library contains additional documentation for some components only. Most documentation in the Documentation Library is available in both HTML and PDF formats. The following topics describe the contents of the Documentation Library and provides instructions for installing and viewing the documentation:

Documentation Library Titles Installing the Documentation Library Viewing the Documentation Library
C.1 Documentation Library Titles

The Documentation Library titles are listed in the following tables. Most titles are available as printed and bound manuals from the Oracle Store at http://store.oracle.com.
Table C1 Getting Started Title Oracle Developer Suite 10g (9.0.4) Installation Guide for Windows, Linux, Solaris, and HP-UX Oracle Developer Suite 10g (9.0.4) Quick Installation Guide for Windows, Linux, Solaris, and HP-UX Oracle Developer Suite 10g (9.0.4) Release Notes for Windows, Linux, Solaris, and HP-UX Oracle Discoverer Administrator Administration Guide 10g (9.0.4)
Part Number B10579-02 B13736-01 B10668-03 B10270-01
Table C2
J2EE & Internet Applications Title Oracle Forms Migrating Forms Applications from Forms 6i to 10g (9.0.4) for Windows and UNIX Oracle Application Server Forms Services Deployment Guide 10g (9.0.4) for Windows and UNIX Oracle Application Developer's Guide - XML 10g (9.0.4) Oracle XML Reference 10g (9.0.4)
Part Number B10469-01 B10470-01 B12099-01 B10926-01
Installing the Documentation Library C-1
Table C2
(Cont.) J2EE & Internet Applications Title Oracle Application Server Containers for J2EE Servlet Developer's Guide 10g (9.0.4) Oracle Application Server Containers for J2EE Services Guide 10g (9.0.4) Oracle Application Server Containers for J2EE Enterprise JavaBeans Developer's Guide 10g (9.0.4) Oracle Application Server Containers for J2EE Support for JavaServer Pages API Reference 10g (9.0.4) Oracle Application Server Containers for J2EE JSP Tag Libraries and Utilities Reference 10g (9.0.4) JAAS Provider API Reference 10g (9.0.4)
Part Number B10321-01 B10326-01 B10324-01 B10387-01 B10319-01 B10389-01
Table C3
Business Intelligence Title Oracle Discoverer Administrator Administration Guide 10g (9.0.4) Oracle Discoverer Administrator Tutorial 10g (9.0.4) Oracle Discoverer Desktop User's Guide 10g (9.0.4) for Windows Oracle Discoverer EUL Command Line for Java User's Guide 10g (9.0.4) Oracle Reports Tutorial 10g (9.0.4) Oracle Application Server Reports Services Publishing Reports to the Web 10g (9.0.4) (volumes 1 and 2) Oracle Reports Developer Building Reports 10g (9.0.4) (volumes 1 and 2)
Part Number B10270-01 B10271-01 B10272-01 B10274-01 B10612-01 B13673-01 B10602-01
C.2 Installing the Documentation Library

You can install the Documentation Library from CD-ROM or DVD in one of the following ways:

Copy the files from the disk to your local computer. Use the installer.
C.2.1 File Copy Installation Method

The simplest installation method is to directly copy the files from the Oracle Documentation Library CD-ROM or Oracle Developer Suite and Documentation DVD to your computer. Use the operating environment commands to copy the contents of the doc directory on the CD-ROM or the /doc_library/doc directory on the DVD to the appropriate installation directory on your computer. For consistency with installations performed by the installer, Oracle recommends that you copy the contents to the Oracle home where Oracle Developer Suite is installed, and that you name the directory doc/dl.
C-2 Installation Guide
To copy the documentation from the CD-ROM or DVD to your Oracle home directory, do the following:
Note: This method may overwrite files if the destination directory
already exists. For Windows, enter the following command: CD-ROM: prompt> xcopy /s cdrom_drive\doc oracle_home DVD: prompt> xcopy /s dvd_drive\doc_library\doc oracle_home For Linux, Solaris, and HP-UX, enter the following command: CD-ROM: prompt> cp -r mount_point/doc oracle_home DVD: prompt> cp -r mount_point/doc_library/doc oracle_home
C.2.2 Installer Method

The installer can also install the documentation to your computer from the CD-ROM or DVD.
Note: To use the installer, you must already have the installer or
an Oracle product that uses the installer (i.e., Oracle Developer Suite) on your computer. The following instructions describe how to install the documentation with the installer:
1.
Launch the installer from your computer, from the Oracle Developer Suite Disk 1 CD-ROM, or from the Oracle Developer Suite and Documentation DVD. This is the same disk used to install Oracle Developer Suite.
See Also: Section 2.9.4, "Starting the Installer".
2. 3.
At the Welcome screen, click Next. At the File Locations screen, do the following:
a. b.
If you are using the Disk 1 CD-ROM, eject it and replace it with the Documentation Library CD-ROM. If you are using the DVD, do not eject it. In the Source field, do the following: For Windows, enter: CD-ROM: cdrom_drive:\stage\products.jar DVD: dvd_drive:\doc_library\stage\products.jar
Installing the Documentation Library C-3
Viewing the Documentation Library
For Linux, Solaris, and HP-UX, enter: CD-ROM: mount_point_directory/stage/products.jar DVD: mount_point_directory/doc_library/stage/products.jar This directs the installer to the installation file for the Documentation Library.
c.
In the Destination section, enter the name and path to the Oracle home you are installing the documentation to, or select one from the list. The documentation will be installed in the doc directory under Oracle home.
d. 4. 5.
Click Next to continue.
At the Summary screen, review the summary and click Install to begin the installation. After installation is completed, the End of Installation screen will appear. Click Exit to quit the installer, then confirm your choice by clicking Yes.
C.3 Viewing the Documentation Library

You can view the Oracle Developer Suite Documentation Library directly from the CD-ROM or DVD, or from the directory on your computer where you installed it. For information about the tools required to view the documentation, see Section 2.5, "Online Documentation Requirements". To view the documentation library:
1.
On Windows, if you used the installer method to copy the documentation, you can access the library from the Start Menu as follows: Start > Programs > Oracle Developer Suite - oracle_home > Documentation > Doc CD Alternatively, you can use your browser to open the index.htm file from the doc directory on the CD-ROM, the /doc_library/doc directory on the DVD, or from oracle_home/doc/dl on your computer after installation.
2. 3.
Click on a tab. Click on the HTML or PDF link next to a document title to see the document contents.
C.3.1 Viewing the Release Notes from Disk

To view the release notes from the Documentation Library CD-ROM or DVD:
1. 2.
Use your browser to open the index.htm file from the doc directory on the CD-ROM, or the /doc_library/doc directory on the DVD. Click the Getting Started tab. This page displays links to release notes for Oracle Developer Suite and for the individual components.
C-4 Installation Guide
D
Silent and Non-Interactive Install
This chapter describes the silent and non-interactive installation of Oracle Developer Suite. The topics include:

Introduction Requirements Preinstallation Working with Response Files Starting the Installation Postinstallation
D.1 Introduction
Oracle Developer Suite features two methods of non-interactive installation:

Silent Installation Non-Interactive Installation
Both methods are available for both Windows and for Linux, Solaris, and HP-UX platforms.
D.1.1 Silent Installation

To do a silent installation of Oracle Developer Suite, you supply the installer with a response file and specify the -silent flag on the command line. The response file is a text file. The installer uses the variables and parameter values in the response file to provide answers to all of the installation prompts. You include responses for all of the installation prompts in the response file. Silent installation does not display graphical output. Use silent installation when you want to do similar installations to more than one computer. You can also use silent installation to install from a remote location using the command line. With silent installation, you do not need to monitor your installation because you do not need to enter information and you do not have a graphical user interface to watch.
Silent and Non-Interactive Install D-1
Requirements
D.1.2 Non-Interactive Installation

You can also do a non-interactive installation of Oracle Developer Suite. You do this by supplying the installer with a response file, but you do not specify the -silent flag on the command line. The installer uses the variables and parameter values contained in the response file to provide answers to some or all of the user prompts. The installer displays its graphical user interface as in a normal installation, and if you choose not to provide responses to all of the prompts, you can enter information during the installation. Use non-interactive installation when you want to see specific installation screens, or you want to enter some information interactively. You can also use non-interactive installation from a remote location using the command line.
D.2 Requirements
For a complete list of installation requirements, refer to Chapter 2, "Getting Started".
D.3 Preinstallation
Before you install, do the following:
1.
Complete the preinstallation tasks listed in Section 2.8, "Preinstallation Tasks".

Note: HP-UX only: You must download and install the HP-UX
Java SDK before you install Oracle Developer Suite. See Section 2.8.1, "General Checklist" for instructions.
2.
Windows NT only: Ensure that you have performed the Windows System Files (WSF) installation. For instructions on starting the installation, please see Section 2.9.4.1.1, "Windows System Files Installation". Linux, Solaris, and HP-UX only: Create the installers inventory directory. To do this, navigate to the Oracle home directory you plan to use, and create a subdirectory such as oracle_home/oraInventory. For more information about the inventory directory, see Section 2.9.3, "The Installer Inventory Directory". Linux, Solaris, and HP-UX only: If this is the first Oracle installation on your computer, create a file that points to the inventory directory. To do this:
a. b. c.
3.
4.
Log in as the root user. Create the directory /var/opt/oracle (except for Linux x86). In the /var/opt/oracle directory (or for Linux x86, the /etc directory), create a file oraInst.loc and insert the following lines: inventory_loc=oracle_home/inventory_directory inst_group=inventory_owner_group where oracle_home is the Oracle home directory inventory_directory is the inventory directory. inventory_owner_group is a group that has write permission for inventory_ directory (see Section 2.8.6.1, "Group Name for the Installer Inventory")
D-2 Installation Guide
Working with Response Files
For example, you might enter the following lines:

inventory_loc=/private1/oracle/oraInventory inst_group=devsuitegrp
Note: On Linux x86, create /etc/oraInst.loc instead of
/var/opt/oracle/oraInst.loc.
D.4 Working with Response Files

To supply information to the installer in a silent or non-interactive installation, you provide a response file. As a starting point, use the response file templates supplied in the stage\Response directory (for Windows) or stage/Response directory (for Linux, Solaris, and HP-UX) on Disk 1 of your Oracle Developer Suite product CD-ROM. On the DVD, this directory is \developer_suite\stage\Response (for Windows) or /developer_suite/stage/Response (for Solaris). Response file templates are available for all of the Oracle Developer Suite install types:
Table D1 Install Type J2EE Development Business Intelligence (Windows only) Rapid Application Development (Windows Only) Complete Response file names for install Types Response File Template Name oracle.ids.toplevel.development.J2EE.rsp oracle.ids.toplevel.development.BI.rsp oracle.ids.toplevel.development.RAD.rsp
oracle.ids.toplevel.development.Complete.rsp
You can find definitions of the response file parameters in the template files.
Note: The installer will fail if you attempt to do a silent
installation using an incorrectly configured response file.
Note: Oracle recommends that you specify either "true" or "false"
for Boolean parameters.
Note: HP-UX only: You must also read section Section D.4.1.4,
"Using Response Files on HP-UX" for special instructions on using response files in a HP-UX environment.
D.4.1 Example Response Files for Oracle Developer Suite Installations

To improve readability, the template file examples listed here do not contain comment lines describing the parameters. You can look at the comment lines in the template files on the CD-ROM or DVD.
D.4.1.1 Business Intelligence (Windows only)

This listing shows an example of a response file for a silent installation of the Business Intelligence install type. You must replace the suggested values (shown in italics) with your desired responses:
RESPONSEFILE_VERSION=2.2.1.0.0 FROM_LOCATION="../stage/products.jar" FROM_LOCATION_CD_LABEL="Oracle Developer Suite 10g" LOCATION_FOR_DISK2="../../Disk2" ORACLE_HOME="C:\DevSuiteHome" ORACLE_HOME_NAME="DevSuiteHome" TOPLEVEL_COMPONENT={"oracle.ids.toplevel.development","9.0.4.0.0"} DEINSTALL_LIST={"oracle.ids.toplevel.development","9.0.4.0.0"} SHOW_SPLASH_SCREEN=true SHOW_WELCOME_PAGE=false SHOW_COMPONENT_LOCATIONS_PAGE=false SHOW_CUSTOM_TREE_PAGE=false SHOW_SUMMARY_PAGE=true SHOW_INSTALL_PROGRESS_PAGE=true SHOW_REQUIRED_CONFIG_TOOL_PAGE=true SHOW_CONFIG_TOOL_PAGE=true SHOW_RELEASE_NOTES=true SHOW_END_SESSION_PAGE=true SHOW_EXIT_CONFIRMATION=true NEXT_SESSION=false NEXT_SESSION_ON_FAIL=true SHOW_DEINSTALL_CONFIRMATION=true SHOW_DEINSTALL_PROGRESS=true ACCEPT_LICENSE_AGREEMENT=true RESTART_SYSTEM=true COMPONENT_LANGUAGES={"en"} INSTALL_TYPE="BI" b_olite_install=true mailServerName="servername.domainname" oracle.wsf.verification:PROD_HOME="C:\DevSuiteHome" oracle.wsf.install:PROD_HOME="C:\DevSuiteHome" oracle.swd.jre:PROD_HOME="C:\DevSuiteHome"
D.4.1.2 Complete Install (Windows)

This listing shows an example of a response file for a silent installation of the Complete install type for Windows. You must replace the suggested values (shown in italics) with your desired responses:
RESPONSEFILE_VERSION=2.2.1.0.0 FROM_LOCATION="../stage/products.jar" FROM_LOCATION_CD_LABEL="Oracle Developer Suite 10g" LOCATION_FOR_DISK2="../../Disk2" ORACLE_HOME="C:\DevSuiteHome" ORACLE_HOME_NAME="DevSuiteHome" TOPLEVEL_COMPONENT={"oracle.ids.toplevel.development","9.0.4.0.0"} DEINSTALL_LIST={"oracle.ids.toplevel.development","9.0.4.0.0"} SHOW_SPLASH_SCREEN=true SHOW_WELCOME_PAGE=false SHOW_COMPONENT_LOCATIONS_PAGE=false SHOW_CUSTOM_TREE_PAGE=false SHOW_SUMMARY_PAGE=true SHOW_INSTALL_PROGRESS_PAGE=true SHOW_REQUIRED_CONFIG_TOOL_PAGE=true
SHOW_CONFIG_TOOL_PAGE=true SHOW_RELEASE_NOTES=true SHOW_END_SESSION_PAGE=true SHOW_EXIT_CONFIRMATION=true NEXT_SESSION=false NEXT_SESSION_ON_FAIL=true SHOW_DEINSTALL_CONFIRMATION=true SHOW_DEINSTALL_PROGRESS=true ACCEPT_LICENSE_AGREEMENT=true RESTART_SYSTEM=true COMPONENT_LANGUAGES={"en"} INSTALL_TYPE="Complete" b_olite_install=true mailServerName="servername.domainname" oracle.wsf.verification:PROD_HOME="C:\DevSuiteHome" oracle.wsf.install:PROD_HOME="C:\DevSuiteHome" oracle.repository.ocxpack90:PROD_HOME="C:\DevSuiteHome" oracle.swd.jre:PROD_HOME="C:\DevSuiteHome"
D.4.1.3 Complete Install (Linux, Solaris, and HP-UX)

This listing shows an example of a response file for a silent installation of the Complete install type for Linux, Solaris, and HP-UX. You must replace the suggested values (shown in italics) with your desired responses:
RESPONSEFILE_VERSION=2.2.1.0.0 UNIX_GROUP_NAME=devsuitegrp FROM_LOCATION="../stage/products.jar" FROM_LOCATION_CD_LABEL="Oracle Developer Suite 10g" LOCATION_FOR_DISK2="../../Disk2" ORACLE_HOME="/private/DevSuiteHome" ORACLE_HOME_NAME="DevSuiteHome" TOPLEVEL_COMPONENT={"oracle.ids.toplevel.development","9.0.4.0.0"} DEINSTALL_LIST={"oracle.ids.toplevel.development","9.0.4.0.0"} SHOW_SPLASH_SCREEN=true SHOW_WELCOME_PAGE=false SHOW_COMPONENT_LOCATIONS_PAGE=false SHOW_CUSTOM_TREE_PAGE=false SHOW_SUMMARY_PAGE=true SHOW_INSTALL_PROGRESS_PAGE=true SHOW_REQUIRED_CONFIG_TOOL_PAGE=true SHOW_CONFIG_TOOL_PAGE=true SHOW_RELEASE_NOTES=true SHOW_ROOTSH_CONFIRMATION=true SHOW_END_SESSION_PAGE=true SHOW_EXIT_CONFIRMATION=true NEXT_SESSION=false NEXT_SESSION_ON_FAIL=true SHOW_DEINSTALL_CONFIRMATION=true SHOW_DEINSTALL_PROGRESS=true ACCEPT_LICENSE_AGREEMENT=true RESTART_SYSTEM=false COMPONENT_LANGUAGES={"en"} INSTALL_TYPE="Complete" b_olite_install=true mailServerName="servername.domainname" PROD_HOME="/private/DevSuiteHome"
Starting the Installation
D.4.1.4 Using Response Files on HP-UX

HP-UX only: Set the JDKHome variable in both the J2EE Development and Complete response files. This variable identifies the location of the Java 2 SDK 1.4.1 for PA-RISC. For example, if you installed the Java 2 SDK to /opt/java/java1.4.1 then you should ensure that the following line appears in the response file: JDKHome=/opt/java/java.1.4.1 If necessary, you should add the line to the response file using a text editor.
D.5 Starting the Installation

To use the response file at install time, start the installer from a command prompt. The form of the command depends on the platform you are installing to, and whether you wish to do a silent installation or a non-interactive installation.
D.5.1 Starting the Installer for a Silent Installation

To start the installer for a silent installation, enter the following at the command prompt:
Windows: setup -silent -responseFile absolute_path_and_filename
Linux, Solaris, and HP-UX:

./runInstaller -silent -responseFile absolute_path_and_filename
D.5.2 Starting the Installer for a Non-Interactive Installation

To start the installer for a non-interactive installation, enter the following at the command prompt:
Windows: setup -responseFile absolute_path_and_filename
Linux, Solaris, and HP-UX: ./runInstaller -responseFile absolute_path_and_filename
D.6 Postinstallation
The installer logs the result of a non-interactive or silent installation in the file installActions.log. For a silent installation, the installer also creates the file silentInstall.log. The log files are created in the inventory directory. After the installation finishes, follow the postinstallation steps described in Section 3.2, "Postinstallation Tasks"
E
Troubleshooting
This appendix lists some methods for troubleshooting your Oracle Developer Suite installation. It includes the following topics:

Before You Begin Troubleshooting the Installation Troubleshooting Oracle Developer Suite Configuration Assistants
E.1 Before You Begin

Oracle recommends that you review the following before you attempt to fix problems in your Oracle Developer Suite installation:

Verify Hardware and Pre-installation Requirements Read the Release Notes
E.1.1 Verify Hardware and Pre-installation Requirements

First, review the Oracle Developer Suite hardware and software requirements and pre-installation tasks:
Ensure that your computer meets the hardware requirements specified in Section 2.1, "Hardware Requirements". Ensure that your software operating environment is supported by Oracle Developer Suite 10g (9.0.4). For a list of supported operating environments, see Section 2.2, "Operating Environments Supported". Ensure that your supported software operating environment meets the software requirements specified in Section 2.3, "Operating Environment Software Requirements". Ensure that you have completed all the product-level pre-installation requirements specified at the beginning of Section 2.8, "Preinstallation Tasks". Ensure that you have completed all the component-level pre-installation requirements for the components you are installing. These are listed in Section 2.8.7, "Completing Component-specific Preinstallation Tasks".
Troubleshooting
E-1
Troubleshooting the Installation
E.1.2 Read the Release Notes

Oracle recommends reading the Oracle Developer Suite release notes prior to installing. Oracle provides these release notes:
Oracle Developer Suite 10g (9.0.4) Release Notes for Windows, Linux, Solaris, and HP-UX contains product-level and component-level release notes for Windows and for Linux, Solaris, and HP-UX platforms. This manual is available in the Oracle Developer Suite Documentation Library. To display the manual, see Section C.3.1, "Viewing the Release Notes from Disk". The manual is also available on Oracle Technology Network (http://otn.oracle.com). Oracle Developer Suite 10g (9.0.4) Release Notes for Windows, Linux, Solaris, and HP-UX is also updated regularly and posted on the Oracle Technology Network (http://otn.oracle.com). Your platform-specific documentation may include release notes for your platform. Platform-specific release notes are also available on Oracle Technology Network (http://otn.oracle.com).
E.2 Troubleshooting the Installation

If you encounter an error while installing Oracle Developer Suite, follow these steps:
Do not exit the installer. You can find the installation log files more easily if you leave the installer running. Incorrect Information: If you think you have entered incorrect information on one of the installation screens, return to that screen by clicking Back until you see the screen, correct the information, then proceed with your installation. Copy or Link Errors: If the installer reports an error while copying or linking files, do the following:
1.
Note the error, then review the installation logs for causes. The installation logs are in your Oracle inventory directory in the subdirectory \logs (for Windows) or /logs (for Linux, Solaris, and HP-UX) and have the following filenames: For Windows: oracle_inventory\logs\installActionstimestamp.log oracle_inventory\logs\oraInstalltimestamp.err oracle_inventory\logs\oraInstalltimestamp.out
For Linux, Solaris, and HP-UX: oracle_inventory/logs/installActionstimestamp.log oracle_inventory/logs/oraInstalltimestamp.err oracle_inventory/logs/oraInstalltimestamp.out
The string timestamp is a value that the installer adds to the filename at the start of the installation. The form of timestamp is yyyy-mm-dd_ hh-mm-ss[AM|PM] where: yyyy is the current year, for example 2003 mm is the current month number, for example 07 for July dd is the current day number, for example 15 for the fifteenth
E-2 Installation Guide
Troubleshooting Oracle Developer Suite Configuration Assistants
hh, mm, and ss are the hour, minute, and second at which the installation started [AM/PM] is either AM or PM, depending on when the installation started
The location of the oracle_inventory directory is specified during the first installation of an Oracle product on your computer. To learn more about the directory and how to find it, refer to Section 2.7, "Directories Used by the Installer".
2. 3. 4.
Remove the failed installation by following the instructions in Chapter 4, "Deinstallation and Reinstallation". Correct the problem that caused the error. Start the Oracle Developer Suite installation again.
E.3 Troubleshooting Oracle Developer Suite Configuration Assistants

To troubleshoot an installation error that occurs when the configuration assistants are running:
Review the installation log files listed in Section E.2, "Troubleshooting the Installation". Review the configuration assistant log files located in the oracle_ home/cfgtoollogs directory for a specific Oracle Developer Suite configuration assistant. Table E2 also lists any other log file locations for a specific configuration assistant. Try to fix the issue that caused the error. If you see a "Fatal Error. Reinstall" message, try to find the cause of the problem by analyzing the log files. Refer to Section E.3.3, "Handling Fatal Errors" for further instructions.
E.3.1 Determining Configuration Assistant Execution Status

Oracle Developer Suite configuration assistant failures are noted at the bottom of the installation screen. The configuration assistant interface displays additional information, if applicable. The configuration assistants execution status will be identified by the result. The result codes are listed in Table E1:
Table E1 Status
Configuration Assistant Result Codes Result Code 0 1 -1
Configuration Assistant Succeeded Configuration Assistant Failed Configuration Assistant Cancelled
This result code is written to the following log file: oraInventory/logs/installActionstimestamp.log
Troubleshooting
E-3
E.3.2 Fixing Configuration Assistant Failures

During installation, configuration assistants run when the Configuration Assistants screen appears. If a configuration assistant fails, try the following procedure to correct the problem:
1. 2.
Review the installation log files for this installation session. Review the log files for each configuration assistant located in the oracle_home/cfgtoollogs directory. Default log file locations are described in Table E2. Refer to the section describing the configuration assistants in Table E2:
a.
3.
If the failing configuration assistant has any dependencies, then run the dependencies again. You must do this even if the dependency completed successfully. If an optional configuration assistant fails, and it does not have any dependencies, run the remaining configuration assistants. Uncheck the cancelled optional configuration assistant, highlight and check the next listed configuration assistant, and click Retry. Run the failing configuration assistant again. If you are using the installer, select the configuration assistant and click Retry.
Note: If the description of a configuration assistant in Table E2
b.
c.
includes an "Initial Tasks" section, you must perform these tasks before running the configuration assistant.
E.3.3 Handling Fatal Errors

Some configuration assistant failures are fatal errors. You cannot recover from a fatal error by correcting the problem and continuing. You must remove the current installation and reinstall Oracle Developer Suite. The following tasks describe the recovery procedure:
1. 2. 3. 4.
Deinstall the failed installation using the procedure described in Section 4.1, "Deinstallation". Correct the cause of the fatal error. Reinstall Oracle Developer Suite. If the fatal error reoccurs, then you must remove all Oracle installations from your computer using the procedure in Section Section 4.1.1, "Deinstalling Using the Installer".
E.3.4 Oracle Developer Suite Configuration Assistant Descriptions

Table E2 lists the configuration assistants that run during Oracle Developer Suite installation. Different installation types may use different configuration assistants.
Note: Some configuration assistants run in silent mode, which
means that their UI is not visible while they are running.
Table E2
Oracle Developer Suite Configuration Assistant Descriptions Description The Oracle Net Configuration Assistant configures the database listener and configures the mid-tier Oracle Application Server instances to use LDAP naming by default. Log File Location STDOUT/STDERR (all messages appear in the installer window)
Configuration Assistant Oracle Net Configuration Assistant
Troubleshooting
E-5
Index
A
Access Bridge installing, 2-13, 3-10 setting up for JDeveloper, 3-17 assistive technologies, 2-13, 3-10 DISPLAY environment variable, documentation online, C-1 product help, 3-25 Documentation Library installing, C-2 titles, C-1 viewing, C-4 2-14
B
Bali, B-5 BI Beans. See Oracle BI Beans browser requirements documentation, 2-9
E
End User Layer upgrading, A-8 environment variables list of, 2-14 setting in Linux, Solaris, and HP-UX, error installation (see troubleshooting) Windows System Files, 2-20 EUL upgrading, A-8 extensions. See JDeveloper extensions
C
Cabo, A-5, B-5 Catalog, BI Beans, 3-19 certified software, 2-8 CLASSPATH environment variable, 2-12 coexistence database, 2-9 Oracle Application Server, 2-9 Oracle home, 2-9 previous versions, 2-9 Release 9.0.2, 2-9 compatibility. See coexistence components installed with Linux, Solaris, or HP-UX. See installable components components installed with Windows. See installable components configuration tools Oracle Network Configuration Assistant, 3-6, E-5
2-14
F
font.properties, 3-12 fonts additional languages, 3-8 problems in Linux, Solaris, and HP-UX,
3-12
G
group names, 2-15
H
hardware requirements CPU, 2-1 disk space, 2-1 memory, 2-1, 2-2 pagefile size, 2-1 swap space, 2-1 TMP space, 2-1 video, 2-1 hosted documentation, JDeveloper, 3-13 HP HP-UX operating environment. See HP HP-UX operating system HP HP-UX operating system
D
database requirements BI Beans, 3-17 deinstallation, 4-1 deploying Forms, 3-22 Reports, 3-20 supported environments BI Beans, B-3 JDeveloper, B-2 deployment requirements BI Beans, B-3
Index-1
Java SDK requirements, 1-4, 2-12 patchset requirements, 2-6 version requirements, 2-6 HP HP-UX operating system, font problems, 3-12 HTTP Listener, 3-9
I
installable components Linux, Solaris, HP-UX, 1-2 Windows, 1-2 installation Documentation Library, C-2 information needed during, 2-17 language, 3-4 non-interactive, 1-5, D-2 process, general, 1-2 product, instructions, 3-1 product, overview, 1-1 response files, D-3 silent, 1-5, D-1 troubleshooting, E-2, E-3 Windows System Files, 2-20 inventory directory, 2-19
migrating Oracle BI Beans, A-3 Oracle Designer, A-9 Oracle Discoverer Administrator, A-8 Oracle Forms Developer, A-8 Oracle Reports Developer, A-7 Oracle SCM, A-8 Oracle9i JDeveloper, A-2 mounting CD-ROMs HP-UX, 2-22 Linux, 2-23 Solaris, 2-21 mounting DVDs Solaris, 2-21
N
Net Services, 3-9 Network Configuration Assistant, 3-6, E-5 NLS_LANG environment variable, 3-8 non-interactive installation. See installation, non-interactive
O
OC4J for Forms Developer port numbers, 3-9 starting and stopping instance, 3-10 OC4J for JDeveloper non-embedded mode, 3-16 port numbers, 3-9 OC4J for Reports Developer port numbers, 3-9 starting and stopping instance, 3-10 OC4J listener, 3-4 online documentation installing, C-1 requirements, 2-9 operating systems and Developer Suite components, 2-3 software requirements, 2-4 Oracle account properties, 2-16 Oracle BI Beans Catalog, 3-19 database requirements, 3-17 database upgrade, 3-19 deployment requirements, B-3 description, B-3 JDBC drivers, 3-19 migrating, A-3 postinstallation tasks, 3-17 Oracle database compatibility. See coexistence, database Oracle Designer description, B-6 Oracle Developer Suite components, B-1 Oracle Developer Suite Documentation Library. See Documentation Library Oracle Discoverer Administrator description, B-5
J
Java Access Bridge installing, 2-13, 3-10 setting up for JDeveloper, 3-17 Java Object support, 3-21 JDBC drivers, BI Beans, 3-19 JDBC OCI driver, 3-19 JDeveloper extensions downloading, 3-11 enabling, 3-11 installing, 3-11 JDK, 2-13, 3-10 JMS, 3-9 JRE, 2-13, 3-10
L
language component runtime, 3-8 fonts, 3-8 selecting, 3-4 LD_LIBRARY_PATH environment variable, 2-12 Linux operating environment patchset requirements, 2-8 version requirements, 2-8 Linux operating system, font problems, 3-12 listener, OC4J, 3-4 locale, setting for Oracle Universal Installer, 2-12
M
mail server, 3-5 memory requirements, 2-1, 2-2 Merant JDBC drivers, 3-20 Microsoft Windows,requirements,
2-4
Index-2
postinstallation tasks, 3-21 Oracle Express Server, 3-20 Oracle Forms Developer description, B-6 postinstallation tasks, 3-21 Oracle home coexistence, 2-9 directory, 2-9 setting, 2-14 unsetting, 2-14 Oracle Network Configuration Assistant, 3-6, E-5 Oracle Reports Developer description, B-5 postinstallation tasks, 3-20 Oracle SCM description, B-6 postinstallation tasks, 3-22 preinstallation tasks, 2-16 Oracle Universal Installer, 2-17 starting (Linux, Solaris, and HP-UX), 2-21 starting (Windows), 2-20 ORACLE_HOME environment variable, 2-14 (See also Oracle home) Oracle9i JDeveloper description, B-1 hosting documentation, 3-13 multiuser environment, 3-13 OC4J in non-embedded mode, 3-16 postinstallation tasks, 3-11 OracleAS Containers for J2EE, 3-4 OracleAS Forms Services, 3-4 OracleAS Portal integration, 3-20 OracleAS Reports Services installing, 3-4 starting and stopping, 3-20 oraInventory directory, 2-19
prerequisite checks, 1-4, 2-18 processor requirements. <italic>See hardware requirements
R
reinstallation, 4-3 release notes, viewing from CD-ROM, C-4 Reports Server configuration file, 3-20 repository, 3-22 Repository Administration Utility, 3-12 requirements CPU. (see hardware requirements hardware. (see hardware requirements) online documentation, 2-9 operating system software (see software requirements) response files, working with, D-3 RMI, 3-9 runtime services, 3-4
S
SHLIB_PATH environment variable, 2-12 silent installation. See installation,silent software requirements, operating systems, 2-4 Solaris operating environment. See Solaris operating system Solaris operating system installed Oracle Developer Suite components, 2-3 package requirements, 2-6 patchset requirements, 2-4 Solaris 6 and 7 support, 1-4 Solaris operating system, font problems, 3-12 source code control, 3-12, 3-21 sqlnet.ora, 3-9 startinst.bat, 3-10 startinst.sh, 3-10 stopinst.bat, 3-10 stopinst.sh, 3-10 stored Java objects, 3-21 Sun Solaris operating environment. See Solaris operating system supported operating environments, 2-3 system files error (Windows), 2-20
P
package requirements HP HP-UX, 2-6 Linux, 2-8 Solaris, 2-6 patchset requirements HP HP-UX, 2-6 Linux, 2-8 Solaris, 2-4 PATH environment variable, 2-12 pkginfo command, 2-5 port numbers, 3-9 portlist.ini file, 3-9 postinstallation tasks, 3-7 Oracle BI Beans, 3-17 Oracle Discoverer Administrator, Oracle Forms Developer, 3-21 Oracle Reports Developer, 3-20 Oracle SCM, 3-22 Oracle9i JDeveloper, 3-11 preinstallation tasks, 2-11 Oracle SCM, 2-16
T
temp directory setting, 2-15 space requirements, 2-2 Terminal Server clients configuring for JDeveloper, 3-14 titles, Documentation Library, C-1 TMP environment variable, setting, 2-15 TNS_ADMIN environment variable, 2-15 tnsnames.ora, 3-9 troubleshooting, E-2, E-3
3-21
Index-3
U
UIX, B-5 UNIX account. See user UNIX groups. See group names UNIX. See specific platform upgrading (see also migration) 6i repository, A-8 End User Layer, A-8 user, creating, 2-16
V
var/opt directory, 3-3 version requirements HP HP-UX, 2-6 Linux, 2-8 Solaris, 2-4 video requirements, 2-2
W
Windows operating system and Developer Suite components, 2-3 requirements, 2-4 Windows System Files installation, 2-20
Index-4

Installation Developer Suite 10g

Uploaded by

Copyright:

Available Formats

Installation Developer Suite 10g

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Installation Developer Suite 10g

Uploaded by

Copyright:

Available Formats

Oracle Developer Suite

Deinstallation and Reinstallation

A.6 A.7 A.8 A.9

A-8 A-8 A-9 A-9

Installing the Documentation Library

Silent and Non-Interactive Install

Send Us Your Comments

Intended Audience Documentation Accessibility Structure Related Documents Conventions

Accessibility of Links to External Web Sites in Documentation This documentation

You can purchase printed documentation in the Oracle Store at http://oraclestore.oracle.com/

[] boldface text Italics code (lowercase monospace or fixed-width font)

1.1 Oracle Developer Suite Installation Overview

About the Installation Process

YES YES YES

YES YES YES

1.2 About the Installation Process

Whats New in the Installation

1.3 About Installing Oracle Developer Suite Components

1.4 Whats New in the Installation

Whats New in the Installation

1.4.1 Installation from DVD is Now Available

1.4.2 Solaris 6 and 7 No Longer Supported

1.4.3 SuSE SLES-7 No Longer Supported

1.4.4 New Operating System Patches Required

1.4.6 More Prerequisite Checks

Whats New in the Installation

1.4.7 Configuration Assistant Enhancements

1.4.8 Removed Restrictions

Whats New in the Installation

2.1 Hardware Requirements

Hardware Item CPU

Business Intelligence (Windows only)

Rapid Application Development (Windows only)

Total Pagefile Size, TMP, or Swap Space4 Video

The computer must be capable of displaying a minimum of 256 colors.

Oracle Discoverer Administrator

Oracle Discoverer Desktop Oracle Forms Developer

Minimum: 128 MB Recommended: 256 MB

Oracle Software Configuration Manager Oracle Designer

Operating Environments Supported

2.2 Operating Environments Supported

YES YES YES

Linux, Solaris, and HP-UX Notes:

Solaris/CDE HP-UX/CDE HP-UX/VUE Linux/GNOME Linux/KDE2

Operating Environment Software Requirements

2.3 Operating Environment Software Requirements

2.3.1 Windows Operating Environment

Software Item Windows Operating Environment

Note: Newer versions of Windows allow you to use a system

2.3.2 Solaris Operating Environment for Sun SPARC workstations

Operating Environment Software Requirements

Solaris Operating Environment Patchset Requirements Requirement

Software Item Solaris 8 (2.8)

Operating Environment Software Requirements

Solaris Operating Environment Package Requirements Requirement

Software Item Solaris 8 (2.8)

2.3.3 HP-UX Operating Environment

Software Item HP-UX Operating Environment

HP PA-RISC HP-UX 11.00 (64-bit) HP PA-RISC HP-UX 11.11 (64-bit)

Operating Environment Software Requirements