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 installation process is divided into two parts:

• Preparing System for Installation

• Installing Oracle9i Application Server

Preparing System for Installation

The following instructions prepare your machine for the installation 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 n_wel.gif

   The Welcome screen provides information about the Oracle Universal Installer.

   The following function buttons appear on the installation screens.

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

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

   • Exit: To quit the installation process and exit the installer.

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

   • Installed Products: To view currently installed products or to deinstall the entire product or components.

   • Previous: To return to the previous screen.

   • Next: To move to the next screen.

2. Verify the source and destination paths and click Next.

   Figure 5-2 File Locations Screen

   
   
   Text description of the illustration n_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 of ORACLE_HOME, which is the root directory in which product is installed.

     - Name: This is the name Windows uses to identify your ORACLE_HOME.

     - Path: This is the full path of the ORACLE_HOME.

     Note: Be sure 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.

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

3. Select Enterprise Edition and click Next.

   Figure 5-3 Installation Types Screen

   
   
   Text description of the illustration n_ent.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.

   The following are the installation options:

   • Oracle HTTP Server Only: Installs Oracle Portal, Oracle Portal-to-Go, Oracle Enterprise Manager Client, and Oracle HTTP Server.

   • Standard Edition: Installs Oracle 8i JVM, Oracle Enterprise Manager Client, Oracle Portal, Oracle Portal-to-Go, Oracle Internet File System, and Oracle HTTP Server.

   • Enterprise Edition: Installs Oracle Forms Services, Oracle Reports Services, Oracle Database Cache, Oracle Management Server, Oracle Enterprise Manager Client, Oracle 8i JVM, Oracle Web Cache, Oracle Portal, Oracle Discoverer 3i Viewer, Oracle Portal-to-Go, Oracle Internet File System, and Oracle HTTP Server.

4. You do not have sufficient space to install Oracle9i Application Server. Free enough disk space to meet the hardware requirements and click Next, or click Previous to select another drive.

   Figure 5-4 Insufficient Disk Space Screen

   
   
   Text description of the illustration n_disksp.gif

   Insufficient Disk Space screen appears only if you do not have enough disk space on your selected drive to install Oracle9i Application Server. You can:

   • Click Next once you have freed sufficient disk space.

   • Click Previous to select another drive to install product.

     See Also: Chapter 1, "Requirements"

5. Select the components for automatic configuration and startup after installation and click Next.

   Figure 5-5 Component Configuration and Startup Screen

   
   
   Text description of the illustration n_stup.gif

   The Component Configuration and Startup screen allows you to select the components that you want the installer to configure and automatically 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 automatically starts that component.

   • If you de-select a component here, then the installer installs it, but does not configure or automatically start it. After installation, 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.

6. Review the system reboot information and click Next.

   Note: Be sure to close all other open applications and processes as your machine will automatically reboot after the configuration files are copied.

   Figure 5-6 System Reboot Screen

   
   
   Text description of the illustration n_reboot.gif

   The System Reboot screen informs you that after the installer copies the necessary files required to install Oracle9i Application Server, your machine will reboot to allow the configuration changes to take effect. When the machine starts up again, Oracle Universal Installer appears and begins the installation process of the Oracle9i Application Server.

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

   Figure 5-7 Install Screen

   
   
   Text description of the illustration n_inst1.gif

   The Install screen appears while Oracle Universal Installer installs required configuration files for Oracle9i Application Server. It also displays the full path of the installation log.

   • Cancel: To discontinue the installation process.

   Your machine will reboot once the configuration files are copied. Do not attempt to restart the installer after reboot. It will launch automatically.

Installing Oracle9i Application Server

Once your machine starts up after rebooting, the Oracle Universal Installer appears and proceeds to install Oracle9i Application Server. The following instructions guide you through the installation process.

Note: Be sure to log in with administrator privileges after your machine starts up again.

Changing Disks: During the installation process, the Disk Location dialog appears and prompts you to change disks. Insert the requested disk into your disk drive, or specify an alternative location, and click OK.

Text description of the illustration n_1_2.gif

The following screen appears as Oracle Universal Installer relaunches.The installer may take up to several minutes to start, and might pause if some screensavers are activated.

Text description of the illustration n_oui.gif

