10 Manual Patching of Oracle Fusion Applications During Offline Patching

The online mode of Oracle Fusion Applications Patch Manager (Patch Manager) supports most of the deployment actions required for patching middleware and database artifacts used by Oracle Fusion Applications. Depending on the type of artifact included in a patch, the artifact deployment may require manual actions. Some manual actions are required only if the patch is applied in offline mode, while others are always required. Before applying any patch, Oracle recommends to run the Patch Impact report to determine which artifact types are included in the patch and if manual actions are required by the patch. For more information, see the Patch Impact Report section.

Table 10-1 provides a quick reference that depicts how Patch Manager supports the Oracle Fusion Middleware artifacts that could be included in a patch. This table assumes that online patching is used unless otherwise specified.

An explanation of the information presented in this table follows:

• Automated Actions Performed by Patch Manager

  Patch Manager always copies the artifacts from the patch to the appropriate location on the system. This column describes additional actions that are performed automatically in online mode for each artifact.

• Actions to Be Performed Manually in Online Mode

  This column describes the actions that must be performed when the patch includes the specified artifact. These actions are described in more detail in this section.

• Actions to Be Performed Manually in Offline Mode and in the Case of Failures

  This column describes the actions that must be performed when the patch includes the specified artifact and the patch is applied in offline mode. If the patch is applied in online mode and there is a failure, these actions may also be required.

• What Must Be Running During Online Patching Mode and Manual Actions

  This column describes what must be running while applying the patch in online mode and when manual actions are performed.

After applying a patch, review the Diagnostics report to find out which manual steps are required for the artifacts included in the patch and where the artifacts were copied in FA_ORACLE_HOME. For more information, see the Diagnostics Report section. For more detailed information about manual actions for each artifact, refer to the relevant sections in this chapter.

The following table describes the Oracle Fusion Middleware artifacts:

The following table provides a quick reference that displays the Oracle Fusion Applications database artifacts that could be included in a patch. Database artifacts typically do not require manual actions be performed during online mode, as they are copied and deployed automatically in online mode. In offline mode, database artifacts are copied but they are not deployed. Before patching database artifacts, the database must be in an idle state with no locks being held on any of the database objects. All background jobs, including jobs in the database, must be terminated before patching to avoid locks on patched objects. There should not be any active processes, such as Oracle Enterprise Scheduler Service jobs running against the database. This is to prevent locking and other data issues during patching.

The following table describes the Oracle Fusion Database artifacts:

Oracle recommends to patch Oracle B2B metadata in online mode. When updates to Oracle B2B metadata are introduced in a patch, no manual steps are required in online mode to redeploy all Trading Partner Agreements that are affected by the metadata change.

When a patch containing Oracle B2B metada updates is applied in offline mode, and the change is implemented, Trading Partner Agreements that are affected by the metadata change must be manually redeployed. If the redeployment is not performed, the runtime continues to use the older metadata. The agreements can be deployed using the B2B User Interface (UI) or by running the b2bdeploy utility from the command line.

When the Oracle Business Intelligence Publisher (BI Publisher) artifacts (Reports and Captions) are patched in online mode, Patch Manager shuts down the BI Presentation Server before the patch applies and restarts it after successful patch application. No manual steps are required in online patching mode. If the shutdown of this server fails for any reason, the BI Publisher artifacts must be manually deployed.

Oracle recommends not to use offline mode when a patch contains BI Publisher artifacts. If applying a patch in offline mode is decided, the changes to the Oracle Business Intelligence repository must be manually deployed, in addition to stopping and restarting the BI Presentation server. These manual steps are required to keep the Oracle home and the Oracle Instance versions of the Oracle Business Intelligence Presentation Catalog synchronized. If these manual steps are not followed as described, subsequent patches containing BI Publisher artifacts may fail.

Perform the following steps to manually deploy BI Publisher artifact after applying a patch in offline mode:

1. The opmn process must be running. Follow these steps:

   1. To verify if the process is running, go to the FA_ORACLE_HOME/instance/BIInstance/bin directory and run this command:

      opmnctl status
      

   2. If the opmn process is not Alive, start it with this command:

      opmnctl start 
      

