Adding New Fusion Applications Product Offerings using Incremental Provisioning

Introduction

A product offering is a logical grouping of features and functionality of Oracle Fusion Applications. Customers who have excluded certain product offerings during their base installation and would like to add these or would like to add newly released product offerings can only do so during upgrade using Incremental Provisioning (IP)

IP provides the ability to extend the Oracle Fusion Applications environments as part of the upgrade flow and is only supported on the following Oracle Fusion Applications environments:

1) on a bare metal Environment which is provisioned using a Provisioning wizard from a prior release.
2) on an environment which is created from Oracle Fusion Applications Oracle Virtual Machine (VM) templates.

Incremental Provisioning cannot be performed:

1) On an existing environment outside of the upgrade flow
2) For adding of optional VM hosts for product offerings such as, Value Chain Planning (VCP) and Governance, Risk and Control (GRC) during upgrade for environments created from a prior release of Oracle Fusion Application Oracle Virtual Machine (VM) templates.

The following diagram will help you determine whether incremental provisioning is required or not :

                                                 Screen Shot 2017-11-29 at 2.29.28 PM

Figure-1

Note:  If your environment has at least one SCM offering or the Procurement offering installed and you are upgrading to R12, then you will need to use incremental provisioning as all mandatory SCM offerings are required in R12.

Prepare for incremental provisioning

If Incremental Provisioning is required based on the Figure-1 , Set the PERFORM_INCREMENTAL_PROVISIONING property to true in the pod.properties file.  Once this parameter is set to true, Upgrade Orchestrator itself will provide a pause point to create the Extended Provisioning Response File and to Run the Provisioning to add the new offerings. In case if this property is not set to true, then Upgrade Orchestrator skips the pause point and there will not be an opportunity to run incremental provisioning.

If the environment does not already have any one of the Oracle Sales, Oracle Marketing, or Oracle Financials offerings, and you plan 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.

Update pod.properties during Pre-Upgrade Phase:

Add the following Parameters in the pod.properties:

pod.properties location: <shared_location>/orchestration/<pod_name>/config

Table 1: List of Incremental Provisioning Parameters

No: Parameter Name Value Description
1 RESPONSE_FILES_DIR_LOC  <shared_location>/<response_files_dir> This property specifies the location where incremental provisioning response files are located. This property is mandatory if PERFORM_INCREMENTAL_PROVISIONING is set to true; it is ignored otherwise.
2 PERFORM_INCREMENTAL_PROVISIONING true This property indicates whether or not Incremental Provisioning should be
performed. Default value is false.
3 INC_PROV_BINARY_HOME <shared_location>/<inc_prov_binary_home>  This property is the location where incremental provisioning binaries are installed. This location must be accessible from all hosts within a POD.This property is mandatory if PERFORM_INCREMENTAL_PROVISIONING is set to true; it is ignored otherwise.

 

Note: All the directory locations mentioned in the pod.properties need to be pre-created before starting the Upgrade Orchestrator.

Whats happening during Upgrade Process when IP is Enabled

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 in the INC_PROV_BINARY_HOME location by the time upgrade reaches a pause point only 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 by launching the provisioning wizard from the INC_PROV_BINARY_HOME location.

Snippet from Upgrade Orchestrator:

Screen Shot 2017-11-15 at 10.27.01 PM

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.

Steps to run the Incremental Provisioning during the Fusion Applications Upgrade from Release 8 to Release 12 is illustrated in the later part of this article. For this Incremental Provisioning example, parameters mention in the section “Prepare for Incremental Provisioning” are already configured during the Pre-Upgrade phase itself.

Launch the Provisioning Wizard from the provisioning framework installed in the INC_PROV_BINARY_HOME location:

export JAVA_HOME=<shared_location>/repository/jdk

export PATH=$JAVA_HOME/bin:$PATH

<shared_location>/<directory_name>/binaries/provisioning/bin/provisioningWizard.sh

 

Table 2: Creating Extended Provisioning Response File

No Installation Step Installation Screenshot
1 Fusion Applications Provisioning Wizard – Welcome Screen Screen Shot 2017-11-14 at 11.45.59 AM
2 Fusion Applications Provisioning Wizard – Installation Options Screen Shot 2017-11-14 at 11.46.12 AM
 3  Fusion Applications Provisioning Wizard – Introspect an existing Fusion Application Environment  Screen Shot 2017-11-14 at 11.46.33 AM
 4  Fusion Applications Provisioning Wizard – Additional Configurations  Screen Shot 2017-11-14 at 11.49.12 AM
 5  Fusion Applications Provisioning Wizard – Provisioning Configurations  Screen Shot 2017-11-14 at 11.53.50 AM
 6  Fusion Applications Provisioning Wizard – Response File Descriptions Screen Shot 2017-11-14 at 12.17.25 PM
 7  Fusion Applications Provisioning Wizard – Response File Descriptions Input the Installers Directory Location:

<shared_location>/repostory

Input the Font Directory: /usr/share/X11/fonts/TTF

 8  Fusion Applications Provisioning Wizard – Summary Click Next for the Validation Screens and in the Summary Screen Provide the Following:

Provisioning Response File Name:

Provisioning Summary:

Directory: RESPONSE_FILES_DIR_LOC provided in the pod.properties

 

After successfully creating the response file for manual incremental provisioning, update the Upgrade Orchestration task status to success on the primordial host as follows:

cd ORCH_LOCATION/bin

./orchestration.sh updateStatus -pod POD_NAME -hosttype PRIMORDIAL -hostname host_name -release 11.12.x.0.0 -phase DowntimePostFA -taskid CreateIpResponseFilePausePointTask -taskstatus success