1. If needed, verify and change the locations of the components displayed on the screen, and click Next.

   This screen appears only under the following condition(s):

   • Oracle Universal Installer is being run on your machine for the first time.

   • Oracle Universal Installer has detected insufficient disk space in the ORACLE_HOME directory.

   Figure 5-8 Component Locations Screen

   
   
   Text description of the illustration entcploc.gif

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

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

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

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

   Figure 5-9 Origin Database Connection Information

   
   
   Text description of the illustration n_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.

3. Enter or accept the default Portal DAD and Schema names. Also, enter the TNS Connect String, if necessary. Click Next. This screen will appear only if you selected Oracle Portal in the Component Configuration and Startup screen.

   Figure 5-10 Apache Listener Configuration for Oracle Portal (DAD and Schema name) Screen

   
   
   Text description of the illustration n_adad.gif

   The Apache Listener Configuration for Oracle Portal DAD screen allows you to enter the name of the Database Access Descriptor (DAD) that will be used to access Oracle Portal, and the name of the database schema where Oracle Portal will be installed. It also enables you to enter the TNS connect string if Oracle 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.

   • TNS Connect String: Enter the TNS connect string or TNS alias that you have defined for the remote Oracle database. It enables you to install the Portal database objects into a remote database. Since you are installing in a new Oracle home, you will need to enter a TNS connect string before it is actually created. The Net8 Assistant will appear later in the installation process to guide you in the configuration of a new TNS alias. Be sure to note the name of the TNS connect string you enter here, so that you will use the same name when the Net8 Assistant appears later.

4. Enter or accept the default Login Server DAD and Schema names. Also, enter the TNS Connect String, if necessary. Click Next. This screen will appear only if you selected Oracle Portal in the Component Configuration and Startup screen.

   Figure 5-11 Apache Listener Configuration for Oracle Portal (Login Server) Screen

   
   
   Text description of the illustration n_alog.gif

   The Apache Listener Configuration for Oracle 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. It also enables you to enter the TNS Connect String if Oracle Portal and Oracle HTTP Server are installed in different Oracle homes.

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

   • TNS Connect String: Enter the TNS connect string or TNS alias that you have defined for the remote Oracle database.

     For more information on these fields, refer to the previous screen.

5. Enter the hostname, port number, and SID of the origin database, and click Next.

   Figure 5-12 Portal-to-Go Repository Information Screen

   
   
   Text description of the illustration n_prep.gif

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

   • Hostname: Enter the hostname.domain of the origin database.

   • Port: Enter the Net8 Listener port number.

   • SID: Enter the System Identifier (SID) of the origin database.

6. Enter the new username and password for the database user to store the Portal-to-Go repository, and click Next.

   Figure 5-13 Portal-to-Go Schema Information Screen

   
   
   Text description of the illustration n_pscma.gif

   The Portal-to-Go Schema Information screen allows you to create a database user to store the Portal-to-Go repository.

   • Username: Enter a new user name for the database user to store the Portal-to-Go repository.

   • Password: Enter a password for the database user.

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

7. Enter and confirm the SYSTEM password of the database, and click Next.

   Figure 5-14 System Password Screen

   
   
   Text description of the illustration n_psys.gif

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

   • Enter Password: Enter the SYSTEM password of the origin database.

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

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

   Figure 5-15 Origin Database User Information Screen

   
   
   Text description of the illustration n_dbinfo.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.

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

   Figure 5-16 Summary Screen

   
   
   Text description of the illustration n_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.

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

    Figure 5-17 Install Screen

    
    
    Text description of the illustration n_inst2.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.

    The following screen indicates that Oracle Installer is installing Oracle Forms Services, Oracle Reports Services, and Oracle Discoverer 3i Viewer. No user input is required.

    Figure 5-18 Oracle Installer

    
    
    Text description of the illustration n_orca19.gif

