5
Enterprise Edition

This chapter guides you through the installation steps for the Enterprise Edition of Oracle9i Application Server. The following topics provide detailed installation steps, and basic postinstallation tasks:

• Installation

• Postinstallation

Installation

The following instructions guide you through the Enterprise Edition installation option of Oracle9i Application Server.

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

   Figure 5-1 Welcome Screen

   
   
   Text description of the illustration wel.gif

   The Welcome screen provides information about the Oracle Universal Installer.

   The following function buttons appear on the installation screens.

   • Deinstall Products: Deinstall individual components or the entire product. This button appears only on the Welcome screen.

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

   • 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 or to deinstall the entire product or components.

   • Previous: Return to the previous screen.

   • Next: Move to the next screen.

2. Verify the source and destination paths and click Next. If you have not previously installed Oracle products on your machine, the "OraInventory Location screen" appears after you click Next. Enter the complete location path for oraInventory directory and click OK.

   Figure 5-2 File Locations Screen

   
   
   Text description of the illustration filloc.gif

   The File Locations screen allows you to enter the full path for the source and destination locations of Oracle9i Application Server.

   • 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 full path to the Oracle home where the product will be installed. The installer defaults to the Oracle home set in the preinstallation chapter.

     Note: Oracle home path must be a real, absolute path. It cannot contain symbolic links, environment variables, or spaces.

     For more information regarding Oracle home, refer to "ORACLE_HOME".

   • Browse: To navigate through the file system to find source and destination locations.

3. This screen appears only the first time you run Oracle Universal Installer on your machine.Take note of the default value if it appears. Enter a UNIX group name and click Next.

   Figure 5-3 UNIX Group Name Screen

   
   
   Text description of the illustration grpnm.gif

   The UNIX Group Name screen grants permission for the oraInventory directory to the group specified. For more information, refer to "UNIX Group Name for the Oracle Universal Installer Inventory" .

   UNIX Group Name:

   • Enter a UNIX group name for those who have permission to configure all the functionality of Oracle9i Application Server. Verify your group name by entering this command from the UNIX prompt the installer was launched from:

     prompt> id
     
     

   • Run the orainstRoot.sh script from your Oracle home to grant permissions to the root user only. You must have root privileges to run this script. 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.

     After you have run the script, click Retry to continue.

4. Select Enterprise Edition and click Next.

   Figure 5-4 Installation Types Screen

   
   
   Text description of the illustration einstype.gif

   The Installation Types screen allows you to select the Oracle9i Application Server installation option that you are licensed to use.

   See Also: Table 2-1, "Oracle9i Application Server Components" for a complete list of components.

   • Minimal Edition: Installs Oracle9iAS Portal, Oracle9iAS Wireless, Oracle Enterprise Manager Client, and Oracle HTTP Server.

   • Standard Edition: Installs Oracle9iAS Portal, Oracle9iAS Wireless, Oracle Enterprise Java Engine, Oracle Enterprise Manager Client, Oracle HTTP Server, and Oracle Internet File System.

   • Enterprise Edition: Installs Oracle9iAS Database Cache, Oracle9iAS Discoverer, Oracle9iAS Forms Services, Oracle9iAS Portal, Oracle9iAS Reports Services, Oracle9iAS Web Cache, Oracle9iAS Wireless, Oracle Enterprise Java Engine, Oracle Enterprise Manager Client, Oracle HTTP Server, Oracle Internet File System, and Oracle Management Server.

5. This screen appears only if Oracle Universal Installer has detected insufficient disk space in the Oracle home directory. If needed, verify and change the locations of the components displayed on the screen, and click Next.

   Figure 5-5 Component Locations Screen

   
   
   Text description of the illustration entcploc.gif

   The Component Locations screen allows you to select alternative locations for some components.

   Note: Insufficient disk space is indicated in red with a hand icon next to it.

   Show all components to be installed: To view the complete list of components chosen for installation. Select check box to display component list.

   Click individual components to view and change destination location path. The installer enables you to change the destination location of the components displayed on the screen.

   • Destination Location: To view the full path of the selected component.

   • Change Location: To browse for alternate locations for the selected component.

   • Available Disk Space: To view available disk space in the current directory. The installer also provides information about the total disk space required for the installation of additional components.

   • Required Disk Space for directory_name: To view the total disk space required for installation in the selected directory.

   • Total Required Disk Space: To view the total disk space required for the product to be installed.

   • Show all available volumes: To browse through file system for available disk space. Select check box to display the file system.