2. Patch Manager must have copied one or more Oracle BI Presentation Catalog files into the Oracle home-based catalog.

3. Within the patch, there are some catalog diff files. These files are used with the Oracle Business Intelligence Catalog Manager tool to apply changes to a catalog. These changes must be applied to:

   • The run-time, or Oracle Instance, Oracle BI Presentation Catalog

   • The Oracle home Oracle BI Presentation Catalog

4. Special care must be taken when the patch being applied is a standard patch. With a standard patch, OPatch may choose to copy only a subset of the total files in the patch archive.

   Before performing the following steps, first determine exactly which files were actually copied to the Oracle home during the OPatch apply stage. Review the Patch Impact report to get this list of files. Capture the list of files from the messages sent to the console and to the FAPatchManager_apply_timestamp.log file.

   After the list is done, apply only the diff files that correspond to the files that were actually copied to the Oracle home. The diff files are named the same as the original files, except they have a .diff extension added. If additional diff files are applied beyond the files that were actually copied to the Oracle home, then previous patch updates may be undone and the Oracle BI Presentation Catalog may be in an unsupportable state. Basically, a previous patch have been partially rolled back.

5. Shut down the BI Presentation server.

6. Unzip the middleware portion of the patch, the OPatch archive file, into a temporary location, such as C:\patch. To see which files are included in the patch, run the Patch Impact report. For more information, see the Patch Impact Report section.

7. Using the example in the previous step, go to the C:\patch\custom\scripts directory.

8. Locate the Catalog Manager diff files listed in the subdirectories under the directory in the previous step. These files have .diff extensions. This is referred to as diff_file_location in subsequent steps.

9. Use Catalog Manager to apply each of these diff files to the Oracle home Oracle BI Presentation Catalog, using the following commands:

   1. Create the Catalog Manager patch file, as follows:

      oracle-instance/runcat.sh -cmd createPatch -inputFile diff_file_location
       -production webcat_location -outputFile webcat_patch.out -winsConflict latest
      

      • diff_file_location refers to the file from the previous step

      • webcat_location is the Oracle home Oracle BI Presentation Catalog location

      • webcat_patch.out is a temporary file created by this step and used in Step 5b

        Example of oracle-instance on Unix:

        APPLICATIONS_BASE/instance/BIInstance/bifoundation
        /OracleBIPresentationServicesComponent/coreapplication_obips1/catalogmanager
        

   2. Apply the Catalog Manager patch file, as follows:

      oracle-instance/runcat.cmd -cmd applyPatch -inputFile webcat_patch.out
      -outputFile  -persistNewApplicationsRoles webcat_applypatch.out
      

      • webcat_patch.out is the file created in Step 5a

      • webcat_applypatch.out is the output file from this deployment process

10. Repeat the previous step for the run-time catalog.

11. Restart the Oracle Business Intelligence system components using opmnctl:

    cd APPLICATIONS_CONFIG/BIInstance/bin/opmnctl
    ./opmnctl stopall
    ./opmnctl startall
    

For more information, see the ”Starting and Stopping Oracle Business Intelligence" section in the System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Oracle recommends to patch Oracle BPM templates in online mode. When updates to Oracle BPM templates are introduced in a patch, no manual steps are required in online mode to publish the new Oracle BPM Template to the Oracle Metadata Services (MDS) repository.

If a patch containing updates to Oracle BPM templates is applied in offline mode, the new Oracle BPM Template must be manually published to the Oracle MDS repository supporting the Oracle BPM Composer instance after the patch is applied. Use the publish_template WebLogic Scripting Tool (WLST) command from the WLST shell. The WLST publish_template command connects to the SOA MDS data using the mds-config.xml configuration file created. Provide the location of the mds-config.xml configuration file as one of the input parameters of the publish_template command.

Perform the following steps to create the mds-config.xml configuration file:

1. Copy the mds-config-template.xml file from the SOA server installation to a local directory, as follows:

   cp SOA_ORACLE_HOME/bpm/config/mds-config-template.xml /local_directory/mds-config.xml
   

2. Modify the following properties in the recently copied file to the temporary directory:

   1. Set jdbc.userid to the database user name of the SOA MDS database

   2. Set jdbc.passwd to the database password of the SOA MDS database

   3. Set jdbc.url to the connection URL of the SOA MDS database, for example, jdbc:oracle:thin:@host2:1525:mds

   4. Set partition.name to obpm

Perform the following steps to publish the new Oracle BPM template to the MDS repository:

For more information about the publish_template command syntax, see the ”publish_template" section in the WLST Command Reference for WebLogic Server.

When updates to C artifacts are introduced in a patch, no manual steps are required in either online or offline mode. Note that before applying C artifacts, all C executable files and the Oracle Enterprise Scheduler Service servers that host the C files must be shut down and the database must be running.

When updates to Common Resource artifacts are introduced in a patch, the Administration Server, Node Manager, and database must be running. Stop and restart all Managed Servers in all domains after the patch is applied.

A conflict between Oracle supplied seed data and customized seed data may occur when applying a patch that uploads seed data. The following types of conflicts may occur:

• When uploaded seed data conflicts with a primary unique index, the customer record is preserved and the Oracle seed data is not uploaded.

• When uploaded seed data conflicts with a non-primary unique index, a uniqueness violation occurs and an automatic conflict resolution feature prevents a seed data upload failure by appending numeric values, such as _1, _2, _3, to the display value.

For more information, see the Understand the Impact of Automatic Conflict Resolution for Seed Data section.

No manual steps are required when patching DTF artifacts in either online or offline mode.

Oracle recommends to patch EWM artifacts in online mode. When updates to EWM artifacts are introduced in a patch, no manual steps are required in online mode. In offline mode, follow the steps in mentioned in the Patch Java EE Artifacts section.

Oracle recommends to patch flexfield artifacts in online mode. When flexfield changes are introduced in a patch, no manual steps are required to automatically deploy the flexfields in online mode, except to ensure that the following are running:

• Administration Server

• Managed Servers that host the FndSetup application

• Database

Users must log out and log in after a successful patch application to see the latest flexfield changes because flexfields reload upon user logout and login. If the changes to a flexfield are not implemented, it is possible to revert to a previous version of a flexfield. For more information, consult following links:

• Revert to a Previous Flexfield Definition After it is Updated by a Patch

• Manually Deploying Patched Flexfields

• Perform Flexfield NameSpaces Merge

Oracle recommends to patch IPM artifacts in online mode. When updates to IPM artifacts are introduced in a patch, no manual steps are required in online mode, other than ensuring all prerequisites are met. In offline mode, the IPM artifacts must be manually deployed.

Perform the following steps to manually deploy IPM artifacts:

1. The opmn processes must be running. Follow these steps:

   1. To verify if the process is running, go to the FA_ORACLE_HOME/CommonDomain_webtier directory and run this command:

      opmnctl status
      

   2. If the opmn process is not Alive, start it with this command:

      opmnctl start 
      

2. The imaging application must be running. The format for the IPM URL is http://host name:Port/imaging/.

3. The Financials SOA server (soa_server1) must be running.

4. The Financials Payables Invoice and Expense Report SOA composites must have been successfully deployed and be in an active state.

5. The FIN wsm-pm application must be in an active state, which means the FinancialCommon server must be running.

6. The IPM to UCM connection, "Fusion Applications UCM Connection", must exist.

7. The IPM to SOA connection, "Financial SOA Connection", must exist.

8. The IPM Input should be set to Offline from the Manage Inputs section of the IPM UI. For example, select Invoices under Manage Inputs and then deselect Online under Basic Information.

9. Follow these steps to back up the existing IPM application definition:

   1. Log in to the IPM server as the IPM super user.

   2. From Tools, select Export Definitions.

   3. Export the Oracle Fusion Payables Application and Expenses Application, all related searches, and inputs to a local file.

