Skip Headers

Oracle9i Developer Suite Installation Guide
Release 2 (9.0.2) for Windows and UNIX

Part Number A95828-02
HomeSolution Area
Go To Table Of Contents
Contents
Go To Index
Index

Go to previous page Go to next page

3
Installation

Before proceeding with the installation instructions in this chapter, 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:

3.1 Installing Oracle9i Developer Suite

Oracle Universal Installer displays in the language as specified in the current locale. For instructions on starting the installer, see Section 2.8.2, "Starting Oracle Universal 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.8.2.1.1, "Windows System Files Installation".


Once Oracle Universal Installer is launched, the Welcome screen appears.

  1. Review the Oracle Universal Installer Welcome screen and click Next.

    Figure 3-1 Welcome Screen

    Text description of welcome.gif follows.

    Text description of the illustration welcome.gif

    The Welcome screen provides information about the Oracle Universal Installer.

    The following function buttons appear on the Welcome screen and all installation screens that follow it.

    • Exit: Quit the installation process and exit the installer.

    • Help: Access detailed information about the functionality of each screen.

    • Installed Products: View currently installed products and deinstall products.

    • Previous: Return to the previous screen.

    • Next: Move to the next screen.

    The Welcome screen has two additional buttons. They are:

    • Deinstall Products: Deinstall individual products or all products.

    • About Oracle Universal Installer: View the version number of the installer in use.

  2. (First time installation) At the Inventory Location screen, verify the location of the base directory for installation files. Then click OK to continue.

    Figure 3-2 Inventory Location Screen

    Text description of invenloc.gif follows.

    Text description of the illustration invenloc.gif

    The Inventory Location screen appears only during the first time installation is performed on the machine. The screen lets you set up the base directory for installation files. You can accept the default value or enter another value.

    The base directory contains the permanent and per-product files in subdirectories, and must be writable by anyone installing or deinstalling products on the computer.

    • For Windows, the default base directory is C:\Program Files\Oracle\Inventory. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., C:\Program Files\Oracle\Inventory\Components.

    • For UNIX, enter the location for the base directory, e.g., /private1. The per-product installation files will automatically be stored in a subdirectory of the base directory, e.g., /private1/Components.

    • Browse: To navigate through the file system to select a location for the base directory, use the Browse button.

  3. For UNIX only: (First time installation) At the UNIX Group Name screen, enter a UNIX group name and click Next.

    Figure 3-3 UNIX Group Name Screen

    Text description of unixa.gif follows.

    Text description of the illustration unixa.gif

    The UNIX Group Name screen appears only on the first time you run Oracle Universal Installer on the machine. The UNIX Group Name screen grants permission for the oraInventory directory to the group specified. For more information, refer to Section 2.7.6, "Creating UNIX Accounts and Groups".

    • Unix Group Name: Enter a UNIX group name for those who have permission to configure the Oracle9iDS install. Verify your group name by entering this command from the UNIX prompt the installer was launched from:

      prompt> id

    • Certain actions with root privileges require execution before the install can continue. You need to run a shell script with root privileges that is stored in the orainstRoot.sh file. (You may need to execute the shell script by typing "./" before orainstRoot.sh). The Root.sh installation screen shows the location of the orainstRoot.sh file. The script creates pointers to the components as the installer installs them in the system so that they can be identified later in the installation procedure. It produces the /var/opt/oracle/oraInst.loc file, which provides a pointer to the oraInventory directory.

    Following execution of the Bourne shell script, continue with the installation process.

  4. At the File Locations screen, verify the source and destination paths and enter or select an Oracle Home name. Then click Next to continue.

    Figure 3-4 File Locations Screen

    Text description of filelocs.gif follows.

    Text description of the illustration filelocs.gif

    The File Locations screen lets you enter the full path for the source and destination locations for your installation.

    Do not install Oracle9iDS into an existing:

    • Oracle Internet Developer Suite home directory (former version of Oracle9iDS)

    • Oracle Database home directory (including Oracle8i and Oracle9i)

    Do not install Oracle9iDS into an existing Oracle9iDS home directory unless you are selecting another installation type or performing an install upgrade.

    For more information about Oracle Homes, see Section 2.6, "Coexistence".

  5. At the Installation Types screen, select the type of installation you want to perform and the product languages to install. Then click Next to continue.

    Figure 3-5 Installation Types Screen (Windows)

    Text description of installt.gif follows.

    Text description of the illustration installt.gif

    The Installation Types screen lets you select the type of installation you want to perform and the product languages to install.

    The available install options are:

    • J2EE Development: Select this option to install Oracle9i JDeveloper and its subcomponents (Oracle9i Business Intelligence Beans, UIX, Bali, and XDK), and Oracle9iAS Containers for J2EE (OC4J). This option configures OC4J as the default listener for testing purposes.

    • Business Intelligence: (Windows only) Select this option to install Oracle9Warehouse Builder, Oracle9i Discoverer Administrator (including Oracle9i Discoverer Desktop), Oracle9i Clickstream Intelligence Builder, and Oracle9i Reports Developer. This option also installs OC4J and Oracle9iAS Reports Services, and configures OC4J as the default listener for testing purposes.

    • Rapid Application Development: (Windows only) Select this option to install Oracle9i Forms Developer, Oracle9i Designer, Oracle9i Software Configuration Manager, Oracle9i Reports Developer, and Oracle9i JDeveloper. This option also installs OC4J, Oracle9iAS Reports Services, and Oracle9iAS Forms Services, and configures OC4J as the default listener for testing purposes.

    • Complete: Select this option to install all Oracle9iDS components. Not all components are available on UNIX. See Table 2-3, "Operating Environments and Oracle9iDS Components" for the Oracle9iDS components that are installed on UNIX.

    Product Languages: To select the languages your installed product will run in, click the Product Languages button to display the Languages Selection screen. You can install multiple product languages and thus switch between product runtime language user interfaces by changing the NLS_LANG environment variable. During product runtime, if the translation files for the language are available and the installed language files are correctly mapped to each other, the product will run in the current locale, otherwise the product will run in English.

  6. At the Languages Selection screen, select the languages you want the installed product to run in. Then click OK to continue.

    Figure 3-6 Language Selection Screen

    Text description of langsele.gif follows.

    Text description of the illustration langsele.gif

    The Language Selection screen lets you select multiple languages to be installed.

    • Available Languages: Displays the languages available for selection. Click the language you want to install. You can select more than one language. After making your selections, click the > or >> button to move the selected languages to the Selected Languages list on the right. Note that selecting languages here does not affect the language of the installation program itself.

    • Selected Languages: Displays the languages you have selected for installation. The default is English and the current locale language. To deselect a language, click the language and click the < or << button to move the selected language back to the Available Languages list on the left.

  7. At the Provide Outgoing Mail Server Information screen, enter a name for the outgoing mail server. Then click Next to continue.

    Figure 3-7 Provide Outgoing Mail Server Information Screen

    Text description of outmails.gif follows.

    Text description of the illustration outmails.gif

    If you intend to generate Oracle Reports from within Oracle9i Designer, you must provide an outgoing mail server name.

    The Provide Outgoing Mail Server Information screen appears only if you selected the Business Intelligence, Rapid Application Development, or Complete install option. This screen lets you enter a name for the outgoing mail server that is to be used by Oracle9iAS Reports Services to distribute reports via e-mail, e.g., mysmtp01.mycorp.com. This mail server will also be used by Oracle9iAS Reports Services to send job success notifications when requested by users.

  8. Verify the information in the Summary screen and click Install to begin installing the files.

    Figure 3-8 Example of a Summary Screen

    Text description of sumj2ee.gif follows.

    Text description of the illustration sumj2ee.gif

    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 Previous to return to the appropriate screen.


    Note:

    Insufficient disk space is indicated in red under Space Requirements.


  9. The Install screen displays and the installer begins copying the required files for Oracle9iDS. Monitor the progress of the installation.

    Figure 3-9 Example of an Install Screen

    Text description of instal1.gif follows.

    Text description of the illustration instal1.gif

    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.

    • See the full path of the installation log. For more information about the installation log, see Section 2.8.1, "Inventory Directory".

    • Click Cancel 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.

  10. The Configuration Tools screen appears only for the Business Intelligence, Rapid Application Development, and Complete installation types.

    Figure 3-10 Configuration Tools Screen

    Text description of cfg_tool.gif follows.

    Text description of the illustration cfg_tool.gif

    The Configuration Tools screen appears while the Oracle Net Configuration Assistant is running. It configures basic network components and creates the tnsnames.ora and sqlnet.ora files for you. The Oracle Net Configuration Assistant tool is automatically started by the installer. Click Help on the Oracle Net Configuration Assistant Welcome screen if you need information on how to use the tool.

    At the Configuration Tools 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:

    1. Press ALT-F4 to cancel the Net Configuration Assistant, then exit the installer. This does not affect the Oracle9iDS installation; it only stops the Net Configuration Assistant tool.

    2. Install Java Access Bridge 1.0.2 into the JRE 1.1.8 location on your computer. See Section 2.7.4, "Installing Java Access Bridge (Windows only)" for information on downloading and installing Java Access Bridge 1.0.2.

    3. Set the following environment variable if it has not been set.

      ORACLE_OEM_CLASSPATH=<drive_letter>:\Program Files\Oracle\jre\1.1.8\lib\access-bridge.jar;<drive_letter>:\Program Files\Oracle\jre\1.1.8\lib\jaccess.jar

      where <drive_letter> is C, D, or wherever the Program Files directory is located on your PC.

    4. Restart your screen reader.

    5. Restart the Net Configuration Assistant tool on the Windows Start Menu as follows:

      Start > Programs > Oracle -IDSHome > Configuration and Migration Tools > Net Configuration Assistant

  11. For UNIX only: Running root.sh

    After copying the required files, the installer prompts you to run the root.sh script. Use the following steps to run the root.sh script.

    1. Log on as the root user.

    2. Run the root.sh script in the Oracle Home directory.

      prompt> $ORACLE_HOME/root.sh

    3. Exit root user.

    Once you see "Finished running generic part of the root.sh script" and "Now product-specific root actions will be performed", exit root user and return to the Install screen.

    The root.sh script detects:

    • Settings of ORACLE_OWNER, ORACLE_HOME and ORACLE_SID environment variables.

    • Full path of local bin directory. You can accept the default or change to a different local bin directory.

  12. After installing the product, the installer displays the End of Installation screen.

    Figure 3-11 End of Installation Screen

    Text description of endinst.gif follows.

    Text description of the illustration endinst.gif

    The End of Installation screen appears at the end of the installation process. It indicates whether the installation is successful or unsuccessful.

    • Exit: 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.

    • Next Install: To continue with the installation program, click Next Install.

    After successfully installing the product, proceed to Section 3.2, "Postinstallation Tasks" for further instructions.