6. This screen appears if the installer detects insufficient TMP space. Remove unneeded files from the swap directory to provide sufficient space for installation and click Next. If your swap space is smaller than 500 MB, click Exit and correct the problem.

   Figure 5-6 Insufficient Space in TMP Screen

   
   
   Text description of the illustration tmpwarn.gif

   The Insufficient Space in TMP screen indicated inadequate space in the swap directory. You have two options:

   • If you have more than 500 MB swap space, then remove unneeded files from your swap space to create room for installation and click Next to proceed.

   • If you have less than 500 MB swap space, then Exit the installer and set TMP environment variable to point to a writable directory with sufficient space.

   For detailed information on TMP directory, refer to"TMP".

7. Click the Help button to verify that all the preinstallation tasks have been performed, and then click Next.

   Figure 5-7 Installation Overview Screen

   
   
   Text description of the illustration preinsta.gif

   The Installation Overview screen gives you an overview of the installation process. Click on the Help button for information on the installation process, preinstallation checklist, automatic process startup, configuration tools, and frequently asked questions.

8. Enter the location of the 8.0.6 RSF based products Oracle Home, and click Next.

   Figure 5-8 Destination Oracle Home for 8.0.6 RSF-Based Products

   
   
   Text description of the illustration filloc2.gif

   The Destination Oracle Home for 8.0.6 RSF-based Products screen enables you to enter the location to install the 8.0.6 RSF based products.

   • Select Oracle Home: Enter the location of the Oracle Home where you want to install the 8.0.6 RSF-based products.

   • Browse: To navigate through the file system to find source and destination locations.

     Note: Do not to install Oracle9i Application Server in an Oracle home containing other Oracle products, including the database. Such an installation could overwrite shared components, causing the products to malfunction. Also, do not use a 8.1.x Oracle home. For migration and upgrade issues, refer to the Oracle9i Application Server Migration Guide.

9. Select the components you wish to configure during the installation process and click Next. These components will automatically start up after installation. If you wish to configure the components later, do not select them.

   Figure 5-9 Component Configuration and Startup Screen

   
   
   Text description of the illustration startup.gif

   The Component Configuration and Startup screen allows you to select the components that you want the installer to configure and start after installation. This screen offers two configuration options:

   • If you select a component here, then the installer prompts you for any or all configuration information required by that component. After installation, the installer starts that component.

   • If you de-select a component here, then the installer installs it, but does not configure or start it. later on, if you decide to use that component, then manually launch the configuration assistant to configure that component.

     See Also: Appendix A, "Configuration Tools"

   You can select or de-select multiple components by holding down the Control key while clicking on the component name.

10. This screen will appear only if you selected Oracle9iAS Database Cache in the Component Configuration and Startup screen. Enter the host name, port number, and service name of the origin database and click Next.

    Figure 5-10 Origin Database Connection Information

    
    
    
    Text description of the illustration dbconn.gif

    The Origin Database Connection Information screen enables you to identify the origin database for the middle-tier cache.

    • Host Name: The name of the machine where the origin database is located.

    • Port Number: The port number of the listener for the origin database. The default port number is 1521.

    • Service Name: The database service name is the global database name. The global database name uniquely distinguishes the database from other databases in your network domain. The installation procedure uses this name to create an entry in the tnsnames.ora file on the local cache node.

      For example, if oasdocs is the database name and us.oracle.com is the network domain in which the database is located, then the service name is oasdocs.us.oracle.com.

11. This screen will appear only if you selected Oracle9iAS Portal in the Component Configuration and Startup screen. Enter or accept the default Portal DAD and Schema names. Also, enter the database connection information. Click Next.

    Figure 5-11 Apache Listener Configuration for Oracle9iAS Portal (DAD and Schema name) Screen

    
    
    Text description of the illustration portdad.gif

    The Apache Listener Configuration for Oracle9iAS Portal screen allows you to enter the name of the Database Access Descriptor (DAD) that will be used to access Oracle9iAS Portal, and the name of the database schema where Oracle9iAS Portal will be installed. It also enables you to enter the database connection information if Oracle9iAS Portal and Oracle HTTP Server are installed in different Oracle homes. The information you enter here is used to create the PL/SQL Gateway settings which you can access upon installation from the following location: http://machine_name:port/pls/admin_/gateway.htm

    • Portal DAD Name: Enter the name of the DAD for each instance you installed in the database. A Database Access Descriptor (DAD) is a set of values that specify how the Apache Listener connects to your Oracle database server to fulfill an HTTP request. Based on this DAD name, the installation automatically sets other DAD-related and default settings such as the name and location of the document table. The default DAD name is portal30.

    • Portal Schema Name: Enter the name of the database schema that will contain Oracle Portal. A schema is a collection of components and database objects under the control of a given database user. Each Oracle Portal application maps to an Oracle database schema. The default schema name is portal30.

    • Connect String: Enter the origin database connection information in the form host:port:sid.