10. Review the Diagnostics report to find the location of the IPM artifacts that were copied to FA_ORACLE_HOME. For more information, see the Online Patch Progress Report and Diagnostics Report section.

11. Access the WLST shell, as follows:

    (UNIX) ECM_ORACLE_HOME/common/bin/wlst.sh
    

12. Deploy the IPM artifact, as follows:

    connect(IPM Server user name,IPM Server password,IPM Server hostname:port)
    importIPMApplication(ipmAppFile,'Update',appDefName,'None');
    importIPMInput(ipmAppFile,'Update',inputDefName);
    

    Example:

    connect('FAadmin','fusion','t3://IPMserver01.mycompany.com:17014');
    
    importIPMApplication(exportFile='/net/server01/fusionapps/applications/fin/ap/ipm/ApInvoiceIpmApp.xml',
    action='Update', name='Payables Invoice Application','None')
    
    importIPMInput(exportFile='/net/server01/fusionapps/applications/fin/ap/ipm/ApInvoiceIpmApp.xml', 
    action='Update', name='Payables Invoice Input') 
    

13. If applicable, perform the customizations on the new file, based on the exported file.

Oracle recommends to you patch Java EE artifacts in online mode. When Java EE artifacts are patched in online mode, no manual steps are required, except to ensure that the following are running:

• Administration Server

• Node manager

• Database

In offline mode, manually stop, patch, and restart the impacted Managed Servers that host the Java EE application. To determine which product family is affected by the patch being applied, run the Patch Impact report. For more information, see the Run the Patch Impact Report section. For example, if the Patch Impact report indicates that the patch updates a Java EE artifact in the Financials Domain, then the Financials Domain must be stopped, apply the patch, and then start the Financials Domain after the patch applies successfully. Examples of artifacts in this category include Oracle ADF Resource JAR files and Oracle Enterprise Scheduler Service MAR files.

Oracle recommends to patch ODI artifacts in online mode. When updates to ODI artifacts are introduced in a patch, Patch Manager imports the ODI changes in online mode. If ODI artifacts are patched in offline mode, the changed ODI content must be manually imported to the ODI repository. In both online and offline modes, the ODI repository import tool and the database must be running.

Oracle Fusion Applications Provisioning does not install ODI Studio. ODI Studio must be installed before manually importing ODI changes. Therefore, ODI Studio must be installed before applying the patches that deliver ODI changes in offline mode or when a failed ODI import step is required to be manually retried in online mode.

Manually Importing ODI Changes

Oracle recommends that the ODI import be performed from a machine that is co-located in the same subnetwork as the database server to maximize performance. The following steps shows the instruction for the Manual Import ODI Changes:

1. Review the instructions in the patch README file to determine which ODI Project or Model must be deleted and imported again. The patch README file contains a list of the ODI files that are included in the patch, in the order that they must be imported.

2. Review the Diagnostics report to determine the location and file name for each ODI artifact that is to be imported. For more information, see the Online Patch Progress Report and Diagnostics Report section.

3. Start the ODI Studio, as follows:

   (UNIX) odi.sh
   

4. Access the ODI Studio. Follow these steps:

   1. Select View, then ODI Designer Navigator.

   2. Click Connect to Repository.

   3. Log in using the super user name and password for the ODI repository.

5. Delete the Model or Project if specified in the patch README file. The README file specifies whether any Model or Project must be deleted and in what order.

   Right-click the Model or Project name and click Delete.

6. Import the ODI files in the order they are listed in the patch README file. Follow these steps:

   1. To import a project, right-click the Project name and click Import, then Import Project.

   2. To import a model, right-click the Model name and click Import, then Import Model.

   3. Select Synonym Mode INSERT_UPDATE from the list in the Import Dialog window.

   4. For the File Import directory, select the directory that contains the ODI file to be imported.

   5. Select the ODI file to import.

   6. Click OK to import.

   Repeat Steps 5 and 6 for each Model or Project in the patch.