11. Verify the list of configuration tools and click Next. This screen appears only if you select components to configure and start automatically in the Components Configuration and Startup screen.

    Figure 5-19 Configuration Tools Screen

    
    
    Text description of the illustration n_econf.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.

    • Automatically starts the components.

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

    Oracle Database Cache Configuration Assistant - It enables you to configure your middle-tier caches.

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

    Note: If you are installing Oracle Database Cache on the same machine as the origin database, then be sure to follow the instructions as listed in Appendix C, "Installing Oracle Database Cache on the Origin Database System".

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

    See Also: "Starting and Stopping Components"

    Oracle Portal Configuration Assistant - It loads necessary database objects for Oracle Portal to run.

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

    Starting Oracle HTTP service- It starts the Oracle HTTP Server.

    Oracle HTTP Server starts up in a DOS window. In that window, you can test the Oracle HTTP Server installation.

    To administer the Oracle HTTP service from the Control Panel, reboot your machine after Oracle9i Application Server installation completes. Then, Oracle HTTP service will start automatically and you will no longer need to start it in a DOS window.

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

    Figure 5-20 End of Installation Screen

    
    
    Text description of the illustration n_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.

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, be sure to install Oracle Portal-to-Go client from the Oracle9i Application Server Administrative and Development Client CD included in the Oracle9i Application Server CD pack.

See Also: Appendix B, "Installing Oracle Portal-to-Go Client"

The postinstallation contains the following sections:

• Environment Variables

• Component Port Numbers

• Component-specific Tasks

• Starting and Stopping Components

• Additional Documentation

Environment Variables

Table 5-1 lists the environment variables that must be set for Enterprise Edition installation option:

Table 5-1 Environment Variables

Environment Variable	Must Be or Include
ORACLE_ HOME	The ORACLE_HOME used for installing Oracle9i Application Server.
PATH	<ORACLE_HOME>\bin <ORACLE_HOME>\Apache\Apache\bin <ORACLE_HOME>\6iserver <ORACLE_HOME>\ifs1.1\bin <ORACLE_HOME>\6iserver\discwb33\util <ORACLE_HOME>\calypso\bin

Component Port Numbers

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

Table 5-2 Port Numbers

Components	Port Number
Oracle Web Cache Oracle Web Cache Administration Port Oracle Web Cache Invalidation Port Oracle Web Cache Statistics Port	1100 4000 4001 4002
Oracle HTTP Server Oracle HTTP Server (SSL-enabled)	80 443
Oracle Database Cache	51719
Oracle Forms Services Load Balancer Client Load Balancer Server	9001 9011 9021
Oracle Reports Services	1950
Oracle Discoverer 3i Viewer	Oracle Discoverer 3i Viewer uses the same port number as Oracle HTTP Server
Oracle Internet File System	80
Oracle Portal	Oracle Portal uses the same port number as Oracle HTTP Server
Oracle Portal-to-Go	Oracle Portal-to-Go uses the same port number as Oracle HTTP Server

Component-specific Tasks

This section contains postinstallation tasks for the following components:

• Oracle Internet File System

• Oracle Management Server

• Oracle Database Cache

• Oracle Portal-to-Go

Oracle Internet File System

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

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

Oracle Management Server

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

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

Oracle Database Cache

Be sure to perform the following postinstallation steps for Oracle Database Cache:

• Setting Up the Oracle Database Cache Environment for Your Applications

• Modify the initicache.ora File

• Set NTFS File System and Windows NT Registry Permissions

Setting Up the Oracle Database Cache Environment for Your Applications

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

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

• Run your application from the Oracle Home in which you installed Oracle Database Cache. This is the supported method.

  See Also: "Using the Oracle 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 Oracle Database Cache Oracle home to the Oracle8i Server or Client Oracle home.

  See Also: "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 Oracle Database Cache.

  See Also: "Relinking Applications That Use Releases Previous to Release 8.1.6" for more information.

Using the Oracle Database Cache Home

To run your application from the Oracle home in which you installed Oracle 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 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 Also: Oracle Database Cache Concepts and Administration Guide in the Oracle9i Application Server Documentation Library.

   • 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 Oracle Database Cache.

   • Set the value of the environment variable PATH so that the Oracle Database Cache library directory (<ORACLE_HOME>\lib) precedes other Oracle library directories.

   • If you use the CLASSPATH environment variable, set it to the Oracle home in which you installed Oracle Database Cache.

2. If you use the environment variable or registry parameter TNS_ADMIN, make sure that it is set to the <ORACLE_HOME>\network\Admin directory in the Oracle home for Oracle Database Cache. The registry parameter is located in the following location:

   HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME id

3. From the Start menu, select Oracle for Windows NT -> Oracle Home Selector. Then, select the Oracle home in which you installed Oracle Database Cache.

