1) If you are installing in an environment where different machines are used to support the database and Applications tiers (as is typically the case), you would run Rapid Install on each machine in turn, starting with the database machine. For example, you might have three machines: one for the database tier and two for the Applications tier. So you would run Rapid Install a total of three times, once on each machine.
2) In a multi-node environment that uses a shared application tier file system, you must run Rapid Install on the primary Applications node first.
3) If you are using a non-shared application tier file system, the order in which you run Rapid Install on the Applications nodes does not matter.
4) In either type of environment, you cannot run Rapid Install on more than one node in an Applications system at once.
5) The main configuration engine used by Rapid Install is called AutoConfig. Rapid Install supplies the configuration information to AutoConfig, which stores the configuration for each node in a node-specific configuration file called a context file.
6) A node is a logical grouping of servers, and therefore fundamentally a software concept rather than a hardware concept, although it is often also used to refer to the machine on which a particular node is installed.
7) A tier is a logical grouping of services, potentially spread across more than one physical machine.
8) Oracle Applications Release 12.1.1 only supports a unified APPL_TOP, i.e. the APPL_TOP is no longer separated into different parts (Concurrent Processing, Forms, Web). However, although all Applications nodes use a unified APPL_TOP, different sets of services can be specified on different nodes. This allows you to create specialized nodes, for example to support Concurrent Processing or Web serving.
9) Oracle Applications Release 12.1.1 requires Oracle Database Enterprise Edition. No other editions are supported.
10)
11)
12)
13)
14)
15)
16)
17)
18)
19)
20)
21)
22)
23)
24)
25)
26)