|Oracle® Fusion Applications Installation Guide
11g Release 5 (11.1.5)
Part Number E16600-21
|PDF · Mobi · ePub|
The top-level directory for the Oracle Fusion Applications binaries. You specify a name for this directory at the time of provisioning. This directory includes two mount points:
/net/mount1/appbase for components that will remain read-only after provisioning, and
APPLICATIONS_CONFIG) to contain instances that are configurable after provisioning. This structure aids performance issues and accommodates a "lock-down" of binaries after provisioning. It ensures that the configurable components remain available.
The installation phase that shuts down processes started during a failed phase and performs the necessary cleanup actions. If the automated cleanup fails, you must manually stop all processes except the Node Manager on all hosts including OPMN and Java EE processes before you can run the restore action. Note, however, that you must stop all processes if you are running the cleanup action on the Configure phase
A group of Oracle WebLogic Servers that work together to provide scalability and high availability for applications. A cluster appears as a single Oracle WebLogic Server instance. The Managed Server instances that constitute a cluster can run on the same host or be located on different hosts. Applications are deployed to the cluster, which implies deployment to every Managed Server within the cluster.
The installation phase that creates domains, Managed Servers, and clusters. Configures data sources and performs Node Manager registration of servers on the primordial host and primary host.
The installation phase that performs the configuration actions on a primary or secondary host (or both), registers Managed Servers with the Node Manager on secondary hosts, and creates a web tier instance. If there are no primary or secondary hosts, or if there are only primary hosts, this phase runs, but takes no action.
A host that cannot access the shared storage within the firewall. This type of host is typically used to install the Oracle HTTP Server so that restrictions on communication with components within the firewall can be enforced.
A directory that contains one or more Oracle Fusion Middleware homes or Oracle Fusion Applications homes. This directory has no functional significance other than as a grouping of related Oracle product offerings.
A properties file that is generated the first time you run the
idmConfigTool during the installation and configuration of an Oracle Identity Management environment. Each time you make changes to that environment, the new information is appended to the properties file. This file includes the configuration values that you must supply to the Provisioning Wizard when you create a response file. These values must be included in your response file in order to integrate Oracle Identity Management Components with an Oracle Fusion Applications environment. The
idmConfigTool is located in
/idmtools/bin. The properties file is created in:
See "About Input to the Fusion Applications Provisioning Tool" in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Identity Management (Oracle Fusion Applications Edition). Note that you must run
idmConfigTool from the same location each time to prevent the creation of duplicate
idmDomainConfig.param files that contain only partial information.
/idmtools/bin/idmDomainConfig.param is in a shared location, you can point the Provisioning Wizard to that location so that it can read the values directly from the file. If you do not have direct access, you can copy the file to an accessible location and point the Provisioning Wizard to that location. You specify the path to the properties file on the Installation Location screen when you create the response file.
The installation phase that installs middleware and applications components and applies database patches shipped with provisioning (for databases created with the wizard).
A server which hosts components and associated resources that constitute each product configuration. The domains are predefined to ensure that product offerings and their dependencies are always stored in a standardized arrangement.
Installation phase which configures Oracle SOA Suite composite deployment and Oracle HTTP Server, and populates policies and grants. Configures middleware and applications that require servers to be online.
The installation phase that updates the Oracle Application Development Framework (Oracle ADF) configuration.
The installation phase that checks to see that the prerequisites for an installation are met.
The host that contains the Common domain (and specifically the Administration Server of the Common domain). There is one, and only one, primordial host per shared drive.
Groups of features within an installation of Oracle Fusion Applications which represent the highest-level collection of functionality that you can license and implement.
A collection of one or more product offerings.
Provisioning Command-line Interface (CLI)
A repository which contains all the installers required to provision a new Oracle Fusion Applications environment. You download the repository from the Oracle Fusion Applications Product Media Package and extract the files to a location of your choice, for example
/installers. The repository must be located on a networked drive or a shared hard disk so that it is accessible to all the hosts in your new environment.
provisioning summary file
A file which contains details that describe the installation. It is automatically created by provisioning after the installation is complete and includes a link to the Oracle Fusion Applications home page.
A question-and-answer interview that guides you through the process of installing a database, creating or updating a response file, and installing or deinstalling the components of an Oracle Fusion Applications environment.
A collection of configuration details you specify about installation locations, product offerings and middleware (technology stack) dependencies. In addition, you enter connection parameters for the database and identity management components that you set up as prerequisites. You use the Provisioning Wizard interview to create and execute the response file.
The installation phase consisting of the necessary restore actions required for a given provisioning phase. This action deletes and restores the instance directory, and, if necessary (and available), restarts the Common Domain Administration Server and Oracle HTTP Server.
Location where the Managed Servers for any application reside when they are not on the same host as the Administration Server of the same domain. Typically used when a domain spans two physical servers.
Installation phase that starts the Administration Server and the Managed Server on the current host. Performs online configuration, including global unique identifier (GUID) reconciliation and Financial/IPM configuration.
Installation phase that validates the deployment configuration and starts the Managed Server.
WebLogic Server Domain
A logically related group of Oracle WebLogic Server resources that is managed as a unit. It consists of an Administration Server and one or more Managed Server.