This section includes the following topics:
Oracle Fusion Applications Provisioning orchestrates the physical installation and configuration of the selected product offerings and deploys those offerings and their dependent middleware components to a predetermined Oracle WebLogic Server Domain. To perform the installation tasks, provisioning requires the provisioning repository of installers, the provisioning framework, and a response file.
When a response file is created, choose provisioning configurations and specify the configuration details for the product offerings and their dependent middleware components. Save the response file and specify its location when it is ready to be used to provision a new environment.
The provisioning repository must have been downloaded, the provisioning framework must be installed, and a database and the identity management components must be also installed before creating a response file. See Preparing the Oracle Fusion Applications Server for provisioning prerequisites.
After the prerequisite setup is complete, run the Provisioning Wizard and select the Create a New Applications Environment Response File option. During the interview process, choose the product offerings to install. The wizard knows which middleware dependencies must be installed for each product offering, and which host must be provisioned first. It detects common products that each offering relies on, as well as the presence of the transaction database and identity-related components, and prompts for the appropriate configuration parameters.
Using a question and answer interview format, the wizard collects information about:
Provisioning configurations (product offerings)
Node Manager credentials and installation and configuration directories
Database connections and schema passwords
Host names and ports for the offerings and their middleware dependencies
Common configuration details for components, such as web tier, virtual hosts, email, and identity management
After completing the response file, save it. Then, to perform the physical installation, choose the Provision a New Environment option from the Provisioning Wizard and indicate the location of the response file. The wizard uses the details in the response file as a guide to what must be retrieved from the provisioning repository.
An installation of Oracle Fusion Applications is logically broken up into groups of features known as product offerings, which represent the highest-level collection of functionality that can licensed and implemented. A provisioning configuration is a collection of one or more product offerings.
Product offerings have interdependencies on companion applications (for example Oracle Fusion Human Capital Management relies on Oracle Financials payroll), as well as middleware dependencies (for example, Oracle SOA Suite) required for runtime execution. The wizard prompts for applications and middleware configuration details at the domain level during Domain Topology Configuration.
When individual product offerings are selected within a configuration instead of selecting all offerings within the configuration, the wizard starts the Managed Servers only for the offerings selected. However, because the interdependent details for the entire configuration are included in the response file, it is possible to activate additional functionality later by using the Oracle Fusion Applications Functional Setup Manager to start the other Managed Servers.
The provisioning configurations are as follows:
Oracle Fusion Customer Relationship Management (Sales and Marketing)
Oracle Fusion Financials (Financials, Oracle Fusion Procurement, and Oracle Fusion Projects)
Oracle Fusion Accounting Hub
Oracle Fusion Human Capital Management (Workforce Deployment, Workforce Development, and Compensation Management)
Oracle Fusion Supply Chain Management (Product Management, Order Orchestration, Material Management and Logistics, Supply Chain Financial Orchestration, Manufacturing and Supply Chain Material Management, Price Management)
Choose also several standalone product offerings. For this group of offerings, only the direct dependencies are installed, configured, and deployed:
Customer Data Hub
Enterprise Contracts
Oracle Fusion Accounting Hub
Oracle Fusion Incentive Compensation
Value Chain Planning
During the Provisioning Wizard interview process, the wizard collects information that is necessary to connect to the Oracle Identity Management components previously installed and configured. This information includes:
The user designated as the Super User. This user must already exist in the policy store.
The existence of the system administrators group. This information determines if the group was created during the Oracle Identity Management component installation and configuration process, or if it must be created during provisioning.
The distinguished name (DN) of the system administrators group (if it exists).
The authenticator that serves as the LDAP identity store: Oracle Internet Directory (OIDAuthenticator).
There are numerous scenarios for the environments than can be created from a small demonstration system to a full production system provisioned on multiple hosts. The Provisioning Wizard can accommodate the creation of response files for specific environments so that a separate response file can be created for each type of environment. Note that all occurrences of a hostname should use the same name in the response file.
Frequently, details for a response file are not final, and so cannot be specified during a single pass through the Provisioning Wizard interview. Or, a completed response file has not been implemented, and requires changes before it is. The wizard options include the choice to save a partially completed response file and update it later. Note that a response file is not complete or available for provisioning until clicking Finish on the Summary screen.
However, after selecting product offerings and saving them in a response file, regardless of whether it is partially or fully complete, the product offerings cannot be updated or changed in that response file. To add or change the mix of offerings, create a new response file and specify the new or additional offerings.
Before creating a response file, the following tasks must be completed:
Complete the wizard interview screens and save the response file in a location that is accessible to the various installers. Record the location, as it must be supplied during the provisioning of the environment. Note that he response file should be created on the Primordial host, which is the host that contains the Administration Server of the Common domain.
The wizard warns if it cannot connect to the database or any of the hosts specified in the response file and if any of the passwords are not valid. If this warning represents an exception, ignore it and continue creating the response file. However, all issues flagged in the warnings must fixed before starting to provision an environment. Provisioning cannot be successfully run until all validations have passed.
The Provisioning Wizard supports the following command line options:
Table 12-1 Provisioning Wizard Command Line Options
| Command Line Option | Description | Default Value |
|---|---|---|
|
|
Location of the |
|
|
- |
Disables validation for database, schema and hosts. Most validation errors are ignored. Note: |
false |
|
|
Displays help text. Note: The |
Usage:
provisioningWizard.sh -invPtrLoc <inventory pointer location file>
-ignoreSysPrereqs {true|false}
-help
To start the Provisioning Wizard, do the following on the primordial host:
Example 12-1
provisioningWizard.sh -invPtrLoc /oracle/oraInst.loc -ignoreSysPrereqs
Table 12-2 shows the steps necessary to create a response file using the Provisioning Wizard. For help with any of the screens, click Help.
WARNING: If the correct values required are not entered, the error and warning messages are displayed at the bottom of the screen.
Table 12-2 Creating a Response File
| Screen | Description and Action Required |
|---|---|
|
Welcome |
No action is required on this read-only screen. Click Next to continue. |
|
Specify Central Inventory Directory |
This screen displays only if one or more of the following conditions are not met:
Specify the location of the Central Inventory Directory that meets the previous criteria. The For non-Windows platforms, in the Operating System Group ID field, select or enter the group whose members are granted access to the inventory directory. All members of this group can install products on this host. Click OK to continue. The Inventory Location Confirmation dialog prompts to run the To continue the installation without root access, select Continue installation with local inventory. Click OK to proceed with the installation. For Windows platforms, this screen displays if the inventory directory does not meet requirements. For more information about inventory location files, see Oracle Universal Installer Inventory in the Oracle Universal Installer User's Guide. Click Next to continue. |
|
Installation Options |
Presents the list of valid installation actions that can be performed using the wizard. Select Create a New Applications Environment Response File. Click Next to continue. |
|
Specify Security Updates |
Set up a notification preference for security-related updates and installation-related information from My Oracle Support. This information is optional.
Click Next to continue. |
|
Provisioning Configurations |
Select one or more offerings, either within a configuration, or from the list of standalone product offerings. Tip: This value is available in the Oracle Fusion Applications Installation Workbook, Provisioning tab, Fusion Applications Offerings table. Select individual product offerings within a configuration, without selecting all available offerings. When individual product offerings are specified, provisioning starts the Managed Servers only for the offerings that have been selected. However, because interdependent details have been specified for the entire configuration, additional functionality can be turned on later. The additional functionality are turned on by using the Oracle Fusion Applications Functional Setup Manager to start the other Managed Servers. Click Details in the message pane to see a breakdown of servers for each offering. After clicking Next, selections cannot be changed on this screen. To make changes, click Cancel, open a new wizard session, and create a new response file Click Next to continue. |
|
Response File Description |
Enter information to describe this response file. This description is not associated in any way with the executable plan file, or the summary file, that has been saved at the end of the response file creation process.
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Installation Location |
Specify credentials for the Node Manager and supply the location of the various directories required for installation and configuration actions. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
System Port Allocation |
Accept the default values or set a custom value for the Applications Base Port. The application domain port ranges are derived from this value. If the base port value is changed, the domain port ranges adjust accordingly. Ranges must not overlap and must be set in ascending order. Ports listed under Other Ports are not derived from the Applications Base Port value. These individual ports can be defined using custom port values. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Database Configuration |
Enter the database parameters established when the Oracle Database was installed. The wizard validates whether the installed database is a single-instance or Oracle Real Application Clusters (Oracle RAC). If a Single Instance Database, enter:
If Oracle RAC has been installed using Multi Data Sources, select Multi Data Sources Real Application Clusters Database and enter the following values:
Click Add to create a new row in the table for each instance. Select a row and click Remove to delete it. Tip: This value is available in the Oracle Fusion Applications Installation Workbook , Database tab, FA Transactional Database table. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Schema Passwords |
The database that is installed contains preloaded schemas required for runtime execution. Select one of the following options and enter the database schema passwords set up when the Oracle Fusion Applications Repository Creation Utility was run. See Table 8-4.
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
ODI Password Configuration |
Enter and confirm the ODI supervisor password. The ODI Supervisor Password is the Supervisor Password entered on the Custom Variables page during execution of Applications RCU under the Primary and Work Repository component. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Domain Topology Configuration |
To determine the flow for the remaining wizard interview screens, choose one of the options. The types of possible topologies are:
Note that all hosts must use the same operating system. For example, domain1 cannot be installed on Windows and domain2 on Linux. Note that any of the Oracle Identity Management hosts cannot be used as the host in the Domain Topology Configuration. Installing Oracle Identity Management and Oracle Fusion Applications on the same host is not a supported topology. See Domain Topology Configuration. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Common Domain |
Note: Individual domain screens appear only if the One host per application and middleware component option is selected on the Domain Topology Configuration screen. Specify values for this domain and its middleware dependencies. All hosts must use the same operating system and share a common mount point for network storage. The host specified for the Admin Server is the default for all servers. The default host can be changed.
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Product Family Domains |
Note: Individual domain screens appear based on which options are selected on the Domain Topology Configuration screen. For example, the Incentive Compensation Domain screen does not appear unless that product offering is selected for installation. All product family domain screens prompt for the same types of values. Specify values for this domain and its middleware dependencies. All hosts must use the same operating system and share a common mount point for network storage. The host specified for the Admin Server is the default for all servers. The default host can be changed.
Note: See Oracle Business Intelligence Configuration for Oracle Business Intelligence configuration requirements. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Web Tier Configuration |
Use this screen to configure Oracle HTTP Server and choose a virtual host type. The web tier can be deployed to a host inside the firewall, or outside the firewall (demilitarized zone, known as DMZ). See Web Tier Configuration for the list of parameters. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Virtual Hosts Configuration |
Provisioning determines the application domains to be deployed based on the product offering choices and lists them on this screen. Specify domain-specific values for the type of virtual host mode that are selected on the Web Tier Configuration screen. See Virtual Hosts Configuration for the list of parameters. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Load Balancer Configuration |
Load balancing enables the distribution of a workload evenly across two or more hosts, network links, CPUs, hard drives, or other resources. Check Enable Load Balancing to take advantage of this feature, and specify:
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Web Proxy Configuration |
Create Proxy Settings to enable users who want to use a proxy server to connect to the Internet. See Web Proxy Configuration. Take note of the special instructions for Oracle Customer Relationship Management customers. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
IDM Properties File |
When a response file is created or an incomplete response file is updated without updates to this page, the IDM properties file can be selected to load IDM configuration data. After the file is selected, the content can be reviewed and a decision to proceed with this file can be made. WARNING: The file can be reviewed and a different file can be selected, if it is required on this screen. An IDM properties file cannot be selected after clicking Next, as the screen displays read-only fields. Disable loading IDM Configuration from IDM Properties file: Select this option to avoid loading the IDM configuration data from the IDM properties file. Load IDM Configuration from IDM Properties file: Select this option to set the values on the Identity Management Configuration screen and the Access and Policy Management Configuration screen to the default values in the IDM properties file (for example, IDM Properties file: Enter the location of the file, for example, IDM Properties file contents: If a valid IDM properties file is selected, the contents are displayed. This field is read-only and cannot be modified. Click Next to continue. |
|
Identity Management Configuration |
Provisioning loads the roles, policies, and application IDs that are created during the prerequisite Oracle Identity Management installation. To share the identity management environment across multiple Oracle Fusion Applications installations, and make the policies and roles accessible to all environments, populate identity management configuration details during the first installation. See Identity Management Configuration for the list of parameters. See also Distinguished Names for information about Distinguished Names conventions. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Access and Policy Management Configuration |
Configure Oracle Fusion Applications for integration with existing Oracle Access Manager components. See Access and Policy Management Configuration for the list of parameters. To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue. |
|
Summary |
Displays the applications and middleware components that are installed when a physical installation is performed using this response file. Includes details such as required disk space and the installation locations. See Summary for a description of the parameters. Click Finish to save the response file. The response file is complete and can be used as the basis for provisioning of a new environment. |
Specify credentials for the Node Manager and supply the location of the various directories required for installation and configuration actions on the Installation Location screen. The credentials provided are used to configure the NodeManager, secure WebLogic Server and OWSM keystores and wallets on the file system.
Ensure to use the specified user name and password to connect to the NodeManager for starting and stopping servers.
Node Manager Credentials
User Name: Specify a user name for the Node Manager role.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, Identity Store / Policy Store table, FA Node Manager Username row.
Password: Specify a password for the Node Manager and retype it in the Confirm Password field.
Installation and Configuration
Provide locations of various directories that the administrator needs access to. Enter the full file path in the Provisioning Wizard UI when asked to provide any file path, such as Oracle Fusion Applications Home, Applications Configuration Directory, and so on. Using symbolic link paths causes provisioning to fail in later phases.
Installers Directory Location: Enter the path to the repository_location directory where the Oracle Fusion Applications software is extracted. This software is obtained from the media pack downloaded from the Oracle Software Delivery Cloud Portal.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Storage tab, Temporary Shared Storage table, Installers Directory Location row.
Applications Base: Enter the directory path to the applications base directory. The top-level directory for the Oracle Fusion Applications binaries is the applications base and is referred to as the APPLICATIONS_BASE directory (net/mount1/appbase). See Oracle Fusion Applications Oracle Home Directory.
The applications base directory must not be set to the system root directory or set to the root directory of a logical drive. Some lifecycle management tools compute directory names by backing up one directory level from the applications base directory and then appending the appropriate subdirectory name. These tools fail if the applications base directory is set to the system root directory or set to the root directory of a logical drive because it is not possible to back up one directory level from the system root directory or from the root directory of a logical drive.
During creation of a provisioning plan in a UNIX environment, ensure that the absolute file path of the APPLICATIONS_BASE directory does not exceed 59 characters before provisioning a new application environment.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Storage tab, Install Directories table, FA Applications Base row.
Applications Configuration: This directory is automatically populated based on the value specified in the Applications Base field. It is the path to the directory where the configuration files for the domain are written. It is possible to specify a different location instead of using the location automatically populated by the UI. This directory must be empty.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Storage tab, Install Directories table, FA Applications Configuration Location row.
Enable Local Applications Configuration: Select this checkbox to run the Managed Servers from a non-networked (local) disk on the host, visible only to the processes running on that host. If this option is enabled, the wizard copies the domain configuration from the shared location and places it on the specified local disk. This configures all Managed Servers to run from the non-networked location.
Local Applications Configuration: Specify the location for the local domain directory to be set up. This field is required if the option Enable Local Applications Configuration is selcted. The specified directory must exist and initially be empty on every host that participates in the domain topology. Ensure the directory has sufficient disk space. During the Preverify phase, provisioning displays an error if the local configuration directory does not have sufficient disk space.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Storage tab, Install Directories table, FA Local Applications Configuration Location row.
Middleware Dependencies
Font Directory: Appears only if Oracle Sales, Oracle Marketing, or Oracle Financials offerings are selected. Enter the directory where the TrueType fonts are installed. The location varies on different operating systems, but is typically found here:
Linux x86-64: /usr/X11R6/lib/X11/fonts/TTF
Oracle Solaris: /usr/X11R6/lib/X11/fonts/TrueType
Some systems may not have TrueType fonts installed. If the fonts cannot be located on the system, verify that they have been installed. In addition, use the fonts directory shipped as part of the JRE installed in the repository. Regardless of which path is specified, access to.ttf files.
Oracle Business Intelligence Repository Password
RPD Password: Specify and Confirm a password to allow access to the metadata repository (RPD) for both Oracle Business Intelligence Applications and Oracle Transactional Business Intelligence. The password must be between 8 and 30 characters and contain at least one digit. It can include letters, numbers, pound sign (#), dollar sign ($), or underscore (_). Toinclude two consecutive dollar signs ($$) in the RPD password, enter one additional dollar sign ($) as the escape character before the second dollar sign in the password. This means it is necessary to enter three dollar signs ($$$) for this field in the Provisioning Wizard to indicate two consecutive dollar signs. Provisioning sets up this password, but does not actually access the repository.
Accept the default values or set a custom value for the Applications Base Port. The application domain port ranges are derived from this value. If the base port value is changed, the domain port ranges adjust accordingly. Ranges must not overlap and must be set in ascending order.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Fusion Applications Port Numbers table, Fusion Applications Base row.
Ports listed under Other Ports are not derived from the Applications Base Port value. These individual ports can be defined using custom port values.
Tip:
Node Manager: This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Fusion Applications Port Numbers table, FA Node Manager row.
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment. Click Next to continue.
If there are other software running on the provisioning hosts, ensure that the system port allocation value in the provisioning response file is not a port already used by other software. The system port allocation cannot be changed after starting provisioning a new Oracle Fusion Applications environment. If a port conflict is detected during provisioning phases, restart provisioning from the beginning with a correct set of system port allocation. See Installation Phases and Types of Hosts in a Multiple-Host Environment.
To display a list of network connections including the port numbers and process identifier holding the ports, run these commands:
UNIX: netstat -anp
To determine the flow for the remaining wizard interview screens, choose one of the topology types. Note that all occurrences of a hostname should use the same name in the response file. A machine name could be a logical or virtual host name. It can either be in fully qualified form, mymachine.mycompany.com, or short form, myMachine, if it is consistent throughout the response file. See Edit Host Names (UNIX).
The types of possible topologies are:
Basic Topology: One host for all domains
Medium Topology: One host per domain
Advanced Topology: One host per application and middleware component
MANDATORY: Install Oracle Identity Management and Oracle Fusion Applications on different hosts. Installing Oracle Identity Management and Oracle Fusion Applications on the same host is not a supported topology.
One host for all domains: Select this option to specify the Host Name to provision all applications domains and their middleware dependencies on a single host. The wizard continues the interview at the Web Tier Configuration screen after clicking Next.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Environment tab, Environment Info table, FA Topology Type row :
For Basic topology, Select One Host For All Domains.
This value is available in the Oracle Fusion Applications Installation Workbook, Topology tab, Component Assignment table:
All Components below must have the same node number in the Oracle Fusion Applications Installation Workbook, use the abstract hostname (or real hostname if absract is blank) that corresponds to that node # in the Topology table:
FA Common Domain
FA CRM Domain
FA Financials Domain
FA HCM Domain
FA IC Domain
FA Procurement Domain
FA Projects Domain
FA Supply Chain Domain
FA Business Intelligence Domain
One host per domain: Select this option and then select a Host Name for each domain to be created. Provisioning installs and configures the Managed Servers for each Application Domain and the middleware dependencies on the host that is specified. The wizard continues the interview at the Web Tier Configuration screen after clicking Next.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Environment tab, Environment Info table, FA Topology Type row:
For Enterprise topology, select One Host Per Domain.
This value is available in the Oracle Fusion Applications Installation Workbook, Topology tab, Component Assignment table:
Use the abstract hostname (or real hostname if abstract is blank) that corresponds to the node # for the following components in the Topology table:
FA Common Domain
FA CRM Domain
FA Financials Domain
FA HCM Domain
FA IC Domain
FA Procurement Domain
FA Projects Domain
FA Supply Chain Domain
FA Business Intelligence Domain
One host per application and middleware component: Select this option to specify the host for each application and middleware component individually. The wizard displays the Common Domain screen after clicking Next, and includes all domain-specific screens in the interview.
This topology is not covered in the Oracle Fusion Applications Installation Workbook by default, but it possible to use it as part of an Enterprise or Enterprise HA example topology.
If the last option is selected, the selections cannot be changed on this screen after clicking Next. Click Cancel, open a new wizard session, and create a new response file to change the configuration domain topology later.
Oracle Business Intelligence products are integrated with, and accessible from, Oracle Fusion Applications. Products include:
Oracle Business Intelligence Enterprise Edition
Oracle Business Intelligence Applications
Oracle Transactional Business Intelligence
Oracle Essbase
Oracle Business Intelligence Publisher
Oracle Real-Time Decisions
Enter the Host where the Oracle Business Intelligence products are installed. An RPD password is specified on the Installation Location screen. Provisioning creates this password and makes it available so that Oracle Business Intelligence Applications and Oracle Transactional Business Intelligence can access the metadata repository in the new environment.
The Oracle Fusion Applications installation and provisioning process installs the Oracle BI Applications software components in the Business Intelligence Oracle home but does no further setup. To finish setting up Oracle BI Applications, follow the instructions in the Installing and Setting Up Oracle BI Applications in the Oracle Business Intelligence Applications Installation Guide.
Virtual hosts can be created on a single web tier. There are three options (IP-based, name-based, and port-based) for each domain that is created during installation. The values assigned during installation are derived from the default HTTP port specified on this screen. Note that all occurrences of a hostname should use the same name in the response file. A machine name could be a logical or virtual host name. It can either be in fully qualified form, mymachine.mycompany.com, or short form, myMachine, if it is consistent throughout the response file. See Edit Host Names (UNIX).
Web Tier
Install Web Tier in DMZ: Select this option if a separate host is setup for web tier installation as a demilitarized zone (DMZ). This host does not have access to the shared file system. It cannot be used for any other host deployed, regardless of domain. See Setting Up a Demilitarized Zone (DMZ) for the Web Tier.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Topology tab: Verify if the DMZ (Yes/No) column has the value Yes for the node that corresponds to the component FA WebTier.
Fusion Applications Web Tier
Host: Enter the name of the host where Oracle HTTP Server is installed and configured.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Topology tab: Use the Abstract Host Name column (or real hostname if abstract is blank) for the node that corresponds to the component FA WebTier.
Virtual Host Mode: Select one of the following:
IP Based: Created on the basis of an IP or IP:host combination (the default).
Name Based: Create new DNS entries, such as fin.example.com and crm.example.com to use as virtual hosts.
Port Based: Created based on the internal and external port for each domain.
WARNING: In the Provisioning Wizard, do not choose the Name Based virtual host mode if it has been planned to specify Load Balancer Configuration details on the next page. This combination is not recommended as it requires manual changes during Oracle Fusion Applications Provisioning. Setting up Name Based virtual hosts is not recommended if a Load Balancer is used.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Virtual Hosts tab, WebTier Virtual Host Mode table, FA WebTier row, Mode column.
Domain Name: Specify a domain name (using the format my.example.com) to configure the domain in which Oracle Fusion Applications receives requests. This value is also used as the default domain name for name-based virtual hosts.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Environment tab, Environment Info table, Domain name row.
HTTP Port: The default port for the web tier. UNIX: Do not specify a port that requires operating system administrator privileges.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Fusion Applications Port Numbers table, FA Oracle HTTP Server row.
HTTPS (SSL) Port: Secure port for the web tier. UNIX: Do not specify a port that requires operating system administrator privileges.
WARNING: On UNIX platforms, using a port below 1024 requires root privileges and Provisioning is not run as root user, so a HTTP/HTTPS port below 1024 should not be specified.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Fusion Applications Port Numbers table, FA Oracle HTTP Server SSL row.
CRM Marketing Web Tier
If the Oracle Fusion Customer Relationship Management offering is selected in the Provisioning Configurations Screen, the CRM Marketing Web Tier group with the following fields is displayed:
Host: Enter the name of the host where the Oracle HTTP Server dedicated for CRM Marketing web tier is installed and configured.
Virtual Host Mode: Select one of the following:
IP Based: Created on the basis of an IP or IP:host combination.
Name Based: Create new DNS entries, such as fin.example.com and crm.example.com to use as virtual hosts.
Port Based: Created based on the internal and external port for each domain.
The default is to create an IP-based host.
Domain Name: Specify a domain name (using the format my.example.com) to configure the domain in which Oracle Fusion Applications receives requests. This value is also used as the default domain name for name-based virtual hosts.
HTTP Port: The default port for the web tier. It should not require operating system administrator privileges.
HTTPS (SSL) Port: Secure port for the web tier. It should not require operating system administrator privileges.
SMTP Server
Host: Specify the host for email marketing. This field appears only if the Oracle Fusion Customer Relationship Management offering.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Environment tab, Email Server table, SMTP Server Host row.
Port: Default port for the SMTP server.
Load balancing enables to distribute a workload evenly across two or more hosts, network links, CPUs, hard drives, or other resources.
Load Balancing Enabled: This checkbox is selected by default. Keep it checked if load balancer is used in front of the Oracle Fusion Applications environment. Ensure that the load balancer configuration is completed as described in Planning Load Balancer Requirements before proceeding and then specify the following:
Internal Load Balancer Configuration: The host and port for the internal Virtual IP (VIP).
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Virtual Hosts tab, HTTP LBR Endpoints table.
External Load Balancer Configuration: The host and port for external Virtual IP (VIP). It must have a publicly available address to be usable.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Virtual Hosts tab, HTTP LBR Endpoints table.
To stop creating this response file and resume later, click Save. This action creates a partial response file. A partial response file cannot be used to provision an environment.
Click Next to continue.
Specify the configuration parameters for the domains to be installed on the virtual hosts that are selected on the Web Tier Configuration page. Note that all occurrences of a hostname should use the same name in the response file. A machine name could be a logical or virtual host name. It can either be in fully qualified form, mymachine.mycompany.com, or short form, myMachine, if it is consistent throughout the response file.
If the Oracle Fusion Customer Relationship Management offering is selected in the Provisioning Configurations Screen, the corresponding section IP-Based Virtual Host for CRM Marketing with the following fields are displayed:
Application Domain: The name of the Oracle Fusion Applications domain to be provisioned.
External Name: The host name or IP address for the external virtual host for this domain or middleware dependency. The host:port should be visible from outside the firewall.
External Port: Port to be used for this external virtual host. The host:port should be visible from outside the firewall.
If the IP Based option is selected, specify the following information for each application domain listed:
Tip:
These values are available in the Oracle Fusion Applications Installation Workbook, Network - Virtual Hosts tab, FA WebTier Virtual Hosts table.
Internal Name: The host name where the web tier listens on the internal virtual host for this domain. The host name can consist of letters A through Z (upper or lower case), digits 0 through 9, minus sign (-) and period (.). The first character must be a letter and the last character must not be a minus sign or a period.
Internal Port: The port for this internal virtual host. Visible only from inside the firewall.
External Name: The host name for the external virtual host for this domain or middleware dependency. The host name can consist of letters A through Z (upper or lower case), digits 0 through 9, minus sign (-) and period (.). The first character must be a letter and the last character must not be a minus sign or a period. The host:port should be visible from outside the firewall.
External Port: The port to be used for this external virtual host. The host:port should be visible from outside the firewall.
If the Name Based option is selected, specify the following information for each domain listed:
Internal.Name: The DNS name for this internal virtual host. For example, for Oracle Fusion Financials, the name might be fin-internal.
External.Name: The DNS name for this external virtual host. For example, for Oracle Fusion Financials, the name might be fin.
If the Port Based option is selected, specify the following information for each domain listed:
Internal Port: The port that is visible only from inside the firewall for this domain.
External Port: The port that is visible from outside the firewall for this domain.
Create Proxy Settings to enable users who want to use a proxy server to connect to the Internet.
Tip:
These values are available in the Oracle Fusion Applications Installation Workbook, Environment tab, Web Proxy table.
Enable Web Proxy: Select to enable proxy-related values to set up access to the Internet. Note: For CRM customers, who have a web proxy for external HTTP(S) traffic, select Enable Web Proxy on this screen and specify the web proxy configuration.
Web Proxy Host: Enter the name of the host where the proxy server is installed.
Web Proxy Port: The listening port assigned to the proxy server.
Enable Secure Web Proxy: Select to have the proxy server SSL-enabled. If this check box is selected, the Secure Web Proxy Host and Secure Web Proxy Port fields are enabled and become mandatory.
Secure Web Proxy Host: Enter the SSL host used for secure communications.
Secure Web Proxy Port: Enter the SSL port used for internal communications.
No Proxy Hosts: Defaults to hosts that are connected directly. If there are multiple hosts, they are listed and separated by a vertical bar (|). A wildcard character (*) can be used to specify hosts that should be bypassed. For example,, *.example.com would bypass all hosts whose name ends with .example.com. The localhost value cannot be entered.
Proxy Server Requires Authentication: To enable authentication for the proxy server, select this option.
User Name: Enter the user name that is set up for accessing the proxy server.
Password: Enter the password that is set up for accessing the proxy server.
A Distinguished Name (DN) identifies an entry in a Lightweight Directory Access Protocol (LDAP) directory. Because directories are hierarchical, DNs identify the entry by its location as a path in a hierarchical tree (much as a path in a file system identifies a file). Generally, a DN begins with a specific common name, and proceeds with increasingly broader areas of identification until the country name is specified.
Table 12-3 provides definitions for distinguished name components (defined in the X.520 standard).
Table 12-3 Distinguished Name Components
| Component | Definition |
|---|---|
|
Common Name (CN) |
Identifies the person or object defined by the entry. For example, |
|
Organizational Unit (OU) |
Identifies a unit within the organization. For example, |
|
Organization (O) |
Identifies the organization where the entry resides. For example, |
|
Locality (L) |
Identities the place where the entry resides. The locality can be a city, county, township, or any other geographic region. For example, |
|
State of Province Name (ST) |
Identifies the state or province in which the entry resides. For example, |
|
Country (C) |
Identifies the name of the country where the entry resides. For example, |
|
Domain Component (DC) |
Identifies the components of a domain. For example, if the domain is |
When a response file is created or an incomplete response file is updated without updates to this page, it is possible to select the IDM properties file to load Oracle Identity Management configuration data. After selecting the file, review the content and decide if proceeding or not with this file.
WARNING: Review the file and select a different file if required on this screen. An IDM properties file cannot be selected after clicking Next, as the screen displays read-only fields.
Do not load IDM Configuration from IDM Properties file: Select this option to avoid loading the IDM configuration data from the IDM properties file.
Load IDM Configuration from IDM Properties file: Select this option to default the values on the Identity Management Configuration screen and the Access and Policy Management Configuration screen to the values in the IDM properties file (for example, idmsetup.properties). For more information about the IDM properties file, see Pass Configuration Properties File to Oracle Fusion Applications.
IDM Properties file: Enter the location of the file, for example, SHARED_CONFIG_DIR/fa/idmsetup.properties, where SHARED_CONFIG_DIR is the shared configuration location selected on the Install Location Configuration page of the Oracle Identity Management Provisioning Wizard.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, IDM Provisioning Files tables, IDM Properties File Location row.
IDM Properties file contents: If a valid IDM properties file is selected, the contents are displayed. This field is read-only and cannot be modified.
Enter the parameters necessary to integrate applications with a previously installed Oracle Identity Management infrastructure. If the values in the IDM properties file (for example, idmsetup.properties) are chosen on the IDM Properties File screen to be used, they appear as defaults in the corresponding fields. The default values can be changed if the original configuration has changed.
Super User Name: By default this field contains the value FAAdmin. Enter the name of an existing user that should be granted administrator and functional setup privileges. The uid attribute must be set to be the same as the cn attribute.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, Identity Store / Policy Store table, FA Super User Name row.
Create Administrators Group: Indicate whether an Administrators group was created, whose members have specialized privileges for all Oracle Fusion Middleware components. If this group is not already present in the identity store, this box should be checked.
Create Monitors Group: Indicate whether a Monitors group was created, whose members have read-only administrative privileges to Oracle WebLogic Server domains. If this group is not already present in the identity store, this box should be checked.
Create Operators Group: Indicate whether an Operators group was created, whose members have Monitors privileges to Oracle WebLogic Server domains. If this group is not already present in the identity store, this box should be checked.
Identity Store Server Type: Indicate the type of identity store that was set up during Oracle Identity Management provisioning. The available options are OID (Oracle Internet Directory) or OVD (Oracle Virtual Directory). If OVD is selected, the Default to Identity Store check box in Oracle Platform Security Services Configuration must be unchecked and the policy store cannot be the same instance as the identity store. Using OVD for policy store is not currently supported.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, Identity Store / Policy Store table, ID Store Type row.
Use SSL to Communicate With Identity Store: This feature is not enabled in this release.
Identity Store Host: Enter the host or DNS name for the identity store LDAP service. This can be the host name of the identity server or the host name for the load balancer endpoint load balancing multiple identity servers.
Identity Store Port: The port assigned to the identity store. This can be the port of the identity server or the port for the load balancer endpoint load balancing multiple identity servers.
Tip:
The value for the Identity Store Port is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Identity Management Port Numbers table.
Identity Store Secure Port: The SSL port assigned to the identity store. This feature is not enabled for this release. This can be the secure port of the identity server or the secure port for the load balancer endpoint load balancing multiple identity servers.
Identity Store User DN: Enter the Distinguished Name of the user that is set up with read-write access to the LDAP.
Identity Store Password: Enter the password that is set up for the user with read-write access to the LDAP.
Identity Store Read-only User DN: Enter the Distinguished Name (DN) of the user that is set up with read-only access to the Identity Store LDAP.
Identity Store Read-only Password: Enter the password that is set up for the identity store read-only user.
Identity Store User Name Attribute: Choose the type of user name attribute that is configured in the identity store. Valid values are: user ID (uid), common name (CN), or email address.
Identity Store User Login Attribute: Enter the name of the attribute that needs to match for the user to be authenticated.
Identity Store User DN Attribute: Enter the attribute that defines the Distinguished Name (DN) of the user.
Identity Store Object Classes For User Creation: Enter the object classes to be assigned to a new user created in identity store, in a comma-separated list of user object class names.
Identity Store Object Classes For Group Creation: Enter the object classes to be assigned to a new group created in identity store, in a comma-separated list of group object class names.
Identity Store User Base DN: Enter the root Distinguished Name assigned to the upload of applications user data. This is the root for all the user data in the identity store.
Identity Store Group Base DN: Enter the root Distinguished Name for all the group data in the identity store.
IDM Weblogic Admin Username: Enter the Weblogic administrator user name for the IDM Weblogic domain. Accept the default value if the IDM was created using the IDM provisioning.
IDM Weblogic Admin Password: Enter the password for the Weblogic administrator user in the IDM Weblogic domain.
The wizard warns if it cannot connect to the database. If this warning represents an exception, ignore it and continue creating the response file. However, all issues must be fixed before starting to provision an environment. Provisioning cannot be run successfully until all validation have passed.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook:
For Basic topology: Topology tab, Topology table, Abstract Host Name column (or real if abstract is blank) for node corresponding to the IDM Identity and Access component. For Enterprise/Enterprise HA: Network - Virtual Hosts tab, HTTP LBR Endpoints table, IDM row.
Enter the parameters necessary to integrate applications with a previously installed Oracle Identity Management infrastructure. If the values in the IDM properties file (for example, idmsetup.properties) are chosen on the IDM Properties File screen to be used, they appear as defaults in the corresponding fields. Replace the defaults if the original configuration has changed.
Oracle Access Manager Configuration
OAM Admin Server Host: Enter the name of the host where the Administration Server for Oracle Access Manager exists.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook:
For Basic topology: Topology tab, Topology table, Abstract Host Name column (or real if abstract is blank) for node corresponding to the IDM Identity and Access component. For Enterprise/Enterprise HA: Network -Virtual Hosts tab, AdminServer Virtual Hosts/VIPs table, IDMDomain AdminServer row.
OAM Admin Server Port: Enter the port number for the Oracle Access Manager Administration Server.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Identity Management Port Numbers table, IDMDomain AdminServer row.
OAM Administrator User Name: Enter the name assigned to this user when Oracle Access Manager was installed.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, OAM table, OAM Administrator User Name row.
OAM Administrator Password: Enter the password assigned to this user when Oracle Access Manager was installed.
OAM HTTP Internal Endpoint URL: The internal access point on the Oracle HTTP Server for Oracle Access Manager.
OAM HTTP(S) External Endpoint URL: The access point to use for accessing the Oracle Access Manager application using a browser.
OAM AAA Server Host: Enter the name of the proxy host where the Oracle Access Manager is installed.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Topology tab, Topology table, Abstract Host Name (or Real if abstract is blank) for node corresponding to the IDM Identity and Access component.
OAM AAA Server Port: The port number for the Oracle Access Manager listener on the OAM proxy host.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Network - Ports tab, Identity Management Port Numbers table, IDMDomain OAM AAA Server Port row.
Access Server Identifier: Name used to identify the Oracle Access Server.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, OAM table, Access Server Identifier row.
Enable Second Primary Oracle Access Manager: Select this checkbox to name a second Primary Oracle Access Manager for high availability.
Second Access Server Identifier: This defaults to aaa2, the name of the second Primary Oracle Access Manager Server.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, OAM table, Second Access Server Identifier row.
Webgate Password: Specify a password for the Resource WebGate. It must contain at least eight alphanumeric characters and at least one digit or punctuation mark. Retype to Confirm the password. If seeding of security data is disabled, the password must be the existing WebGate password.
Oracle Platform Security Services Configuration
OPSS Policy Store JPS Root Node: This is the Distinguished Name of the node to be used as the OPSS policy root for Oracle Fusion Applications. This field is read-only and the default value is set as cn=FAPolicies.
Tip:
This value is available in the Oracle Fusion Applications Installation Workbook, Identity Management tab, LDAP table, FA JPS Root DN row.
Identity Management Keystore Configuration
The IDM Keystore file and password value fields are enabled if either the Identity Store, the OPSS Store, or the OIM endpoint is SSL-enabled. These fields are populated by the values from the IDM properties file (for example,idmsetup.properties), if the file that contains these values exists. Edit these values if the fields are enabled.
IDM Keystore File: Enter the location of the JKS keystore containing the certificates for the Oracle Identity Management components.
IDM Keystore Password: Enter the password that is set up for the IDM Keystore File.
Note: The wizard warns if it cannot connect to the database. If this warning represents an exception, ignore it and continue creating the response file. However, all issues must be fixed before starting to provision an environment. Provisioning cannot be run successfully until all validation have passed.
Verify that the installation represented on this screen is correct. Click Back to return to the interview screens that require changes. Complete the following information:
Response File Name: Specify a unique file name for this response file. This is the executable file that is supplied to the wizard when prompted for other options.
Provisioning Summary: Specify a unique name for the summary details file. This file cannot be used to execute the response file.
Directory: Enter the directory path where this response file and the summary file will be saved. Choose a location that is visible to all servers accessing shared storage. Make sure the location is not read-only.
Record the name of the response file and its location. Supply it to the system administrator to use when performing system maintenance tasks.
During the response file creation process, it is possible to create a partial response file, which contains an incomplete set of configuration details. To create a partial response file, click Save at any point during the interview. To continue with the creation of the response file, start the wizard and select Update an Existing Response File from the Installation Options screen. Page through the screens and continue where it was left off.
Clicking Cancel is another way to create a partial response file, or, alternatively, exit the wizard without saving any response file details:
Save a partial response file and return to the wizard as many times as necessary to complete it. The wizard does not recognize a response file as being complete or valid until clicking Finish on the Summary screen.
Update also a completed response file if it has not been implemented. Note that after selecting product offerings for a partial or completed response file, the mix cannot be changed by updating the response file. Start a new wizard session and create a new response file.
After saving the response file, return to the Installation Options screen and select the Provision an Applications Environment option to perform the physical installation. Or, create another response file to use for another type of installation, for example, to create a test or demonstration environment.
To create another response file, repeat the tasks in Create a Response File. Save the new response file.
To use a response file to provision a new environment, go to Provision a New Oracle Fusion Applications Environment .