7. Close the ODI Studio after importing all the files in the order specified in the patch README file.

Oracle Forms Recognition (OFR) and Oracle Document Capture (ODC) artifacts are used only by Windows. When a patch that contains OFR and ODC artifacts is applied, Patch Manager backs up the customized files, if any, before copying the new files to FA_ORACLE_HOME., the OFR and ODC artifacts that were delivered in the patch must be manually installed. If the OFR and ODC have not been installed, refer to the Set Up Oracle Document Capture and Oracle Forms Recognition section in the Oracle Fusion Applications Installation Guide for the installation steps. Then return to this section for patching.

Install OFR Artifacts

If the AP_Packaged_Project_1004a.ini file was previously customized, then this file should not be installed from the patch as the patch delivers it. Instead keep the existing file and copy the file from the patch to a directory with a different name. Then compare the files and manually update the existing file with the changes to preserve the customizations, as follows:

1. Review the Patch Impact report to find the location of the files related to OFR.

2. Rename the file AP_Packaged_Project_1004a.ini to another name as a backup and copy APPLICATIONS_BASE/fusionapps/fin/ap/ofr/AP_Packaged_Project_1004a.ini to a new file on the Windows environment.

3. Move this .ini file to the OFR AP Project directory, which is located in the OFR directory structure, Projects\AP\Global (for example, C:\Program Files\OFR\Projects\AP\Global). If the existing AP_Packaged_Projects_1004a.ini file is in this location, rename it to a backup file.

4. Create a data link:

   1. Click the Windows Start menu button.

   2. Select Run.

   3. Enter Notepad into the Open field and click OK.

      Do not right click on the desktop to create a new file. Windows will assign a hidden file type to the file that will interfere with the following steps.

   4. Click File - Save.

   5. Navigate to the Desktop folder.

   6. In the File name field, enter the following, including quote marks: "odbc_dns.udl". Substitute the actual ODBC data source name for odbc_dns. The data source name can be found by opening the Control Panel, then Administrative Tools, and Data Source (ODBC).

   7. Click Save.

   8. Find the file on the desktop and double-click it to open the Data Link Properties dialog. If a text file is opened instead, go back and carefully follow the instructions for creating this file again.

   9. Set Data Source: ODBC data source name

   10. Select the Use a specific user name and password option.

   11. Enter the READ-ONLY user name and password

   12. Select the Allow saving password option.

   13. Select Test Connection.

   14. Click OK. An example of the file contents follows:

       Provider=MSDASQL.1;Password=fusion;Persist Security Info=True;User ID=fusion;Data Source=ffinde
       

5. Open the data link (.udl file) previously created, as follows:

   1. Click the Windows Start menu button.

   2. Select Run.

   3. Enter Notepad into the Open field and click OK.

   4. Open the .udl file.

   5. From the .udl file, copy the entire string, starting with Provider=.

6. Open the AP Packaged Project_1004a.ini file (under C:\OFR_Projects\AP\Global) in another instance of Notepad and make the following changes:

   1. Replace the connection string for the line starting with SQL_VL_01_ConnectionString=, with the text copied in Step 5.

   2. Update attribute ASA_VL_01_ImportODBCDSN with the System DSN name of the Oracle Fusion Applications database.

   3. Update attribute ASA_VL_01_ImportODBCUser with the READ-ONLY user name.

   4. Update the attribute, ASA_VL_01_ImportODBCPWD, with the READ-ONLY account password.

   5. Proceed with any additional customizations on the .ini file, as required by the implementation.

   6. Verify the changes.

   7. Save and close the file.

Update ODC Expenses Metadata

Perform the following steps to update ODC Expenses metadata:

1. Install the ODC Import-Export Utility from the Companion DVD, if this has not already been done.

2. Copy the ODC metadata ZIP files from APPLICATIONS_BASE/fusionapps/fin/ap/odc and APPLICATIONS_BASE/fusionapps/fin/exm/odc to a temporary directory in the Windows desktop environment.

3. Go to Start, then Oracle Document Capture, then Import-Export Utility and log in. The user name is ADMIN and the password is admin.