3.2 Postinstallation Tasks

The postinstallation tasks for Oracle9iDS are divided into the following parts:

3.2.1 General Checklist

Review the general postinstallation checklist and perform any required tasks.

3.2.1.1 NLS

Depending on the product languages selected during installation, the required translation files are installed for each component. To change the component runtime language, set NLS_LANG to the appropriate language.

NLS_LANG determines the environmental values for the language, territory dependent conventions, and character set to be used during product runtime. NLS_LANG consists of three parameters:

For example

sets the NLS environmental values so that components run in Japanese, use Japanese cultural conventions, and use the EUC character set for data manipulation.

Refer to the Oracle9i Application Server Globalization Support Guide (included in the Oracle9i Application Server Documentation Library) for more details about NLS_LANG values.

3.2.1.2 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 (UNIX). 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 your database documentation library--Oracle9i Net Services Administrator's Guide or Net8 Administrator's Guide.

3.2.1.3 Port Numbers

Following installation, the Oracle Universal Installer creates a file showing the port assignments during installation of Oracle9iDS components. The installation process automatically detects any port conflicts and chooses an alternate port in the range allocated for that component.

The file portlist.ini is located in the %ORACLE_HOME%\install directory (Windows) or $ORACLE_HOME/install directory (UNIX). 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 3-1 lists the default port numbers that the Oracle Universal Installer uses for select components during installation.

