Oracle9i application server installation guide

The Oracle home name identifies the program group associated with a specific Oracle home and the installed Oracle services associated with the home. The Oracle home name must consist of 1 to 16 characters long and can only include alphanumeric characters and underscores; spaces are not allowed.

See Also: Section 2. Do not install Oracle9 i AS into any of the following directories:. Oracle9 i AS home directory unless it is for an install extension Oracle9 i Database home directory Oracle8 i Database home directory Select the Oracle9 i Application Server installation and click Next. After choosing the Oracle9 i AS install, select one of the three install types listed in Section 3.

Portal and Wireless : Enables the deployment of enterprise portals and wireless applications. Business Intelligence and Forms : Enables analysis of clickstream data, personalization of applications, use of forms-based applications, and deployment of Decision Support System and Web-based reports. Table lists the three installation options for Oracle9 i AS and the Oracle9 i AScomponents that are installed with each option.

The Clickstream Collector Agent is also installed. Select the Oracle9 i AS install type you would like to install and click Next. Figure Installation Types Screen Text description of the illustration installtypesjee. During the installation you will be asked if you would like to use the single sign-on or clustering functionality. An application server cluster is a collection of application server instances with identical configuration and application deployment.

Clusters enforce homogeneity between member instances so that a cluster of application server instances can appear and function as a single instance. With appropriate front-end load balancing, any instance in an application server cluster can serve client requests.

This simplifies configuration and deployment across multiple instances and enables fault tolerance among clustered instances. Clustering enables you to expand your application server capabilities and single sign-on simplifies security over your network.

If you want to use either of these features you need to install Oracle9 i AS Infrastructure first. Information about the application server cluster is maintained in the Oracle9 i AS Infrastructure Metadata Repository. If you are not sure, you can configure for application server clustering and single sign-on later. Prior to installing the Portal and Wireless or Business Intelligence and Forms install types, you must install and configure the Oracle9 i AS Infrastructure somewhere in your network, optimally on a separate machine.

Note: The installation size shown in parentheses for the three Oracle9 i AS install types may vary based on your system settings and file allocation during installation. Accurate install file size is available from the Summary screen in Step 8. Figure Component Configuration and Startup Screen Text description of the illustration compconfum. The Oracle9 i AS components listed for configuration and startup will differ depending on the Oracle9 i AS install type you choose.

If you de-select a component here, then the installer installs it, but does not configure or start it. After installation, the installer starts the selected Oracle9 i AS component. If you want to use existing database metadata, do not select to configure Oracle9 i AS Portal. See Also: Section 3.

Other Oracle9 i AS instances on the installation host are not using single sign-on or clustering functionality. This screen offers two options:.

This screen appears for you to enter information about an existing instance of Oracle9 i AS Single Sign-On that you will be using for your installation of Oracle9 i AS.

Review and note the information provided on the screen. Oracle Internet Directory enables retrieval of shared information about dispersed users and network resources. You will need the following information to add information about an Oracle9 i AS instance into Oracle Internet Directory:. Password: The password for user to access Oracle Internet Directory.

The username and password are defined in Oracle Internet Directory as either the:. If the Oracle Internet Directory administrator does not wish to give out the orcladmin password, the administrator creates a user and password. The administrator then adds this user to the IASAdmins group. The username and password you enter enables the registration of Oracle9 i AS configuration information into Oracle Internet Directory. The default user is orcladmin.

The Oracle Internet Directory administrator may add other users and assign a different password for this group. The following terms may be used on the following three screens:. This password is required for installation of additional Oracle9 i AS instances. Text description of the illustration createinstance. This screen appears if this is a first time installation of Oracle9 i AS on this host.

Enter a unique name in the instance name field for this installation of Oracle9 i AS. The instance name must contain alphanumeric and underscore characters only. Additionally, at least one of the characters must be a number. The unique instance name will be used to identify this installation of Oracle9 i AS on the install host. The existing Oracle9 i AS instance name will be used for this installation.

Text description of the illustration createinstance2. If the Oracle Universal Installer has detected a previous installation of Oracle9 i AS on this host but in a different Oracle home, this screen appears.

If you want to implement application server instance clustering, you must select the metadata repository used by other application server instances in your network. If you do not want to use application server instance clustering, select any listed metadata repository. Your selection will be the default location for Oracle9 i AS component metadata. If you want an Oracle9 i AS component within this Oracle9 i AS installation to use a different database, use the Oracle Enterprise Manager Home Page following installation to change database connectivity.

Oracle9 i AS Reports Services supports distribution of reports via email. To use this feature, you must provide the name of the outgoing mail server. For example:. The Summary screen allows you to review all the settings before the installation begins. These settings include source, destination, installation type, product language, install file sizes, and a list of components. Note: Insufficient disk space is indicated in red under Space Requirements.

When you click Install , the installation process begins. The Install screen appears while the product is installing. The Install screen shows installation operations, including executing actions such as file copy and linking, and executing decision points and calculations. It displays the full path of the installation log. Cancel : Discontinues the installation process. The default user is orcladmin.