4. In the utility, go to File - Import or click Import and then import the metadata files one at a time. Ensure that all files are imported.

When updates to Oracle Fusion Applications Patch Manager are introduced in a patch, the patch must be applied with the OPatch utility. Oracle Fusion Applications is compatible with a specific version of OPatch instead of the generic version of OPatch. If an incompatible version of OPatch exists in FA_ORACLE_HOME, errors can occur while applying patches and running Upgrade Orchestrator. The compatible version of Opatch is available on My Oracle Support under patch 14044793.

During provisioning, the data model for Oracle Fusion Applications Patch Manager is updated by running the fapmgr bootstrap command. If the data model is updated again by a patch, the patch README file instructs to run the fapmgr bootstrap command.

Use this syntax to run bootstrap:

(UNIX) FA_ORACLE_HOME/lcm/ad/bin/fapmgr.sh bootstrap [-logfile log_file_name] [-loglevel level]

In Oracle Fusion Applications, the following artifact types related to security can be patched:

• Function Security Policies (Applications Policies, using the system-jazn-data.xml file)

• Data Security Grants (using Seed Data)

• Data Role (RGX) Templates

• JAR files secured by the Data Security Grants and Function Security Grants

A patch can contain one or more of these artifacts. This section describes the steps for applying security patches and recovering from patch failures. Examples of scenarios that may be needed when following the recovery steps include:

• Apply a security patch that introduces a set of new policies and LDAP GUIDs, after backing up the policy store and the applications database. The GUID reconciliation has not been performed with the applications database due to an unrelated database issue. To resolve the database issue, restore from the backup, resulting in the policy store containing extra GUIDs from the database and a synchronization issue between the policy store and the database.

• Apply a security patch that includes updates to the applications policies and the patch fails, resulting in a set of LDAP GUIDs not applying correctly.

The patching and recovery scenarios for the following combinations of security artifact patches are included:

• Patch Applications Policies (system-jazn-data.xml)

• Patch Data Security Grants

• Patch Data Role (RGX) Templates in Offline Mode

• Patch Data Security Grants and Data Role (RGX) Templates

• Back up the Data Security Store

• Recover Data Security Seed Data from the Backup

Oracle recommends to apply security patches in online mode and run the Patch Impact report to understand which artifacts are included in the patch. The Patch Impact report displays security artifacts as JAZN, Data Security, and RGXTEMPLATE. For more information, see the Patch Impact Report section.

When updates to SOA composites are introduced in a patch, no manual steps are required if both of the following conditions are met:

• SOA composite customizations are not available in Oracle JDeveloper. If customizations exist, follow the steps in the Preserve SOA Composite JDeveloper Customizations Before Applying a Patch section.

• Apply the patch in online mode and no validation or deployment errors occurred during the application of the patch that contains SOA composites. Oracle recommends not to use offline mode when a patch contains SOA composites. If the patch fails while attempting to deploy a SOA composite, manually deploy the composite. For more information, see the Manually Deploy SOA Composites section.

For information about resolving validation errors, see the Troubleshoot SOA Composite Validation Failures section. For information about recovering from deployment errors, see the Troubleshoot SOA Composite Deployment Failures section.

If SOA composites used by Oracle Fusion Applications are customized in JDeveloper, preserve these customizations before applying a patch that includes the next revision of the composite. Other customizations to the SOA composite being patched are automatically merged by the SOA deployment command called during patching. These runtime customizations, such as design time and run-time (DT@RT) changes or property changes, do not require a manual merge process.

What must be running when patching SOA composite:

• Administration Server

• SOA-INFRA Managed Servers

• Database

• At least one server must be running the Policy Manager component from the Web Services Manager (WSM-PM) application. Typically in an Oracle Fusion Applications environment, this is the Common Cluster, for example in the CRMDomain, it is the CRMCommonCluster. Find out which server is running by logging in to Fusion Applications Control to verify that the application named wsm-pm is running with an OK or green status.