Table 3-1 Port Numbers
Components Default Port Number Port Number Range

OC4J for JDeveloper testing

  • HTTP Listener

  • RMI

  • JMS

8988

23891

9227

8988 - 8998

23891-23901

9227 - 9237

OC4J for Forms Developer and Reports Developer testing

  • HTTP Listener

8888

none

3.2.1.4 OC4J Instance for Oracle9iDS

3.2.1.5 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 Oracle9iDS must have Sun's Java Access Bridge installed in all the Java virtual machine locations on the computer.

The Oracle Universal Installer for Oracle9iDS has installed files for JDK/JRE 1.1.8 and JDK/JRE 1.3 on your computer, but it has installed Java Access Bridge 1.0.2 files in the JDK/JRE 1.3 location only.

For assistive technologies to work with Oracle9iDS 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.7.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.7.4, "Installing Java Access Bridge (Windows only)" for more information.)

  1. Confirm that the jar files: access-bridge.jar and jaccess.jar are added to the folders Program Files\Oracle\jre\1.1.8\lib and Program Files\Oracle\jre\1.3.1\lib\ext.

  2. Confirm that two DLL files: JavaAccessBridge.dll and WindowsAccessBridge.dll are added to the folder Winnt\System32 as they must be in the system path.

  3. Confirm 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 to the folder.

  4. Confirm 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 to the folder.

  5. Confirm that the PATH environment variable has been updated to include the directory where the DLL files are installed, %ORACLE_HOME%\jdk\jre\lib\ext.

  6. Confirm 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=<drive_letter>:\Program Files\Oracle\jre\1.1.8\lib\access-bridge.jar;<drive_letter>:\Program Files\Oracle\jre\1.1.8\lib\jaccess.jar

  7. Confirm that the file accessibility.properties in the folders %ORACLE_HOME%\jdk\jre\lib and Program Files\Oracle\jre\1.3.1\lib includes the following line:

    assistive_technologies=com.sun.java.accessibility.AccessBridge

    If necessary, copy the file from <accessbridge_home>\installer\installerFiles to the appropriate folders.

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 Enabling WebDAV Support in JDeveloper

