This section describes the process of extending an Oracle Fusion Applications environment using incremental provisioning when upgrading from a prior release as part of the upgrade process. For more information about upgrading from a prior release of Oracle Fusion Applications, see Introduction to Oracle Fusion Applications Upgrade in the Oracle Fusion Applications Upgrade Guide.
Incremental provisioning gives the ability to extend an Oracle Fusion Applications environment during the upgrade, by adding product offerings that are not already present. Add product offerings that are available for selection in the Provisioning Wizard, including those introduced in a later release.
To use incremental provisioning, an existing Oracle Fusion Applications environment created from a prior release is necessary. This environment is used for upgrading to the current release.
Use incremental provisioning if the Oracle Fusion Applications environment is a bare metal environment. This means that the environment was created by using the Provisioning Wizard from a prior release where the product offerings were selected and the Oracle Fusion Applications provisioning process described in the guide for that release was followed.
For example: To upgrade from Release 11 to 12, the Provisioning Wizard must have been used to select the product offerings and the Oracle Fusion Applications provisioning process, described in this guide, must have been followed to create the environment for Release 11.
Use incremental provisioning if the Oracle Fusion Applications environment is created from Oracle Fusion Applications Oracle VM templates of a prior release and to add product offerings during upgrading to this release. The available selection of product offerings are the ones newly introduced up to this release (excluding any that already existing in the OVM environment).
For more information about the list of product offerings included in each of the Oracle Fusion Applications Oracle VM templates, see Introduction to Oracle VM Installation in the the Oracle Fusion Applications Installing and Managing in an Oracle VM Environment Guide.
Incremental provisioning cannot be performed for an Oracle Fusion Applications environment created in a current release. This means that an Oracle Fusion Applications environment cannot be provisioned for Release 12, and then decide to perform incremental provisioning to add product offerings that were not selected using the provisioning repository from the same release.
During the upgrade from a prior release to Release 12, if the environment meets one of the conditions described in Conditions for manually performing the incremental provisioning task during the incremental provisioning pause point to add the FOS offering, then perform the incremental provisioning task manually during the incremental provisioning pause point to add the FOS offering. If none of the conditions are true, then skip the incremental provisioning task. For more information about incremental provisioning pause point, see Pause Point 6 - Perform Incremental Provisioning in the Oracle Fusion Applications Upgrade Guide.
Conditions for manually performing the incremental provisioning task during the incremental provisioning pause point to add the FOS offering:
Bare Metal environments: The Provisioning Wizard has been run to select product offerings and provision the environment on several hosts. The environment contains any one of these product offerings: Product Management, Order Orchestration, or Material Management and Logistics from Supply Chain Management, or Procurement from Financials.
Oracle VM environments: An environment has been created from one of the Oracle Fusion Applications Oracle VM templates not managed by Oracle Cloud and the Oracle VM template used is GSI (available since 11 g Release 7 (11.1.7) or FSCMH (Financial, Supply Chain Management and Human Capital Management, available prior to 11 g Release 6 (11.1.6). If an HCM or CRM template is used, see Verify Environment Before Proceeding to Downtime in the Oracle Fusion Applications Upgrade Guide.
Bare Metal: An environment that does not include any software. In the context of Oracle Fusion Applications, this means a supported version of operating system must be installed in order for the computer system to be functional prior to provisioning Oracle Fusion Applications.
Oracle VM: An environment running on virtual servers. In the context of Oracle Fusion Applications, the supported virtualization technology is Oracle VM Manager. Installing an Oracle Fusion Applications Oracle VM template creates multiple Oracle VM servers running a version of Linux operating system that comes with the Oracle VM template on the virtual servers.
As described in Oracle WebLogic Server Domains, incremental provisioning is capable of creating a single Managed Server instance within a cluster. It does not provide scale out capability such as creating multiple Managed Server instance within a cluster. After incremental provisioning is complete, scale out Oracle Fusion Middleware components, such as Oracle HTTP Server and Oracle SOA Suite, and product domains, such as Oracle Fusion Customer Relationship Management domain, Oracle Fusion Common domain, Oracle Fusion Human Capital Management domain, and so on. For more information about scaling out capabilities, see Complete Conditional Common High Availability Post-Installation Tasks for Oracle Identity Management and Complete Conditional Common High Availability Post-Installation Tasks for Oracle Fusion Applications.
This section includes the following topics:
Oracle Fusion Applications Provisioning orchestrates the physical installation and configuration of the product offerings selected 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 incremental provisioning is used to extend an existing Oracle Fusion Applications environment running a prior release, provisioning also requires the provisioning repository of installers, the provisioning framework, and a response file. During the upgrade process, Upgrade Orchestrator installs the provisioning framework by the time upgrade reaches a pause point if the PERFORM_INCREMENTAL_PROVISIONING property is set to true in the pod.properties file. At this time, proceed with creating an extended provisioning response file to be used by incremental provisioning.
The incremental provisioning process consists of the following two tasks:
Creating an Extended Provisioning Response File
An extended provisioning response file contains the same provisioning response when the Oracle Fusion Applications environment is initially provisioned, and any additional information provisioning needs to extend the Oracle Fusion Applications product offerings selected to be added. Instead of entering the same information again, incremental provisioning introspects the existing Oracle Fusion Applications environment and creates the extended provisioning response file. See Create an Extended Provisioning Response File.
Performing Incremental Provisioning
To create an extended provisioning response file, start the Provisioning Wizard and select the Create a Response File for Extending an Existing Fusion Application Environment option.
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 when performing incremental provisioning. Note that the extended provisioning response file should be created on the Primordial host, which is the host that contains the Administration Server of the Common domain.
When a response file is created, chose a provisioning configuration and incremental provisioning then takes through a series of interview screens to 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.
Currently updating an extended response file is not supported. To make changes to the extended provisioning response file, re-create an extended provisioning response file.
MANDATORY: Select only the Create a Response File for Extending an Existing Fusion Application Environment option during upgrade and follow the Upgrade Orchestration flow.
Confirm the following before starting incremental provisioning.
Ensure that the existing Oracle Fusion Applications environment to be extended is active and running correctly.
Ensure to complete the required upgrade tasks, including backing up the Oracle Fusion Applications environment as part of the upgrade process and are ready to extend the environment. For more information about backing up during the upgrade process, see Back Up Fusion Applications in the Oracle Fusion Applications Upgrade Guide.
To add new provisioning host(s) to the environment, ensure the host(s) is/are prepared as described in Prepare for an Installation.
The Provisioning Wizard supports the following command line options:
Table 27-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 will be ignored. Note: |
false |
|
|
Displays help text. |
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 27-1
provisioningWizard.sh -invPtrLoc /oracle/oraInst.loc -ignoreSysPrereqs
Table 27-2 shows the steps necessary to create a response file using the Provisioning Wizard. For help with any of the screens, click Help.
If the correct values required are not entered, the error and warning messages are displayed at the bottom of the screen.
Table 27-2 Creating an Extended Provisioning Response File
| Screen | Description and Action Required |
|---|---|
|
Welcome |
No action is required on this read-only screen. Click Next to continue. |
|
Installation Options |
Presents the list of valid installation actions that can be performed using the wizard. Select Create a Response File for Extending an Existing Fusion Application Environment. Click Next to continue. |
|
Introspect an Existing Fusion Applications Environment |
Introspects an existing Oracle Fusion Applications environment which can be extended. Ensure that all Admin servers are running before proceeding with the introspection.
Click Next to continue. |
|
Additional Configurations |
This screen displays the product offerings selected when the environment was originally provisioned. Select the required checkbox to start the previously provisioned offerings. Note: If a new offering is available for selection on this screen. DO NOT select the new offering on this screen because only the offerings that are already provisioned in the environment that is being extended must be selected. Click Next to continue. |
|
Provisioning Configurations |
This screen only displays the offerings that have not been selected when the environment was provisioned. To see the details of the provisioned environment, use the Click here to view the configurations that are already provisioned and started link available on the screen. To extend the existing Oracle Fusion Applications environment, select one or more offerings, either within a configuration, or from the list of standalone product offerings. 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 for extending the existing Oracle Fusion Applications environment. 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 response file, or the summary file, that has been saved at the end of the response file creation process.
Click Next to continue. |
|
Installation Location |
This screen displays the credentials for the Node Manager and the location of the various directories required for installation and configuration actions. Click Next to continue. |
|
System Port Allocation |
Read-only screen displaying the Applications Base Port and Other Ports: Node Manager. Click Next to continue. |
|
Database Configuration |
Read-only screen displaying the database parameters established when the Oracle Database was installed. Click Next to continue. |
|
Schema Passwords |
The database that is installed contains preloaded schemas required for runtime execution. This read-only screen displays the schema password details. Click Next to continue. |
|
ODI Password Configuration |
Read-only screen displaying the ODI supervisor password. The ODI Supervisor Password is the Supervisor Password that is entered on the Custom Variables page during execution of Oracle Fusion Applications RCU, under the Primary and Work Repository component. Click Next to continue. |
|
Domain Topology Configuration |
Read-only screen displaying the domain topology configuration option chosen while provisioning the environment. The types of possible topologies are:
Click Next to continue. |
|
Common Domain |
If applicable, specify values for the new selected 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 values for the previously selected configuration cannot be changed.
Click Next to continue. |
|
Product Family Domains |
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.
Click Next to continue. |
|
Web Tier Configuration |
Read-only screen displaying the values selected during the provisioning of the environment. Click Next to continue. |
|
Virtual Hosts Configuration |
If applicable, specify values for the new domain that is selected. The values for the previously selected configuration cannot be changed. Specify the configuration parameters for the domains to be installed on the virtual hosts that is selected on the Web Tier Configuration screen. Note: If the environment has a Load Balancer enabled, the fields on this page are editable and populated with default values that may not be valid for the environment. Review and overwrite the default values with the values applicable to the environment. Review the settings from the original provisioning summary file and enter those values. Click Next to continue. |
|
Load Balancer Configuration |
Read-only screen displaying the Load Balancer configuration details. Load balancing enables the distribution of a workload evenly across two or more hosts, network links, CPUs, hard drives, or other resources. Click Next to continue. |
|
Web Proxy Configuration |
Read-only screen displaying the Web Proxy configuration details. Click Next to continue. |
|
IDM Properties File |
Read-only screen displaying the IDM Properties file details. Click Next to continue. |
|
Identity Management Configuration |
Read-only screen displaying the Oracle Identity Management configuration details. Click Next to continue. |
|
Access and Policy Management Configuration |
Read-only screen displaying the Access and Policy Management configuration details to integrate the Oracle Fusion Applications environment with Oracle Identity Management. Click Next to continue. |
|
Summary |
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:
Record the name of the response file and its location. Supply it to the system administrator to use when performing system maintenance tasks. Click Finish to save the response file and the summary. The response file is complete and can be used as the basis for extending the exiting Oracle Fusion Applications environment. If the Oracle Fusion Applications environment is being upgraded, follow the steps in Update Status to Success (Incremental Provisioning) in the Oracle Fusion Applications Upgrade Guide to proceed with the upgrade. |
After the extended provisioning response file is created, perform incremental provisioning to extend the existing Oracle Fusion Applications environment. The incremental provisioning process is the same as provisioning a new Oracle Fusion Applications Environment as described in Provision a New Oracle Fusion Applications Environment, except that the provisioning phases are based on the extended provisioning response file.
In the extended provisioning response file previously created, the configuration details necessary to run a physical installation of Oracle Fusion Applications product offerings were specified. For full-scale environments, typically the offerings must be provisioned on multiple hosts, and the installation must be run from a shared drive that is accessible to all hosts.
Incremental provisioning goes through the same provisioning process to create a new Oracle Fusion Applications environment. The installation provisioning process is run in phases, in an assigned order. Complete each phase, in order, on each host, before moving to the next phase. All phases must be completed successfully on all the hosts in the environment to create a fully operational applications environment.
When the preverify phase is successful on the primordial host and the webtier host is placed in the DMZ, place a copy of the response file, the generated provisioning plan (APPLICATIONS_BASE/provisioning/plan/provisioning.plan), and a copy of the introspect response file (introspect.rsp, located in APPLICATIONS_BASE/provisioning/introspect/introspect.rsp in the webtier host in the DMZ.
After incremental provisioning completes successfully, follow the steps in Update Status to Success (Incremental Provisioning) in the Oracle Fusion Applications Upgrade Guide to proceed with the upgrade.
If an issue is encountered while performing incremental provisioning, follow the same guidelines and steps described in Troubleshoot an Oracle Fusion Applications Environment to resolve the issues.
The following section describes troubleshooting for specific issues that might be encountered with incremental provisioning.
If the environment does not already have any one of the Oracle Sales, Oracle Marketing, or Oracle Financials offerings, and to add at least one of them through incremental provisioning, then confirm that the true-type fonts are installed at /usr/share/X11/fonts/TTF. If the true-type fonts are missing, install them before proceeding to the next step.
Problem
The creation of the extended provisioning response file fails with the following password validation error for Node Manager confirm password, BI RPD confirm password and OAM webgate confirm password:
Confirm Password: The password must contain only alphanumeric and punctuation characters. Trailing or leading whitespace characters are not allowed.
Solution
Manually update the introspect.rsp file to reflect correct confirm passwords:
Run the wizard and proceed until the introspection page
Click next to complete introspection
Close the wizard at the Additional Configurations screen
Update the $PROVTMP/introspect.rsp (Default /tmp/introspect.rsp) file for these properties. Copy the value of *PWD and paste to *PWDCONFIRM:
INSTALL_NODEMNGR_PWD=<copy_this_value> INSTALL_NODEMNGR_PWDCONFIRM=<paste_the_value_from INSTALL_NODEMNGR_PWD> INSTALL_BIRPD_PWD=<copy_this_value> INSTALL_BIRPD_PWDCONFIRM=<paste_the_value_from INSTALL_BIRPD_PWD> OAM_WEBGATE_PWD=<copy_this_value> OAM_WEBGATE_PWDCONFIRM=<paste_the_value_from OAM_WEBGATE_PWD>
Note:
For Linux, the default location for theintrospect.rsp file is /tmp/introspect.rsp. For Solaris, the default location for the introspect.rsp file is /var/tmp.Set the env variable:
export SKIP_INTROSPECTION=true
Rerun the wizard and go through all the pages to create the response file.
The following section describes the steps to troubleshoot preverify phase errors.
If the webtier host is located in DMZ, then invoke the preverify phase on the webtier host with the -ignoreSyspreqs argument.
The following section describes the steps to troubleshoot install phase errors.
Do not make configuration changes to the Oracle Fusion Applications environments using super user (root) or other privileged users. Such changes alter file permissions, causing issues that are hard to troubleshoot and result in severe errors as shown in the following example.
Example
The install phase of performing incremental provisioning fails with the following error message in the provisioning log file:
[2014-10-09T10:33:01.762+00:00] [runProvisioning-install] [NOTIFICATION] [FAPROV-01214] [runProvisioning-install] [tid: 10] [ecid: 0000KZoTsKmDĝ95RfL6id1KDaGu000001,0] [arg: /u02/instance] [arg: /u01/APPLTOP/instance/provisioning/restart/backup_install/instance.tar] Compressing /u02/instance to backup /u01/APPLTOP/instance/provisioning/restart/backup_install/instance.tar [2014-10-09T10:33:02.771+00:00] [runProvisioning-install] [WARNING] [] [runProvisioning-install] [tid: 12] [ecid: 0000KZoU18nDĝ95RfL6id1KDaGu000004,0] [exec] /bin/tar: /CommonDomain_webtier_local/config/OHS/ohs1/webgate/config/oblog_config_wg.xml.09222014: Cannot open: Permission denied [2014-10-09T10:33:16.858+00:00] [runProvisioning-install] [WARNING] [] [runProvisioning-install] [tid: 12] [ecid: 0000KZoU18nDĝ95RfL6id1KDaGu000004,0] [exec] /bin/tar: Error exit delayed from previous errors [2014-10-09T10:33:16.868+00:00] [runProvisioning-install] [NOTIFICATION] [] [runProvisioning-install] [tid: 10] [ecid: 0000KZoTsKmDĝ95RfL6id1KDaGu000001,0] [delete] Deleting: /u01/APPLTOP/instance/provisioning/restart/backup_install/instance.tar [2014-10-09T10:33:16.906+00:00] [runProvisioning-install] [NOTIFICATION] [FAPROV-01214] [runProvisioning-install] [tid: 10] [ecid: 0000KZoTsKmDĝ95RfL6id1KDaGu000001,0] [arg: /u02/instance] [arg: /u01/APPLTOP/instance/provisioning/restart/backup_install/instance.tar] Compressing /u02/instance to backup /u01/APPLTOP/instance/provisioning/restart/backup_install/instance.tar [2014-10-09T10:33:17.028+00:00] [runProvisioning-install] [WARNING] [] [runProvisioning-install] [tid: 13] [ecid: 0000KZoU4b^Dĝ95RfL6id1KDaGu000005,0] [exec] /bin/tar: ./CommonDomain_webtier_local/config/OHS/ohs1/webgate/config/oblog_config_wg.xml.09222014: Cannot open: Permission denied [2014-10-09T10:33:18.422+00:00] [runProvisioning-install] [WARNING] [] [runProvisioning-install] [tid: 13] [ecid: 0000KZoU4b^Dĝ95RfL6id1KDaGu000005,0] [exec] /bin/tar: Error exit delayed from previous errors
These errors are caused by the OHS configuration being changed by a user other than the user that provisioned the Oracle Fusion Applications environment prior to performing incremental provisioning. In this case the file, APPLICATIONS_CONFIG/OHS/ohs1/webgate/config/oblog_config_wg.xml.09222014, was altered and is now owned by the root user.
Resolution
Perform the following steps to resolve this issue.
After successfully extending the Oracle Fusion Applications environment, resume the Upgrade Orchestrator process to complete the upgrade. For more information about the upgrade process, see Update Status to Success (Incremental Provisioning) in the Oracle Fusion Applications Upgrade Guide to proceed with the upgrade.
DO NOT start using the environment unless the upgrade process is successfully completed.
To scale out the Oracle Fusion Applications environment to make it high availability, follow the required steps after completing the upgrade. For more information about scaling out, see Complete Conditional Common High Availability Post-Installation Tasks for Oracle Fusion Applications.