A Release Update Patch Installer Screens

This appendix presents the Release Update Patch (RUP) Installer interview screens and describes the purpose of each of the following screens:

• Welcome

• Installation Location

• Installation Summary

• Installation Progress

• Policy Store Analysis

• Configuration Progress

• Installation Complete

A.1 Welcome

This screen appears each time you start RUP Installer the first time. This screen does not appear if you restart RUP Installer after a failure. The standard Welcome screen is read-only. It contains a navigation pane on the left-hand side that summarizes the tasks the installer will take. Each item in the pane represents an installer screen, which contains prompts for the necessary information.

Click Next to continue.

A.2 Installation Location

Specify the location of the existing Oracle Fusion Applications home (FA_ORACLE_HOME) where you want to install the RUP.

Click Next to continue.

A.3 Installation Summary

Summarizes the selections you made during this installation session. It includes the Oracle home, required and available disk space, and the version of the RUP to be installed. Review the information displayed to ensure that the installation details are what you intend.

To make changes before installing, click Back to return to previous screens in the interview.

Click Install to accept this configuration and start the installation.

A.4 Installation Progress

Displays a progress indicator that shows the percentage of the installation that is complete and indicates the location of the installation log file. The installation task consists of copying files from the RUP to the Oracle home. The configuration process starts when the installation progress indicator shows 100 percent. Click Next to proceed.

A.5 Policy Store Analysis

Analysis is available for the following policy store stripes: hcm, crm, fscm, and obi. Select the stripes to be analyzed and then click Run Analysis to identify any conflicts or deletions. Only the stripes that will be updated are enabled for analysis and the analysis could run for several minutes. After the analysis runs, review the results of the analysis to determine which deployment method RUP Installer will use for policy store changes to each stripe. Oracle recommends that you select Apply safe changes only. This is the safest method unless you have read and totally understood the consequences of the other three options. If you decide to resolve the conflicts or deletions before the actual JAZN upload from RUP Installer, you should run the Policy Store Analysis step again to get the most accurate analysis report. The choices for deployment method are:

• Apply safe changes only (choose this method if there are no conflicts)

• Apply all changes and overwrite customizations

• Append additive changes

• Manually resolve conflicts and upload changes using Authorization Policy Manager

If you choose Apply safe changes only or Append additive changes, then you must review the results of the analysis to manually upload any changes not applied by RUP Installer with the choice you selected, after the installation is complete. If you choose Apply all changes and overwrite customizations, then you may need to reapply the customizations that are overwritten after the installation is complete. If you choose one of these options, click Next after you make your selection.

If you choose Manually resolve conflicts and upload changes using Authorization Policy Manager (APM), you must pause the upgrade while you bring up the APM application and upload the changes. For more information, see the "Upgrading Oracle Fusion Applications Policies" chapter in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note the location of the following files:

• Baseline file: FA_ORACLE_HOME/admin/JAZN/stripe/baseline

• Patch file for fscm, crm, and hcm stripes: FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml

• Patch file for the obi stripe: FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml

When you complete this task in APM, shut down the APM application, return to RUP Installer, and click Next.

Note:

If you installed a Language Pack and chose to override the base English strings in the policy store, this screen no longer displays during RUP installation.

A.6 Configuration Progress

Displays a progress indicator that shows the percentage of the configuration phase that is complete. It displays each task, including steps within tasks, in the message pane as it is performed. Tasks that could be included in the configuration phase are described in Section 5.1.4, "RUP Installer Configuration Tasks" in the Oracle Fusion Applications Patching Guide.

Before the Starting All Servers task, the Verifying Node Manager and OPMN Status configuration task checks for access to the Node Manager and the OPMN control process. This should fail because you manually shut down these processes prior to starting RUP Installer. When this task fails, follow these steps:

1. Start the Node Manager on all hosts that are part of the Oracle Fusion Applications provisioned system. For more information, see "Start Node Manager" in Oracle Fusion Applications Administrator's Guide.

2. Restart the OPMN server for BI and GOP, and the OPMN server plus managed processes for webtier. This is similar to the stop steps described in Section 5.3.3.2, "Stop the Node Manager and the OPMN Control Process" in the Oracle Fusion Applications Patching Guide, except that for BI and GOP, you must start only the OPMN server itself, while for webtier, you should start OPMN and all processes that it manages. If you run the webtier (OHS) installed with the Oracle Fusion Applications middle tier, you can start it using the following steps. If you run the webtier on a separate machine, you may be able to run the steps below on the other machine. In either case, ensure that webtier (OHS) is up at this point.

   Example for BI: (note the usage of start instead of startall)

   cd APPLICATIONS_BASE/instance/BIInstance/bin
   ./opmnctl start
   

   Example for GOP: (note the usage of start instead of startall)

   cd APPLICATIONS_BASE/instance/gop_1/bin
   ./opmnctl start
   

   Example for webtier:

   cd APPLICATIONS_BASE/instance/CommonDomain_webtier/bin
   ./opmnctl startall
   

   For more information about the location of APPLICATIONS_BASE, see Section 2.1.2, "Oracle Fusion Applications Oracle Home" in the Oracle Fusion Applications Patching Guide.

   The BI processes managed by OPMN are started by RUP installer in the Start All Servers configuration task. The GOP processes managed by OPMN can be started by an administrative user from the GOP home page in Oracle Enterprise Manager after RUP installer completes.

3. Fix any other environment issues before retrying the session. If RUP Installer exits for any reason, make sure that all node managers and OPMN processes are running. Contact Oracle Support Services to proceed out of this step if you have environment issues.

4. After you start these services, click Retry to move to the Starting All Servers task.

No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 5.5.3, "General Troubleshooting During the Configuration Phase" in the Oracle Fusion Applications Patching Guide.

A.7 Installation Complete

Summarizes the installation just completed. If you want to save this configuration to a response file, click Save. For more information, see "How Response Files Work" in the Oracle Database Installation Guide 11g Release 2 (11.2) for Linux.To complete a successful installation, click Finish. The Finish button is activated only if all mandatory configuration tasks completed successfully. If you want to rerun this session to resolve failed configuration tasks, click Cancel.