Oracle recommends to patch SOA resource bundles in online mode. No manual steps are required when patching SOA resource bundles in online mode unless the SOA resource bundle JAR file contains translatable strings for human task-mapped attribute labels and standard view names, as indicated by a JAR name that ends with FlexFieldSoaResource.jar. In offline mode, in case of patch failure, or if the patch contains human task-mapped attribute labels and standard view names, manually deploy the SOA resource bundle and restart the SOA composites that depend on the SOA resource bundle.

The following must be running when SOA resource bundles are patched:

• Administration Server

• SOA-INFRA Managed Servers

• Node manager

• Database

After applying the patch, refer to the Diagnostics Report section to get a complete list of composites that depend on each SOA resource bundle and also the domains.

Manually Deployment SOA Resource Bundle JAR Files

Perform the following steps to manually deploy SOA resource Bubdle JAR files:

1. From the Diagnostics report for patch validation, review the list of SOA resource bundle JAR files included in the patch and the domain where they should be deployed. Use the ant-sca-deploy.xml script to deploy the appropriate SOA cluster for each JAR included in the patch.

   Set the ANT_HOME variable:

   ANT_HOME=FA_ORACLE_HOME/modules/org.apache.ant_1.7.1; export ANT_HOME
   

   Deploy the appropriate cluster:

   ant -f Middleware_Home/SOA_Suite_Home/bin/ant-sca-deploy.xml
        -DserverURL=URL_to_SOA_server
        -DsarLocation=Location_of_resource_bundle_jar under FA_ORACLE_HOME
        -Duser=weblogic
        -Dpassword=weblogic_password
   

2. The Diagnostics report lists the composite affected by the patch and the domain where the composite is deployed. Follow these steps for each affected composite:

   1. Log in to in the domain where the composite is deployed.

   2. Go to domain name, then SOA, then soa-infra (SOA cluster name), then default, and then composite name.

   3. Click Shut Down.

   4. Click Yes in the confirmation window.

   5. Click Start Up.

   6. Click Yes in the confirmation window.

3. Review the list of SOA resource bundle JAR files being patched. If a patch contains a JAR file with a name which starts with "jar_" and ends with "FlexFieldSoaResource.jar", for example, jar_AppCmmnCompNotesFlexFieldSoaResource.jar, perform the following steps to ensure that the patched resource bundle is reflected in the Oracle BPM Worklist. These steps describe how to set the WorkflowCustomClasspathURL MBean property to null, and then set it to oramds:///apps/resource/ and apply the changes in Fusion Applications Control.

   1. Log in to Fusion Applications Control in the domain where the JAR was deployed.

   2. Go to SOA, then soa-infra in the left-hand panel. Go to SOA Infrastructure, then Administration, and then System MBean Browser in the right-hand panel.

   3. Go to Application Defined MBeans, then oracle.as.soainfra.config, then Server: SOA cluster name, then WorkflowConfig and then human-workflow.

   4. Remove the contents in the Value column of the WorkflowCustomClasspathURL attribute.

   5. Click Apply.

   6. Enter oramds:///apps/resource/ in the Value column of the WorkflowCustomClasspathURL attribute.

   7. Click Apply.

The following documents provide additional information related to subjects discussed in this section:

• For more information about the ant-sca-deploy.xml script that is used to deploy the SOA resource bundle, see "How to Manage SOA Composite Applications with ant Scripts" in the Developing SOA Applications with Oracle SOA Suite.

• For information about shutting down and starting up SOA composites in Oracle Enterprise Manager, see "Managing the State of Deployed SOA Composite Applications" in the Administering Oracle SOA Suite and Oracle Business Process Management Suite.

Oracle recommends to patch data role templates in online mode. When updates to SPE Inline Service artifacts are introduced in a patch, no manual steps are required in online mode to deploy changed SPE artifacts.

Updates to SPE Inline Service are delivered in the SPE_ILS.zip file and the AdfZspPredictionModuleSupportUtilities.jar file. This section contains information about manual deployment of SPE artifacts, in the case of offline patching or failure during online patching.

