|Oracle E-Business Suite Installation Guide: Using Rapid Install|
Release 12.1 (12.1.1)
Part Number E12842-04
This appendix contains details of the fields in the various screens of the Rapid Install wizard. It pays special attention to the configuration values that are not visible in the sample screen shots, and also discusses additional system requirements.
This appendix covers the following topics:
This section lists and defines configuration parameters on the Database Install Information screen, the node-specific configuration information screens, and the Global Settings screen in the Rapid Install wizard. Rapid Install uses these values during an installation or upgrade to set up and configure your system.
Note: See Applications File System in Oracle E-Business Suite Concepts for more information about the directories and subdirectories discussed in this section.
This section lists and describes the values you enter on the database install information screen in the Rapid Install wizard. Rapid Install uses this information to set up the top-level directory and the subdirectories on the database node.
|Input Field Name||Definition|
|Database OS User (UNIX)||The operating system user that owns the Oracle technology stack (including the database).|
|Database OS Group (UNIX)||The Oracle OS user must belong to this group.|
|Base Install directory||The top-level directory that Rapid Install uses to install the RDBMS. All subdirectories (mount points) associated with the RDBMS are derived from this directory.|
|Oracle Home||The location of the 11gR1 database Oracle Home, which contains files for running and maintaining the RDBMS.|
|Data Top (SYS)||Derived from the Base Install directory, this is the mount point for all database system files.|
|Data Top (LOG)||Derived from the Base Install directory, this is the mount point for all database log files.|
|Data Top (TXN)||Derived from the Base Install directory, this is the mount point for all transaction data and index files.|
|Data Top (ARCHIVE)||Derived from the Base Install directory, this is the mount point for all archive, media, advanced queue, summary, and undo files.|
Note: For more information, see Tablespace Management in Oracle E-Business Suite Concepts.
This section lists and describes the fields on the Applications node screens in the Rapid Install wizard. You enter configuration details for these nodes (one or more) on the Primary Applications Node Configuration screen.
|Input Field Name||Definition|
|X Display (UNIX)||This display must always be accessible during runtime. Set it to an active and authorized X Windows display, pointing to a machine that is always available to the instance.|
|UNIX Toolkit Directory (Windows)||Location of MKS tools. Used for relinking executables and DLLs.|
|Visual Studio Directory (Windows)||Location of the Microsoft Visual C/C++ executables and DLLs. Used for linking executables or DLLs.|
|Apps OS User (UNIX)||The operating system user that owns the Oracle E-Business Suite file system and Applications node technology stack.|
|Apps OS Group (UNIX)||The group to which the Apps OS User belongs.|
|Base Install directory||The top-level directory that Rapid Install uses to install the Applications node technology stack . All subdirectory names are derived from this directory.|
|Instance directory||The top-level directory for an Oracle E-Business Suite instance. This directory is referred to as the Instance Home, and denoted by the environment variable $INST_TOP.|
|COMMON_TOP||Holds directories for files used across products or in conjunction with third-party products, including:
|Tools ORACLE_HOME||The OracleAS 10.1.2.3 ORACLE_HOME directory, used for the Developer 10g products (Forms and Reports). Sometimes also referred to as the C ORACLE_HOME.|
|Web ORACLE_HOME||The OracleAS 10.1.3.4 ORACLE_HOME directory, used for the Oracle HTTP Server. Sometimes also referred to as the Java ORACLE_HOME.|
|Temp Directory||Contains temporary files. This directory is not used during installation.|
This section lists and describes the fields on the Global Settings screen in the Rapid Install wizard. Rapid Install uses them to identify the fully qualified domain name, and derive port settings that your system will use to connect all services and listeners.
|Input Field Name||Definition|
|Domain Name||A valid domain name used when configuring Oracle E-Business Suite for the network. This value, when combined with a host (machine) name, must produce a fully qualified domain name (FQDN). For example, a host name of apps1 and domain name of company.com make up an FQDN of apps1.company.com|
|Port Pool||A list of increment settings that you can choose to make the preset port numbers unique. For example, choosing 3 from the list changes port 1521 to 1524.|
|Database Port||Net Services Listener port that receives requests from the various servers for processing on the RDBMS.|
Rapid Install saves the log files associated with the installation or upgrade. They are located in the following directories:
|Database tier log files||<APPS_BASE>/db/tech_st/11.1.0/appsutil/log/<CONTEXT_NAME>/<timestamp>.log|
|Applications tier log files||<APPS_BASE>/inst/apps/<CONTEXT_NAME>/logs/<timestamp>.log|
In Oracle E-Business Suite Release 12.1.1, the fresh database installed by Rapid Install is Oracle 11gR1 (220.127.116.11). It can be used for any purpose, such as a production system or a test system. It is minimally sized, with 100% sizing factor. The default character set is US7ASCII, and the default database block size is 8192 bytes.
Important: Oracle E-Business Suite Release 12.1.1 requires a database block size of 8K. No other size may be used.
The initialization file for the database is located in the $ORACLE_HOME/dbs directory, and is called init<SID>.ora.
In Oracle E-Business Suite Release 12.1.1, all base products are fully installed. However, only basic technology products are automatically registered as being licensed and active. You register all the products in your Oracle licensing agreement using the Rapid Install wizard. During the process of entering initial configuration values on the wizard screens, you can change the character set, and Rapid Install will convert your database accordingly.
The database utilizes the Oracle Applications Tablespace Model (OATM). This streamlined model consists of locally managed tablespaces based on the objects’ input/output characteristics. OATM also provides support for implementing Oracle Real Application Clusters on Linux.
Note: For further details of OATM, see Oracle E-Business Suite System Administrator's Guide - Configuration.
The tablespace sizes shown below are approximate, and may vary from platform to platform.
|APPS_TS_ARCHIVE||Tables that contain archived purge-related data||908|
|APPS_TS_INTERFACE||Interface and temporary data and indexes||1092|
|APPS_TS_MEDIA||Multimedia objects, such as text, video, sound, graphics, and spatial data||1516|
|APPS_TS_NOLOGGING||Materialized views not used for summary management and temporary objects||67|
|APPS_TS_QUEUES||Advanced Queuing and dependent tables and indexes||1048|
|APPS_TS_SEED||Reference and setup data and indexes||3126|
|APPS_TS_SUMMARY||Summary management objects, such as materialized views, fact tables, and other objects that record summary information||1202|
|APPS_TS_TX_DATA||Tables that contain transactional data||5936|
|APPS_TS_TX_IDX||Indexes on transaction tables||7749|
|APPS_UNDOTS1||Automatic Undo Management (AUM) tablespace. UNDO segments are same as ROLLBACK segments when AUM is enabled||1238|
|PORTAL||Single Sign-On SDK||105|
|ODM||Oracle Data Mining||12|
|OWAPUB||Oracle Application Server||10|
|SYSAUX||Stores auxiliary database metadata related to Oracle options and features||463|
|SYSTEM||System tablespace used by the Oracle database||12594|
Note: The above list of tablespaces is not exhaustive.
The Vision Demo database provides a sample set of transaction data for a fictitious company (Vision Corporation). It uses most Oracle E-Business Suite products and is configured for multi-node systems. It is installed with the AL32UTF8 (universal) character set to maximize the number of supported languages.
The database initialization file is located in the $ORACLE_HOME/dbs directory, and is called init<SID>.ora.
Note: The sizes shown in the table are approximate, and may vary from platform to platform.
|APPS_TS_ARCHIVE||Tables that contain archived purge-related data||1154|
|APPS_TS_INTERFACE||Interface and temporary data and indexes||3600|
|APPS_TS_MEDIA||Multimedia objects, such as text, video, sound, graphics, and spatial data||5464|
|APPS_TS_NOLOGGING||Materialized views not used for summary management and temporary objects||602|
|APPS_TS_QUEUES||Advanced Queuing and dependent tables and indexes||4507|
|APPS_TS_SEED||Reference and setup data and indexes||3987|
|APPS_TS_SUMMARY||Summary management objects, such as materialized views, fact tables, and other objects that record summary information||23455|
|APPS_TS_TX_DATA||Tables that contain transactional data.||65802|
|APPS_TS_TX_IDX||Indexes on transaction tables||34050|
|APPS_UNDOTS1||Automatic Undo Management (AUM) tablespace. UNDO segments are identical to ROLLBACK segments when AUM is enabled||3865|
|ODM_DATA||Oracle Data Mining||42|
|OWAPUB||Oracle Application Server||10|
|SYSTEM||System tablespace used by the Oracle database||20225|
The Vision Demo database uses the Multiple Organizations feature. The following table shows the operating units in the database. Responsibilities connect to one of these operating units.
|Vision Project Manufacturing||APPS/APPS|
Note: There are several schemas in the Vision Demo database for other accounts, which are used to demonstrate Oracle E-Business Suite integration with other products. These schemas are not documented here.
Many Oracle E-Business Suite users are predefined in the Vision Demo database. The following username/password pairs have System Administrator responsibility:
Copyright © 2000, 2009, Oracle and/or its affiliates. All rights reserved.