4. If your application was running previously on the node on which you installed Oracle 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 Oracle 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 Oracle Database Cache.

   Note that the Oracle 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 Oracle 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 Oracle Database Cache. Do not use this method if your application ran from a release later than 8.1.6.1.

See Also: "Using the Oracle Database Cache Home" for the recommended method.

1. Copy the following library files from the Oracle home in which you installed Oracle Database Cache to the Oracle home for the Oracle8i server or client that your application uses:

   <ORACLE_HOME>\bin\oraclient8.dll
<ORACLE_HOME>\bin\orageneric8.dll (not required for 8.1.6.1)
   <ORACLE_HOME>\bin\orawtc8.dll
<ORACLE_HOME>\bin\orawtc8.lib

2. From the Start menu, select Oracle for Windows NT -> Oracle Home Selector. Then, select the Oracle home for the Oracle8i server or client that your application uses.

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

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

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

6. Copy the entries in the tnsnames.ora file from the Oracle home in which you installed Oracle 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 Oracle Database Cache.

See Also: Oracle Call Interface Programmers Guide and Oracle8i Administrator s Reference in your Oracle Database Documentation Library

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

Modify the initicache.ora File

The Oracle 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"

initicache.ora is located in the ORACLE_HOME\Admin\icache\pfile directory.

Set NTFS File System and Windows NT Registry Permissions

Oracle Corporation recommends that you configure Oracle Database Cache files, directories, and registry settings to allow only authorized database administrators to have full control. The following sections describe how to perform these tasks.

See your Windows NT documentation for more information about modifying NTFS file system and Windows NT registry settings.

NTFS File System Security

Oracle Database Cache uses files to store data and configuration information. To do this, the Oracle Database Cache process runs under a security account. This security account (the account under which you installed Oracle Database Cache) includes the ability to create and access these files. The security account is assigned to the service that Oracle Database Cache uses (in the Control Panel). This account requires full file system permissions to create, read, write, delete, and execute files.

To ensure that only authorized users have full file system permissions:

1. From Windows NT Explorer, select Oracle Database Cache executables and dynamic link libraries (in ORACLE_HOME\bin), Oracle Database Cache directories, and files for the cache (in ORACLE_HOME\dbs).

2. Right-click and select Properties.

3. Adjust the file and directory permissions to ensure that:
   • Only the security account has full control permissions to these files

   • User accounts that must run Oracle applications (for example, SQL*Plus, Server Manager, and Pro*C) have read privileges on the necessary executables (for example, sqlplus.exe for SQL*Plus)

Windows NT Registry Security

Oracle Corporation recommends that you remove write permissions in the NT registry from users who are not DBAs or system administrators.

To remove write permissions:

1. From the Windows NT Start menu, select Run. For Open, type regedt32.

2. Select the key HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE.

3. From the Security menu, select Permissions.

4. In the Registry Key Permissions dialog box, remove write permissions from any users who are not Oracle Database Cache DBAs or system administrators. Note that the SYSTEM account must have Full Control.

5. Ensure that user accounts that must run Oracle applications have read privileges.

6. Click OK.

7. Exit the registry.

SSL Authentication Method Configuration

This section guides you through configuring Oracle Database Cache to use SSL and Oracle 8i JVM.

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

Oracle Database Cache

To configure Oracle 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 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 Java Beans

To configure distributed CORBA application and Enterprise Java Beans 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 Oracle Database Cache as a Multi-threaded server for the following applications:

Oracle Servlets Engine for Java

To configure Oracle 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)"
  
  

Distributed CORBA Applications and Enterprise Java Beans

To configure Oracle Database Cache as a multi-threaded server (MTS) for distributed CORBA applications and Enterprise Java Beans, 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)(PREoracle.aurora.server.SGiopServer)"
  
  

Oracle Portal-to-Go

The following section describes postinstallation configuration instructions for Oracle Portal-to-Go:

• Loading Oracle Portal-to-Go Repository

• Oracle Portal-to-Go Web Integration Server Configuration

• Oracle Portal-to-Go Configuration Parameters

• Oracle Portal-to-Go Configuration Verification

Loading Oracle Portal-to-Go Repository

To load the bootstrap repository in the Oracle Portal-to-Go schema:

1. Open a DOS session, and go to ORACLE_HOME\panama\setupconf directory.

2. Type the following command:

   Set JAVA_HOME=ORACLE_HOME\Apache\jdk
   
   