SPE artifacts are provisioned only when Oracle Fusion CRM Performance Management is provisioned. If CRM Performance Management is not provisioned in the environment, do not deploy SPE artifacts.

Manually Deploying SPE Artifacts After Applying the Patch

Perform the following steps:

1. JDK 1.6 or later must be running.

2. Access to the ZIP file, rtd-deploytool-11.1.1.zip. This ZIP file resides inside another ZIP file, FA_ORACLE_HOME/bi/clients/rtd/rtd_client_11.1.1.zip.

3. Make a backup copy, in a temporary directory, of the existing SPE_ILS.zip file, which is located under FA_ORACLE_HOME in this directory:

   (Unix) crm/components/crmPerformance/zsp/predictionmodule/inlineservice
   

4. Oracle suggests to refer to the text file that was created when provisioning completed, which is a textual overview of the topology, as you follow these steps.

5. Stop and start bi_server1 to include the changes in AdfZspPredictionModuleSupportUtilities.jar.

6. Follow these steps to deploy the new SPE_ILS.zip artifact:

   1. Unzip rtd_client_11.1.1.zip in a temporary directory. To find this file, refer to Step 2 in this section.

   2. In the unzipped files, go to the folder .../client/CommandLineDeploy and find rtd-deploytool-11.1.1.zip.

   3. Unzip rtd-deploytool-11.1.1.zip and go to the folder, .../OracleBI/RTD/deploytool.

   4. In this folder, open a command terminal. Ensure having the JDK class path set for this terminal.

   5. Run this command:

      java -jar deploytool.jar -deploy 
      -server Host name of the server where BI domain is created
      -port Managed server port where the OracleRTD app is deployed
      -terminateSessions true Full directory path to SPE_ILS.zip
      

      Example:

      (UNIX) java -jar deploytool.jar -deploy -server server01.oracle.com -port
      7001 -terminateSessions true FA_ORACLE_HOME/crm/components/ \
      crmPerformance/zsp/predictionmodule/inlineservice/SPE_ILS.zip
      

   6. When prompted, enter the user name and password to connect to the RTD server. This user must have a role that includes ILS deploy permission. Both the BIAdministrator and BIAuthor have this permission.

   7. This message indicates the deployment is complete:

      deploymentStateId is 5Inline service "SPE_ILS" in "FA_ORACLE_HOME/crm/components/crmPerformance/zsp/predictionmodule/inlineservice/SPE_ILS.zip/SPE_ILS.zip" 
      deployed to server: "server01.oracle.com" port: "7001" deployment state: "Development"
      

Tree artifacts are delivered as seed data in patches and therefore, do not typically require manual steps after they are patched. A process called tree flattening automatically runs during the patching process. If this process fails, perform the following additional steps:

1. To determine if the patch contains any files related to tree flattening, refer to the Patch Impact report and look for a file named FndTreeVersionSD.xml. This is the only file that requires tree flattening. For more information, see the Patch Impact Report section.

2. Confirm that the tree version changes were successfully flattened by reviewing the worker logs for errors related to tree flattening. To determine the worker that executed the specific seed data task, based on the file name FndTreeVersionSD.xml, refer to the Diagnostics report generated at the end of the patching session. Note any tree versions that failed because the version numbers are needed to manually flatten the tree version changes.

3. Follow these steps to manually flatten tree versions:

   1. Access the administrative area of Oracle Fusion Functional Setup Manager by logging in to Oracle Fusion Applications with a user account that is provisioned with the necessary role. Contact the security administrator for details.

   2. From the Administration menu in the work area of Oracle Fusion Applications, choose Setup and Maintenance.

   3. Choose the Manage Trees and Tree Versions task.

   4. Search for the tree versions that require flattening.

   5. Choose the appropriate tree version and optionally choose Audit from the Actions menu to diagnose the issues.

   6. If changes to the tree version need to be made, click the tree version and edit it.

   7. Choose Flattening, Row Flattening, then Flattening, Column Flattening from the Actions menu to flatten the selected tree version.