12. This screen will appear only if you selected Oracle9iAS Portal in the Component Configuration and Startup screen. Enter or accept the default Login Server DAD and Schema names. Click Next.

    Figure 5-12 Apache Listener Configuration for Oracle9iAS Portal (Login Server) Screen

    
    
    Text description of the illustration portlog.gif

    The Apache Listener Configuration for Oracle9iAS Portal screen allows you to enter the Login Server DAD and Schema Name, with a _sso extension for easy recognition. The Login Server provides an enterprise-wide Single Sign-On (SSO) mechanism that enables an Oracle Portal user to log in securely to Oracle Portal and any partner and external applications using a single user name and password.

    • Login Server DAD Name: Enter the name of the DAD for each instance you installed in the database.The default DAD name is portal30_sso.

    • Login Server Schema Name: Enter the name of the database schema that will contain Oracle Portal.The default schema name is portal30_sso.

13. This screen will appear only if you have selected Oracle9iAS Database Cache in the Component Configuration and Startup screen. Enter the SYSDBA name and password and click Next.

    Figure 5-13 Origin Database User Information Screen

    
    
    Text description of the illustration dbinf.gif

    The Origin Database User Information screen allows you to enter the SYSDBA information created for the origin database.

    • User Name: The SYSDBA user name for the origin database that the installer detects and defaults. You can change the name or accept the default.

    • Password: The password for the SYSDBA user.

14. Enter the hostname, port number, and SID of the origin database where you will install the Oracle9iAS Wireless, and click Next. If you are upgrading from Oracle9i Application Server, version 1.0.2.1, then an "Upgrade Installation Detected" screen will appear. Review the content on the screen and click Next or Exit accordingly. If you click Next, then the installation will continue and the following screen will appear.

    Note: Do not enter Oracle9iAS Database Cache hostname, port number, and SID in this screen.

    Figure 5-14 Wireless Edition Repository Information Screen

    
    
    Text description of the illustration repinf.gif

    The Wireless Edition Repository Information screen allows you to enter the hostname, Net8 Listener port number, and SID of the database where you will install the Oracle9iAS Wireless repository.

    • Hostname: Enter the hostname.domain of the database where you will install the Oracle9iAS Wireless.

    • Port: Enter the Net8 Listener port number.

    • SID: Enter the System Identifier (SID) of the database where you will install the Oracle9iAS Wireless repository.

15. Enter the new username and password for the database user to store the Oracle9iAS Wireless repository, and click Next. If you are upgrading from Oracle9i Application Server, version 1.0.2.1, then the "Oracle9iAS Wireless Schema Information Screen" will be slightly different. Enter the existing Oracle9iAS Wireless username and password, and click Next.

    Note: Do not use an existing database user, (that is, SYS, SYSTEM, or any other existing database user) as the username.

    Figure 5-15 Wireless Edition Schema Information Screen

    
    
    Text description of the illustration schema.gif

    The Wireless Edition Schema Information screen allows you to create a database user to store the Oracle9iAS Wireless repository.

    • Username: Enter a new user name for the database user to store the Oracle9iAS Wireless repository.

    • Password: Enter a password for the database user.

16. Enter and confirm the SYSTEM password of the database, and click Next. If you are upgrading from Oracle9i Application Server, version 1.0.2.1, then a "Wireless Edition Administrator Password Information" screen appears. Enter and confirm the "Administrator" password, and click Next.

    Note: Do not enter the database schema owner password.

    Figure 5-16 System Password for Wireless Edition Screen

    
    
    Text description of the illustration system.gif

    The System Password screen allows you to enter and confirm the SYSTEM password of the database where you are loading the Oracle9iAS Wireless repository.

    • Enter Password: Enter the SYSTEM password of the database where you will install the Oracle9iAS Wireless.

    • Confirm Password: Re-enter the SYSTEM password as entered above for verification.

17. Review the summary and click Install to begin the installation process.

    Figure 5-17 Summary Screen

    
    
    Text description of the illustration esumm.gif

    The Summary screen allows you to review all the settings before the actual installation process. These settings include source, destination, installation type, product language, space requirements, and a list of components.

    • To make changes to any of these settings, click Previous to return to the respective screens.

      Note: Insufficient disk space is indicated in red under Space Requirements.

    When you click Install, the installation process begins.