3. Type the following to run the batch files:

   pa_java_inst
   
   

Oracle Portal-to-Go Web Integration Server Configuration

Oracle Portal-to-Go Web Integration Server hosts services that applications can use to exchange data and information sources via the Web. The Web Integration Server is installed with the Oracle Portal-to-Go components.

Note: The Web Integration Developer, the development environment for creating and testing Web Integration services written in Web Interface Definition Language (WIDL), is installed as part of the Oracle Portal-to-Go client.

See Also: Appendix B, "Installing Oracle Portal-to-Go Client"

The following steps guide you through the configuration process of the Web Integration Server:

1. Run the Web Integration Server.

   Web Integration Server is installed as a service. Select Oracle Web Integration Server from the Services dialog, and click the Start button.

2. From a browser, go to the Web Integration Server URL:

   http://host_name.domain:5555

3. Log in to the Web Integration Server with the user name Administrator, and password manage, which is the default password.

4. Select Settings. The server settings appear. Click Edit.

5. Enter the Proxy (HTTP) and Secure Proxy (HTTPS) settings for your environment.

6. Click Submit.

7. Click Logout.

Oracle Portal-to-Go Configuration Parameters

1. Configure the httpd.conf file.

   The httpd.conf file is in the ORACLE_HOME\Apache\Apache\conf directory.

   Create a Personalization Portal (papz) alias. This is needed so that the application server can find the

   http://hostname/papz/login.jsp.

   Add a line at the end of the Alias section:

   # PTG Start
   Alias /papz/ "<ORACLE_HOME>\panama\server\papz\"
   # PTG End
   
   

2. Configure the jserv.conf file.

   The jserv.conf file is in the ORACLE_HOME\Apache\Jserv\conf directory.

   In the ApJServMount section, add the Oracle Portal-to-Go specific mount point:

   # PTG Start
   ApJServMount /ptg /root
   # PTG End
   
   

3. Configure the jserv.properties file.

   The jserv.properties file is in the ORACLE_HOME\Apache\Jserv\conf directory.

   Next to the other "wrapper.classpath" entries, add all the required Oracle Portal-to-Go files to the classpath.

   # PTG Start
   wrapper.classpath=<ORACLE_HOME>\panama\server\classes
   wrapper.classpath=<ORACLE_HOME>\panama\lib\panama_core.zip
   wrapper.classpath=<ORACLE_HOME>\panama\lib\panama_papz.zip
   wrapper.classpath=<ORACLE_HOME>\panama\lib\client.zip
   wrapper.classpath=<ORACLE_HOME>\panama\lib\server.zip
   # PTG End
   
   

4. Configure the zone.properties file.

   The zone.properties file is in the

   ORACLE_HOME\Apache\Jserv\servlets directory.

   1. In the List of Repositories section, add the Oracle Portal-to-Go specific repository to the existing repository line with a comma (,) separator:

      # PTG Start
      repositories=<ORACLE_HOME>\Apache\Jserv\servlets,<ORACLE_HOME>\panama\
      server\papz
      # PTG End
      
      

   2. In the Startup Servlets section, add the Oracle Portal-to-Go specific servlets:

      # PTG Start
      servlets.startup=oracle.panama.ParmImpl
      # PTG End
      
      

   3. In the Servlet Aliases section, add the Oracle Portal-to-Go specific servlets:

      # PTG Start
      servlet.rm.code=oracle.panama.ParmImpl
      # PTG End
      
      

Oracle Portal-to-Go Configuration Verification

After installation, you can verify that individual Oracle Portal-to-Go components are properly configured:

1. Test the sample Java Servlet at the following URL:

   http://host_name.domain/papz/test.jsp

   "Hello World" should appear on the screen.

2. Test whether the Personalization Portal is working properly by accessing the following URL:

   http://host_name.domain/papz/login.jsp

   The login page should appear. The Personalization Portal prompts you to enter a user name and a password. You can log in using "Administrator" as the user name and "manager" as the password.

3. Run the Oracle Portal-to-Go Request Manager by accessing the following URL:

   http://host_name.domain/ptg/rm

Starting and Stopping Components

You can manually start and stop a component by doing the following:

1. In the Windows Control Panel, open Services.

2. In Services, select the service then click Start or Stop for desired result.

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 E, "Installing Documentation Library".