Once the task status is updated and Orchestration is restarted on PRIMORDIAL Node, Upgrade Orchestrator will provide the next pause point to execute the IP Manually:

Snippet from Upgrade Orchestrator:

Screen Shot 2017-11-15 at 10.56.14 PM

Perform Incremental Provisioning

Check Point:

Ensure that the existing Oracle Fusion Applications environment to be extended is active and running correctly.

Ensure that Backups are executed before the Upgrade Process.

Launch the Provisioning Wizard from the provisioning framework installed in the INC_PROV_BINARY_HOME location:

export JAVA_HOME=<shared_location>/repository/jdk

export PATH=$JAVA_HOME/bin:$PATH

Verify that the LIBPATH value is null.

echo $LD_LIBRARY_PATH

<shared_location>/<directory_name>/binaries/provisioning/bin/provisioningWizard.sh

Table 3: Perform Incremental Provisioning

No Installation Step Installation Screenshot 
1 Fusion Applications Provisioning Wizard – Welcome Screen   Screen Shot 2017-11-14 at 2.16.55 PM
2  Fusion Applications Provisioning Wizard – Installation Options  Screen Shot 2017-11-14 at 2.17.40 PM
3  Fusion Applications Provisioning Wizard – Confirmation  Screen Shot 2017-11-14 at 2.18.07 PM
4  Fusion Applications Provisioning Wizard – Response File Description  Screen Shot 2017-11-14 at 2.18.21 PM
5  Fusion Applications Provisioning Wizard – Installation Location  Screen Shot 2017-11-14 at 2.18.37 PM
6  Fusion Applications Provisioning Wizard – Provisioning Configuration  Screen Shot 2017-11-14 at 2.19.22 PM
7  Fusion Applications Provisioning Wizard – Summary Screen Shot 2017-11-14 at 2.20.52 PM
8  Fusion Applications Provisioning Wizard – Pre Requisite Checks  Screen Shot 2017-11-14 at 2.54.25 PM
9  Fusion Applications Provisioning Wizard – Configure  Screen Shot 2017-11-14 at 5.08.20 PM
10  Fusion Applications Provisioning Wizard – Configure Primary/Secondary  Screen Shot 2017-11-14 at 5.14.07 PM
 11 Fusion Applications Provisioning Wizard – Post Configure Screen Shot 2017-11-14 at 6.33.54 PM
12 Fusion Applications Provisioning Wizard – Startup  Screen Shot 2017-11-14 at 9.08.41 PM
13  Fusion Applications Provisioning Wizard – Validation  Screen Shot 2017-11-14 at 11.10.46 PM
14  Fusion Applications Provisioning Wizard – Complete  Screen Shot 2017-11-14 at 11.10.57 PM

 

 

Note:

For Scaled Out 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. Also Incremental Provisioning does not provide scale out capability such as creating multiple Managed Server instance within a cluster

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.

Once the IP is successfully completed and  before 'postUpgradeCleanup' step of upgrade , update the following parameters in the  <APPTOP>/instance/fapatch/FUSION_env.properties on the CommonDomain AdminServer host.

  POLICY_STORE_LDAP_HOSTNAME=<fully qualified OID host name>

  POLICY_STORE_LDAP_PORT=<OID port>

  POLICY_STORE_CONNECT_PROTOCOL_SSL=<Yes/No>

This information is available from the response file used to provision the FA environment initially, OAM_OPSS_HOST and OAM_OPSS_PORT respectively of the response file.

Update the Upgrade Orchestration task status to Success After Incremental Provisioning

After successfully performing manual incremental provisioning, update the task status to success on the primordial, OHS, and Midtier hosts:

Update the task status on the primordial host as follows:
cd ORCH_LOCATION/bin
./orchestration.sh updateStatus -pod POD_NAME -hosttype PRIMORDIAL -hostname host_name -release 11.12.x.0.0 -phase DowntimePostFA -taskid RunIncrementalProvisioningManually -taskstatus success

Update the task status on each Midtier host that is listed in the HOSTNAME_MIDTIER property in the pod.properties file as follows:
cd ORCH_LOCATION/bin
./orchestration.sh updateStatus -pod POD_NAME -hosttype MIDTIER -hostname host_name -release 11.12.x.0.0 -phase DowntimePostFA -taskid RunIncrementalProvisioningManually -taskstatus success

Update the task status on each OHS host that is listed in the HOSTNAME_OHS property in the pod.propertie file as follows:
cd ORCH_LOCATION/bin
./orchestration.sh updateStatus -pod POD_NAME -hosttype OHS -hostname host_name -release 11.12.x.0.0 -phase DowntimePostFA -taskid RunIncrementalProvisioningManually -taskstatus success

Restart the Orchestration and Continue with the rest of the Upgrade Process.

Snippet from Upgrade Orchestrator:

Screen Shot 2017-11-15 at 11.22.54 PM

Summary

Once the Upgrade is successfully completed, the new Products offerings which are added as a part of the Incremental Provisioning can be viewed from the Fusion Application HomePage and also by comparing the response file created during the initial provisioning and extended response file created during the Incremental provisioning:

Response file during the Initial Provisioning:

Screen Shot 2017-11-14 at 10.06.45 AM

Extended Response file during the Incremental Provisioning:

Screen Shot 2017-11-14 at 2.02.11 PM

Reference:
Fusion Applications Upgrade Guide
Fusion Applications Installation Guide

Add Your Comment