| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.1.5) Part Number E16602-08 |
|
|
View PDF |
| Oracle® Fusion Applications Patching Guide 11g Release 1 (11.1.1.5) Part Number E16602-08 |
|
|
View PDF |
This chapter describes how to apply patches to update Oracle Fusion Functional Setup Manager.
This chapter contains the following topics:
Oracle Fusion Functional Setup Manager enables rapid and efficient planning, implementation, and deployment of Oracle Fusion Applications through self-service administration. The code for Functional Setup Manager is maintained in the ATGPF_ORACLE_HOME for Oracle Fusion Applications.
The same set of patching related software and database tables is used by both Functional Setup Manager and Oracle Fusion Middleware Extensions for Applications (Applications Core). You run Oracle Fusion Applications AutoPatch directly to apply an applications database patch for Functional Setup Manager. For more information, see Section 5.1, "Patching Applications Core Database Artifacts". The patch README file for Functional Setup Manager patches contains information to assist you in performing the patching steps correctly.
Table 6-1 lists the types of artifacts that are supported for Functional Setup Manager.
Table 6-1 Database Artifacts Supported for Functional Setup Manager
| Artifact Type | Description | Patching Recommendations |
|---|---|---|
|
Applications Seed Data (XML,XLF files) |
Examples include static lists of values, functional or error messages, and lookup values. Any non-transactional data values loaded into your database can be considered seed data. |
Oracle recommends that patches containing seed data be applied from a machine that is collocated in the same subnetwork as the database server to maximize performance. |
|
Applications Database schema changes (SXML files) |
Examples include tables, triggers, views, sequences, synonyms, queues, queue tables, policies, and contexts. |
To apply a Functional Setup Manager database patch, follow the steps in Section 5.1.2, "Running Oracle Fusion Applications AutoPatch".
Functional Setup Manager requires middleware artifacts that are deployed on the WebLogic Server.
Functional Setup Manager requires certain middleware artifacts that may need to be patched. Table 6-2 displays these middleware artifacts along with actions that need to be performed manually after you apply the patch and what must be running while you apply the patch and perform the manual actions.
Table 6-2 Oracle Fusion Middleware Artifacts Required by Functional Setup Manager
| Artifact Type | Actions to Be Performed Manually | What Must Be Running During Patching and Manual Actions |
|---|---|---|
|
Oracle ADF JAR |
Start and stop the relevant servers that host the Java EE application. |
Administration Server, node manager, database. |
|
Applications Policies ( |
Follow the steps in Section 6.3.3, "How to Patch Applications Policies (jazn-data.xml)". |
Oracle Authorization Policy Manager, security policy server. |
|
Oracle Business Intelligence Publisher (Reports and Captions) |
Shut down the BI Presentation server before patching, deploy to Business Intelligence repository, and start the BI Presentation server after patching. |
Shut down the BI presentation server before patching. See Section 4.4, "Patching Oracle Business Intelligence Publisher Artifacts". |
|
Oracle Enterprise Scheduler Service MAR |
Stop and start the relevant servers that host the Java EE application. |
Administration Server, node manager, database. |
You use the OPatch utility to patch Functional Setup Manager middleware artifacts. The patch README file for Functional Setup Manager patches contains information to assist you in performing the patching steps correctly. Follow the steps in Section 5.2, "Patching Applications Core Middleware Artifacts".
The following steps must be performed if you patch applications policies.
Back up function security policies in the Oracle Internet Directory (OID) Policy store by following the steps in "Prerequisites to Patching Policies" in the Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition).
Deploy on the FSCM policy stripe using Oracle Authorization Policy Manager. The jazn files are available in ATGPF_ORACLE_HOME/setup and ATGPF_ORACLE_HOME/setupEss directories. For more information, see "Upgrading Oracle Fusion Applications Policies" in Oracle Fusion Middleware Oracle Authorization Policy Manager Administrator's Guide (Oracle Fusion Applications Edition). Note that FSM is only one of the components in the FSCM stripe and there are other components in the same stripe that you should not update.
Oracle Fusion Applications AutoPatch creates log files in the ATGPF_ORACLE_HOME/admin/APPLCORE directory. For more information, see Section 5.3, "Log Files".
The AD Controller utility, adctrl, can monitor and control the progress of the workers called by Oracle Fusion Applications AutoPatch to update database content. For more information, see Section 5.4, "Monitoring and Troubleshooting Patching Sessions".
AD Administration is a standalone utility that performs administration maintenance tasks for the products in ATGPF_ORACLE_HOME. The general purpose of the maintenance tasks is to keep your ATGPF_ORACLE_HOME files and database objects up-to-date. Some maintenance tasks should be performed systemwide on a regular basis, while others are required infrequently. For more information, see Section 5.5, "Performing System Maintenance Tasks".
|
 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