The Oracle Internet Directory administrator may add other users and assign a different password for this group. The following terms may be used on the following three screens:.

This password is required for installation of additional Oracle9 i AS instances. Text description of the illustration createinstance. This screen appears if this is a first time installation of Oracle9 i AS on this host. Enter a unique name in the instance name field for this installation of Oracle9 i AS. The instance name must contain alphanumeric and underscore characters only.

Additionally, at least one of the characters must be a number. The unique instance name will be used to identify this installation of Oracle9 i AS on the install host. The existing Oracle9 i AS instance name will be used for this installation. Text description of the illustration createinstance2. If the Oracle Universal Installer has detected a previous installation of Oracle9 i AS on this host but in a different Oracle home, this screen appears.

If you want to implement application server instance clustering, you must select the metadata repository used by other application server instances in your network. If you do not want to use application server instance clustering, select any listed metadata repository.

Your selection will be the default location for Oracle9 i AS component metadata. If you want an Oracle9 i AS component within this Oracle9 i AS installation to use a different database, use the Oracle Enterprise Manager Home Page following installation to change database connectivity. To use this feature, you must provide the name of the outgoing mail server. You can leave this field blank and proceed with the installation. At a later time you can make changes to the outgoing Email server in the Oracle9 i AS Reports Services configuration file at the following location:.

The Summary screen allows you to review all the settings before the installation begins. These settings include source, destination, installation type, product language, install file sizes, and a list of components. Note: Insufficient disk space is indicated in red under Space Requirements.

When you click Install , the installation process begins. The Install screen appears while the product is installing. The Install screen shows installation operations, including executing actions such as file copy and linking, and executing decision points and calculations.

It displays the full path of the installation log. For more information about the installation log, refer to Section 2.

During installation of Oracle9 i AS, the installer prompts you to run the root. Run the root. After you see the Finished running generic part of the root. Full path of local bin directory. You can accept the default or change to a different local bin directory. Review the status of Oracle9 i AS configuration tools and click Next. The Components Configuration and Startup screen appears for components to configure and start. The screen lists the configuration tools for all installed components.

Depending on the configurations selected, you will see some component configuration screens, but no input is required. Monitor the progress of each configuration tool by scrolling down the tools list to review the configuration status of each tool.

The status changes as each component is configured. 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 : Re-executes the configuration script if the configuration of a component fails.

Stop : Quits the configuration process. Exit : Quit the configuration tool and continue with the installation. Review the End of Installation screen. Figure End of Installation Screen Text description of the illustration eoiappsrv.

The End of Installation screen appears at the end of the installation process. It notifies you whether the installation was successful or unsuccessful and provides information about accessing the Oracle9 i AS instance. The Oracle9 i AS Welcome page provides links to demonstrations and information about new features. A complete listing of log files is included in the Oracle9i Application Server Administrator's Guide. You have successfully installed your selected Oracle9 i AS install type.

Proceed to Section 3. The following instructions guide you through the basic postinstallation tasks for Oracle9 i AS. Following successful installation and configuration of Oracle9 i Application Server you must download and install the Oracle9 i Application Server patches. You can download the patches from:.

Select the Patches link. On the patch download form, select Oracle9 i Application Server in the Product Family field and then submit the form. Descriptions of interdependencies between Oracle9 i AS components and configuration dependencies can be found in the Oracle9i Application Server Administrator's Guide.

You can configure additional Oracle9 i AS components after installation. In order to use the following Oracle9 i AS components you must use an existing customer database. Refer to component documentation for the following:. For information on manually starting and stopping of Oracle9 i AS components, refer to component specific documentation. Following installation, the Oracle Universal Installer creates a file showing the port assignments during installation of Oracle9 i AS components.

The installation process automatically detects any port conflicts and chooses an alternative port in the range allocated for that component. The file portlist. You can also view the port numbers by pointing your browser to the Oracle9 i AS Welcome page and selecting the Ports tab. Note: The Oracle Universal Installer allocates the port numbers for the selected components during installation.

If you want to install additional Oracle9 i AS instances, make sure the existing instances are running before attempting to install these additional instances. In order to run a demonstration for a specific Oracle9 i AS component, you must have an Oracle9 i AS installation that contains the component, the component must be configured, and the required component instances must be running.

For more information and run the demonstration software go to the Oracle Enterprise Manager Home Page and click Demonstrations. For further information on postinstallation and configuration tasks, refer to the Oracle9i Application Server Administrator's Guide and component-specific documentation. For information on viewing and installing the documentation, refer to Appendix G, "Installing the Documentation Library". 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. Browse : Navigate through the available directory to select a location for the base directory for your installation. The base directory has the following attributes: Contains the permanent and per-product component files in subdirectories Must be writable by anyone in the same user group installing or deinstalling products on the install computer Enter the location where you would like the base directory to be stored.

You need to run a shell script with root privileges, that is, the orainstRoot. You may need to execute the shell script by typing ". The Root. 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 oraInst. See Table for the location of the orainst. Verify the source path, destination name, and destination path for your Oracle9 i AS installation and click Next.

Source : This is the full path to the products. The installer detects and uses the default values of the products. Do not change the path.