18. Monitor the installation process and after the installer finishes, click Next.

    Figure 5-18 Install Screen

    
    
    Text description of the illustration inst.gif

    The Install screen appears while the product is installing. Installation operations include executing actions such as file copy and linking, and executing decision points and calculations. It also displays the full path of the installation log.

    • Cancel: To discontinue the installation process. You can then choose to stop the installation of an individual component or the entire product.

    For more information about installation log, refer to "oraInventory Directory".

    During the installation process, Oracle Installer appears to install 8.0.6 RSF-based products such as Oracle9iAS Forms Services, Oracle9iAS Reports Services, and Oracle9iAS Discoverer. No user input is required.

    Changing Disks

    During installation, the installer prompts you to switch between Disks 1 through 5. Use these steps to change disks and continue the installation process.

    Figure 5-19 Changing Disks Dialog

    
    
    Text description of the illustration disk2.gif
    1. Eject and unmount the current disk.

       If you are using Solaris Volume Management software and Disk1 was automatically mounted, then this can be done with the following command:

       prompt> eject cdrom
       
       

       If you are not using Solaris Volume Management software, then you must manually eject and unmount the disk. For further instructions, refer to your operating system documentation

    2. Insert the next disk into the CD-ROM drive and mount it.

       If you are using the Solaris Volume Management software, then the next disk will be automatically mounted.

       If you are not using Solaris Volume Management software, then you must manually mount the disk. For further instructions, refer to "Starting Oracle Universal Installer".

    3. Click the Browse button on the changing disks dialog, and navigate to /cdrom/9ias_1022_diskx. This directory may be different depending on where the original disk was mounted.

    4. Click OK to continue the installation process.

    Running root.sh

    After installation is completed, the installer prompts you to run root.sh script. Use these steps to run the root.sh script.

    1. Log on as the root user.

    2. Go to the Oracle home directory.

       prompt> cd $ORACLE_HOME
       
       

    3. Run the root.sh script.

       prompt> ./root.sh
       
       

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

19. Start the origin database if it has been shut down during installation. Verify the list of configuration tools and click Next. This screen appears only if you select components to configure and start in the Components Configuration and Startup screen.

    Note: The installer has completed copying and linking the necessary files. Be sure to start the database if it had been shut down for the installation process. The configuration tools such as Oracle9iAS Portal Configuration Assistant need to connect to an active database for configuration purposes.

    Figure 5-20 Configuration Tools Screen

    
    
    Text description of the illustration ecftool.gif

    The Configuration Tools screen lists the configuration tools for all installed components.

    Scroll down the list to review the configuration status of each tool. The status changes as each component is configured.

    The installer performs the following functions in this screen:

    • Executes a configuration tool for each component selected previously in the Component Configuration and Startup screen.

    • Displays all the configuration settings in the display window below as it executes a configuration tool for each component.

    • Enables you to view configuration settings after all configuration tools are executed. Click on each component to review all the changes made.

    • Allows you to view data for failed executions in the display window. You can either fix the error and click Retry to execute the configuration tool again, or ignore the error and click Next to proceed to the next screen.

    • Retry: To re-execute the configuration script if the configuration of a component fails.

    • Stop: To quit the configuration process.

    Configuration Tools

    Depending on the components you select in the Configuration and Startup screen, the following configuration tools launch:

    Oracle9iAS Database Cache Configuration Assistant - This configuration assistant enables you to configure your middle-tier caches. Oracle9iAS Database Cache Configuration Assistant will not appear if you are migrating from Oracle9i Application Server 1.0.2.1to 1.0.2.2.

    See Also: "Oracle9iAS Database Cache Configuration Assistant" for instructions on running Oracle9iAS Database Cache Configuration Assistant.

    Oracle9iAS Web Cache Configuration Assistant - This launches the service to start Oracle9iAS Web Cache. Oracle9iAS Web Cache service starts up automatically by default. If you choose not to use Oracle9iAS Web Cache, you will need to stop the service manually.

    See Also: "Starting and Stopping Components"

    Starting HTTP Server - This starts Oracle HTTP Server.

    Starting Forms Server - This starts the Oracle9iAS Forms Services.

    Starting Reports Server - This starts the Oracle9iAS Reports Services.

    Oracle9iAS Portal Configuration Assistant - This configuration assistant loads necessary database objects for Oracle9iAS Portal to run.

    See Also: "Oracle9iAS Portal Configuration Assistant" for instructions on running Oracle9iAS Portal Configuration Assistant.

    Starting Discoverer 4i Viewer Server - This starts the Oracle9iAS Discoverer Services.

20. Ensure that the installation was successful. Click Exit to quit the installer.

    Figure 5-21 End of Installation Screen

    
    
    Text description of the illustration end.gif

    The End of Installation screen appears at the end of the installation process. It notifies you whether the installation was successful or unsuccessful.

    • Release Information: To view the latest release information.

    If the installer detects that specific port numbers such as 7777, are occupied, it will display the alternate port numbers on the end of Installation screen. For Oracle HTTP Server port number information, refer to "Port Allocation".

