Technical Training
Oracle Apps 11iTable of Contents
Single Node and Multi Node Installation Part 1
Single Node and Multi Node Installation Part 1 - Page 2
Single Node and Multi Node Installation Part 1 - Page 3Single Node and Multi Node Installation Part 1 Page - 3
Single Node and Multi Node Installation Part 1
Step 7. Set up a shared APPL_TOP In a shared APPL_TOP system, the APPL_TOP is installed on only one node. The other nodes are set up to share that APPL_TOP, making changes to the shared file system immediately visible on all nodes. Using a shared APPL_TOP simplifies the maintenance of your configuration and greatly reduces downtime during maintenance tasks.
Ads
Click Details to see the file system actions for this shared configuration.

The Define File System screen shows the file sharing for the configuration you have described. It identifies the nodes as follows:
§ Install: This is the base node. Its APPL_TOP is available for sharing with other nodes. On subsequent node-specific screens, the wizard prompts for directory paths for each node you mark as Install.
§ Share Existing: A node marked Share Existing does not have its own APPL_TOP. It must share the APPL_TOP of a node marked Install. Click OK to return to the Node Information screen. Then, click Next to continue.
Step 8. Define database type
On the Database Type screen, indicate the kind of database you want to install in the new system and supply the name you will use to identify it.
You can install a fresh database or a Vision Demo database.
§ A fresh database is fully configured and ready for a new implementation. This type of database is suitable for any type of system that requires a fresh database, such as a production system or a test system. The default name for a production database is PROD. If you are installing a database for another use, for example as a test system or a backup system, choose the Fresh Database option and enter a Database Name that reflects that purpose, for example TEST.
§ A Vision Demo database is used for demonstration or training purposes. It contains a fully configured Oracle Applications system that has been implemented and populated with a set of transactions for a fictitious company. The Vision Demo database is set up for multiple-organization use. It is installed with the UTF8 character set to maximize the support for character sets in this release. The default database name is VIS.
Click Next to continue.
Step 9. Set up database installation directory
The Database Install Information screen prompts you for information Rapid Install needs to set up and install the database.
The "Base Install directory" field defaults to a sample directory name, using the operating system syntax for the machine where you started the Rapid Install wizard. In this example, the syntax is for Windows. This directory is the top-level directory that Rapid Install uses to derive the mount points associated with the RDBMS. On a Unix operating system, the screen would look like this.
Notice that the syntax has changed, and there are two fields that are specific to this platform. The Oracle OS User is the account that will own the database server file system. Enter the name of the Oracle OS Group. The Oracle OS User may belong to other groups, but it must belong to this group. Enter a base installation directory on this screen, or click Browse.
Navigate to the new directory, and highlight the path, or enter a path in the Directory field. Click OK to save the changes and return to the Database Install Information screen. Click Cancel to return without making changes. From the Database Install Information screen, click Advanced Edit to review the derived mount points or to change the directory paths.
This screen displays default directories based on the base installation directory you specified on the Database Install Information screen. Accept the defaults or change the derived mount points as needed. Click OK to return to the Database Install Information screen. Then, click Next to continue.
We will continue with the installation in next tutorial Single Node and Multi Node Installation Part 2 which explains about different product license types, country-specific functionality, additional languages and internationalization (NLS) settings.
Oracle Apps 11i
- ERP Overview
- Oracle Apps 11i: Overview of popular ERP Products
- Oracle Apps 11i: Advantages of Oracle E-Business Suite
- Oracle Apps 11i : Getting started with Oracle Applications
- Oracle Apps 11i: Internationalization Support and Multiple Reporting Currencies
- Oracle Apps 11i : File System
- Oracle Apps 11i Installation - System Requirements
- Oracle Apps 11i - Using Rapid install and the Steps Before Apps Installation
- Single Node and Multi Node Installation Part 1
- Single Node and Multi Node Installation Part 2
- Oracle Apps Application Framework
- Oracle Apps Table Registration API
- Oracle Apps Concurrent Processing
- Oracle Apps Concurrent Library Window
- Oracle Apps Message Dictionary
- Oracle Apps Flex fields
- Oracle Apps Implementing Key Flex field and Descriptive Flex field
- Oracle Apps Template Form
- Special Triggers in the Template Form in Oracle Apps 11i
- Creating New Forms in Oracle Apps 11i
- Creation of Master Detail Block in Oracle Apps 11i
- Registering New Forms in Oracle Apps 11i
- Oracle Apps 11i: Setting up Chart Of Accounts (COA)
- Oracle Apps Sys Admin - Users and Responsibilities
- Oracle Apps 11i : Creating Journals through Oracle GL
- Oracle Apps 11i : Suppliers
- Oracle Apps 11i : Asset Management - Asset Book Positioning
- Oracle Apps 11i : Asset Management - Asset Books Regions
- Oracle Apps 11i : Asset Management - Manual and Quick Additions
- Oracle Apps 11i : Asset Management - Mass Additions
- Oracle Apps 11i : Asset Management - Asset Adjustments
- Oracle Apps 11i : Asset Management - Mass Transfers
- Oracle Apps 11i : Asset Management - Depreciation
- Oracle Apps 11i : Asset Management - Retirements
- Oracle Apps 11i : Asset Management - Journal Entries
- Oracle Reports 6i