Before you can use WebDAV support in JDeveloper, you first need to download the WebDAV addin for JDeveloper from OTN. The WebDAV addin download includes IBM's DAV4J driver.

To download the WebDAV Addin for JDeveloper:

  1. Go to http://otn.oracle.com/software/products/jdev/content.html.

  2. Click the WebDAV Addin for JDeveloper link in the section on Oracle9i JDeveloper Downloads.

  3. Follow the remaining instructions and click jdev9iWebDAV.zip.

To install the WebDAV Addin for JDeveloper:

  1. Shutdown any instances of JDeveloper that are currently running on your machine.

  2. Unzip the downloaded jdev9iWebDAV.zip file to a temporary directory.

  3. Locate the directory in which JDeveloper is installed.

  4. Copy dav4j.jar, dav4j_license.htm, jdwebdav.jar and xml4j.jar into the %ORACLE_HOME%\jdev\lib\ext directory (Windows) or $ORACLE_HOME/jdev/lib/ext directory (UNIX).

When you next start JDeveloper, you will be able to create and use WebDAV connections.

For information about using WebDAV support in JDeveloper, see the JDeveloper online help.

3.2.2.1.2 Enabling Source Code Control (Windows only)

A connection to an Oracle9i Software Configuration Manager (SCM) repository is required to perform source code control using SCM from JDeveloper. The repository resides within an Oracle database and must be precreated. Install the Rapid Application Development option, then use the Repository Administration Utility in SCM to create the repository in the database. For instructions on creating the repository, see the Oracle SCM Repository Installation Guide (available on the Oracle9i Developer Suite Product CD).

3.2.2.1.3 Font Problems on UNIX Computers

If you see an error similar to:

when starting JDeveloper on a Unix computer, your JDK isn't set up to use the mentioned font. JDeveloper, by default, uses the information in the file font.properties included with each JDK. If this file references fonts not available on your computer, you will see the above error (or one like it). To fix this error, you'll 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.2.2.1.4 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 the first launch of the hosted help system 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:

Once you have done that, your users will have to set their copy of JDeveloper to use your new server. In the IDE Settings dialog, navigate to "Documentation". Ensure that "Use Hosted Documentation" radio button is selected. Provide the URL to the jdeveloper.hs file on your server.

3.2.2.1.5 Using JDeveloper in a Terminal Server/Multiuser Environment

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 installing and configuring JDeveloper for a multiuser environment, you'll need to account for the resource planning, such as number of users and power of the server, to deliver optimal performance for JDeveloper and your users.

Installing JDeveloper on a Citrix WinFrame Server or a Microsoft Terminal Server

You need to have administrative privileges to install JDeveloper.

Configuring User Home Directories in a Multiuser Environment

(The following information is written for Windows, but the logic applies to UNIX as well.)

Before you run JDeveloper in a terminal server environment, you must define the user home environment variable and set its value for each user in order for JDeveloper to identify user home directories correctly. If the variable is not defined and set, JDeveloper uses the ORACLE_HOME\jdev as the home directory for all users. Using this directory may cause unstable behavior in JDeveloper with multiple users.

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.

3.2.2.1.6 Using OC4J in non-embedded mode with JDeveloper

Included with the J2EE Development installation is a fully functioning version of Oracle9i Application Server Containers for J2EE (OC4J). If you are using JDeveloper to test your applications, you will be using the embedded version of OC4J and you will 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 an admin password and press Enter.

    You will be prompted to confirm the password.

  3. Confirm the password by typing it again and press Enter.

Installation will be complete.

You can now start the server.

To start the OC4J server for use in non-embedded mode:

For more information on fine tuning your OC4J server instance, see the OC4J documentation in the Oracle9i 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.2.2.1.7 Using Assistive Technologies with JDeveloper (Windows only)

First, follow the steps in Section 3.2.1.5, "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. Confirm that two DLL files: JavaAccessBridge.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.

  2. Modify the file jdev.conf located in the folder %ORACLE_HOME%\jdev\bin to uncomment the AddVMOption line as shown below:

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

  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. Start your screen reader.

  5. Start JDeveloper.

The steps above 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 Oracle9i Business Intelligence (BI) Beans

3.2.2.3 Oracle9i Reports Developer

3.2.2.4 Oracle9i Discoverer Administrator

3.2.2.5 Oracle9i Warehouse Builder

3.2.2.6 Oracle9i Clickstream Intelligence Builder

The following instructions assume you have installed the Business Intelligence and Forms option of Oracle9i Application Server Release 2 (9.0.2), which means the two Clickstream schemas (clkrt and clkana) already exist in a database.

3.2.2.7 Oracle9i Forms Developer

3.2.2.8 Oracle9i Software Configuration Manager (formerly Oracle Repository)

3.2.2.9 Oracle9i Designer

3.2.3 Additional Documentation

All components have online help that is installed with the product. Some components provide additional documentation that is available on the Oracle9i Developer Suite Documentation Library CD-ROM. For information on viewing and installing the Oracle9i 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 on the documentation library CD-ROM.

For Windows users, you can access release notes and Getting Started information from the Start Menu as follows:

Start > Programs > Oracle9i Developer Suite - ORACLE_HOME > Release Notes

Start > Programs > Oracle9i Developer Suite - ORACLE_HOME > Documentation > Getting Started

Alternatively, you can point your browser to the file <ORACLE_HOME>/doc/ids902welcome/index.htm.

For documentation updates, white papers, or other collateral, please visit the Oracle Technology Network at

http://otn.oracle.com


Go to previous page Go to next page
Oracle
Copyright © 2002 Oracle Corporation.

All Rights Reserved.
HomeSolution Area
Go To Table Of Contents
Contents
Go To Index
Index