You have successfully installed the Enterprise Edition installation option of Oracle9i Application Server. Proceed to "Postinstallation" to complete the installation process.

Postinstallation

The following instructions guide you through the basic postinstallation tasks for Oracle9i Application Server. Before performing these tasks, install, if needed, Oracle9i Application Server Client from the Oracle9i Application Server Administrative and Development Client CD included in the Oracle9i Application Server CD pack.

See Also: Appendix B, "Installing Oracle9i Application Server Administrative and Development Client CD-ROM"

The postinstallation contains the following sections:

• Environment Scripts

• Component-specific Tasks

• Starting and Stopping Components

• Component Web Sites

• Component Port Numbers

• Additional Documentation

Environment Scripts

Table 5-1 and Table 5-2 list the environment script for Enterprise Edition installation option:

Table 5-1 Environment Scripts for C Shell Users

Component	C Shell
Oracle9iAS Database Cache	ORACLE_HOME/8ienv.csh
Oracle9iAS Discoverer	ORACLE_HOME/6iserver/discwb4/discwb.csh
Oracle9iAS Forms Services	ORACLE_HOME/6iserver/forms60.csh
Oracle9iAS Reports Services	ORACLE_HOME/6iserver/reports60.csh
Oracle9iAS Web Cache	ORACLE_HOME/8ienv.csh
Oracle Internet File System	Using the Bourne or Korn shell, run the following scripts: ORACLE_HOME/ifs1.1/bin/infenv.sh ORACLE_HOME/ifs1.1/bin/ifsconfig
Oracle Management Server	ORACLE_HOME/8ienv.csh

Table 5-2 Environment Scripts for Bourne or Korn Shell Users

Component	Bourne/Korn Shell
Oracle9iAS Database Cache	ORACLE_HOME/8ienv.sh
Oracle9iAS Discoverer	ORACLE_HOME/6iserver/discwb4/discwb.sh
Oracle9iAS Forms Services	ORACLE_HOME/6iserver/forms60.sh
Oracle9iAS Reports Services	ORACLE_HOME/6iserver/reports60.sh
Oracle9iAS Web Cache	ORACLE_HOME/8ienv.sh
Oracle Internet File System	ORACLE_HOME/ifs1.1/bin/infenv.sh ORACLE_HOME/ifs1.1/bin/ifsconfig
Oracle Management Server	ORACLE_HOME/8ienv.sh

Component-specific Tasks

This section contains postinstallation tasks for the following topics:

• Oracle Internet File System

• Oracle Management Server

• Oracle9iAS Database Cache

• SSL Authentication Method Configuration

• Multi-threaded Server Configuration

Oracle Internet File System

You must run the Oracle Internet File System Configuration Assistant manually to configure Oracle Internet File System.

See Also: "Oracle Internet File System Configuration Assistant" for instructions on running Oracle Internet File System Configuration Assistant.

Oracle Management Server

You must run the Oracle Enterprise Manager Configuration Assistant manually to configure Oracle Management Server.

See Also: "Oracle Management Server Configuration Assistant" for instructions on running Oracle Enterprise Manager Configuration Assistant.

Oracle9iAS Database Cache

Be sure to perform the following post-installation steps to Oracle9iAS Database Cache

• Setting Up the Oracle9iAS Database Cache Environment for Your Applications

• Using the Oracle9iAS Database Cache Home

• Using a Previous Oracle8i Release 8.1.6 Oracle Home

• Relinking Applications That Use Releases Previous to Release 8.1.6

• Modify the initicache.ora File

Setting Up the Oracle9iAS Database Cache Environment for Your Applications

When you install Oracle9iAS Database Cache, the installation procedure installs files that are specific to Oracle9iAS Database Cache and files that are updates to Oracle8i Server or Client release 8.1.6.1. These files contain the Oracle9iAS Database Cache functionality, as well as bug fixes to files usually installed with the Oracle8i Server or Client.

To use Oracle9iAS Database Cache, you must make sure that your applications are using the files and libraries installed for Oracle9iAS Database Cache. You can do this in the following ways:

• Run your application from the Oracle home in which you installed Oracle9iAS Database Cache. This is the supported method. See "Using the Oracle9iAS Database Cache Home" for a description of the steps you must take.

• If you have multiple Oracle homes and you need to run your application from the Oracle home for Oracle8i Server or Client release 8.1.6 or 8.1.6.1, you must copy files from the Oracle9iAS Database Cache Oracle home to the Oracle8i Server or Client Oracle home. See "Using a Previous Oracle8i Release 8.1.6 Oracle Home" for a description of the steps you must take.

