| Oracle® Fusion Applications Upgrade Guide 11g Release 7 (11.1.7) Part Number E35833-18 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Applications Upgrade Guide 11g Release 7 (11.1.7) Part Number E35833-18 |
|
|
PDF · Mobi · ePub |
This chapter describes the tasks you must perform after you complete the steps in Chapter 4, "Upgrading to Oracle Fusion Applications Release 7".
This chapter contains the following topics:
Add Administration Servers to the Machine Created During Scale Out
Confirm the Informatica Identity Resolution (IIR) Server is Running
Resolve Conflicts That Occurred During Oracle BI Metadata Updates
Upgrade Oracle Fusion Project Portfolio Management Integration with Primavera P6
Note that Upgrade Orchestrator runs Health Checker for post-upgrade checks automatically, but if you want to run Health Checker manually, see Section A.2.2.3, "How to Run Health Checker.".
Confirm that the deployment of artifacts updated during the Load Database Components configuration assistant was successful by reviewing the Diagnostics report and log files. For more information, see "Diagnostics Report" in the Oracle Fusion Applications Patching Guide. Confirm the successful deployment for both Release 6 and Release 7 if you performed a chained upgrade.
Review the Post RUP Installer report to check for any errors or warnings that require attention. The Post RUP Installer report provides an overview of the tasks that Upgrade Orchestrator ran when it called RUP Installer. It is generated in HTML and XML files and includes links to log files. If you performed a chained upgrade, review the Post RUP Installer for the upgrade to Release 6 as well as the upgrade to Release 7.
The Post RUP Installer report displays the following information:
Configuration Assistant: The name of the configuration assistant.
Attempts: The number of times the configuration assistant ran.
Time Taken: The duration of the configuration assistant in minutes and seconds.
Result: The result of the configuration assistant, such as PASSED or FAILED.
Errors: Any errors that were reported during the configuration assistant.
Log Files: Link to log files for the configuration assistant.
For Release 6, the Post RUP Installer report files are located here:
FA_ORACLE_HOME/admin/FUSION/log/fapatch/fapatch_11.1.6.0:
PostRUPInstallerReport_20130613024237.html
PostRUPInstallerReport_20130613024237.log
PostRUPInstallerReport_20130613024237.xml
For Release 7, the Post RUP Installer report files are located here:
APPLICATIONS_CONFIG/lcm/logs/11.1.7.0.0/RUP:
PostRUPInstallerReport_20130610151550.html
PostRUPInstallerReport_20130610151550.log
PostRUPInstallerReport_20130610151550.xml
For information about resolving errors, see Chapter 6, "Monitoring and Troubleshooting the Upgrade".
Review the Oracle Fusion Applications Orchestrator Upgrade Report to check for any errors or warnings that require attention, to confirm whether the upgrade completed successfully. If there were previous failures during the upgrade, this report would have been generated each time there was a failure. The report name is FAOrchestrationUpgradeReport_release_hosttype_hostname_timestamp.html. The Upgrade Orchestrator report is generated for each pod and its location is defined in the mandatory ORCH_REPORT_LOCATION property in the pod.properties file. Previous reports are archived and available for troubleshooting purposes. For more information, see Section 1.3.4, "Oracle Fusion Applications Orchestrator Upgrade Report".
Review the JAZN Analysis reports for potential conflicts and deletions that are not patched automatically during the upgrade. The reports are located in this directory:
FA_ORACLE_HOME/admin/JAZN/stripe/delta/report.txt
The stripe is crm, fscm, hcm, obi, soa, ucm or bpm.
Review the Modification section of the report to see the roles that were not updated during the upgrade. For each conflict that displays in this report, you must evaluate and manually patch the role by using Oracle Authorization Policy Manager (APM). For more information, see "Upgrading Oracle Fusion Applications Policies" in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition).
The following example shows a typical Application Role conflict that has been modified by both the patch and production, therefore it is not applied during the upgrade.
MODIFICATION CONFLICTS Artifact type: Application Role Artifact Name: OBIA_PARTNER_CHANNEL_ADMINISTRATIVE_ANALYSIS_DUTY Description: This artifact is modified at attribute level in patch version and also in production.
Note the location of the following files for reference when using APM:
Location of baseline files, where stripe is crm, fscm, hcm, obi, soa, ucm or bpm:
FA_ORACLE_HOME/admin/JAZN/stripe/baseline
Location of patch files for fscm, crm, and hcm stripes:
FA_ORACLE_HOME/stripe/deploy/system-jazn-data.xml
Location of patch files for the obi, soa, ucm or bpm stripes:
FA_ORACLE_HOME/com/acr/security/jazn/bip_jazn-data.xml
Perform this step if you have customized BI Publisher reports.
Reload custom templates for BI Publisher reports on Oracle-delivered BI Publisher reports by following the steps in "Task: Upload the Template File to the Report Definition" in the Oracle Fusion Applications Extensibility Guide for Business Analysts.
Perform the steps in this section only if the steps in Section 2.5.5, "Validate Domain Directories" required you to temporarily add any Administration Servers back to the originally provisioned machine.
Log in to the WebLogic console for the domain.
Navigate to Environment, then Machines.
Find the machine that was created manually for the purposes of AdminServer high availability scaleout.
Click on the machine and go to the Servers tab.
Click Lock & Edit to make changes.
Click Add.
Select the AdminServer and click Finish.
Click Activate Changes to apply the changes.
Note:
Perform the step in this section only if you are running Oracle Fusion Applications in an Oracle VM environment that was created from the official releases of Oracle VM templates for Oracle Fusion Applications Release 2 (11.1.2) and higher. The content is not applicable for any Oracle VM environments that are created using other methods.
Stop and start the servers on the Common Domain and the CRM Managed Server to remove WebChat connections that were disabled by the DisableWebchatConnections plug-in when you ran RUP Lite for OVM. For more information, see "Starting and Stopping the Administration Servers and Managed Servers" in the Oracle Fusion Applications Administrator's Guide.
Run the following script to delete Webchat tablespaces:
Ensure that there are no guaranteed restore points in the database by performing the following steps:
Connect as SYS user.
Run the following SQL query:
SELECT NAME, SCN, TIME, DATABASE_INCARNATION#,GUARANTEE_FLASHBACK_DATABASE,STORAGE_SIZE FROM V$RESTORE_POINT WHERE GUARANTEE_FLASHBACK_DATABASE='YES';
If there are restore points returned by the query, drop the restore points and continue with the next steps.
To delete Webchat tablespaces, perform the following steps to run the script that is located on the primordial host.
Connect to the fusion database as SYSDBA user.
Run the following script:
/u01/lcm/rupliteovm/ovm/scripts/dropwebchattablespaces.sql
Note:
If the restore point is still required, perform the steps in this section until the restore point is no longer required, and is dropped.
Confirm the IIR server is running. If it is not running, follow the steps in "Troubleshooting Informatica Identity Resolution and Data Quality Setup" in the "Define Data Quality" chapter of the Oracle Fusion Applications Customer Data Management Implementation Guide to manually check for files that need to be cleaned up and to retry the steps to start the server.
Follow any post-upgrade steps mentioned in the Post-Upgrade Known Issues section of Release Notes for Oracle Fusion Applications 11g Release 7 (11.1.7.0.0).
Upgrade Orchestrator updates the applications policies for Oracle Business Intelligence during the Apply Offline BI Metadata and Configuration Updates configuration assistant. When Upgrade Orchestrator runs the Apply Online BI Metadata and Configuration Updates configuration assistant, it updates the Oracle BI Applications metadata in the Oracle BI repository and the Oracle BI Presentation Catalog for Oracle Fusion Transactional Business Intelligence and Oracle Business Intelligence Applications.
Note:
This section refers to different Oracle BI directory paths. The BI Oracle home contains the binary and library files necessary for Oracle BI. BI_ORACLE_HOME represents the BI Oracle home in path names.
For more information about the Oracle BI directory structure, see "Oracle Business Intelligence Directory Structure" in Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence.
Also, see "Understanding Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide for information about the Fusion Middleware directory structure.
This section contains the following topics:
When you run Upgrade Orchestrator, the Oracle BI Metadata Update Tool overwrites all customizations to catalog objects in the Presentation Catalog with the new Oracle-supplied content and logs conflicts in a conflict report.
After Upgrade Orchestrator completes, you must review the conflict report and decide whether you want to retain the new content or re-apply your customizations using a manual process.
Points to Consider
The folders, /shared/backup/shared and /shared/backup/system, are created in the updated Presentation Catalog during the Upgrade Orchestrator and the Metadata Update Tool process. You access these folders through the Folders pane of the Catalog page in the Oracle BI Enterprise Edition user interface, as described in the following procedure.
Note: The /shared/backup folder should not exist before Upgrade Orchestrator runs, because the updated Presentation Catalog file will not be copied to this folder if it already exists.
As a precaution, to ensure the /shared/backup folder does not exist before Upgrade Orchestrator runs, you can optionally create an environment variable called webcat.force.restore, which will overwrite the contents of an existing /shared/backup folder. This environment variable must be set in the shell prompt from where the orchestrator is going to be invoked, using the command, setenv webcat.force.restore true.
Conflicts that arise during Upgrade Orchestrator and the Metadata Update Tool process are stored in the folder /shared/backup/shared in the updated Presentation Catalog. Object references that have conflicts are also stored in /shared/backup/shared.
To resolve conflicts in the Presentation Catalog:
Locate the conflict report named update-conflict-report.txt, which is stored in the folder BI_SHARED_DIR/.biapps_patch_storage/update/Run_ID.
Sign in to Oracle Business Intelligence Enterprise Edition (Oracle BI EE).
See "Signing In to Oracle BI Enterprise Edition" and "Navigating Oracle BI Enterprise Edition" in Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition (Oracle Fusion Applications Edition) for instructions on signing in and navigating in the Oracle BI EE user interface.
Click Catalog in the global header.
In the Folders pane, navigate to Shared Folders, backup, and then shared folder.
Open an object that has a conflict. This object depicts the state of the object before Upgrade Orchestrator and the Metadata Update Tool were run.
Open a second instance of Oracle BI EE and the Presentation Catalog.
Navigate to the Shared Folders folder.
Open the same object you opened in step 5. This object depicts the state of the object after Upgrade Orchestrator and the Metadata Update Tool were run (and after the metadata updates were applied).
Compare the two objects and decide whether you want to retain the Oracle-supplied updated content or re-apply your customization from the previous version of the Presentation Catalog.
To re-apply your customization to an updated object, manually edit the object.
Repeat steps 5 through 10 for all objects that have conflicts.
When you run Upgrade Orchestrator, the Oracle BI Metadata Update Tool performs a safe upgrade on the Oracle Business Intelligence policy store, which means it updates only the metadata content that does not conflict with your customizations. Updated content that conflicts with your customizations is not applied. Conflicts are listed in the Oracle BI Metadata Tool update report, located at BI_SHARED_DIR/.biapps_patch_storage/update/Timestamp/policystore_delta/report.txt.
This procedure provides instructions for overriding the customizations of the previous Oracle Business Intelligence policy store by applying the Oracle-supplied updated content. This procedure uses Oracle Authorization Policy Manager. For detailed information about upgrading Oracle Fusion Applications policies using Oracle Authorization Policy Manager, see "Upgrading Oracle Fusion Applications Policies" in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition).
Note: You do not need to back up your existing policy store file, because the Metadata Update Tool process does not overwrite your customizations.
To resolve conflicts in the policy store:
Log in to the Authorization Policy Manager Administration Console.
See "Getting Started With Oracle Authorization Policy Manager" in Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition) for instructions.
Navigate to the Home tab of the Policy Upgrade Management page.
Click Patch Application in the upper-left corner of the page to display the Patch Application dialog.
Select the appropriate application from the Application list.
In the Patch File field, specify the new patch file name and location, for example, BI_ORACLE_HOME/bifoundation/admin/provisioning/biapps-policystore.xml.
In the Baseline field, specify the previous policy store that was backed up by the Oracle BI Metadata Update Tool, for example, BI_ORACLE_HOME/.biapps_patch_storage_UPGRADE_from_VERSION/OH_BACKUP/bifoundation/admin/provisioning/biapps-policystore.xml.
Navigate to the Patch Details tab to view the policy store conflicts.
See the sections titled "Analyzing Patch Differences" and "Resolving Changes and Conflicts" in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition) for instructions on taking the appropriate action regarding conflicts.
If you are deploying Oracle Business Intelligence Applications, then you must perform the post-installation or upgrade steps specified in "Roadmap for Installing, Setting Up, and Upgrading Oracle BI Applications" in the Oracle Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications.
If you have installed Oracle Fusion Project Portfolio Management and configured it to integrate with Primavera P6 Enterprise Project Portfolio Management, then perform the following manual steps, depending on whether you are upgrading from Release 6 or from Release 5.
Perform the following steps if you are upgrading from Release 5:
Register the Primavera P6 Endpoint address details in Oracle Fusion Functional Setup Manager.
Click Topology Registration > Register Enterprise Applications and add the following enterprise application:
Enterprise Application: PJGP6 Primavera Application
Name: PJGP6_Primavera1
Enter the host and port server details where the P6 integration service is deployed:
Server Protocol: http
External Server host: host of the P6 integration service
External Server port: port of the P6 integration service
Upgrade the Fusion PPM Bridge and other related configurations in Primavera P6. For more information, see "Upgrading to Fusion REL 6" in the Primavera P6 EPPM Administrator's Guide for an Oracle Database.
Perform this step if you are upgrading from Release 6.
Upgrade the Fusion PPM Bridge and other related configurations in Primavera P6. For information on upgrading and working with Oracle Fusion Project Portfolio Management, see "Updating Fusion PPM Bridge in WebLogic" in the Primavera P6 EPPM Administrator's Guide for an Oracle Database.
This section is applicable only if you plan to use the Human Capital Management (HCM) Workforce Reputation Management product packaged with the Workforce Deployment, or Workforce Development product offerings.
The physical machine hosting HCM Workforce Reputation Management (WorkforceReputationServer_1) managed server must have a minimum of 24 GB of memory. You need to allocate 8 GB of memory to the HCM Workforce Reputation Management (WorkforceReputationServer_1) managed server. The HCM Workforce Reputation Management externalization process may use up to 16 GB of memory.
Perform the following steps to specify memory allocation for HCM Workforce Reputation Management (WorkforceReputationServer_1) managed server:
Edit the fusionapps_start_params.properties file located under APPLICATIONS_CONFIG/domains/host_name/HCMDomain/config.
Locate the # HCMDomain: Main Settings section in the file. Replace the line:
fusion.HCMDomain.WorkforceReputationCluster.default.minmaxmemory.main=-Xms512m -Xmx2048
with:
fusion.HCMDomain.WorkforceReputationCluster.default.minmaxmemory.main=-Xms4096m -Xmx8192m
Save the fusionapps_start_params.properties file.
Restart HCM Workforce Reputation Management (WorkforceReputationServer_1) managed server either from the WebLogic console or Enterprise Management for the HCM domain. For more information, see "Chapter 4, Performing Routine Administrative Tasks" in the Oracle Fusion Applications Administrator's Guide.
Ensure you have applied the following high water mark patch bundles on your current environment prior to upgrading to next release:
Fusion Middleware Patch Bundles for Fusion Applications
Fusion Application Patch Bundles
To get more information about high watermark patch bundles, contact Oracle Support.
|
 Copyright © 2011, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|