Release 1.0.2 for Windows NT
Part Number A86240-01
 Library |
 Contents |
 Index |
| Oracle9i Application Server Installation Guide Release 1.0.2 for Windows NT Part Number A86240-01 |
|
This chapter guides you through the basic concepts and preinstallation steps for Oracle9i Application Server. The following topics provide information about Oracle9i Application Server overview, environment variables settings, configuration options, and starting Oracle Universal Installer:
Oracle9i Application Server is a scalable, secure, middle-tier application server. It enables you to deliver Web content, host Web applications, connect to back-office applications, and access your data on wireless devices. Oracle9i Application Server has three installation options:
Table 2-1 lists the three installation options of Oracle9i Application Server, and the components that are installed with each option. This is followed by a brief description of each component.
Oracle 8i JVM is an enterprise-class 100% Java-compatible server environment that supports Enterprise JavaBeans, CORBA, and database stored procedures. Oracle 8i JVM achieves high scalability through its unique architectural design, which minimizes the burden and complexity of memory management when the number of users increases.
Oracle Advanced Security provides a comprehensive suite of security features to protect enterprise networks and securely extend corporate networks to the Internet. It provides a single source of integration with network encryption and authentication solutions, single signon services, and security protocols. By integrating industry standards, it delivers unparalleled security to the Oracle network and beyond.
Oracle Business Components for Java is a 100% Java-compatible, XML-powered framework that enables productive development, portable deployment, and flexible customization of multi-tier, database applications from business components.
Oracle Database Cache improves the performance and scalability of applications that access Oracle databases by storing frequently used data on middle tier machines. With Oracle Database Cache, your applications can process several times as many requests as their original capacity. In addition, you do not need to modify your existing applications to use Oracle Database Cache, and it is transparent to your end users.
The Oracle Database Client Developer's Kit contains the following client libraries:
Oracle Discoverer 3i Viewer is a query and analysis tool with a 100% thin client, CORBA architecture that makes it easy to deploy, and provides unsurpassed scalability. Using Oracle Discoverer's easy-to-use interface via a Web browser, users can access and analyze database data. Oracle Discoverer 3i Viewer scales up easily to support more users as demand on the system increases. It also optimizes for performance and is designed to minimize network traffic.
Oracle Enterprise Manager Client provides an integrated solution for centrally managing your Oracle environment. Combining a graphical console, Oracle Intelligent Agents, common services, and administrative tools, Oracle Enterprise Manager Client provides a comprehensive systems management platform for managing Oracle9i Application Server. To use this client, you must have a previously installed Oracle Management Server on your network.
Oracle Forms Services deploys Forms applications with database access to Java clients in a Web environment. Oracle Forms Services automatically optimizes class downloads, network traffic, and interactions with Oracle database. Applications are automatically load-balanced across multiple servers and, therefore, can easily scale to service any number of requests.
Oracle9i Application Server uses the Oracle HTTP Server, which is built on Apache Web server technology. Oracle HTTP Server offers scalability, stability, speed, and extensibility. It also supports Java Servlets, JavaServer Pages, Perl, PL/SQL, and CGI applications.
This component also includes the following sub-components:
Oracle Internet File System is a file system and development platform that stores files in an Oracle8i database. It provides a mechanism for creating, storing, and managing various types of information, from Web pages to email, from spreadsheets to XML files, in a common repository for users to access and update.
LDAP (Lightweight Directory Access Protocol) is the emerging Internet standard for directory services. Oracle LDAP Developer's Kit supports client interaction with any LDAP-compliant directory server, for example, Oracle Internet Directory. The toolkit provides tools and development libraries to support client calls to directory services, encrypted connections, and enables you to manage your directory data.
Oracle Management Server provides distributed control between the database and Oracle9i Application Server in the network. As a central engine for notifications, it processes all system management tasks and administers the distribution of these tasks across the enterprise. Ensure that you do not have multiple Oracle Management Servers installed on a single machine.
Oracle Plug-in for Microsoft IIS enables you to use Microsoft Internet Information Server (IIS) to directly access PL/SQL and Java Web components stored in an Oracle database. It provides functionality in a Microsoft IIS environment that is similar to the Oracle HTTP Server Modules, mod_plsql and mod_ose. Using it, you can access Web components by passing either a preconfigured virtual directory prefix (PL/SQL access), or a predefined file extension and virtual directory prefixes which are stored in the Java configuration file (Java access).
Oracle Portal is a complete solution for building, deploying and monitoring Web database applications and content-driven Web sites. Oracle Portal enables you to create and view database objects through an easy-to-use HTML-based interface, and provides tools for creating HTML-based interfaces. It also allows you to resolve performance problems using performance tracking facilities, and enables you to manage database security through its interface.
Oracle Portal-to-Go is a portal service for delivering information and applications to mobile devices. Using Oracle Portal-to-Go, you can create custom portal sites that use different kinds of content, including Web pages, custom Java applications, and XML-based applications. Portal sites make this diverse information accessible to mobile devices without you having to rewrite the content for each target device platform.
Oracle Reports Services provides an easy-to-use, scalable, and manageable solution for high-quality database publishing and reporting by creating dynamic reports for the Web and across the enterprise. It enables you to implement a multi-tiered architecture for running your reports.
Oracle Web Cache is a server accelerator caching service that improves the performance, scalability, and availability of frequently used e-business Web sites that run on Oracle9i Application Server and Oracle8i. By storing frequently accessed URLs in virtual memory, Oracle Web Cache eliminates the need to repeatedly process requests for those URLs on the Web server, and it caches both static and dynamically-generated HTTP content from one or more applications Web servers.
The Oracle XML Developer's Kit (XDK) contains the necessary XML components libraries and utilities to give developers the ability to easily XML-enable applications and Web sites. Oracle XDK supports development in Java, C, C++, and PL/SQL with a collection of libraries, command-line utilities, and tools.
Perform the following preinstallation tasks before installing the Oracle9i Application Server.
If you are migrating from Oracle Internet Application Server, Release 1.0.1, then you must perform certain migration tasks before installing Oracle9i Application Server, Release 1.0.2.
The list below directs you to the installation option that you have licence to:
Oracle HTTP Server Only installation option does not require any preinstallation tasks.
Proceed to "About Oracle Universal Installer" to start the installer.
The following are the preinstallation steps for the Standard Edition of the Oracle9i Application Server.
Perform the following tasks before installing Oracle Internet File System:
Installation of Oracle Internet File System requires reconfiguration of specific database parameters on the server machine.
Set the following Oracle initialization parameters to the values specified. These
parameters are contained in the init<SID>.ora file in the ORACLE_
HOME\admin\<global_database_name>\pfile directory.
open_cursors to at least 255.
shared_pool_size at least 50M.
To verify that there is at least one online non-system rollback segment, connect to Oracle as the SYS user with SQL*Plus and execute the following SQL statement:
SQL> SELECT segment_name, tablespace_name, status
FROM dba_rollback_segs;
This will result in output that looks like the following table:
| SEGMENT_NAME | TABLESPACE_NAME | STATUS |
|---|---|---|
|
SYSTEM |
SYSTEM |
ONLINE |
|
PUBLIC_RS |
SYSTEM |
ONLINE |
|
USERS_RS |
USERS |
ONLINE |
In this example, USERS_RS is an online non-system rollback segment. To ensure that the rollback segment is always online after a database startup, include the following line in the init<SID>.ora file:
rollback_segments = (rbs_name1, .... , rbs_namex)
SQL> SELECT name, value FROM v$parameter WHERE name = open_cursors;
You should see the open_cursors value you entered in the init<SID>.ora file in step 2.
Oracle9i Application Server requires an active database connection. The installer uses this connection to add database objects to the origin database. The origin database is the original and primary storage for your data and is typically located on a database server tier.
Before installing Oracle9i Application Server, verify that the origin database and its TNS listener are running.
You have completed the preinstallation tasks for the Oracle9i Application Server. Proceed to "About Oracle Universal Installer" to start the installer.
The following are the preinstallation steps for the Enterprise Edition of the Oracle9i Application Server.
For TCP/IP performance tuning tips for the computer running Oracle Web Cache, refer to Oracle HTTP Server powered by Apache Performance Guide in the Oracle9i Application Server Documentation Library.
Perform the following preinstallation tasks for Oracle Database Cache. Be sure to shut down the origin database and listener before making any changes.
To allow remote access to the origin database through Oracle Database Cache, you must check the initSID.ora file of the origin database and create a password file for the database if it does not exist. Take the following steps:
initSID.ora) of the origin database. If the file contains the REMOTE_LOGIN_PASSWORDFILE parameter, then make sure that the value equals SHARED or EXCLUSIVE. Oracle Database Cache can use either value. If the parameter is already set to either SHARED or EXCLUSIVE, then you do not need to change the value.
SYS and INTERNAL.
SYS and INTERNAL.
If the file does not contain the entry, then add it to the file, specifying either SHARED or EXCLUSIVE as the value. For example, to specify EXCLUSIVE, add the following entry to the file:
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
initSID.ora file is in the ORACLE_HOME\admin\dbs directory for of the origin database.
For the database, check if a password file exists. The file is named pwdSID.ora, where SID is the system identifier of the origin database. It is located in the following directory:
prompt> ORACLE_HOME\Database
orapwd utility with the following commands:
prompt> cd ORACLE_HOME\bin prompt> ORAPWD FILE=PWDSID.ORA PASSWORD=sys_password ENTRIES=maxRemUsers
There are no spaces around the equal sign (=). The parameters have the following meaning:
SYS for the origin database. This parameter sets the password for SYSOPER and SYSDBA. If you issue the ALTER USER statement to change the password after connecting to the origin database, both the password stored in the data dictionary and the password stored in the password file are updated.
You must configure the listener for the origin database so that it listens for external procedure calls. To do so, take the following steps:
tnsnames.ora file for the origin database by adding an entry that enables you to connect to the listener process (and subsequently, the extproc process). For example, add the following entry to the tnsnames.ora file:
EXTPROC_CONNECTION_DATA.US.ORACLE.COM= (DESCRIPTION=
(ADDRESS_LIST=
(ADDRESS= (PROTOCOL=IPC) (KEY=EXTPROC0))
) (CONNECT_DATA= (SID=PLSExtProc)
(PRESENTATION= RO)
) )
Verify the following:
EXTPROC_CONNECTION_DATA". (Note that the domain name can be set to any value appropriate for your network.)
ADDRESS_LIST contains an ADDRESS entry setting "(PROTOCOL = IPC)".
Make a note of the KEY value (in this example, it is "EXTPROC0"). Also make a note of the SID value (in his example, it is "PLSExtProc"). These values must match the KEY and SID_NAME value, respectively, in the corresponding entry in the listener.ora file.
listener.ora file for the origin database and add the following entries for the external procedure listener:
LISTENER_01= (DESCRIPTION_LIST= (DESCRIPTION= (ADDRESS_LIST= (ADDRESS= (PROTOCOL= TCP) (HOST = my_hostname) (PORT = 1521))
) (ADDRESS_LIST= (ADDRESS= (PROTOCOL= TCP) (KEY=EXTPROC0))
) ) ) Verify the following:
ADDRESS_LIST contains an ADDRESS entry setting "(PROTOCOL = IPC)".
ADDRESS_LIST containing "(PROTOCOL = IPC) "has a key value which is the same KEY value from the tnsnames.ora file. In this example, the key value is "EXTPROC0".
Make a note of the name of the listener that will be used for external procedures. In this example, the listener name is "LISTENER_01".
listener.ora file and verify that there is a SID for external procedure listener in the listener's SID list.
SID_LIST_LISTENER= (SID_LIST= (SID_DESC= (SID_NAME=PLSExtProc) (ORACLE_HOME=/dsk1/oracle/rdbms/OraHome) (PROGRAM=extproc) )
...(SID_DESC = (GLOBAL_DBNAME = <global_DBname>) (ORACLE_HOME = /dks1/oracle/rdbms/OraHome) (SID_NAME = ias) ) )
Verify the following:
If the listener name you notes in step 2 is anything other than "LISTENER", then you will need to start and stop that specific listener. In the following example, the listener name is "LISTENER_01".
prompt> lsnrctl stop listener_01 prompt> lsnrctl start listener_01
extproc process spawned by the listener inherits the operating system privileges of the listener, so Oracle Corporation strongly recommends that you restrict the privileges for the separate listener process. The process should not have permission to read or write to database files or the Oracle server address space. Also, the owner of this separate process should not be the oracle user (which is the default owner of the server executable and database files). Therefore, you should start the listener from a user account that does not have permission to read or write to database files or the Oracle server address space.
extproc executable in the bin directory under the ORACLE_HOME of the origin database.
sqlnet.ora:
NAMES.DEFAULT_DOMAIN = <your.Domain.Name>
SQLNET.AUTHENTICATION_SERVICES= (NTS)
NAMES.DIRECTORY_PATH= (TNSNAMES, ONAMES, HOSTNAME)
Perform the following tasks before installing Oracle Internet File System:
Installation of Oracle Internet File System requires reconfiguration of specific database parameters on the server machine.
Set the following Oracle initialization parameters to the values specified. These
parameters are contained in the init<SID>.ora file in the ORACLE_
HOME\admin\<global_database_name>\pfile directory.
open_cursors to at least 255.
shared_pool_size at least 50M.
To verify that there is at least one online non-system rollback segment, connect to Oracle as the SYS user with SQL*Plus and execute the following SQL statement:
SQL> SELECT segment_name, tablespace_name, status
FROM dba_rollback_segs;
This will result in output that looks like the following table:
| SEGMENT_NAME | TABLESPACE_NAME | STATUS |
|---|---|---|
|
SYSTEM |
SYSTEM |
ONLINE |
|
PUBLIC_RS |
SYSTEM |
ONLINE |
|
USERS_RS |
USERS |
ONLINE |
In this example, USERS_RS is an online non-system rollback segment. To ensure that the rollback segment is always online after a database startup, include the following line in the init<SID>.ora file:
rollback_segments = (rbs_name1, .... , rbs_namex)
SQL> SELECT name, value FROM v$parameter WHERE name = open_cursors;
You should see the open_cursors value you entered in the init<SID>.ora file in step 2.
Oracle9i Application Server requires an active database connection. The installer uses this connection to add database objects to the origin database. The origin database is the original and primary storage for your data and is typically located on a database server tier.
Before installing Oracle9i Application Server, verify that the origin database and its TNS listener are running.
You have completed the preinstallation tasks for the Oracle9i Application Server. Proceed to "About Oracle Universal Installer" to start the installer.
Oracle9i Application Server uses Oracle Universal Installer to configure environment variables and to install components. The installer guides you through each step of the installation process, so you can choose configuration options for a customized product.
The installer includes features that perform the following tasks:
If the installer fails during installation, do the following before launching it again.
Look in the registry for the string value HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\iAS Install, Install Status and delete it.
Follow these steps to launch Oracle Universal Installer, which installs Oracle9i Application Server:
If your machine does not support the auto run feature, perform the following steps to launch the installer:
This launches Oracle Universal Installer through which you can install Oracle9i Application Server.
The list below navigates you to installation instructions for the Oracle9i Application Server edition you are licensed to:
|
 Copyright © 2000 Oracle Corporation. All Rights Reserved. |
|