• If your application was compiled and linked using a release prior to Oracle8i Server or Client release 8.1.6, you must relink your application using the OCI libraries that are installed by Oracle9iAS Database Cache. See "Relinking Applications That Use Releases Previous to Release 8.1.6" for more information.

Using the Oracle9iAS Database Cache Home

To run your application from the Oracle home in which you installed Oracle9iAS Database Cache, you must take the following steps:

1. From the process in which you will run your application, set the following environment variables:
   • Set Oracle home to the Oracle home in which you have installed Oracle9iAS Database Cache.

   • Set LD_LIBRARY_PATH so that the Oracle9iAS Database Cache library directory (ORACLE_HOME/lib) precedes library directories from other Oracle homes.

   • Set ORA_OCI_CACHE to "1" so that all applications started from the process will use the cache. (Alternatively, you can use parameters within OCI applications to control which applications or statements use the cache. See the Oracle9iAS Database Cache Concepts and Administration Guide for more information.)

   • If you use the environment variable TNS_ADMIN, make sure that it is set to the ORACLE_HOME/network/admin directory in the Oracle home for Oracle9iAS Database Cache.

2. If your application was running previously on the node on which you installed Oracle9iAS Database Cache and the application connected to the origin database by using an entry in an existing tnsnames.ora file, you must copy that entry to the tnsnames.ora file used by Oracle9iAS Database Cache.

   The tnsnames.ora file is located in the ORACLE_HOME/network/admin directory. Copy the entry from the file in the previously existing Oracle home to the tnsnames.ora file in the Oracle home in which you installed Oracle9iAS Database Cache.

   Note that the Oracle9iAS Database Cache installation creates an entry for the origin database in the tnsnames.ora file on the local cache node. It assigns the alias ora_icache_origin. Do not modify or delete the ora_icache_origin entry. To assign a different alias for another purpose, edit the tnsnames.ora file and add another entry. The Oracle9iAS Database Cache installation also creates an entry, ora_icache, for the cache. Do not modify or delete this entry.

Using a Previous Oracle8i Release 8.1.6 Oracle Home

If you previously ran your application from the Oracle home for Oracle8i Server or Client release 8.1.6 or 8.1.6.1 and you continue to need to run your application from that Oracle home, you must take the following steps:

Note: Use this method only if you cannot use the Oracle home for Oracle9iAS Database Cache. Do not use this method if your application ran from a release later than 8.1.6.1. Instead, refer to "Using the Oracle9iAS Database Cache Home" for the recommended method.

1. Copy the following library files from the Oracle home in which you installed Oracle9iAS Database Cache to the Oracle home for the Oracle8i server or client that your application uses:
   • ORACLE_HOME/lib/libclient8.a

   • ORACLE_HOME/lib/libgeneric8.a (not required for 8.1.6.1)

   • ORACLE_HOME/lib/libwtc8.so

   • ORACLE_HOME/lib/libwtc8.a

2. Set the following environment variables to the Oracle home for the Oracle8i server or client that your applications uses:
   • Set ORACLE_HOME to the Oracle home.

   • Set LD_LIBRARY_PATH to ORACLE_HOME/lib.

   • Set PATH to include ORACLE_HOME/bin.

3. From the Oracle home for the Oracle8i server or client that your application uses, run the executable file genclntsh, which is located in the ORACLE_HOME/bin directory.

4. Copy the SQL*Plus executable file from the Oracle home in which you installed Oracle9iAS Database Cache to the Oracle home for the Oracle8i server or client that your application uses.

5. Set the value of the environment variable ORA_OCI_CACHE to "1" so that all applications started from the process will use the cache. (Alternatively, you can use parameters within OCI applications to control which applications or statements use the cache.)

6. If you use the environment variable or registry parameter TNS_ADMIN, make sure it points to the Oracle home that your application uses.

7. Copy the entries in the tnsnames.ora file from the Oracle home in which you installed Oracle9iAS Database Cache to the tnsnames.ora file in the Oracle home for the Oracle8i server or client that your application uses.

Relinking Applications That Use Releases Previous to Release 8.1.6

If your application was compiled and linked using a release prior to Oracle8i Server or Client release 8.1.6, you must relink your application using the OCI libraries that are installed by Oracle8i Cache.

For information about relinking applications, see Oracle Call Interface Programmers Guide and Oracle8i Administrator s Reference in the database documentation.

Then, you must take the steps described in "Using the Oracle9iAS Database Cache Home" .

Modify the initicache.ora File

