| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Upgrade Guide 11g Release 6 (11.1.6) Part Number E35833-07 |
|
|
PDF · Mobi · ePub |
This appendix presents the RUP Installer interview screens and describes the purpose of each screen. The RUP Installer screens are presented in the following two sections:
The first installer of RUP Installer includes the following screens:
This screen appears when you start RUP Installer. 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 steps the installer will take. Each item in the pane represents an installer screen, which contains prompts for the necessary information.
Click Next to continue.
Specify the location of the existing Oracle Fusion Applications home (FA_ORACLE_HOME).
Click Next to continue.
This screen summarizes the configuration that will be used during this installation session. It includes the Oracle home, required and available disk space, and the version of the release 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.
This screen displays a progress indicator that shows the percentage of the installation phase that is complete and indicates the location of the installation log file. The installation phase consists of copying files to the appropriate Oracle homes that are related to configuration assistants that run during the first installer.
When the installation progress indicator shows 100 percent, click Next to continue.
This screen displays a progress indicator that shows the percentage of the configuration phase that is complete. It displays each configuration assistant, including steps within configuration assistants, in the message pane as they are performed. Tasks that could be included in the first installer's configuration phase are described in Table 1–1, " Configuration Assistants Run by Oracle Fusion Applications 11g Release 1 (11.1.6.0.0) RUP Installer Part 1 of 2" in the Oracle Fusion Applications Upgrade Guide.
No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see Section 6.4, "General Troubleshooting During the Configuration Phase in GUI Mode" in the Oracle Fusion Applications Upgrade Guide.
This screen 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 of the first installer, click Finish. The Finish button is activated only if all mandatory configuration assistants completed successfully. If you want to rerun this session to resolve failed configuration assistants, click Cancel.
You must run RUP Lite for Domain Configuration on all servers that contain local domains before proceeding to the next screen. The first installer must complete successfully before you proceed to the second installer. Do not click OK until you complete this step.
You can skip this step if the environment does not contain any local domains. Local domains are those that are hosted on the local storage of various hosts, rather than in shared storage.
Note that this step is not required for Oracle VM environments, as Oracle VM environments do not use local domains.
Log in to each remote machine.
Set the JAVA_HOME environment variable:
(Unix) setenv JAVA_HOME APPLICATIONS_BASE/fusionapps/jdk6 (Windows) set JAVA_HOME=APPLICATIONS_BASE\fusionapps\jdk6
Go to the directory that contains RUP Lite for Domain Configuration:
(Unix) cd APPLICATIONS_CONFIG/fapatch/admin/ruplitedomain/RUP_version/bin (Windows) cd APPLICATIONS_CONFIG\fapatch\admin\ruplitedomain\RUP_version\bin
Run RUP Lite for Domain Configuration. Note that RUP Lite cannot be run in parallel on remote servers and it does not have to be run from the primordial host where you started RUP Installer. It must be run on one server at a time.
(Unix) ./ruplite.sh (Windows) ruplite.bat
Ensure that you run RUP Lite for Domain Configuration on each server that contains local domains.
Click OK to proceed to the second installer.
The second installer of RUP Installer includes the following screens:
This screen appears when the second installer starts.
You must perform the following steps to start the Node Manager and OPMN server before proceeding to the next screen.
To ensure that Node Manager does not automatically start servers, even if crashRecovery is enabled, remove all files that end with .pid, .state, and .lck from domain_home/servers/server_name.
Start the Node Manager on all hosts that are part of the Oracle Fusion Applications provisioned system. For more information, see "Task 3: Start Node Manager" in the Oracle Fusion Applications Administrator's Guide.
Restart the OPMN server for BI, GOP (if you have GOP installed), and Web Tier. If you run the Web Tier (OHS) installed with the Oracle Fusion Applications middle tier, you can start it using the following steps. If you run the Web Tier on a separate machine, you may be able to run the steps below on the other machine. In either case, ensure that Web Tier (OHS) is up at this point.
Example for BI: (note the usage of start instead of startall)
cd APPLICATIONS_CONFIG/BIInstance/bin
./opmnctl start
Example for GOP: (note the usage of start instead of startall) Note that the OPMN server for GOP should be started from the machine that hosts the Advanced Planning Managed server. Start the OPMN server for GOP only if GOP is installed.
cd APPLICATIONS_CONFIG/gop_1/bin
./opmnctl start
Example for Web Tier: (note the usage of start instead of startall)
cd APPLICATIONS_CONFIG/CommonDomain_webtier/bin
./opmnctl start
For more information about the location of APPLICATIONS_CONFIG, see Section 2.2.1, "Before You Begin" in the Oracle Fusion Applications Upgrade Guide.
The BI and Web Tier processes managed by OPMN are started by RUP Installer during the Starting All Servers configuration assistant. The GOP processes managed by OPMN must be started using Fusion Applications Control after RUP Installer completes, as described in Section 4.7, "Start the GOP Processes" in the Oracle Fusion Applications Upgrade Guide.
Click Next to continue.
Specify the location of the existing Oracle Fusion Applications home (FA_ORACLE_HOME).
Click Next to continue.
This screen summarizes the configuration that will be used during this installation session. It includes the Oracle home, required and available disk space, and the version of the release 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 second installer.
This screen displays a progress indicator that shows the percentage of the installation phase that is complete and indicates the location of the installation log file. The installation phase consists of copying files to the appropriate Oracle homes that are related to configuration assistants that run during the second installer.
When the installation progress indicator shows 100 percent, click Next to continue.
Note:
If you installed a Language Pack and chose to override the base English strings in the policy store, this screen does not display during RUP installation.
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 by RUP Installer 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, 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 installation 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 applications, return to RUP Installer, and click Next.
The second installer supports parallel processing of certain configuration assistants, which run in groups. For more information, see "Parallel Configuration Assistants" in the Oracle Fusion Applications Upgrade Guide.
This screen 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 they are performed. Tasks that could be included in the second installer's configuration phase are described in Table 1–2, " Configuration Assistants Run by Oracle Fusion Applications 11g Release 1 (11.1.6.0.0) RUP Installer Part 2 of 2" in the Oracle Fusion Applications Upgrade Guide.
Before the Starting All Servers task, the Verifying Node Manager and OPMN Status configuration assistant checks for access to the Node Manager and the OPMN control process. This may fail if you did not start the Node Manager and OPMN processes after the completion of the first installer. Do not cancel and exit out of RUP Installer in response to this task. For more information, see "Troubleshooting Failure During Verifying Node Manager and OPMN Status" in the Oracle Fusion Applications Upgrade Guide.
No additional user action is required in the Configuration Progress screen unless a failure occurs. For more information, see "General Troubleshooting During the Configuration Phase in GUI Mode" in the Oracle Fusion Applications Upgrade Guide.
This screen 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 assistants completed successfully. If you want to rerun this session to resolve failed configuration assistants, click Cancel.
|
 Copyright © 2011, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|