The Oracle9iAS Database Cache installation creates a cache using the same database character set as the origin database. However, it does not set other National Language Support (NLS) features, such as date format or currency symbols.

If the initialization file (initSID.ora) of your origin database specifies NLS parameters, you must copy those parameters to the initialization file (initicache.ora) of the cache. (NLS parameters begin with "NLS_".)

For example, if the initialization file of your origin database contains the following parameters, copy them to initicache.ora:

NLS_LANGUAGE = JAPANESE
NLS_CALENDAR = "Japanese Imperial"
NLS_DATE_FORMAT = "E YY-MM-DD"

The file initicache.ora is located in the following directory:

ORACLE_HOME/admin/icache/pfile

For information about setting up your caches and additional information about configuring your application environment, see the Oracle9iAS Database Cache Concepts and Administration Guide.

SSL Authentication Method Configuration

This section guides you through configuring SSL for Oracle9iAS Database Cache, Oracle Servlets Engine for Java, Distributed CORBA Applications, and Enterprise JavaBeans.

These steps guide you through the SSL configuration for the following:

Oracle9iAS Database Cache

To configure Oracle9iAS Database Cache to use SSL, remove the comment characters (#) from the following entry in the listener.ora file:

For secure connections over SSL, uncomment the following lines:

#  (DESCRIPTION = # Secure TCP connections
#      (ADDRESS =
#         (PROTOCOL = TCPS) (HOST = host_name) (PORT = 2484)
#      )
#  )

The listener will listen for all SSL requests.

Oracle Servlets Engine for Java

To configure Oracle Servlets Engine for Java to use SSL, (in addition to removing the comment characters from the appropriate line in the initialization file) you must remove the comment characters (#) from the following entry in the tnsnames.ora file:

# Support for mod_ose over TCP with SSL connections.
# inst1_https =
#   (DESCRIPTION =
#      (ADDRESS =
#         (PROTOCOL=TCPS)
#         (HOST=host_name)
#         (PORT=2484)
#      )
#      (CONNECT_DATA=
#         (SERVICE_NAME=MODOSE)
#         (SERVER=shared)
#         (PRESENTATION=http://admin)
#      )
#   )

Distributed CORBA Applications and Enterprise JavaBeans

To configure distributed CORBA application and Enterprise JavaBeans to use SSL, (in addition to removing the comment characters from the appropriate line in the initialization file) you must remove the comment characters (#) from the following entry in the listener.ora file:

For secure IIOP connections over SSL, uncomment the following lines:

# (DESCRIPTION = # Secure IIOP Connections
#    (PROTOCOL_STACK =
#       (PRESENTATION=GIOP)
#       (SESSION=RAW)
#     )
#    (ADDRESS=(PROTOCOL=TCPS)(HOST=% s_host_name%)(PORT=2482))
#  )

Multi-threaded Server Configuration

These steps guide you through configuring Oracle9iAS Database Cache as a Multi-threaded server for Oracle Servlets Engine for Java, Distributed CORBA Applications, and Enterprise JavaBeans:

Oracle Servlets Engine for Java

To configure Oracle9iAS Database Cache as a multi-threaded server (MTS) for Oracle Servlets Engine for Java, you must make one or both of the following changes to your initialization file (instSID.ora):

• For standard connections, remove the comment character (#) from the following line:

  # mts_dispatcher = "(PROTOCOL=TCP)(SERV=MODOSE)"
  
  

• To use the secure socket layer (SSL) authentication method, remove the comment character (#) from the following line:

  # mts_dispatcher = "(PROTOCOL=TCPS)(SERV=MODOSE)"
  
  

For information on enabling SSL for Oracle9iAS Portal, refer to Oracle Portal 3.0.8 Configuration Guide.

Distributed CORBA Applications and Enterprise JavaBeans

To configure Oracle9iAS Database Cache as a multi-threaded server (MTS) for distributed CORBA applications and Enterprise JavaBeans, you must make the following changes in your initialization file (instSID.ora):

• Remove the comment character (#) from the following line:

  # mts_dispatcher = "(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServer)"
  
  

• To use the secure socket layer (SSL) authentication method, remove the comment character (#) from the following line:

  # mts_dispatcher = "(PROTOCOL=TCPS)(SERV=oracle.aurora.server.SGiopServer)"
  
  

Starting and Stopping Components

Table 5-3 lists the commands needed to individually start and stop the components.

Table 5-3 Starting and Stopping Components

Component	Function	Command
Oracle9iAS Database Cache	Start	ORACLE_HOME/bin/cachstrt
	Stop	ORACLE_HOME/bin/cachshut
Oracle9iAS Discoverer	Start	ORACLE_HOME/6iserver/discwb4/util/startall.sh
	Stop	ORACLE_HOME/6iserver/discwb4/util/stopall.sh
Oracle9iAS Forms Services	Start	ORACLE_HOME/6iserver/forms60_server start
	Stop	ORACLE_HOME/6iserver/forms60_server stop
Oracle9iAS Reports Services	Start	ORACLE_HOME/6iserver/reports60_server start
	Stop	ORACLE_HOME/6iserver/reports60_server stop
Oracle9iAS Web Cache	Start	ORACLE_HOME/webcache/bin/webcachectl start
	Stop	ORACLE_HOME/webcache/bin/webcachectl stop
Oracle9iAS Wireless Web Integration Server	Start	ORACLE_HOME/panama/WebIntegration/Server/bin/server.sh
	Stop	Go to http://hostname.domainname:5555 and click on shutdown.
Oracle HTTP Server	Start	ORACLE_HOME/Apache/Apache/bin/apachectl start
	Stop	ORACLE_HOME/Apache/Apache/bin/apachectl stop
Oracle HTTP Server SSL-enabled	Start	ORACLE_HOME/Apache/Apache/bin/apachectl startssl (Log in as root user.)
	Stop	ORACLE_HOME/Apache/Apache/bin/apachectl stop (Log in as root user.)
Oracle Internet File System	Start	ORACLE_HOME/ifs1.1/bin/ifsstart
	Stop	ORACLE_HOME/ifs1.1/bin/ifsstop
Oracle Management Server	Start	ORACLE_HOME/bin/oemctrl start oms &
	Stop	ORACLE_HOME/bin/oemctrl stop oms &

Component Web Sites

Table 5-4 lists Web sites for Oracle9i Application Server components.

Table 5-4 Component Web sites

Component	Web Site
Oracle9iAS Discoverer Viewer	http://hostname.domain:listener_port/discoverer4i/viewer
Oracle9iAS Discoverer Plus	http://hostname.domain:listener_port/discwb4/html/english/welcome.htm
Oracle9iAS Forms Services	http://hostname.domain:listener_port/dev60html/runform.htm
Oracle9iAS Portal	http://hostname.domain:listener_port/pls/portal30
Oracle9iAS Reports Services	http://hostname.domain:listener_port/dev60html/runrep.htm
Oracle9iAS Wireless Web Integration Server	http://hostname.domain:5555 (Log on as Administrator/manage)
Oracle9iAS Web Cache	http://hostname.domain:4000 (Log on as Administrator/Administrator)
Oracle HTTP Server Oracle HTTP Server (SSL-enabled)	http://hostname.domain:listener_port https://hostname.domain:listener_port
Oracle Internet File System	http://hostname.domain:listener_port/ifs/files (Log on as system/manager)
Oracle Management Server	http://hostname.domain:3339

Component Port Numbers

Table 5-5 lists the default port numbers on which requests are received for each component.

Table 5-5 Port Numbers

Components	Port Number
Oracle9iAS Database Cache Oracle9iAS Database Cache TNS Listener Oracle9iAS Database Cache -wtcme process Oracle9iAS Database Cache Data Gatherer -vppdc process	51719 TCP/IP: 1521, IIOP: 2481 51719, 51720 1808, 1809
Oracle9iAS Discoverer	Oracle9iAS Discoverer uses the same port number as Oracle HTTP Server
Oracle9iAS Forms Services Load Balancer Client Load Balancer Server	9001 9011 9021
Oracle9iAS Portal	Oracle9iAS Portal uses the same port number as Oracle HTTP Server
Oracle9iAS Reports Services	1950
Oracle9iAS Web Cache Oracle9iAS Web Cache Administration Port Oracle9iAS Web Cache Invalidation Port Oracle9iAS Web Cache Statistics Port	1100 4000 4001 4002
Oracle9iAS Wireless Oracle9iAS Wireless Web Integration Server	Oracle9iAS Wireless uses the same port as Oracle HTTP Server 5555
Oracle HTTP Server Oracle HTTP Server (SSL-enabled) Oracle HTTP Server Jserv Servlet Engine	For information on port numbers, refer to "Port Allocation". 8007
Oracle Internet File System	Oracle Internet File System uses the same port number as Oracle HTTP Server FTP: 21 SMB: 139 SMTP: 2500 IMAP: 143 CUP: 4180
Oracle Enterprise Java Engine TNS Listener	TCP/IP: 1521 IIOP: 2481
Oracle Management Server	7771, 7772, 7773

Additional Documentation

For further information on postinstallation and configuration tasks, refer to component-specific documentation. For information on viewing and installing the documentation, refer to Appendix F, "Installing Documentation Library".