Oracle Fusion Middleware Patching Guide

Oracle Fusion Middleware Patching Guide
Oracle® Fusion Middleware
Patching Guide
11g Release 1 (11.1.1.9.0)
E16793-32
July 2016
Explains how to patch your existing Oracle Fusion
Middleware environment or upgrade your existing Oracle
Application Server environment.
Oracle Fusion Middleware Patching Guide, 11g Release 1 (11.1.1.9.0)
E16793-32
Copyright © 2014, 2016, Oracle and/or its affiliates. All rights reserved.
Primary Author:
Lisa Jamen
Contributing Author:
Savita Thakur
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to
the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content,
products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and
expressly disclaim all warranties of any kind with respect to third-party content, products, and services
unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its
affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of
third-party content, products, or services, except as set forth in an applicable agreement between you and
Oracle.
Contents
Preface ................................................................................................................................................................. xi
Intended Audience...................................................................................................................................... xi
Documentation Accessibility ..................................................................................................................... xi
Related Documents ..................................................................................................................................... xi
Conventions ................................................................................................................................................ xii
1
Oracle Fusion Middleware Patching and Upgrade Overview
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.3
2
Installation, Patching, and Upgrade Terminology.................................................................
Patching.................................................................................................................................
Migration...............................................................................................................................
Upgrade.................................................................................................................................
Installation ............................................................................................................................
Patching and Upgrade Tools.....................................................................................................
About Database Patches for Oracle Fusion Middleware ......................................................
1-1
1-1
1-1
1-2
1-2
1-2
1-3
Patching Oracle Fusion Middleware with Oracle OPatch
2.1
2.1.1
2.1.2
2.2
2.2.1
2.2.2
2.2.3
2.2.4
2.2.5
2.3
2.3.1
2.3.2
2.3.3
2.3.3.1
2.3.3.2
2.3.4
2.4
2.4.1
2.4.1.1
About Patching with Oracle OPatch ........................................................................................ 2-1
Types of Patches That Are Applied Using OPatch ........................................................ 2-1
Types of Patches that Cannot be Applied with OPatch................................................. 2-2
About OPatch .............................................................................................................................. 2-3
Getting OPatch ..................................................................................................................... 2-3
Getting Patches that Can be Applied with OPatch......................................................... 2-3
OPatch Environment Variables ......................................................................................... 2-4
OPatch System Requirements............................................................................................ 2-4
Backup and Recovery Considerations for Patching ....................................................... 2-4
OPatch in a Fusion Middleware Environment....................................................................... 2-5
A Typical Patching Scenario .............................................................................................. 2-5
Patching a Fusion Middleware Product........................................................................... 2-8
Patching in a Distributed Environment............................................................................ 2-8
Patching with a Local Middleware Home ................................................................ 2-9
Patching with a Shared Middleware Home .......................................................... 2-11
Patching Artifacts Deployed Outside the Oracle Home ............................................. 2-12
Running OPatch ....................................................................................................................... 2-12
Applying Patches and Deploying Patched Artifacts to WebLogic Servers ............. 2-13
Using the OPatch Property File ............................................................................... 2-13
iii
2.4.1.2
Using the -auto Option .............................................................................................
2.4.1.3
Using the apply Command ......................................................................................
2.4.1.4
Sample Output for the apply Command ...............................................................
2.4.2
Rolling Back Patches and Deploying Patched Artifacts to WebLogic Servers ........
2.4.3
Deploying Patched Artifacts to WebLogic Servers......................................................
2.4.4
Listing the Source Oracle Homes ...................................................................................
2.4.5
Listing the Domains Created from the Middleware Home or Oracle Home ..........
2.4.6
Listing the Applicable Oracle Homes for a Patch ........................................................
2.4.7
Listing Patches Applied to an Oracle Home or WebLogic Domain..........................
2.4.8
Starting or Stopping a Runtime Instance ......................................................................
2.5
Troubleshooting OPatch in a Fusion Middleware Environment......................................
2.5.1
Notes About Patching the MDS Repository .................................................................
2.5.2
Setting the Machine Name and Listen Address...........................................................
2-13
2-14
2-15
2-16
2-17
2-18
2-20
2-21
2-22
2-24
2-26
2-26
2-26
3 Applying the Latest Oracle Fusion Middleware Patch Set
Oracle Fusion Middleware Patching Process Overview....................................................... 3-2
Oracle Fusion Middleware Patching Process Roadmap ....................................................... 3-2
Before You Begin......................................................................................................................... 3-4
Special Instructions for Patching a Distributed Environment ...................................... 3-5
Special Instructions for Patching Oracle SOA Suite ....................................................... 3-5
Special Instructions for Patching Oracle WebLogic Server 10.3.6 with SOA Suite.... 3-5
Special Instructions for Patching Oracle WebCenter Portal.......................................... 3-5
Special Instructions for Patching Oracle WebCenter Content ...................................... 3-5
Enabling WebCenter Content Components Before Upgrade ................................ 3-6
Disabling Obsolete Components Before Upgrade................................................... 3-7
Special Instructions for Patching Oracle WebCenter Enterprise Capture................... 3-7
Special Instructions for Patching Oracle Portal, Forms, Reports and Discoverer...... 3-8
General Pre-Patching Tasks....................................................................................................... 3-8
Reviewing System Requirements and Certification ....................................................... 3-8
System Requirements and Specifications.................................................................. 3-9
Certification and Supported Platforms ..................................................................... 3-9
Verify that the Java Development Kit (JDK) Version is Supported and Certified
with Oracle Fusion Middleware 11g (11.1.1.9) .................................................. 3-9
3.4.1.4
Updating the setDomainEnv Script File with Upgraded JDK Location............... 3-9
3.4.2
Reviewing the Oracle Fusion Middleware Interoperability and Compatibility Guide ....
.............................................................................................................................................. 3-10
3.4.3
Stopping the Servers and Processes ............................................................................... 3-10
3.4.4
Backing Up Your Middleware Home, Domain Home and Oracle Instances .......... 3-10
3.4.5
Backing Up Your Database and Database Schemas .................................................... 3-11
3.4.6
Backing Up Additional Configuration Information .................................................... 3-11
3.4.7
Upgrading Oracle WebLogic Server and Applying Required WebLogic Server Patches
................................................................................................................................................ 3-12
3.4.8
Renaming the emCCR File for Silent Patching............................................................. 3-13
3.5
Downloading the Installer ...................................................................................................... 3-14
3.5.1
About the Installers Used for Patching ......................................................................... 3-14
3.5.2
Downloading the Required Installer ............................................................................. 3-15
3.6
Patching Oracle Fusion Middleware .................................................................................... 3-15
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.5.1
3.3.5.2
3.3.6
3.3.7
3.4
3.4.1
3.4.1.1
3.4.1.2
3.4.1.3
iv
3.6.1
3.6.2
3.6.3
3.7
3.8
3.9
3.9.1
3.9.2
3.9.3
3.9.4
Starting the Installer .........................................................................................................
Applying the Patch Set.....................................................................................................
Performing the Required Post Patching Procedures ...................................................
Upgrading Your Schemas with Patch Set Assistant ...........................................................
Starting the Servers and Processes ........................................................................................
Verifying Your Patch Set Installation....................................................................................
Verifying the Upgrade Log .............................................................................................
Verifying the Domain Server Logs.................................................................................
Verifying OPMN Status ...................................................................................................
Checking Browser URLs..................................................................................................
3-15
3-16
3-17
3-17
3-17
3-18
3-18
3-18
3-18
3-19
4 Upgrading Your Schemas with Patch Set Assistant
4.1
4.2
4.3
4.4
4.4.1
4.4.2
4.4.3
4.4.4
4.4.5
4.4.6
4.4.7
4.4.8
4.5
4.5.1
4.5.2
4.5.3
4.5.4
4.6
Creating a Non-SYSDBA User to Upgrade Schemas............................................................. 4-2
Which Schemas Need to be Upgraded with Patch Set Assistant?....................................... 4-3
Special Instructions for Standalone Oracle Portal Repository Schemas ............................. 4-6
Before You Begin Using the Patch Set Assistant .................................................................... 4-7
Verify that the Java Development Kit (JDK) Version is Supported and Certified with
Oracle Fusion Middleware 11g (11.1.1.9) ................................................................. 4-7
Upgrade Oracle WebLogic Server and Apply Mandatory Patches ............................. 4-8
Back Up Your Database and Database Schemas ............................................................. 4-8
Check Your Database and Schemas .................................................................................. 4-8
Create an Edition on the Database Server for Editions-Based Redefinition ............... 4-9
Shut Down All Components Using the Schemas You Want to Upgrade.................... 4-9
Check the aq_tm_processes Value for Oracle Portal ...................................................... 4-9
Setting ORACLE_HOME and JAVA_HOME Environment Variables..................... 4-10
Running the Patch Set Assistant ............................................................................................ 4-10
Using the Patch Set Assistant Graphical Interface....................................................... 4-10
Using the Patch Set Installer from the Command Line............................................... 4-11
Verifying the Schema Version Number After Upgrade.............................................. 4-12
Checking for Invalid Database Objects ......................................................................... 4-12
Patch Set Assistant Log Files .................................................................................................. 4-13
5 Post-Patching Procedures
5.1
5.1.1
5.1.1.1
5.1.1.2
5.1.1.3
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.8.1
General Post-Patching Tasks ..................................................................................................... 5-1
Starting the Servers.............................................................................................................. 5-1
Starting the Node Manager......................................................................................... 5-2
Starting the WebLogic Administration Server ......................................................... 5-2
Starting the Managed Server(s) .................................................................................. 5-2
Post-Patching Tasks If Your Starting Point is Release 11.1.1.2............................................. 5-3
Post-Patching Tasks If Your Starting Point is Release 11.1.1.3............................................. 5-5
Post-Patching Tasks If Your Starting Point is Release 11.1.1.4............................................. 5-7
Post-Patching Tasks If Your Starting Point is Release 11.1.1.5............................................. 5-8
Post-Patching Tasks If Your Starting Point is Release 11.1.1.6............................................. 5-9
Post-Patching Tasks If Your Starting Point is Release 11.1.1.7.......................................... 5-11
Post-Patching Tasks If Your Starting Point is Release 11.1.1.8.......................................... 5-11
Patching the ADF UI Domain for WebCenter Content............................................... 5-12
v
Post-Patching Tasks for System Components ..................................................................... 5-12
Upgrading System Components .................................................................................... 5-13
Upgrading Oracle Configuration Manager .................................................................. 5-14
Resolving JDBC Errors in Oracle Reports and Oracle Portal ..................................... 5-15
Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for
Oracle Internet Directory ....................................................................................... 5-16
5.9.5
Generating the BASE64 Encoded Encryption Key for OPSS...................................... 5-16
5.9.6
Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode .... 5-17
5.9.7
Configuring Diagnostic Framework Dump Sampling................................................ 5-17
5.9.8
Adding Batik Library Jar Files to the JRF Template for IBM WebSphere ................ 5-17
5.10
Post-Patching Tasks for Oracle Identity Management Components ............................... 5-17
5.10.1
Enabling New Features of Oracle Directory Integration Platform (DIP) with OUD and
ODSEE .................................................................................................................. 5-17
5.10.2
Upgrading Configuration Properties in Oracle Identity Federation ........................ 5-19
5.10.3
Using Oracle Enterprise Manager to View Oracle Identity Management Metrics and
Configuration Settings ........................................................................................... 5-20
5.11
Post-Patching Tasks for Your WebLogic Server Domain .................................................. 5-21
5.11.1
Upgrading Fusion Middleware Shared Libraries ........................................................ 5-21
5.11.2
Upgrading Configurations and Stores........................................................................... 5-22
5.11.3
Upgrading Oracle WSM Configurations....................................................................... 5-22
5.11.4
Enabling WS-AtomicTransaction ................................................................................... 5-23
5.11.5
Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms ........ 5-24
5.11.6
Upgrading the Plug-In Configuration When Using a Proxy with WebLogic Server ........
................................................................................................................................................ 5-25
5.12
Post-Patching Tasks for Oracle SOA Suite ........................................................................... 5-25
5.12.1
Loading the Oracle SOA Suite Purge Scripts for Database Management................ 5-26
5.12.2
Removing the tmp Folder for SOA Composer, BPM Workspace and B2B.............. 5-26
5.12.3
Upgrading the "BPEL Message Recovery Required" Warning Message Duration 5-27
5.12.4
Upgrading MAXRECOVERATTEMPT Attribute to 2 ................................................ 5-27
5.12.5
Upgrading the soa-infra Application in Warning State.............................................. 5-28
5.12.6
Running bpm-ps6-upgrade.py to Upgrade the Policy Store...................................... 5-28
5.12.7
Running soa-upgrade.py to Upgrade the Policy Store and Deploy a Shared Library ......
................................................................................................................................................ 5-29
5.12.8
Upgrading the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled .........
............................................................................................................................................... 5-30
5.12.9
Saving and Restoring XEngine Customizations for Oracle B2B ................................ 5-31
5.12.10
Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS............................ 5-32
5.12.11
Extending the SOA Domain with UMS Adapter Features ......................................... 5-32
5.12.12
Extending the SOA Domain with Business Process Management Features............ 5-33
5.13
Post-Patching Tasks for Oracle WebCenter Content .......................................................... 5-33
5.13.1
Upgrading Oracle WebCenter Content: Imaging ........................................................ 5-34
5.13.2
Upgrading Oracle Application Adapters for Oracle WebCenter Content............... 5-35
5.13.3
Configuring the Report Library for Records Management in Content Server ........ 5-36
5.13.4
Using Fusion Middleware Control to Monitor IBR ..................................................... 5-36
5.13.5
Starting Oracle WebCenter Content Server with SOA or BAM................................. 5-36
5.13.6
Enabling System Components for WebCenter Content.............................................. 5-36
5.14
Post-Patching Tasks for Oracle Service Bus ......................................................................... 5-37
5.14.1
Upgrading an Oracle Service Bus Domain After Applying the Latest Patch Set.... 5-37
5.9
5.9.1
5.9.2
5.9.3
5.9.4
vi
5.14.2
Using Oracle Service Bus With WebLogic Server 10.3.5 ............................................
5.14.3
Using Oracle Service Bus With WebLogic Server 10.3.6.............................................
5.14.4
Performing Additional Post-Upgrade Tasks for Oracle Service Bus IDE ................
5.14.4.1
Deleting Oracle WebLogic Server 11g Release 1 (10.3.3) .....................................
5.14.4.2
Creating Servers.........................................................................................................
5.15
Post-Patching Tasks for Oracle Business Intelligence ........................................................
5.15.1
Enabling the WebLogic JMS Queue for WebCenter Content Delivery Channel ....
5.15.2
Upgrading Oracle Business Intelligence Code Grants ................................................
5.15.3
Upgrading Oracle BI Presentation Catalogs.................................................................
5.15.4
Enabling bicontentserver Features ................................................................................
5.15.5
Enabling Oracle Business Intelligence Composer Features........................................
5.15.6
Enabling JBIPS Features for the Smartview Client ......................................................
5.15.7
Re-encrypting the Essbase Studio Password ................................................................
5.15.8
Upgrading Oracle Real-Time Decisions ........................................................................
5.15.8.1
Upgrading the rtd_ils Resource Type Using WLST .............................................
5.15.8.2
Adding Permissions to the BIAdministrator Principle Using EM .....................
5.15.8.3
Removing JMS............................................................................................................
5.15.9
Configuring the Business Intelligence Mobile App Designer Apps Library ..........
5.16
Post-Patching Tasks for Oracle Data Integrator ..................................................................
5.16.1
Finalizing Repository Patching.......................................................................................
5.16.2
Reconfiguring the Java EE Agent ...................................................................................
5.16.3
Reconfiguring the ODI Standalone Agent ....................................................................
5.16.4
Reconfiguring Oracle Enterprise Manager Properties ................................................
5.16.5
Reconfiguring the ODI Console......................................................................................
5.16.6
Adding the Version Number for the odi-sdk-ws Application in config.xml...........
5-37
5-37
5-38
5-38
5-38
5-39
5-40
5-40
5-40
5-41
5-42
5-43
5-43
5-44
5-44
5-45
5-46
5-46
5-46
5-47
5-47
5-48
5-49
5-49
5-49
6 Patching Oracle WebCenter Portal
6.1
6.2
6.3
6.4
6.5
6.6
6.6.1
6.6.2
6.6.3
6.7
6.8
6.8.1
6.8.2
6.8.2.1
6.8.2.2
6.8.2.3
6.8.2.4
6.8.2.5
6.8.2.6
New Product Names for Oracle WebCenter and Oracle Enterprise Content Management
Suite ................................................................................................................................ 6-2
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation ............................................... 6-3
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation ............................................... 6-8
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation ............................................ 6-13
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation .................................. 6-19
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation .................................. 6-27
Managed Server Changes ................................................................................................ 6-27
Migration Roadmap for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0........................... 6-27
Updating Oracle WebCenter Portal Using WLST Commands .................................. 6-35
Patching an Oracle WebCenter 11.1.1.1.0 Installation ........................................................ 6-39
Troubleshooting Issues ........................................................................................................... 6-40
Troubleshooting Issues with Patching Oracle WebCenter Portal ............................ 6-40
Troubleshooting Post-Patching Issues .......................................................................... 6-41
Related Items Tab Not in Focus............................................................................... 6-41
Content Getting Clipped and Inner Scrollbars Appearing ................................. 6-41
Pretty URLs Not Working for Page Navigation ................................................... 6-41
Content Queries Not Rendered in Navigation Model ......................................... 6-42
Blog Posts Not Displayed in Portals ....................................................................... 6-42
Comments and Likes Not Displayed in Activity Stream .................................... 6-43
vii
Pre-Patching Tasks for Oracle WebCenter Portal ............................................................... 6-43
Exporting Deployment Descriptor for Portlet Producer Applications Secured with
OWSM ................................................................................................................... 6-43
6.9.2
Saving Your OmniPortlet and Web Clipping Customizations .................................. 6-44
6.9.3
Running purgeMetadata() for WebCenter Spaces....................................................... 6-45
6.9.4
Considerations for Upgrading Oracle WebCenter Content or Oracle ECM............ 6-46
6.9.4.1
Upgrading Oracle ECM ............................................................................................ 6-47
6.10
Post Patching Tasks for Oracle WebCenter Portal .............................................................. 6-47
6.10.1
Importing Web Service Deployment Descriptors for Portlet Producers Secured with
OWSM .................................................................................................................... 6-47
6.10.2
Running the upgradeOpss WLST Command .............................................................. 6-49
6.10.3
Extending the Domain Using the Pagelet Producer Upgrade Template ................. 6-50
6.10.4
Updating SSO and OHS Configuration ........................................................................ 6-51
6.10.4.1
Updating OHS Configuration for Pagelet Producer ............................................ 6-51
6.10.4.2
Updating SSO Configuration for Pagelet Producer ............................................. 6-52
6.10.4.3
Updating SSO Configuration for Portlet Producer Applications....................... 6-55
6.10.4.4
Updating SSO Configuration for Oracle SES ........................................................ 6-55
6.10.4.5
Verifying SSOFilter Grant ........................................................................................ 6-55
6.10.5
Performing Post-Patching Tasks for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Installations ............................................................................................................ 6-56
6.10.5.1
Migrating Oracle Wiki Pages and Blogs ................................................................ 6-57
6.10.5.2
Migrating Content Presenter Custom Templates ................................................. 6-62
6.10.5.3
Updating the Configuration for WebCenter REST APIs ..................................... 6-63
6.10.5.4
Updating Multi-Calendar Layouts ......................................................................... 6-63
6.10.5.5
Restoring Your OmniPortlet and Web Clipping Customizations...................... 6-63
6.10.5.6
Extending a Domain to Install Oracle WSM Policy Manager............................. 6-64
6.10.5.7
Remove openusage Properties in setDomainEnv................................................... 6-65
6.10.5.8
Redeploying your Custom Applications to Upgraded Custom Managed Servers ....
......................................................................................................................................... 6-66
6.10.5.9
Remove the LD_LIBRARY_PATH Entry from the setDomainEnv Script ........ 6-66
6.10.5.10
Migrating WSRP Portlet Preferences...................................................................... 6-67
6.10.6
Performing Post-Patching Tasks for the WebCenter Portal Application ................. 6-67
6.10.6.1
Setting the Web Server Context Root on the Content Server Connection ........ 6-67
6.10.6.2
Configuring WebCenter Portal Workflows ........................................................... 6-67
6.10.6.3
Updating the Timezone Attribute........................................................................... 6-68
6.10.6.4
Updating the Portal Display Mode......................................................................... 6-68
6.10.6.5
Choosing a Default Start (or Landing) Page.......................................................... 6-69
6.10.6.6
Migrating WebCenter Portal Customizations....................................................... 6-69
6.10.6.7
Upgrading Process Spaces ....................................................................................... 6-70
6.10.6.8
Granting Permissions to Manage Assets................................................................ 6-74
6.10.7
Adding Oracle Single Sign-On Authentication Provider to the List of Authentication
Providers ............................................................................................................................ 6-74
6.10.8
Adding New Features to Oracle WebCenter Portal .................................................... 6-75
6.10.8.1
Installing Activity Graph, Analytics, Pagelet Producer, Personalization Server, and
Services Portlets ............................................................................................... 6-75
6.10.8.2
Adding Portal Framework Features to WebCenter Custom Applications ....... 6-76
6.10.9
Running the upgradeWebCenterPermissions WLST Command .............................. 6-77
6.10.10
Resetting Search Customizations ................................................................................... 6-77
6.9
6.9.1
viii
6.10.11
6.10.12
6.10.13
Updating Resource Protection Level in OAM 11.1.2.2.0............................................. 6-78
Restoring Profile Page Customizations ......................................................................... 6-78
Removing the -noverify Flag ........................................................................................ 6-79
A Installer Screens
A.1
A.2
A.3
A.4
A.5
A.6
A.7
A.8
Welcome ......................................................................................................................................
Install Software Updates...........................................................................................................
Prerequisite Checks ...................................................................................................................
Specify Installation Location ....................................................................................................
Application Server .....................................................................................................................
Installation Summary ................................................................................................................
Installation Progress ..................................................................................................................
Installation Complete ................................................................................................................
A-1
A-2
A-3
A-4
A-5
A-6
A-7
A-8
B Patch Set Assistant Screens
B.1
B.2
B.3
B.4
B.5
B.6
B.7
B.8
B.9
B.10
Welcome ......................................................................................................................................
Select Component ......................................................................................................................
Prerequisites ...............................................................................................................................
Content Server Directory (WebCenter Content Only) .........................................................
Schema Database Credentials ..................................................................................................
Records Directory (WebCenter Content Only)......................................................................
Examine .......................................................................................................................................
Upgrade Summary ..................................................................................................................
Upgrade Progress ....................................................................................................................
Upgrade Success ......................................................................................................................
B-1
B-3
B-4
B-5
B-6
B-8
B-9
B-10
B-11
B-12
C Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1
(11.1.1.2.0)
C.1
C.2
C.3
C.3.1
C.3.2
C.3.2.1
C.3.2.2
C.3.2.3
C.3.2.4
C.3.2.5
C.4
C.4.1
C.4.2
C.4.2.1
C.4.2.2
C.4.2.3
C.4.2.4
Overview of Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) Patch Assistant ........ C-1
Migration Process ...................................................................................................................... C-2
Preparing to Migrate ................................................................................................................. C-3
Evaluating and Reviewing your Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0)
Environment ........................................................................................................................ C-3
Preparing to Migrate Your Configuration ...................................................................... C-3
Prerequisites ................................................................................................................. C-3
Extracting the Contents of Patch Assistant.............................................................. C-7
Setting Up the Patch Assistant Environment .......................................................... C-7
Stopping Oracle Fusion Middleware........................................................................ C-7
Setting Logging Properties......................................................................................... C-8
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) .................................... C-8
Migration Roadmap ........................................................................................................... C-9
Migration Procedure ........................................................................................................ C-11
Stopping the Old Domain ........................................................................................ C-12
Installing Oracle Software for 11.1.1.2.0 ................................................................. C-12
Downloading Patch Assistant ................................................................................. C-13
Migrating the Schema ............................................................................................... C-13
ix
C.4.2.5
C.4.2.6
C.4.2.7
C.4.2.8
C.4.2.9
C.4.2.10
C.4.2.11
C.4.3
C.4.3.1
C.4.3.2
C.4.3.3
C.4.3.4
C.4.3.5
C.4.3.6
C.4.3.7
C.4.3.8
C.4.3.9
C.4.3.10
C.4.4
C.4.5
C.4.6
C.4.6.1
C.4.7
Creating a WebLogic Domain for 11.1.1.2.0 .......................................................... C-15
Migrating the Domain .............................................................................................. C-16
Migrating an Instance ............................................................................................... C-17
Registering the Instance............................................................................................ C-18
Starting or Stopping the 11.1.1.2.0 Domain ........................................................... C-18
Completing Post-Migration Tasks .......................................................................... C-19
Decommissioning the 11.1.1.1.0 Installation.......................................................... C-19
Post-Migration Configuration for Oracle Fusion Middleware Components .......... C-19
Post-Migration Configuration for Oracle Fusion Middleware Audit Framework .....
.........................................................................................................................................C-20
Post-Migration Configuration for Oracle Business Intelligence Discoverer..... C-22
Post-Migration Configuration for Oracle Directory Integration Platform........ C-22
Post-Migration Configuration for Oracle Identity Federation............................ C-23
Post-Migration Configuration for Oracle Platform Security Services ............... C-24
Post-Migration Configuration for Oracle Reports ................................................ C-29
Post-Migration Configuration for Oracle SOA ..................................................... C-29
Post-Migration Configuration for Oracle User Messaging Service.................... C-31
Post-Migration Configuration for Oracle WebCenter.......................................... C-31
Post Migration Configuration for Oracle Web Services Manager...................... C-38
Installation Process ........................................................................................................... C-39
Configuration Process ...................................................................................................... C-40
Properties in the patchMaster.properties File .............................................................. C-41
Overriding Properties Set in the patchMaster.properties File ............................ C-48
Oracle Fusion Middleware Components Supported by Patch Assistant ................. C-48
D Sample Patch Master Properties File
x
Preface
The Oracle Fusion Middleware Patching Guide describes the tools and procedures
required for you to patch your existing Oracle Fusion Middleware environment or
upgrade your existing Oracle Application Server environment.
Intended Audience
This guide is intended for existing Oracle Fusion Middleware users who are
upgrading their Oracle Fusion Middleware products to a more recent version or to the
latest version. To follow the instructions provided in this document, the reader should
be comfortable running system administration operations, such as creating users and
groups, adding users to groups, and installing operating system patches on the
computer where the products are going to be installed. Users on UNIX systems who
are upgrading their Oracle Fusion Middleware software may need root access to run
some scripts.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle
Accessibility Program website at
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers that have purchased support have access to electronic support
through My Oracle Support. For information, visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit
http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing
impaired.
Related Documents
For additional information, see the following manuals:
■
■
■
Oracle Fusion Middleware Concepts. This book introduces the common terms and
concepts in an Oracle Fusion Middleware environment.
Oracle Fusion Middleware Administrator's Guide. This book contains information for
managing your Oracle Fusion Middleware environment after installation and
configuration is complete.
Oracle Fusion Middleware High Availability Guide. This book contains information
for installing Oracle Fusion Middleware in high availability environments.
xi
Conventions
The following text conventions are used in this document:
xii
Convention
Meaning
boldface
Boldface type indicates graphical user interface elements associated
with an action, or terms defined in text or the glossary.
italic
Italic type indicates book titles, emphasis, or placeholder variables for
which you supply particular values.
monospace
Monospace type indicates commands within a paragraph, URLs, code
in examples, text that appears on the screen, or text that you enter.
1
1
Oracle Fusion Middleware Patching and
Upgrade Overview
This book describes the tools available for you to patch your existing Oracle Fusion
Middleware or upgrade your existing Oracle Application Server environment.
[1]
This chapter includes the following topics:
■
Installation, Patching, and Upgrade Terminology
■
Patching and Upgrade Tools
■
About Database Patches for Oracle Fusion Middleware
If you are upgrading Oracle Identity and Access Management
components, such as Oracle Access Manager, Oracle Adaptive Access
Manager or Oracle Identity Manager, see "Oracle Fusion Middleware
Upgrade Guide for Oracle Identity and Access Management".
Note:
1.1 Installation, Patching, and Upgrade Terminology
This section describes various terms that you should be familiar with before you
continue.
1.1.1 Patching
Patching involves copying a small collection of files over an existing installation. A
patch is normally associated with a particular version of an Oracle product and
involves upgrading from one minor version of the product to a newer minor version
of the same product (for example, from version 11.1.1.2.0 to version 11.1.1.3.0). In some
cases a patch may be used to upgrade schemas.
A patch set is a single patch that contains a collection of patches designed to be
applied together.
1.1.2 Migration
Migration typically involves moving from a third-party (non-Oracle) product to an
Oracle product.
It can also be used to refer to moving an existing set of software parameters (for
example, an existing configuration or existing domain) from one release to another.
For example, instructions for migrating your configuration from Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0) to 11g Release 1 (11.1.1.2.0) are provided in
Appendix C, "Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to
Oracle Fusion Middleware Patching and Upgrade Overview
1-1
Patching and Upgrade Tools
Release 1 (11.1.1.2.0)".
1.1.3 Upgrade
Upgrade involves moving from a previous major version to a new major version. For
example, an upgrade would be required to move from Oracle Application Server 10g
to Oracle Fusion Middleware 11g.
1.1.4 Installation
Installation is when new software is copied onto your system for use. After the new
software is installed, you can patch it or upgrade it as necessary.
1.2 Patching and Upgrade Tools
Table 1–1 provides a brief summary of the patching and upgrade tools, and provides
pointers to more detailed information.
Table 1–1
Summary of Patching, Migration, and Upgrade Tools
Tool
Description
More Information
OPatch
OPatch is typically used to patch the software on your
system by copying a small collection of files over your
existing installation.
Chapter 2, "Patching Oracle
Fusion Middleware with Oracle
OPatch"
In Oracle Fusion Middleware, OPatch is used to patch
an existing Oracle Fusion Middleware 11g installation.
WebLogic Server
Upgrade Installer
WebLogic Server Upgrade Installer is used to upgrade Upgrading Oracle WebLogic Server
your existing Oracle WebLogic Server installation to the
latest available version.
Oracle Fusion Middleware products require the
presence of Oracle WebLogic Server and its directory
structure on your system. When you upgrade your
Oracle Fusion Middleware software, you must also
upgrade the version of Oracle WebLogic Server on your
system using the WebLogic Server Upgrade Installer.
The WebLogic Server Upgrade Installer is only
available from My Oracle Support.
1-2 Oracle Fusion Middleware Patching Guide
About Database Patches for Oracle Fusion Middleware
Table 1–1 (Cont.) Summary of Patching, Migration, and Upgrade Tools
Tool
Description
More Information
Product Installer and The Patch Set Installer is used to upgrade your existing
Patch Set Installer
Fusion Middleware product to the latest version. At the
time of publication, the latest version is 11g Release 1
(11.1.1.9.0) and in this release, only Oracle Portal,
Forms, Reports and Discoverer require upgrading with
the Patch Set Installer. All other Oracle Fusion
Middleware products in this release can be upgraded
with their usual product installer.
NOTE: If you are upgrading from 11g Release 1
(11.1.1.1.0) you must first follow the steps in
Appendix C, "Using Patch Assistant to Migrate from
11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)".
Patch Set Assistant
See Chapter 3, "Applying the
Latest Oracle Fusion Middleware
Patch Set" for instructions on how
to use the Patch Set Installer for
Oracle Portal, Forms, Reports and
Discoverer.
See Section 3.5.1, "About the
Installers Used for Patching" for
more information about the types
of installers available for patching.
Patch Set Assistant is used to upgrade your database
Chapter 4, "Upgrading Your
schemas to prepare them for use with the latest version Schemas with Patch Set Assistant"
of Oracle Fusion Middleware software.
This tool is used with Patch Set upgrades only and
cannot be used for upgrades.
If you need to add or drop schemas, you should use the
Repository Creation Utility (RCU).
Upgrade Assistant
The Upgrade Assistant is used to upgrade schemas and Oracle Fusion Middleware Upgrade
configuration information from Oracle Application
Planning Guide
Server 10g to Oracle Fusion Middleware 11g.
1.3 About Database Patches for Oracle Fusion Middleware
This guide provides instructions for applying Oracle Fusion Middleware patches to
your existing Oracle Fusion Middleware installations.
However, there are specific cases where you might be instructed to apply an Oracle
Database patch to an existing Oracle Fusion Middleware Oracle home. This is because
some Oracle Fusion Middleware products include specialized components, such as
application programming interfaces (APIs), software libraries, and other software code
developed for Oracle Database products.
In these specific cases, you might be referred to Oracle Database patching and
installation documentation for more information.
Note that in most cases Oracle Fusion Middleware patches include all necessary
software upgrades. You should apply Database patches only when specifically
instructed or if you are experiencing a specific issue that can be resolved by the
database patch.
Oracle Fusion Middleware Patching and Upgrade Overview
1-3
About Database Patches for Oracle Fusion Middleware
1-4 Oracle Fusion Middleware Patching Guide
2
2
Patching Oracle Fusion Middleware with
Oracle OPatch
This chapter describes patching in an Oracle Fusion Middleware environment.
[2]
This chapter includes the following topics:
■
About Patching with Oracle OPatch
■
About OPatch
■
OPatch in a Fusion Middleware Environment
■
Running OPatch
■
Troubleshooting OPatch in a Fusion Middleware Environment
2.1 About Patching with Oracle OPatch
Patches are a small collection of files copied over to an existing installation. They are
associated with particular versions of Oracle products.
Oracle recommends that all customers upgrade to the latest
version of OPatch. Review the following My Oracle Support note and
follow the instructions to upgrade to the latest version if needed:
Note:
Note 224346.1 - Opatch - Where Can I Find the Latest Version of
Opatch?
2.1.1 Types of Patches That Are Applied Using OPatch
Oracle has implemented a new patch nomenclature for Oracle
products. The new patch names and the previous names are listed
below for reference.
Note:
OPatch can be used for the following types of patches:
Patching Oracle Fusion Middleware with Oracle OPatch 2-1
About Patching with Oracle OPatch
Table 2–1
Patches that can be used with OPatch
New Name
Old Name(s)
Description
Interim Patch
PSE
A patch containing one or more
fixes made available to customers
who cannot wait until the next
patch set or new product release to
get a fix.
MLR
Exception release
One-Off
x-fix
Hotfix
Security One-Off
Bundle Patch
Maintenance Pack
Service Pack
MLRs
Cumulative Patch
Update Release
Bundle Patch
Security Patch Update (SPU)
Critical Patch Updates
CPUs
An iterative, cumulative patch that
is issued between patch sets.
Bundle patches usually include
only fixes, but some products may
include minor enhancements.
Examples are the Database
Windows Bundles and SOA Bundle
Patches.
An iterative, cumulative patch
consisting of security fixes.
Formerly known as Critical Patch
Update.
Note: The program name which
delivers SPUs will still be called
Critical Patch Update, as defined
below:
Critical Patch Update: Oracle's
program for quarterly release of
security fixes. Patches released as
part of this program may be Patch
Set Updates, Security Patch
Updates, and Bundle Patches.
Regardless of the patch type, the
patches are cumulative.
Patch Set Updates (PSUs)
Patch Set Updates are used to patch
Oracle WebLogic Server only.
Patch Set Updates are released on a
quarterly basis, following the same
schedule as the Critical Patch
Updates (CPUs). These come out
the closest Tuesday to the 15th of
the months of January, April, July
and October. Patch Set Update
content is intended to address the
top fifty critical bugs affecting the
broad customer base.
2.1.2 Types of Patches that Cannot be Applied with OPatch
The only type of patch that is not applied with OPatch is a patch set. A patch set
contains a large number of merged patches, is thoroughly tested, changes the version
2-2 Oracle Fusion Middleware Patching Guide
About OPatch
of the product it is applied to, and can sometimes introduce new functionality. Patch
sets are cumulative bug fixes that fix all bugs and consume most patches since the last
base release.
Patch sets and the Patch Set Assistant are usually applied through OUI-based product
specific installers. For more information, see Chapter 3, "Applying the Latest Oracle
Fusion Middleware Patch Set".
2.2 About OPatch
OPatch is a Java-based utility that runs on all supported operating systems and
requires installation of the Oracle Universal Installer. This document contains
information pertaining to OPatch commands that are most commonly used in an
Oracle Fusion Middleware environment. You can use all supported OPatch commands
if you choose; for a full list of OPatch commands and for more information about the
OPatch utility, refer to the Oracle Universal Installer and OPatch User's Guide at the
following URL:
http://docs.oracle.com/cd/B28359_01/em.111/b31207/toc.htm
This section contains the following:
■
Section 2.2.1, "Getting OPatch"
■
Section 2.2.2, "Getting Patches that Can be Applied with OPatch"
■
Section 2.2.3, "OPatch Environment Variables"
■
Section 2.2.4, "OPatch System Requirements"
■
Section 2.2.5, "Backup and Recovery Considerations for Patching"
2.2.1 Getting OPatch
OPatch can be found in your Fusion Middleware product's ORACLE_HOME/OPatch
(on UNIX operating systems) or ORACLE_HOME\OPatch (on Windows operating
systems) directory.
Oracle recommends that you always check for and obtain the latest version of OPatch
from My Oracle Support (formerly Oracle MetaLink).
1.
Access and log into My Oracle Support at the following location:
http://support.oracle.com/
2.
In the Search Knowledge Base field, enter 224346.1. This is the ID of the document
that describes how to obtain the latest version of OPatch.
3.
In the search results, click on the link corresponding to document ID 224346.1.
4.
In the document, click on the Patch 6880880 link which will take you to the screen
where you can obtain the latest version of OPatch based on release versions and
platforms.
Make sure you verify that the OPatch release number in the "Release" column is
"11.1.0.0.0" as this is the correct version of OPatch for Oracle Fusion Middleware
11g products.
2.2.2 Getting Patches that Can be Applied with OPatch
You can obtain the latest patches by specifying the patch ID in My Oracle Support
(formerly MetaLink):
Patching Oracle Fusion Middleware with Oracle OPatch 2-3
About OPatch
1.
Access and log into My Oracle Support at the following location:
http://support.oracle.com/
2.
Click the Patches & Updates link.
3.
Enter the Patch ID or Number, then click Search. A Patch Search Results table
appears.
4.
Using the Release and Platform columns, find the desired patch, then click the
associated Patch ID.
5.
In the page that now appears, click the Download button in the right-hand
column.
2.2.3 OPatch Environment Variables
OPatch uses the environment variables listed in Table 2–2:
Table 2–2
OPatch Environment Variables
Variable
Description
ORACLE_HOME
Points to the location of the Oracle home directory.
MW_HOME
Points to the location of the Middleware home directory.
PATH
Points to the location(s) from which various commands should be run.
2.2.4 OPatch System Requirements
The OPatch utility has the following requirements:
■
■
■
The ORACLE_HOME environment variable must point to a valid Oracle home
directory and match the value used during installation of the Oracle home
directory.
If the -invPtrLoc command-line argument was used during installation, then it
must be used when using the OPatch utility. Oracle recommends the use of the
default central inventory for a platform.
The java, ar, cp, and make commands must be available in one of the directories
listed in the PATH environment variable. The commands are not available for all
platforms.
2.2.5 Backup and Recovery Considerations for Patching
It is highly recommended that you back up the ORACLE_HOME before any patch
operation. You can back up the ORACLE_HOME using your preferred method. You can
use any method such as zip, cp -r, tar, and cpio to compress the ORACLE_HOME.
If the ORACLE_HOME does not appear when you execute the opatch lsinventory
-detail command, the ORACLE_HOME might be missing from the Central Inventory, or
the Central Inventory itself could be missing or corrupted.
If the ORACLE_HOME is listed when you execute the opatch lsinventory -detail
command, but the products and components within the ORACLE_HOME are not listed,
the inventory within the ORACLE_HOME (local inventory) might be missing or corrupted.
If the local inventory is corrupted or lost for some reason, you can simply restore the
ORACLE_HOME/inventory (on UNIX operating systems) or ORACLE_HOME\inventory (on
Windows operating systems) if it was backed up. If a backup does not exist, you may
have to reinstall the software.
2-4 Oracle Fusion Middleware Patching Guide
OPatch in a Fusion Middleware Environment
2.3 OPatch in a Fusion Middleware Environment
This section describes the Oracle OPatch utility as it pertains to an Oracle Fusion
Middleware environment. You should be familiar with the Oracle Fusion Middleware
concepts introduced in the Oracle Fusion Middleware Installation Planning Guide, which
is available at the following URL:
http://download.oracle.com/docs/cd/E15523_01/install.1111/b32474/toc.htm
This section contains the following:
■
Section 2.3.1, "A Typical Patching Scenario"
■
Section 2.3.2, "Patching a Fusion Middleware Product"
■
Section 2.3.3, "Patching in a Distributed Environment"
■
Section 2.3.4, "Patching Artifacts Deployed Outside the Oracle Home"
2.3.1 A Typical Patching Scenario
Consider a common, non-distributed Fusion Middleware topology for Oracle SOA
Suite and Oracle WebCenter, as show in Figure 2–1:
OPatch can be used to patch any Fusion Middleware product,
even though only a few are shown in this example. OPatch can not be
used to patch Oracle WebLogic Server.
Note:
Patching Oracle Fusion Middleware with Oracle OPatch 2-5
OPatch in a Fusion Middleware Environment
Figure 2–1 Common Fusion Middleware Topology for Oracle SOA Suite and Oracle
WebCenter
Suppose you have a problem in the SOA Domain. Below is a typical patching process:
Step 1. Contact Oracle Support
You can contact your Oracle support representative, or you can go to My Oracle
Support (formerly OracleMetaLink):
http://support.oracle.com/
Step 2. Check for Existing Patches
If Oracle Support is not able to resolve the issue, they may ask to see if you have any
patches already installed on your system. To determine this information, you should
run the opatch lsinventory command.
To check if a particular patch is installed in the Oracle home (or the set of Oracle
homes within a Middleware home) you use the opatch checkInstalledOneOffs
command. See Section 2.4.7, "Listing Patches Applied to an Oracle Home or WebLogic
Domain" for more information about this command.
2-6 Oracle Fusion Middleware Patching Guide
OPatch in a Fusion Middleware Environment
Step 3. Obtain OPatch and the Necessary Patch
Upon determining that you are in need of a new patch and it has not already been
installed on your system, you should do the following:
1.
Make certain that you have the latest version of OPatch, as described in
Section 2.2.1, "Getting OPatch".
2.
Obtain the patch as described in Section 2.2.2, "Getting Patches that Can be
Applied with OPatch".
Step 4. Determine the Oracle Home
Once you obtain the patch, determine the Oracle home directory to which you are
going to apply the patch.
The most common type of patch available in a Fusion Middleware environment
involves patching a specific Oracle home directory. Some patches (for example, a patch
pertaining to JRF) may apply to multiple Oracle home directories within a specific
Middleware home. A third type of patch could involve client components in one
Oracle home and server components in a different Oracle home (for example, Oracle
WebCenter in the WebCenter Oracle home depends on BPEL Process Manager in the
Oracle SOA Suite Oracle home).
If you do not know the name of your Oracle home, you should run the opatch
lshomes command as described in Section 2.4.6, "Listing the Applicable Oracle Homes
for a Patch" to obtain a list of Oracle homes that pertain to the domain. In this example,
the Oracle home to which the patch should be applied is the SOA Oracle home.
After you determine your Oracle home, you should run the opatch checkApplicable
command as described in Section 2.4.6, "Listing the Applicable Oracle Homes for a
Patch" to make sure that the patch can actually be applied to the Oracle home.
As the Middleware home is the top-level entity in a Fusion Middleware topology, the
location of your Middleware home will be required for many of the OPatch commands
in a Fusion Middleware environment.
Step 5. Read the README File
Read the README file that accompanies the patch. This file contains important
information and instructions that must be followed prior to applying your patch.
For example, the README file may instruct you to apply the patch using the -auto
option (described in Section 2.4.1.2, "Using the -auto Option"). The more common
scenario is that the README will instruct you to use a series of OPatch commands,
including opatch stop and opatch start (see Section 2.4.8, "Starting or Stopping a
Runtime Instance").
Step 6. Apply the Patch
After you determine the Oracle home to which you need to apply the patch, you
should apply the patch with the opatch apply command as described in Section 2.4.1,
"Applying Patches and Deploying Patched Artifacts to WebLogic Servers".
After Applying the Patch...
In most cases, after you apply the patch the instructions in the README file will tell
you to run the opatch start command to re-start your servers.
After the patching is complete and your servers are restarted, you should check your
product software to verify that the issue has been resolved.
Patching Oracle Fusion Middleware with Oracle OPatch 2-7
OPatch in a Fusion Middleware Environment
If for some reason the result is not satisfactory, you can use the opatch rollback
command to remove the patch from the Oracle home. See Section 2.4.2, "Rolling Back
Patches and Deploying Patched Artifacts to WebLogic Servers" for more information,
and consult the README file for specific instructions.
2.3.2 Patching a Fusion Middleware Product
Many Fusion Middleware artifacts are deployed to a runtime environment, where
applications pick up these binaries for execution. A common example of this are J2EE
artifacts (for example, .ear, .war, or .rar files) or J2EE shared libraries deployed to a
Managed Server or cluster running within a domain. Patching in a Fusion Middleware
environment involves upgrading and replacing these artifacts in the Oracle home. The
servers to which the artifacts are deployed need to be restarted for the changes to take
effect.
After the artifacts are deployed, there are various staging modes that affect how
WebLogic Server treats these artifacts, which in turn determine how the applications
are patched. All artifacts in Oracle Fusion Middleware 11g are deployed in NoStage
Mode, which means that each Managed Server must access the archive files from a
single source directory for deployment. If a J2EE application is deployed to three
Managed Servers within a cluster, each Managed Server must be able to access the
same application archive files from a shared or network-mounted directory in order to
deploy the new J2EE application.
Take note of the following:
■
■
■
If multiple Managed Servers on multiple machines are used, the path to the
application bits must be the same on all machines because there is a single point of
entry for the application in the domain configuration.
Since the source location for the application bits is fixed and points back to its own
ORACLE_HOME location, all domains that were created using a given ORACLE_
HOME will pick up the patched bits once the ORACLE_HOME is patched.
If you are using multiple Managed Servers on multiple machines and the product
ORACLE_HOME is not shared or network-mounted on the target Managed Servers,
then each machine must have the product installed on an ORACLE_HOME on the local
file system from which the Managed Servers can access the application binaries.
Therefore, the ORACLE_HOME on each local file system of each machine must be
patched separately.
The steps that need to be performed for this scenario are as follows:
1.
Stop all Managed Servers in the WebLogic Domain to which the application is
deployed.
2.
Use the opatch apply command to apply the bits to an Oracle home.
3.
Restart all the Managed Servers in the same WebLogic Domain.
Steps 1 and 3 are performed by the Fusion Middleware capabilities in OPatch.
2.3.3 Patching in a Distributed Environment
The process to patch in a distributed environment depends on whether or not your
Middleware home directory is shared or not shared.
2-8 Oracle Fusion Middleware Patching Guide
OPatch in a Fusion Middleware Environment
2.3.3.1 Patching with a Local Middleware Home
Consider the environment shown in Figure 2–2. This is a distributed environment,
where you have identical topologies on separate machines, each with its own local
Middleware home and Fusion Middleware products inside the Middleware home:
Patching Oracle Fusion Middleware with Oracle OPatch 2-9
OPatch in a Fusion Middleware Environment
Figure 2–2 Distributed Fusion Middleware Topology for Oracle SOA Suite and Oracle
WebCenter
If you encountered a problem in the SOA domain, you would have to patch the
corresponding Oracle home on each machine separately, according to the instructions
2-10 Oracle Fusion Middleware Patching Guide
OPatch in a Fusion Middleware Environment
in the README file. After you patch the SOA Oracle home on "Middleware Host 1,"
for example, you must then repeat the same procedure on "Middleware Host 2."
2.3.3.2 Patching with a Shared Middleware Home
Consider the environment shown in Figure 2–3. This is also a distributed environment,
where you have identical topologies on separate machines, but the Middleware home
on "Middleware Host 2" is shared or NFS mounted:
Figure 2–3 Distributed Fusion Middleware Topology for Oracle SOA Suite and Oracle
WebCenter
In this topology, if you encountered a problem in the SOA Domain, you would only
need to patch the SOA Oracle home on either "Middleware Host 1" or "Middleware
Host 2" in accordance with the instructions in the README file, and OPatch would
automatically patch all of the matching Oracle homes that share the same Middleware
home.
Patching Oracle Fusion Middleware with Oracle OPatch 2-11
Running OPatch
2.3.4 Patching Artifacts Deployed Outside the Oracle Home
Some applications, such as Oracle Enterprise Manager Fusion Middleware Control
and Oracle Web Services Manager Policy Manager (WSM-PM), are deployed outside
of the product Oracle home (in the Oracle Common Home or oracle_common)
directory. OPatch can also apply patches to files that reference the oracle_common
directory.
2.4 Running OPatch
The OPatch utility is located in the ORACLE_HOME/OPatch (on UNIX operating
systems) or ORACLE_HOME\OPatch (on Windows operating systems) directory.
Below is the syntax for the OPatch utility:
path_to_opatch/opatch command -options
Acceptable values for command are described in Table 2–3.
Valid options for each command are described in the sections that describe each
command.
Table 2–3
Commands for the OPatch Utility in a Fusion Middleware Environment
Command
Description
apply
Apply the patch to an Oracle home and deploy the patch to a
WebLogic domain.
For details, see Section 2.4.1, "Applying Patches and
Deploying Patched Artifacts to WebLogic Servers".
rollback
Remove the patch from an Oracle home.
For details, see Section 2.4.2, "Rolling Back Patches and
Deploying Patched Artifacts to WebLogic Servers".
deploy
Deploy the patch to a WebLogic domain.
For details, see Section 2.4.3, "Deploying Patched Artifacts to
WebLogic Servers".
checkApplicable
List all Oracle homes to which a patch can be applied.
For details, see Section 2.4.6, "Listing the Applicable Oracle
Homes for a Patch".
lshomes
List the Oracle homes that have been used to create WebLogic
Domains.
For details, see Section 2.4.4, "Listing the Source Oracle
Homes".
lsdomains
List all WebLogic domains created from the Middleware home
or specific Oracle home.
For details, see Section 2.4.5, "Listing the Domains Created
from the Middleware Home or Oracle Home".
checkInstalledOneOffs
Check if certain patches are installed on any Oracle homes.
For details, see Section 2.4.7, "Listing Patches Applied to an
Oracle Home or WebLogic Domain".
start | stop
Start or Stop a WebLogic Administration Server, Managed
Server, or Cluster.
For details, see Section 2.4.8, "Starting or Stopping a Runtime
Instance".
2-12 Oracle Fusion Middleware Patching Guide
Running OPatch
To view additional information for these Fusion Middleware options, use the
following command:
path_to_OPatch/opatch -help -fmw
2.4.1 Applying Patches and Deploying Patched Artifacts to WebLogic Servers
The apply command in a Fusion Middleware environment applies the patch to the
Oracle home on the local machine.
The option to apply a patch to a Middleware home (including
all Oracle homes inside that Middleware home) is not yet available.
Note:
2.4.1.1 Using the OPatch Property File
Sensitive information such as Administration Server credentials, and other important
information such as the Administration Server URL, domain location and applications
directory location, are obtained by prompts from the console. In some cases, default
values may be found and specified by OPatch; in these cases, press Enter to use these
default values.
Automation applications such as Grid Control may invoke OPatch with the -silent
option, which does not prompt for any input from the console. To supply the
necessary Administration Server credentials and other information, a response file can
be created and passed to OPatch as an argument with the -property_file option.
For Fusion Middleware components, userConfigFile and userKeyFile can be
specified in the property file as keys with corresponding file names. The
userConfigFile file contains an encrypted user name and password, while the
userKeyFile contains a secret key that is used to encrypt and decrypt the user name
and password. Similarly, the AdminServerURL (URL of the Administration Server),
DomainHome (full path to the domains directory) and ApplicationsDir (full path to the
applications directory) can also be specified in the properties file.
2.4.1.2 Using the -auto Option
Some patches are certified by Oracle Product Support as capable of being used with
the -auto option, which can automate certain portions of your patching procedure.
The -auto option applies the patch to the Oracle home; verifies that the patch is
actually applied, then performs any necessary redeploy operations against the
specified WebLogic Domain, including stopping and starting all the servers that are
affected by the patch. If your patch is certified for use with the -auto option, you will
be informed of such in the patch's README file.
2.4.1.2.1 Configuring Node Manager Beginning with OPatch release 11.1.0.8.2, the -auto
option requires the Node Manager user name and password. In order for OPatch to be
used properly:
■
■
The Administration Server must be up and running.
If the Managed Servers are up and running, OPatch will stop the servers, apply
the patch, then restart the servers.
If the Managed Servers are not running, OPatch will apply the patch but then you
must manually start the servers in order to see the effects of the patch.
To configure Node Manager, refer to "General Node Manager Configuration" in
Administering Node Manager for Oracle WebLogic Server.
Patching Oracle Fusion Middleware with Oracle OPatch 2-13
Running OPatch
2.4.1.2.2 Using the -auto Option with the -domain Option The -auto option should be used
in conjunction with the -domain option; the only exception is if only one WebLogic
Domain was configured from the Oracle home. In such cases, OPatch will use that
domain as the default domain. If multiple domains have been created and the -domain
option is not used, then it is the user's responsibility to run opatch deploy to redeploy
the patched artifacts to their respective domains, and also stop and start the affected
servers in each of the domains.
2.4.1.3 Using the apply Command
The apply command (with the -auto option specified) performs the following:
1.
Stops all affected target servers.
This might involve stopping server instances on other nodes for:
a.
Staged mode applications.
b.
NoStage mode applications sharing the Oracle home.
2.
Applies the patch to the Oracle home on the local machine.
3.
Performs any required deploy operations for patched artifacts.
4.
Restarts all affected servers.
The syntax for the apply command is shown below:
opatch apply
[-auto [-domain domain_name]]
[-mw_home MW_HOME]
[-oh ORACLE_HOME]
[-property_file path_to_property_file]
[-report]]
A summary of the options for the apply command are described in Table 2–4.
Table 2–4
Options for the OPatch apply Command
Option
Description
-auto [-domain domain_
name]
Optional - causes OPatch to automate the rollout of the patch
to Oracle Fusion Middleware entities. If -auto is used then
-domain must also be used to indicate the name of the domain
in which the rollout should occur; the exception is when there
is only one domain configured out of the Oracle home, in
which case the -domain flag is optional.
See Section 2.4.1.2, "Using the -auto Option" for more
information.
-mw_home MW_HOME
Optional - The Middleware home to which the patch will be
applied. The Middleware home specified here supersedes the
MW_HOME environment variable. If neither is specified, then
the Middleware home from where the command is run will be
used.
-oh ORACLE_HOME
Optional - This option is used to specify the Oracle home to
which the patch should be applied. This value supersedes the
ORACLE_HOME environment variable. If neither is specified,
OPatch will apply the upgrades to the Oracle home from
which it was launched.
-property_file name
Optional - absolute path and name of the property file.
See Section 2.4.1.1, "Using the OPatch Property File" for more
information.
2-14 Oracle Fusion Middleware Patching Guide
Running OPatch
Table 2–4 (Cont.) Options for the OPatch apply Command
Option
Description
-report
Optional - print out the actions that will be taken by executing
the command, but does not actually execute the command.
2.4.1.4 Sample Output for the apply Command
Below is a sample output from the opatch apply command on a UNIX operating
system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch apply
-auto /OracleFMW/Middleware_PS1_RC2/FMWPatches/9991008/
-oh /OracleFMW/Middleware_PS1_RC2/oracle_common/
-domain MySOAWebCenterDist
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/oracle_common
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/oracle_common//oui
Log file location : /OracleFMW/Middleware_PS1_RC2/oracle_
common/cfgtoollogs/opatch/opatch2009-12-06_09-44-02AM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/oracle_
common/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Please enter the WebLogic Admin Server username:> weblogic
Please enter the WebLogic Admin Server password:>
Please enter the WebLogic Admin Server URL(t3://stadn41:7011):>
Please enter the WebLogic domain directory
location(/OracleFMW/MyDomains/domains/MySOAWebCenterDist):>
Please enter the WebLogic applications directory
location(/OracleFMW/MyDomains/applications/MySOAWebCenterDist):>
[FMW] Running apply '-auto' prerequisite checks...
[FMW] ProductDriver::preReq_Product() succeeded
[FMW] ProductDriver::preReq_Deploy() succeeded
All the applications affected by this patch are deployed in 'No Stage' mode.
Redeploy operation will not be performed for the affected applications.
Please refer to the log file for more details.
[FMW] ProductDriver::preReq_LifeCycle() succeeded
[FMW] Apply '-auto' prerequisite checks succeeded...
ApplySession applying interim patch '9991008' to OH '/OracleFMW/Middleware_PS1_
RC2/oracle_common'
Running prerequisite checks...
You selected -local option, hence OPatch will patch the local system only.
Patching Oracle Fusion Middleware with Oracle OPatch 2-15
Running OPatch
Please shutdown Oracle instances running out of this ORACLE_HOME on the local
system.
(Oracle Home = '/OracleFMW/Middleware_PS1_RC2/oracle_common')
Is the local system ready for patching? [y|n]
y
User Responded with: Y
Backing up files and inventory (not for auto-rollback) for the Oracle Home
Backing up files affected by the patch '9991008' for restore. This might take a
while...
Backing up files affected by the patch '9991008' for rollback. This might take a
while...
Patching component oracle.jrf.j2ee, 11.1.1.2.0...
Copying file to "/OracleFMW/Middleware_PS1_RC2/oracle_common/modules/oracle.jrf_
11.1.1/jrf-api.jar"
Patching component oracle.jrf.dms, 11.1.1.2.0...
Copying file to "/OracleFMW/Middleware_PS1_RC2/oracle_common/modules/oracle.dms_
11.1.1/dms.war"
ApplySession adding interim patch '9991008' to inventory
Verifying the update...
Inventory check OK: Patch ID 9991008 is registered in Oracle Home inventory with
proper meta-data.
Files check OK: Files from Patch ID 9991008 are present in Oracle Home.
The local system has been patched and can be restarted.
[FMW] Ignoring Deploy operations as all patched artifacts are deployed in 'No
Stage' mode
[FMW] Performing Auto Post-Deploy Actions
[FMW] Performing Auto Post-Bounce Actions
-------------------------------------------------------------------------------The following warnings have occurred during OPatch execution:
1) OUI-67851:
All the applications affected by this patch are deployed in 'No Stage' mode.
Redeploy operation will not be performed for the affected applications.
Please refer to the log file for more details.
-------------------------------------------------------------------------------OPatch Session completed with warnings.
OPatch completed with warnings.
2.4.2 Rolling Back Patches and Deploying Patched Artifacts to WebLogic Servers
The rollback command allows you to remove an existing one-off patch by specifying
the unique patch ID.
The rollback command (with the -auto option specified) performs the following:
1.
Stops all affected target servers.
This might involve stopping server instances on other nodes for:
a.
Staged mode applications.
b.
NoStage mode applications sharing the Oracle home.
2-16 Oracle Fusion Middleware Patching Guide
Running OPatch
2.
Rolls back the patch on the Oracle home on the local machine.
3.
Performs any required deploy operations for patched artifacts.
4.
Restarts all affected servers.
The syntax for the rollback option is shown below:
opatch rollback -id patch_id
[-auto [-domain domain_name]]
[-mw_home MW_HOME]
[-oh ORACLE_HOME]
[-property_file path_to_property_file
[-report]]
A summary of the options for the rollback command are described in Table 2–5.
Table 2–5
Options for the OPatch rollback Command
Option
Description
-id patch_id
Use the -lsinventory option to display all applied patch IDs.
Each one-off patch is uniquely identified by an ID. To rollback
to a previous patch version, that patch version's ID must be
supplied.
-auto [-domain domain_
name]
Optional - causes OPatch to automate the rollout of the patch
to Oracle Fusion Middleware entities. If -auto is used then
-domain must also be used to indicate the name of the domain
in which the rollout should occur; the exception is when there
is only one domain configured out of the Oracle home, in
which case the -domain flag is optional.
Refer to Section 2.4.1, "Applying Patches and Deploying
Patched Artifacts to WebLogic Servers" for more information.
-mw_home MW_HOME
Optional - The Middleware home to which the patch will be
applied. The Middleware home specified here supersedes the
MW_HOME environment variable. If neither is specified, then
the Middleware home from where the command is run will be
used.
-oh ORACLE_HOME
Optional - This option is used to specify the Oracle home to
which the patch should be applied. This value supersedes the
ORACLE_HOME environment variable. If neither is specified,
OPatch will apply the upgrades to the Oracle home from
which it was launched.
-property_file name
Optional - absolute path and name of the property file.
Refer to Section 2.4.1, "Applying Patches and Deploying
Patched Artifacts to WebLogic Servers" for more information.
-report
Optional - print out the actions that will be taken by executing
the command, but does not actually execute the command.
2.4.3 Deploying Patched Artifacts to WebLogic Servers
This operation deploys modified artifacts from the Fusion Middleware ORACLE_
HOME to the Fusion Middleware domain.
The location of the patch binaries must be specified using the -ph option. If the patch is
installed in the current Oracle home (the Oracle home from which you are running this
command) then the -ph option is not required.
If the patch is already applied to the Oracle home, the -id option can be used to
specify the patch you want to use for deployment.
Patching Oracle Fusion Middleware with Oracle OPatch 2-17
Running OPatch
The syntax for the deploy command is shown below:
opatch deploy -id patch_id -ph patch_location
[-auto [-domain domain_name]]
[-mw_home MW_HOME]
[-oh ORACLE_HOME]
[-property_file path_to_property_file
[-report]]
A summary of the options for the deploy command are described in Table 2–6.
Table 2–6
Options for the OPatch deploy Command
Option
Description
-id patch_id
The unique ID of the patch that is installed in the Oracle home.
-ph patch_location
The absolute path to the location of the patch. If none is
specified, then the current directory is used.
-auto [-domain domain_
name]
Optional - causes OPatch to automate the rollout of the patch
to Oracle Fusion Middleware entities. If -auto is used then
-domain must also be used to indicate the name of the domain
in which the rollout should occur; the exception is when there
is only one domain configured out of the Oracle home, in
which case the -domain flag is optional.
Refer to Section 2.4.1, "Applying Patches and Deploying
Patched Artifacts to WebLogic Servers" for more information.
-mw_home MW_HOME
Optional - The Middleware home to which the patch will be
applied. The Middleware home specified here supersedes the
MW_HOME environment variable. If neither is specified, then
the Middleware home from where the command is run will be
used.
-oh ORACLE_HOME
Optional - This option is used to specify the Oracle home to
which the patch should be applied. This value supersedes the
ORACLE_HOME environment variable. If neither is specified,
OPatch will apply the upgrades to the Oracle home from
which it was launched.
-property_file name
Optional - absolute path and name of the property file.
Refer to Section 2.4.1, "Applying Patches and Deploying
Patched Artifacts to WebLogic Servers" for more information.
-report
Optional - print out the actions that will be taken by executing
the command, but does not actually execute the command.
2.4.4 Listing the Source Oracle Homes
The lshomes command lists all the Oracle homes pertaining to logical entities such as
Host or Domain. For a Host, the list of Oracle homes is obtained from the machine's
central inventory. For a WebLogic domain, the list of homes is limited to product
Oracle homes that are installed within a top-level Middleware home.
If the -domain or -domaindir option is used, the command lists the Oracle homes that
have been used to create or extend the WebLogic domain. If not, all the homes
registered with the machine's central inventory or the inventory location specified
using -invPtrLoc are listed.
The Middleware home can be specified by using the -mw_home option or by setting the
MW_HOME environment variable. When the Middleware home is specified and the
-domain or -domaindir option is not specified, this command will list all the Oracle
2-18 Oracle Fusion Middleware Patching Guide
Running OPatch
homes within the Middleware home that are registered with the machine's central
inventory or the specified inventory location.
The syntax for the lshomes option is shown below:
opatch lshomes
[-domain domain_name | -domain_dir domain_location]
[-mw_home MW_HOME ]
[-invPtrLoc path_to_oraInst.loc]
A summary of the options for the lshomes command are described in Table 2–7.
Table 2–7
Options for the OPatch lshomes Command
Option
Description
-domain domain_name
Optional - list the Oracle homes that have been used to create
or extend this WebLogic Domain.
-domain_dir domain_
location
Optional - list the Oracle homes that have been used to create
or extend the WebLogic Domain at this location.
You must specify the absolute path to the WebLogic Domain.
-mw_home MW_HOME
Optional - list only the Oracle homes registered with the
machine's central inventory that are located in this
Middleware home.
You must specify the absolute path to the Middleware home
directory; this value supersedes the MW_HOME environment
variable. If neither is available, the Middleware home from
which the command is executed will be used.
-invPtrLoc path_to_
oraInst.loc
Optional - absolute path to the location of your oraInst.loc
file; this option is needed if the installation was performed
using the -invPtrLoc option.
Below is an example of the opatch lshomes command on a UNIX operating system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch lshomes
-domain MySOAWebCenterDist
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1/oui
Log file location : /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch2009-12-06_10-57-49AM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility "lshomes"
Home path = "/OracleFMW/Middleware_PS1_RC2/oracle_common"
Patching Oracle Fusion Middleware with Oracle OPatch 2-19
Running OPatch
Home path = "/OracleFMW/Middleware_PS1_RC2/Oracle_SOA1"
Home path = "/OracleFMW/Middleware_PS1_RC2/Oracle_WC1"
OPatch command 'lshomes' done.
OPatch succeeded.
2.4.5 Listing the Domains Created from the Middleware Home or Oracle Home
The lsdomains command lists all the WebLogic Domains that have been created from
a certain Oracle home:
■
■
■
If the Oracle home is specified, then only those domains created from the specified
Oracle home are listed. If no Oracle home is specified, OPatch will list the domains
created from the Oracle home as defined by the ORACLE_HOME environment
variable. If neither is available, then OPatch will use the Oracle home directory
from which the command is run.
If a Middleware home is specified, all domains created from all Oracle homes
within the specified Middleware home are listed.
If neither is specified, and neither the MW_HOME or ORACLE_HOME
environment variable is defined, then OPatch will run the command for the
Middleware home from where the command was run.
The syntax for the lsdomains command is shown below:
opatch lsdomains
[-oh ORACLE_HOME]
[-mw_home MW_HOME]
[-invPtrLoc path_to_oraInst.loc]
A summary of the options for the lsdomains command are described in Table 2–8.
Table 2–8
Options for the OPatch lsdomains Command
Option
Description
-oh ORACLE_HOME
Optional - absolute path to the Oracle home directory.
-mw_home MW_HOME
Optional - absolute path to the Middleware home directory.
-invPtrLoc path_to_
oraInst.loc
Optional - absolute path to the location of your oraInst.loc
file; this option is needed if the installation was performed
using the -invPtrLoc option.
Below is an example of the opatch lsdomains command on a UNIX operating system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch lsdomains
-oh /OracleFMW/Middleware_PS1_RC2/oracle_common
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
Central Inventory
from
OPatch version
OUI version
OUI location
Log file location
:
:
:
:
:
:
:
/OracleFMW/Middleware_PS1_RC2/oracle_common
/ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
/etc/oraInst.loc
11.1.0.6.9
11.1.0.7.0
/OracleFMW/Middleware_PS1_RC2/oracle_common/oui
/OracleFMW/Middleware_PS1_RC2/oracle_
2-20 Oracle Fusion Middleware Patching Guide
Running OPatch
common/cfgtoollogs/opatch/opatch2009-12-06_11-04-41AM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/oracle_
common/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility "lsdomains"
Domain Name = "MySOAWebCenterDist" Path =
"/OracleFMW/MyDomains/domains/MySOAWebCenterDist"
Domain Name = "MyWebCenterOnly" Path =
"/OracleFMW/MyDomains/domains/MyWebCenterOnly"
OPatch command 'lsdomains' done.
OPatch succeeded.
2.4.6 Listing the Applicable Oracle Homes for a Patch
This checkApplicable command produces a list of Oracle homes to which the patch
can be applied. For Fusion Middleware, this command is limited in scope to the
top-level Middleware home:
■
■
■
If only the Middleware home is specified, OPatch will check to see whether or not
this patch can be applied to all Oracle homes within the specified Middleware
home.
If an Oracle home is specified in addition to the Middleware home, OPatch will
check to see if the patch can be applied to the specified Oracle home in the
specified Middleware home.
If neither is specified, and neither the MW_HOME or ORACLE_HOME
environment variable is defined, then OPatch will run the command for the
Middleware home from where the command was run.
The syntax for the checkApplicable command is shown below:
opatch checkApplicable
[-ph patch_location]
[-mw_home MW_HOME]
[-oh ORACLE_HOME]
[-invPtrLoc path_to_oraInst.loc]
A summary of the options for the checkApplicable command are described in
Table 2–9.
Table 2–9
Options for the OPatch checkApplicable Command
Option
Description
-ph patch_location
Optional - location of the patch for which you want to run the
checkApplicable command. If not specified, then the patch in
the current directory is used.
-mw_home MW_HOME
Optional - absolute path to the Middleware home directory.
-oh ORACLE_HOME
Optional - absolute path to the Oracle home directory.
-invPtrLoc path_to_
oraInst.loc
Optional - absolute path to the location of your oraInst.loc
file; this option is needed if the installation was performed
using the -invPtrLoc option.
Patching Oracle Fusion Middleware with Oracle OPatch 2-21
Running OPatch
Below is an example of the opatch checkApplicable command on a UNIX operating
system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch checkapplicable
-ph /OracleFMW/Middleware_PS1_RC2/FMWPatches/9991008/
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1/oui
Log file location : /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch2009-12-06_10-59-57AM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility "checkapplicable"
"checkApplicable" passed for Patch "9991008" and Oracle Home
"/OracleFMW/Middleware_PS1_RC2/oracle_common".
"checkApplicable" failed for Patch "9991008" and Oracle Home
"/OracleFMW/Middleware_PS1_RC2/Oracle_SOA1".
The details are:
Patch 9991008: Required component(s) missing : [ oracle.jrf.j2ee, 11.1.1.2.0 ] , [
oracle.jrf.dms, 11.1.1.2.0 ]
"checkApplicable" failed for Patch "9991008" and Oracle Home
"/OracleFMW/Middleware_PS1_RC2/Oracle_WC1".
The details are:
Patch 9991008: Required component(s) missing : [ oracle.jrf.j2ee, 11.1.1.2.0 ] , [
oracle.jrf.dms, 11.1.1.2.0 ]
Some of the Oracle Homes under the Middleware Home "/OracleFMW/Middleware_PS1_RC2"
have failed this check.
OPatch command 'checkApplicable' done.
-------------------------------------------------------------------------------The following warnings have occurred during OPatch execution:
1) OUI-67124:Some of the Oracle Homes under the Middleware Home
"/OracleFMW/Middleware_PS1_RC2" have failed this check.
-------------------------------------------------------------------------------OPatch Session completed with warnings.
OPatch completed with warnings.
2.4.7 Listing Patches Applied to an Oracle Home or WebLogic Domain
The checkInstalledOneOffs command checks to see if the specified patch or patches
have been applied to certain Oracle homes or WebLogic Domains:
2-22 Oracle Fusion Middleware Patching Guide
Running OPatch
■
■
■
■
If a Middleware home is specified, OPatch checks all the Oracle homes within the
specified Middleware home that are registered with the machine's central
inventory. If not specified, then the MW_HOME environment variable is used.
If an Oracle home is specified, OPatch checks the patch against the specified
Oracle home only.
If neither is specified, and neither the MW_HOME or ORACLE_HOME
environment variable is defined, then OPatch will run the command for the
Middleware home from where the command was run.
If a WebLogic Domain is specified, OPatch checks against all the Oracle homes
within the specified WebLogic Domain.
The syntax for the checkInstalledOneOffs command is shown below:
opatch checkInstalledOneOffs -id patch_IDs
[-mw_home MW_HOME]
[-oh ORACLE_HOME]
[-domain domain_name]
[-invPtrLoc path_to_oraInst.loc]
A summary of the options for the checkInstalledOneOffs command are described in
Table 2–10.
Table 2–10
Options for the OPatch checkInstalledOneOffs Command
Option
Description
-id patch_IDs
ID of the patch or patches that you want to check. Separate
multiple patch IDs with a comma (,) character.
-mw_home MW_HOME
Optional - absolute path to the Middleware home directory.
-oh ORACLE_HOME
Optional - absolute path to the Oracle home.
-domain domain_name
Optional - name of the WebLogic Domain.
-invPtrLoc path_to_
oraInst.loc
Optional - absolute path to the location of your oraInst.loc
file; this option is needed if the installation was performed
using the -invPtrLoc option.
Below is an example of the opatch checkInstalledOneOffs command on a UNIX
operating system. In this example, patch 8965224 is installed in the SOA Oracle home
and patch 9991008 is installed in the Oracle Common Home:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch checkinstalledoneoffs
-id 8965224,9991008
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1/oui
Log file location : /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch2009-12-06_09-40-41AM.log
Patching Oracle Fusion Middleware with Oracle OPatch 2-23
Running OPatch
Patch history file: /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility "checkinstalledoneoffs"
"checkInstalledOneOffs" failed for Oracle Home "/OracleFMW/Middleware_PS1_
RC2/oracle_common".
Not Installed Patch IDs: [8965224]
"checkInstalledOneOffs" failed for Oracle Home "/OracleFMW/Middleware_PS1_
RC2/Oracle_SOA1".
Not Installed Patch IDs: [9991008]
"checkInstalledOneOffs" failed for Oracle Home "/OracleFMW/Middleware_PS1_
RC2/Oracle_WC1".
Not Installed Patch IDs: [8965224, 9991008]
Some of the Oracle Homes under the Middleware Home "/OracleFMW/Middleware_PS1_RC2"
have failed this check.
OPatch command 'checkInstalledOneOffs' done.
-------------------------------------------------------------------------------The following warnings have occurred during OPatch execution:
1) OUI-67124:Some of the Oracle Homes under the Middleware Home
"/OracleFMW/Middleware_PS1_RC2" have failed this check.
-------------------------------------------------------------------------------OPatch Session completed with warnings.
OPatch completed with warnings.
2.4.8 Starting or Stopping a Runtime Instance
The start and stop commands allow Fusion Middleware runtime entities to be
started or stopped, respectively. Only entities of the same type can be started or
stopped; if you need to start or stop entities of multiple types, you must run this
command separately for each entity type.
In order to run this command:
■
■
■
Node Manager must be configured and running on the target server machine.
The WebLogic_Home/common/nodemanager/nodemanager.domains (on UNIX
operating systems) or WebLogic_
Home\common\nodemanager\nodemanager.domains (on Windows operating
systems) must be populated.
You must be able to connect to the Administration Server, which must be up and
running.
The syntax for the start and stop commands is shown below:
opatch start|stop
-domain domain_name
-targets product_entity_name
-target_type product_entity_type
[-oh ORACLE_HOME]
A summary of the options for the start and stop commands are described in
Table 2–11.
2-24 Oracle Fusion Middleware Patching Guide
Running OPatch
Table 2–11
Options for the OPatch start and stop Commands
Option
Description
-domain domain_name
The name of the domain in which the specified targets will be
started or stopped.
-targets product_entity_
name
The name of the WebLogic or Fusion Middleware entity you
want to start or stop. Only entities of the same type can be
specified; multiple entities should be separated by a comma.
-target_type target_type
The type of WebLogic or Fusion Middleware entity you want
to start. Valid values are:
■
fmwApplication
■
fmwServer
■
fmwCluster
■
fmwContainer
The fmwContainer option starts or stops the container (for
example, the WebLogic Server) hosting the application.
The fmwServer option starts or stops the actual java process
that is running (for example, a Managed Server).
Optional - the absolute path to the Oracle home directory. If
this is not specified, the value in the ORACLE_HOME
environment variable is used. If neither is available, then the
Oracle home from which the command is executed is used.
-oh ORACLE_HOME
Below is an example of the opatch start command on a UNIX operating system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch start
-targets soa_server1
-target_type fmwserver
-domain MySOAWebCenterDist
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1/oui
Log file location : /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch2009-12-06_12-30-31PM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility
Please enter the
Please enter the
Please enter the
[FMW] Performing
"start"
WebLogic Admin Server username:> weblogic
WebLogic Admin Server password:>
WebLogic Admin Server URL(t3://stadn41:7011):>
Start Actions
Patching Oracle Fusion Middleware with Oracle OPatch 2-25
Troubleshooting OPatch in a Fusion Middleware Environment
[FMW] Finished Start Actions
OPatch command 'start' done.
OPatch succeeded.
Below is an example of the opatch stop command on a UNIX operating system:
[aime@stadn41 Oracle_SOA1]$ ./OPatch/opatch stop -targets soa_server1 -target_type
fmwserver -domain MySOAWebCenterDist
Invoking OPatch 11.1.0.6.9
Oracle Interim Patch Installer version 11.1.0.6.9
Copyright (c) 2009, Oracle Corporation. All rights reserved.
UTIL session
Oracle Home
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1
Central Inventory : /ade/aime_dte6989/oracle/work/EM_SH_1/oraInventory
from
: /etc/oraInst.loc
OPatch version
: 11.1.0.6.9
OUI version
: 11.1.0.7.0
OUI location
: /OracleFMW/Middleware_PS1_RC2/Oracle_SOA1/oui
Log file location : /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch2009-12-06_11-13-59AM.log
Patch history file: /OracleFMW/Middleware_PS1_RC2/Oracle_
SOA1/cfgtoollogs/opatch/opatch_history.txt
OPatch detects the Middleware Home as "/OracleFMW/Middleware_PS1_RC2"
Invoking utility "stop"
Please enter the WebLogic Admin Server username:> weblogic
Please enter the WebLogic Admin Server password:>
Please enter the WebLogic Admin Server URL(t3://stadn41:7011):>
[FMW] Performing Stop Actions
[FMW] Finished Stop Actions
OPatch command 'stop' done.
OPatch succeeded.
2.5 Troubleshooting OPatch in a Fusion Middleware Environment
This section describes common issues you may encounter when running the OPatch
utility in a Fusion Middleware environment.
2.5.1 Notes About Patching the MDS Repository
For special information about patching the MDS repository, refer to "Understanding
the MDS Repository" in the Oracle Fusion Middleware Administrator's Guide.
2.5.2 Setting the Machine Name and Listen Address
The machine name of the Administration Server and Managed Servers must be set to a
valid value. It cannot be set to blank or None.
The listen address of the Administration and Managed Servers must be set to the real
physical host's address (hostname, FQDN, or IP address). It cannot be set to blank or
localhost.
2-26 Oracle Fusion Middleware Patching Guide
Troubleshooting OPatch in a Fusion Middleware Environment
These values need to be properly set only once; you will not need to reset them should
you ever need to patch your software.
To set the machine name and listed address of the Managed Servers:
1.
Open the Administration Console.
2.
In the Domain Structure, navigate to domain_name > Environments > Machines.
3.
If your WebLogic Server is running in Production Mode, click the Lock & Edit
button on the left hand side. If your WebLogic Server is running in Development
Mode, this step is not needed.
4.
Click the New button to create a new machine. Specify a name and select the
operating system.
5.
Select the machine you just created, go to Configuration > Node Manager and
change the Listen Address to the host on which the Node Manager is listening,
then click the Save button.
6.
In the Domain Structure, navigate to domain_name > Environments > Servers.
7.
For each Managed Server, assign the machine you just created. In the Listen
Address field, specify the name of the host on which the Node Manager is
listening. Click Save when you are finished.
8.
If your WebLogic Server is running in Production Mode, click the Activate
Changes button on the left hand side. If your WebLogic Server is running in
Development Mode, this step is not needed.
To set the machine name and listen address of the Administration Server:
1.
Stop the Administration Server and all Managed Servers.
2.
Back up the config.xml file in the domain.
The default location of this file is the config directory inside your Domain home.
3.
Modify the existing config.xml file as follows:
a.
Find the following line:
<name>AdminServer</name>
b.
Add the following lines:
<machine>host_name</machine>
<listen-address>host_name</listen-address>
c.
4.
Save the file.
Restart the Administration Server and all the Managed Servers.
If you encounter any problems, revert back to the saved version of the config.xml
file and contact Oracle Support.
Patching Oracle Fusion Middleware with Oracle OPatch 2-27
Troubleshooting OPatch in a Fusion Middleware Environment
2-28 Oracle Fusion Middleware Patching Guide
3
Applying the Latest Oracle Fusion Middleware
Patch Set
3
This chapter describes how to patch your existing Oracle Fusion Middleware software
to the latest version. The specific patching instructions you follow depend on the
version of your current software. Instructions in this chapter are provided for software
versions 11.1.1.2.0 and later.
[3]
The following pre-patching procedures must be completed
before you can upgrade your software to Release 11.1.1.9.0:
Note:
■
■
If you have Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0),
you must upgrade to Release 1 (11.1.1.2.0) before you can upgrade
your software to Release 11.1.1.9.0. See Appendix C, "Using Patch
Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1
(11.1.1.2.0)"for instructions.
If you are upgrading Oracle Identity and Access Management
components, such as Oracle Access Manager, Oracle Adaptive
Access Manager or Oracle Identity Manager, see "Oracle Fusion
Middleware Upgrade Guide for Oracle Identity and Access
Management".
This chapter includes the following topics:
■
Oracle Fusion Middleware Patching Process Overview
■
Oracle Fusion Middleware Patching Process Roadmap
■
Before You Begin
■
General Pre-Patching Tasks
■
Downloading the Installer
■
Patching Oracle Fusion Middleware
■
Upgrading Your Schemas with Patch Set Assistant
■
Starting the Servers and Processes
■
Verifying Your Patch Set Installation
Applying the Latest Oracle Fusion Middleware Patch Set
3-1
Oracle Fusion Middleware Patching Process Overview
3.1 Oracle Fusion Middleware Patching Process Overview
Figure 3–1 shows the general patching procedures for Oracle Fusion Middleware.
Review the overview before you begin your patching procedures to ensure you
understand the process.
Figure 3–1 Oracle Fusion Middleware Patching Process Overview and Roadmap
3.2 Oracle Fusion Middleware Patching Process Roadmap
Table 3–1 provides links to additional information for each of the patching steps.
3-2 Oracle Fusion Middleware Patching Guide
Oracle Fusion Middleware Patching Process Roadmap
Table 3–1
Summary of Patching Procedures and Links to Documentation
Step
Description
1
Perform the following general pre-patching tasks before you begin the patching process:
1.
Before You Begin
■
Special Instructions for Patching Oracle WebCenter Portal
■
Special Instructions for Patching Oracle WebCenter Content
■
■
Special Instructions for Patching a Distributed Environment
■
Special Instructions for Patching Oracle SOA Suite
Special Instructions for Patching Oracle WebLogic Server 10.3.6 with
SOA Suite
General Pre-Patching Tasks
■
■
■
■
■
2
Special Instructions for Patching Oracle Portal, Forms, Reports and
Discoverer
■
■
2.
Special Instructions for Patching Oracle WebCenter Enterprise
Capture
Reviewing System Requirements and Certification
Reviewing the Oracle Fusion Middleware Interoperability and
Compatibility Guide
Upgrading Oracle WebLogic Server and Applying Required
WebLogic Server Patches
Stopping the Servers and Processes
Backing Up Your Middleware Home, Domain Home and Oracle
Instances
■
Backing Up Your Database and Database Schemas
■
Backing Up Additional Configuration Information
■
Renaming the emCCR File for Silent Patching
Download and start the appropriate installer for your product:
For details, see Downloading the Installer.
3
Upgrade the software in your Oracle home using the downloaded Installer.
Also, apply the Oracle SOA Suite patch.For information, see Patching Oracle Fusion Middleware.
4
If necessary, upgrade your database schemas with the Patch Set Assistant.
To see if you need to run the Patch Set Assistant, refer to Table 4–1, " Schemas That Require Upgrading for
the Latest Release".
For more information, see Upgrading Your Schemas with Patch Set Assistant.
Applying the Latest Oracle Fusion Middleware Patch Set
3-3
Before You Begin
Table 3–1 (Cont.) Summary of Patching Procedures and Links to Documentation
Step
Description
5
Perform any necessary post-patching tasks (for example, starting the servers and processes in a domain,
starting Oracle instances, running scripts or modifying configuration files). The tasks that need to be
performed will vary depending on the version of your existing software and components configured in
your environment. Refer to the tables in the following sections for details:
■
Section 5.2, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.2"
■
Section 5.3, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.3"
■
Section 5.4, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.4"
■
Section 5.5, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.5"
■
Section 5.6, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.6"
■
Section 5.7, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.7"
■
Section 5.8, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.8"
■
Section 5.9, "Post-Patching Tasks for System Components"
■
Section 5.10, "Post-Patching Tasks for Oracle Identity Management Components"
■
Section 5.11, "Post-Patching Tasks for Your WebLogic Server Domain"
■
Section 5.12, "Post-Patching Tasks for Oracle SOA Suite"
■
Section 5.13, "Post-Patching Tasks for Oracle WebCenter Content"
■
Section 5.14, "Post-Patching Tasks for Oracle Service Bus"
■
Section 5.15, "Post-Patching Tasks for Oracle Business Intelligence"
■
Section 5.16, "Post-Patching Tasks for Oracle Data Integrator"
Post-patching tasks related to Oracle WebCenter Portal are described here:
■
6
Chapter 6, "Patching Oracle WebCenter Portal"
Start the servers and processes.
For more information, see Section 3.8, "Starting the Servers and Processes".
7
Verify that your patch installation is complete.
For more information, see Section 3.9, "Verifying Your Patch Set Installation".
3.3 Before You Begin
Before you begin the patching procedures discussed in this chapter, complete any
applicable pre-patching tasks outlined in this section. The "Special Instructions"
sections in this chapter will help you determine if there are any special pre-patching
tasks required for your environment.
■
Special Instructions for Patching a Distributed Environment
■
Special Instructions for Patching Oracle SOA Suite
■
Special Instructions for Patching Oracle WebLogic Server 10.3.6 with SOA Suite
■
Special Instructions for Patching Oracle WebCenter Portal
■
Special Instructions for Patching Oracle WebCenter Content
■
Special Instructions for Patching Oracle WebCenter Enterprise Capture
■
Special Instructions for Patching Oracle Portal, Forms, Reports and Discoverer
3-4 Oracle Fusion Middleware Patching Guide
Before You Begin
3.3.1 Special Instructions for Patching a Distributed Environment
If you are running your products in a distributed environment (for example, you have
Managed Servers running in multiple domains on multiple systems) and you have set
up a shared Middleware home on a shared network drive mounted to each machine
that is part of your domain, then this patching procedure only needs to be done once
(see Section 2.3.3, "Patching in a Distributed Environment").
If your distributed environment has a separate Middleware home on each system,
then this patching procedure must be repeated for each domain on each system.
More information about distributed topologies can be found in the Enterprise
Deployment Guide for your specific product.
3.3.2 Special Instructions for Patching Oracle SOA Suite
Before upgrading to the latest release, make sure all Edit sessions in SOA Composer
are committed or reverted.
SOA Composer provides DT@RT functionality to edit rules dictionaries after
deployment. After upgrading to the latest version, all uncommitted sessions in SOA
Composer will be lost or there can be issues accessing the edit sessions. This is because
the MDS sandboxes (used for handling sessions) are not upgraded by the patch set.
To commit or revert the sessions:
1.
Log in to the SOA Composer (/soa/composer) as any user with active sessions.
2.
Go to Open > My Edits to view all of your active sessions.
3.
Open each document listed in "My Edits" and do one of the following:
a.
Click Commit to commit the session changes.
b.
Select Revert > Clear all session edits and saved changes to abort the
changes.
Either step will result in the session being closed.
3.3.3 Special Instructions for Patching Oracle WebLogic Server 10.3.6 with SOA Suite
After installing the latest version of Oracle WebLogic Server (version 10.3.6), you must
install the required patches as described on the "Known Issues for Oracle SOA
Products and Oracle AIA Foundation Pack" page on Oracle Technology Network at:
http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-186603
0.html
3.3.4 Special Instructions for Patching Oracle WebCenter Portal
The procedures you need to follow for patching your existing Oracle WebCenter
software depend on your current software version. Chapter 6, "Patching Oracle
WebCenter Portal" describes the procedures for patching the various versions of
Oracle WebCenter. For patching Oracle WebCenter, you can directly navigate to
Chapter 6 and follow the instructions there. Many of the steps listed in refer back to
this and other chapters of this guide.
3.3.5 Special Instructions for Patching Oracle WebCenter Content
Review the following before applying the patch set:
■
Enabling WebCenter Content Components Before Upgrade
Applying the Latest Oracle Fusion Middleware Patch Set
3-5
Before You Begin
■
Disabling Obsolete Components Before Upgrade
3.3.5.1 Enabling WebCenter Content Components Before Upgrade
If you manually disabled any WebCenter Content components that you plan to use
after the upgrade, then you must enable them prior to applying the latest patch set.
Oracle recommends that you do not manually disable any
components before applying the latest patch sets. Disabling
components can cause the upgrade to fail and content servers will not
be able to start. The only exceptions are listed in Section 3.3.5.2.
Note:
Specifically, if any of the following components were disabled before the upgrade
process, and you plan to use them after the upgrade, then you should enable them
before the upgrade explicitly:
■
Content Folios
■
ArchiverReplicationExceptions
■
CheckoutAndOpenInNative
■
CheckSCSHealth
■
ConfigMigrationUtility
■
CSDms
■
ExtendedUserAttributes
■
FileStoreProvider
■
IdcClient
■
InboundRefinerySupport
■
iTextComponent
■
JpsUserProvider
■
Localization
■
NativeOsUtils
■
OCM
■
OracleLocalization
■
OracleQueryOptimizer
■
PopUpCalendar
■
ProxyConnections
■
RMFeatureConfig
■
SecurityProviders
■
ServletPlugin
■
UserProfileSchemaLoader
■
WebUrlMapPlugin
■
WsdlGenerator
■
YahooUserInterfaceLibrary
3-6 Oracle Fusion Middleware Patching Guide
Before You Begin
■
ZipRenditionManagement
For more information, see "Enabling or Disabling a Component Using the Component
Manager" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
3.3.5.2 Disabling Obsolete Components Before Upgrade
The following components should be disabled before the upgrade because they are
obsolete or disabled in 11g Release 1 (11.1.1.9.0).
Failure to disable these components may cause the upgrade to fail and content servers
will not be able to start.
■
FCKEditor
■
Query Folders
■
ProxyConnection8 (renamed to ProxyConnection)
■
LinkManager8 (renamed to LinkManger)
For more information, see "Enabling or Disabling a Component Using the Component
Manager" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
3.3.6 Special Instructions for Patching Oracle WebCenter Enterprise Capture
Before applying this patch to update Oracle WebCenter Enterprise Capture, review the
following and complete all applicable tasks.
■
■
■
Apply this patch only to standard (non Fusion Application) environments already
running Capture 11.1.1.8.0.
Patch all Capture systems within a clustered environment simultaneously.You can
patch independent Capture systems separately.
Identify a time to perform the updates that will not interfere with operations.
The services will be unavailable while the update is being performed.
■
Stop the Capture server before applying this patch.
■
Clear the read-only attributes for the following files before applying the patch:
ORACLE_HOME/capture/bin/win32/clearimage.dll
ORACLE_HOME/capture/bin/win64/clearimage.dll
■
Verify all batch processing completes and ensure that the Capture JMS queues are
empty.
1.
Open the Administration Console for this domain.
http://<AdminServerName>:7001/console
Where:
<AdminServerName> = is the name or IP address of the administration server
associated with the Capture domain
7001 = the communication port associated with the administration server
2.
In the "Domain Structure" navigation panel on the left, expand "Services".
3.
Expand the "Messaging" node.
4.
Select the "JMS Servers" item in the tree list.
5.
Select the "capture-jms-server" item in the "JMS Servers" list in the main panel.
Applying the Latest Oracle Fusion Middleware Patch Set
3-7
General Pre-Patching Tasks
6.
Select the "Monitoring" tab.
7.
Select the "Monitoring" sub-tab.
8.
Verify that the "Messages Current" and "Messages Pending" values in the table
are both "0".
If either of these values is greater than zero, indicating pending jobs, wait until
all jobs have been processed and these counters show "0" before proceeding.
Once you have completed these Enterprise Capture pre-upgrade tasks, go to section
Section 3.4, "General Pre-Patching Tasks" and complete any other pre-upgrade tasks
that pertain to your deployment.
3.3.7 Special Instructions for Patching Oracle Portal, Forms, Reports and Discoverer
To prevent compatibility issues with other Fusion Middleware products, Oracle
recommends that Oracle Portal, Forms, Reports, and Discoverer be installed in its own
Middleware home directory that it does not share with any other Oracle Fusion
Middleware products.
For more information on the compatibility and interoperability of Fusion Middleware
products, see the Oracle Fusion Middleware Interoperability and Compatibility Guide.
3.4 General Pre-Patching Tasks
This section describes tasks that should be completed before you patch your software:
■
■
Reviewing System Requirements and Certification
Reviewing the Oracle Fusion Middleware Interoperability and Compatibility
Guide
■
Stopping the Servers and Processes
■
Backing Up Your Middleware Home, Domain Home and Oracle Instances
■
Backing Up Your Database and Database Schemas
■
Backing Up Additional Configuration Information
■
■
Upgrading Oracle WebLogic Server and Applying Required WebLogic Server
Patches
Renaming the emCCR File for Silent Patching
3.4.1 Reviewing System Requirements and Certification
Before you begin to upgrade your software, you should make sure that your system
environment and configuration meet the minimum requirements for the software you
want to install in order to perform the upgrade. This section contains links to several
key pieces of documentation you should review:
■
System Requirements and Specifications
■
Certification and Supported Platforms
■
■
Verify that the Java Development Kit (JDK) Version is Supported and Certified
with Oracle Fusion Middleware 11g (11.1.1.9)
Updating the setDomainEnv Script File with Upgraded JDK Location
3-8 Oracle Fusion Middleware Patching Guide
General Pre-Patching Tasks
3.4.1.1 System Requirements and Specifications
For certification information, refer to the System Requirements and Supported
Platforms for Oracle Fusion Middleware 11gR1 document on the Oracle Fusion
Middleware Supported System Configurations page at the following URL:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certific
ation-100350.html
This page contains information related to hardware and software requirements,
minimum disk space and memory requirements, database schema requirements, and
required system libraries, packages, or patches.
3.4.1.2 Certification and Supported Platforms
Read the System Requirements and Supported Platforms for Oracle Fusion Middleware
11gR1 document. This document contains certification information related to
supported 32-bit and 64-bit operating systems, databases, web servers, LDAP servers,
adapters, IPv6, JDKs, and third-party products. It is located on the Oracle Fusion
Middleware Supported System Configurations page.
3.4.1.3 Verify that the Java Development Kit (JDK) Version is Supported and
Certified with Oracle Fusion Middleware 11g (11.1.1.9)
This release of Oracle Fusion Middleware requires a 64-bit JDK 7 (1.7.x), which can be
downloaded at the following URL:
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880
260.html.
JRockit Users: JRockit is no longer supported. You must install
the Sun JDK to use with this release.
Note:
For up to date supported configuration information, see Oracle Fusion
Middleware Supported System Configurations at:
http://www.oracle.com/technetwork/middleware/ias/downloads/f
usion-certification-100350.html.
For more information about JDK version requirements, see the "Oracle WebLogic
Server and JDK Considerations" topic in the Oracle Fusion Middleware System
Requirements and Specifications for Oracle Fusion Middleware 11g Release 1 (11.1.1.9)
document.
For more information about using JDK 7 with this release of Oracle Fusion
Middleware, see "Using WebLogic Server with JDK 7" in Installing and Configuring
Oracle WebLogic Server and Coherence.
Before an upgrade, always consult the System Requirements and Supported Platforms for
Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported
System Configurations page for supported JDK versions.
3.4.1.4 Updating the setDomainEnv Script File with Upgraded JDK Location
If you just upgraded your JDK, make sure that you manually update the path to point
to the new JDK 1.7.x.
To configure your domains to use the updated JDK, edit the following file:
For Windows operating systems:
cd MW_HOME\user_projects\domains\domain_name\bin
Applying the Latest Oracle Fusion Middleware Patch Set
3-9
General Pre-Patching Tasks
edit setDomainEnv.cmd
For UNIX operating systems:
cd MW_HOME/user_projects/domains/domain_name/bin
edit setDomainEnv.sh
Replace all occurrences of the existing JDK version with the updated JDK.
Stop and restart the servers to make sure that there are no issues with the JDK before
you begin using the upgraded environment.
For more information about using JDK 7 with WebLogic
Server 10.3.6, see "Using WebLogic Server with JDK 7" in Installing and
Configuring Oracle WebLogic Server and Coherence.
Note:
3.4.2 Reviewing the Oracle Fusion Middleware Interoperability and Compatibility Guide
Read "Patch Set Interoperability" in the Oracle Fusion Middleware Interoperability and
Compatibility Guide before you begin your patching process. This document contains
important information regarding the ability of Oracle Fusion Middleware products to
function with previous versions of other Oracle Fusion Middleware, Oracle, or
third-party products. This information is applicable to both new Oracle Fusion
Middleware users and existing users who are upgrading their existing environment.
Caution: Some versions of Oracle Identity Management products are
not compatible with previous versions. For detailed information, see
the Oracle Fusion Middleware Interoperability and Compatibility Guide.
3.4.3 Stopping the Servers and Processes
Before you run the installer to upgrade your software, you should stop all servers and
processes (including OPMN) on all machines which are part of any domain used
from the Middleware home.
Instructions for stopping an Oracle Fusion Middleware environment are provided in
"Stopping an Oracle Fusion Middleware Environment" in Oracle Fusion Middleware
Administrator's Guide.
If your environment is running Oracle Process Manager and Notification Server
(OPMN), you should also stop OPMN with the opmnctl stopall command.
If you are running Node Manager, you should also stop Node Manager. You can do
this by closing the console window in which Node Manager is running, or by using
the stopNodeManager WLST command.
In order for the stopNodeManager command to work, Node
Manager must be configured with QuitEnabled=true.
Note:
See "stopNodeManager" in WLST Command Reference for WebLogic
Server for more information.
3.4.4 Backing Up Your Middleware Home, Domain Home and Oracle Instances
After stopping the servers and processes, back up your Middleware home directory
(including the Oracle home directories inside the Middleware home), your local
3-10 Oracle Fusion Middleware Patching Guide
General Pre-Patching Tasks
Domain home directory, your local Oracle instances, and also the Domain home and
Oracle instances on any remote systems that use the Middleware home.
Backing up your environment before applying your patch is an important step in the
patching process. If your patch set installation is unexpectedly interrupted, or if you
choose to cancel out of the installation before it is complete, you may not be able to
install the patch unless you restore your environment to the previous configuration
before running the Installer again.
For more information on backing up your environment, see "Backing Up Your
Environment" in the Oracle Fusion Middleware Administrator's Guide.
3.4.5 Backing Up Your Database and Database Schemas
If your database schemas require upgrading, you should also back up your database
before you begin the patching procedure. Make sure this back up includes the schema
version registry table, as each Fusion Middleware schema has a row in this table. The
name of the schema version registry table is SYSTEM.SCHEMA_VERSION_REGISTRY$. Refer
to your database documentation for instructions on how to do this.
If you run the Patch Set Assistant to upgrade an existing schema and it does not
succeed, you must restore the original schema before you can try again. Make sure you
back up your existing database schemas before you run the Patch Set Assistant.
Oracle recommends that you use RMAN to make a physical
backup of the database.
Note:
Some components use additional, auxiliary schemas that would also
need to be backed up, even though those particular schemas do not
contain a schema version registry entry. If, in addition to RMAN, you
also want to back up individual schemas using the exp or expd
utilities, verify that all Oracle Fusion Middleware schemas are backed
up, not just those having a row in the SYSTEM.SCHEMA_VERSION_
REGISTRY$ table.
Oracle does not recommend users to consider expd and exp utilities as
a substitute for performing a complete database level physical backup
with RMAN. RMAN is always required.
To see if your schemas require upgrading, refer to Table 4–1, " Schemas That Require
Upgrading for the Latest Release" in "Upgrading Your Schemas with Patch Set
Assistant".
3.4.6 Backing Up Additional Configuration Information
Depending on your specific environment, you might also need to back up the
following before performing any patching procedures:
■
Back Up Configurations and Stores
Each WebLogic Server domain must be upgraded using the upgradeOpss() WLST
command. Before running the upgradeOpss() command, make sure that you
backup the store to be upgraded. In case of a LDAP store, backup all data under
the root node of the store (which is specified as a property of the store in the
configuration file). In case of an upgrade failure, restore that node entirely.
For more information, see "Upgrading Policies with upgradeOpss" in Securing
Applications with Oracle Platform Security Services.
Applying the Latest Oracle Fusion Middleware Patch Set 3-11
General Pre-Patching Tasks
■
Save OmniPortlet and WebClipping Customizations for Oracle WebCenter or
Oracle Portal
If you are using OmniPortlet and WebClipping customizations, and they are being
used with a file-based preferences store, you must save your customizations.
■
Save XEngine Customizations for Oracle B2B
This procedure is needed only if you use custom XEngine configurations in cases
where B2B server is integrated with B2B EDI endpoints. In such cases, all B2B
domains created from the same installation share the a single XEngine
configuration stored within a single directory. This directory must be backed up
prior to patching, and then restored after patching is complete.
For more information, see Section 5.12.9, "Saving and Restoring XEngine
Customizations for Oracle B2B".
■
Back Up Existing Oracle BI Presentation Catalogs
When upgrading your Oracle Business Intelligence (BI) software from Release
11.1.1.3.0 to 11.1.1.9.0, you must manually upgrade your Oracle BI Presentation
Catalogs. See Section 5.15.3, "Upgrading Oracle BI Presentation Catalogs" for more
information.
■
Back Up Files for Oracle Data Integrator Java EE Standalone Agent
Make sure the following files and directories are backed up (they should be if you
backed up your Oracle home directory, as specified in Section 3.4.4, "Backing Up
Your Middleware Home, Domain Home and Oracle Instances"):
1.
Backup the ODI_HOME/oracledi/agent/bin/odiparams.sh (on UNIX
operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on
Windows operating systems) file.
2.
Backup the ODI_HOME/oracledi/agent/drivers (on UNIX operating systems)
or ODI_HOME\oracledi\agent\drivers (on Windows operating systems)
directory.
After Oracle Data Integrator is patched, follow the instructions in Section 5.16.3,
"Reconfiguring the ODI Standalone Agent".
■
Back up custom JSPs for Oracle Identity Federation
If you are upgrading your Oracle Identity Federation to the latest release, you
should back up any custom JSPs before patching to the latest version. The
patching process will overwrite the JSPs included in the oif.ear file.
After the patching process is complete, you should restore your custom JSPs.
3.4.7 Upgrading Oracle WebLogic Server and Applying Required WebLogic Server
Patches
If Oracle WebLogic Server 10.3.6 is already installed on your system, and your MW_HOME
is configured to use 10.3.6, then make sure you have applied all required WebLogic
Server patches before using the Upgrade installer.
Also, verify that the JDK you are using is supported for this version of WebLogic
Server. For more information, see Verify that the Java Development Kit (JDK) Version
is Supported and Certified with Oracle Fusion Middleware 11g (11.1.1.9).
If WebLogic Server 10.3.6 is not installed on your system, you must upgrade the MW_
HOME to 10.3.6 and then apply all mandatory patches. For more information, see
Upgrading Oracle WebLogic Server.
3-12 Oracle Fusion Middleware Patching Guide
General Pre-Patching Tasks
You can find a list of required WebLogic Server patches in "Mandatory Patches for
Oracle WebLogic Server" in the Oracle Fusion Middleware Infrastructure Release Notes.
Caution: Do not apply the WebLogic Server patches to the MW_HOME
until it has been upgraded to 10.3.6
The patches listed in the release notes are available from My Oracle Support. The
patching instructions are mentioned in the README.txt file that is provided with each
patch.
Some Oracle WebLogic Server patches require additional post-patching tasks before
starting the servers. For more information, see the Readme.txt file that is provided
with each patch.
Note: Even if you already have Oracle WebLogic Server 10.3.6
installed, make sure that you have applied the mandatory patches
before you begin the upgrade process.
To upgrade the WebLogic Server:
1.
Download the Upgrade installer from My Oracle Support.
For instructions, see "Downloading an Upgrade Installer From My Oracle
Support" in Installing and Configuring Oracle WebLogic Server and Coherence.
2.
Run the Upgrade installer in graphical mode to patch your WebLogic Server.
For instructions, see "Running the Upgrade Installer in Graphical Mode" in
Installing and Configuring Oracle WebLogic Server and Coherence.
If you want to run the Upgrade installer in silent mode (for example, you have an
environment where you need to patch multiple instances of Oracle WebLogic Server),
see the instructions in "Running the Installation Program in Silent Mode" in Installing
and Configuring Oracle WebLogic Server and Coherence.
Note: If you have Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0), and you are installing Oracle WebLogic Server for the first
time to upgrade to Release 1 (11.1.1.2.0) or later, see the "Installation
Overview" in the Installing and Configuring Oracle WebLogic Server and
Coherence.
3.4.8 Renaming the emCCR File for Silent Patching
If you are patching your software in silent mode, you may encounter the following
error messages:
"SEVERE:Values for the following variables could not be obtained from the command
line or response file(s):
MYORACLESUPPORT_USERNAME(MyOracleSupportUsername)"
To work around this issue, rename the ORACLE_HOME/ccr/bin/emCCR (on UNIX
operating systems) or ORACLE_HOME\ccr\bin\emCCR (on Windows operating systems)
file.
For example, on a UNIX operating system:
cd ORACLE_HOME/ccr/bin
Applying the Latest Oracle Fusion Middleware Patch Set 3-13
Downloading the Installer
mv emCCR emCCR_LAST
On a Windows operating system:
cd ORACLE_HOME\ccr\bin
mv emCCR emCCR_LAST
See "Silent Oracle Fusion Middleware Installation and Deinstallation" in Oracle Fusion
Middleware Installation Planning Guide for more details about silent installation.
3.5 Downloading the Installer
The following sections contain instructions on how to obtain the proper installer
required to patch your product:
■
About the Installers Used for Patching
■
Downloading the Required Installer
3.5.1 About the Installers Used for Patching
The installers you use to apply the latest Oracle Fusion Middleware patch sets vary in
their behavior and capabilities, depending upon the product you are using. Before you
begin the patching process, review Table 3–2 for information about the types of
installers and what to expect when you run the installer to apply the latest patch set.
Note that this table is not a complete list of Oracle Fusion Middleware products. For a
complete list of the products available with each patch set release, see the Oracle Fusion
Middleware Download, Installation, and Configuration ReadMe Files.
Table 3–2
Patch Set
Summary of the Oracle Fusion Middleware Installers Used to Apply the Latest
Products
Type and Behavior of the Installer
Oracle Application Developer These installers are full installers that can also function as
Runtime
upgrade installers. You can use them to upgrade an existing
11g Release 1 Oracle home, or you can use them to install a
Oracle SOA Suite
new, complete Oracle home.
Oracle Business Intelligence
Oracle Service Bus
Oracle WebCenter Portal
Oracle WebCenter Content
Oracle WebCenter Enterprise
Capture
Oracle Internet Directory
Oracle Virtual Directory
Oracle Web Tier
Oracle Business Intelligence
3-14 Oracle Fusion Middleware Patching Guide
These installers are full installers that can also function as
upgrade installers. They can be used to upgrade an existing
11g Release 1 Oracle home, or they can be used to install a new,
complete Oracle home.
These installers also offer a configuration option. When using
them to apply a patch set, you must select the option to install
the software only. Do not select the option to configure the
software. The domain you are patching is already configured
and does not require any reconfiguration.
Patching Oracle Fusion Middleware
Table 3–2 (Cont.) Summary of the Oracle Fusion Middleware Installers Used to Apply
the Latest Patch Set
Products
Type and Behavior of the Installer
Oracle Forms, Reports and
Discover
This installer is an upgrade-only installer, which requires an
existing Oracle Fusion Middleware 11g Release 1 Oracle home.
Note that Oracle Portal will
remain 11g Release 11.1.1.6.0
as it is not being upgraded in
this release.
3.5.2 Downloading the Required Installer
To download and unpack the Installer files for your product:
1.
Download the installer from the Oracle Technology Network, My Oracle Support,
or Oracle Software Delivery Cloud (formerly E-Delivery).
For more information, see "Select an Oracle Fusion Middleware Software
Download Site" and "Download the Software Required for Your Starting Point" in
Oracle Fusion Middleware Download, Installation, and Configuration ReadMe Files.
2.
Unpack the downloaded archive that contains the installer and software that you
want to install into a directory on the target computer.
3.6 Patching Oracle Fusion Middleware
The following sections contain instructions on how to start the installer and apply the
patch set for your product:
■
Starting the Installer
■
Applying the Patch Set
■
Performing the Required Post Patching Procedures
3.6.1 Starting the Installer
To start the installer you just downloaded and unpacked:
1.
Change directory to the Disk1 folder inside the unpacked archive folder.
2.
Start the Installer:
On UNIX operating systems:
./runInstaller
On Windows operating systems:
setup.exe
Depending on your system environment and product you are upgrading, you may be
prompted to provide the location of a JRE/JDK on your system when you start the
installer. When you installed Oracle WebLogic Server, a JRE was installed in the
jdk160_version directory inside the Middleware home; you can use this location to
start the installer.
If you do not have Oracle WebLogic Server installed on your system, you can use the
JDK in the jdk directory inside the Oracle home.
Applying the Latest Oracle Fusion Middleware Patch Set 3-15
Patching Oracle Fusion Middleware
Make sure you specify the absolute path to your JRE/JDK location; relative paths are
not supported.
The Installer can also be run in silent mode. See "Silent Oracle Fusion Middleware
Installation and Deinstallation" in Oracle Fusion Middleware Installation Planning Guide
for more details.
3.6.2 Applying the Patch Set
After you have started the Installer, follow the instructions on the screen to apply the
patch set to your existing Middleware home.
If your domain includes multiple host computers, you must
run the Installer separately on each host to upgrade the software on
that host.
Note:
As you review each screen of the installer, note that there are two significant
differences between applying a patch set and installing software for the first time:
■
■
When you are applying a patch set, you must identify an existing Middleware
home on the Specify Installation Location screen.
If you are installing Oracle Identity Management, Oracle Business Intelligence, or
Oracle Web Tier, then you must perform a software only install and select the
existing Middleware home and Oracle home you want to patch. There is no need
to configure or re-configure your existing software.
Table 3–3 provides a summary of the typical installation screens you will see when you
are applying a patch set to an existing Middleware home.
Oracle Fusion Middleware products in this release can be
upgraded with their usual product installer.
Note:
If you need additional help with any of the installation screens, refer to Appendix A,
"Installer Screens" or click Help to access the online help.
Table 3–3
Typical Installation Flow For Installing a Patch Set
Screen
Description
Welcome
This page introduces you to the Oracle Fusion Middleware installer.
Install Software Updates
Select the method you want to use for obtaining software upgrades, or select Skip
Software Updates if you do not want to get updates.
If updates are found, the installer will automatically attempt to apply them at this
point; make sure that the server you are using to perform the installation is
connected to the Internet.
Some updates will require that the installer be restarted; if this happens, the Install
Software Updates screen will not be seen the next time.
Prerequisite Checks
Verify that your system meets all necessary prerequisites.
Specify Installation Location
Specify Oracle Middleware home and Oracle home locations.
The Oracle Common home (oracle_common) directory will automatically be
created inside the Middleware home; do not use oracle_common as the name of
your Oracle home directory.
Application Server
Select the application server and specify its location.
3-16 Oracle Fusion Middleware Patching Guide
Starting the Servers and Processes
Table 3–3 (Cont.) Typical Installation Flow For Installing a Patch Set
Screen
Description
Installation Summary
Verify the information on this screen, then click Install to begin the installation.
Installation Progress
This screen shows the progress of the installation.
When the progress shows 100% complete, click Next to continue.
Installation Complete
Click Save to save your configuration information to a file. This information
includes port numbers, installation directories, URLs, and component names
which you may need to access at a later time.
After saving your configuration information, click Finish to dismiss the installer.
3.6.3 Performing the Required Post Patching Procedures
Some components require that you preform additional post-patching tasks. Review
Post-Patching Procedures to determine if any additional configuration tasks are
required after applying the patch set.
3.7 Upgrading Your Schemas with Patch Set Assistant
To see if your schema requires upgrading with the Patch Set Assistant, refer to
Table 4–1, " Schemas That Require Upgrading for the Latest Release" in "Which
Schemas Need to be Upgraded with Patch Set Assistant?".
If the product you are patching uses one of the schemas listed in the table, follow the
instructions in Chapter 4, "Upgrading Your Schemas with Patch Set Assistant" to
upgrade your schemas.
If the product you are patching does not use one of these schemas, you can skip this
section and proceed to Chapter 5, "Post-Patching Procedures".
3.8 Starting the Servers and Processes
After you have finished patching your software and performing any necessary
post-patching tasks, you are ready to start the servers and processes.
Some components require that you preform additional
post-patching tasks. Review Post-Patching Procedures to determine if
any additional configuration tasks are required after applying the
patch set.
Note:
You must start the Node Manager, the WebLogic Administration Server, and the
Managed Servers with Java Secure Socket Extension (JSSE) enabled, if you have
applied the following Oracle WebLogic Server patches to your Middleware home:
■
13964737 (YVDZ)
■
14174803 (IMWL)
These patches are available from My Oracle Support.
For information on how to start the Node Manager with JSSE enabled, see the "Set the
Node Manager Environment Variables" topic in the Administering Node Manager for
Oracle WebLogic Server.
After starting Node Manager with JSSE enabled, you must start the Administration
Server and Managed Servers with JSSE enabled. For more information, see the "Using
Applying the Latest Oracle Fusion Middleware Patch Set 3-17
Verifying Your Patch Set Installation
the JSSE-Enabled SSL Implementation" topic in Administering Security for Oracle
WebLogic Server.
For more information, see Section 5.1.1, "Starting the Servers".
If you are upgrading a WebCenter Content or IBR deployment
that is integrated with Oracle SOA or BAM, see Section 5.13.5,
"Starting Oracle WebCenter Content Server with SOA or BAM".
Note:
Procedures for starting and stopping Oracle Fusion Middleware, including the
Administration Server, Managed Servers, and components are provided in "Starting
and Stopping Oracle Fusion Middleware" in Oracle Fusion Middleware Administrator's
Guide.
Once the servers are restarted, you may need to clear your
browser cache. See your internet browser documentation for
information on clearing cache.
Note:
3.9 Verifying Your Patch Set Installation
After you have successfully patched your environment, you can verify the status of
your installation by performing any combination of the following:
■
Verifying the Upgrade Log
■
Verifying the Domain Server Logs
■
Verifying OPMN Status
■
Checking Browser URLs
3.9.1 Verifying the Upgrade Log
View the log file located in the MW_HOME/oracle_common/upgrade/logs (on UNIX
operating systems) or MW_HOME\oracle_common\upgrade\logs (on Windows operating
systems) directory for details about the upgrade.
3.9.2 Verifying the Domain Server Logs
Check the domain server logs, which are located in the servers directory inside the
domain home directory. For example, on UNIX systems:
MW_HOME/user_projects/domains/domain_name/servers/server_name
On Windows systems:
MW_HOME\user_projects\domains\domain_name\servers\server_name
3.9.3 Verifying OPMN Status
Run the opmnctl status command from the INSTANCE_HOME/bin (on UNIX operating
systems) or INSTANCE_HOME\bin (on Windows operating systems) directory in your
instance home location. The example below shows the output on a UNIX system:
> ./opmnctl status
Processes in Instance: asinst_1
---------------------------------+--------------------+---------+--------3-18 Oracle Fusion Middleware Patching Guide
Verifying Your Patch Set Installation
ias-component
| process-type
|
pid | status
---------------------------------+--------------------+---------+--------emagent_asinst_1
| EMAGENT
|
11849 | Alive
wc1
| WebCache-admin
|
11333 | Alive
wc1
| WebCache
|
11332 | Alive
ohs1
| OHS
|
11207 | Alive
This information shows the components configured for this installation. The status
"Alive" means the component is up and running.
You can also run the opmnctl status -l command to obtain a list of ports used by the
components. The example below shows the output on a UNIX system:
> ./opmnctl status -l
Processes in Instance: asinst_1
---------------------------------+--------------------+---------+----------+-----------+----------+-----------+-----ias-component
| process-type
|
pid | status |
uid | memused |
uptime | ports
---------------------------------+--------------------+---------+----------+-----------+----------+-----------+-----emagent_asinst_1
| EMAGENT
|
11849 | Alive
|
1133259606 |
4204 |
0:09:38 | N/A
wc1
| WebCache-admin
|
11333 | Alive
|
1133259605 |
43736 |
0:15:35 | http_admin:8091
wc1
| WebCache
|
11332 | Alive
|
1133259604 |
63940 |
0:15:35 | http_stat:8092,http_invalidation:8093,https_
listen:8094,http_listen:8090
ohs1
| OHS
|
11207 | Alive
|
1133259603 |
50744 |
0:15:43 | https:8889,https:8890,http:8888
3.9.4 Checking Browser URLs
Verify that you can access your installed and configured products, as shown in
Table 3–4:
Table 3–4
Installed Product URLs
Product or Component
URL
Administration Server Console
http://host:port/console
Enterprise Manager Console
http://host:port/em
Enterprise Manager Agent
http://host:port/emd/main
Oracle Portal
http://host:port/portal/pls/portal
Oracle Forms
http://host:port/forms/frmservlet
Oracle Reports
http://host:port/reports/rwservlet
Oracle Discoverer Viewer
http://host:port/discoverer/viewer
Oracle Business Process Manager
(BPM) Composer
http://host:port/bpm/composer
Oracle Universal Content
Management
http://administration_server_host:cs_port/cs
Oracle Universal Records
Management
http://administration_server_host:urm_port/urm
Oracle Inbound Refinery
http://administration_server_host:ibr_port/ibr
Applying the Latest Oracle Fusion Middleware Patch Set 3-19
Verifying Your Patch Set Installation
Table 3–4 (Cont.) Installed Product URLs
Product or Component
URL
Oracle Information Rights
Management
http://administration_server_host:irm_port/irm_
rights
http://administration_server_host:cs_port/irm_
desktop
Oracle Imaging and Process
Management
http://administration_server_host:ipm_
port/imaging
Oracle WebCenter Portal
http://host:port/webcenter
Oracle WebCenter Portal's Discussion http://host:port/owc_discussions
Server
Oracle Portlet Producers
http://host:port/portalTools
http://host:port/wsrp-tools
Oracle WebCenter Pagelet Producer
http://host:port/pagelets/admin
Oracle WebCenter Activity Graph
Engines
http://host:port/activitygraph-engines
Oracle WebCenter Personalization
http://host:port/wcps/api/property/resourceInde
x
http://host:port/wcps/api/conductor/resourceInd
ex
Oracle WebCenter Analytics
Collector
http://host:port/collector/analytics-collectordiagnostics.jsp
Oracle WebCenter Enterprise
Capture Workspace Console
http://host:port/dc-console
Oracle WebCenter Enterprise
Capture Client
http://host:port/dc-client
For more information about Oracle WebCenter Portal
components, see the section "Getting Started with Oracle WebCenter
Portal Components" in Oracle Fusion Middleware Installation Guide for
Oracle WebCenter Portal.
Note:
3-20 Oracle Fusion Middleware Patching Guide
4
Upgrading Your Schemas with Patch Set
Assistant
4
This chapter describes how to upgrade the database schemas of Oracle Fusion
Middleware components by using Patch Set Assistant.
[4]
The Patch Set Assistant is used to upgrade the database schemas of Oracle Fusion
Middleware components. The schemas that are valid for upgrading with the Patch Set
Assistant must meet one of the following criteria:
■
The schema was created in an 11g release using the Repository Creation Utility
(RCU).
Or:
■
The schema was upgraded from 10g to 11g using the Upgrade Assistant.
■If you are upgrading Oracle Identity and Access Management
components, such as Oracle Access Manager, Oracle Adaptive
Access Manager or Oracle Identity Manager, see "Oracle Fusion
Middleware Upgrade Guide for Oracle Identity and Access
Management".
Note:
■
■
The Patch Set Assistant does not upgrade schemas that are in
customer databases, which includes any database that has not
been upgraded using the Upgrade Assistant (UA), Repository
Creation Utility (RCU), or Patch Set Assistant (PSA).
If you are an Oracle Portal user, note that the Oracle Portal schema
can, in certain circumstances, be installed in a customer database.
For more information, refer to Section 4.3, "Special Instructions for
Standalone Oracle Portal Repository Schemas".
In most cases, the Patch Set Assistant upgrades 11g Release 1 schema versions starting
at 11.1.1.2.0 to version 11.1.1.9.0. See Table 4–1 for specific information.
If your existing schema version is 11.1.1.1.0, you must migrate to version 11.1.1.2.0
before you can run the Patch Set Assistant. See Appendix C, "Using Patch Assistant to
Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)" for more information.
If you want to create new schemas or drop the existing schemas, you must use the
Repository Creation Utility (RCU). Information is provided in Oracle Fusion Middleware
Repository Creation Utility User's Guide.
Upgrading Your Schemas with Patch Set Assistant
4-1
Creating a Non-SYSDBA User to Upgrade Schemas
Before you attempt to upgrade to 11.1.1.9.0, check the Oracle
Fusion Middleware compatibility matrix to ensure that all the
components in the domain are supported to interoperate with Oracle
Fusion Middleware 11.1.1.9.0 components. If you have components in
the domain that are not compatible, the upgrade should not be
attempted.
Note:
For more information, see Section 3.4.1, "Reviewing System
Requirements and Certification" and the Oracle Fusion Middleware
Interoperability and Compatibility Guide.
This chapter includes the following topics:
■
Creating a Non-SYSDBA User to Upgrade Schemas
■
Which Schemas Need to be Upgraded with Patch Set Assistant?
■
Special Instructions for Standalone Oracle Portal Repository Schemas
■
Before You Begin Using the Patch Set Assistant
■
Running the Patch Set Assistant
■
Patch Set Assistant Log Files
4.1 Creating a Non-SYSDBA User to Upgrade Schemas
Oracle recommends that you create a user with the privileges required to upgrade the
schemas. The privileges listed below must be granted before starting the Patch Set
Assistant.
In the following example, "FMW" is the user created to run the Patch Set Assistant and
"welcome1" is the password. Make sure that you specify your actual user name and
password when granting privileges.
create user FMW identified by welcome1;
grant dba to FMW;
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
execute on DBMS_LOB to FMW with grant option;
execute on DBMS_OUTPUT to FMW with grant option;
execute on DBMS_STATS to FMW with grant option;
execute on sys.dbms_aq to FMW with grant option;
execute on sys.dbms_aqadm to FMW with grant option;
execute on sys.dbms_aqin to FMW with grant option;
execute on sys.dbms_aqjms to FMW with grant option;
execute on sys.dbms_aqadm to FMW with grant option;
execute on sys.dbms_aq to FMW with grant option;
execute on utl_file to FMW with grant option;
execute on dbms_lock to FMW with grant option;
select on sys.V_$INSTANCE to FMW with grant option;
select on sys.GV_$INSTANCE to FMW with grant option;
select on sys.V_$SESSION to FMW with grant option;
select on sys.GV_$SESSION to FMW with grant option;
select on dba_scheduler_jobs to FMW with grant option;
select on dba_scheduler_job_run_details to FMW with grant option;
select on dba_scheduler_running_jobs to FMW with grant option;
select on dba_aq_agents to FMW with grant option;
execute on sys.DBMS_SHARED_POOL to FMW with grant option;
select on dba_2pc_pending to FMW with grant option;
4-2 Oracle Fusion Middleware Patching Guide
Which Schemas Need to be Upgraded with Patch Set Assistant?
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
grant
select on dba_pending_transactions to FMW with grant option;
execute on DBMS_FLASHBACK to FMW with grant option;
execute on dbms_crypto to FMW with grant option;
execute on DBMS_REPUTIL to FMW with grant option;
execute on dbms_job to FMW with grant option;
select on pending_trans$ to FMW with grant option;
select on dba_scheduler_job_classes to fmw with grant option;
select on SYS.DBA_DATA_FILES to FMW with grant option;
select on SYS.V_$ASM_DISKGROUP to FMW with grant option;
select on v$xatrans$ to FMW with grant option;
execute on sys.dbms_system to FMW with grant option;
execute on DBMS_SCHEDULER to FMW with grant option;
select on dba_data_files to FMW with grant option;
execute on UTL_RAW to FMW with grant option;
execute on DBMS_XMLDOM to FMW with grant option;
execute on DBMS_APPLICATION_INFO to FMW with grant option;
execute on DBMS_UTILITY to FMW with grant option;
execute on DBMS_SESSION to FMW with grant option;
execute on DBMS_METADATA to FMW with grant option;
execute on DBMS_XMLGEN to FMW with grant option;
execute on DBMS_DATAPUMP to FMW with grant option;
execute on DBMS_MVIEW to FMW with grant option;
execute on ALL_ENCRYPTED_COLUMNS to FMW with grant option;
Note: 11.2.0.3 Database Users ONLY: You must apply Oracle Patch
13036331 before you begin the upgrade. Go to My Oracle Support to
download the patch.
If you do not apply this patch, then you will have to grant additional
privileges for some schemas. Table 4–1 describes the privileges you
will need to grant.
4.2 Which Schemas Need to be Upgraded with Patch Set Assistant?
The component schemas available for upgrade in Table 4–1 (default names shown) can
be upgraded with the Patch Set Assistant in order to upgrade them to 11g Release 1
(11.1.1.9.0).
The Schema(s) column in Table 4–1 shows the default schema
name format of prefix and schema name separated by an underscore
(_) character. The default prefix is DEV, but you may have created new
prefixes for your schemas while using the RCU.
Note:
Important Notes About the Schemas That Need to Be Upgraded:
■
Some schema upgrades require advanced privileges. Make sure that you grant the
appropriate privileges to the DBA user before you upgrade the schemas. Table 4–1
describes the specific privileges required for each schema.
■
■
Applying the Release 1 (11.1.1.9.0) patch set will only upgrade schemas listed in
Table 4–1. Some component schemas will not be upgraded and will remain at
their original schema version.
The WebCenter and Oracle Enterprise Content Management Suite component
names shown in Table 4–1 are the new component names that were changed as of
Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0).
Upgrading Your Schemas with Patch Set Assistant
4-3
Which Schemas Need to be Upgraded with Patch Set Assistant?
For more information, see Section 6.1, "New Product Names for Oracle WebCenter
and Oracle Enterprise Content Management Suite".
■
Table 4–1
Component
Name
Audit
Services
When upgrading _OPSS schemas from a previous release, it is important to note
that OPSS audit data will now be stored in IAU common tables instead of the JPS
table. Any existing data in the JPS table can remain unchanged for reporting or
auditing purposes, and there is no need to upgrade JPS table with extra columns.
Schemas That Require Upgrading for the Latest Release
Schema(s)
Schema
Schema Version Version After
Before Upgrade Upgrade
Dependencies
prefix_IAU
11.1.1.2.0
11.1.1.9.0
None.
11.1.1.9.0
None.
11.1.1.9.0
The prefix_MDS schema must be
upgraded first.
11.1.1.9.0
None.
11.1.1.6.0
None.
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Metadata
Services
prefix_MDS
11.1.1.2.0
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Oracle
Enterprise
Scheduler
Service
prefix_ESS
11.1.1.2.0
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Oracle
Platform
Security
Services
prefix_OPSS
11.1.1.2.0
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Oracle Portal1 prefix_PORTAL
11.1.1.2.0
11.1.1.3.0
11.1.1.4.0
11.1.1.6.0
4-4 Oracle Fusion Middleware Patching Guide
Which Schemas Need to be Upgraded with Patch Set Assistant?
Table 4–1 (Cont.) Schemas That Require Upgrading for the Latest Release
Component
Name
Oracle
Internet
Directory
Schema(s)
Schema
Schema Version Version After
Before Upgrade Upgrade
ODS
11.1.1.2.0
NOTE: The Oracle
Internet Directory
schema (ODS) cannot
be prepended with a
custom prefix.
11.1.1.3.0
11.1.1.9.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Dependencies
11.2.0.3 Database Users ONLY: This
schema requires that you apply Oracle
Patch 13036331 before you begin the
upgrade. Go to My Oracle Support to
download the patch. If you do not apply
the patch you must grant these
additional privileges:
grant execute on sys.dbms_reputil
to ODS;
grant execute on sys.dbms_reptuil
to SYSTEM with grant option;
grant execute on sys.dbms_job to
ods;
Oracle
Business
Intelligence
Platform
prefix_BIPLATFORM
Master and
Work
Repository
(Oracle Data
Integrator)
prefix_ODI_REPO
11.1.1.3.0
11.1.1.9.0
The prefix_MDS schema must be
upgraded first.
11.1.1.9.0
None.
11.1.1.9.0
The prefix_MDS schema must be
upgraded first.
11.1.1.7.0
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
SOA
Infrastucture
prefix_SOAINFRA
11.1.1.2.0
11.1.1.3.0
11.2.0.3 Database Users ONLY: This
schema requires that you apply Oracle
Patch 13036331 before you begin the
upgrade. Go to My Oracle Support to
download the patch. If you do not apply
the patch you must grant these
additional privileges:
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
grant execute on utl_file to
&&soa_user
WebCenter
Portal
(previously
WebCenter
Spaces)
prefix_WEBCENTER
11.1.1.2.0
11.1.1.8.0
The prefix_MDS schema must be
upgraded first.
11.1.1.8.0
None.
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Discussions
(WebCenter
Suite)
prefix_DISCUSSIONS 11.1.1.2.0
11.1.1.4.0
11.1.1.7.0
Upgrading Your Schemas with Patch Set Assistant
4-5
Special Instructions for Standalone Oracle Portal Repository Schemas
Table 4–1 (Cont.) Schemas That Require Upgrading for the Latest Release
Component
Name
Discussions
Crawler2
Schema(s)
prefix_
DISCUSSIONS_
CRAWLER
Schema
Schema Version Version After
Before Upgrade Upgrade
11.1.1.2.0
Dependencies
11.1.1.9.0
The prefix_DISCUSSIONS schema must
be upgraded first.
11.1.1.8.0
None.
11.1.1.8.0
None.
11.1.1.9.0
None.
11.1.1.4.0
11.1.1.7.0
11.1.1.8.0
Activity
Graph and
Analytics
prefix_ACTIVITIES
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
Oracle
Universal
Records
Management
11g
prefix_URMSERVER
Oracle
Content
Server 11g Complete
prefix_OCS
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
11.1.1.8.0
Oracle
Universal
Content
Management
prefix_OCSSEARCH
11.1.1.4.0
11.1.1.8.0
11.1.1.5.0
11.1.1.7.0
Oracle Secure prefix_SEARCHSYS
Enterprise
Search
11.2.1
11.2.2
The prefix_ESS must be upgraded first.
Oracle User
Messaging
Service
11.1.1.2.0
11.1.1.9.0
11.2.0.3 Database Users ONLY: This
schema requires that you apply Oracle
Patch 13036331 before you begin the
upgrade. Go to My Oracle Support to
download the patch. If you do not apply
the patch you must grant these
additional privileges:
prefix_ORASDPM
11.1.1.3.0
11.1.1.4.0
11.1.1.5.0
11.1.1.6.0
11.1.1.7.0
1
2
grant execute on sys.dbms_aqjms to
&&user
A schema upgrade is not required if Oracle Portal 11.1.1.6.0 has already been installed. 11.1.1.6.0 is the latest version of Oracle
Portal.
If the Discussions Crawler schema has not previously been installed using RCU, then migrating Discussions will automatically
install the Discussions Crawler schema, assigning the same password as the Discussions schema. If you then attempt to upgrade
the Discussions Crawler schema individually, the Patch Set Assistant will warn that the schema has already been upgraded.
4.3 Special Instructions for Standalone Oracle Portal Repository
Schemas
If you are using an Oracle Portal repository stored outside of the OracleAS Metadata
Repository (any database that has not used the Upgrade Assistant, Repository
Creation Utility, or Patch Set Assistant), then do not use the Patch Set Assistant to
upgrade the Portal schemas in the repository. Instead, refer to "Upgrading an Oracle
4-6 Oracle Fusion Middleware Patching Guide
Before You Begin Using the Patch Set Assistant
Portal Repository in a Customer Database" in Oracle Fusion Middleware Upgrade Guide
for Oracle Portal, Forms, Reports, and Discoverer.
4.4 Before You Begin Using the Patch Set Assistant
This section contains information about things you should check before you run the
Patch Set Assistant:
■
Section 4.4.1, "Verify that the Java Development Kit (JDK) Version is Supported
and Certified with Oracle Fusion Middleware 11g (11.1.1.9)"
■
Section 4.4.2, "Upgrade Oracle WebLogic Server and Apply Mandatory Patches"
■
Section 4.4.3, "Back Up Your Database and Database Schemas"
■
Section 4.4.4, "Check Your Database and Schemas"
■
■
Section 4.4.5, "Create an Edition on the Database Server for Editions-Based
Redefinition"
Section 4.4.6, "Shut Down All Components Using the Schemas You Want to
Upgrade"
■
Section 4.4.7, "Check the aq_tm_processes Value for Oracle Portal"
■
Section 4.4.8, "Setting ORACLE_HOME and JAVA_HOME Environment Variables"
4.4.1 Verify that the Java Development Kit (JDK) Version is Supported and Certified
with Oracle Fusion Middleware 11g (11.1.1.9)
This release of Oracle Fusion Middleware requires a 64-bit JDK 7 (1.7.x), which can be
downloaded at the following URL:
http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880
260.html.
JRockit Users: JRockit is no longer supported. You must install
the Sun JDK to use with this release.
Note:
For up to date supported configuration information, see Oracle Fusion
Middleware Supported System Configurations at:
http://www.oracle.com/technetwork/middleware/ias/downloads/f
usion-certification-100350.html.
For more information about JDK version requirements, see the "Oracle WebLogic
Server and JDK Considerations" topic in the Oracle Fusion Middleware System
Requirements and Specifications for Oracle Fusion Middleware 11g Release 1 (11.1.1.9)
document.
For more information about using JDK 7 with this release of Oracle Fusion
Middleware, see "Using WebLogic Server with JDK 7" in Installing and Configuring
Oracle WebLogic Server and Coherence.
Before an upgrade, always consult the System Requirements and Supported Platforms for
Oracle Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported
System Configurations page for supported JDK versions.
Upgrading Your Schemas with Patch Set Assistant
4-7
Before You Begin Using the Patch Set Assistant
Make sure that you update the setDomainEnv script file to
point to the upgraded JDK version. See Updating the setDomainEnv
Script File with Upgraded JDK Location.
Note:
4.4.2 Upgrade Oracle WebLogic Server and Apply Mandatory Patches
Make sure that you have applied the mandatory patches for Oracle WebLogic Server
before you begin the patching process. For more information, see Upgrading Oracle
WebLogic Server and Applying Required WebLogic Server Patches.
Note: The WebLogic domain must be upgraded to 10.3.6 before
applying the WebLogic Server patches.
Some Oracle WebLogic Server patches require additional post-patching tasks before
starting the servers. For more information, see the Oracle Fusion Middleware Download,
Installation, and Configuration ReadMe Files for Oracle WebLogic Server.
4.4.3 Back Up Your Database and Database Schemas
Make sure you have backed up your existing database and database schemas before
you run the Patch Set Assistant, as instructed in Section 3.4.5, "Backing Up Your
Database and Database Schemas".
4.4.4 Check Your Database and Schemas
Before running Patch Set Assistant, you should check to make sure that your database
is up and running and that the schemas you want to upgrade are at versions that are
supported for upgrade. If you are using an Oracle database, connect to the database as
SYS and run the following from SQL*Plus:
SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
If the number in the "VERSION" column is 11.1.1.2.0 or greater, then the schema is
supported for upgrade.
If you are using an Oracle database, you should recompile database objects before
running the Patch Set Assistant to check for invalid objects before the upgrade.
Connect to the database as SYS and run the following from SQL*Plus:
/rdbms/admin/utlrp.sql
Caution: If you are running Oracle database 11g (11.2.0.3), you must
first patch the database to enable advanced privileges when
upgrading select schemas. Table 4–1 describes the specific privileges
required for each schema.
After running utlrp.sql, and before you upgrade your schema, issue the following
query to ensure there are no longer any invalid database objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
Take note of any invalid objects. The existence of invalid database objects may prevent
the upgrade from completing successfully.
4-8 Oracle Fusion Middleware Patching Guide
Before You Begin Using the Patch Set Assistant
To recompile just the objects that belong to a single Oracle Fusion Middleware schema,
you can use the Oracle Database stored procedure dbms_utility.compile_schema as
shown in the example below:
SQL> execute
dbms_utility.compile_schema('DEV_SOAINFRA');
PL/SQL procedure successfully completed
4.4.5 Create an Edition on the Database Server for Editions-Based Redefinition
Edition-based redefinition (EBR) enables you to support multiple versions of a
database schema on the same database and at the same time.
When using the Patch Set Assistant, the database type Oracle
Database enabled for editions-based redefinition should only be
selected when editions created in the EBR database require an
upgrade. If this is not the intent, select Oracle Database.
Note:
EBR is not available for all Oracle Fusion Middleware components,
therefore the EBR database option may not be available.
Before upgrading an EBR-enabled schema from FMW 11.1.1.7.0 release to 11.1.1.9.0,
you must connect to the database server and create an edition on the database server
for the 11.1.1.9.0 release. The new edition for 11.1.1.9.0 must be a child of your previous
edition.
To create an edition on the database server, log in as SYS (or another Oracle user that
has DBA privileges) and use the following command:
SQL> create edition Oracle_FMW_11_1_1_9_0 as child of Oracle_FMW_11_1_1_7_0;
Edition created.
Note that in the code example above, 'Oracle_FMW_11_1_1_7_0' is used as an example
of the edition name you specified in RCU 11.1.1.7.0 when the 11.1.1.7.0 schemas were
created. Be sure to provide the actual name used when creating the edition.
After you have created the schemas and before you create the domain, you must
specify that the new schema is to be used as the default edition using the following
command:
ALTER DATABASE DEFAULT EDITION = edition_name;
4.4.6 Shut Down All Components Using the Schemas You Want to Upgrade
Before running Patch Set Assistant, shut down all Oracle Fusion Middleware
components (including the Managed Server and Oracle instances) that may be using
the schemas you want to upgrade. There should be no Oracle Fusion Middleware
components connected to the database while schemas are being upgraded.
4.4.7 Check the aq_tm_processes Value for Oracle Portal
If you are running the Patch Set Assistant for the Oracle Portal schema on an Oracle
database, make sure that the aq_tm_processes value in your database is greater than
0. To check, use the following command after connecting to the database:
show parameter aq_tm_processes;
Upgrading Your Schemas with Patch Set Assistant
4-9
Running the Patch Set Assistant
If the value returned is 0, use the following command to change the value to 1:
alter system set aq_tm_processes=1 scope=both;
4.4.8 Setting ORACLE_HOME and JAVA_HOME Environment Variables
You may need to set or modify your environment variables in the following scenarios:
■
■
If you are running the Patch Set Assistant with an Oracle WebLogic Server, and
the environment variables ORACLE_HOME or JAVA_HOME have been set on
either UNIX or Windows operating systems, then you must remove these
variables prior to running Patch Set Assistant. In some cases if you run the Patch
Set Assistant with these variables already set, then the PSA may not run properly.
If you are running the Patch Set Assistant and your install does not contain an
Oracle WebLogic Server (standalone) or Java files, you must set the JAVA_HOME
environment variable. PSA may not be able to detect the location of the required
Java files without setting this variable.
4.5 Running the Patch Set Assistant
The following sections describe how to run the Patch Set Assistant when you are
installing the Oracle Fusion Middleware 11g Release 1 (11.1.1.9.0) patch set:
■
Section 4.5.1, "Using the Patch Set Assistant Graphical Interface"
■
Section 4.5.2, "Using the Patch Set Installer from the Command Line"
■
Section 4.5.3, "Verifying the Schema Version Number After Upgrade"
■
Section 4.5.4, "Checking for Invalid Database Objects"
4.5.1 Using the Patch Set Assistant Graphical Interface
The Patch Set Assistant is installed into the bin directory in the Oracle Home by the
Product or Patch Set Installer.
You can use the Patch Set Assistant to patch any component schema in the
Middleware home from where the Patch Set Assistant started.
To start Patch Set Assistant, go to the bin directory in the Oracle Home, then run the
following command:
On UNIX operating systems:
cd Oracle_Home/bin
./psa [-logLevel <log_level>] [-logDir <log_directory>]
On Windows operating systems:
CD Oracle_Home\bin
psa.bat [-logLevel <log_level>] [-logDir <log_directory>]
Follow the instructions in Table 4–2 to use the Patch Set Assistant to upgrade your
schemas.
4-10 Oracle Fusion Middleware Patching Guide
Running the Patch Set Assistant
Note: Table 4–2 describes only the common Patch Set Assistant
screens - standard screens that appear for all components. Your
environment may have components that require additional
component-specific screens. For more information on the
component-specific screens, click Help on the screen to access the
online help
If you need additional help with any of the screens, refer to
Appendix B, "Patch Set Assistant Screens".
Table 4–2
Patch Set Assistant Screens
Screen
Description
Welcome
This page introduces you to the Patch Set Assistant.
Select Component
Select the single top-level component you want to upgrade. You
may only upgrade one component at a time.
NOTE: If you are upgrading from Release 11.1.1.2.0 or 11.1.1.3.0,
the prefix_ACTIVITIES schema will not be available in your
environment as this schema was not introduced until Release
11.1.1.4.0. Make sure you de-select this schema from the
WebCenter Portal component; otherwise the Patch Set Assistant
will ask for credentials for this schema.
Prerequisites
Verify that you have satisfied the database prerequisites.
Schema Database
Credentials
Use this screen to specify database connection credentials and
schema information for upgrade. You can select the schema
name from the drop-down list of available schemas.
Examine
This page displays the status of the Patch Set Assistant as it
examines each component schema. Verify that your schemas
have a "succeeded" or "already upgraded" indicator in the Status
column.
Upgrade Summary
Verify that the schemas listed to be upgraded are the ones you
expect.
Upgrade Progress
This screen shows the progress of the schema upgrade.
Upgrade Success
This screen shows the final status of the upgrade and the
location of the log file.
4.5.2 Using the Patch Set Installer from the Command Line
Use the following syntax to perform upgrades using the command line interface (CLI):
cd Oracle_Home/bin
psa -response <response_file> [-logLevel <log_level>] [-logDir <log_directory>]
See Table 4–3 for descriptions of these parameters.
Upgrading Your Schemas with Patch Set Assistant 4-11
Running the Patch Set Assistant
Table 4–3
Patch Set Assistant Command Line Parameters
Parameter
Required or
Optional
Parameter?
-response
Required.
Description
The full path and name of the file containing inputs
required to perform an upgrade.
To generate the response file used with the -response
parameter, you should run the Patch Set Assistant GUI
(Section 4.5.1, "Using the Patch Set Assistant Graphical
Interface").
NOTE: When Patch Set Assistant is run in -reponse file
mode it will not upgrade any schemas that return "already
upgraded" during the Schema Database Credentials phase.
These schemas will skip the upgrade phase entirely. This
applies only when Patch Set Assistant is run in -response
file mode.
-logLevel
Optional.
Logging level. Select one of the following:
■
TRACE
■
NOTIFICATION
■
WARNING
■
ERROR
■
INCIDENT_ERROR
The default logging level is NOTIFICATION.
-logDir
Optional.
Name of an existing, writable directory where PSA will
create log files and temporary files.
Default location is MW_HOME/oracle_
common/upgrade/logs
-help
Optional.
View all of the command line options.
4.5.3 Verifying the Schema Version Number After Upgrade
You can use the SQL command below to verify that the schema version in schema_
version_registry has been properly upgraded:
SELECT OWNER, VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY;
Check that the number in the "VERSION" column matches the latest version number
for that schema. See Table 4–1 to verify that the upgraded version number is correct for
your schema.
If the status appears as "INVALID" then the schema upgrade failed. You should
examine the logs files to determine the reason for the failure. For more information, see
Section 4.6, "Patch Set Assistant Log Files".
4.5.4 Checking for Invalid Database Objects
If you are using an Oracle database, you should recompile database objects after
running the Patch Set Assistant by connecting to the database as SYS and running the
following from SQL*Plus:
SQL> /rdbms/admin/utlrp.sql
This will compile the database objects that were upgraded by Patch Set Assistant.
4-12 Oracle Fusion Middleware Patching Guide
Patch Set Assistant Log Files
Then issue the following query to ensure there are no longer any invalid database
objects:
SELECT owner, object_name FROM all_objects WHERE status='INVALID';
None of the database objects for the upgraded schema should be invalid at this point.
If there are any, run the utlrp.sql command again and check again. If the problem
persists, you should file a service request.
4.6 Patch Set Assistant Log Files
The Patch Set Assistant writes log files to the following locations:
On UNIX operating systems:
MW_HOME/oracle_common/upgrade/logs/psatimestamp.log
On Windows operating systems:
MW_HOME\oracle_common\upgrade\logs\psatimestamp.log
Some components will create a second log file called psatimestamp.out, also in the
same location.
The timestamp will reflect the actual date and time that Patch Set Assistant was run.
Should any failures occur when running Patch Set Assistant, these log files will be
needed to help diagnose and correct the problem; do not delete them. You can alter the
contents of your log files by specifying a different -logLevel from the command line.
Some of the operations performed by the Patch Set Assistant may take longer to
complete than others. If you want to see the progress of these long operations, you can
see this information in the log file, or you can use the following query:
SELECT VERSION, STATUS, UPGRADED FROM SCHEMA_VERSION_REGISTRY WHERE OWNER='schema_
name';
In the query results, the STATUS field will be either "UPGRADING" or "UPGRADED"
during the schema patching operation, and will become "VALID" when the operating
is finished.
Upgrading Your Schemas with Patch Set Assistant 4-13
Patch Set Assistant Log Files
4-14 Oracle Fusion Middleware Patching Guide
5
Post-Patching Procedures
5
This chapter contains information about manual tasks performed after the Release
11.1.1.9.0 patch installation is complete. Some of the tasks may not apply to your
environment as you may not be using the products in question.
[5]
The post-patching tasks described in this chapter are not
required for all environments or upgrade paths.
NOTE:
Consult the Release Starting Point table for your existing environment
to determine which tasks apply.
If you are patching WebCenter Portal, see Section 6.10, "Post Patching
Tasks for Oracle WebCenter Portal".
This chapter includes the following topics:
■
Section 5.1, "General Post-Patching Tasks"
■
Section 5.2, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.2"
■
Section 5.3, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.3"
■
Section 5.4, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.4"
■
Section 5.5, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.5"
■
Section 5.6, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.6"
■
Section 5.7, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.7"
■
Section 5.8, "Post-Patching Tasks If Your Starting Point is Release 11.1.1.8"
5.1 General Post-Patching Tasks
Most components requires some post-patching configuration tasks. Review the
common post-patching tasks in this section to determine if your upgraded
environment requires any additional configurations.
■
Starting the Servers
5.1.1 Starting the Servers
To start the WebLogic Administration Server and the Managed Server(s), refer to the
following sections:
■
Starting the Node Manager
■
Starting the WebLogic Administration Server
Post-Patching Procedures
5-1
General Post-Patching Tasks
■
Starting the Managed Server(s)
You must start the Node Manager, the WebLogic
Administration Server, and the Managed Servers with Java Secure
Socket Extension (JSSE) enabled, if you have applied the following
Oracle WebLogic Server patches to your Middleware home:
Note:
■
13964737 (YVDZ)
■
14174803 (IMWL)
These patches are available from My Oracle Support.
For information on how to start the Node Manager with JSSE enabled,
see the "Set the Node Manager Environment Variables" topic in the
Administering Node Manager for Oracle WebLogic Server.
After starting Node Manager with JSSE enabled, you must start the
Administration Server and Managed Servers with JSSE enabled. For
more information, see the "Using the JSSE-Enabled SSL
Implementation" topic in Administering Security for Oracle WebLogic
Server.
5.1.1.1 Starting the Node Manager
To start the Node Manager, you must run the command startNodeManager.sh (on
UNIX) or startNodeManager.cmd (on Windows) from the location $WL_
HOME/server/bin.
For more information, see "startNodeManager" in the Oracle Fusion Middleware
WebLogic Scripting Tool Command Reference.
5.1.1.2 Starting the WebLogic Administration Server
To start the WebLogic Administration Server, do the following:
On UNIX:
Run the following commands:
cd MW_HOME/user_projects/domains/domain_name/bin
./startWebLogic.sh
On Windows:
Run the following commands:
cd MW_HOME\user_projects\domains\domain_name\bin
startWebLogic.cmd
5.1.1.3 Starting the Managed Server(s)
To start the Managed Server(s), do the following:
On UNIX:
1.
Move from your present working directory to the MW_HOME/user_
projects/domains/domain_name/bin directory by running the following
command on the command line:
cd MW_HOME/user_projects/domains/domain_name/bin
2.
Run the following command to start the Managed Servers:
5-2 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks If Your Starting Point is Release 11.1.1.2
./startManagedWebLogic.sh managed_server_name admin_url admin_username
password
where
managed_server_name is the name of the Managed Server
admin_url is URL of the administration console. Specify it in the format
http://host:port/console. Specify only if the WebLogic Administration Server is
on a different computer.
admin_username is the username of the WebLogic Administration Server.
password is the password of the WebLogic Administration Server.
For example:
./startManagedWebLogic.sh soa_server1 http://host.example.com:7001/console
weblogic password123
On Windows:
1.
Move from your present working directory to the MW_HOME\user_
projects\domains\domain_name\bin directory by running the following
command on the command line:
cd MW_HOME\user_projects\domains\domain_name\bin
2.
Run the following command to start the Managed Servers:
startManagedWebLogic.cmd managed_server_name admin_url admin_username
password
where
managed_server_name is the name of the Managed Server.
admin_url is URL of the administration console. Specify it in the format
http://host:port/console. Specify only if the WebLogic Administration Server is
on a different computer.
admin_username is the username of the WebLogic Administration Server.
password is the password of the WebLogic Administration Server.
For example:
startManagedWebLogic.cmd soa_server1 http://host.example.com:7001/console
weblogic password123
5.2 Post-Patching Tasks If Your Starting Point is Release 11.1.1.2
Table 5–1 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.2.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Post-Patching Procedures
5-3
Post-Patching Tasks If Your Starting Point is Release 11.1.1.2
Table 5–1
Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0
Product Area
Documentation
System and Identity Management Components
Patch any system component(s) associated with a
WebLogic Server domain.
Section 5.9.1, "Upgrading System Components"
Oracle Internet Directory, if you plan to add more than
one million entries.
Section 5.9.4, "Adding Datafiles to the OLTS_CT_STORE
and OLTS_ATTRSTORE Tablespaces for Oracle Internet
Directory"
Oracle Configuration Manager for Oracle Portal, Forms, Section 5.9.2, "Upgrading Oracle Configuration
Manager"
Reports and Discoverer (Windows operating system
only).
Oracle Reports and Oracle Portal.
Section 5.9.3, "Resolving JDBC Errors in Oracle Reports
and Oracle Portal"
Section 5.11.6, "Upgrading the Plug-In Configuration
When Using a Proxy with WebLogic Server"
Diagnostic Framework
Section 5.9.7, "Configuring Diagnostic Framework
Dump Sampling"
Oracle Identity Federation.
Section 5.10.2, "Upgrading Configuration Properties in
Oracle Identity Federation"
Oracle Identity Management Components, if you plan
to use Oracle Enterprise Manager to view metrics and
configuration settings.
Section 5.10.3, "Using Oracle Enterprise Manager to
View Oracle Identity Management Metrics and
Configuration Settings"
Oracle WebCenter
Patching procedures for either a Release 11.1.1.2.0 or
11.1.1.3.0 installation.
Section 6.6, "Patching an Oracle WebCenter 11.1.1.2.0 or
11.1.1.3.0 Installation"
WebLogic Server Domain
Shared Libraries.
Section 5.11.1, "Upgrading Fusion Middleware Shared
Libraries"
Configurations and Stores.
Section 5.11.2, "Upgrading Configurations and Stores"
Web Services Atomic Transaction.
Section 5.11.4, "Enabling WS-AtomicTransaction"
Oracle SOA Suite
SOA Schemas and database growth.
Section 5.12.1, "Loading the Oracle SOA Suite Purge
Scripts for Database Management"
SOA Composer and BPM Workspace.
Section 5.12.2, "Removing the tmp Folder for SOA
Composer, BPM Workspace and B2B"
Oracle SOA soa-infra application.
Section 5.12.5, "Upgrading the soa-infra Application in
Warning State"
Application Policy Store.
Section 5.12.6, "Running bpm-ps6-upgrade.py to
Upgrade the Policy Store"
Policy Store and Shared Library.
Section 5.12.7, "Running soa-upgrade.py to Upgrade the
Policy Store and Deploy a Shared Library"
BAM-ODI Integration.
Section 5.12.8, "Upgrading the Oracle Data Integrator
Clients if BAM-ODI Integration is Enabled"
Oracle B2B.
Section 5.12.9, "Saving and Restoring XEngine
Customizations for Oracle B2B"
5-4 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks If Your Starting Point is Release 11.1.1.3
Table 5–1 (Cont.) Post-Patching Tasks If Your Starting Point is Release 11.1.1.2.0
Product Area
Documentation
User Messaging Service (UMS) Adapter
Section 5.12.11, "Extending the SOA Domain with UMS
Adapter Features"
Business Process Management (BPM)
Section 5.12.12, "Extending the SOA Domain with
Business Process Management Features"
Oracle Service Bus.
Section 5.14, "Post-Patching Tasks for Oracle Service
Bus"
5.3 Post-Patching Tasks If Your Starting Point is Release 11.1.1.3
Table 5–2 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.3.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Table 5–2
Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0
Product Area
Documentation
System and Identity Management Components
Patch any system component(s) associated with a
WebLogic Server domain.
Section 5.9.1, "Upgrading System Components"
Oracle Internet Directory, if you plan to add more
than one million entries.
Section 5.9.4, "Adding Datafiles to the OLTS_CT_STORE and
OLTS_ATTRSTORE Tablespaces for Oracle Internet
Directory"
Oracle Configuration Manager for Oracle Portal,
Forms, Reports and Discoverer (Windows
operating system only).
Section 5.9.2, "Upgrading Oracle Configuration Manager"
Oracle Reports and Oracle Portal.
Section 5.9.3, "Resolving JDBC Errors in Oracle Reports and
Oracle Portal"
Section 5.11.6, "Upgrading the Plug-In Configuration When
Using a Proxy with WebLogic Server"
Diagnostic Framework
Section 5.9.7, "Configuring Diagnostic Framework Dump
Sampling"
Oracle Identity Federation.
Section 5.10.2, "Upgrading Configuration Properties in
Oracle Identity Federation"
Oracle Identity Management Components, if you
plan to use Oracle Enterprise Manager to view
metrics and configuration settings.
Section 5.10.3, "Using Oracle Enterprise Manager to View
Oracle Identity Management Metrics and Configuration
Settings"
WebLogic Server Domain
Shared Libraries.
Section 5.11.1, "Upgrading Fusion Middleware Shared
Libraries"
Configurations and Stores.
Section 5.11.2, "Upgrading Configurations and Stores"
Oracle SOA Suite
SOA Schemas and database growth.
Section 5.12.1, "Loading the Oracle SOA Suite Purge Scripts
for Database Management"
SOA Composer and BPM Workspace.
Section 5.12.2, "Removing the tmp Folder for SOA Composer,
BPM Workspace and B2B"
Oracle SOA soa-infra application.
Section 5.12.5, "Upgrading the soa-infra Application in
Warning State"
Post-Patching Procedures
5-5
Post-Patching Tasks If Your Starting Point is Release 11.1.1.3
Table 5–2 (Cont.) Post-Patching Tasks If Your Starting Point is Release 11.1.1.3.0
Product Area
Documentation
Application Policy Store.
Section 5.12.6, "Running bpm-ps6-upgrade.py to Upgrade
the Policy Store"
Policy Store and Shared Library.
Section 5.12.7, "Running soa-upgrade.py to Upgrade the
Policy Store and Deploy a Shared Library"
BAM-ODI Integration.
Section 5.12.8, "Upgrading the Oracle Data Integrator Clients
if BAM-ODI Integration is Enabled"
Oracle B2B.
Section 5.12.9, "Saving and Restoring XEngine
Customizations for Oracle B2B"
User Messaging Service (UMS) Adapter
Section 5.12.11, "Extending the SOA Domain with UMS
Adapter Features"
Business Process Management (BPM)
Section 5.12.12, "Extending the SOA Domain with Business
Process Management Features"
Oracle WebCenter Content
Oracle WebCenter Content: Imaging.
Section 5.13.1, "Upgrading Oracle WebCenter Content:
Imaging"
Oracle WebCenter Content application adapters.
Section 5.13.2, "Upgrading Oracle Application Adapters for
Oracle WebCenter Content"
Report Library for Records Management in Content Section 5.13.3, "Configuring the Report Library for Records
Server.
Management in Content Server"
Inbound Refinery (IBR)
Section 5.13.4, "Using Fusion Middleware Control to Monitor
IBR"
WebCenter Content Server
Section 5.13.5, "Starting Oracle WebCenter Content Server
with SOA or BAM"
WebCenter Content System Components
Section 5.13.6, "Enabling System Components for WebCenter
Content"
Oracle Service Bus
Oracle Service Bus.
Section 5.14, "Post-Patching Tasks for Oracle Service Bus"
Oracle Business Intelligence
Oracle Business Intelligence Code Grants.
Section 5.15.2, "Upgrading Oracle Business Intelligence Code
Grants"
Oracle Business Intelligence Catalogs.
Section 5.15.3, "Upgrading Oracle BI Presentation Catalogs"
Oracle Real-Time Decisions.
Section 5.15.8, "Upgrading Oracle Real-Time Decisions"
Oracle Data Integrator
Oracle Data Integrator repository objects.
Section 5.16.1, "Finalizing Repository Patching"
Oracle Data Integrator Java EE Agent.
Section 5.16.2, "Reconfiguring the Java EE Agent"
Oracle Data Integrator Standalone Agent.
Section 5.16.3, "Reconfiguring the ODI Standalone Agent"
Oracle Enterprise Manager.
Section 5.16.4, "Reconfiguring Oracle Enterprise Manager
Properties"
Oracle Data Integrator Console.
Section 5.16.5, "Reconfiguring the ODI Console"
Oracle Data Integrator odi-sdk-ws Application.
Section 5.16.6, "Adding the Version Number for the
odi-sdk-ws Application in config.xml"
Oracle WebCenter
Patching procedures for either 11.1.1.2.0 release or
11.1.1.3.0 installation.
5-6 Oracle Fusion Middleware Patching Guide
Section 6.6, "Patching an Oracle WebCenter 11.1.1.2.0 or
11.1.1.3.0 Installation"
Post-Patching Tasks If Your Starting Point is Release 11.1.1.4
5.4 Post-Patching Tasks If Your Starting Point is Release 11.1.1.4
Table 5–3 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.4.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Table 5–3
Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0
Product Area
Documentation
System and Identity Management Components
Patch any system compoment(s) associated with a WebLogic
Server domain.
Section 5.9.1, "Upgrading System Components"
Oracle Identity Federation.
Section 5.10.2, "Upgrading Configuration
Properties in Oracle Identity Federation"
Oracle Identity Management Components, if you plan to use
Oracle Enterprise Manager to view metrics and configuration
settings.
Section 5.10.3, "Using Oracle Enterprise Manager
to View Oracle Identity Management Metrics and
Configuration Settings"
Oracle Internet Directory, if you plan to add more than one
million entries.
Section 5.9.4, "Adding Datafiles to the OLTS_CT_
STORE and OLTS_ATTRSTORE Tablespaces for
Oracle Internet Directory"
Oracle Reports and Oracle Portal.
Section 5.9.3, "Resolving JDBC Errors in Oracle
Reports and Oracle Portal"
Patch any system using a proxy module in front of WebLogic
Server
Section 5.11.6, "Upgrading the Plug-In
Configuration When Using a Proxy with
WebLogic Server"
Oracle Platform Security Services (OPSS)
Section 5.9.5, "Generating the BASE64 Encoded
Encryption Key for OPSS"
Section 5.9.6, "Enabling Dynamic Audit Metadata
Model for OPSS Running in JavaSE Mode"
Diagnostic Framework
Section 5.9.7, "Configuring Diagnostic Framework
Dump Sampling"
JRF Template for IBM WebSphere
Section 5.9.8, "Adding Batik Library Jar Files to
the JRF Template for IBM WebSphere"
Oracle SOA Suite
SOA Composer and BPM Workspace (this is only applicable if
your Release 11.1.1.4.0 software is upgraded from Release
11.1.1.3.0. If you installed and configured Release 11.1.1.4.0
from scratch then you do not need to perform this task).
Section 5.12.2, "Removing the tmp Folder for SOA
Composer, BPM Workspace and B2B"
Oracle BPEL
Section 5.12.4, "Upgrading
MAXRECOVERATTEMPT Attribute to 2"
Oracle SOA soa-infra application.
Section 5.12.5, "Upgrading the soa-infra
Application in Warning State"
Application Policy Store.
Section 5.12.6, "Running bpm-ps6-upgrade.py to
Upgrade the Policy Store"
BAM-ODI Integration.
Section 5.12.8, "Upgrading the Oracle Data
Integrator Clients if BAM-ODI Integration is
Enabled"
Oracle B2B.
Section 5.12.9, "Saving and Restoring XEngine
Customizations for Oracle B2B"
User Messaging Service (UMS) Adapter
Section 5.12.11, "Extending the SOA Domain with
UMS Adapter Features"
Post-Patching Procedures
5-7
Post-Patching Tasks If Your Starting Point is Release 11.1.1.5
Table 5–3 (Cont.) Post-Patching Tasks If Your Starting Point is Release 11.1.1.4.0
Product Area
Documentation
Business Process Management (BPM)
Section 5.12.12, "Extending the SOA Domain with
Business Process Management Features"
Oracle WebCenter Content
Oracle WebCenter Content application adapters.
Section 5.13.2, "Upgrading Oracle Application
Adapters for Oracle WebCenter Content"
Report Library for Records Management in Content Server.
Section 5.13.3, "Configuring the Report Library for
Records Management in Content Server"
Inbound Refinery (IBR)
Section 5.13.4, "Using Fusion Middleware Control
to Monitor IBR"
WebCenter Content Server
Section 5.13.5, "Starting Oracle WebCenter
Content Server with SOA or BAM"
WebCenter Content System Components
Section 5.13.6, "Enabling System Components for
WebCenter Content"
Oracle Data Integrator
Oracle Data Integrator repository objects.
Section 5.16.6, "Adding the Version Number for
the odi-sdk-ws Application in config.xml"
Oracle WebCenter Portal
Patching procedures for either 11.1.1.4.0 release or 11.1.1.5.0
installation.
Section 6.5, "Patching an Oracle WebCenter
11.1.1.4.0 or 11.1.1.5.0 Installation"
5.5 Post-Patching Tasks If Your Starting Point is Release 11.1.1.5
Table 5–4 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.5.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Table 5–4
Post-Patching Tasks If Your Starting Point is Release 11.1.1.5.0
Product Area
Documentation
System and Identity Management Components
Patch any system component(s) associated with a
WebLogic Server domain.
Section 5.9.1, "Upgrading System Components"
Oracle Identity Federation.
Section 5.10.2, "Upgrading Configuration Properties in
Oracle Identity Federation"
Oracle Identity Management Components, if you plan
to use Oracle Enterprise Manager to view metrics and
configuration settings.
Section 5.10.3, "Using Oracle Enterprise Manager to View
Oracle Identity Management Metrics and Configuration
Settings"
Oracle Internet Directory, if you plan to add more than
one million entries.
Section 5.9.4, "Adding Datafiles to the OLTS_CT_STORE
and OLTS_ATTRSTORE Tablespaces for Oracle Internet
Directory"
Oracle Reports and Oracle Portal.
Section 5.9.3, "Resolving JDBC Errors in Oracle Reports
and Oracle Portal"
Section 5.11.6, "Upgrading the Plug-In Configuration
When Using a Proxy with WebLogic Server"
Oracle Platform Security Services (OPSS)
Section 5.9.5, "Generating the BASE64 Encoded
Encryption Key for OPSS"
Section 5.9.6, "Enabling Dynamic Audit Metadata Model
for OPSS Running in JavaSE Mode"
5-8 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks If Your Starting Point is Release 11.1.1.6
Table 5–4 (Cont.) Post-Patching Tasks If Your Starting Point is Release 11.1.1.5.0
Product Area
Documentation
Diagnostic Framework
Section 5.9.7, "Configuring Diagnostic Framework Dump
Sampling"
JRF Template for IBM WebSphere
Section 5.9.8, "Adding Batik Library Jar Files to the JRF
Template for IBM WebSphere"
Oracle SOA Suite
SOA Composer and BPM Workspace.
Section 5.12.2, "Removing the tmp Folder for SOA
Composer, BPM Workspace and B2B"
Oracle BPEL
Section 5.12.4, "Upgrading MAXRECOVERATTEMPT
Attribute to 2"
BAM-ODI Integration.
Section 5.12.8, "Upgrading the Oracle Data Integrator
Clients if BAM-ODI Integration is Enabled"
Oracle B2B.
Section 5.12.9, "Saving and Restoring XEngine
Customizations for Oracle B2B"
Oracle JMS Adapter.
Section 5.12.10, "Configuring Oracle JMS Adapter with
IBM WebSphere MQ JMS"
User Messaging Service (UMS) Adapter
Section 5.12.11, "Extending the SOA Domain with UMS
Adapter Features"
Business Process Management (BPM)
Section 5.12.12, "Extending the SOA Domain with
Business Process Management Features"
Oracle WebCenter Content
Oracle WebCenter Content application adapters.
Section 5.13.2, "Upgrading Oracle Application Adapters
for Oracle WebCenter Content"
Report Library for Records Management in Content
Server.
Section 5.13.3, "Configuring the Report Library for
Records Management in Content Server"
Inbound Refinery (IBR)
Section 5.13.4, "Using Fusion Middleware Control to
Monitor IBR"
WebCenter Content Server
Section 5.13.5, "Starting Oracle WebCenter Content
Server with SOA or BAM"
WebCenter Content System Components
Section 5.13.6, "Enabling System Components for
WebCenter Content"
Oracle Service Bus
Oracle Service Bus IDE.
Section 5.14.2, "Using Oracle Service Bus With WebLogic
Server 10.3.5"
Section 5.14.4, "Performing Additional Post-Upgrade
Tasks for Oracle Service Bus IDE"
Oracle Business Intelligence
Oracle Business Intelligence.
Section 5.15.4, "Enabling bicontentserver Features"
Oracle WebCenter Portal
Patching procedures for either 11.1.1.4.0 release or
11.1.1.5.0 installation.
Section 6.5, "Patching an Oracle WebCenter 11.1.1.4.0 or
11.1.1.5.0 Installation"
5.6 Post-Patching Tasks If Your Starting Point is Release 11.1.1.6
Table 5–5 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.6.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Post-Patching Procedures
5-9
Post-Patching Tasks If Your Starting Point is Release 11.1.1.6
Table 5–5
Post-Patching Tasks If Your Starting Point is Release 11.1.1.6.0
Product Area
Documentation
System and Identity Management Components
Patch any system component(s) associated
with a WebLogic Server domain.
Section 5.9.1, "Upgrading System Components"
Oracle Identity Federation.
Section 5.10.2, "Upgrading Configuration Properties in Oracle
Identity Federation"
Oracle Identity Management Components, if Section 5.10.3, "Using Oracle Enterprise Manager to View Oracle
you plan to use Oracle Enterprise Manager
Identity Management Metrics and Configuration Settings"
to view metrics and configuration settings.
Oracle Platform Security Services (OPSS)
Section 5.9.5, "Generating the BASE64 Encoded Encryption Key for
OPSS"
Section 5.9.6, "Enabling Dynamic Audit Metadata Model for OPSS
Running in JavaSE Mode"
Diagnostic Framework
Section 5.9.7, "Configuring Diagnostic Framework Dump
Sampling"
JRF Template for IBM WebSphere
Section 5.9.8, "Adding Batik Library Jar Files to the JRF Template for
IBM WebSphere"
Oracle SOA Suite
Oracle B2B, SOA Composer, BPM Workspace Section 5.12.2, "Removing the tmp Folder for SOA Composer, BPM
Workspace and B2B"
Business Process Execution Language (BPEL) Section 5.12.3, "Upgrading the "BPEL Message Recovery Required"
Messaging
Warning Message Duration"
Oracle BPEL
Section 5.12.4, "Upgrading MAXRECOVERATTEMPT Attribute to
2"
User Messaging Service (UMS) Adapter
Section 5.12.11, "Extending the SOA Domain with UMS Adapter
Features"
Business Process Management (BPM)
Section 5.12.12, "Extending the SOA Domain with Business Process
Management Features"
Oracle WebCenter Content
Oracle WebCenter Content application
adapters.
Section 5.13.2, "Upgrading Oracle Application Adapters for Oracle
WebCenter Content"
Report Library for Records Management in
Content Server.
Section 5.13.3, "Configuring the Report Library for Records
Management in Content Server"
Inbound Refinery (IBR)
Section 5.13.4, "Using Fusion Middleware Control to Monitor IBR"
WebCenter Content Server
Section 5.13.5, "Starting Oracle WebCenter Content Server with
SOA or BAM"
WebCenter Content System Components
Section 5.13.6, "Enabling System Components for WebCenter
Content"
Oracle Service Bus
Oracle Service Bus with Oracle WebLogic
Server 10.3.6
Section 5.14.3, "Using Oracle Service Bus With WebLogic Server
10.3.6"
Oracle Business Intelligence
Oracle Business Intelligence Composer
Section 5.15.5, "Enabling Oracle Business Intelligence Composer
Features"
Oracle Business Intelligence JBIPS
Section 5.15.6, "Enabling JBIPS Features for the Smartview Client"
Oracle WebCenter Portal
5-10 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks If Your Starting Point is Release 11.1.1.8
Table 5–5 (Cont.) Post-Patching Tasks If Your Starting Point is Release 11.1.1.6.0
Product Area
Documentation
Patching procedures for Release 11.1.1.6.0
installation.
Section 6.4, "Patching an Oracle WebCenter Portal 11.1.1.6.0
Installation"
Oracle Directory Integration Platform
Oracle Directory Integration Platform (DIP)
Support with Oracle Unified Directory
(OUD) and Oracle Directory Server
Enterprise Edition (ODSEE)
Section 5.10.1, "Enabling New Features of Oracle Directory
Integration Platform (DIP) with OUD and ODSEE"
5.7 Post-Patching Tasks If Your Starting Point is Release 11.1.1.7
Table 5–6 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.7.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Table 5–6
Post-Patching Tasks If Your Starting Point is Release 11.1.1.7.0
Product Area
Documentation
Oracle Directory Integration Platform
Oracle Directory Integration Platform (DIP)
Support with Oracle Unified Directory
(OUD) and Oracle Directory Server
Enterprise Edition (ODSEE)
Section 5.10.1, "Enabling New Features of Oracle Directory
Integration Platform (DIP) with OUD and ODSEE"
Oracle Identity Management Components, if Section 5.10.3, "Using Oracle Enterprise Manager to View Oracle
you plan to use Oracle Enterprise Manager
Identity Management Metrics and Configuration Settings"
to view metrics and configuration settings.
Oracle Service Bus
Oracle Service Bus Configuration
Information
Section 5.14.1, "Upgrading an Oracle Service Bus Domain After
Applying the Latest Patch Set"
Oracle WebCenter Portal
Patching procedures for Release 11.1.1.7.0
installation.
Section 6.3, "Patching an Oracle WebCenter Portal 11.1.1.7.0
Installation"
Oracle WebCenter Content
Oracle WebCenter Content application
adapters.
Section 5.13.2, "Upgrading Oracle Application Adapters for Oracle
WebCenter Content"
Report Library for Records Management in
Content Server.
Section 5.13.3, "Configuring the Report Library for Records
Management in Content Server"
Inbound Refinery (IBR)
Section 5.13.4, "Using Fusion Middleware Control to Monitor IBR"
WebCenter Content Server
Section 5.13.5, "Starting Oracle WebCenter Content Server with
SOA or BAM"
WebCenter Content System Components
Section 5.13.6, "Enabling System Components for WebCenter
Content"
5.8 Post-Patching Tasks If Your Starting Point is Release 11.1.1.8
Table 5–7 summarizes the post-patching tasks that may be required depending on
your existing Release 11.1.1.8.0 environment. Locate the applicable product area in the
table, then refer to the documentation link for instructions.
Post-Patching Procedures 5-11
Post-Patching Tasks for System Components
Table 5–7
Post-Patching Tasks If Your Starting Point is Release 11.1.1.8.0
Product Area
Documentation
Oracle WebCenter Portal
Patching procedures for WebCenter Portal
Chapter 6, "Patching Oracle WebCenter Portal".
Oracle WebCenter Content
Oracle WebCenter Content ADF UI.
Section 5.8.1, "Patching the ADF UI Domain for WebCenter
Content"
5.8.1 Patching the ADF UI Domain for WebCenter Content
The ADF UI for WebCenter Content domain must be patched after upgrading the
WebCenter Content domain to 11.1.1.9.0. The p19926432_111190_Generic.zip patch is
located in the following directory:
ORACLE_HOME/ucm/Distribution/WccADFUI
The installation package, WccADFUI.zip, is also located in this directory.
For detailed instructions on applying the patch in the ADF UI environment, refer to
the README.txt file included in the installation package.
5.9 Post-Patching Tasks for System Components
A system component is a manageable process that is not deployed as a Java
application. Instead, a system component is managed by Oracle Process Manager and
Notification (OPMN). For more information, see "Understanding Key Oracle Fusion
Middleware Concepts" in Oracle Fusion Middleware Administrator's Guide.
Post-patching procedures for the Oracle Identity Management components are
described in Section 5.10, "Post-Patching Tasks for Oracle Identity Management
Components".
Note: WebCenter Content users may need to perform additional
tasks for enabling and disabling system components. See
Section 5.13.6, "Enabling System Components for WebCenter Content"
for more information.
Oracle Fusion Middleware system components include the following:
■
■
■
■
■
Products included with Oracle Web Tier, including Oracle HTTP Server and Oracle
Web Cache.
Products included with Oracle Identity Management, including Oracle Virtual
Directory and Oracle Internet Directory.
Products included with Oracle Portal, Forms, Reports and Discoverer.
Products included with Oracle Business Intelligence, including BI Server, BI
Scheduler and BI Presentation Services.
Products included with Oracle Data Integrator.
If you have patched one or more of these components, the tasks in this section should
be performed. For more information about system components, refer to
"Understanding Key Oracle Fusion Middleware Concepts" in Oracle Fusion Middleware
Administrator's Guide.
5-12 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for System Components
The following tasks should be performed:
■
Section 5.9.1, "Upgrading System Components"
■
Section 5.9.2, "Upgrading Oracle Configuration Manager"
■
Section 5.9.3, "Resolving JDBC Errors in Oracle Reports and Oracle Portal"
■
■
■
■
■
Section 5.11.6, "Upgrading the Plug-In Configuration When Using a Proxy with
WebLogic Server"
Section 5.9.5, "Generating the BASE64 Encoded Encryption Key for OPSS"
Section 5.9.6, "Enabling Dynamic Audit Metadata Model for OPSS Running in
JavaSE Mode"
Section 5.9.7, "Configuring Diagnostic Framework Dump Sampling"
Section 5.9.8, "Adding Batik Library Jar Files to the JRF Template for IBM
WebSphere"
5.9.1 Upgrading System Components
This step is required for any system component that is associated with a WebLogic
domain. In some cases (for example, Oracle Web Tier and Oracle Internet Directory),
you can choose to create standalone system components that are not associated with
any domain; in these cases, you do not have to perform this procedure.
After you have patched your system component software that is associated with a
WebLogic domain, you must run the ORACLE_HOME/opmn/bin/upgradenonj2eeapp.sh
(on UNIX operating systems) or ORACLE_HOME\opmn\bin\upgradenonj2eeapp.bat (on
Windows operating systems) script to upgrade your system components.
Before running this script, make sure:
1.
The Administration Server is up and running.
2.
The ORACLE_HOME environment variable has been set to your product's Oracle
home directory.
3.
The OPMN instance in the bin directory in the Instance home is up and running.
On UNIX operating systems:
cd INSTANCE_HOME/bin
./opmnctl start
On Windows operating systems:
cd INSTANCE_HOME\bin
opmnctl start
To run the script on UNIX operating systems:
cd ORACLE_HOME/opmn/bin
./upgradenonj2eeapp.sh
-oracleInstance Instance_Home_Location
-adminHost WebLogic_Server_Host_Name
-adminPort administration_server_port_number
-adminUsername administration_server_user
On Windows operating systems:
cd ORACLE_HOME\opmn\bin
upgradenonj2eeapp.bat
-oracleInstance Instance_Home_Location
Post-Patching Procedures 5-13
Post-Patching Tasks for System Components
-adminHost WebLogic_Server_Host_Name
-adminPort administration_server_port_number
-adminUsername administration_server_user
Troubleshooting
If you encounter the Command failed: NonJ2EEManagement Application deployment
failed error while running the upgradenonj2eeapp script, perform the following steps
to diagnose and correct the problem:
1.
Review the provisioning.log to determine the root cause of the failure. The log file
is located in the following directory:
MW_HOME/instances/myinstance/diagnostics/logs/OPMN/opmn
2.
If the root cause of the failure is a locking issue, continue with the remaining steps.
If the error was not caused by a locking failure, you may need to simply redeploy
and register your instance as described in Step 5.
3.
Login to the Oracle WebLogic Server Administration console:
http://localhost:7001/console
Navigate to the Change Center and click Release Configuration.
The lock on the configuration will be removed, but you may also need to deploy
re-register your instance.
4.
Restart the upgradenonj2eeapp script as described above and review the
provisioning.log.
If you see: "Failed to unregister instance instance1, does not exist on the
adminserver", continue to the next step.
5.
Redeploy and register the instance as shown in the following examples. Be sure to
use the directory path and instance name for your environment.
./opmnctl redeploy -oracleInstance /Middleware/instances/instance1 -adminHost
localhost -adminPort 7001 -adminUsername weblogic
Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:
./opmnctl registerinstance
Command requires login to weblogic admin server (localhost):
Username: weblogic
Password:
6.
Restart the upgradenonj2eeapp script as described above. You should see
"Successfully upgraded NonJ2EEManagement.ear and the registration."
5.9.2 Upgrading Oracle Configuration Manager
If you are patching Oracle Portal, Forms, Reports and Discoverer, you must run some
emCCR commands after applying the latest patch set in order for the correct version to
appear. emCCR is used by Oracle Configuration Manager, which is used to collect client
configuration information and upload it to the Oracle repository:
1.
Go to the ORACLE_HOME\ccr\bin directory.
5-14 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for System Components
2.
Set the ORACLE_CONFIG_HOME environment variable to the Instance home that
contains Oracle Configuration Manager.
For example, on a Windows operating system:
set ORACLE_CONFIG_HOME=C:\Oracle\Middleware\Instances\asinst_ocmoc
Below is an example on a UNIX operating system:
setenv ORACLE_CONFIG_HOME /home/Oracle/Middleware/asinst_ocmoc
3.
Run the following emCCR commands:
emccr collect
emccr status
5.9.3 Resolving JDBC Errors in Oracle Reports and Oracle Portal
If you have Oracle Reports or Oracle Portal configured in a domain and you apply the
latest patch set, you will see the following error if you try to change the invalidation
password:
Error.
Check logs for details.
[OK].
The following errors are seen in the portal_wls.log and wls_portal.out log files:
<Date and time> <Warning> <RMI> <BEA-080003>
<RuntimeException thrown by rmi server:
javax.management.remote.rmi.RMIConnectionImpl.invoke
(Ljavax.management.ObjectName;Ljava.lang.String;Ljava.rmi.MarshalledObject;[Ljava.
lang.String;Ljavax.security.auth.Subject;)
javax.management.RuntimeErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I.javax.management.Runti
meErrorException:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at
oracle.as.jmx.framework.standardmbeans.spi.OracleStandardEmitterMBean.doInvoke(Ora
cleStandardEmitterMBean.java:991)
at
oracle.adf.mbean.share.AdfMBeanInterceptor.internalInvoke(AdfMBeanInterceptor.java
:104)
at
oracle.as.jmx.framework.generic.spi.interceptors.AbstractMBeanInterceptor.doInvoke
(AbstractMBeanInterceptor.java:252)
....
Caused By: java.lang.UnsatisfiedLinkError:
oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber()I
at oracle.jdbc.driver.T2CConnection.getLibraryVersionNumber(Native
Method)
at oracle.jdbc.driver.T2CConnection$1.run(T2CConnection.java:3537)
at java.security.AccessController.doPrivileged(Native Method)
at oracle.jdbc.driver.T2CConnection.loadNativeLibrary
(T2CConnection.java:3532)
....
You must perform the following in order to avoid these JDBC error messages:
1.
Go to the bin directory inside your DOMAIN_HOME (user_projects by default).
2.
Edit the setDomainEnv.sh (on UNIX operating systems) or setDomainEnv.cmd (on
Windows operating systems) file and search for EXT_PRE_CLASSPATH.
Post-Patching Procedures 5-15
Post-Patching Tasks for System Components
3.
Change the definition to match the following:
On UNIX operating systems:
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar
export EXT_PRE_CLASSPATH
For example:
if [ "${EXT_PRE_CLASSPATH}" != "" ] ; then
if [ "${PRE_CLASSPATH}" != "" ] ; then
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
export EXT_PRE_CLASSPATH
// add this line
PRE_CLASSPATH="${EXT_PRE_CLASSPATH}${CLASSPATHSEP}${PRE_CLASSPATH}"
export PRE_CLASSPATH
else
EXT_PRE_CLASSPATH=$ORACLE_HOME/jdbc/lib/ojdbc6.jar // add this line
export EXT_PRE_CLASSPATH
// add this line
PRE_CLASSPATH="${EXT_PRE_CLASSPATH}"
export PRE_CLASSPATH
fi
fi
On Windows operating systems:
if NOT "%EXT_PRE_CLASSPATH%"=="" (
if NOT "%PRE_CLASSPATH%"=="" (
set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%;%PRE_CLASSPATH%
) else (
set EXT_PRE_CLASSPATH=%ORACLE_HOME%\jdbc\lib\ojdbc6.jar
set PRE_CLASSPATH=%EXT_PRE_CLASSPATH%
)
)
4.
// add this line
// add this line
Restart the Portal Managed Server.
5.9.4 Adding Datafiles to the OLTS_CT_STORE and OLTS_ATTRSTORE Tablespaces for
Oracle Internet Directory
If your Oracle Internet Directory schema was created during installation of a version
prior to 11g Release 1 (11.1.1.6.0), you must add datafiles to the OLTS_CT_STORE and
OLTS_ATTRSTORE tablespaces if you intend to add more than a million entries to Oracle
Internet Directory. Perform this step prior to the bulkload or ldapadd operation.
For details, see "Creating Data Files and Adding Data Files to a Tablespace" in Oracle
Database Administrator's Guide.
5.9.5 Generating the BASE64 Encoded Encryption Key for OPSS
The upgradeOpss() command is used to add a new BASE64 encoded key for each
encryption key already in the bootstrap wallet. This key is required when OBI C based
code accesses DB credential store. This optional command can be used when starting
from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed, OBI will be
unable to access DB-based credential stores in 11.1.1.9.0.
For more information on running OPSS in JSE mode, see "Configuring DB-Based OPSS
Security Stores" in Securing Applications with Oracle Platform Security Services.
5-16 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Identity Management Components
5.9.6 Enabling Dynamic Audit Metadata Model for OPSS Running in JavaSE Mode
To enable the dynamic audit metadata model in audit service for OPSS running in
JavaSE mode, the upgradeOpss() command is used to modify jps-config-jse.xml with
the additional audit service properties. This optional command can be used when
starting from version 11.1.1.4.0, 11.1.1.5.0, or 11.1.1.6.0. If this step is not followed,
11.1.1.9.0 components registered to audit service with the new metadata model will
not have audit service in JSE mode.
For more information on running OPSS in JSE mode, see "Configuring Policy and
Credential Stores in Java SE Applications" in Securing Applications with Oracle Platform
Security Services.
5.9.7 Configuring Diagnostic Framework Dump Sampling
As of Release 11.1.1.7.0 a new dump sampling feature was added to Diagnostic
Framework. To enable this optional feature, the following WLST command should be
run while connected to the AdminServer:
wlst.sh <ORACLE_HOME>/common/scripts/wlst/upgradeDFWConfig.py --adminuser <admin
user name> --password <admin password> --adminurl <admin url>
5.9.8 Adding Batik Library Jar Files to the JRF Template for IBM WebSphere
This optional post-patching step enables you to provide printer-friendly renderings of
certain DVT components such as treemap and sunburst by adding the Batik SVG
libraries to the ADF View JRF classpath and the Apache JARs to the application
classpath.
For more information, see "upgradeADFLibrary" in the Administering Oracle ADF
Applications.
5.10 Post-Patching Tasks for Oracle Identity Management Components
This section describes post-patching tasks for products included in Oracle Identity
Management: Oracle Internet Directory, Oracle Directory Integration Platform, Oracle
Virtual Directory, Oracle Directory Services Manager and Oracle Identity Federation.
■
■
■
Section 5.10.1, "Enabling New Features of Oracle Directory Integration Platform
(DIP) with OUD and ODSEE"
Section 5.10.2, "Upgrading Configuration Properties in Oracle Identity Federation"
Section 5.10.3, "Using Oracle Enterprise Manager to View Oracle Identity
Management Metrics and Configuration Settings"
If you are upgrading Oracle Identity and Access Management
components, such as Oracle Access Manager, Oracle Adaptive Access
Manager or Oracle Identity Manager, see "Oracle Fusion Middleware
Upgrade Guide for Oracle Identity and Access Management".
Note:
5.10.1 Enabling New Features of Oracle Directory Integration Platform (DIP) with OUD
and ODSEE
If you want to use the new DIP features with Oracle Unified Directory (OUD) or
Oracle Directory Server Enterprise Edition (ODSEE) after upgrading the Oracle
Post-Patching Procedures 5-17
Post-Patching Tasks for Oracle Identity Management Components
WebLogic Server domain, then you must run the dipConfigurator update (<ORACLE_
HOME>/bin) command on the command line and enter the following arguments:
Table 5–8
dipConfigurator Properties
Properties
Description
wlshost
Oracle WebLogic Server host name where Oracle Directory
Integration Platform is deployed. The default host name is
localhost.
wlsport
Listening port number of the Oracle WebLogic Managed Server
where Oracle Directory Integration Platform is deployed. The
default port number is 7001.
wlsuser
Oracle WebLogic Server login user name.
ldaphost
Oracle Unified Directory host name. The default host name is
localhost.
ldapport
Oracle Unified Directory server port number. The default value
is 636.
isldapssl
Specify true or false, to enable or disable SSL. The default
value is true.
ldapuser
The default value is cn=Directory Manager.
ldapadminport
This parameter is used to specify the OUD administration port.
The default value in 4444.
NOTE: This parameter is only required when the backend is
OUD. You do not need this parameter when the backend is
ODSEE.
You must start Directory Integration Platform before running
dipConfigurator. For information on starting DIP, see "Starting and
Stopping Oracle Directory Integration Platform Using WLST" in
Oracle Fusion Middleware Administrator's Guide for Oracle Directory
Integration Platform
Note:
You can view the dipConfig.log file, located at <ORACLE_
HOME>/ldap/log/.
Example:
cd $ORACLE_HOME/bin/
$ ./dipConfigurator update
Enter WLS Admin Server Host Name [localhost] : machine_name
Enter WLS Admin Server Port [7001] : 7001
Enter username to contact WebLogic Server : weblogic
Enter password to contact WebLogic Server :
Enter backend LDAP Server HostName [localhost] : machine_name
Enter backend LDAP Server Port [636] : 1389
Enter if LDAP port is SSL enabled [true] : false
Enter username to contact LDAP server : cn=orcladmin
Enter password to contact LDAP Server :
Enter LDAP Server Admin Port [4444] : 4444
Alternatively, you can use a single command line as shown below:
$ORACLE_HOME/bin/dipConfigurator update -wlshost localhost -wlsport 7001 -wlsuser
weblogic -ldaphost localhost -ldapport 1389 -isldapssl false -ldapuser
"cn=Directory Manager" -ldapadminport 4444
5-18 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Identity Management Components
Verifying the Upgrade
Once the dipConfigurator update command has been run, you can validate the
results of the upgrade by executing the dipStatus command, which is located in the
$ORACLE_HOME/bin/ directory. For more information, see "Verifying Oracle
Directory Integration Platform" in Oracle Fusion Middleware Administrator's Guide for
Oracle Directory Integration Platform.
You can also verify the Oracle Directory Integration Platform (ODIP) upgrade using
the Oracle Enterprise Manager Fusion Middleware Control, as follows:
1.
Log in to the Oracle Enterprise Manager Fusion Middleware Control.
2.
In the navigation panel on the left, click or expand Identity and Access and then
select the DIP component.
3.
Click the DIP Server menu, point to Administration, and then select Server
Properties.
4.
Click Test Connection and verify the instance.
5.10.2 Upgrading Configuration Properties in Oracle Identity Federation
Oracle Identity Federation has new features and bug fixes that require new properties
to be defined in the Oracle Identity Federation configuration file. If you want to take
advantage of the functionality provided by these new properties, you must run one of
the following WLST scripts:
■
■
■
■
Run the oif-upgrade-11.1.1.2.0-11.1.1.9.0.py script if:
–
You are upgrading your software from 11.1.1.2.0 or 11.1.1.3.0 to 11.1.1.9.0
–
You did not previously run the oif-upgrade-11.1.1.2.0-11.1.1.4.0.py
script on an existing 11.1.1.4.0 or 11.1.1.5.0 installation.
Run the oif-upgrade-11.1.1.4.0-11.1.1.9.0.py script if you are upgrading
your software from 11.1.1.4.0 or 11.1.1.5.0 to 11.1.1.9.0.
Run the oif-upgrade-11.1.1.6.0-11.1.1.9.0.py script if you are upgrading
your software from 11.1.1.6.0 to 11.1.1.9.0.
Run the oif-upgrade-11.1.1.7.0-11.1.1.9.0.py script if you are upgrading
your software from 11.1.1.7.0 to 11.1.1.9.0.
The instructions to run the scripts are shown below:
1.
On Linux operating systems, enter the bash command:
bash
2.
Set the DOMAIN_HOME variable to your Oracle Identity Federation Domain home
location.
3.
Set the ORACLE_HOME variable to your Oracle Identity Federation Oracle home
location.
4.
Run the setOIFEnv script.
On UNIX operating systems:
bash
export DOMAIN_HOME=full_path_to_domain_home_directory
source ORACLE_HOME/fed/scripts/setOIFEnv.sh
Post-Patching Procedures 5-19
Post-Patching Tasks for Oracle Identity Management Components
On Microsoft Windows operating systems:
cd ORACLE_HOME\fed\scripts
setOIFEnv.cmd
5.
Run the oif-upgrade-11.1.1.2.0-11.1.1.9.0.py,
oif-upgrade-11.1.1.4.0-11.1.1.9.0.py,
oif-upgrade-11.1.1.6.0-11.1.1.9.0.py or
oif-upgrade-11.1.1.7.0-11.1.1.9.0.py script.
For example, on UNIX operating systems:
cd ORACLE_HOME/common/bin>wlst.sh $ORACLE_
HOME/fed/scripts/oif-upgrade-11.1.1.2.0-11.1.1.9.0.py
On Microsoft Windows operating systems:
cd ORACLE_HOME\common\bin>wlst.cmd $ORACLE_
HOME\fed\scripts\oif-upgrade-11.1.1.2.0-11.1.1.9.0.py
You will be prompted for the WebLogic Server Administrator credentials (user
name and password) and the location of the Managed Server where Oracle
Identity Federation is running. You only need to do this for one Managed Server
even if you have multiple Managed Servers in your domain.
5.10.3 Using Oracle Enterprise Manager to View Oracle Identity Management Metrics
and Configuration Settings
If you are patching Oracle Identity Management components to 11g Release 1 (11.1.1.9)
from a version prior to 11.1.1.6, and you want to use Oracle Enterprise Manager to
view configuration settings and metrics for Oracle Virtual Directory, Directory
Integration Platform or Oracle Unified Directory, you must do the following after
applying the patch:
1.
Navigate to the /lib directory of your WebLogic Server.
For example:
cd $WL_HOME/server/lib
2.
Execute the following:
java -jar wljarbuilder.jar
3.
Navigate to the /jlib directory of your Oracle Home.
For example:
cd $ORACLE_HOME/sysman/jlib
4.
Copy the wlfullclient.jar file to ORACLE_HOME/sysman/jlib.
cp $WL_HOME/server/lib/wlfullclient.jar .
5.
Stop and restart the EMAGENT:
$ORACLE_INSTANCE/bin/opmnctl stopproc ias-component=EMAGENT
$ORACLE_INSTANCE/bin/opmnctl startproc ias-component=EMAGENT
6.
Log in to the Oracle Fusion Middleware Control Console and verify that the
Configuration Settings page is available for Oracle Virtual Directory or Oracle
Internet Directory.
5-20 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Your WebLogic Server Domain
5.11 Post-Patching Tasks for Your WebLogic Server Domain
Your existing WebLogic Server Domain must be upgraded by performing the
following tasks:
■
Section 5.11.1, "Upgrading Fusion Middleware Shared Libraries"
■
Section 5.11.2, "Upgrading Configurations and Stores"
■
Section 5.11.3, "Upgrading Oracle WSM Configurations"
■
Section 5.11.4, "Enabling WS-AtomicTransaction"
■
■
Section 5.11.5, "Optimizing Performance for WebLogic Server Domains on 64-Bit
Platforms"
Section 5.11.6, "Upgrading the Plug-In Configuration When Using a Proxy with
WebLogic Server"
5.11.1 Upgrading Fusion Middleware Shared Libraries
For each WebLogic Server domain, you must run the upgradeJRF() WLST command
to upgrade the shared libraries in your domain:
If you are patching Oracle WebCenter Portal, you do not need
to run this command if you follow the directions in Chapter 6,
"Patching Oracle WebCenter Portal".
Note:
1.
Stop all running instances, Managed Servers, Administration Server, and Node
Manager in the domain. See "Starting and Stopping Oracle Fusion Middleware" in
Oracle Fusion Middleware Administrator's Guide for more information.
2.
Start WLST.
On UNIX operating systems:
cd oracle_common/common/bin
./wlst.sh
On Windows operating systems:
cd oracle_common\common\bin
wlst.cmd
3.
Run the upgradeJRF() command on the node or system where the Administration
Server is located for each domain you want to upgrade. Your domain location is
passed as a parameter:
wlst> upgradeJRF('/DOMAIN_HOME')
Post-Patching Procedures 5-21
Post-Patching Tasks for Your WebLogic Server Domain
After you run this command, any custom changes that you
have made to your setDomainEnv script will be lost. Oracle
recommends that you keep your custom modifications in a separate
script that is called by setDomainEnv in order to minimize the
disruption that is caused when other domain templates are applied
and the setDomainEnv script is regenerated.
Note:
If you have set IPv6 to false in your setDomainEnv script, this change
will be overwritten when you run the upgradeJRF() command. Make
sure you reset IPv6 to false in the setDomainEnv script after you run
the upgradeJRF() command.
5.11.2 Upgrading Configurations and Stores
For each WebLogic Server domain, you must run the upgradeOpss() WLST command
to upgrade your configurations and stores from previous releases to Release 11.1.1.9.0
configurations and stores using a system-jazn-data file.
When running upgradeOpss for 11.1.1.9.0, you may receive a
"File Not Found" error message for the audit-store.xml file. This error
message can be ignored. The audit-store.xml file is provided after
running the upgradeOpss script.
Note:
For more information on upgrading configurations and stores, see "Configuring
File-Based Policy and Credential Stores" in the Securing Applications with Oracle
Platform Security Services.
If you are patching Oracle WebCenter Portal, you do not need
to run this script if you follow the directions in Chapter 6, "Patching
Oracle WebCenter Portal".
Note:
5.11.3 Upgrading Oracle WSM Configurations
For each WebLogic Server domain, you must run the upgradeWSM() WLST command
to upgrade the Oracle WSM configuration and policies from a previous release
(11.1.1.1.0–11.1.1.6.0) to Release 11.1.1.9.0.
The Oracle WSM configuration and policies will be upgraded, such as:
■
Any predefined policies that have not been customized for your environment are
replaced, and any new policies are automatically added. Note, however, that
predefined policies that have been customized and user-created custom policies in
the repository are not replaced.
■
WS-Trust configuration, such as DNs and trusted issuers.
■
Custom roles for secure EJBs.
This command must be run as a WLST offline command.
Therefore, make sure to stop all running instances, Managed Servers,
Administration Server, and Node Manager in the domain. See
"Starting and Stopping Oracle Fusion Middleware" in the Oracle
Fusion Middleware Administrator's Guide for more information.
Note:
5-22 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Your WebLogic Server Domain
To run the upgradeWSM() WLST command:
1.
Start WLST offline.
On UNIX operating systems:
cd oracle_common/common/bin
./wlst.sh
On Windows operating systems:
cd oracle_common\common\bin
wlst.cmd
2.
Run the upgradeWSM() command on the node or system where the Administration
Server is located for each domain you want to upgrade. The absolute path to your
domain location is passed as a parameter:
wls:/offline> upgradeWSM('/domainPath')
In the following example, the OWSM configuration in a WebLogic Server 11g
11.1.1.5.0 domain is being upgraded to release 11.1.1.9.0.
oracle_common\common\bin > 'Oracle_HOME/user_projects/domains/ps5_domain')
Starting Operation upgradeWSM ...
Upgrading Oracle Web Services Manager configuration started.
Upgrading Oracle Web Services Manager configuration files started.
Upgrading Oracle Web Services Manager configuration files completed.
Migration of custom roles and policies started.
Migration of custom roles and policies completed.
Oracle Web Services Manager successfully upgraded to version 11.1.1.9.0.
3.
Restart the servers and instances in your domain.
For more information on using the upgradeWSM() WLST command, see "Web Services
Custom WLST Commands" in the WLST Command Reference for WebLogic Server. For
more information about using Oracle WSM, refer to the Administering Web Services.
5.11.4 Enabling WS-AtomicTransaction
WS-AtomicTransaction is a Web services feature that was introduced in Oracle Fusion
Middleware Release 11.1.1.3.0 release. If you are upgrading a domain that is at the
11.1.1.2.0 release, then you need to perform the following steps to ensure that
WS-AtomicTransactions are enabled:
1.
Edit the following file.
On UNIX operating systems:
DOMAIN_HOME/config/fmwconfig/policy-accessor-config.xml
On Windows operating systems:
DOMAIN_HOME\config\fmwconfig\policy-accessor-config.xml
2.
In the Interceptors section, add the following XML code:
<interceptor name="ClientWSATInterceptor"
class="oracle.j2ee.ws.client.transaction.ClientWSATInterceptor"
category="transaction" />
<interceptor name="ServerWSATInterceptor"
Post-Patching Procedures 5-23
Post-Patching Tasks for Your WebLogic Server Domain
class="oracle.j2ee.ws.server.transaction.ServerWSATInterceptor"
category="transaction" />
3.
In the Interceptor Chains section:
■
<interceptor-ref name="ServerWSATInterceptor"/> should be added in the
existing entry of SOAPServiceBindingInterceptorChain between the Context
and RM interceptors. For example:
<interceptor-chain name="SOAPServiceBindingInterceptorChain"
@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
<interceptor-ref name="MTOMInterceptor"/>
<interceptor-ref name="BindingSecurityInterceptor"/>
<interceptor-ref name="ServerAddressingInterceptor"/>
<interceptor-ref name="MEXInterceptor"/>
<interceptor-ref name="WSRMServerInterceptor"/>
<interceptor-ref name="ServerWSATInterceptor"/>
<interceptor-ref name="ContextInterceptor"/>
<interceptor-ref name="BindingManagementInterceptor"/>
</interceptor-chain>
■
<interceptor-ref name="ClientWSATInterceptor"/> should be added in the
existing entry of SOAPReferenceBindingInterceptorChain between the
Context and RM interceptors. For example:
<interceptor-chain name="SOAPReferenceBindingInterceptorChain"
@ class="oracle.integration.platform.common.SOAPBindingInterceptorChain">
<interceptor-ref name="BindingManagementInterceptor"/>
<interceptor-ref name="ContextInterceptor"/>
<interceptor-ref name="ClientWSATInterceptor"/>
<interceptor-ref name="WSRMClientInterceptor"/>
<interceptor-ref name="ClientAddressingInterceptor"/>
<interceptor-ref name="BindingSecurityInterceptor"/>
<interceptor-ref name="MTOMInterceptor"/>
</interceptor-chain>
5.11.5 Optimizing Performance for WebLogic Server Domains on 64-Bit Platforms
If you are upgrading any existing 11g Oracle WebLogic Domain to Release 11.1.1.9.0, it
is recommended to make the changes in the setDomainEnv file as described below to
optimize performance:
if [ "${JAVA_USE_64BIT}" = "true" ] ; then
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
EXTRA_JAVA_PROPERTIES="-XXcompressedRefs:enable=TRUE
${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
fi
fi
if [ "${JAVA_VENDOR}" = "Oracle" ] ; then
EXTRA_JAVA_PROPERTIES="-XX:+UseLargePagesForHeap
${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
fi
EXTRA_JAVA_PROPERTIES="-Djps.auth.debug=false ${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
5-24 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle SOA Suite
The applicable EXTRA_JAVA_PROPERTIES are described in
Table 5–9
Description of Parameters for EXTRA_JAVA_PROPERTIES
Property
Description
-XXcompressedRefs
This option governs the use of compressed references,
limiting all pointers stored on the heap to 32 bits.
Compressed references use fewer Java heap resources
and transport less data on the memory bus, thereby
improving the performance. This option also frees space
on the heap.
-XXcompressedRefs:enable=TRUE is applicable for the
JRockit JVM running on a 64-bit operating system.
-XX:+UseLargePagesForHeap
This option enables the use of large pages (if they are
available) for the Java heap and code in the JVM. Large
pages allow your application to more effectively use the
translation look-aside buffer (TLB) in the processor.
This option is applicable for the JRockit JVM.
-Djps.auth.debug
This option is used to make sure JPS debugging is turned
off.
This option is applicable for all JVM types.
5.11.6 Upgrading the Plug-In Configuration When Using a Proxy with WebLogic Server
Due to security changes in WebLogic Server, if you are running a proxy module in
front of your WebLogic Server, such as mod_wl_ohs for example, you will need to
perform the steps mentioned in the Using Oracle WebLogic Server Proxy Plug-Ins 12.1.3.
In addition, if a load balancer or other software deployed in front of the web server
and plug-in is the SSL termination point, and that product sets the WL-Proxy-SSL
request header to true or false based on whether or not the client connected to it over
SSL, you may to configure the WLProxySSL and WLProxySSLPassThrough
parameters as described in "Parameters for Web Server Plug-Ins" in Using Oracle
WebLogic Server Proxy Plug-Ins 12.1.3.
5.12 Post-Patching Tasks for Oracle SOA Suite
This section contains the following topics for completing your Oracle SOA Suite patch:
Before you perform any of the tasks in this section, make sure
you have completed the tasks in Section 5.11, "Post-Patching Tasks for
Your WebLogic Server Domain".
Note:
■
■
Section 5.12.1, "Loading the Oracle SOA Suite Purge Scripts for Database
Management"
Section 5.12.2, "Removing the tmp Folder for SOA Composer, BPM Workspace and
B2B"
■
Section 5.12.5, "Upgrading the soa-infra Application in Warning State"
■
Section 5.12.6, "Running bpm-ps6-upgrade.py to Upgrade the Policy Store"
■
Section 5.12.7, "Running soa-upgrade.py to Upgrade the Policy Store and Deploy a
Shared Library"
Post-Patching Procedures 5-25
Post-Patching Tasks for Oracle SOA Suite
■
Section 5.12.8, "Upgrading the Oracle Data Integrator Clients if BAM-ODI
Integration is Enabled"
■
Section 5.12.9, "Saving and Restoring XEngine Customizations for Oracle B2B"
■
Section 5.12.10, "Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS"
■
Section 5.12.11, "Extending the SOA Domain with UMS Adapter Features"
■
Section 5.12.12, "Extending the SOA Domain with Business Process Management
Features"
5.12.1 Loading the Oracle SOA Suite Purge Scripts for Database Management
When the amount of data in Oracle Fusion Middleware databases grows very large,
maintaining the databases can become difficult and can affect performance. Oracle
Fusion Middleware 11g Release 1 (11.1.1.4.0) and later provide a set of tools that can
help you purge the Oracle Fusion Middleware of unneeded data.
When a new Oracle Fusion Middleware user installs the latest Oracle SOA Suite
schemas using the Repository Creation Utility (RCU), stored procedures required by
the Oracle SOA Suite purge scripts are automatically installed in the database.
However, if you are running Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) or
Release 1 (11.1.1.3.0), these stored procedures are not installed automatically. As a
result, after you run the Patch Set Assistant to upgrade your Oracle SOA Suite
schemas to the latest version, you must manually install the necessary database objects
using the following procedure. This procedure is necessary if you want to use the
purging capabilities provided by Oracle SOA Suite 11g Release 1 (11.1.1.4.0) or later:
1.
Locate, download, and unpack the latest Oracle Fusion Middleware 11g
Repository Creation Utility (RCU) software archive.
For more information, see "Obtaining RCU" in the Oracle Fusion Middleware
Repository Creation Utility User's Guide.
The directory where you unpack the RCU software is referred to as the RCU_HOME
directory.
2.
Using SQLPlus, connect to the database where the Oracle SOA Suite schemas are
installed using the database user that owns the SOAINFRA schema.
3.
Run the following script to load the database objects required for purging Oracle
SOA Suite data:
RCU_HOME/rcu/integration/soainfra/sql/soa_purge/soa_purge_scripts.sql
4.
Run the following script to load the database objects required for verifying the
Oracle SOA Suite data in the database:
RCU_HOME/rcu/integration/soainfra/sql/verify/soa_verify_scripts.sql
After you load the database objects using the provided SQL scripts, refer to "Managing
Database Growth" in the Administering Oracle SOA Suite and Oracle Business Process
Management Suite for more information.
5.12.2 Removing the tmp Folder for SOA Composer, BPM Workspace and B2B
This manual step must be performed if:
■
You are upgrading from any previous SOA release, the Admin tabs within B2B
may not appear after you patch to the latest version.
5-26 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle SOA Suite
■
■
You are upgrading Oracle SOA Composer from Release 11.1.1.2.0 or 11.1.1.3.0; the
SOA Composer login screen may appear blank after you patch to the latest
version.
You are upgrading Oracle BPM Workspace from Release 11.1.1.3.0; the Oracle BPM
Workspace application will not start after you patch to the latest version.
To resolve these issues, do the following:
1.
Stop all servers (Administration Server and all Managed Servers).
2.
Remove the tmp directory in DOMAIN_HOME/servers/AdminServer (on UNIX
operating systems) or DOMAIN_HOME\servers\AdminServer (on Windows operating
systems).
3.
Remove the tmp directory in DOMAIN_HOME/servers/soa_server1 (on UNIX
operating systems) or DOMAIN_HOME\servers\soa_server1 (on Windows operating
systems).
If the name of your SOA Managed Server is not soa_server1, replace soa_server1
with the name of your SOA Managed Server.
4.
Start all the servers.
5.12.3 Upgrading the "BPEL Message Recovery Required" Warning Message Duration
The bpelRecoveryAlertDurationInDays key limits the BPEL Message Recovery
Required inline warning message to be displayed only when recoverable BPEL
messages have been created in the last seven days. The default setting of seven days
can be changed. You cannot set this property to negative values such as -1 or to 0. In
such cases, the key uses its default value (seven days).
To disable the alert message, use the bpelRecoveryStatus key. The duration value is
not applicable to the flow trace alert message.
5.12.4 Upgrading MAXRECOVERATTEMPT Attribute to 2
When upgrading from Oracle SOA Release 11.1.1.4.0, 5.0 or 6.0 to the latest version,
you must manually reset the MAXRECOVERATTEMPT attribute (default 0) to a non-zero
value to correctly display activity recoverable messages.
Use Oracle Enterprise Manager Fusion Middleware Control to reset this System
MBean Browser property:
1.
Access this page through one of the following options:
From the SOA Infrastructure Menu...
1.
Select SOA Administration > BPEL
Properties.
From the SOA Folder in the Navigator...
1.
Right-click soa-infra.
2.
Select SOA Administration > BPEL
Properties.
The BPEL Service Engine Properties page is displayed.
2.
Click More BPEL Configuration Properties.
3.
In the Attributes tab, click MAXRECOVERATTEMPT.
4.
In the Value field, enter 2.
5.
Click Apply.
Post-Patching Procedures 5-27
Post-Patching Tasks for Oracle SOA Suite
5.12.5 Upgrading the soa-infra Application in Warning State
If you have a Release 11.1.1.3.0 Oracle SOA Suite domain with only Oracle SOA
configured (no Oracle BAM and no Oracle BPM), or only Oracle SOA and Oracle BAM
configured (no Oracle BPM), the soa-infra application (the WebLogic server EAR file
which contains the underlying logic for the SOA Suite infrastructure) will have a
deployment status of Warning which will be visible within the WebLogic Server
Administration Console. This state will not cause any loss or degradation in service.
This step is only applicable if your Release 11.1.1.4.0 software
is upgraded from Release 11.1.1.3.0. If Release 11.1.1.4.0 is the only
version you have installed and configured, then you do not need to
perform this task.
Note:
If you want to fix this issue, you must create JMS connection factories and topics as
follows:
1.
From the WebLogic Server Administration Console, navigate to Domain
Structure>JMS Modules>SOAJMSModule and add the following objects:
■
jms/bpm/PeopleQueryConnectionFactory
■
jms/bpm/CubeCommandXAConnectionFactory
■
jms/bpm/PeopleQueryConnectionFactory
■
jms/bpm/MeasurementTopic
■
jms/bpm/PeopleQueryTopic
2.
Complete any additional post-patching tasks.
3.
Restart the WebLogic Server and Administration Console.
5.12.6 Running bpm-ps6-upgrade.py to Upgrade the Policy Store
To upgrade your policy store to add the new Code Source Permissions, run the
bpm-ps6-upgrade.py script from the bin directory inside your SOA Oracle home. You
do not need to run this script if you are starting from version 11.1.1.5.0 or later.
This script must be run as a WLST online script. Make sure the
Administration Server and Managed Servers are up and running
before running this script.
Note:
On a UNIX operating systems:
cd SOA_ORACLE_HOME/bin
../common/bin/wlst.sh bpm-ps6-upgrade.py
On a Windows operating system:
cd SOA_ORACLE_HOME\bin
..\common\bin\wlst.cmd bpm-ps6-upgrade.py
The command will prompt you for the following items of information:
■
Administrator username for your Oracle BPM domain.
■
Administrator password for your Oracle BPM domain.
5-28 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle SOA Suite
■
Host name and Administration Server listen port number where your WebLogic
Server/Oracle BPM domain are installed. This should be specified in the following
format:
t3://host:port
After the script has completed, stop and restart all the servers as described in "Starting
and Stopping Oracle WebLogic Server Instances" in the Oracle Fusion Middleware
Administrator's Guide.
5.12.7 Running soa-upgrade.py to Upgrade the Policy Store and Deploy a Shared
Library
To upgrade your policy store and deploy shared libraries, run the soa-upgrade.py
WLST script, which does the following:
■
■
Adds a new Role Grant and Policy grant within the soa-infra application stripe
in the Policy Store.
Deploys the oracle.soa.worklist.webapp shared library to the SOA domain.
The soa-upgrade.py script must be run from the bin directory inside your SOA Oracle
home. The syntax for the soa-upgrade.py script is shown below.
Note:
This script must be run as a WLST online script.
If you are upgrading from Release 11.1.1.4.0 or earlier, make sure the
Administration Server is the only server that is up and running before
running this script. The other Managed Servers should be shut down.
If you are upgrading from Release 11.1.1.4 or higher, make sure the
Administration Server and all other Managed Servers are up and
running before running this script.
On a UNIX operating system:
cd SOA_ORACLE_HOME/bin
../common/bin/wlst.sh soa-upgrade.py --targetList list_of_SOA_servers_or_
migratable_targets
On a Windows operating system, run wlst.cmd from the same directory.
cd SOA_ORACLE_HOME\bin
..\common\bin\wlst.cmd soa-upgrade.py --targetList list_of_SOA_servers_or_
migratable_targets
The command will prompt you for the following items of information:
■
Administrator username for your Oracle SOA domain.
■
Administrator password for your Oracle SOA domain.
■
Host name and Administration Server listen port number where your WebLogic
Server/Oracle SOA domain are installed. This should be specified in the following
format:
t3://host:port
After running this command, stop and restart all the servers.
Post-Patching Procedures 5-29
Post-Patching Tasks for Oracle SOA Suite
5.12.8 Upgrading the Oracle Data Integrator Clients if BAM-ODI Integration is Enabled
If you are currently using Oracle BAM and Oracle Data Integrator (ODI) integration,
you must re-run an installation script to upgrade your ODI clients after patching your
software.
The Oracle BAM interface used by ODI has undergone some changes which require an
upgrade by all ODI client endpoints. This manual step is only required for domains
where a BAM-ODI integration has been configured.
For each such domain, you must run the SOA_ORACLE_HOME/bam/bin/bam_odi_
configuration.sh (on UNIX operating systems) or SOA_ORACLE_HOME\bam\bin\bam_
odi_configuration.bat (on Microsoft Windows operating systems) script. Use the
PATCH command line parameter to copy the Oracle BAM artifacts. For details, see
"Using Oracle Data Integrator With Oracle BAM" in Developing SOA Applications with
Oracle SOA Suite.
If ODI and Oracle BAM Server are installed on hosts in different networks, or for any
reason you cannot use the script in your environment, you must manually do the
following to upgrade your ODI clients:
1.
Using the Middleware home directory under which Oracle BAM is installed,
generate a wlfullclient.jar file by using the instructions in "Using the WebLogic
JarBuilder Tool" in Developing Stand-alone Clients for Oracle WebLogic Server.
2.
Copy wlfullclient.jar to the ODI_ORACLE_HOME/lib/weblogic (on UNIX
operating systems) or ODI_ORACLE_HOME\lib\weblogic (on Windows operating
systems) directory.
3.
Copy the following Oracle BAM .jar files to the lib directory in the ODI Oracle
home:
On UNIX operating systems:
SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-common.jar
SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-etl.jar
SOA_ORACLE_HOME/bam/modules/oracle.bam_11.1.1/oracle-bam-adc-ejb.jar
SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/commons-codec-1.3.jar
SOA_ORACLE_HOME/bam/modules/oracle.bam.thirdparty_11.1.1/xstream-1.3.1.jar
oracle_common/modules/oracle.odl_11.1.1/ojdl.jar
oracle_common/modules/oracle.jps_11.1.1/jps-api.jar
oracle_common/modules/oracle.dms_11.1.1/dms.jar
oracle_common/modules/org.jaxen_1.1.1.jar
On Windows operating systems:
SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-common.jar
SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-etl.jar
SOA_ORACLE_HOME\bam\modules\oracle.bam_11.1.1\oracle-bam-adc-ejb.jar
SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\commons-codec-1.3.jar
SOA_ORACLE_HOME\bam\modules\oracle.bam.thirdparty_11.1.1\xstream-1.3.1.jar
oracle_common\modules\oracle.odl_11.1.1\ojdl.jar
oracle_common\modules\oracle.jps_11.1.1\jps-api.jar
oracle_common\modules\oracle.dms_11.1.1\dms.jar
oracle_common\modules\org.jaxen_1.1.1.jar
4.
Copy the following Oracle BAM Knowledge Modules from the SOA_ORACLE_
HOME/bam/ODI/knowledge_modules (on UNIX operating systems) or SOA_ORACLE_
HOME\bam\ODI\knowledge_modules (on Windows operating systems) directory to
the ODI_HOME/lib (on UNIX operating systems) or ODI_HOME\lib (on Windows
operating systems) directory:
5-30 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle SOA Suite
KM_CKM
KM_IKM
KM_IKM
KM_IKM
KM_IKM
KM_IKM
KM_IKM
KM_LKM
KM_LKM
KM_RKM
5.
Get Oracle BAM Metadata.xml
SQL to Oracle BAM (delete).xml
SQL to Oracle BAM (insert).xml
SQL to Oracle BAM (looksert natural).xml
SQL to Oracle BAM (looksert surrogate).xml
SQL to Oracle BAM (update).xml
SQL to Oracle BAM (upsert).xml
Get Source Metadata.xml
Oracle BAM to SQL.xml
Oracle BAM.xml
Backup the following ODI_HOME configuration files.
On UNIX operating systems:
ODI_HOME/lib/bam_odi.logging.properties
ODI_HOME/lib/config/BAMODIConfig.xml
On Windows operating systems:
ODI_HOME\lib\bam_odi.logging.properties
ODI_HOME\lib\config/BAMODIConfig.xml
6.
Copy the new version of the ODI configuration files from the SOA_ORACLE_
HOME/bam/ODI (on UNIX operating systems) or SOA_ORACLE_HOME\bam\ODI (on
Windows operating systems) directory to the ODI_ORACLE_HOME directory as
follows.
If you made any changes to the ODI configuration files before
you installed the patch set, then you must make those changes again
after you copy the new configuration files from the SOA Oracle home.
Note:
On UNIX operating systems:
SOA_ORACLE_HOME/bam/ODI/config/bam_odi.logging.properties to ODI_HOME/lib/bam_
odi.logging.properties
SOA_ORACLE_HOME/bam/ODI/config/BAMODIConfig.xml to ODI_
HOME/lib/config/BAMODIConfig.xml
On Windows operating systems:
SOA_ORACLE_HOME\bam\ODI\config\bam_odi.logging.properties to ODI_HOME\lib\bam_
odi.logging.properties
SOA_ORACLE_HOME\bam\ODI\config\BAMODIConfig.xml to ODI_
HOME\lib\config\BAMODIConfig.xml
5.12.9 Saving and Restoring XEngine Customizations for Oracle B2B
The procedure in this section is needed only if you use custom XEngine configurations
in cases where B2B server is integrated with B2B EDI endpoints.
In such cases, all B2B domains created from the same installation share the a single
XEngine configuration stored within the following directory:
■
On UNIX operating systems:
MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
■
On Windows operating systems:
Post-Patching Procedures 5-31
Post-Patching Tasks for Oracle SOA Suite
MW_HOME\SOA_ORACLE_HOME\soa\thirdparty\edifecs\XEngine
To preserve your XEngine customizations:
1.
Prior to patching Oracle SOA Suite, back up all contents in the following directory:
MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
For example, on a UNIX operating system:
cp -pr SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine backup_location
2.
Run the Installer to upgrade the software.
3.
Unzip the XEngine ZIP file in the following directory:
MW_HOME/SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine
For example, on a UNIX operating system:
cd SOA_ORACLE_HOME/soa/thirdparty/edifecs
gunzip XEngine.tar.gz
tar -xvf XEngine.tar
4.
Restore only the customized configuration files from your backup location.
For example, if you made changes to the XERegistry.xml file on a UNIX operating
system:
cp backup_location/config/XERegistry.xml
SOA_ORACLE_HOME/soa/thirdparty/edifecs/XEngine/config
5.12.10 Configuring Oracle JMS Adapter with IBM WebSphere MQ JMS
This step is needed if you are upgrading Oracle SOA Suite from release 11.1.1.2.0 or
earlier to the latest release, and you have developed and deployed composites that
leverage the Oracle JMS Adapter to access JMS messages that are utilizing IBM
WebSphere MQ for message transport/persistence services.
If the Outbound Connection Pool entry created for the JMS Adapter is to be used with
Topics, you must use the following additional connection property, which must be
added to the end of the connection factory properties for Outbound Connection Pool
entry:
ThirdPartyJMSProvider=true
For more information, see "Configuring Oracle JMS Adapter with IBM WebSphere MQ
JMS" in Understanding Technology Adapters.
5.12.11 Extending the SOA Domain with UMS Adapter Features
This manual step is needed if you are upgrading your Oracle SOA Suite from release
11.1.1.6.0 or earlier to the latest release, and you want to enable the new User
Messaging Service (UMS) Adapter features.
1.
Stop all Admin and Managed Servers as described in "Starting and Stopping
Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's
Guide.
2.
Launch the Oracle WebLogic Configuration Wizard as described in "Starting the
Configuration Wizard in Graphical Mode" in Creating WebLogic Domains Using the
Configuration Wizard.
5-32 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle WebCenter Content
3.
On the Select Extension Source screen of the Configuration Wizard, select Extend
my domain using an existing extension template and specify the following path
to the SOA upgrade extension template in the Template location field:
SOA_HOME/common/templates/applications/oracle.soa_template_111160_111170.jar
4.
Continue through the remaining screens to complete the extension.
5.
Restart the Admin and Managed Servers as described in "Starting and Stopping
Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's
Guide.
5.12.12 Extending the SOA Domain with Business Process Management Features
This manual step is needed if you are upgrading your Oracle SOA Suite from release
11.1.1.6.0 or earlier to the latest release, and you want to enable the new BPM features
such as Case Management and Frevvo Webforms.
1.
Apply the SOA upgrade template as described in Section 5.12.11, "Extending the
SOA Domain with UMS Adapter Features". This is a mandatory prerequisite.
2.
Stop all Admin and Managed Servers as described in "Starting and Stopping
Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's
Guide.
3.
Launch the Oracle WebLogic Configuration Wizard as described in "Starting the
Configuration Wizard in Graphical Mode" in Creating WebLogic Domains Using the
Configuration Wizard.
4.
On the Select Extension Source screen of the Configuration Wizard, select Extend
my domain using an existing extension template and specify the following path
to the BPM upgrade extension template in the Template location field:
[SOA_HOME]/common/templates/applications/oracle.bpm_template_1111xx_1111xx.jar
5.
Continue through the remaining screens to complete the extension.
6.
Restart the Admin and Managed Servers as described in "Starting and Stopping
Oracle WebLogic Server Instances" in the Oracle Fusion Middleware Administrator's
Guide.
5.13 Post-Patching Tasks for Oracle WebCenter Content
This section contains the following topics:
■
■
■
Section 5.13.1, "Upgrading Oracle WebCenter Content: Imaging"
Section 5.13.2, "Upgrading Oracle Application Adapters for Oracle WebCenter
Content"
Section 5.13.3, "Configuring the Report Library for Records Management in
Content Server"
■
Section 5.13.4, "Using Fusion Middleware Control to Monitor IBR"
■
Section 5.13.5, "Starting Oracle WebCenter Content Server with SOA or BAM"
■
Section 5.13.6, "Enabling System Components for WebCenter Content"
Post-Patching Procedures 5-33
Post-Patching Tasks for Oracle WebCenter Content
5.13.1 Upgrading Oracle WebCenter Content: Imaging
After upgrading your Oracle WebCenter Content software to Release 11.1.1.9.0 from
11.1.1.3.0 or previous version, the manual steps in this section must be performed to
target a newly distributed library to the Oracle WebCenter Content: Imaging
deployment. If these steps are not performed, the Oracle WebCenter Content: Imaging
Managed Server (default of IPM_server1) will not start.
1.
Make sure Oracle WebLogic Server is started, then open the Oracle WebLogic
Server Administration Console:
http://administration_server_host:administration_server_port/console
2.
For production systems, go to the "Change Center" portion of the navigation panel
on the left and click Lock & Edit.
3.
Targeting the Oracle Application Core Stub file:
a.
In the "Domain Structure" portion of the navigation panel on the left, click
Deployments.
b.
Above the "Deployments" table, click the Install button.
c.
In the "Path" field, browse to the directory containing the Oracle Application
Core Stub file.
The default location is MW_HOME/oracle_
common/atgpf/modules/oracle.applcore.model_11.1.1 (on UNIX operating
systems) or MW_HOME\oracle_
common\atgpf\modules\oracle.applcore.model_11.1.1 (on Windows
operating systems).
4.
d.
Select the oracle.applcore.model.stub.ear file and click Next.
e.
Select Install this deployment as a library and click Next.
f.
Select IPM_server1 as the deployment target and click Next.
g.
Click Finish.
Targeting the Oracle SOA Libraries file for BPM:
Note: If oracle.soa.workflow.wc.jar is already installed due to
Oracle SOA Suite being a part of the domain, you should skip the
following Steps a-f. Instead, navigate to oracle.soa.workflow.wc in
deployments, then go into its "Targets" tab and target IPM_server1.
a.
In the "Domain Structure" portion of the navigation panel on the left, click
Deployments.
b.
Above the "Deployments" table, click the Install button.
c.
In the "Path" field, browse to the directory containing the Oracle SOA
Libraries file.
The default location is ECM_ORACLE_HOME/soa/modules/oracle.soa.workflow_
11.1.1 (on UNIX operating systems) or ECM_ORACLE_
HOME\soa\modules\oracle.soa.workflow_11.1.1 (on Windows operating
systems).
d.
Select the oracle.soa.workflow.wc.jar file and click Next.
5-34 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle WebCenter Content
A message indicating errors while parsing the deployment will appear in the
"Messages" box at the top of the screen. The configuration will treat this as a
library deployment. This is expected.
e.
Select IPM_server1 as the deployment target and click Next.
f.
Click Finish.
5.
For production systems, go to the "Change Center" portion of the navigation panel
on the left and click Activate Changes.
6.
Any instances of the IPM Managed Server must be restarted for this change to take
effect.
7.
Redeploy the imaging.ear file that is installed by the patch set.
The imaging.ear file is saved by the installer to the following directory:
ECM_ORACLE_HOME/ipm/lib/imaging.ear
ECM_ORACLE_HOME\ipm\lib\imaging.ear
To redeploy the EAR file, you can use the command-line, or you can use the Oracle
WebLogic Server Administration Console:
■
■
For information about redeploying an EAR file in from the Administration
Console, see "Upgrade (redeploy) an Enterprise application" in the Oracle
WebLogic Server Administration Console Online Help.
From the command-line, you can use the Oracle WebLogic Server deployer
command; for example:
java weblogic.Deployer -redeploy -name appName
Where appName is the name of the EAR file as defined in the config.xml file.
■
You can also redeploy using the WLST redeploy() command:
redeploy("appName")
For more information about the redeploy() WLST command, see "redeploy"
in WLST Command Reference for WebLogic Server.
5.13.2 Upgrading Oracle Application Adapters for Oracle WebCenter Content
The Oracle WebCenter Content application adapters as described in Oracle Fusion
Middleware Administering the Application Adapters for Oracle WebCenter contain manual
steps for installing the adapters to their respective ERP system (EBS and PeopleSoft).
In order to upgrade to from any previous release to Release 11.1.1.9.0, these adapters
must be reinstalled.
To reinstall the EBS adapter:
1.
Follow the instructions in "Compiling Oracle E-Business Suite Forms" in Oracle
Fusion Middleware Administering the Application Adapters for Oracle WebCenter to
upgrade the AXF_CUSTOM.PLL module.
2.
If you are configured for SSL, follow the instructions in "Configuring the
Integration for SSL" in Oracle Fusion Middleware Administering the Application
Adapters for Oracle WebCenter.
To re-import the PeopleSoft project, follow the instructions (steps 1-6) in "Importing
the Oracle PeopleSoft Project" in Oracle Fusion Middleware Administering the Application
Adapters for Oracle WebCenter.
Post-Patching Procedures 5-35
Post-Patching Tasks for Oracle WebCenter Content
5.13.3 Configuring the Report Library for Records Management in Content Server
If you plan to configure the Records Management feature in Content Server, you need
configure the report library for Records Management after creating the domain that
includes the WebCenter Content Managed Server, before starting it for the first time.
Without this library, you cannot check in any templates to Content Server.
For more information on configuring the report library for Records Management, see
"Configuring the Report Library for Records Management in Content Server" in the
Oracle Fusion Middleware Installing and Configuring Oracle WebCenter Content.
5.13.4 Using Fusion Middleware Control to Monitor IBR
When Inbound Refinery (IBR) has been upgraded to 11.1.1.9.0, the domain must be
expanded to use the Oracle Enterprise Manager Plug-in for IBR template with
Enterprise Manager Fusion Middleware Control to monitor IBR.
The steps below describe how to expand the domain to include the Oracle Enterprise
Manager Plug-in for IBR template.
1.
Navigate to ECM_Home/common/bin/
2.
Execute config.sh
./config.sh
3.
Select Extend an existing Weblogic domain
4.
Select the domain to be extended.
5.
In the next screen, select Oracle Enterprise Manager Plugin for IBR
6.
Click Extend to extend the domain with the IBR template.
5.13.5 Starting Oracle WebCenter Content Server with SOA or BAM
When WebCenter Content is integrated with Oracle SOA or Oracle Business Activity
Monitoring (BAM), you must start SOA and BAM before starting Oracle WebCenter
Content or Oracle Inbound Refinery (IBR).
For more information on launching WebCenter Content server from Fusion
Middleware Control, see "Getting Started with Oracle WebCenter Content" in Oracle
Fusion Middleware Administering Oracle WebCenter Content.
If you attempt to start the WebCenter Content server or IBR before starting Oracle
SOA or BAM servers, then you may see the following error:
oracle.wsm.policymanager.PolicyManagerException:
WSM-02120 : Unable to connect to the policy access service.
5.13.6 Enabling System Components for WebCenter Content
If you disabled components before the upgrade process, and you did not enable them
before the upgrade, then you may experience issues with starting the components after
the upgrade. If so, enable the components and retry the upgrade. See Section 3.3.5.1,
"Enabling WebCenter Content Components Before Upgrade" for a complete list of
components that may be impacted.
For more information, see "Enabling or Disabling a Component Using the Component
Manager" in Oracle Fusion Middleware Administering Oracle WebCenter Content.
5-36 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Service Bus
5.14 Post-Patching Tasks for Oracle Service Bus
The instructions in this section describe the tasks that you may need to perform based
on your upgrade starting point. Review the upgrade starting point tables to determine
which tasks you need to perform after you upgrade your Oracle Service Bus Release
domain configuration information to the latest release.
■
Section 5.14.1, "Upgrading an Oracle Service Bus Domain After Applying the
Latest Patch Set"
■
Section 5.14.2, "Using Oracle Service Bus With WebLogic Server 10.3.5"
■
Section 5.14.3, "Using Oracle Service Bus With WebLogic Server 10.3.6"
■
Section 5.14.4, "Performing Additional Post-Upgrade Tasks for Oracle Service Bus
IDE"
5.14.1 Upgrading an Oracle Service Bus Domain After Applying the Latest Patch Set
To upgrade your Oracle Service Bus domain configuration information:
1.
Make sure you have backed up and shut down all domains to be upgraded.
2.
Under each Oracle Service Bus domain to be upgraded, open a command window
and run the user_projects/bin/setDomainEnv.sh (on UNIX operating systems)
or user_projects\bin\setDomainEnv.cmd (on Windows operating systems)
command.
3.
In the command window, switch to the directory in which the upgrade scripts
resides:
OSB_ORACLE_HOME/common/lib/upgrade
4.
On the command line, run the appropriate script for your operating system:
(UNIX) java weblogic.WLST ./domainUpgrade.py
(Windows) java weblogic.WLST domainUpgrade.py
5.14.2 Using Oracle Service Bus With WebLogic Server 10.3.5
Oracle Fusion Middleware 11g supports both Oracle WebLogic Server release 10.3.5
and 10.3.6. However, if you have already configured Oracle Service Bus with Oracle
WebLogic Server 10.3.5 and you want to upgrade Oracle Service Bus with Oracle
Service Bus IDE to 11g Release 1 (11.1.1.9.0), then you must also upgrade Oracle
WebLogic Server to release 10.3.6. Oracle WebLogic Server 10.3.5 is not supported in
an Oracle Service Bus IDE 11g Release 1 (11.1.1.9.0) environment.
If you must upgrade Oracle Service Bus to 11g Release 1 (11.1.1.9.0), and you want to
keep your Oracle WebLogic Server release at 10.3.5, then you must disable Oracle
Service Bus IDE by manually deleting the following file:
(UNIX) MW_HOME/oepe_11.1.1.9.0/dropins/oracle.osb.ide.lnk
(Windows) MW_HOME\oepe_11.1.1.9.0\dropins\oracle.osb.ide.lnk
5.14.3 Using Oracle Service Bus With WebLogic Server 10.3.6
If you installed Oracle WebLogic Server version 10.3.6, and you upgraded Oracle
Service Bus to 11g Release 1 (11.1.1.9.0), then you must install the required patches as
described on the "Known Issues for Oracle SOA Products and Oracle AIA Foundation
Pack" page on Oracle Technology Network at:
Post-Patching Procedures 5-37
Post-Patching Tasks for Oracle Service Bus
http://www.oracle.com/technetwork/middleware/docs/aiasoarelnotesps6-186603
0.html
5.14.4 Performing Additional Post-Upgrade Tasks for Oracle Service Bus IDE
If you are using Oracle Service Bus IDE in your environment, this section describes the
required tasks after upgrading your Oracle Service Bus software to the latest version.
5.14.4.1 Deleting Oracle WebLogic Server 11g Release 1 (10.3.3)
You need to create a new Server pointing to Weblogic Server 11g Release 1 (10.3.6) to
successfully publish the Oracle Service Bus configuration to the server. In order to do
this, you need to delete Oracle WebLogic Server 11g Release 1 (10.3.3).
To delete Oracle WebLogic Server 11g Release 1 (10.3.3), use the following steps:
1.
Select Oracle WebLogic Server 11g Release 1 (10.3.3), right click and select Delete
option.
2.
Uncheck Stop server(s) before deleting and click OK.
5.14.4.2 Creating Servers
You can deploy (publish) and test your Oracle Service Bus configuration on a running
server in Eclipse. When connected to a running server in development, you can also
connect to resources in the run-time environment such as JNDI resources and remote
EJBs.
If you have an existing Oracle WebLogic Server you want to connect to, the server
creation process simply involves you pointing at the existing server domain. If you
want to create a new server, the new server wizard lets you create one using the Oracle
Fusion Middleware Configuration Wizard.
To create a server in Eclipse, use the following steps:
1.
In the Oracle Service Bus perspective, select File > New > Server. The New Server
wizard appears.
2.
Select the server type/version you want to create or connect to.
3.
For Server's host name, enter localhost for a local server or enter the name or IP
address of the remote system hosting an existing server.
4.
The Server name is for display purposes in Eclipse.
5.
Click Next.
6.
For WebLogic home, click Browse and select the WebLogic_Server_HOME in the
Oracle Fusion Middleware installation where the server domain is to reside (or
already resides). The default WebLogic home directory is called wlserver_10.3.
For example, if you are creating a new server in MW_HOME_1, select the MW_HOME_
1/wlserver_10.3; or if you are connecting to an existing server domain in MW_
HOME_2, select the MW_HOME_2/wlserver_10.3.
You cannot reference a WebLogic_Server_HOME that is outside
of the server's installation MW_HOME, even if the external MW_HOME is the
same product version.
Note:
5-38 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Business Intelligence
7.
The Java home should be populated automatically. If you want to use a different
JRE, such as the default Oracle JRockit JRE, click Browse and select the JRE under
the same MW_HOME as the server.
8.
Click Next.
9.
Select whether the server is Local or Remote. Remote implies an existing remote
server.
■
If Local, either select an existing server in the Domain Directory field or click
the link to create a new domain. After creating a new domain, select it in the
Domain Directory field.
Set other options as desired, such as automatic publishing and debug mode.
For information on creating a new Oracle Service Bus domain, see
"Configuring Oracle Service Bus" in the Oracle Fusion Middleware Installation
Guide for Oracle Service Bus.
■
If Remote, enter the connection settings to an existing remote server.
10. Click Next.
11. Move any Oracle Service Bus configuration(s) you want to publish on the server
to the Configured pane. You can modify this targeting after you create the server
by right-clicking the server and selecting Add and Remove.
12. Click Finish. The new server appears in the Servers view in Eclipse, where you
can start, stop, and publish to the server.
5.15 Post-Patching Tasks for Oracle Business Intelligence
This section contains instructions for post-patching tasks for Oracle Business
Intelligence. It contains the following topics:
■
Section 5.15.1, "Enabling the WebLogic JMS Queue for WebCenter Content
Delivery Channel"
■
Section 5.15.2, "Upgrading Oracle Business Intelligence Code Grants"
■
Section 5.15.3, "Upgrading Oracle BI Presentation Catalogs"
■
Section 5.15.4, "Enabling bicontentserver Features"
■
Section 5.15.5, "Enabling Oracle Business Intelligence Composer Features"
■
Section 5.15.6, "Enabling JBIPS Features for the Smartview Client"
■
Section 5.15.7, "Re-encrypting the Essbase Studio Password"
■
Section 5.15.8, "Upgrading Oracle Real-Time Decisions"
■
Section 5.15.9, "Configuring the Business Intelligence Mobile App Designer Apps
Library"
Before you continue, make sure you have performed the tasks
in Section 5.9, "Post-Patching Tasks for System Components" to
upgrade your Oracle Business Intelligence system components.
Note:
Post-Patching Procedures 5-39
Post-Patching Tasks for Oracle Business Intelligence
5.15.1 Enabling the WebLogic JMS Queue for WebCenter Content Delivery Channel
You must execute the BIPCreateWCCQueue.py WLST script post upgrade to add the
new WebLogic JMS queue for WebCenter Content delivery channel that was added in
11.1.1.9.0.
The script is located in the following directory:
MW_HOME/Oracle_BI1/bifoundation/install/BIPCreateWCCQueue.py
To manually execute the script (if config.sh is not used):
cd <WLS_Home>/common/bin
./wlst.sh BIPCreateWCCQueue.py <WLS_Username> <WLS_Password> t3://<Adminserver_
host>:<Adminserver_port>
5.15.2 Upgrading Oracle Business Intelligence Code Grants
If you are upgrading to the latest version of Oracle Business Intelligence (BI) from
Release 11.1.1.3.0, you must run the bi-upgrade.py script in each Oracle BI domain.
This script configures the code grants necessary to ensure that SSL works correctly for
Oracle BI, and must be run even if SSL is not used.
To run the script on UNIX operating systems:
cd MW_HOME/oracle_common/common/bin
./wlst.sh BI_ORACLE_HOME/bin/bi-upgrade.py --bioraclehome BI_ORACLE_HOME
--domainhome bi_domain_home
To run the script on Windows operating systems:
cd MW_HOME\oracle_common\common\bin
wlst.cmd BI_ORACLE_HOME\bin\bi-upgrade.py --bioraclehome BI_ORACLE_HOME
--domainhome bi_domain_home
Replace BI_ORACLE_HOME with the full path to your Business Intelligence Oracle home
location, and replace bi_domain_home with the full path to your Business Intelligence
domain home location.
5.15.3 Upgrading Oracle BI Presentation Catalogs
When upgrading your Oracle Business Intelligence (BI) software from Release
11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x, you must manually upgrade your Oracle BI
Presentation Catalogs. Instructions are provided below:
1.
Stop Oracle BI Presentation Services using Oracle Enterprise Manager.
For details, see "Using Fusion Middleware Control to Start and Stop Oracle
Business Intelligence System Components and Java Components" in Oracle Fusion
Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise
Edition.
2.
Back up your Release 11.1.1.3.0, 11.1.1.5.0 or 11.1.1.6.x catalogs by using the 7-Zip
utility to create a compressed file for it.
3.
Create a backup copy of the instanceconfig.xml file.
The instanceconfig.xml file is located in the ORACLE_
INSTANCE/config/OracleBIPresentationServicesComponent/coreapplication_
obipsn (on UNIX operating systems) or ORACLE_
5-40 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Business Intelligence
INSTANCE\config\OracleBIPresentationServicesComponent\coreapplication_
obipsn (on Windows operating systems) directory.
4.
Change the upgradeAndExit option to true in the instanceconfig.xml file.
Find the following code:
<Catalog>
<UpgradeAndExit>false</UpgradeAndExit>
</Catalog>
Change it to the following:
<Catalog>
<UpgradeAndExit>true</UpgradeAndExit>
</Catalog>
5.
Start Oracle BI Presentation Services using the following OPMN command to
upgrade the catalogs:
opmnctl startproc ias-component=coreapplication_obipsn
For example, on a UNIX operating system:
cd ORACLE_INSTANCE/bin
./opmnctl startproc ias-component=coreapplication_obips1
On a Windows operating system:
cd ORACLE_INSTANCE\bin
opmnctl startproc ias-component=coreapplication_obips1
6.
After the catalogs are upgraded, edit the instanceconfig.xml file again and
change the upgradeAndExit option back to false.
7.
Restart Oracle BI Presentation Services using Fusion Middleware Control.
5.15.4 Enabling bicontentserver Features
If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.5.0), you
must perform the following if you want to enable the bicontentserver configuration
template features:
1.
Make sure all processes in the domain are stopped, including all Oracle instances,
the Administration Server, all Managed Servers, and Node Manager.
2.
Start the Configuration Wizard.
On UNIX operating systems:
cd WLHOME/common/bin
where WLHOME is the directory in which WebLogic Server is installed.
./config.sh
On Windows operating systems:
cd WLHOME\common\bin
config.bat
3.
On the Welcome screen, select Extend an existing WebLogic domain.
4.
On the Select a WebLogic Domain Directory screen, select the location of your
existing Oracle BI domain.
Post-Patching Procedures 5-41
Post-Patching Tasks for Oracle Business Intelligence
5.
On the Select Extension Source screen, select Extend my domain using an existing
extension template and select the following:
On UNIX operating systems:
ORACLE_HOME/common/templates/applications/oracle.bicontentserver_template_
11.1.1.jar
On Windows operating systems:
ORACLE_HOME\common\templates\applications\oracle.bicontentserver_template_
11.1.1.jar
6.
Continue with the remainder of the Configuration Wizard screens to apply this
template.
7.
After the template is applied, restart all Oracle Instances, the Administration
Server, Managed Servers, and Node Manager.
5.15.5 Enabling Oracle Business Intelligence Composer Features
If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x), you
must perform the following if you want to enable the Oracle BI Composer or Oracle BI
Composer Runtime configuration template features:
1.
Make sure all processes in the domain are stopped, including all Oracle instances,
the Administration Server, all Managed Servers, and Node Manager.
2.
Start the Configuration Wizard.
On UNIX operating systems:
cd WLHOME/common/bin
where WLHOME is the directory in which WebLogic Server is installed.
./config.sh
On Windows operating systems:
From the Start Menu, launch the Configuration Wizard for WebLogic from the
WebLogic Server\Tools\WebLogic Server menu option.
3.
On the Welcome screen, select Extend an existing WebLogic domain.
4.
On the Select a WebLogic Domain Directory screen, select the location of your
existing Oracle BI domain.
5.
On the Select Extension Source screen, select Extend my domain using an existing
extension template and enter the location of the oracle.bicomposer_template_
11.1.1.jar file.
On Unix operating systems enter a command such as the following:
ORACLE_HOME/common/templates/applications/oracle.bicomposer_template_
11.1.1.jar
6.
Continue with the remainder of the Configuration Wizard screens to apply this
template.
7.
After the template is applied, restart all Oracle Instances, the Administration
Server, Managed Servers, and Node Manager.
5-42 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Business Intelligence
After you perform the steps in this section, you must edit an
MBean to enable Oracle BI Composer. For information, see "Manually
Enabling BI Composer" in Oracle Fusion Middleware Upgrade Guide for
Oracle Business Intelligence.
Note:
5.15.6 Enabling JBIPS Features for the Smartview Client
If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x), and
you want to enable the Oracle BI JBIPS configuration template features for the
Smartview client, you must perform the following:
1.
Make sure all processes in the domain are stopped, including all Oracle instances,
the Administration Server, all Managed Servers, and Node Manager.
2.
Start the Configuration Wizard.
On UNIX operating systems:
cd WLHOME/common/bin
where WLHOME is the directory in which WebLogic Server is installed.
./config.sh
On Windows operating systems:
From the Start Menu launch the Configuration Wizard for WebLogic from the
Programs > Oracle WebLogic > WebLogic Server > Tools > Configuration
Wizard menu option.
3.
On the Welcome screen, select Extend an existing WebLogic domain.
4.
On the Select a WebLogic Domain Directory screen, select the location of your
existing Oracle BI domain.
5.
On the Select Extension Source screen, select Extend my domain automatically to
support the following added products and select Oracle JBIPS.
6.
Continue with the remainder of the Configuration Wizard screens to apply this
template.
7.
Review the Configuration Summary screen and verify that the JBIPS Enterprise
Web application and the following JBIPS shared libraries are listed:
■
oracle.bi.jbips
■
oracle.bi.jbips.commons
■
oracle.bi.jbips.soap
NOTE: The JBIPS Web application and JBIPS shared libraries must be deployed to
the same target as Analytics web application. The default target is "bi_cluster".
8.
After the template is applied, restart all Oracle Instances, the Administration
Server, Managed Servers, and Node Manager.
You should see "jbips (11.1.1)" Enterprise Application and the JBIPS shared
libraries in the list of deployed modules in the Weblogic Administration Console.
5.15.7 Re-encrypting the Essbase Studio Password
If you are upgrading Oracle Business Intelligence from 11g Release 1 (11.1.1.x) and
your BI installation includes Essbase Studio, then you must manually re-encrypt the
Essbase Studio password using the Essbase Studio password encryption utility.
Post-Patching Procedures 5-43
Post-Patching Tasks for Oracle Business Intelligence
For more information, see "Encrypting the Catalog Password Manually In BI
Installations" in the Oracle Essbase Studio User's Guide.
5.15.8 Upgrading Oracle Real-Time Decisions
This section describes how to upgrade Oracle Real-Time Decisions (RTD) to the latest
patch set. The following steps are required only if you are patching from 11g Release 1
(11.1.1.3.0); you do not need to perform these steps if you are patching from 11g
Release 1 (11.1.1.5.0).
■
Section 5.15.8.1, "Upgrading the rtd_ils Resource Type Using WLST"
■
Section 5.15.8.2, "Adding Permissions to the BIAdministrator Principle Using EM"
■
Section 5.15.8.3, "Removing JMS"
5.15.8.1 Upgrading the rtd_ils Resource Type Using WLST
Perform the following to add actions to the rtd_ils resource type:
1.
Navigate to the MW_HOME/oracle_common/common/bin (on UNIX operating
systems) or MW_HOME\oracle_common\common\bin (on Windows operating systems)
directory.
2.
Launch the WebLogic Scripting Tool (WLST).
On UNIX operating systems:
./wlst.sh
On Windows operating systems:
wlst.cmd
3.
Connect to the WebLogic Server using the connect() command:
connect('adminuser', 'adminuser_password', 't3://admin_server_host:admin_
server_port')
Replace adminuser and adminuser_password with the name and password of the
Administrator you provided during the Oracle BI installation. Replace admin_
server_host and admin_server_port with the host name and port number of the
system where Oracle WebLogic Server is running. Below is a sample command:
connect('exampleuser', 'examplepassword', 't3://examplehost:7001')
4.
List all resources of the resource type "rtd_ils" using the following command:
listResources(appStripe="obi", type="rtd_ils")
This will list all ILS's deployed to the RTD server. For example, if the sample ILS
CrossSell was deployed to your RTD server, you would see the following:
[Name: CrossSell Type: rtd_ils DisplayName: CrossSell Description: CrossSell ]
5.
Delete all resources of resource type "rtd_ils" using the following command:
deleteResource(appStripe="obi", name=resource_name, type="rtd_ils")
For example, the following command would delete the CrossSell resource:
deleteResource(appStripe="obi", name="CrossSell", type="rtd_ils")
5-44 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Business Intelligence
6.
Run the listResources() command again to ensure all the resources have been
deleted:
listResources(appStripe="obi", type="rtd_ils")
There should be no resources listed.
7.
Delete the resource type "rtd_ils":
deleteResourceType(appStripe="obi", resourceTypeName="rtd_ils")
8.
Create a resource type "rtd_ils" using the following createResourceType()
command:
createResourceType(appStripe="obi",
resourceTypeName="rtd_ils",
displayName="ILS",
description="Inline Service name",
matcher="oracle.security.jps.ResourcePermission",
allowedActions="choice_editor,decision_service:stress,open_
service:write,decision_service:normal,open_service:read,deploy_
service,download_service,clear_choice_history,clear_statistics,clear_
study,clear_all_operational_data,delete_service,unlock_service,clear_model",
delimiter=",")
9.
Disconnect from Oracle WebLogic Server:
disconnect()
10. Exit from the WebLogic Scripting Tool:
exit()
5.15.8.2 Adding Permissions to the BIAdministrator Principle Using EM
The steps in this section need to be performed if you are using the BIAdministrator
principle included with the product, or if you have replaced the BIAdministrator
principle included with the product with your own principle:
1.
Start Fusion Middleware Control using the following syntax:
http://admin_server_host:admin_server_port/em
2.
In the left tree view, select Weblogic Domain / bifoundation_domain.
3.
In the content pane, select Security/Application Policies from the drop down
"WebLogic Domain".
4.
Check Select Application Stripe to Search, and select "obi" from its drop down
list.
5.
Leave the Principal and Permissions blank.
6.
Click the Search button next to the Permission field.
7.
From the search result, click on the Principal "BIAdministrator" (or the name of
your own principle if you are not using "BIAdministrator").
8.
Click the Edit button.
9.
In the Edit Application Grant pane, go to the Permissions section and click the
Add button.
10. In the Add Permission dialog, under the Customize section, add the following
entries:
Post-Patching Procedures 5-45
Post-Patching Tasks for Oracle Data Integrator
Permission Class: oracle.security.jps.ResourcePermission
Resource Name: resourceType=rtd_ils,resourceName=_all_
Permission Actions: clear_choice_history,clear_statistics,clear_study,clear_
all_operational_data,delete_service,unlock_service,clear_model
11. Click OK in the Add Permission dialog.
12. Click OK in the Edit Application Grant pane.
5.15.8.3 Removing JMS
In earlier releases, Oracle RTD relied on JMS for its intra-member cluster
communication. In the latest release, JMS is replaced with JRF web services. This is an
optional step and no functionality will be affected if you choose not to perform this
step.
To remove JMS for Oracle RTD:
1.
Using a browser, connect to the Administration Server Console:
http://admin_server_host:admin_server_port/console
2.
Click Lock & Edit.
3.
Under Domain Structure, expand Services > Messaging.
4.
Click JMS Modules.
5.
On JMS Modules table in the right pane, select RTDJMSMODULE.
6.
Click the Delete button, then click the Yes button to confirm.
7.
On the left pane, click JMS Servers (under Services > Messaging).
8.
On the JMS Servers table on the right pane, select RTDJmsServer.
9.
Click the Delete button, then click the Yes button to confirm.
10. Click the Activate Changes button.
5.15.9 Configuring the Business Intelligence Mobile App Designer Apps Library
The BI Mobile Apps Library is used to make applications available to your users to run
on their mobile devices. You will have to configure this library after an upgrade if you
have not previously installed Business Intelligence (BI) Mobile App Designer.
For information about the Apps Library and set up steps, see "About the Apps
Library" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence
Mobile App Designer.
5.16 Post-Patching Tasks for Oracle Data Integrator
This section contains instructions for post-patching tasks for Oracle Data Integrator. It
contains the following topics:
■
Section 5.16.1, "Finalizing Repository Patching"
■
Section 5.16.2, "Reconfiguring the Java EE Agent"
■
Section 5.16.3, "Reconfiguring the ODI Standalone Agent"
■
Section 5.16.4, "Reconfiguring Oracle Enterprise Manager Properties"
■
Section 5.16.5, "Reconfiguring the ODI Console"
5-46 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Data Integrator
■
Section 5.16.6, "Adding the Version Number for the odi-sdk-ws Application in
config.xml"
5.16.1 Finalizing Repository Patching
After you have patched the Oracle Data Integrator schemas in your database
(Chapter 4, "Upgrading Your Schemas with Patch Set Assistant"), you must upgrade
the following repository objects (technologies, profiles, knowledge modules), which
are not upgraded with Patch Set Assistant:
■
Technology Changes
–
Added: ComplexFile and Groovy
–
Changed: Oracle
*
Natural keyword join was added
*
Join capability was extended to BOTH
*
Default table name prefixes were added
–
Changed: Teradata
–
Changed: PostgreSQL
–
Changed: Netezza
–
Changed: OracleBI
–
Changed: Hypersonic In-Memory Engine
–
Changed: PostgreSQL supports SQL for retrieving sequences
■
Language Changes: Groovy was added
■
Profile Changes
Changes were made to LoadPlan support in the following profiles:
■
–
[NG] DESIGNER
–
[NG] REPOSITORY EXPLORER
–
[NG] VERSION ADMIN
–
OPERATOR
–
SECURITY_ADMIN
Knowledge Modules
LKM File to Oracle (SQLLDR) works after removing 'import javaos' from KM step
'call sqlldr'. The old LKM no longer works with an upgraded Jython version.
For more information about how to upgrade these repository objects, see
"Reconfiguring ODI After an Upgrade" in Oracle Fusion Middleware Upgrade Guide for
Oracle Data Integrator.
5.16.2 Reconfiguring the Java EE Agent
NOTE: If ODI is already deployed in the domain, then there is no need to re-run
configuration wizard after upgrading to ODI 11.1.1.9.0.
By default, ODI ships a static Java EE Agent deployment template. To reconfigure the
Java EE agent:
Post-Patching Procedures 5-47
Post-Patching Tasks for Oracle Data Integrator
1.
Run the Configuration Wizard. On the Select Domain Source screen, select the
appropriate Oracle Data Integrator Agent template for your environment.
2.
On UNIX operating systems, check user_projects/bin/setDomainEnv.sh for the
following line:
-Dodi.oracle.home=${ODI_ORACLE_HOME}
On Windows operating systems, check user_projects\bin\setDomainEnv.cmd for
the following line:
-Dodi.oracle.home=%ODI_ORACLE_HOME%
On either operating system, if this line is not present, add it to the EXTRA_JAVA_
PROPERTIES parameter.
3.
After the upgrade, make sure the admin server and managed servers are restarted
and verify that they are running
ODI also enables you to generate a Java EE agent deployment template from ODI
Studio. You can customize the Java EE agent with additional data sources and
libraries. To do so:
1.
Undeploy the previous version Java EE agent from your domain.
For more information, see "Managing Deployed Applications" in Deploying
Applications to Oracle WebLogic Server.
2.
Using ODI Studio or the command line script to generate equivalent Java EE agent
template with required data sources and additional libraries.
For more information on data source declaration, deployment and template
generation in ODI Studio, see "Java EE Agent" in the Developer's Guide for Oracle
Data Integrator.
3.
Run the Configuration Wizard. On the Select Domain Source screen, select Oracle
Data Integrator – Agent Libraries– 11.1.1.0 to deploy the template.
4.
Run the Configuration Wizard a second time, and on the Select Domain Source
screen, deploy the generated version 11.1.1.9.0 ODI Java EE agent template to the
domain.
5.16.3 Reconfiguring the ODI Standalone Agent
To reconfigure the ODI standalone agent:
1.
Make sure you have backed up the necessary files and directories as described in
"Section 3.4.6, "Backing Up Additional Configuration Information".
2.
Run the Oracle Data Integrator installer.
On the Configure Repositories Install screen, choose Skip Repository Creation.
3.
After the installation is complete:
■
■
Restore the ODI_HOME/oracledi/agent/bin/odiparams.sh (on UNIX
operating systems) or ODI_HOME\oracledi\agent\bin\odiparams.bat (on
Windows operating systems) file.
Restore the ODI_HOME/oracledi/agent/drivers (on UNIX operating systems)
or ODI_HOME\oracledi\agent\drivers (on Windows operating systems)
directory.
5-48 Oracle Fusion Middleware Patching Guide
Post-Patching Tasks for Oracle Data Integrator
For more information, see "Stopping a Standalone Agent" and "Manually Configuring
and Starting the Standalone Agent" in Oracle Fusion Middleware Installation Guide for
Oracle Data Integrator.
5.16.4 Reconfiguring Oracle Enterprise Manager Properties
After you have patched Oracle Data Integrator, some of the properties in Oracle
Enterprise Manager are lost. To restore these properties, set the following property
before starting the Managed Server on which the Oracle Data Integrator Console is
deployed:
set JAVA_OPTIONS="-Doracle.odi.repex.view.main.init.skipem=false"
5.16.5 Reconfiguring the ODI Console
If the domain created in Release 11.1.1.3.0 contains odiconsole components,
reconfigure the odiconsole application as follows:
1.
Extend the domain with Oracle Shared SDK Library 11.1.1.0 and target the
deployment to odi_server1.
2.
Set the CLASSPATH by running the Weblogic_Home/server/bin/setWLSEnv.sh (on
UNIX operating systems) or Weblogic_Home\server\bin\setWLSEnv.cmd (on
Windows operating systems) script.
3.
Start the Administration Server and the odi_server1 Managed Server.
4.
Redeploy the odiconsole application using the following command:
java weblogic.Deployer -url administration_server_url -username administration_
server_username -password administration_server_password -targets odi_server_
name -name odi_console_name –redeploy
For example:
java weblogic.Deployer -url t3://examplehost.com:7001 -username exampleuser
-password examplepassword -targets odi_server1 -name odiconsole –redeploy
5.16.6 Adding the Version Number for the odi-sdk-ws Application in config.xml
As of 11g Release 1 (11.1.1.6.0), the odi-sdk-ws application was upgraded to introduce
a version number. This version number must be added to the config.xml file prior to
starting the Administration Server or Managed Servers in the domain for Releases
11.1.1.3.0, 11.1.1.4.0, 11.1.1.5.0, 11.1.1.7.0 to Release 11.1.1.9.0.
To do this:
1.
Edit the user_projects/config/config.xml (on UNIX operating systems) or
user_projects\config\config.xml (on Windows operating systems) file.
2.
Change the following line:
<name>odi-sdk-ws</name>
to add a version number, as shown below:
<name>odi-sdk-ws#11.1.1.9.0.0</name>
3.
Start or restart the Administration Server and Managed Servers in the domain.
Post-Patching Procedures 5-49
Post-Patching Tasks for Oracle Data Integrator
5-50 Oracle Fusion Middleware Patching Guide
6
Patching Oracle WebCenter Portal
6
This chapter describes how to patch your existing Oracle WebCenter Portal
installations to release 11.1.1.9.0.
[6]
The WebCenter Portal Framework technology is fully
supported in Oracle WebCenter Portal 11g R1 release. However, it is in
maintenance mode since release 11.1.1.7.0. Any new features, such as
Portal Builder and mobile web support added in the WebCenter Portal
application in release 11.1.1.8.0, are not available in Portal Framework
applications.
Note:
If you are running a Portal Framework application from release
11.1.1.6.0, 11.1.1.7.0, 11.1.1.8.x, and 11.1.1.9.x and want to benefit from
new WebCenter Portal new features and capabilities, Oracle
recommends that you migrate your Portal Framework application as a
portal to the WebCenter Portal application. For information, see
"Migrating a Portal Framework Application to WebCenter Portal" in
Oracle Fusion Middleware Administering Oracle WebCenter Portal.
This chapter includes the following topics:
■
New Product Names for Oracle WebCenter and Oracle Enterprise Content
Management Suite
■
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
■
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
■
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
■
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
■
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
■
Patching an Oracle WebCenter 11.1.1.1.0 Installation
■
Troubleshooting Issues
■
Pre-Patching Tasks for Oracle WebCenter Portal
■
Post Patching Tasks for Oracle WebCenter Portal
Patching Oracle WebCenter Portal
6-1
New Product Names for Oracle WebCenter and Oracle Enterprise Content Management Suite
Note: Oracle recommends that all products must be patched to their
latest released versions. There is no particular order in which the
products must be patched unless specified.
Chapter 3 provides instructions for patching your existing Oracle
Fusion Middleware software to the latest version, whereas this
chapter provides instructions for patching Oracle WebCenter Portal.
Many of the steps listed in this chapter refer back to Chapter 3 or other
chapters of this guide. If you have already completed any generic
steps, like performing pre-patching generic tasks, patching Fusion
Middleware products other than Oracle WebCenter Portal, or
updating schemas, as per instructions in Chapter 3, you may skip
those steps.
For an Oracle WebCenter Portal instance patched from an
earlier release that used the Folders_g folder service, you can choose
to continue with Folders_g or migrate to the FrameworkFolders folder
service. Oracle recommends that you enable the FrameworkFolders
component for better performance and so as to be able to use any new
Content Server features. For information, see the "Migrating Folders_g
to FrameworkFolders" appendix in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
Important:
6.1 New Product Names for Oracle WebCenter and Oracle Enterprise
Content Management Suite
Oracle WebCenter and Oracle Enterprise Content Management Suite have been
rebranded (renamed) from Release 11.1.1.6.0 onward. Table 6–1 lists the old product
and feature names, and the revised names in release 11.1.1.6.0, 11.1.1.7.0, and 11.1.1.9.0.
This chapter uses the rebranded product names where
appropriate. The old product terminology has been used wherever an
old feature is discussed.
Note:
Table 6–1
Onward
Mapping Old Terminology with the Terminology Used From Release 11.1.1.6.0
Name in Release 11.1.1.6.0
and 11.1.1.7.0
Name in Release 11.1.1.8.x
and 11.1.1.9.0
Oracle WebCenter
Oracle WebCenter Portal
Oracle WebCenter Portal
Oracle WebCenter Spaces
Oracle WebCenter Portal: Spaces WebCenter Portal
Oracle Enterprise Content
Management Suite
Oracle WebCenter Content
Oracle WebCenter Content
Oracle Universal Content
Management (Oracle UCM)
Oracle WebCenter Content
(short name WebCenter
Content)
Oracle WebCenter Content
(short name WebCenter
Content)
Oracle Content Server
Oracle WebCenter Content
Server (short name Content
Server)
Oracle WebCenter Content
Server (short name Content
Server)
Old Name
Product Name Changes
6-2 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
Table 6–1 (Cont.) Mapping Old Terminology with the Terminology Used From Release
11.1.1.6.0 Onward
Old Name
Name in Release 11.1.1.6.0
and 11.1.1.7.0
Name in Release 11.1.1.8.x
and 11.1.1.9.0
WebCenter Portal application
No umbrella term used
Feature Name Changes in
Documentation
WebCenter application
(Umbrella term for: Framework
applications, Portlet Producer
applications, and the Spaces
application)
WebCenter Portal
application/WebCenter
custom application
Framework application/
WebCenter Portal: Framework
application
Portal Framework application
Group Space
workflows/WebCenter
Spaces workflows
Spaces workflows
WebCenter Portal workflows
Personal Space
Home space
Home portal
Group Space/Space
Space
Portal
WebCenter domain
WebCenter Portal domain
WebCenter Portal domain
WebCenter Spaces
Spaces/Spaces application
WebCenter Portal
Oracle WebCenter Capture 11.1.1.8.x is renamed to Oracle
WebCenter Enterprise Capture in release 11.1.1.9.0.
Note:
6.2 Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
Figure 6–2 illustrates the steps required to patch an Oracle WebCenter Portal Release
11.1.1.8.0 or 11.1.1.8.3 installation to Release 11.1.1.9.0. Table 6–3 describes each of these
steps in detail. Click the required steps in the table to navigate to the information for
each step.
Note: Many of the steps listed in Figure 6–2 and Table 6–3 refer back
to chapter 3 or other chapters of this guide. If you have already
completed any generic steps, like performing pre-patching generic
tasks, patching Fusion Middleware products other than WebCenter
Portal, or updating schemas, as per instructions in Chapter 3, you may
skip those steps.
In Figure 6–2, Oracle WebCenter Portal-specific steps are highlighted
in green.
Patching Oracle WebCenter Portal
6-3
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
The WebCenter Portal Framework technology is fully
supported in Oracle WebCenter Portal 11g R1 release. However, it is in
maintenance mode since release 11.1.1.7.0. Any new features, such as
Portal Builder and mobile web support added in the WebCenter Portal
application in release 11.1.1.8.0, are not available in Portal Framework
applications.
Note:
If you are running a Portal Framework application from release
11.1.1.8.x and want to benefit from new WebCenter Portal features and
capabilities, Oracle recommends that you migrate your Portal
Framework application as a portal to the WebCenter Portal
application. For information, see "Migrating a Portal Framework
Application to WebCenter Portal" in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
Figure 6–1 Patching Oracle WebCenter Portal 11.1.1.8.x to Release 11.1.1.9.0
6-4 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
Table 6–2
Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.8.x
Task
Mandatory or
Optional?
Description
Links
Section 6.9.1,
"Exporting
Deployment
Descriptor for Portlet
Producer
Applications Secured
with OWSM"
Export Web service deployment
descriptors for portlet producers that are
secured with OWSM security policies
Mandatory
If Oracle WebCenter Portal's
Services Portlets producer or
any custom portlet producers
are deployed and secured
with OWSM security
policies, export the Web
service deployment
descriptors for those portlet
producers to a Java Archive
(JAR) file.
Perform the general pre-patching tasks:
Mandatory
Section 3.4, "General
Before patching Oracle
WebCenter Portal, make sure Pre-Patching Tasks"
your system environment
and configuration meet the
minimum requirements and
the backups are in place.
Also, you must patch Oracle
WebLogic Server to the latest
supported release.
■
■
■
■
■
■
■
Review system requirement,
certification, and interoperability
information
Stop the servers and processes
Back up your Middleware Home,
Domain Home, and Oracle instances
Back up your database and database
schemas
If you are patching your
software in silent mode,
rename the emCCR file.
Back up additional configuration
information
Patch Oracle WebLogic Server
Rename the emCCR file for silent
patching
Download the installer for Oracle
WebCenter Portal and Oracle WebCenter
Content
Download the Oracle
WebCenter Portal installer,
which is a full installer that
also functions as an update
installer. Also download
installer for Oracle
WebCenter Content.
Section 3.5,
"Downloading the
Installer"
Note: If you have already
downloaded product
installers as per instructions
in Chapter 3, you may skip
this step.
Run the WebCenter Portal installer to
patch to Release 11.1.1.9.0
Patch Oracle WebCenter Content
Mandatory
Mandatory
Run the WebCenter Portal
11.1.1.9.0 installer. While
applying the patch set,
specify your existing Oracle
Middleware home and
WebCenter Portal Oracle
home locations.
Run the Oracle WebCenter
Content product installer. If
you have already patched it
as per instructions in chapter
3, you may skip this step.
■
■
Section 3.6.1,
"Starting the
Installer"
Section 3.6.2,
"Applying the
Patch Set"
Section 3.6.1,
"Starting the Installer"
and Section 3.6.2,
"Applying the Patch
Set"
Patching Oracle WebCenter Portal
6-5
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
Table 6–2 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.8.x
Task
Mandatory or
Optional?
If required, patch to Oracle SES 11.2.2.2.
Mandatory
For your patched or any existing Oracle
SES instance, install the new version of
Oracle WebCenter Portal's Document
Service Manager
Description
Oracle WebCenter Portal
release 11.1.1.9.0 supports
Oracle SES 11.2.2.2, which
provides faceted search.
Oracle recommends using
Oracle SES release 11.2.2.2 for
best performance and latest
search features.
For your patched or any
existing Oracle SES
installation, you must install
the new version of Oracle
WebCenter Portal's
Document Service Manager
and configure Oracle SES
facets and sorting attributes.
Note: Installing Oracle SES
11.2.2.2 or other supported
versions in the same Fusion
Middleware home as Oracle
WebCenter Portal 11.1.1.7.0
or later is not supported. The
recommended and
supported topology is to
install Oracle SES in a
separate Fusion Middleware
home. That is, treat Oracle
SES as a remote service for
Oracle WebCenter Portal.
Update the WEBCENTER, ACTIVITIES,
DISCUSSIONS , and DISCUSSIONS_CRAWLER
schemas
Mandatory
■
■
For patching to
Oracle SES
11.2.2.2, see
Oracle Secure
Enterprise Search
Installation and
Upgrade Guide in
the Secure
Enterprise Search
Online
Documentation
Library 11g
Release 2
(11.2.2.2) on
OTN.
For information
about installing
the new version
of Oracle
WebCenter
Portal's
Document
Service Manager,
see the "Oracle
SES Installation"
section in Oracle
Fusion
Middleware
Installation Guide
for Oracle
WebCenter Portal.
Use the Patch Set Assistant to Chapter 4,
"Upgrading Your
update Oracle WebCenter
Schemas with Patch
Portal-related schemas.
Set Assistant"
Before running Patch Set
Assistant, check to make sure
that your database is up and
running and the schema you
want to upgrade is at the
version supported for
upgrade.
Note: Check whether
schemas of other patched
products need to be updated.
You can update all the
required schemas at this
stage. You may skip this step
if you have already patched
schemas listed in Table 4–1,
" Schemas That Require
Upgrading for the Latest
Release".
6-6 Oracle Fusion Middleware Patching Guide
Links
Patching an Oracle WebCenter Portal 11.1.1.8.x Installation
Table 6–2 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.8.x
Task
Perform the following post-patching task
for WebCenter Portal:
■
■
■
■
■
■
■
■
Start the administration server and
managed servers
Run
upgradeWebCenterPermissions()
Import Web service deployment
descriptors for portlet producers
secured with OWSM security policies
Reset search customizations if using
Oracle SES 11.2.2.2
Update OAM policies if OAM is
patched to release 11.1.2.2.0
Run setProfileConfig to restore
Profile page customizations
Remove the -noverify flag if present
Choose whether to continue using
Folders_g or migrate to
FrameworkFolders
Note: You do not need to perform
post-patching task for WebCenter Portal if
you are migrating a Portal Framework
application as a portal on the portal server.
Mandatory or
Optional?
Mandatory
Description
Links
Start the administration
server and managed servers,
and run the
upgradeWebCenterPermissio
ns() WLST command to
update permissions for
WebCenter Portal.
Import the Web service
deployment descriptors if
Oracle WebCenter Portal's
Services Portlets producer or
any custom portlet producers
were deployed and secured
with OWSM security policies
in your prepatched instance.
■
■
■
If you patched to Oracle SES
11.2.2.2, reset search
customizations.
If OAM is patched to release
11.1.2.2.0, update the OAM
policies. You must restore
Profile page customizations.
Further, remove the -noverify
flag if present in
setDomainEnv.sh or
setDomainEnv.cmd.
In your patched instance,
you can continue to use the
Folders_g component or
choose to migrate to the
FrameworkFolders interface.
Oracle recommends that you
migrate to
FrameworkFolders.
■
■
■
■
■
Section 3.8,
"Starting the
Servers and
Processes"
Section 6.10.9,
"Running the
upgradeWebCent
erPermissions
WLST
Command"
Section 6.10.1,
"Importing Web
Service
Deployment
Descriptors for
Portlet Producers
Secured with
OWSM"
Section 6.10.10,
"Resetting Search
Customizations"
Section 6.10.11,
"Updating
Resource
Protection Level
in OAM
11.1.2.2.0"
Section 6.10.12,
"Restoring
Profile Page
Customizations"
Section 6.10.13,
"Removing the
-noverify Flag"
"Migrating
Folders_g to
FrameworkFolde
rs" in Oracle
Fusion
Middleware
Administering
Oracle WebCenter
Portal
Patching Oracle WebCenter Portal
6-7
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
Table 6–2 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.8.x
Mandatory or
Optional?
Task
Description
Links
Perform post-patching tasks for other
Fusion Middleware products
Mandatory
Perform any post patching
tasks required for Oracle
WebCenter Content or other
products
Section 5.8,
"Post-Patching Tasks
If Your Starting Point
is Release 11.1.1.8"
Start/restart the servers and processes
Mandatory
Start your Oracle Fusion
Middleware environment.
This involves starting your
Oracle WebLogic Server,
Administration Server,
managed servers, node
manager, OPMN, and all
system components.
Section 3.8, "Starting
the Servers and
Processes"
Note: If you had started any
managed servers before, you
must restart them now.
Verify Oracle WebCenter Portal 11.1.1.9.0
installation
Mandatory
Verify your patched Oracle
WebCenter Portal instance by
trying to access various URLs
like for Administration
Server and WebCenter Portal.
"Verifying Your
Configuration"
section in Oracle
Fusion Middleware
Installation Guide for
Oracle WebCenter
Portal
6.3 Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
Figure 6–2 illustrates the steps required to patch an Oracle WebCenter Portal Release
11.1.1.7.0 installation to Release 11.1.1.9.0. Table 6–3 describes each of these steps in
detail. Click the required steps in the table to navigate to the information for each step.
Note: Many of the steps listed in Figure 6–2 and Table 6–3 refer back
to chapter 3 or other chapters of this guide. If you have already
completed any generic steps, like performing pre-patching generic
tasks, patching Fusion Middleware products other than WebCenter
Portal, or updating schemas, as per instructions in Chapter 3, you may
skip those steps.
In Figure 6–2, Oracle WebCenter Portal-specific steps are highlighted
in green.
6-8 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
The WebCenter Portal Framework technology is fully
supported in Oracle WebCenter Portal 11g R1 release. However, it is in
maintenance mode since release 11.1.1.7.0. Any new features, such as
Portal Builder and mobile web support added in the WebCenter Portal
application in release 11.1.1.8.0, are not available in Portal Framework
applications.
Note:
If you are running a Portal Framework application from release
11.1.1.7.0 and want to benefit from new WebCenter Portal features and
capabilities, Oracle recommends that you migrate your Portal
Framework application as a portal to the WebCenter Portal
application. For information, see "Migrating a Portal Framework
Application to WebCenter Portal" in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
Figure 6–2 Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.7.0
Patching Oracle WebCenter Portal
6-9
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
Table 6–3
Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.7.0
Task
Mandatory or
Optional?
Description
Links
Section 6.9.1,
"Exporting
Deployment
Descriptor for Portlet
Producer
Applications Secured
with OWSM"
Export Web service deployment
descriptors for portlet producers that are
secured with OWSM security policies
Mandatory
If Oracle WebCenter Portal's
Services Portlets producer or
any custom portlet producers
are deployed and secured
with OWSM security
policies, export the Web
service deployment
descriptors for those portlet
producers to a Java Archive
(JAR) file.
Perform the general pre-patching tasks:
Mandatory
Section 3.4, "General
Before patching Oracle
WebCenter Portal, make sure Pre-Patching Tasks"
your system environment
and configuration meet the
minimum requirements and
the backups are in place.
Also, you must patch Oracle
WebLogic Server to the latest
supported release.
■
■
■
■
■
■
■
Review system requirement,
certification, and interoperability
information
Stop the servers and processes
Back up your Middleware Home,
Domain Home, and Oracle instances
Back up your database and database
schemas
If you are patching your
software in silent mode,
rename the emCCR file.
Back up additional configuration
information
Patch Oracle WebLogic Server
Rename the emCCR file for silent
patching
Download the installer for Oracle
WebCenter Portal and Oracle WebCenter
Content
Download the Oracle
WebCenter Portal installer,
which is a full installer that
also functions as an update
installer. Also download
installer for Oracle
WebCenter Content.
Section 3.5,
"Downloading the
Installer"
Note: If you have already
downloaded product
installers as per instructions
in Chapter 3, you may skip
this step.
Run the WebCenter Portal installer to
patch to Release 11.1.1.9.0
Patch Oracle WebCenter Content
Mandatory
Mandatory
6-10 Oracle Fusion Middleware Patching Guide
Run the WebCenter Portal
11.1.1.9.0 installer. While
applying the patch set,
specify your existing Oracle
Middleware home and
WebCenter Portal Oracle
home locations.
Run the Oracle WebCenter
Content product installer. If
you have already patched it
as per instructions in chapter
3, you may skip this step.
■
■
Section 3.6.1,
"Starting the
Installer"
Section 3.6.2,
"Applying the
Patch Set"
Section 3.6.1,
"Starting the Installer"
and Section 3.6.2,
"Applying the Patch
Set"
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
Table 6–3 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.7.0
Task
If required, patch to Oracle SES 11.2.2.2.
For your patched or any existing Oracle
SES instance, install the new version of
Oracle WebCenter Portal's Document
Service Manager
Mandatory or
Optional?
Mandatory
Description
Links
Oracle WebCenter Portal
release 11.1.1.9.0 supports
Oracle SES 11.2.2.2, which
provides faceted search.
Oracle recommends using
Oracle SES release 11.2.2.2 for
best performance and latest
search features.
For your patched or any
existing Oracle SES
installation, you must install
the new version of Oracle
WebCenter Portal's
Document Service Manager
and configure Oracle SES
facets and sorting attributes.
Note: Installing Oracle SES
11.2.2.2 or other supported
versions in the same Fusion
Middleware home as Oracle
WebCenter Portal 11.1.1.7.0
or later is not supported. The
recommended and
supported topology is to
install Oracle SES in a
separate Fusion Middleware
home. That is, treat Oracle
SES as a remote service for
Oracle WebCenter Portal.
Update the WEBCENTER, ACTIVITIES,
DISCUSSIONS , and DISCUSSIONS_CRAWLER
schemas
Mandatory
■
■
For patching to
Oracle SES
11.2.2.2, see
Oracle Secure
Enterprise Search
Installation and
Upgrade Guide in
the Secure
Enterprise Search
Online
Documentation
Library 11g
Release 2
(11.2.2.2) on
OTN.
For information
about installing
the new version
of Oracle
WebCenter
Portal's
Document
Service Manager,
see the "Oracle
SES Installation"
section in Oracle
Fusion
Middleware
Installation Guide
for Oracle
WebCenter Portal.
Use the Patch Set Assistant to Chapter 4,
"Upgrading Your
update Oracle WebCenter
Schemas with Patch
Portal-related schemas.
Set Assistant"
Before running Patch Set
Assistant, check to make sure
that your database is up and
running and the schema you
want to upgrade is at the
version supported for
upgrade.
Note: Check whether
schemas of other patched
products need to be updated.
You can update all the
required schemas at this
stage. You may skip this step
if you have already patched
schemas listed in Table 4–1,
" Schemas That Require
Upgrading for the Latest
Release".
Patching Oracle WebCenter Portal 6-11
Patching an Oracle WebCenter Portal 11.1.1.7.0 Installation
Table 6–3 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.7.0
Task
Perform the following post-patching task
for WebCenter Portal:
■
■
■
■
■
■
■
■
Mandatory or
Optional?
Mandatory
Start the administration server and
managed servers
Run
upgradeWebCenterPermissions()
Import Web service deployment
descriptors for portlet producers
secured with OWSM security policies
Description
Start the administration
server and managed servers,
and run the
upgradeWebCenterPermissio
ns() WLST command to
update permissions for
WebCenter Portal.
Import the Web service
deployment descriptors if
Oracle WebCenter Portal's
Services Portlets producer or
any custom portlet producers
were deployed and secured
with OWSM security policies
in your prepatched instance.
Reset search customizations if using
Oracle SES 11.2.2.2
Update OAM policies if OAM
patched to release 11.1.2.2.0
Links
■
■
■
If you patched to Oracle SES
11.2.2.2, reset search
customizations.
Run setProfileConfig to restore
Profile page customizations
Remove the -noverify flag if present
If you patch to OAM
11.1.2.2.0, update the OAM
policies. You must restore
Profile page customizations.
Further, remove the -noverify
flag if present in
setDomainEnv.sh or
setDomainEnv.cmd.
Choose whether to continue using
Folders_g or migrate to
FrameworkFolders
Note: You do not need to perform
post-patching task for WebCenter Portal if
you are migrating a Portal Framework
application as a portal to the portal server.
In your patched instance,
you can continue to use the
Folders_g component or
choose to migrate to the
FrameworkFolders interface.
Oracle recommends that you
migrate to
FrameworkFolders.
■
■
■
■
■
Perform post-patching tasks for other
Fusion Middleware products
Mandatory
6-12 Oracle Fusion Middleware Patching Guide
Perform any post patching
tasks required for Oracle
WebCenter Content or other
products
Section 3.8,
"Starting the
Servers and
Processes"
Section 6.10.9,
"Running the
upgradeWebCent
erPermissions
WLST
Command"
Section 6.10.1,
"Importing Web
Service
Deployment
Descriptors for
Portlet Producers
Secured with
OWSM"
Section 6.10.10,
"Resetting Search
Customizations"
Section 6.10.11,
"Updating
Resource
Protection Level
in OAM
11.1.2.2.0"
Section 6.10.12,
"Restoring
Profile Page
Customizations"
Section 6.10.13,
"Removing the
-noverify Flag"
"Migrating
Folders_g to
FrameworkFolde
rs" in Oracle
Fusion
Middleware
Administering
Oracle WebCenter
Portal
Section 5.7,
"Post-Patching Tasks
If Your Starting Point
is Release 11.1.1.7"
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Table 6–3 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.7.0
Task
Mandatory or
Optional?
Start/restart the servers and processes
Mandatory
Description
Links
Start your Oracle Fusion
Middleware environment.
This involves starting your
Oracle WebLogic Server,
Administration Server,
managed servers, node
manager, OPMN, and all
system components.
Section 3.8, "Starting
the Servers and
Processes"
Note: If you had started any
managed servers before, you
must restart them now.
Verify Oracle WebCenter Portal 11.1.1.9.0
installation
Mandatory
Verify your patched Oracle
WebCenter Portal instance by
trying to access various URLs
like for Administration
Server and WebCenter Portal.
"Verifying Your
Configuration"
section in Oracle
Fusion Middleware
Installation Guide for
Oracle WebCenter
Portal
Upgrade existing portals
Optional
Upgrade your existing
portals to take advantage of
the features available in
release 11.1.1.9.0.
"Upgrading a
Pre-11.1.1.8.0 Portal"
in Oracle Fusion
Middleware Building
Portals with Oracle
WebCenter Portal
6.4 Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Figure 6–3 illustrates the steps required to patch an Oracle WebCenter Portal
installation from Release 11.1.1.6.0 to Release 11.1.1.9.0. Table 6–4 describes each of
these steps in detail. Click the required steps in the table to navigate to the information
for each step.
Note: Many of the steps listed in Figure 6–3 and Table 6–4 refer back
to chapter 3 or other chapters of this guide. If you have already
completed any generic steps, like performing pre-patching generic
tasks, patching Fusion Middleware products other than WebCenter
Portal, or updating schemas, as per instructions in Chapter 3, you may
skip those steps.
In Figure 6–3, WebCenter Portal-specific steps are highlighted in
green.
Patching Oracle WebCenter Portal 6-13
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
The WebCenter Portal Framework technology is fully
supported in Oracle WebCenter Portal 11g R1 release. However, it is in
maintenance mode since release 11.1.1.7.0. Any new features, such as
Portal Builder and mobile web support added in the WebCenter Portal
application in release 11.1.1.8.0, are not available in Portal Framework
applications.
Note:
If you are running a Portal Framework application from release
11.1.1.6.0 and want to benefit from new WebCenter Portal features and
capabilities, Oracle recommends that you migrate your Portal
Framework application as a portal to the WebCenter Portal
application. For information, see "Migrating a Portal Framework
Application to WebCenter Portal" in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
Figure 6–3 Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
6-14 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Table 6–4
Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Task
Mandatory or
Optional?
Description
Links
Section 6.9.1,
"Exporting
Deployment
Descriptor for Portlet
Producer
Applications Secured
with OWSM"
Export Web service deployment
descriptors for portlet producers secured
with OWSM security policies
Mandatory
If Oracle WebCenter Portal's
Services Portlets producer or
any custom portlet producers
are deployed and secured
with OWSM security
policies, export the Web
service deployment
descriptors for those portlet
producers to a Java Archive
(JAR) file.
Perform the general pre-patching tasks:
Mandatory
Section 3.4, "General
Before patching Oracle
WebCenter Portal, make sure Pre-Patching Tasks"
your system environment
and configuration meet the
minimum requirements and
the backups are in place.
Also, you must patch Oracle
WebLogic Server to the latest
supported release.
■
■
■
■
■
■
■
Review system requirement,
certification, and interoperability
information
Stop the servers and processes
Back up your Middleware Home,
Domain Home, and Oracle instances
Back up your database and database
schemas
If you are patching your
software in silent mode, you
need to rename the emCCR
file.
Back up additional configuration
information
Patch Oracle WebLogic Server
Rename the emCCR file for silent
patching
Download the installer for Oracle
WebCenter Portal and other required
products
Mandatory
Section 3.5,
Download the Oracle
"Downloading the
WebCenter Portal installer,
Installer"
which is a full installer that
also functions as an update
installer. At this stage, if
required, you can also
download installers for other
Fusion Middleware products
that you plan to patch, such
as Oracle WebCenter Content
and Oracle SOA Suite.
Note: If you have already
downloaded the product
installers as per instructions
in Chapter 3, you may skip
this step.
Patching Oracle WebCenter Portal 6-15
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Table 6–4 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Task
Mandatory or
Optional?
Run Patch Set Installer to patch the
following Fusion Middleware products to
release 11.1.1.9.0:
■
■
Mandatory
only if these
products are
installed in
Oracle Web Tier (Oracle HTTP Server)
your
Oracle Forms, Reports and Discoverer environment
Description
Patch these products before
you patch Oracle WebCenter
Portal.
This Oracle Fusion
Middleware patch set
provides Oracle Portal
11.1.1.6.0, which is the latest
version of Oracle Portal. If
Oracle Portal 11.1.1.6.0 is
already installed, you do not
need to patch it.
Links
■
■
■
Note: If you have already
patched these Fusion
Middleware products as per
instructions in Chapter 3,
you may skip this step.
Section 3.3.7,
"Special
Instructions for
Patching Oracle
Portal, Forms,
Reports and
Discoverer"
Section 3.6.1,
"Starting the
Installer"
Section 3.6.2,
"Applying the
Patch Set"
Note: Oracle recommends
that Oracle Portal, Forms,
Reports and Discoverer
should be installed in a
separate Middleware home
directory that is not shared
with other Oracle Fusion
Middleware products.
Run the Oracle WebCenter Portal installer
Patch the other required Fusion
Middleware products
Mandatory
Mandatory
only for the
products
installed in the
Middleware
home
Run the Oracle WebCenter
Portal 11.1.1.9.0 installer.
While applying the patch set,
specify your existing Oracle
Middleware home and
WebCenter Portal Oracle
home locations.
At this stage, you can patch
other Fusion Middleware
products, such as Oracle
WebCenter Content and
Oracle SOA Suite, by
running their product
installers.
Note: If you have already
patched other Fusion
Middleware products as per
instructions in Chapter 3,
you may skip this step.
6-16 Oracle Fusion Middleware Patching Guide
■
■
■
■
Section 3.6.1,
"Starting the
Installer"
Section 3.6.2,
"Applying the
Patch Set"
Section 6.9.4,
"Considerations
for Upgrading
Oracle
WebCenter
Content or
Oracle ECM"
Section 3.6,
"Patching Oracle
Fusion
Middleware"
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Table 6–4 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Task
If required, patch to Oracle SES 11.2.2.2.
For your patched or any existing Oracle
SES instance, install the new version of
Oracle WebCenter Portal's Document
Service Manager
Mandatory or
Optional?
Mandatory
Description
Links
Oracle WebCenter Portal
release 11.1.1.9.0 supports
Oracle SES 11.2.2.2, which
provides faceted search.
Oracle recommends using
Oracle SES release 11.2.2.2 for
best performance and latest
search features.
For your patched or any
existing Oracle SES
installation, you must install
the new version of Oracle
WebCenter Portal's
Document Service Manager
and configure Oracle SES
facets and sorting attributes.
Upgrade the MDS, WEBCENTER, ACTIVITIES,
DISCUSSIONS and DISCUSSIONS_CRAWLER
schemas
Mandatory
■
■
For patching to
Oracle SES
11.2.2.2, see
Oracle Secure
Enterprise Search
Installation and
Upgrade Guide in
the Secure
Enterprise Search
Online
Documentation
Library 11g
Release 2
(11.2.2.2) on
OTN.
For information
about installing
the new version
of Oracle
WebCenter
Portal's
Document
Service Manager,
see the "Oracle
SES Installation"
section in Oracle
Fusion
Middleware
Installation Guide
for Oracle
WebCenter Portal.
Use the Patch Set Assistant to Chapter 4,
"Upgrading Your
upgrade the required
Schemas with Patch
schemas.
Set Assistant"
Before running Patch Set
Assistant, check to make sure
that your database is up and
running and that the schema
you want to upgrade is at the
version supported for
upgrade.
Note: For database-based
OPSS policy store, upgrade
the prefix_OPSS schema
using Patch Set Assistant.
Check whether schemas of
other patched products need
to be updated. You can
update all the required
schemas at this stage. You
may skip this step if you
have already upgraded
schemas listed in Table 4–1,
" Schemas That Require
Upgrading for the Latest
Release".
Patching Oracle WebCenter Portal 6-17
Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation
Table 6–4 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Task
Mandatory or
Optional?
Perform the following post-patching tasks Mandatory
for WebCenter Portal:
■
■
■
■
■
■
■
■
■
■
■
Run UpgradeOpss WLST command
Start the administration server and
managed servers
Run the
upgradeWebCenterPermissions()
WLST command
Import Web service deployment
descriptors for portlet producers
secured with OWSM security policies
Configure WebCenter Portal
workflows
Upgrade Process Spaces
Reset Oracle SES search
customizations if using Oracle SES
11.2.2.2
Update OAM policies if OAM is
patched to release 11.1.2.2.0
Run setProfileConfig to restore
Profile page customizations
Remove the -noverify flag if present
Choose whether to continue using
Folders_g or migrate to
FrameworkFolders
Note: You do not need to perform
post-patching task for WebCenter Portal if
you are migrating a Portal Framework
application as a portal to the portal server.
Description
Run UpgradeOpss. Start the
administration server and
managed servers, and then
run the
upgradeWebCenterPermissio
ns WLST command.
Import the Web service
deployment descriptors if
WebCenter Service Portlets
producer or any custom
portlet producers were
deployed and secured with
OWSM security policies in
your prepatched instance.
If WebCenter Portal
workflows are configured,
upgrade the related
configuration. It is optional,
but recommended, to
upgrade Process Spaces.
Links
■
■
■
■
If you patched to Oracle SES
11.2.2.2, reset search
customizations.
If you patch to OAM
11.1.2.2.0, update the OAM
policies. You must restore
Profile page customizations.
Further, remove the
-noverify flag if present in
setDomainEnv.sh or
setDomainEnv.cmd.
In your patched instance,
you can continue to use the
Folders_g component or
choose to migrate to the
FrameworkFolders interface.
Oracle recommends that you
migrate to
FrameworkFolders.
■
■
■
■
■
■
■
6-18 Oracle Fusion Middleware Patching Guide
Section 6.10.2,
"Running the
upgradeOpss
WLST
Command"
Section 3.8,
"Starting the
Servers and
Processes"
Section 6.10.9,
"Running the
upgradeWebCent
erPermissions
WLST
Command"
Section 6.10.1,
"Importing Web
Service
Deployment
Descriptors for
Portlet Producers
Secured with
OWSM"
Section 6.10.6.2,
"Configuring
WebCenter
Portal
Workflows"
Section 6.10.6.7,
"Upgrading
Process Spaces"
Section 6.10.10,
"Resetting Search
Customizations"
Section 6.10.11,
"Updating
Resource
Protection Level
in OAM
11.1.2.2.0"
Section 6.10.12,
"Restoring
Profile Page
Customizations"
Section 6.10.13,
"Removing the
-noverify Flag"
"Migrating
Folders_g to
FrameworkFolde
rs" in Oracle
Fusion
Middleware
Administering
Oracle WebCenter
Portal
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–4 (Cont.) Applying the Latest Patch to Oracle WebCenter Portal 11.1.1.6.0
Mandatory or
Optional?
Task
Description
Links
Perform post-patching tasks for other
patched Fusion Middleware products.
Mandatory
For all the Fusion
Middleware products that
you patched to Release
11.1.1.9.0, perform the
required post-patching tasks.
Section 5.6,
"Post-Patching Tasks
If Your Starting Point
is Release 11.1.1.6"
Start/restart the servers and processes
Mandatory
Start your Oracle Fusion
Middleware environment.
This involves starting your
Oracle WebLogic Server,
Administration Server,
managed servers, node
manager, OPMN, and all
system components.
Section 3.8, "Starting
the Servers and
Processes"
Note: If you had started any
managed servers before, you
must restart them now.
Verify Oracle WebCenter Portal 11.1.1.9.0
installation
Mandatory
Verify your patched Oracle
WebCenter Portal instance by
trying to access various URLs
like for Administration
Server and WebCenter Portal.
"Verifying Your
Configuration"
section in Oracle
Fusion Middleware
Installation Guide for
Oracle WebCenter
Portal
Upgrade existing portals
Optional
Upgrade your existing
portals to take advantage of
the features available in
release 11.1.1.9.0.
"Upgrading a
Pre-11.1.1.8.0 Portal"
in Oracle Fusion
Middleware Building
Portals with Oracle
WebCenter Portal
6.5 Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Figure 6–4 illustrates the steps required to update an Oracle WebCenter 11.1.1.4.0 or
11.1.1.5.0 installation to 11.1.1.9.0. Follow the instructions in Table 6–5 to navigate to
the information for each step.
Note: Many of the steps listed in Figure 6–4 and Table 6–5 refer back
to chapter 3 or other chapters of this guide. If you have already
completed any generic steps, like performing pre-patching generic
tasks, patching Fusion Middleware products other than WebCenter
Portal, or updating schemas, as per instructions in Chapter 3, you may
skip those steps.
In Figure 6–4, Oracle WebCenter Portal-specific steps are highlighted
in green.
Patching Oracle WebCenter Portal 6-19
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Figure 6–4 Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
6-20 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5
Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task
Mandatory or
Optional?
Description
Links
Export Web service deployment descriptors for
portlet producers secured with OWSM security
policies
Mandatory
If Oracle WebCenter's
Services Portlets producer
or any custom portlet
producers are deployed
and secured with OWSM
security policies, export the
Web service deployment
descriptors for those
portlet producers to a Java
Archive (JAR) file.
Section 6.9.1,
"Exporting
Deployment
Descriptor for
Portlet Producer
Applications
Secured with
OWSM"
Perform the general pre-patching tasks:
Mandatory
Before patching Oracle
WebCenter Portal, make
sure your system
environment and
configuration meet the
minimum requirements
and the backups are in
place. Also, you must
patch Oracle WebLogic
Server to the latest
supported release.
Section 3.4,
"General
Pre-Patching
Tasks"
■
■
■
Review system requirement, certification and
interoperability information
Stop the servers and processes
Back up your Middleware Home, Domain
Home, and Oracle instances
■
Back up your database and database schemas
■
Back up additional configuration information
■
Patch Oracle WebLogic Server
■
Rename the emCCR file for silent patching
Download the installer for Oracle WebCenter
Portal and other required products
If you are patching your
software in silent mode,
you need to rename the
emCCR file.
Mandatory
Section 3.5,
Download the Oracle
WebCenter Portal installer, "Downloading
which is a full installer that the Installer"
also functions as an update
installer. At this stage, if
required, you can also
download installers for
other Fusion Middleware
products that you plan to
patch, such as Oracle
WebCenter Content and
Oracle SOA Suite.
Note: If you have already
downloaded the product
installers as per
instructions in Chapter 3,
you may skip this step.
Patching Oracle WebCenter Portal 6-21
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task
Run Patch Set Installer to patch the following
Fusion Middleware products to their latest
release:
■
Oracle Web Tier (Oracle HTTP Server)
■
Oracle Forms, Reports and Discoverer
■
Oracle Portal to release 11.1.1.6.0
Mandatory or
Optional?
Mandatory
only if these
products are
installed in
your
environment
Description
Patch these products to
release 11.1.1.7.0 before you
patch Oracle WebCenter
Portal
This Oracle Fusion
Middleware patch set
provides Oracle Portal
11.1.1.6.0, which is the
latest version of Oracle
Portal. When you run the
patch set, Oracle Portal is
patched to release
11.1.1.6.0.
Links
■
■
Note: Oracle recommends
that Oracle Portal, Forms,
Reports and Discoverer
should be installed in a
separate Middleware home
directory that is not shared
with other Oracle Fusion
Middleware products.
Section 3.3.7,
"S
pecial
Instructions
for Patching
Oracle
Portal,
Forms,
Reports and
Discoverer"
Section 3.6,
"Patching
Oracle
Fusion
Middleware
"
Note: If you have already
patched these Fusion
Middleware products as
per instructions in Chapter
3, you may skip this step.
Run the Oracle WebCenter Portal installer
Mandatory
Patch other required Fusion Middleware products Mandatory
only for the
products
installed in the
Middleware
home
Run the Oracle WebCenter
Portal 11.1.1.9.0 installer.
While applying the patch
set, specify your existing
Oracle Middleware home
and WebCenter Portal
Oracle home locations.
At this stage, you can patch
other Fusion Middleware
products, such as Oracle
WebCenter Content and
Oracle SOA Suite, by
running their product
installers.
Note: If you have already
patched the other Fusion
Middleware products as
per instructions in Chapter
3, you may skip this step.
6-22 Oracle Fusion Middleware Patching Guide
Section 3.6,
"Patching Oracle
Fusion
Middleware"
■
■
Section 3.6,
"Patching
Oracle
Fusion
Middleware
"
Section 6.9.4,
"C
onsideratio
ns for
Upgrading
Oracle
WebCenter
Content or
Oracle
ECM"
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task
If required, patch to Oracle SES 11.2.2.2. For your
patched or any existing Oracle SES instance,
install the new version of Oracle WebCenter
Portal's Document Service Manager
Mandatory or
Optional?
Mandatory
Description
Oracle WebCenter Portal
release 11.1.1.9.0 supports
Oracle SES 11.2.2.2, which
provides faceted search.
Oracle recommends using
Oracle SES release 11.2.2.2
for best performance and
latest search features.
Links
■
For your patched or any
existing Oracle SES
installation, you must
install the new version of
Oracle WebCenter Portal's
Document Service
Manager and configure
Oracle SES facets and
sorting attributes.
■
For
patching to
Oracle SES
11.2.2.2, see
Oracle
Secure
Enterprise
Search
Installation
and Upgrade
Guide in the
Secure
Enterprise
Search
Online
Documentat
ion Library
11g Release
2 (11.2.2.2)
on OTN.
For
information
about
installing
the new
version of
Oracle
WebCenter
Portal's
Document
Service
Manager,
see the
"Oracle SES
Installation"
section in
Oracle
Fusion
Middleware
Installation
Guide for
Oracle
WebCenter
Portal.
Patching Oracle WebCenter Portal 6-23
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task
Mandatory or
Optional?
Upgrade the MDS, WEBCENTER, ACTIVITIES,
Mandatory
DISCUSSIONS, and DISCUSSIONS_CRAWLER schemas
Description
Use the Patch Set Assistant Chapter 4,
to upgrade your schemas. "Upgrading
Your Schemas
Before running Patch Set
with Patch Set
Assistant, you should
Assistant"
check to make sure that
your database is up and
running and that the
schemas you want to
upgrade are at the
versions that are supported
for upgrade.
Note: For database-based
OPSS policy store, upgrade
the prefix_OPSS schema
using Patch Set Assistant.
Check whether schemas of
other patched products
need to be upgraded. You
can upgrade all the
required schemas at this
stage. You may skip this
step if you have already
patched the schemas listed
in Table 4–1, " Schemas
That Require Upgrading
for the Latest Release".
6-24 Oracle Fusion Middleware Patching Guide
Links
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Task
Perform the following post-patching tasks for
WebCenter Portal:
■
■
■
■
■
■
Run UpgradeOpss WLST command
Start the administration server and managed
servers
Run the upgradeWebCenterPermissions()
WLST command
Import Web service deployment descriptors
for portlet producers secured with OWSM
security policies
Extend the domain using the Pagelet
Producer upgrade template
Update SSO and OHS configuration for
Pagelet Producer, Portlet Producer
applications, and Oracle SES
■
Configure WebCenter Portal workflows
■
Upgrade Process Spaces
■
■
■
■
■
Reset Oracle SES search customizations if
using Oracle SES 11.2.2.2
Update OAM policies if OAM is patched to
release 11.1.2.2.0
Run setProfileConfig to restore Profile
page customization
Remove the -noverify flag if present
Choose whether to continue using Folders_g
or migrate to FrameworkFolders
Mandatory or
Optional?
Mandatory
Description
Run UpgradeOpss. Start the
administration server and
managed servers, and run
the
upgradeWebCenterPermiss
ions WLST command.
Import the Web service
deployment descriptors if
Services Portlets producer
or any custom portlet
producers were deployed
and secured with OWSM
security policies in your
prepatched instance.
It is optional, but
recommended, to upgrade
Pagelet Producer and
Process Spaces.
Links
■
■
■
■
If WebCenter Portal
workflows, SSO, and OHS
are configured, it is
mandatory to reconfigure
them after patching your
instance.
If you patched to Oracle
SES 11.2.2.2, reset the
search customizations. If
OAM is patched to release
11.1.2.2.0, update the OAM
policies.
You must restore Profile
page customizations.
Further, remove the
-noverify flag if present in
setDomainEnv.sh or
setDomainEnv.cmd.
In your patched instance,
you can continue to use the
Folders_g component or
choose to migrate to the
FrameworkFolders
interface. Oracle
recommends that you
migrate to
FrameworkFolders.
■
■
■
Section 6.10.2,
"
Running the
upgradeOps
s WLST
Command"
Section 3.8,
"Starting the
Servers and
Processes"
Section 6.10.9,
"
Running the
upgradeWe
bCenterPer
missions
WLST
Command"
Section 6.10.1,
"I
mporting
Web Service
Deployment
Descriptors
for Portlet
Producers
Secured
with
OWSM"
Section 6.10.3,
"
Extending
the Domain
Using the
Pagelet
Producer
Upgrade
Template"
Section 6.10.4,
"
Updating
SSO and
OHS
Configurati
on"
Section 6.10.6.2,
"Configurin
g
WebCenter
Portal
Workflows"
■
■
Section 6.10.6.7,
"Upgrading
Process
Spaces"
Section 6.10.10,
"Resetting
Search
Customizati
ons"
Section 6.10.11,
"Updating
Resource
Protection
Patching Oracle WebCenterLevel
Portal
in 6-25
OAM
11.1.2.2.0"
■
Patching an Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0 Installation
Table 6–5 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.4.0 or 11.1.1.5.0
Mandatory or
Optional?
Task
Perform post-patching tasks for the required
Fusion Middleware products
Mandatory
Description
For the Fusion Middleware
products that you patched,
perform the required
post-patching tasks.
Links
■
■
Start/restart the servers and processes
Mandatory
Start your Oracle Fusion
Middleware environment.
This involves starting your
Oracle WebLogic Server,
Administration Server,
managed servers, node
manager, OPMN, and all
system components.
Section 5.4,
"Post-Patchi
ng Tasks If
Your
Starting
Point is
Release
11.1.1.4"
Section 5.5,
"Post-Patchi
ng Tasks If
Your
Starting
Point is
Release
11.1.1.5"
Section 3.8,
"Starting the
Servers and
Processes"
Note: If you had started
any managed servers
before, you must restart
them now.
Verify Oracle WebCenter Portal 11.1.1.9.0
installation
Mandatory
Verify your patched Oracle
WebCenter Portal instance
by trying to access various
URLs like for
Administration Server and
WebCenter Portal.
"Verifying Your
Configuration"
section in Oracle
Fusion
Middleware
Installation Guide
for Oracle
WebCenter Portal
Upgrade existing portals
Optional
Upgrade your existing
portals to take advantage
of the features available in
release 11.1.1.9.0.
"Upgrading a
Pre-11.1.1.8.0
Portal" in Oracle
Fusion
Middleware
Building Portals
with Oracle
WebCenter Portal
Beginning with Release 11.1.1.6.0, a new Services Portlets
producer is available for exposing task flows from WebCenter Portal
tools and services as portlets. You can consume portlets from Oracle
WebCenter Portal's Services Portlets in Oracle Portal, Oracle WebLogic
Portal, and Oracle WebCenter Interaction applications. For
information, see Section 6.10.8.1, "Installing Activity Graph, Analytics,
Pagelet Producer, Personalization Server, and Services Portlets."
Note:
6-26 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
After patching to release 11.1.1.9.0, you can optionally disable
the Analytics Collector TRACE log level and enable the NOTIFICATION
log level for a stable server performance. On the WC_Utilities
managed server, the level attribute of the com.plumtree.analytics
logger is set to value TRACE:32. Change this value to
NOTIFICATION:16. For more information, see the "Setting the Level of
Information Written to Log Files" section in Oracle Fusion Middleware
Administrator's Guide.
Note:
6.6 Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
This section describes the procedures involved in patching an Oracle WebCenter
11.1.1.2.0 or 11.1.1.3.0 installation to release 11.1.1.9.0. It contains the following
subsections:
■
Section 6.6.1, "Managed Server Changes"
■
Section 6.6.2, "Migration Roadmap for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0"
■
Section 6.6.3, "Updating Oracle WebCenter Portal Using WLST Commands"
6.6.1 Managed Server Changes
From Release 11.1.1.4.0 onward, managed servers have been renamed from WLS_name
to WC_name, where name refers to the name of the managed server. For more
information, see the "Oracle WebCenter Portal Managed Servers" section in Oracle
Fusion Middleware Installation Guide for Oracle WebCenter Portal.
In Release 11.1.1.2.0 and 11.1.1.3.0, the WLS_Services managed server hosts Oracle
WebCenter Discussions and Oracle WebCenter Wiki and Blog Server. From Release
11.1.1.4.0 onward, WLS_Services is no longer supported. Oracle WebCenter Portal's
Discussion Server is deployed to WC_Collaboration, and wikis and blogs reside on
Content Server.
From Release 11.1.1.4.0 onward, a new managed server, WC_Utilities, is supported
that hosts the following Oracle WebCenter Portal components: Analytics Collector,
Activity Graph Engines, and Personalization.
6.6.2 Migration Roadmap for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Figure 6–5 illustrates the steps required to patch an Oracle WebCenter 11.1.1.2.0 or
11.1.1.3.0 installation to 11.1.1.9.0. Follow the instructions in Table 6–6 to navigate to
the information for each step.
Note: Many of the steps listed in Figure 6–5 and Table 6–6 refer back
to chapter 3 or other chapters of this guide. If you have already
completed any generic steps, like performing pre-patching generic
tasks, patching Fusion Middleware products other than WebCenter
Portal, or updating schemas, as per instructions in Chapter 3, you may
skip those steps.
In Figure 6–5, Oracle WebCenter Portal-specific steps are highlighted
in green.
Patching Oracle WebCenter Portal 6-27
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Figure 6–5 Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
6-28 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6
Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Mandatory
or Optional? Description
Link
Export Web service deployment
descriptors for portlet producers secured
with OWSM security policies
Mandatory
If your portlet producers
are deployed and
secured with OWSM
security policies, export
the Web service
deployment descriptors
for those portlet
producers to a Java
Archive (JAR) file.
Perform the general pre-patching tasks:
Mandatory
Before you begin
patching Oracle
WebCenter Portal, make
sure your system
environment and
configuration meet the
minimum requirements,
and the backups are in
place.
■
■
■
■
■
Review system requirement,
certification, and interoperability
information
Stop the servers and processes
Back up your Middleware Home,
Domain Home and Oracle instances
Section 6.9.1, "Exporting
Deployment Descriptor for
Portlet Producer
Applications Secured with
OWSM"
■
■
■
Back up your database and database
schemas
Back up additional configuration
information
■
■
Perform pre-patching tasks for Oracle
WebCenter Portal:
■
■
■
Mandatory
Save OmniPortlet and Web Clipping
customizations
Run purgeMetadata()
Patch Oracle ECM 10g to release
10.1.3.5.1 if required
Before patching Oracle
WebCenter Portal, save
the OmniPortlet and
Web Clipping
customizations. Run
purgeMetadata() for
WebCenter Portal
(previously called
WebCenter Spaces).
If Oracle ECM 10g is
installed, upgrade to
release 10.1.3.5.1 if you
are using a previous
version.
Patch Oracle WebLogic Server to the latest
version
Mandatory
Rename the emCCR file if using the silent
mode for patching
Mandatory
for silent
mode
Patch Oracle WebLogic
Server to the latest
release.
■
■
■
Section 3.4.1,
"Reviewing System
Requirements and
Certification"
Section 3.4.3,
"Stopping the Servers
and Processes"
Section 3.4.4, "Backing
Up Your Middleware
Home, Domain Home
and Oracle Instances"
Section 3.4.5, "Backing
Up Your Database and
Database Schemas"
Section 3.4.6, "Backing
Up Additional
Configuration
Information"
Section 6.9.2, "Saving
Your OmniPortlet and
Web Clipping
Customizations"
Section 6.9.3, "Running
purgeMetadata() for
WebCenter Spaces"
Section 6.9.4,
"Considerations for
Upgrading Oracle
WebCenter Content or
Oracle ECM"
Section 3.4.7, "Upgrading
Oracle WebLogic Server
and Applying Required
WebLogic Server Patches"
Section 3.4.8, "Renaming
the emCCR File for Silent
Patching"
Patching Oracle WebCenter Portal 6-29
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Download the installer for Oracle
WebCenter Portal and other required
products
Mandatory
or Optional? Description
Mandatory
Download the
WebCenter Portal
installer, which is a full
installer that can also
function as an update
installer. At this stage,
you can also download
the installers for any
other FMW products
that you plan to patch,
such as Oracle
WebCenter Content and
Oracle SOA Suite.
Link
Section 3.5, "Downloading
the Installer"
Note: If you have
already downloaded
product installers as per
instructions in Chapter
3, you may skip this
step.
Run Patch Set Installer to patch the
following Fusion Middleware products to
their latest release:
■
Oracle Identity Management
■
Oracle Web Tier (Oracle HTTP Server)
■
Oracle Forms, Reports and Discoverer
■
Oracle Portal to release 11.1.1.6.0
Mandatory
only if these
products are
installed in
your
environment
Patch these products to
release 11.1.1.7.0 before
you patch Oracle
WebCenter Portal.
This Oracle Fusion
Middleware patch set
provides Oracle Portal
11.1.1.6.0, which is the
latest version of Oracle
Portal. When you run
the patch set, Oracle
Portal is patched to
release 11.1.1.6.0.
■
■
Section 3.3.7, "Special
Instructions for
Patching Oracle Portal,
Forms, Reports and
Discoverer"
Section 3.6, "Patching
Oracle Fusion
Middleware"
Note: Oracle
recommends that Oracle
Portal, Forms, Reports
and Discoverer be
installed in a separate
Middleware home
directory that is not
shared with other Oracle
Fusion Middleware
products.
Note: If you have
already patched these
Fusion Middleware
products as per
instructions in Chapter
3, you may skip this
step.
Run the Oracle WebCenter Portal installer
to patch to Release 11.1.1.9.0
Mandatory
6-30 Oracle Fusion Middleware Patching Guide
Section 3.6, "Patching
Run the Oracle
Oracle Fusion Middleware"
WebCenter Portal
11.1.1.9.0 installer. While
applying the patch set,
specify your existing
Oracle Middleware
home and WebCenter
Portal Oracle home
locations.
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Mandatory
or Optional? Description
Link
Upgrade Oracle ECM 10.1.3.5.1 to Oracle
WebCenter Content 11.1.1.9.0
Mandatory
If you are using Oracle
ECM 10g, you must
upgrade to Oracle
WebCenter Content
11.1.1.9.0. (Release
11.1.1.6.0 onward, Oracle
ECM has been
rebranded as Oracle
WebCenter Content.)
Section 6.9.4,
"Considerations for
Upgrading Oracle
WebCenter Content or
Oracle ECM"
Run other product installers to patch the
other required Fusion Middleware
products
Mandatory
only for the
products
installed in
the
Middleware
home
At this stage, you can
patch other Fusion
Middleware products,
such as Oracle SOA
Suite.
Section 3.6, "Patching
Oracle Fusion Middleware"
Note: If you have
already patched the
other Fusion
Middleware products as
per instructions in
Chapter 3, you may skip
this step.
Patching Oracle WebCenter Portal 6-31
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Upgrade the required schemas: MDS,
WEBCENTER, DISCUSSIONS, and
DISCUSSIONS_CRAWLER
Mandatory
or Optional? Description
Mandatory
Upgrade Oracle
WebCenter
Portal-specific schemas.
Link
Chapter 4, "Upgrading
Your Schemas with Patch
Set Assistant"
Note: For WebCenter
Portal (previously called
WebCenter Spaces)
schemas that were
originally installed using
the Release 11.1.1.1.0
Repository Creation
Utility and have
subsequently been
upgraded to Release
11.1.1.2.0/11.1.1.3.0, it is
necessary to grant an
additional privilege to
the WebCenter Portal
schema owner prior to
running the Patch Set
Assistant to upgrade the
schema to Release
11.1.1.9.0. Connect as a
SYSDBA user to the
database containing the
WebCenter Portal
schema using SQL*Plus,
and grant create view
to the WebCenter Portal
schema owner.
Note: For
database-based OPSS
policy store, upgrade the
prefix_OPSS schema
using Patch Set
Assistant. Check
whether schemas of
other patched products
need to be upgraded.
You can upgrade all the
required schemas at this
stage. You may skip this
step if you have already
upgraded schemas listed
in Table 4–1, " Schemas
That Require Upgrading
for the Latest Release".
Update WebCenter Portal using the WLST
commands
Mandatory
6-32 Oracle Fusion Middleware Patching Guide
Use WLST commands to Section 6.6.3, "Updating
Oracle WebCenter Portal
update WebCenter
Using WLST Commands"
Portal, the
out-of-the-box
enterprise-ready
customizable
application.
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Perform post-patching tasks for Oracle
WebCenter Portal:
■
■
■
Update multi-calendar layouts
■
■
■
■
■
■
■
Section 6.10.12,
"Restoring Profile Page
Customizations"
Remove LD_LIBRARY_PATH from
setDomainEnv script
Migrate WSRP portlet preferences
Update OAM policies if OAM is
patched to release 11.1.2.2.0
Run setProfileConfig to restore
Profile page customizations
Set the Web Context Root on the
Content Server connection
Mandatory
Perform post-patching
tasks for WebCenter
Portal.
Section 6.10.6, "Performing
Post-Patching Tasks for the
WebCenter Portal
Application"
Configure WebCenter Portal
workflows
Update the portal display mode
■
Section 6.10.11,
"Updating Resource
Protection Level in
OAM 11.1.2.2.0"
Redeploy applications to upgraded
custom portal managed servers
■
■
■
Section 6.10.5,
"Performing
Post-Patching Tasks
for Oracle WebCenter
11.1.1.2.0 or 11.1.1.3.0
Installations"
Remove OpenUsage properties in
setDomainEnv
Update the timezone attribute
■
■
Extend a domain to install Oracle
WSM Policy Manager
■
■
■
Perform post-patching
tasks for Oracle
WebCenter Portal.
Restore your OmniPortlet and Web
Clipping customizations
Perform post-patching tasks for the
WebCenter Portal application:
■
Mandatory
Migrate Content Presenter custom
templates
Update REST API configuration
■
Link
Migrate Oracle Wiki pages and blogs
■
■
Mandatory
or Optional? Description
Choose a default start (or landing)
page
Migrate WebCenter Portal
customizations
Upgrade Process Spaces
Grant permissions to manage assets in
upgraded portals
Patching Oracle WebCenter Portal 6-33
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Perform post-patching tasks for Oracle
WebCenter Portal security:
■
■
■
■
Mandatory
or Optional? Description
Link
Mandatory
■
Import Web service deployment
descriptors for portlet producers
secured with OWSM security policies
Update the list of authentication
providers to add the Oracle Single
Sign-On authentication provider
Import Web service
deployment descriptors
for portlet producers if
they were secured with
OWSM security policies
in your prepatched
instance.
If an external
authentication provider
or identity asserter was
configured in your
pre-patched instance,
you must configure it
again after patching the
instance.
Remove the -noverify flag if present
Choose whether to continue using
Folders_g or migrate to
FrameworkFolders
You must remove the
-noverify flag if present
in setDomainEnv.sh or
setDomainEnv.cmd.
■
■
■
In your patched
instance, you can
continue to use the
Folders_g component or
choose to migrate to the
FrameworkFolders
interface. Oracle
recommends that you
migrate to
FrameworkFolders.
Section 6.10.1,
"Importing Web
Service Deployment
Descriptors for Portlet
Producers Secured
with OWSM"
Section 6.10.7,
"Adding Oracle Single
Sign-On
Authentication
Provider to the List of
Authentication
Providers"
Section 6.10.13,
"Removing the
-noverify Flag"
"Migrating Folders_g
to FrameworkFolders"
in Oracle Fusion
Middleware
Administering Oracle
WebCenter Portal
Note: If you want to set
additional WS-Security
for WebCenter Portal,
refer to the "Configuring
WS-Security" chapter in
Oracle Fusion Middleware
Administering Oracle
WebCenter Portal.
Add new Oracle WebCenter Portal
features:
■
■
Optional
Section 6.10.8, "Adding
Compared to Release
11.1.1.2.0 and 11.1.1.3.0, New Features to Oracle
Oracle WebCenter Portal WebCenter Portal"
11.1.1.9.0 includes
several new features.
You can extend the
WebCenter Portal
domain to add new
features and can update
your WebCenter custom
applications, if required.
Mandatory
For the Fusion
Middleware products
that you patched,
perform the required
post-patching tasks.
Extend the domain to add Activity
Graph, Analytics, Pagelet Producer,
Personalization, and Services Portlets
Upgrade WebCenter custom
applications to add Portal Framework
features
Perform post-patch tasks for the required
Fusion Middleware products
6-34 Oracle Fusion Middleware Patching Guide
■
■
Section 5.2,
"Post-Patching Tasks If
Your Starting Point is
Release 11.1.1.2"
Section 5.3,
"Post-Patching Tasks If
Your Starting Point is
Release 11.1.1.3"
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
Table 6–6 (Cont.) Applying the Latest Patch to Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Task
Mandatory
or Optional? Description
Start/restart the servers and processes
Mandatory
Link
Start your Oracle Fusion Section 3.8, "Starting the
Servers and Processes"
Middleware
environment. This
involves starting your
Oracle WebLogic Server
Administration Server,
managed servers, node
manager, OPMN and all
system components.
Note: If you had started
any managed servers
before, you must restart
them now.
Verify Oracle WebCenter Portal 11.1.1.9.0
installation
Mandatory
Verify your patched
Oracle WebCenter Portal
instance by trying to
access various URLs like
for Administration
Server and WebCenter
Portal.
"Verifying Your
Configuration" section in
Oracle Fusion Middleware
Installation Guide for Oracle
WebCenter Portal
Upgrade existing portals
Optional
Upgrade your existing
portals to take
advantage of the
features available in
release 11.1.1.9.0.
"Upgrading a Pre-11.1.1.8.0
Portal" in Oracle Fusion
Middleware Building Portals
with Oracle WebCenter
Portal
6.6.3 Updating Oracle WebCenter Portal Using WLST Commands
Before you upgrade Oracle WebCenter Portal using WLST:
■
■
Ensure that you have updated the binaries for your Oracle WebCenter Portal
software by running the Oracle WebCenter Portal 11.1.1.9.0 installer.
Ensure that you have updated your database schemas.
To update Oracle WebCenter Portal by using WLST commands:
1.
Stop the Administration Server and all Managed Servers.
2.
Start WLST from the Oracle Common Home directory.
On UNIX operating systems:
cd ORACLE_COMMON_HOME/common/bin
./wlst.sh
On Windows operating systems:
cd ORACLE_COMMON_HOME\common\bin
wlst.cmd
3.
Ensure the external LDAP server is up and running, then run the upgradeOpss
command in offline mode (without connecting to any server):
On UNIX operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml',
jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/system-jazn-data.xml')
Patching Oracle WebCenter Portal 6-35
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
On Windows operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME\\config\\fmwconfig\\jps-config.xml',
jaznData='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\system-jazn-data.xml')
Note: If you need to re-run the upgradeOpss() command, you must
exit the current WLST session and start a new session before
re-running upgradeOpss().
4.
If using a database-based OPSS policy store, run the upgradeOpss command in
offline mode (without connecting to any server):
■
On UNIX operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml',
jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/system-jazn-data.xml',
auditStore='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/auditstore.xml',
jdbcDriver='oracle.jdbc.driver.OracleDriver',
url='jdbc:oracle:thin:@db_host:db_port:db_sid', user='Prefix_OPSS',
password='password', upgradeJseStoreType='true')
■
On Windows operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME\\config\\fmwconfig\\jps-config.xml',
jaznData='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\system-jazn-data.xml',
auditStore='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\auditstore.xml', jdbcDriver='oracle.jdbc.driver.OracleDriver',
url='jdbc:oracle:thin:@db_host:db_port:db_sid', user='prefix_OPSS',
password='password', upgradeJseStoreType='true')
For more information, see the "Upgrading Policies with upgradeOpss" section in
Securing Applications with Oracle Platform Security Services.
5.
Navigate to your WebCenter Portal Oracle home directory (WCP_ORACLE_HOME) and
invoke the WLST script:
(UNIX) WCP_ORACLE_HOME/common/bin/wlst.sh
(Windows) WCP_ORACLE_HOME\common\bin\wlst.cmd
6.
Run the upgradeWebCenterDomain command in offline mode:
upgradeWebCenterDomain(domainDirName='DOMAIN_HOME', oracleHome='WCP_ORACLE_
HOME', upgradeCustomSpaces=[1|0])
Where:
■
■
■
domainDirName - Replace DOMAIN_HOME with the full path to your Domain
home directory.
oracleHome - Replace WCP_ORACLE_HOME with the full path to your WebCenter
Portal Oracle home directory.
upgradeCustomSpaces - Set to 1 if you used the custom.webcenter.spaces
shared library to customize WebCenter Portal (previously named WebCenter
Spaces) and you want to migrate your customizations to the upgraded
6-36 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
instance. For information about how to use your extensions in WebCenter
Portal, refer to:
http://www.oracle.com/technetwork/middleware/webcenter/owcs-ps4-wcs
-ext-samples-wp-406559.pdf
WARNING: If you upgrade your Oracle WebCenter Portal domain
with upgradeCustomSpaces set to 0, none of your previous
customizations and resources that you developed, like page
templates and skins, will be available in the upgraded WebCenter
Portal instance; there is no facility to migrate WebCenter Portal
customizations after the upgrade process.
For example:
upgradeWebCenterDomain(domainDirName='/home/Oracle/Domains/wc_domain',
oracleHome='/home/Oracle/Middleware/Oracle_WC1', upgradeCustomSpaces=1)
You may see error messages when you run the
upgradeWebCenterDomain command. These errors can be safely
ignored so long as there is some text indicating that the operation was
completed successfully. For more information about error messages,
refer to Oracle Fusion Middleware Release Notes.
Note:
7.
Start the Administration Server.
8.
Start the WC_Spaces and WC_Collaboration managed servers.
9.
Connect to the Administration Server.
connect(admin_username, admin_password, host)
10. In the domain running the WC_Spaces Managed Server, run the
upgradeWebCenterPermissions command to add the required permission to the
LDAP store.
upgradeWebCenterPermissions()
You may see error messages when you run the
upgradeWebCenterPermissions command. These errors can be safely
ignored so long as there is some text indicating that the operation was
completed successfully. For more information about error messages,
refer to Oracle Fusion Middleware Release Notes.
Note:
11. All of the instructions to this point have been for a single node. If your domain has
servers running on more than one machine, you need to pack and unpack your
domain to replicate the changes to other nodes in your cluster.
To pack and unpack your updated domain:
a.
Pack the Administration Server:
cd WCP_ORACLE_HOME/common/bin
./pack.sh -managed=true -domain=DOMAIN_HOME -template=wcdomaintemplate.jar
-template_name=wc_domain_template
Patching Oracle WebCenter Portal 6-37
Patching an Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0 Installation
b.
Copy wcdomaintemplate.jar to the WCP_ORACLE_HOME/common/bin on the
other machines.
c.
Remove or move the old domain directories (DOMAIN_HOME and APPLICATION_
HOME) on the other machines.
d.
Unpack the domain on each of the other machines:
cd WCP_ORACLE_HOME/common/bin
./unpack.sh -domain=DOMAIN_HOME -template=wcdomaintemplate.jar
12. Start the Oracle WebCenter Portal Managed Servers:
■
WC_Spaces (WebCenter Portal)
■
WC_Portlet (Portlet Producers)
■
WC_Collaboration (Discussion Server)
Make sure the WC_Spaces server is up and running before moving to the next step.
13. Disconnect from the Administration Server, and connect to the WC_Spaces server
as an Oracle WebCenter Portal administrator that is defined in the external LDAP
server and is defined as an administration user in the embedded Oracle WebLogic
Server.
It is important to note that the administration user must be
defined both as a user in the external LDAP directory and as a user
with administration privileges in the embedded Oracle WebLogic
Server LDAP directory.
Note:
If necessary, you can add a user to the Administration Group of the embedded
Oracle WebLogic Server LDAP server as follows:
1.
Log in to the WebLogic Server console.
2.
Click Security Realms and select the "myrealm" link.
3.
Click the Roles/Policies tab.
4.
Expand Global Roles, then expand Roles, then click "View Role Conditions"
for the Admin role.
5.
Click Add Condition, then select User from the "Predicate List" field, then
click Next.
6.
Enter the user name in the "User Argument Name" field, then click Add.
7.
Click Finish. The user you just entered should now be listed along with the
administrators.
8.
Save your changes and exit.
14. In the domain running the WC_Spaces managed server, run the
upgradeWebCenterApplication command:
upgradeWebCenterApplication(appName='webcenter')
If you have a cluster environment where there are multiple servers with
WebCenter Portal deployed, you must specify the server name. For example:
upgradeWebCenterApplication(appName='webcenter', server="server_name")
6-38 Oracle Fusion Middleware Patching Guide
Patching an Oracle WebCenter 11.1.1.1.0 Installation
15. Copy the Trust Store file from the Oracle home directory to the Oracle WebLogic
Server domain directory.
For example:
cp MW_HOME/oracle_common/modules/oracle.jps_11.1.1/jps-wls-trustprovider.jar
DOMAIN_HOME/lib/mbeantypes/jps-wls-trustprovider.jar
16. Restart the Administration Server and all the Managed Servers in the domain.
6.7 Patching an Oracle WebCenter 11.1.1.1.0 Installation
If you are running Oracle WebCenter 11g (11.1.1.1.0), you must first update your
Oracle Fusion Middleware environment to 11g Release 11.1.1.2.0, and then apply the
Oracle WebCenter Portal 11.1.1.9.0 patch.
Figure 6–6 illustrates the steps required to update an Oracle WebCenter 11.1.1.1.0
installation to Oracle WebCenter Portal Release 11.1.1.9.0. Table 6–7 describes these
steps in detail. Use the table to navigate to the information about each step.
Alternatively, follow the instructions in Appendix C, "Using Patch Assistant to Migrate
from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)".
Figure 6–6 Applying the Latest Patch to Oracle WebCenter 11.1.1.1.0
Patching Oracle WebCenter Portal 6-39
Troubleshooting Issues
Table 6–7
Applying the Latest Patch to Oracle WebCenter 11.1.1.1.0
Mandatory
or
Optional?
Links
Prepare to patch Oracle WebCenter 11.1.1.1.0 to
Release 11.1.1.2.0
Mandatory
Appendix C.3, "Preparing to Migrate"
Patch Oracle WebCenter and other Fusion
Middleware products to 11.1.1.2.0
Mandatory
Appendix C.4.2, "Migration Procedure"
Perform post-patching configuration for Oracle
WebCenter 11.1.1.2.0:
Mandatory
Appendix C.4.3.9, "Post-Migration Configuration
for Oracle WebCenter"
Perform post-patching configuration for other
Fusion Middleware products
Mandatory
Appendix C.4.3, "Post-Migration Configuration
for Oracle Fusion Middleware Components"
Decommission the 11.1.1.1.0 installation
Mandatory
Appendix C.4.2.11, "Decommissioning the
11.1.1.1.0 Installation"
Patch from Release 11.1.1.2.0 to 11.1.1.9.0
Mandatory
Section 6.6, "Patching an Oracle WebCenter
11.1.1.2.0 or 11.1.1.3.0 Installation"
Task and Link to More Information
■
■
■
■
Reconfigure ID store and migrate
application policy and credential stores
Configure SSL and keystores, if used in
11.1.1.1.0
Configure SSO, if used in 11.1.1.1.0
Refresh group space data (WebCenter
Spaces only)
■
Reapply 11.1.1.1.0 configuration changes
■
Migrate custom WebCenter applications
■
Configure WS-Security for Discussions
(WebCenter Spaces only)
■
Migrate to Oracle Content Server 10.1.3.5.1
■
Migrate wiki templates and attachments
6.8 Troubleshooting Issues
This section provides information to help you troubleshoot problems you may
encounter while patching or after patching Oracle WebCenter.
6.8.1 Troubleshooting Issues with Patching Oracle WebCenter Portal
This section provides information to help you troubleshoot problems you may
encounter while patching Oracle WebCenter Portal.
Problem
While running the upgrade.py script, you may encounter the following error:
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : Connection refused. Could not connect to NodeManager.
Solution
If you encounter this error, check that the Node Manager is running and that the user
and server details provided to the script are correct. Then, re-run the upgrade.py script
to complete patching your Oracle WebCenter Portal instance.
6-40 Oracle Fusion Middleware Patching Guide
Troubleshooting Issues
6.8.2 Troubleshooting Post-Patching Issues
This section provides information to help you troubleshoot issues you may encounter
after patching to Oracle WebCenter Portal 11.1.1.9.0. It contains the following
subsections:
■
Section 6.8.2.1, "Related Items Tab Not in Focus"
■
Section 6.8.2.2, "Content Getting Clipped and Inner Scrollbars Appearing"
■
Section 6.8.2.3, "Pretty URLs Not Working for Page Navigation"
■
Section 6.8.2.4, "Content Queries Not Rendered in Navigation Model"
■
Section 6.8.2.5, "Blog Posts Not Displayed in Portals"
■
Section 6.8.2.6, "Comments and Likes Not Displayed in Activity Stream"
6.8.2.1 Related Items Tab Not in Focus
Problem
In Oracle WebCenter 11.1.1.4.0, your WebCenter Portal application contained a
Document Viewer task flow, and the Initial Sidebar property was set to relatedItems.
However in the patched instance, the Related Items tab is not in focus when you
navigate to the task flow though the related items are visible.
Solution
Beginning with Release 11.1.1.6.0, Related Items no longer exists as a tab. You can
change the value of the Initial Sidebar property to target one of the new tabs: tags,
links or recommendations.
6.8.2.2 Content Getting Clipped and Inner Scrollbars Appearing
Problem
In the portals (previously called spaces) upgraded from Release 11.1.1.2.0 and
11.1.1.3.0, content is getting clipped and inner scrollbars appear on the components.
Solution
Beginning with Release 11.1.1.6.0, the default page template for WebCenter Portal is
Top Navigation, which implements a flowing layout. All the page templates that
implement a flowing layout have a fixed width. Most of the pages created before
Release 11.1.1.4.0 were based on page templates that implemented a stretching layout
that allows components to be stretched to maximize the usage of the viewable area. In
your upgraded WebCenter Portal instance, Top Navigation is set as the default
template, and therefore portal pages might not be rendered properly if they are based
on a stretching layout page template.
After patching from Release 11.1.1.2.0 or 11.1.1.3.0, configure your portals, if required,
to use a page template that allows the content to be stretched. Beginning with Release
11.1.1.6.0, the following out-of-the-box page templates support a stretching layout: Top
Navigation (Stretch), Side Navigation (Stretch), Fusion Top Navigation, and Fusion
Side Navigation.
6.8.2.3 Pretty URLs Not Working for Page Navigation
Problem
In your patched WebCenter Portal application, you are unable to navigate to a specific
page using the pretty URL.
Solution
Patching Oracle WebCenter Portal 6-41
Troubleshooting Issues
Beginning with Release 11.1.1.6.0, the pretty URLs to navigate to a specific page in a
portal have changed.
To go to a specific page in the Home portal, use:
http://host:port/webcenter/spaces/profile/userName/page/escapedPageDisplayName
The variable userName is your user name or the name of the user who owns the page
in the Home portal. The variable escapedPageDisplayName indicates the use of an
escaped version of the page display name. For example, when you create a page with
the name My Page, the URL to this page ends with My+Page. For example:
http://host:port/webcenter/spaces/profile/weblogic/page/My+Page
Use the following syntax for UI URLs that target business role pages and system
pages:
http://host:port/webcenter/spaces/system/page/pageName
For example:
http://host:port/webcenter/spaces/system/page/Documents
6.8.2.4 Content Queries Not Rendered in Navigation Model
Problem
After patching to Release 11.1.1.9.0, content queries do not get rendered in a
navigation model.
Solution
After patching Oracle WebCenter Portal, if previous content queries are no longer
listed in your navigation model, you must re-build the index collection on Content
Server. For information, see the "Rebuilding the Collection" section in Oracle Fusion
Middleware Administering Oracle WebCenter Content.
6.8.2.5 Blog Posts Not Displayed in Portals
Problem
After you patched your Oracle WebCenter 11.1.1.2.0 instance, blog posts are not
getting displayed in portals.
Solution
The Wiki Migrator utility wiki-upgrade.jar migrates only the wiki pages and blogs
that are created using the Wiki and Blog page styles. In a portal, you can configure a
page to point to a different wiki or blog by using the wcURL parameter. However, this
type of customization is not supported in wiki migration. Therefore, in Release
11.1.1.2.0, if your page was custom wired to point to a different wiki or blog, the page
will not display the wiki or blog in the patched instance.
The wiki-upgrade.jar utility migrates your Release 11.1.1.2.0 wiki and blog data to a
temporary folder with the same name as the domain. You must move this folder to the
required portal folder. Then, you can either:
■
■
Rename the domain folder to have the same name as the wiki page or blog.
Create a new page with the same name as the newly moved folder, in the required
portal. This will create a new page that exposes the wiki or blog. You can then
delete the old broken page.
6-42 Oracle Fusion Middleware Patching Guide
Pre-Patching Tasks for Oracle WebCenter Portal
6.8.2.6 Comments and Likes Not Displayed in Activity Stream
Problem
In your patched Oracle WebCenter Portal instance, Activity Stream lists the various
messages that were posted and documents that were added in your pre-patched
instance. However, it does not show the comments and likes associated with these
messages and documents.
Explanation
In Oracle WebCenter Portal 11.1.1.9.0, comments and likes are associated with an
activity, and not with the object (a message or a document), whereas in previous
releases, comments and likes were associated with the object itself.
For example, suppose you upload version 1 of a document, and later update the
document to version 2. Activity Stream will display any comments or likes associated
with the activity of uploading version 1 or updating the document to version 2. Any
comments or likes associated with the document itself are not displayed.
6.9 Pre-Patching Tasks for Oracle WebCenter Portal
Preparing to patch your Oracle WebCenter Portal environment involves performing
generic tasks such as stopping the servers, backing up your environment, and
upgrading to the latest version of WebLogic Server. It also involves preparing your
Oracle WebCenter Portal instance. This section describes all Oracle WebCenter
Portal-specific pre-patching tasks that you may need to perform before patching
WebCenter Portal to release 11.1.1.9.0.
The pre-patching tasks described in this section are not
required for all upgrade paths. To determine whether a task is
applicable, refer to the diagram and the table given in this chapter for
your existing environment. For example, if you are patching Oracle
WebCenter Portal 11.1.1.6.0, refer to the diagram and the table given in
Section 6.4, "Patching an Oracle WebCenter Portal 11.1.1.6.0
Installation."
Note:
This section contains the following subsections:
■
Section 6.9.1, "Exporting Deployment Descriptor for Portlet Producer Applications
Secured with OWSM"
■
Section 6.9.2, "Saving Your OmniPortlet and Web Clipping Customizations"
■
Section 6.9.3, "Running purgeMetadata() for WebCenter Spaces"
■
Section 6.9.4, "Considerations for Upgrading Oracle WebCenter Content or Oracle
ECM"
6.9.1 Exporting Deployment Descriptor for Portlet Producer Applications Secured with
OWSM
In your Oracle WebCenter Portal instance, if Services Portlets producer or any custom
portlet producers are deployed and secured with OWSM security policies, you will
need to re-configure the security policies after patching your instance. To prepare for
this, you must export the Web service deployment descriptors for those portlet
producers to a Java Archive (JAR) file.
To export the Web service deployment descriptors for portlet producers to a JAR file:
Patching Oracle WebCenter Portal 6-43
Pre-Patching Tasks for Oracle WebCenter Portal
1.
Ensure the WC_Portlet managed server and any custom managed servers on
which custom portlet producers are deployed are up and running.
2.
Invoke the WLST script from your WebCenter Portal Oracle home directory and
connect to the Administration Server for Oracle WebCenter Portal. For
information, see the "Running Oracle WebLogic Scripting Tool (WLST)
Commands" section in Oracle Fusion Middleware Administering Oracle WebCenter
Portal.
3.
Run WLST commands to export the Web service deployment descriptors for
portlet producers to a JAR file.
■
Services Portlets producer
This producer is available out-of-the-box from WebCenter Portal release
11.1.1.6.0 onward. If this producer is deployed in your instance, run the
following command:
exportJRFWSApplicationPDD(application,pddJarFileName)
Where, application refers to the location of the Services Portlets producer,
and pddJarFileName refers to the name of the JAR file.
For example:
exportJRFWSApplicationPDD('/wc_domain/WC_
Portlet/services-producer#11.1.1.6.0',
'/tmp/exportPDD-services-producer.jar')
■
Custom portlet producers
You may have various custom portlet producers deployed in your Oracle
WebCenter Portal instance, and have OWSM security policies attached to
custom portlet producers' Web service end points (WSRP_v2_Markup_Service).
You must export the Web service deployment descriptors to a JAR file for each
custom portlet producer before your patch your instance.
For example, if your custom portlet producer is named TestJSR286 and is
deployed to WC_PORTLET managed server with version 1.0, run the following
command to export the deployment descriptor to a JAR file named
exportPDD.jar:
exportJRFWSApplicationPDD('/wls-domain/WC_
PORTLET/TestJSR286#1.0','/tmp/exportPDD.jar')
6.9.2 Saving Your OmniPortlet and Web Clipping Customizations
Perform the procedure listed in this section only if you are
using OmniPortlet and Web Clipping customizations, and they are
stored in a file-based preferences store. By default, in Oracle
WebCenter Portal and Oracle Portal, a file-based preferences store is
not used. Such stores are used by default only for 11g Release 1 (11.1.1)
Portal environments that are upgraded from their 10g versions.
Note:
When you apply the latest patch set for Oracle WebCenter Portal or Oracle Portal, both
the OmniPortlet and Web Clipping applications are re-deployed, and all configuration
data stored within file-based preference stores is lost. You must save the OmniPortlet
6-44 Oracle Fusion Middleware Patching Guide
Pre-Patching Tasks for Oracle WebCenter Portal
and Web Clipping configuration and customizations to ensure that customizations are
not lost when you apply the patch set.
To save and back up your customizations:
1.
Locate the following directories:
On UNIX operating systems:
■
path_to_war_directory/WEB-INF/providers/omniPortlet
■
path_to_war_directory/WEB-INF/providers/webclipping
On Windows operating systems:
■
path_to_war_directory\WEB-INF\providers\omniPortlet
■
path_to_war_directory\WEB-INF\providers\webclipping
Where path_to_war_directory refers to the following path:
■
■
On a UNIX operating system: DOMAIN_HOME/servers/WLS_Portlet/tmp/_WL_
user/portalTools_version/randomly_generated_directory/war
On a Windows operating system: DOMAIN_HOME\servers\WLS_Portlet\tmp\_
WL_user\portalTools_version\randomly_generated_directory\war
Where, DOMAIN_HOME is the domain home locations for your Oracle Portal or
Oracle WebCenter Portal domain, as specified on the "Specify Domain Name
and Location" screen in Creating WebLogic Domains Using the Configuration
Wizard.
2.
Run the following command to back up the directory:
■
On UNIX operating systems:
cp -fr path_to_war_directory/WEB-INF/providers/omniPortlet backup_location
cp -fr path_to_war_directory/WEB-INF/providers/webclipping backup_location
■
On Windows operating systems:
xcopy /y/e path_to_war_directory\WEB-INF\providers\omniPortlet backup_
location
xcopy /y/e path_to_war_directory\WEB-INF\providers\webclipping backup_
location
6.9.3 Running purgeMetadata() for WebCenter Spaces
If you are using WebCenter Spaces, you must run the purgeMetadata() WLST
command to remove older versions of documents in MDS. This enables the patching
process to run on a smaller set of data and thus decrease the time required to upgrade.
To purge metadata for WebCenter Spaces:
1.
Start your Administration Server and Spaces Managed Server (WLS_Spaces) as the
purgeMetadata() command is an online command.
2.
Start WLST from your WebCenter Oracle home.
On UNIX operating systems:
cd WebCenter_ORACLE_HOME/common/bin
./wlst.sh
Patching Oracle WebCenter Portal 6-45
Pre-Patching Tasks for Oracle WebCenter Portal
On Windows operating systems:
cd WebCenter_ORACLE_HOME\common\bin
wlst.cmd
3.
Connect to the Administration Server using the WLST connect() command.
4.
Run the purgeMetadata() WLST command. For example, run the following
command to purge metadata older than 3060 seconds:
purgeMetadata('webcenter', 'WLS_Spaces', 3060)
For more information, see "purgeMetadata" in WLST Command Reference for
WebLogic Server.
5.
Re-collect the database statistics. For example, you can connect to the WebCenter
MDS schema using SQLPlus:
execute dbms_stats.gather_schema_stats(ownname=>null, options=>'GATHER AUTO');
6.
Stop your WLS_Spaces managed server and Administration Server.
For more information, see the "Metadata Services (MDS) Custom WLST Commands"
chapter in WLST Command Reference for WebLogic Server.
6.9.4 Considerations for Upgrading Oracle WebCenter Content or Oracle ECM
Beginning with Release 11.1.1.6.0, Oracle Enterprise Content
Management Suite (Oracle ECM) and Oracle Universal Content
Management (Oracle UCM) have been rebranded (renamed) as Oracle
WebCenter Content, and Oracle Content Server has been renamed as
Oracle WebCenter Content Server (short name Content Server).
Note:
Oracle WebCenter Content includes Content Server. If your Oracle WebCenter Portal
instance uses Content Server as a content repository, consider the following:
■
■
■
If your existing environment uses Oracle Content Server 10g as the content
repository, you must upgrade to Oracle WebCenter Content 11.1.1.9.0. This is
important to take advantage of the full set of features that the 11g release provides.
If you are using Content Server, both Oracle WebCenter Portal and Oracle
WebCenter Content must be of the same patch set level. For example, if you are
patching to Oracle WebCenter Portal 11.1.1.9.0, you must also patch to Oracle
WebCenter Content 11.1.1.9.0.
Oracle WebCenter Portal and Oracle WebCenter Content can be within the same
domain or in separate domains.
For information about upgrading to Oracle WebCenter Content 11g, see Oracle Fusion
Middleware Upgrade Guide for Oracle WebCenter Content.
For Content Server 11g, Oracle recommends Folders (the
FrameworkFolders component) as the folder interface instead of
Contribution Folders (the Folders_g component).
Note:
6-46 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
6.9.4.1 Upgrading Oracle ECM
If you are running a version of Oracle ECM older than 10g Release 3 (10.1.3.5.1), you
must upgrade to the 10g Release 3 (10.1.3.5.1) version before attempting to upgrade to
Oracle WebCenter Content 11.1.1.9.0.
6.10 Post Patching Tasks for Oracle WebCenter Portal
This section describes all the tasks that you may need to perform to complete patching
to Oracle WebCenter Portal release 11.1.1.9.0.
The tasks described in this section are not required for all
patching paths. To determine whether a task is applicable, refer to the
diagram and the table given in this chapter for your existing
environment. For example, if you are patching Oracle WebCenter
Portal 11.1.1.6.0, refer to the diagram and table given in Section 6.4,
"Patching an Oracle WebCenter Portal 11.1.1.6.0 Installation."
Note:
This section contains the following subsections:
■
■
■
■
■
■
■
Section 6.10.1, "Importing Web Service Deployment Descriptors for Portlet
Producers Secured with OWSM"
Section 6.10.2, "Running the upgradeOpss WLST Command"
Section 6.10.3, "Extending the Domain Using the Pagelet Producer Upgrade
Template"
Section 6.10.4, "Updating SSO and OHS Configuration"
Section 6.10.5, "Performing Post-Patching Tasks for Oracle WebCenter 11.1.1.2.0 or
11.1.1.3.0 Installations"
Section 6.10.6, "Performing Post-Patching Tasks for the WebCenter Portal
Application"
Section 6.10.7, "Adding Oracle Single Sign-On Authentication Provider to the List
of Authentication Providers"
■
Section 6.10.8, "Adding New Features to Oracle WebCenter Portal"
■
Section 6.10.9, "Running the upgradeWebCenterPermissions WLST Command"
■
Section 6.10.10, "Resetting Search Customizations"
■
Section 6.10.11, "Updating Resource Protection Level in OAM 11.1.2.2.0"
■
Section 6.10.12, "Restoring Profile Page Customizations"
■
Section 6.10.13, "Removing the -noverify Flag"
6.10.1 Importing Web Service Deployment Descriptors for Portlet Producers Secured
with OWSM
When you patch your Oracle WebCenter Portal instance, the assigned Oracle Web
Services Manager (OWSM) security policies are removed, and no other security policy
is applied. You must restore your previous security policy configuration using the Web
service deployment descriptors for portlet producers you exported in Section 6.9.1,
"Exporting Deployment Descriptor for Portlet Producer Applications Secured with
OWSM."
Patching Oracle WebCenter Portal 6-47
Post Patching Tasks for Oracle WebCenter Portal
To import Web service deployment descriptors for portlet producers secured with
OWSM security policies:
1.
Ensure the WC_Spaces, WC_Collaboration, and WC_Portlet managed servers are
running. If custom portlet producers are deployed to any custom managed
servers, ensure those servers are also up and running.
2.
Connect to the Administration Server for Oracle WebCenter Portal, for running
WLST commands. For information, see the "Running Oracle WebLogic Scripting
Tool (WLST) Commands" section in Oracle Fusion Middleware Administering Oracle
WebCenter Portal.
3.
Run the WLST command to import Web service deployment descriptor for a
custom portlet producer. For example, if your portlet producer's name is
TestJSR286, and it is deployed to the WC_Portlet managed server with version
1.0, run the following command to import the Web service deployment descriptor
from a file named exportPDD.jar.
importJRFWSApplicationPDD('/wls-domain/WC_
PORTLET/TestJSR286#1.0','/tmp/exportPDD.jar')
Note that exportPDD.jar is the same file to which you exported the deployment
descriptor in Section 6.9.1, "Exporting Deployment Descriptor for Portlet Producer
Applications Secured with OWSM."
This step is required only if any custom portlet producers are
deployed in your Oracle WebCenter Portal environment. To attach the
OWSM security policy, you must run the WLST command for each
custom portlet producer separately.
Note:
4.
Run the following WLST command to attach the OWSM security policy to the Web
service endpoint (services-producer) for the Oracle WebCenter Portal's Services
Portlets producer:
importJRFWSApplicationPDD('/wc_domain/WC_Portlet/services-producer#11.1.1.6.0',
'/tmp/exportPDD-services-producer.jar')
Where exportPDD-services-producer.jar is the file from which you want to
import the Web service deployment descriptor.
Oracle WebCenter Portal's Services Portlets producer is
available only from release 11.1.1.6.0 onward. If you are patching
from a previous release and want to deploy the Services Portlets
producer, you must first extend your domain as described in
Section 6.10.8.1, "Installing Activity Graph, Analytics, Pagelet
Producer, Personalization Server, and Services Portlets." Then, attach
the OWSM security policy for the Web services end point for the
Services Portlets producer.
Note:
5.
Restart the WC_Spaces, WC_Collaboration, and WC_Portlet managed servers. Also
restart custom managed servers if custom portlet producers are deployed to those
managed servers.
6-48 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
6.10.2 Running the upgradeOpss WLST Command
The upgradeOpss WLST command updates older configurations and stores to the
latest OPSS security store. For more information, see the "Upgrading Policies with
upgradeOpss" section in Securing Applications with Oracle Platform Security Services.
To run the upgradeOpss WLST command:
1.
Stop the Administration Server and all Managed Servers.
2.
Start WLST from the Oracle Common home.
On UNIX operating systems:
cd ORACLE_COMMON_HOME/common/bin
./wlst.sh
On Windows operating systems:
cd ORACLE_COMMON_HOME\common\bin
wlst.cmd
3.
Ensure the external LDAP server is up and running, then run the upgradeOpss
command in offline mode (without connecting to any server):
On UNIX operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml',
jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/system-jazn-data.xml')
On Windows operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME\\config\\fmwconfig\\jps-config.xml',
jaznData='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\system-jazn-data.xml')
Note: If you need to re-run the upgradeOpss() command, you must
exit the current WLST session and start a new session before
re-running upgradeOpss().
4.
For database-based OPSS policy store, run the upgradeOpss command in offline
mode (without connecting to any server):
■
On UNIX operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME/config/fmwconfig/jps-config.xml',
jaznData='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/system-jazn-data.xml',
auditStore='MW_HOME/oracle_common/modules/oracle.jps_11.1.1/domain_
config/auditstore.xml',
jdbcDriver='oracle.jdbc.driver.OracleDriver',
url='jdbc:oracle:thin:@db_host:db_port:db_sid', user='Prefix_OPSS',
password='password', upgradeJseStoreType='true')
■
On Windows operating systems:
upgradeOpss(jpsConfig='DOMAIN_HOME\\config\\fmwconfig\\jps-config.xml',
jaznData='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\system-jazn-data.xml',
auditStore='MW_HOME\\oracle_common\\modules\\oracle.jps_11.1.1\\domain_
config\\auditstore.xml', jdbcDriver='oracle.jdbc.driver.OracleDriver',
Patching Oracle WebCenter Portal 6-49
Post Patching Tasks for Oracle WebCenter Portal
url='jdbc:oracle:thin:@db_host:db_port:db_sid', user='prefix_OPSS',
password='password', upgradeJseStoreType='true')
6.10.3 Extending the Domain Using the Pagelet Producer Upgrade Template
A new version of Pagelet Producer was released with WebCenter Portal 11.1.1.6.0. If
your upgraded Oracle WebCenter Portal instance already has Pagelet Producer
installed, you can choose to apply the new Pagelet Producer upgrade template to your
domain to take advantage of the new features.
To apply the Pagelet Producer upgrade template:
1.
Stop the Admin server and all managed servers.
2.
Start the Configuration Wizard on the machine running the Admin server.
On UNIX, run WCP_ORACLE_HOME/common/bin/config.sh.
On Windows, run WCP_ORACLE_HOME\common\bin\config.cmd.
Where WCP_ORACLE_HOME refers to the WebCenter Portal Oracle home
directory.
3.
Select Extend an existing WebLogic domain and click Next.
4.
Select your domain and click Next.
5.
Select the Extend my domain using an existing extension template option.
6.
Specify the path to the template, oracle.pagelet-producer-upgrade_template_
11.1.1.jar and click Next. The template is available at the following location:
WCP_ORACLE_
HOME/common/templates/applications/oracle.pagelet-producer-upgrade_
template_11.1.1.jar
7.
Click Next on the remaining screens until you get the Configuration Summary
screen, then click Extend.
For more information on extending a domain, see the "Extending a WebLogic
Domain in Graphical Mode" section in Creating WebLogic Domains Using the
Configuration Wizard.
8.
Start the Admin server and all managed servers.
9.
Reconfigure the Pagelet Producer connections for the WebCenter Portal
application and WebCenter custom applications (Portal Framework applications)
by using Fusion Middleware Control or WLST. For information, see the
"Registering the Pagelet Producer" section in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
6-50 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
In previous releases, it was mandatory to deploy Pagelet
Producer to the following path:
Note:
http://<pagelet-producer-server>:<port>/
Pagelet Producer could not be accessed if it was deployed at any other
location other than the root '/'. From Release 11.1.1.6.0 onward,
Pagelet Producer is deployed to the following path:
http://<pagelet-producer-server>:<port>/pagelets/
Where pagelets refers to any location of your choice where you want
to deploy Pagelet Producer. Therefore, after extending the domain
using the new Pagelet Producer upgrade template, you must
reconfigure your Pagelet Producer connections.
If you have OHS and SSO configured, you must configure them to use
the new context root. For information, see Section 6.10.4, "Updating
SSO and OHS Configuration."
10. Undeploy the older version of Pagelet Producer.
a.
Stop WC_Portlet, the managed server on which Pagelet Producer is running.
b.
In WLS Console, click Deployments.
c.
Select the check box next to pagelet-producer (11.1.1.4.0) deployment.
d.
Click Delete.
11. Target the WebCenterDS data source to WC_Portlet. This is required to enable the
OpenSocial feature.
a.
In WLS Console, go to Services > Data Source.
b.
Click WebCenterDS.
c.
On the Targets tab, select WC_Portlet and click Save.
6.10.4 Updating SSO and OHS Configuration
If you have Oracle HTTP Server (OHS) and Single Sign-on (SSO) configured in your
upgraded Oracle WebCenter Portal environment, you may need to update the
configuration for Pagelet Producer, Portlet Producer applications, and Oracle SES.
This section includes the following subsections:
■
Section 6.10.4.1, "Updating OHS Configuration for Pagelet Producer"
■
Section 6.10.4.2, "Updating SSO Configuration for Pagelet Producer"
■
Section 6.10.4.3, "Updating SSO Configuration for Portlet Producer Applications"
■
Section 6.10.4.4, "Updating SSO Configuration for Oracle SES"
■
Section 6.10.4.5, "Verifying SSOFilter Grant"
6.10.4.1 Updating OHS Configuration for Pagelet Producer
Beginning with Release 11.1.1.6.0, Pagelet Producer's web context root has changed
from "/" to "/pagelets", where pagelets refers to any location of your choice where
Pagelet Producer is deployed. Before Release 11.1.1.6.0, since Pagelet Producer used
Patching Oracle WebCenter Portal 6-51
Post Patching Tasks for Oracle WebCenter Portal
"/" as a web context root, virtual host configuration was recommended, but it is no
longer required.
If you have OHS configured, you must update the OHS entry in mod_wl_ohs.conf.
This file is available at the following path:
WT_ORACLE_HOME/instances/your_instance/config/OHS/ohs1
Where, WT_ORACLE_HOME refers to the Web Tier Oracle Home.
Replace the following entries, if present:
<Location /pageletadmin>
SetHandler weblogic-handler
WebLogicHost webcenter.example.com
WebLogicPort 8889
</Location>
<Location /authenticateWithApplicationServer>
SetHandler weblogic-handler
WebLogicHost webcenter.example.com
WebLogicPort 8889
</Location>
With the following entry:
<Location /pagelets>
SetHandler weblogic-handler
WebLogicHost webcenter.example.com
WebLogicPort 8889
</Location>
6.10.4.2 Updating SSO Configuration for Pagelet Producer
Beginning with Release 11.1.1.6.0, Pagelet Producer's web context root has changed
from "/" to "/pagelets". If SSO is configured for your Oracle WebCenter Portal
environment, you must update your SSO configuration or policy to use the new
context root for protected and public URIs.
This section describes how you can update the policy for OAM 11g, OAM 10g, and
OSSO.
Updating OAM 11g policies for Pagelet Producer
Updating OAM 11g policies for Pagelet Producer involves creating the following
resources:
■
■
■
/pagelets* and /pagelets/.../*
/pagelets/authenticateWithApplicationServer* and
/pagelets/authenticateWithApplicationServer/.../*
/pagelets/admin* and /pagelets/admin/.../*
To update OAM 11g policies for Pagelet Producer:
1.
Log on to the OAM Console using the following URL format:
http://host:port/oamconsole
2.
Go to Policy Configuration > Application Domains. The Policy Manager pane
displays.
3.
Locate the application domain created while registering the WebGate agent.
6-52 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
4.
Open the Resources tab, and click New Resource.
5.
Add the resources for Pagelet Producer applications.
To add the /pagelets* resource:
a.
In Resource Type, select HTTP.
b.
In the Host Identifier field, select the host created while registering the
WebGate agent.
c.
In the Resource URL field, enter the following:
/pagelets*
d.
In the Description field, enter a description for the resource.
e.
Set Protection Level to Unprotected.
f.
Set Authentication Policy to Public Resource Policy.
g.
Set Authorization Policy to Protected Resource Policy.
h.
Click Apply.
6.
Repeat step 5 to add /pagelets/.../* as a resource.
7.
Add /pagelets/authenticateWithApplicationServer* as a resource:
a.
In the Resource Type field, select HTTP.
b.
In the Host Identifier field, select the host created while registering the
WebGate agent.
c.
In the Resource URL field, enter the following:
/pagelets/authenticateWithApplicationServer*
d.
In the Description field, enter a description for the resource.
e.
Set Protection Level to Protected.
f.
Set Authentication Policy to Protected Resource Policy.
g.
Set Authorization Policy to Protected Resource Policy.
h.
Click Apply.
8.
Repeat step 7 to add /pagelets/authenticateWithApplicationServer/.../* as a
protected resource.
9.
Repeat step 7 to add /pagelets/admin* as a protected resource.
10. Repeat step 7 to add /pagelets/admin/.../* as a protected resource.
11. On the Resources tab, search for /pageletadmin* and
/authenticateWithApplicationServer* and remove these old resources.
12. Restart Web Tier and verify your changes.
Updating OAM 10g Policies for Pagelet Producer
Updating OAM 10g policies for Pagelet Producer involves creating the following
resources:
■
/pagelets
■
/pagelets/authenticateWithApplicationServer
■
/pagelets/admin
Patching Oracle WebCenter Portal 6-53
Post Patching Tasks for Oracle WebCenter Portal
To update OAM 10g policies for Pagelet Producer:
1.
Log on to the OAM Console using the following URL format:
http://host:port/access/oblix
2.
Select Policy Manager.
3.
Locate the policy domain that you created to protect your Oracle WebCenter
Portal resources.
4.
Open the Resources tab and click Add.
5.
Add the /pagelets resource. For the resource:
a.
Select HTTP as the resource type.
b.
Select the Host Identifier for the WebCenter Web Tier.
c.
Enter /pagelets as the URL Prefix.
d.
Enter a description for the resource.
e.
Ensure that Update Cache is selected, and then click Save.
6.
Repeat step 5 to add /pagelets/authenticateWithApplicationServer as a
resource.
7.
Repeat step 5 to add /pagelets/admin as a resource.
8.
Go to the Policies tab and locate the public policy.
9.
Open the public policy and select the resource created in step 5 (that is, /pagelets)
to apply public policy to this resource.
Do not select the other two resources
(/pagelets/authenticateWithApplicationServer and /pagelets/admin)
created as we want them to be protected by default.
10. Save your changes.
11. On the Resources tab, delete the old resource entries, /pageletadmin and
/authenticateWithApplicationServer.
12. Restart Web Tier and verify your changes.
Updating OSSO Configuration for Pagelet Producer
If you have an OSSO setup, to update the policy for Pagelet Producer:
1.
In the mod_osso.conf file, replace the following entry:
<Location /pageletadmin>
OssoSendCacheHeaders off
require valid-user
AuthType Osso
</Location>
With:
<Location /pagelets/admin>
OssoSendCacheHeaders off
require valid-user
AuthType Osso
</Location>
2.
Replace the following entry:
6-54 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
<Location /authenticateWithApplicationServer*>
OssoSendCacheHeaders off
require valid-user
AuthType Osso
</Location>
With:
<Location /pagelets/authenticateWithApplicationServer*>
OssoSendCacheHeaders off
require valid-user
AuthType Osso
</Location>
3.
Restart Web Tier and verify your changes.
6.10.4.3 Updating SSO Configuration for Portlet Producer Applications
Beginning with Release 11.1.1.6.0, you must explicitly exclude the portlets URI in an
OAM setup. You must update all custom and out-of-the-box Portlet Producer
applications configured with SSO. For information, see the following sections in Oracle
Fusion Middleware Administering Oracle WebCenter Portal:
■
Configuring Portlet Producer Applications for OAM 11g
■
Configuring Portlet Producer Applications for OAM 10g
6.10.4.4 Updating SSO Configuration for Oracle SES
In Release 11.1.1.4.0 and 11.1.1.5.0, the recommendation was to use virtual host
configuration to configure SES crawl and authorization end points. However, this is no
longer required from Release 11.1.1.6.0 onward. You can consider marking the SES
endpoints as excluded resources in OAM configuration. For information, see the
following sections in Oracle Fusion Middleware Administering Oracle WebCenter Portal:
■
For OAM 11g: Registering the WebGate Agent
■
For OAM 10g: Configuring the WebCenter Portal Policy Domain
6.10.4.5 Verifying SSOFilter Grant
If your environment is configured with Oracle Access Manager SSO, check the OAM
Asserter configured in your WebLogic domain. Ensure the active types chosen are
OAM_REMOTE_USER and ObSSOCookie. If OAM_IDENTITY_ASSERTION is also one of the
chosen active types, you need to ensure the following:
1.
Open the jps-config.xml file. The file is located at the following path:
DOMAIN_HOME/config/fmwconfig/jps-config.xml
Where, DOMAIN_HOME is the domain home location for your Oracle WebCenter Portal
domain.
2.
Ensure AttributeService is configured.
■
The default jps context must have the following entry for configuring the
attribute service:
<serviceInstanceRef ref="attribute"/>
■
The serviceProviders list must contain the following entry:
<serviceProvider
class="oracle.security.jps.internal.attribute.impl.AttributeServiceProvider
Patching Oracle WebCenter Portal 6-55
Post Patching Tasks for Oracle WebCenter Portal
Impl" name="attribute.provider" type="ATTRIBUTE">
<description>Attribute Service Provider</description>
</serviceProvider>
■
The serviceInstances list must contain the following entry:
<serviceInstance provider="attribute.provider" name="attribute">
<description>Attribute Service Instance</description>
<property value="86400" name="attribute.expire.time.seconds"/>
</serviceInstance>
3.
Ensure that the SSOFilter JAR has the AttributeAccessPermission grant. To
verify this, log on to WLST as described in "Running Oracle WebLogic Scripting
Tool (WLST) Commands" in Oracle Fusion Middleware Administering Oracle
WebCenter Portal. Then, run the following WLST command to list permissions:
listCodeSourcePermissions(codeBaseURL="file:${common.components.home}/modules/o
racle.ssofilter_11.1.1/ssofilter.jar")
If you get an output containing the following it means you already have the
required grant.
[Permission Clz Name :
oracle.security.jps.service.attribute.AttributeAccessPermission, Target : *,
Actions : get,set,remove ]
4.
If you do not have the required grant, add it using the following WLST command:
grantPermission(codeBaseURL='file:${common.components.home}/modules/oracle.ssof
ilter_11.1.1/ssofilter.jar',
permClass='oracle.security.jps.service.attribute.AttributeAccessPermission',
permTarget='*', permActions='get,set,remove')
5.
Restart all servers in your WebLogic domain.
6.10.5 Performing Post-Patching Tasks for Oracle WebCenter 11.1.1.2.0 or 11.1.1.3.0
Installations
This section describes the tasks that you may need to perform, depending on your
system environment, after patching to Oracle WebCenter Portal 11.1.1.9.0.
The section contains the following subsections:
■
Section 6.10.5.1, "Migrating Oracle Wiki Pages and Blogs"
■
Section 6.10.5.2, "Migrating Content Presenter Custom Templates"
■
Section 6.10.5.3, "Updating the Configuration for WebCenter REST APIs"
■
Section 6.10.5.4, "Updating Multi-Calendar Layouts"
■
Section 6.10.5.5, "Restoring Your OmniPortlet and Web Clipping Customizations"
■
Section 6.10.5.6, "Extending a Domain to Install Oracle WSM Policy Manager"
■
Section 6.10.5.7, "Remove openusage Properties in setDomainEnv"
■
■
■
Section 6.10.5.8, "Redeploying your Custom Applications to Upgraded Custom
Managed Servers"
Section 6.10.5.9, "Remove the LD_LIBRARY_PATH Entry from the setDomainEnv
Script"
Section 6.10.5.10, "Migrating WSRP Portlet Preferences"
6-56 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
6.10.5.1 Migrating Oracle Wiki Pages and Blogs
This section contains the following sections to help you migrate your existing Wiki
pages and blogs for use in the newly patched Oracle WebCenter Portal domain:
■
Section 6.10.5.1.1, "How to Migrate Oracle Wiki Pages and Blogs"
■
Section 6.10.5.1.2, "Troubleshooting Problems During Wiki Migration"
6.10.5.1.1 How to Migrate Oracle Wiki Pages and Blogs If you had Oracle Wiki installed,
you must run the Wiki Migrator utility wiki-upgrade.jar to migrate the wiki pages
and blogs. The utility is available in the following directory in the WebCenter Portal
Oracle home:
WebCenter_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar
This Wiki Migrator utility migrates your wiki pages and blogs into portal-specific
folders in Content Server, and the upgraded pages for wikis and blogs are migrated
accordingly. The utility also migrates attachments and provides links to them in your
wiki pages as appropriate. Links to other wiki pages within your wiki page content are
updated to point to the new locations, provided that the URL in each link has the same
WebCenter Portal root that is provided in the migration parameters. The utility does
not migrate comments, discussion threads, templates, nor it alters wiki or blog content.
If you encounter any errors during the migration process, check the output log, which
is located in the same directory as the wiki-upgrade.jar file. For more information,
see Section 6.10.5.1.2, "Troubleshooting Problems During Wiki Migration".
Before performing wiki migration, do the following:
1.
Make sure you have upgraded to Oracle WebCenter Content 11.1.1.9.0 (see
Section 6.9.4, "Considerations for Upgrading Oracle WebCenter Content or Oracle
ECM."
2.
Verify that the root folder PersonalSpaces exists in Oracle WebCenter Content;
this is the folder in which all personal folders get created. Wiki migration may fail
if the PersonalSpaces folder does not exist in Oracle WebCenter Content. The
PersonalSpaces folder gets created when the WC_Spaces managed server is
started. Therefore, it is recommended that you start WC_Spaces prior to performing
wiki migration.
3.
Update the folder limit in Oracle WebCenter Content as follows:
a.
Log on to the Oracle WebCenter Content user interface, go to Administration
> Folder Configuration and change the "Maximum Folders Per Virtual
Folder" and "Maximum Content Per Virtual Folder" to 1000.
b.
Create a temporary folder that the Wiki migration utility will use to store
orphan data (for example, the data that does not have a corresponding portal).
This does NOT have to be a root folder; it can be created as the Administrator
user under the PersonalSpaces folder or the Spaces root folder. If a root folder
is preferred, the service using the URL IdcService=COLLECTION_ADD will need
to be used. For example:
http://host:port/idc/idcplg?IdcService=COLLECTION_
ADD&dParentCollectionID=-1&hasParentCollectionID=true&force=true%20&xForceF
olderSecurity=FALSE&ignoreMaxFolderLimit=true&hasMark=true&dCollectionName=
PS3WikiMigration_Orphans&mark=PS3WikiMigration_
Orphans&dDocAccount=PUBLIC&idcToken=1290338486670:A17C2CCCCE0C2FD2544E0A1B2
F03DB67
Patching Oracle WebCenter Portal 6-57
Post Patching Tasks for Oracle WebCenter Portal
Note the idcToken can be retrieved via the browser's Page Source from a
logged in session to Oracle WebCenter Content. Alternatively, the attribute
DisableAuthorizationTokenCheck can be disabled by selecting
Administration > Content Server > General Configuration > Additional
Configuration Variables -> DisableAuthorizationTokenCheck=true and then
restarting the server.
4.
Choose one of the following ways to run the wiki-upgrade.jar file from
WebCenter Portal Oracle home:
■
Do not pass any arguments from the command line, as follows:
> cd WCP_ORACLE_HOME/webcenter/archives
> MW_HOME/jdk160_21/bin/java -jar wiki-upgrade.jar
You will be prompted for each of the required arguments listed in Table 6–8.
■
Pass a properties file (WikiMigrator.properties) as an argument:
MW_HOME/jdk160_21/bin/java
-jar WCP_ORACLE_HOME/webcenter/archives/wiki-upgrade.jar
WikiMigrator.properties
The WikiMigrator.properties must reside in the same directory as
wiki-upgrade.jar. The following is a sample properties file:
MDSConn
= jdbc:oracle:thin:@exampleDB:1521:exampleSID
MDSUser
= dbuser_example_mds
UCMConn
= idc://examplehost:9444
UCMUser
= sysadmin
UCMConnName
= example_connection_name
UCMTempFolderPath = /RootFolder/.../TempFolder
wikiConn
= jdbc:oracle:thin:@exampleDB:1521:exampleSID
wikiUser
= example_wiki
SpacesRootURL = http://examplehost:port/webcenter
You will be prompted for the MDS, UCM, and Wiki passwords from the
command line.
■
Pass all arguments from the command line:
MW_HOME/jdk160_21/bin/java -jar wiki-upgrade.jar
MDSConn MDSUser MDSPswd UCMConn UCMTempFolderPath UCMUser UCMPswd
UCMConnName
wikiConn wikiUser wikiPswd SpacesRootURL
For example:
java -jar WikiMigrator.jar
jdbc:oracle:thin:@exampleDB:1521:exampleSID
dbuser_example_mds
example_mds_password
idc://examplehost:9444
sysadmin
example_ucm_password
example_ucm_connection_name
example_path_to_ucm_temporary_folder
jdbc:oracle:thin:@example:1521:exampleSID
example_wiki
example_wiki_password
http://examplehost:port/webcenter
6-58 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
Table 6–8
Descriptions and Examples of the Wiki Migration Utility Arguments
Argument
Description
MDSConn
Name of the connection used to connect to the MDS data source.
For example: jdbc:oracle:thin:@host:port:SID
MDSUser
Name of the database user used to connect to the MDS data source.
MDSPswd
Password to the database user that is used to connect to the MDS
data source.
UCMConn
Content Server connection URL over the idc protocol.
For example: idc://host:port
UCMUser
Use sysadmin as the Content Server user; the user weblogic does not
get administrator privileges with socket connections.
UCMPswd
Password for the Content Server user account.
UCMConnName
Name used in Enterprise Manager or WLST to create the connection
to Content Server.
UCMTempFolderPath
Temporary folder on Content Server to store orphaned data
For example: /RootFolder/.../TempFolder
wikiConn
Name of the connection used to connect to the Wiki data source.
For example: jdbc:oracle:thin:@host:port:SID
wikiUser
Name of the database user that is used to connect to the Wiki data
source.
wikiPswd
Password for the database user connecting to the Wiki data source.
SpacesRootURL
WebCenter Portal root URL.
For example: http://host:port/context_root
If you have wiki or blog pages that use Query String
parameters, then after upgrade these parameters do not take effect.
Any links that pointed to other wiki pages through a URL such as the
following are converted to a Resource Action Handler URL that points
to the corresponding wiki document in the content repository,
assuming the server:port value entered for SpacesRootURL matches
the server:port value in the URL.
Note:
http://server:port/owc_
wiki/page/show.jz?inline=1&scope=#{communityContext.communityName}&
theme=#{adfFacesContext.skinFamily}
Special Note for 10g and Release 1 (11.1.1.1.0) Users
If you are upgrading from a 10g release or Release 1 (11.1.1.1.0) version of Wiki, then
after you run the Migrator utility wiki-upgrade.jar, there may be some wiki and blog
folders that end up in the MigrationTemp folder. You must manually move these
folders to the correct portal folders on Content Server.
Perform the following steps after migrating Oracle Wiki pages and blogs:
1.
Log on to Content Server and go to the MigrationTemp folder under sysadmin (or
the Content Server user running the migration program). Move the wiki and blog
folders to the correct portal folders. You may need to rename the wiki and blog
folders to match the corresponding portal names in WebCenter Portal.
Patching Oracle WebCenter Portal 6-59
Post Patching Tasks for Oracle WebCenter Portal
2.
Log on to the WebCenter Portal application, navigate to the required portal and
create a new page with Wiki or Blog page style. The name of the page must match
the name of the wiki/blog folder in order for the page to properly display the
wiki/blog content.
6.10.5.1.2 Troubleshooting Problems During Wiki Migration During wiki migration, you
may see some error messages in the output log. Descriptions and available
workarounds are described below.
Error Message 1
[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - there is no webcenter page information stored on
the domain: domain_name
This message indicates that there is no data specified in the domain to connect it with a
portal (previously called group space) page (the wcURL on the domain is missing).
The last part of the migration program will find any remaining
unmigrated portal pages that still point to owc_wiki and will try to
gather domain information from the page's source URL to be matched
against a jzwiki domain. If the proper information is found, it will
move the folder and content out of migration temp and into the proper
portal folder.
Note:
Error Message 2
[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - invalid group space that corresponds to the
guid: portal_guid
This message indicates that there is either no portal information specified in the
domain, or the portal GUID specified is not valid (the portal GUID specified in the
wcURL is not valid).
Error Message 3
[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - no group space that corresponds to the guid:
portal_guid
This message indicates that the domain's portal information points to a portal that no
longer exists. Doing a lookup with the portal GUID does not find a corresponding
portal name. Most likely the portal has been deleted.
Error Message 4
[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - no UCM folder for the groupspace exists: page_
name, gsname: portal_name
This message indicates that the portal page has been migrated already, but the Content
Server folder for that portal does not exist.
To correct this, create the portal folder (by provisioning the Document feature in the
portal), and then move the folder (with the same name as the domain) from migration
temp to the portal folder. Then rename the domain folder to have the same name as
the page.
Error Message 5
6-60 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - could not get UCM folder for the wiki domain,
page: page_name, gsname: portal_name
This message indicates that the portal page has been migrated already, but the Content
Server folder for domain could not be created in the portal folder.
To correct this, move the folder (with the same name as the domain) from migration
temp to the portal folder. Then rename the domain folder to have the same name as
the page.
Error Message 6
[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - no UCM folder exists for the user: user_name,
page: page_name
This message indicates that the portal page has been migrated already, but the Content
Server folder for the user does not exist.
To correct this, create the user's personal folder (this folder is created when the user
accesses Documents from the Home portal), and then move the folder (with the same
name as the domain) from migration temp to the personal folder. Then rename the
domain folder to have the same name as the page.
Error Message 7
[INFO] PROCESSING Domain: domain_name
[ERROR] migrating to temp folder - could not get personal UCM folder for the user:
user_name, page: page_name
This message indicates that the portal page has been migrated already, but the Content
Server folder for the domain could not be created in the user's personal folder.
To correct this, move the folder (with the same name as the domain) from migration
temp to the user's personal folder. Then rename the domain folder to have the same
name as the page.
Error Message 8
[INFO] PROCESSING Domain: domain_name
[INFO] migrating to temp folder - default scope, but no user specified on page:
page_name
This message indicates that this is a personal wiki or blog, but the information stored
on the domain (the wcURL passed in from the spaces page) does not indicate a user.
Error Message 9
[INFO] PROCESSING Domain: domain_name
[INFO] sourceUrl: source_url
[INFO] migrating to temp folder - the page source url is not pointing to the
correct domain, page: page_name, wcURL: wcURL
This message indicates that there is more than one domain pointing to the same portal
and page information, and the current domain being processed does not match the
domain indicated in the source URL.
Error Message 10
[INFO] PROCESSING User Blog: blog_name
[INFO] migrating to temp folder - could not get user UCM folder for the user:
user_name
Patching Oracle WebCenter Portal 6-61
Post Patching Tasks for Oracle WebCenter Portal
This is a jzwiki user blog that is not connected with a domain. The message indicates
that the Content Server folder for the user does not exist, so the content could not be
migrated there.
Error Message 11
[INFO] PROCESSING User Blog: blog_name
[INFO] migrating to temp folder - could not get UCM folder for the user: user_name
This is a jzwiki user blog that is not connected with a domain. The message indicates
that the "Blogs" Content Server folder for the user does not exist and could not be
created, so the content could not be migrated there.
6.10.5.2 Migrating Content Presenter Custom Templates
Content Presenter custom templates used in Release 11.1.1.3.0 applications are not
automatically migrated when you upgrade to Release 11.1.1.9.0. You must register the
required custom templates in Release 11.1.1.9.0 version of your applications.
To migrate Content Presenter custom templates from Release 11.1.1.3.0:
1.
In JDeveloper 11.1.1.9.0, create or open a Portal Framework application
(previously called WebCenter Portal application)
2.
On the filesystem, copy your Release 11.1.1.3.0 .jsff files to your Release
11.1.1.9.0 application.
From the Release 11.1.1.3.0 version of your application, copy the required custom
template from following folder:
PROJECT_ROOT/public_html/oracle/webcenter/content/templates/custom
Copy the custom template to the following folder of your application upgraded to
Release 11.1.1.9.0:
PROJECT_ROOT/public_html/oracle/webcenter/portalapp
3.
In JDeveloper, create the Content Presenter custom template as a portal resource.
The properties that you set for the custom template must match those that were
previously registered in your Release 11.1.1.3.0 application.
For information, see the "Export a Content Presenter Display Template as a Portal
Resource" section in Oracle Fusion Middleware Developing Portals with Oracle
WebCenter Portal and Oracle JDeveloper.
4.
Redeploy your application using the new custom Managed Servers, as described
in Section 6.10.5.8, "Redeploying your Custom Applications to Upgraded Custom
Managed Servers."
5.
If the custom template is also used in WebCenter Portal, prepare the template to be
used in your upgraded environment:
a.
Using JDeveloper, export the Content Presenter display template as a portal
resource.
b.
Log on to the WebCenter Portal application and navigate to Portal Builder
Administration.
c.
Select Shared Assets > Content Presenter and upload your template.
For information, see the "Making Content Presenter Display Templates Available"
section in Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal
and Oracle JDeveloper.
6-62 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
6.10.5.3 Updating the Configuration for WebCenter REST APIs
Before you can use the WebCenter Representational State Transfer (REST) APIs, you
must perform server-side configurations. You must configure an identity asserter. You
must also seed the required entries in the credential store, which enables the REST
security tokens to function properly.
This section includes the following subsections:
■
Section 6.10.5.3.1, "Configure an Identity Asserter"
■
Section 6.10.5.3.2, "Configure the Credential Store"
This configuration is not required for the navigation REST
APIs or for the CMIS REST APIs.
Note:
For more information about security tokens, see the "Security Considerations for CMIS
REST APIs" section in Oracle Fusion Middleware Developing Portals with Oracle
WebCenter Portal and Oracle JDeveloper.
6.10.5.3.1 Configure an Identity Asserter You must configure an identity asserter before
using the REST APIs. For detailed instructions, see the "Configuring the REST Service
Identity Asserter" section in Oracle Fusion Middleware Administering Oracle WebCenter
Portal.
6.10.5.3.2 Configure the Credential Store You must seed entries in the credential store
that enable the REST security tokens to function properly. Run the following WLST
commands to configure the credential store:
createCred(map="o.webcenter.jf.csf.map", key="keygen.algorithm",
user="keygen.algorithm", password="AES")
createCred(map="o.webcenter.jf.csf.map", key="cipher.transformation",
user="cipher.transformation", password="AES/CBC/PKCS5Padding")
Run these commands while the Administration server is running. You do not have to
restart the server after executing these commands. For more information, see the
"createCred" command in WLST Command Reference for WebLogic Server.
6.10.5.4 Updating Multi-Calendar Layouts
In Release 11.1.1.2.0 and 11.1.1.3.0, the Calendar Overlay Style FULL could be used to
enable multiple calendars for some events task flow and add multiple portal calendars
in one events task flow. In the upgraded Release 11.1.1.9.0, the Events task flow no
longer displays multiple calendars; only the current portal calendar is displayed.
To work around this issue, you must enable the calendar overlaying feature for the
Events task flow. Go to the page editor, find the Calendar Overlay Style parameter
and select Full from the list of available options. For more information, see the
"Displaying Additional Calendars" section in Oracle Fusion Middleware Building Portals
with Oracle WebCenter Portal.
6.10.5.5 Restoring Your OmniPortlet and Web Clipping Customizations
After you have saved your OmniPortlet and Web Clipping customizations ( as
described in Section 6.9.2, "Saving Your OmniPortlet and Web Clipping
Customizations") and successfully patched your software, you must restore them.
Patching Oracle WebCenter Portal 6-63
Post Patching Tasks for Oracle WebCenter Portal
The Web Clipping portlet has been deprecated in Release 11g
(11.1.1.9.0). Consider using a clipper pagelet using Oracle WebCenter
Portal's Pagelet Producer. For more information, see the "Managing
the Pagelet Producer" chapter in Oracle Fusion Middleware
Administering Oracle WebCenter Portal.
Note:
To restore OmniPortlet and Web Clipping configuration and customizations:
1.
Navigate to the following directories:
On UNIX operating systems:
■
path_to_war_directory/WEB-INF/providers/omniPortlet
■
path_to_war_directory/WEB-INF/providers/webclipping/
Where path_to_war_directory refers to DOMAIN_HOME/servers/WC_
Portlet/tmp/_WL_user/portalTools_version/randomly_generated_
directory/war
On Windows operating systems:
■
path_to_war_directory\WEB-INF\providers\omniPortlet
■
path_to_war_directory\WEB-INF\providers\webclipping/
Where path_to_war_directory refers to DOMAIN_HOME\servers\WC_
Portlet\tmp\_WL_user\portalTools_version\randomly_generated_
directory\war
DOMAIN_HOME is the domain home locations for your Oracle Portal or Oracle
WebCenter Portal domain, as specified on the "Specify Domain Name and
Location" screen in the Configuration Wizard in Creating WebLogic Domains Using
the Configuration Wizard.
Since the Patch Set Installer re-deployed the OmniPortlet and
Web Clipping applications, the new path may be different than the
path from where you backed up customizations.
Note:
2.
Replace these directories with their backed up copies.
For example, to restore the omniportlet directory, you can use the following
commands:
On a UNIX operating system:
cp -fr backup_location path_to_war_directory/WEB-INF/providers/omniPortlet
On a Windows operating system:
xcopy /y/e backup_location path_to_war_directory\WEB-INF\providers\omniPortlet
3.
Restart the Managed Server WC_Portlet.
6.10.5.6 Extending a Domain to Install Oracle WSM Policy Manager
If discussions server is the only Oracle WebCenter Portal application installed in the
domain, you must extend the domain to install Oracle WSM Policy Manager, if not
already installed.
To extend an Oracle WebCenter Portal domain to install Oracle WSM Policy Manager:
6-64 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
1.
Stop the Admin server and all managed servers.
2.
Start the Configuration Wizard on the machine running the Admin server.
On UNIX, run WCP_ORACLE_HOME/common/bin/config.sh.
On Windows, run WCP_ORACLE_HOME\common\bin\config.cmd.
Where WCP_ORACLE_HOME refers to WebCenter Portal Oracle home directory.
3.
Select Extend an existing WebLogic domain and click Next.
4.
Select your domain and click Next.
5.
Select the check box for Oracle WSM Policy Manager and click Next.
6.
Enter the connection details for OWSM MDS Schema and click Next.
7.
Click Next on the remaining screens until you get the Configuration Summary
screen, then click Extend.
For more information on extending a domain, see the "Extending a WebLogic
Domain in Graphical Mode" section in Creating WebLogic Domains Using the
Configuration Wizard.
If your domain is running on multiple machines, you must
pack the domain on the machine running the Administration Server
and unpack on the other machines. For information, see Section 6.6.3,
"Updating Oracle WebCenter Portal Using WLST Commands."
Note:
6.10.5.7 Remove openusage Properties in setDomainEnv
If you want to extend your Oracle WebCenter Portal domain to install Analytics
Collector, you must remove the openusage properties:
1.
Back up the DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating
systems) or DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems).
2.
Remove the openusage properties from EXTRA_JAVA_PROPERTIES in
setDomainEnv.sh or setDomainEnv.cmd.
Specifically, the entries that need to be removed are:
EXTRA_JAVA_PROPERTIES="-Doracle.wc.openusage.clustername=localhost
-Doracle.wc.openusage.collectorport=port_number
-Doracle.wc.openusage.timeout=30
-Doracle.wc.openusage.unicast=true
-Doracle.wc.openusage.enabled=false
${EXTRA_JAVA_PROPERTIES}"
export EXTRA_JAVA_PROPERTIES
These entries may appear multiple times in setDomainEnv.sh
or setDomainEnv.cmd. So ensure that all the entries are removed.
Note:
If you extend your domain to add new products, you may need to
repeat the task of removing the openusage properties from
setDomainEnv.
3.
Restart all the servers in the Oracle WebCenter Portal domain.
Patching Oracle WebCenter Portal 6-65
Post Patching Tasks for Oracle WebCenter Portal
6.10.5.8 Redeploying your Custom Applications to Upgraded Custom Managed
Servers
If there are custom Managed Servers in your domain, they may not have the correct
libraries targeted. Therefore you must upgrade them after patching Oracle WebCenter
Portal, and redeploy your Portal Framework applications (previously called custom
applications).
To upgrade custom managed servers:
1.
Remove the old custom Managed Servers.
2.
Use Repository Creation Utility (RCU) to install the ACTIVITIES schema for the
custom managed server. For information, see the "Obtaining and Running
Repository Creation Utility" chapter in Oracle Fusion Middleware Repository Creation
Utility User's Guide.
3.
Run the Configuration Wizard to extend your existing Oracle WebCenter Portal
domain and apply custom templates.
a.
On the "Select Extension Source" screen, select Extend my domain using an
existing extension template.
b.
Navigate to the WCP_ORACLE_HOME/common/templates/applications (on
UNIX operating systems) or WCP_ORACLE_
HOME\common\templates\applications (on Windows operating systems)
directory and locate the following templates:
oracle.wc_custom_portal_template_11.1.1.jar (for WebCenter custom
applications/Portal Framework applications)
oracle.wc_custom_services_producer_template_11.1.1.jar (for
WebCenter Custom Producer/Portlet Producer applications)
c.
4.
Select the desired template and complete the domain extension process.
Re-deploy your applications using the new custom Managed Servers.
Oracle recommends that you open your projects in Oracle
JDeveloper and migrate your applications to the latest version before
deploying to the new custom Managed Servers.
Note:
6.10.5.9 Remove the LD_LIBRARY_PATH Entry from the setDomainEnv Script
After patching Oracle WebCenter Portal, you must remove the following entry from
the setDomainEnv script:
LD_LIBRARY_PATH="${WL_HOME}/server/native/linux/i686${CLASSPATHSEP}${LD_LIBRARY_
PATH}"
export LD_LIBRARY_PATH
The setDomainEnv script is available at the following path:
■
DOMAIN_HOME/bin/setDomainEnv.sh (on UNIX operating systems)
■
DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows operating systems)
If you extend your domain to add new products, you may
need to repeat this task.
Note:
6-66 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
6.10.5.10 Migrating WSRP Portlet Preferences
By default, all custom JSR286 portlets (created using Portlet Creation Wizard) use a
file-based preference store. Post upgrade, you must move WSRP portlet preferences
from:
$MW_HOME/WCP_ORACLE_HOME/portal/portletdata
To:
$MW_HOME/oracle_common/portal/portletdata
Where, MW_HOME refers to Middleware Home, and WCP_ORACLE_HOME refers to the
WebCenter Portal Oracle Home directory.
You can move WSRP portlet preferences manually or by using a migration utility. For
more information, see the "Migrating a WSRP Producer Persistence Store" chapter in
Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal and Oracle
JDeveloper.
6.10.6 Performing Post-Patching Tasks for the WebCenter Portal Application
After patching to release 11.1.1.9.0, you must reconfigure WebCenter Portal
(previously named WebCenter Spaces).
This section contains the following topics:
■
Section 6.10.6.1, "Setting the Web Server Context Root on the Content Server
Connection"
■
Section 6.10.6.2, "Configuring WebCenter Portal Workflows"
■
Section 6.10.6.3, "Updating the Timezone Attribute"
■
Section 6.10.6.4, "Updating the Portal Display Mode"
■
Section 6.10.6.5, "Choosing a Default Start (or Landing) Page"
■
Section 6.10.6.6, "Migrating WebCenter Portal Customizations"
■
Section 6.10.6.7, "Upgrading Process Spaces"
■
Section 6.10.6.8, "Granting Permissions to Manage Assets"
6.10.6.1 Setting the Web Server Context Root on the Content Server Connection
If Oracle WebCenter Content and WebCenter Portal instances are configured for access
through a common Oracle HTTP server, the Web Server Context Root property
(WebContextRoot) on the existing Content Server connection can be set to make
Content Server features available in the WebCenter Portal application via an iFrame.
The Content Server connection can be set either through Fusion Middleware Control
or WLST using the setJCRContentServerConnection command. For information, see
the "Setting Connection Properties for the WebCenter Portal Content Repository"
section in Oracle Fusion Middleware Administering Oracle WebCenter Portal.
6.10.6.2 Configuring WebCenter Portal Workflows
If your WebCenter Portal instance had WebCenter Portal workflows (previously called
Group Space Workflows) configured, after upgrading to the latest release you must
redeploy sca_CommunityWorkflows.jar and WebCenterWorklistDetailApp.ear.
To configure WebCenter Portal workflows:
1.
Log on to Fusion Middleware Control.
Patching Oracle WebCenter Portal 6-67
Post Patching Tasks for Oracle WebCenter Portal
2.
Deploy sca_CommunityWorkflows.jar to the Oracle SOA managed server. This file
is located at the following path in your Oracle SOA Suite installation:
SOA_ORACLE_HOME/webcenter/modules/oracle.webcenter.sca_11.1.1/sca_
CommunityWorkflows.jar
Where, SOA_ORACLE_HOME refers to the Oracle SOA Suite installation directory.
Note that version 11.1.1.9.0 is active in the console, and other older versions are
inactive.
For information about deploying the JAR using Fusion Middleware Control, see
the "Deploying SOA Composite Applications" section in Administering Oracle SOA
Suite and Oracle Business Process Management Suite.
For information about deploying the JAR using WLST, see the "Deployment
Commands" section in WLST Command Reference for WebLogic Server.
3.
Undeploy WebcenterWorklistDetailApp.ear, and then redeploy it to the SOA
managed server. You can find the application at the following location in your
Oracle SOA Suite installation:
SOA_ORACLE_HOME/webcenter/applications/WebCenterWorklistDetailApp.ear
For information about deploying the EAR using WLST, see the "Deploying
Applications" chapter in Oracle Fusion Middleware Administrator's Guide. For
information about deploying the EAR using Fusion Middleware Control, see the
"Deploying the Application to a WebLogic Managed Server" section in Oracle
Fusion Middleware Administering Oracle WebCenter Portal.
6.10.6.3 Updating the Timezone Attribute
In Release 11.1.1.2.0, the Timezone attribute in WebCenter Spaces is a free-form text
field. From Release 11.1.1.4.0 onward, this attribute was changed to a drop-down list.
If you are upgrading WebCenter Spaces from Release 11.1.1.2.0, the Timezone attribute
is not carried over, and you must manually select the appropriate timezone.
6.10.6.4 Updating the Portal Display Mode
If you have upgraded portals (previous called group spaces) from Release 11.1.1.2.0 or
11.1.1.3.0, you must update the metadata of your portals to ensure that they display
correctly.
To update a portal to display correctly:
1.
Export the portal. For information, see the "Creating Portal Archives" section in
Oracle Fusion Middleware Administering Oracle WebCenter Portal.
2.
At a command prompt, go to the directory where you saved the export archive.
3.
Extract the metadata from the export archive.
For example, the following code extracts the export archive named export.ear,
which contains transport.mar. The code further extracts transport.mar in a
directory named mar.
a.
jar xvf export.ear transport.mar
b.
mkdir mar
c.
cd mar
d.
jar xvf ../transport.mar
6-68 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
The transport.mar file contains space.xml that you must edit to update the
portal's display mode.
4.
Open the space.xml file from the following path:
oracle/webcenter/space/metadata/spaces/portalName/space.xml
Where, portalName refers to the name of the portal whose display mode you are
updating.
5.
Delete the entire <shell-chrome-type> entry from space.xml.
6.
Update the export archive.
For example, the following code updates the space.xml file in transport.mar, and
then updates transport.mar in export.ear.
7.
a.
jar uvfM ../transport.mar
oracle/webcenter/space/metadata/spaces/portalName/space.xml
b.
cd ..
c.
jar uvfM export.ear transport.mar
Import the portal. For information, see the "Importing One or More Portals from
an Archive" section in Oracle Fusion Middleware Administering Oracle WebCenter
Portal.
6.10.6.5 Choosing a Default Start (or Landing) Page
By default, when you log on to the WebCenter Portal application, the last accessed
page is displayed. This behavior can be overridden by setting the
oracle.webcenter.spaces.disableLastAccessPageBehavior system property to
false in the setDomainEnv domain startup script. This script is available at DOMAIN_
HOME/bin/setDomainEnv.sh (on UNIX operating systems) or DOMAIN_
HOME\bin\setDomainEnv.cmd (on Windows operating systems).
If you had overridden the default behavior, you must re-apply this setting after
patching Oracle WebCenter Portal. For information, see the "Choosing a Default Start
(or Landing) Page" section in Oracle Fusion Middleware Using Oracle WebCenter Portal.
6.10.6.6 Migrating WebCenter Portal Customizations
WebCenter Portal can be customized, for example to deploy additional shared libraries
that include custom code or some additional assets (previously called resources) like
task flows, page styles, and skins. If you deployed any custom page styles by
extending WebCenter Spaces 11.1.1.2.0 or 11.1.1.3.0 through the custom library
custom.webcenter.spaces.war, then after patching you must modify the entry for
each page style in the custom library and redeploy custom.webcenter.spaces.war.
To migrate WebCenter Portal customizations:
1.
In JDeveloper, open ExtendWebCenterSpaces.jws (11.1.1.2.0 or 11.1.1.3.0).
2.
For each and every deployed page style, find the following:
<af:pageTemplate
And replace it with the following:
<af:pageTemplate
value="#{bindings.shellTemplateBinding.templateModel}" id="T"
3.
For each and every pageDef, find the following:
Patching Oracle WebCenter Portal 6-69
Post Patching Tasks for Oracle WebCenter Portal
<page>
And replace it with the following:
<page
viewId="#{WCAppContext.application.siteTemplateManager.currentSiteTemplateViewI
d}" id="shellTemplateBinding" Refresh="ifNeeded" />
4.
Redeploy the custom.webcenter.spaces.war shared library to your WC_Spaces
11.1.1.9.0 managed server.
Always use Oracle JDeveloper 11.1.1.2 or 11.1.1.3 to build and
deploy extensions developed for this release. For detailed steps, see
the links for white papers "Extending WebCenter Spaces (11.1.1.2.0)"
or "Extending WebCenter Spaces (11.1.1.3.0)" on Oracle Technology
Network:
http://www.oracle.com/technetwork/middleware/webcenter/porta
l/overview/index.html
Note:
6.10.6.7 Upgrading Process Spaces
Oracle Business Process Management (Oracle BPM) Process Spaces is a workspace
built on top of WebCenter Portal, and provides portals that are designed specifically
for modeling and executing business processes. If you have Process Spaces installed,
then after patching to WebCenter Portal 11.1.1.9.0, you must upgrade it by running the
install.xml script. The installation script can be used for a single-server configuration
as well as a cluster configuration.
To extend your Oracle WebCenter Portal 11.1.1.9.0 domain
with Oracle BPM 11.1.1.7.0 Process Spaces, you may also need to
apply a patch. For information, refer to the latest Oracle Fusion
Middleware Release Notes on OTN here:
Note:
http://www.oracle.com/technetwork/middleware/fusion-middlewa
re/documentation/index.html
For more information about the Process Spaces functionality, see the "Using Oracle
Business Process Management Process Spaces" part in User's Guide for Oracle Business
Process Management.
The procedure described in this section applies only if you
have upgraded your existing Oracle WebCenter Portal installation to
the latest release, and Process Spaces is already enabled on Webcenter
Portal.
Note:
For information about enabling Process Spaces in a new Oracle
WebCenter Portal installation (or new domain), see the "Extending a
Domain to Enable Oracle BPM Process Spaces" section in Oracle Fusion
Middleware Installation Guide for Oracle WebCenter Portal.
To upgrade Process Spaces for your upgraded Oracle WebCenter Portal instance:
1.
Take the Process Workspace and Modeling Space offline.
a.
Log on to WebCenter Portal.
6-70 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
2.
b.
Click the Administration link to open WebCenter Portal administration pages.
c.
Under the Portals tab, select the Modeling Space row.
d.
From the Actions menu, select Take Offline.
e.
In the Take Portal Offline dialog, click OK.
f.
Repeat this procedure to take Process Workspace offline.
Copy the process_spaces folder from the SOA Oracle home directory to any
location on the system where Oracle WebCenter Portal is installed. Copy the folder
from the following location:
On UNIX: SOA_ORACLE_HOME/bpm/process_spaces
On Windows: SOA_ORACLE_HOME\bpm\process_spaces
3.
Open the process-portal-install.properties file from the newly copied
process_spaces folder on your Oracle WebCenter Portal system.
4.
Specify the required Oracle BPM and Oracle WebCenter Portal properties as listed
in Table 6–9.
For security purposes, you can skip specifying the passwords,
and provide them later when prompted.
Note:
Table 6–9
Properties Specified in process-portal-install.properties
Property
Description
extendSoa
The flag to decide whether to extend the existing BPM
domain or create a new one. Specify the value as true if
WebCenter Portal and SOA are in the same domain, else
false.
promptForPasswords
The flag to decide whether to prompt for passwords or read
them from the process-portal-install.properties file
while running the installer.
Oracle BPM Schema Details
bpmDBUser
User name to connect to the database configured for Oracle
BPM
bpmDBPassword
Password to connect to Oracle BPM's database
bpmDBType
Database type configured for Oracle BPM
bpmDBDriver
Driver used to connect to Oracle BPM's database
bpmDBUrl
URL of Oracle BPM's database, like
jdbc:oracle:thin:@adc2170307:1521
Oracle BPM MDS Details
bpmMDSUser
User name for the MDS schema used for Oracle BPM
bpmMDSPassword
Password for Oracle BPM's MDS schema
Oracle BPM Runtime Details
Patching Oracle WebCenter Portal 6-71
Post Patching Tasks for Oracle WebCenter Portal
Table 6–9 (Cont.) Properties Specified in process-portal-install.properties
Property
Description
bpmServerURL
Oracle BPM server URL.
For a single BPM server:
t3://<bpmHost>:<bpmRuntimePort>
For example: t3://myHost:8001
For BPM cluster, specify separated list of BPM server URLs
for all servers in the cluster in the following format:
t3://host1:port1,host2:port2,...
For example,
t3://myHost1:8001,myHost2:8002,myHost3:8003
bpmAdminUser
Name of the user that has Administrator privileges on the
Oracle BPM server
bpmAdminPassword
Password for the Oracle BPM Admin user
WebCenter Portal Installation
Details
wcOracleHome
Path to the WebCenter Portal Oracle home directory
wcDomainName
Name of the domain where Oracle WebCenter Portal is
installed. If extendSoa flag is set to true, point to the BPM
domain.
wcSetDomainRealmPassword
Flag to control whether to set the domain realm password;
set the value to either true or false.
Note: This property is for setting up Global Trust. It is
recommended that you set Global Trust manually; so set
this property to false.
wcDomainRealmPassword
Password to set up trusted domains. Same password must
be set on Oracle BPM domain as well.
Note: This property is for setting up Global Trust. It is
recommended that you set Global Trust manually, and not
by using this property.
wc.server.port
Port on which WC_Spaces managed server is hosted
Oracle WebCenter Portal's
WebLogic Installation Details
wcHost
Host name on which Oracle WebCenter Portal's
Administration server is running
wcAdminPort
Port number on which Oracle WebCenter Portal's
Administration server is running
wcAdminUser
Admin user for the Administration server
wcAdminPwd
Password of the Administration server
wcManagedServerName
In a single-server environment, specify the name of the
managed server where WebCenter Portal is deployed.
In a clustered environment, specify the name of any one of
the WebCenter Portal managed servers that is part of the
cluster.
6-72 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
Table 6–9 (Cont.) Properties Specified in process-portal-install.properties
Property
Description
wcConfigServices
Flag to configure the Content Server and Discussions Server
to work with Oracle WebCenter Portal. The Content Server
and Discussion Server details listed later in this table must
be specified only if wcConfigServices is set to true.
Note: It is strongly recommended that instead of using the
install.xml script to configure Content Server and
Discussion Server by setting wcConfigServices to true, you
should set wcConfigServices to false, and manually
configure Content Server and Discussion Server to work
with Oracle WebCenter Portal. For information, see the
"Managing Content Repositories" and "Managing
Announcements and Discussions" chapters in Oracle Fusion
Middleware Administering Oracle WebCenter Portal.
isWebcenterClusterConfig
Flag to specify whether Oracle WebCenter Portal
installation is configured for a cluster. Set to true if it is a
cluster configuration.
wcSpacesClusterName
Name of the WebCenter Portal application's cluster.
Set this property only if isWebcenterClusterConfig is set to
true.
Content Server Details
Set these properties if wcConfigServices is set to true.
wcContentServerName
Name of the host Content Server configured for Oracle
WebCenter Portal
wcContentServerPort
Port on which Content Server is running.
wcContentSpacesRoot
Name of the WebCenter Portal root folder on Content
Server
wcContentAdminUser
Name of the Admin user for Content Server
Discussion Server Details
Set these properties if wcConfigServices is set to true.
wcDiscussionServerUrl
Name of the Discussion Server configured for WebCenter
Portal
wcDiscussionAdminUser
Name of the Admin user for Discussion Server
5.
Make sure you have ant and Java JDK installed.
Ant is shipped with Oracle BPM. You can find the installer under the path SOA_
ORACLE_HOME/modules/org.apache.ant_1.7.0.
6.
Ensure that the PATH and CLASSPATH environment variables are set for both ant
and Java JDK.
7.
Run the ant script install.xml:
SOA_ORACLE_HOME/modules/org.apache.ant_1.7.0/bin/ant -f install.xml
-DpromptForPasswords=true
Use the -DpromptForPasswords=true argument only if you did not specify
passwords in the process-portal-install.properties file.
8.
If wcConfigServices is set to true in process-portal-install.properties, do
the following:
a.
Restart WC_Spaces. Running the install.xml script shuts down the WC_
Spaces managed server.
Patching Oracle WebCenter Portal 6-73
Post Patching Tasks for Oracle WebCenter Portal
b.
Run the install script again to complete the post upgrade steps. Use the
following command:
ant -f install.xml post-install -DpiArgs -importGSOnly
If wcConfigServices is set to false, you do not need to run
the install script again.
Note:
9.
If Oracle BPM and Oracle WebCenter Portal have been configured in different
domains, configure Trusted Domain Credentials in both the Oracle BPM and
Oracle WebCenter Portal domains, and restart the Oracle BPM Admin Server and
the Oracle WebCenter Portal Admin Server.
For more information, see the "Enabling Trust Between WebLogic Server Domains"
chapter in Administering Security for Oracle WebLogic Server.
10. Start Oracle BPM. For information, see the "Configuring Oracle SOA Suite and
Oracle Business Process Management Suite" chapter in Oracle Fusion Middleware
Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
If Oracle BPM is not up and running, you may face problems
logging into WebCenter Portal.
Note:
If required, bring the Process Workspace and Modeling Space online
by selecting Bring Online from the Actions menu, as described in
step 1.
11. In WebCenter Portal, delete the old process spaces, templates, and resources, if
required.
When you run the install.xml ant script, Release 11.1.1.4.0 or 11.1.1.5.0 process
spaces and related templates and resources are imported with '11.1.1.9.0'
appended to their names. So, after the upgrade, there are two sets of process
spaces and related templates and resources, for example 'Process Workspace
11.1.1.9.0' and 'Process Workspace'. If you do not want the old items, you can
delete them manually. For information, see the following sections in Oracle Fusion
Middleware Using Oracle WebCenter Portal: "Deleting a Portal", "Deleting a Portal
Template", and "Deleting an Asset".
6.10.6.8 Granting Permissions to Manage Assets
In the portals upgraded from release 11.1.1.2.0 or 11.1.1.3.0, you must enable
authorized users to be able to manage portal assets. For this, grant the Create, Edit
and Delete Assets permission to the required roles. For information, see the
"Managing Roles and Permissions for a Portal" chapter in Oracle Fusion Middleware
Building Portals with Oracle WebCenter Portal.
6.10.7 Adding Oracle Single Sign-On Authentication Provider to the List of
Authentication Providers
In the upgraded Oracle WebCenter Portal environment, Oracle Single Sign-on (OSSO)
Identity Asserter does not appear in the list of authentication providers. If you
continue to use OSSO 10g even after upgrading to WebCenter Portal 11.1.1.9.0, you
must update the setDomainEnv script to add the authentication provider.
6-74 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
To add the OSSO authentication provider:
1.
Search for the following entry in the DOMAIN_HOME/bin/setDomainEnv.sh (on
UNIX operating systems) or DOMAIN_HOME\bin\setDomainEnv.cmd (on Windows
operating systems) file:
ALT_TYPES_DIR="${ORACLE_HOME}/modules/oracle.ossoiap_11.1.1,${ORACLE_HOME}/mod
ules/oracle.oamprovider_11.1.1
Replace the entry with:
ALT_TYPES_DIR="${COMMON_COMPONENTS_HOME}/modules/oracle.ossoiap_
11.1.1,${COMMON_COMPONENTS_HOME}/modules/oracle.oamprovider_11.1.1
2.
Restart the Administration Server.
6.10.8 Adding New Features to Oracle WebCenter Portal
This section includes the following subsections:
■
■
Section 6.10.8.1, "Installing Activity Graph, Analytics, Pagelet Producer,
Personalization Server, and Services Portlets"
Section 6.10.8.2, "Adding Portal Framework Features to WebCenter Custom
Applications"
6.10.8.1 Installing Activity Graph, Analytics, Pagelet Producer, Personalization
Server, and Services Portlets
Compared to Release 11.1.1.2.0 or 11.1.1.3.0, Oracle WebCenter Portal 11.1.1.9.0
includes several new features, including:
■
■
Activity Graph, which enables users to analyze various statistics collected by
Analytics. Various similarity scores for objects and users are collected, and used to
give recommendations.
Analytics, which enables users to view various user activity reports
If you want to extend your WebCenter domain to install
Oracle WebCenter Portal's Analytics Collector, you must remove the
openusage properties. For information, see Section 6.10.5.7, "Remove
openusage Properties in setDomainEnv."
Note:
■
■
■
Pagelet Producer, which provides a collection of useful tools and features that
facilitate dynamic pagelet development
Personalization Server, which enables you to deliver application content to
targeted users based on selected criteria.
Services Portlets, which enables you to expose Oracle WebCenter Portal services
and tools task flows in other applications as WSRP portlets or pagelets. You can
consume Services Portlets in the following applications: Oracle Portal, Oracle
WebLogic Portal, and Oracle WebCenter Interaction.
For more information about these features as well as other Oracle WebCenter Portal
components, see the "Getting Started with Oracle WebCenter Portal Components"
chapter in Oracle Fusion Middleware Installation Guide for Oracle WebCenter Portal.
To take advantage of these new features, you must extend your domain by installing
the required components. For information about extending a domain in a:
Patching Oracle WebCenter Portal 6-75
Post Patching Tasks for Oracle WebCenter Portal
■
■
Simple topology, see the "Extending an Existing Domain" section in Oracle Fusion
Middleware Installation Guide for Oracle WebCenter Portal.
Cluster or distributed environment, refer to:
–
Chapter "Extending the Domain for WebCenter Portal Components" in Oracle
Fusion Middleware Enterprise Deployment Guide for Oracle WebCenter Portal.
–
Chapter "Configuring High Availability for Oracle ADF and Oracle
WebCenter Portal" in Oracle Fusion Middleware High Availability Guide.
Before you extend your domain, you must do the following:
■
Decide on the products and topology for your environment.
To verify that your system meets the necessary minimum requirements, refer to
the following documents:
–
Oracle Fusion Middleware System Requirements and Specifications:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requireme
nts-100147.html
This document contains information related to hardware and software
requirements, minimum disk space and memory requirements, database
schema requirements, and required system libraries, packages, or patches.
–
Oracle Fusion Middleware Supported System Configurations:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certifica
tion-100350.html
This page contains various certification documents for current and previous
product releases. The System Requirements and Supported Platforms for Oracle
Fusion Middleware 11gR1 document contains certification information related
to supported 32-bit and 64-bit operating systems, databases, web servers,
LDAP servers, adapters, IPv6, JDKs, and third-party products.
–
Oracle Fusion Middleware Interoperability and Compatibility Guide
This document covers the compatibility and interoperability issues that may
arise when installing or upgrading Oracle Fusion Middleware 11g products.
■
Use Repository Creation Utility (RCU) to install any necessary schemas.
Analytics and Activity Graph require the ACTIVITES schema. Services Portlets
requires three additional schemas: MDS, WEBCENTER, and PORTLET. These schemas
must be mapped to the data sources mds-ServicesProducerDS,
WC-ServicesProducerDS, and Portlet-ServicesProducerDS, respectively. No
additional schemas are required for Pagelet Producer or Personalization Server.
For information about required schemas, see the "Oracle WebCenter Portal
Schemas" section, and for information about installing the schemas with RCU, see
the "Obtaining and Running Repository Creation Utility" chapter in Oracle Fusion
Middleware Repository Creation Utility User's Guide.
6.10.8.2 Adding Portal Framework Features to WebCenter Custom Applications
Oracle WebCenter Portal Framework supports various new features such as page
navigations and page hierarchies. If you want to use new features, the recommended
best practice for migration of a release 11.1.1.2.0 or 11.1.1.3.0 custom application that
contains portal components (like portlets) is to create a new release 11.1.1.9.0 Portal
Framework application using the WebCenter Portal Framework Application
template and then manually migrate the content, configurations, and logic from your
6-76 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
old application (release 11.1.1.2.0 or 11.1.1.3.0) to the new Portal Framework
application. For information about adding features to your Portal Framework
application, see Oracle Fusion Middleware Developing Portals with Oracle WebCenter Portal
and Oracle JDeveloper.
6.10.9 Running the upgradeWebCenterPermissions WLST Command
Run the upgradeWebCenterPermissions() WLST command to upgrade permissions for
WebCenter Portal. This command creates additional application roles, and grants some
additional permissions required for Oracle WebCenter Portal. It also determines and
restores the OWSM security policy to the Web service endpoints for WebCenter Portal
and Discussions.
To run the upgradeWebCenterPermissions() WLST command:
1.
Ensure the Administration Server and all the Oracle WebCenter Portal managed
servers are up and running.
2.
Invoke the WLST script from your WebCenter Portal Oracle home directory, and
connect to the Administration Server for Oracle WebCenter Portal. You must run
all WebCenter Portal WLST commands from your WebCenter Portal Oracle home
directory (WCP_ORACLE_HOME).
For information, see the "Running Oracle WebLogic Scripting Tool (WLST)
Commands" section in Oracle Fusion Middleware Administering Oracle WebCenter
Portal.
3.
Run the upgradeWebCenterPermissions() command. The following example
upgrades permissions for WebCenter Portal:
cd <WC_ORACLE_HOME>/common/bin
./wlst.sh
connect(<admin_username>, <admin_password>, <host>)
upgradeWebCenterPermissions()
When you run this command, various warnings or error messages like 'COMMAND
FAILED due to an unknown reason, Check the stack trace for details' are
displayed. You can ignore these as long as there is a message that the command
completed successfully.
4.
Restart the WC_Spaces and WC_Collaboration managed servers.
6.10.10 Resetting Search Customizations
In systems upgraded from earlier Oracle WebCenter Portal or Oracle SES instances,
previous search customizations set by task flow parameters are overridden.
When you upgrade your existing Oracle SES instance to release 11.2.2.2, all the
crawlers sources, crawler schedules, and source groups get migrated to the upgraded
instance. But because of different Authorization Manager on the old and upgraded
Oracle SES instances, search query will not render any results. After upgrading to
Oracle SES 11.2.2.2, you must perform the following tasks:
■
■
Re-create spaces crawler (delete the existing spaces crawler and create it again),
and assign it to your upgraded portals.
Configure a connection between WebCenter Portal and Oracle SES 11.2.2.2. Note
that the default port numbers on the old and the upgraded Oracle SES instances
are different.
Patching Oracle WebCenter Portal 6-77
Post Patching Tasks for Oracle WebCenter Portal
This task must also include running the setSESVersion WLST command to enable
the Tools and Services - Search administration page, and to gain access to the
capabilities of Oracle SES 11.2.2.2.
For information, see the "Managing Oracle Secure Enterprise Search in WebCenter
Portal" chapter in Oracle Fusion Middleware Administering Oracle WebCenter Portal.
6.10.11 Updating Resource Protection Level in OAM 11.1.2.2.0
If OAM is patched to release 11.1.2.2.0, update OAM policies.
To update OAM policies:
1.
Log on to OAM Console using the following URL format:
http://host:port/oamconsole
2.
Click Application Domains.
3.
Locate the application domain for Oracle WebCenter Portal.
4.
Open the Resources tab for the domain, and click the New Resource button.
5.
Add /webcenter/SpacesWebService* as a resource:
a.
In Resource Type, select HTTP.
b.
In the Host Identifier field, select the host created while registering OAM.
c.
In the Resource URL field, enter the following:
/webcenter/SpacesWebService*
6.
d.
In the Description field, enter a description for the resource.
e.
Set Protection Level to Excluded.
f.
Click Apply.
Repeat step 5 to add /webcenter/SpacesWebService/** as a resource.
6.10.12 Restoring Profile Page Customizations
When you upgrade from an older version of WebCenter Portal to 11.1.1.9.0, run the
setProfileConfig WLST command to restore Profile page customizations.
To run the setProfileConfig WLST command:
1.
Ensure the Administration Server and all the Oracle WebCenter Portal managed
servers are up and running.
2.
Invoke the WLST script from your WebCenter Portal Oracle home directory, and
connect to the Administration Server for Oracle WebCenter Portal. You must run
all WebCenter Portal WLST commands from your WebCenter Portal Oracle home
directory (WCP_ORACLE_HOME).
For information, see the "Running Oracle WebLogic Scripting Tool (WLST)
Commands" section in Oracle Fusion Middleware Administering Oracle WebCenter
Portal.
3.
Run the setProfileConfig command. The following example restores WebCenter
Portal’s Profile page customizations for profile page version v1.
cd <WC_ORACLE_HOME>/common/bin
./wlst.sh
connect(<admin_username>, <admin_password>, <host>)
setProfileConfig(appName='webcenter',ProfilePageVersion='v1')
6-78 Oracle Fusion Middleware Patching Guide
Post Patching Tasks for Oracle WebCenter Portal
4.
Restart the WC_Spaces managed server.
6.10.13 Removing the -noverify Flag
In your patched Oracle WebCenter Portal instance, the -noverify flag may be set to
disable bytecode verification. You must remove this flag if it is enabled.
To remove the -noverify flag:
1.
Open the setDomainEnv.sh or setDomainEnv.cmd file:
On UNIX: domain_home/bin/setDomainEnv.sh
On Windows: domain_home\bin\setDomainEnv.cmd
2.
Look under EXTRA_JAVA_PROPERTIES and remove the -noverify flag if it is
present.
3.
Save the file.
Patching Oracle WebCenter Portal 6-79
Post Patching Tasks for Oracle WebCenter Portal
6-80 Oracle Fusion Middleware Patching Guide
A
Installer Screens
A
This appendix contains sample screenshots and descriptions for the Installer screens
used to apply the patch. The screen functionality will be the same for most installers.
[7]
This appendix includes the following topics:
■
Welcome
■
Install Software Updates
■
Prerequisite Checks
■
Specify Installation Location
■
Application Server
■
Installation Summary
■
Installation Progress
■
Installation Complete
A.1 Welcome
Installer Screens A-1
Install Software Updates
This page introduces you to the Oracle Fusion Middleware installer and provides two
important pieces of information:
■
■
A navigation pane on the left that summarizes the tasks the installer will help you
complete. Each item in the navigation pane represents a specific installer screen
that will prompt you for information required to install the software.
Information about any prerequisites you might need to perform before continuing
with the installation.
Review the information on this screen carefully to be sure you have performed all the
necessary prerequisites.
If you are not sure about any of the prerequisite tasks, refer to the Oracle Fusion
Middleware Installation Planning Guide, as well as the installation guide for the specific
Oracle Fusion Middleware software you are about to install.
A.2 Install Software Updates
Use this screen to quickly and easily search for the latest software updates, including
important security updates, via your My Oracle Support account.
The following table describes the fields on this screen.
Element
Description
Skip Software Updates
Select this option to skip this screen. The installer will not
check for updates that might be applicable to the current
product installation.
A-2 Oracle Fusion Middleware Patching Guide
Prerequisite Checks
Element
Description
Search My Oracle Support for
Updates
If you have a My Oracle Support account, then select this
option to have the installer automatically search My Oracle
Support for software updates that apply to the software
products are about to install.
Enter your My Oracle Support account name and
password, and then click Search for Updates.
The installer automatically downloads applicable software
updates from My Oracle Support.
Before you search for update, you can test your login
credentials and the connection to My Oracle Support by
clicking Test Connection. Click Proxy Settings to configure
a proxy server if one is required.
Search Local Directory for
Updates
Select this option if you already downloaded the latest
software updates and you want the installer to search a
local directory for updates applicable to the products you
are about to install.
When you select this option, the installer displays an
additional field and Browse button that you can use to
identify the local directory where your updates are located.
A.3 Prerequisite Checks
This screen analyzes the host computer to ensure that specific operating system
prerequisites have been met.
If any of the prerequisite checks fail, then a short error message appears in the bottom
portion of the screen. Fix the error and click Retry to try again. If you want to ignore
the error or warning messages and continue with the installation, click Continue.
Click Abort to stop prerequisite checking for all components.
Installer Screens A-3
Specify Installation Location
A.4 Specify Installation Location
Use this screen to identify where you want to install your Oracle Fusion Middleware
software.
The following table describes the fields that appear on this page.
Field
Description
Oracle Middleware Home
Use this field to specify the location of your Oracle
Middleware home directory:
■
If you are using Oracle WebLogic Server as your
application server:
In the Oracle Middleware Home field, specify the
absolute path to your existing Oracle Middleware home
directory; this is the directory that was created when
you installed Oracle WebLogic Server. If you do not
know the full path to your Middleware home, you can
click Browse to select an existing directory in your
system.
■
If you are using IBM WebSphere as your application
server:
In the Oracle Middleware Home field, specify the
absolute path to the directory you want to use as the
Middleware home. This directory has no relation to the
location of your WebSphere installation. If you specify a
directory location that does not already exist, the
installer will create the directory for you.
A-4 Oracle Fusion Middleware Patching Guide
Application Server
Field
Description
Oracle Home Directory
Use this field to specify the directory inside the Middleware
home where you want to install your products.
If you specify a directory that already exists, it must be
either:
■
■
An empty directory inside the Middleware home (for
example, you have created an empty directory inside
the Middleware home in advance of this installation
and should specify this directory here).
An existing Oracle home directory (for example, you
are reinstalling Oracle SOA Suite to an existing Oracle
home because of an incomplete previous installation).
If you specify a new directory, it will be created inside the
Middleware home.
For the remainder of this document, the directory specified in
the Oracle Home Directory field will be referred to as your SOA
Oracle home to avoid any confusion with the Oracle home directories
of other Oracle Fusion Middleware products.
Note:
For more information about the Oracle home and Middleware home
directories, refer to "Oracle Fusion Middleware Installation Directory
Structure" in Oracle Fusion Middleware Installation Planning Guide.
If you are performing an installation on a Windows operating system, be sure that
your directory paths are valid and do not contain double backslashes (\\).
A.5 Application Server
Installer Screens A-5
Installation Summary
Use this screen to select the application server you want to use for this installation.
■
■
■
If the installer detects a Middleware home with Oracle WebLogic Server installed,
then this is the application server that will be used. All other fields in this screen
will be inactive.
If the installer detects a Middleware home without an Oracle WebLogic Server
installed, you must select one of the application server options and then provide
its location in the Application Server Location field.
If the installer does not detect a Middleware home directory, the "WebLogic
Server" option will be inactive. You must select "WebSphere" and then provide the
location of your IBM WebSphere in the Application Server Location field.
A.6 Installation Summary
This screen summarizes the selections you have made during this installation session.
It includes the following information:
■
The location of your installation
■
How much disk space will be used for the installation
■
The applications you have selected for installation
Review information on this screen carefully, and take one of the following actions:
■
■
If you want to make any changes to the configuration before starting the
installation, use the navigation pane to select the Installer screen you want to
return to and edit.
If you are satisfied with the information, click Install to begin the installation
procedure.
A-6 Oracle Fusion Middleware Patching Guide
Installation Progress
■
If you want to save this configuration to a text file (called a response file), click
Save. The resulting response file can be used later if you choose to perform the
same installation from the command line.
A.7 Installation Progress
This screen shows you the progress of the installation.
If you want to quit before the installation is completed, click Cancel. Doing so will
result in a partial installation; the portion of the software that was installed on your
system before you click Cancel will remain on your system, and you will have to
remove it manually.
Installer Screens A-7
Installation Complete
A.8 Installation Complete
This screen summarizes the installation that was just completed.
If you want to save this summary information to a text file for future reference, click
Save.
Click Finish to dismiss the screen.
A-8 Oracle Fusion Middleware Patching Guide
B
Patch Set Assistant Screens
B
This appendix contains screenshots and descriptions for the Patch Set Assistant
screens.
[8]
This appendix includes the following topics:
■
Welcome
■
Select Component
■
Prerequisites
■
Content Server Directory (WebCenter Content Only)
■
Schema Database Credentials
■
Records Directory (WebCenter Content Only)
■
Examine
■
Upgrade Summary
■
Upgrade Progress
■
Upgrade Success
B.1 Welcome
Patch Set Assistant Screens B-1
Welcome
The Welcome screen is displayed each time you start the installer.
You can click View Log at any time during the schema upgrade process to view the
log file. A separate window (Log File Viewer) is displayed that contains the messages
being written to the log file. The top of the Log File Viewer contains the location and
name of the log file. You can click Refresh to see the most recent messages being
logged.
B-2 Oracle Fusion Middleware Patching Guide
Select Component
B.2 Select Component
Use this screen to select the component schema you want to upgrade.
The Patch Set Installer lists all components that are found in the Middleware home.
For example, if you started the Patch Set Installer from the MW_HOME/oracle_
common/bin/psa directory (on UNIX operating systems) or
c:\Products\Oracle\Middleware\Oracle_SOA1\bin directory (on Windows
operating systems), the Patch Set Installer will list all components found in
/home/Oracle/Middleware directory (on UNIX operating systems) or
c:\Products\Oracle\Middleware directory (on Windows operating systems).
You can only use Patch Set Assistant to upgrade one top-level component at a time. In
the figure above, notice that Oracle SOA is selected, which means Patch Set Assistant
would upgrade the SOAINFRA schema as well as the MDS schema, upon which the
SOAINFRA schema is dependent. However, the top-level "Oracle Metadata Services" box
is not selected even though that schema is going to be upgraded.
If you wanted to upgrade either of the other two top-level schema found in this
Middleware home (in this case, "Oracle Audit Services" or "Oracle Platform Security
Services") you would have to restart the Patch Set Assistant and select those
components separately.
If you are upgrading from Release 11.1.1.2.0 or 11.1.1.3.0, the
prefix_ACTIVITIES schema will not be available in your environment
as this schema was not introduced until Release 11.1.1.4.0. Make sure
you de-select this schema from the WebCenter Portal component;
otherwise the Patch Set Assistant will ask for credentials for this
schema.
Note:
Patch Set Assistant Screens B-3
Prerequisites
B.3 Prerequisites
Use this screen to verify that you have satisfied the database prerequisites before you
continue. You must check all the boxes acknowledging that all prerequisites for
upgrade have been met, or else you will be unable to continue to the next screen. For
webcenter content, after the prerequisites screen, a new screen called Content server
directory is also present. Specify the domain directory path , where the content server
is installed.
Select Database backup completed to verify that you have backed up your database
as described in Section 4.4.3, "Back Up Your Database and Database Schemas".
Select Database version is certified by Oracle for Fusion Middleware upgrade to
verify that you have read the System Requirements and Supported Platforms for Oracle
Fusion Middleware 11gR1 document on the Oracle Fusion Middleware Supported
System Configurations page, and that your database is certified for use with Oracle
Fusion Middleware.
B-4 Oracle Fusion Middleware Patching Guide
Content Server Directory (WebCenter Content Only)
B.4 Content Server Directory (WebCenter Content Only)
Patch Set Assistant Screens B-5
Schema Database Credentials
B.5 Schema Database Credentials
Use this screen to specify database connection credentials and schema information for
upgrade. This screen appears once for each component schema that needs to be
upgraded; each time after the first time the screen will have all the database credential
values filled in for you. If you have schemas on different databases then you will need
to alter your database connection information accordingly.
The following table describes the fields on this screen:
B-6 Oracle Fusion Middleware Patching Guide
Schema Database Credentials
Field
Description
Database Type
Select your database type from the drop-down list. Only database
types that are valid for the schema are available in this list. The
following database types are supported:
■
Oracle Database
■
Oracle Database enabled for editions-based redefinition
■
Microsoft SQL Server
■
IBM DB2
■
MySQL
In addition, Oracle Data Integrator also supports the following
databases:
■
Sybase Adaptive Server Enterprise
■
PostgreSQL
■
Hypersonic SQL
NOTE: The database type Oracle Database enabled for
editions-based redefinition should only be selected when editions
created in the EBR database require an upgrade. If this is not the
intent, select Oracle Database.
Connect String
Specify the connection credentials to your database.
■
For Oracle databases:
host:port/service_name
■
For Microsoft SQL Server and IBM DB2 databases:
//host:port;DatabaseName=dbname
■
For MySQL databases:
//host:port/database
DBA User Name
Specify the user name and role of the database administrator user.
■
■
■
DBA Password
For Oracle databases, enter SYS or any user with DBA role (for
example, sys as sysdba or any user with DBA privileges).
For Microsoft SQL Server databases, enter sa or any user with
db_owner role.
For IBM DB2 databases, enter db2admin or any user with DBA
role.
■
For Hypersonic databases, enter sa.
■
For Sybase databases, enter sa.
■
For MySQL databases, enter root.
Enter the password for your database administrator user.
After these values are filled in, click Connect to connect to your database. After the
connection succeeds, two additional fields will become active on the screen:
Patch Set Assistant Screens B-7
Records Directory (WebCenter Content Only)
Field
Description
Schema User Name
This drop-down list contains all available product schemas in the
database to which you are connected. Select the schema you want to
upgrade from the drop-down list.
NOTE: For the Oracle WebCenter Content Server - Complete
(prefix_OCS), there is a drop-down list that populates the names of
the schema.
NOTE: If the drop-down list is empty, make sure you have connected
to the database as a user with the required privileges.
Schema Password
Specify the password for the selected schema.
B.6 Records Directory (WebCenter Content Only)
In this screen, specify the complete path to your domain directory.
B-8 Oracle Fusion Middleware Patching Guide
Examine
B.7 Examine
This page displays the status of each component schema for upgrade. The meaning of
the status indicators for the components is listed in the following table.
Status
Description
in progress
The Patch Set Assistant is examining whether or not the schema can be
upgraded.
pending
The schema will be examined when the Patch Set Assistant is finished
examining the preceding component.
already upgraded
The schema was previously successfully upgraded with the Patch Set
Assistant or was created with the latest version of the Repository
Creation Utility (RCU). No action will be taken on this schema.
failed
The schema can not be upgraded.
skipped
The examination of this schema was skipped. This is caused when the
examination of a dependent schema fails.
succeeded
The examination of the schema was successful and the schema is ready
to be upgraded.
Patch Set Assistant Screens B-9
Upgrade Summary
B.8 Upgrade Summary
Use this page to review a summary of the options you have selected and to start the
upgrade process.
Click Save Response File to save this upgrade information to a response file. This file
can be used later of you want to run the Patch Set Assistant from the command line.
For more information, see Section 4.5.2, "Using the Patch Set Installer from the
Command Line"
B-10 Oracle Fusion Middleware Patching Guide
Upgrade Progress
B.9 Upgrade Progress
This screen shows you the progress of your schema upgrade. The "Upgrade Progress"
bar moves from 0% at the beginning to 100% when the upgrade is complete.
Patch Set Assistant Screens B-11
Upgrade Success
B.10 Upgrade Success
This screen indicates that the upgrade was successful.
Be sure to view the log file located in the MW_HOME/oracle_common/upgrade/logs (on
UNIX operating systems) or MW_HOME\oracle_common\upgrade\logs (on Windows
operating systems) directory for details about the upgrade. (The exact directory path
will be shown on your screen.) You can view the log file with any text editor, or you
can click the View Log button.
B-12 Oracle Fusion Middleware Patching Guide
C
Using Patch Assistant to Migrate from 11g
Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C
[9This
]
appendix describes how to migrate from Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) to Release 1 (11.1.1.2.0) by using Patch Assistant.
This appendix includes the following topics:
■
Overview of Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) Patch Assistant
■
Migration Process
■
Preparing to Migrate
■
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Important Notes: The information and procedures in this chapter
apply only to users who have installed and configured Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0). If you are currently running
Release 1 (11.1.1.1.0), then you must use this chapter to upgrade your
Oracle Fusion Middleware environment to Release 1 (11.1.1.2.0) before
you can patch your environment.
If you are already running Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) or a later patch set, then disregard this appendix.
The procedures in this chapter are for installing and configuring and
migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). As a
result, for all cross-references in this section, refer to the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
C.1 Overview of Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Patch Assistant
Patch Assistant enables you to migrate your existing configuration of Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0) components, used in conjunction with the
11.1.1.1.0 and 11.1.1.2.0 installations. Patch Assistant is not a complete software
distribution. You must run this Patch Assistant over an existing Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0) installation. Patch Assistant is designed to work
with all Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) products. You may see
messages that an Oracle product is not present in a domain or instance. This message
is informational and does not indicate an error.
Refer to Table C–7 for the Oracle Fusion Middleware components supported by Patch
Assistant.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C-1
Migration Process
Patch Assistant is used only for upgrading Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0) Domains and Oracle Instances. If
you are not upgrading your existing 11.1.1.1.0 domains and instances,
you are not required to use Patch Assistant.
Note:
Patch Assistant helps to migrate the following from Oracle Fusion Middleware 11g
Release 1 (11.1.1.1.0):
■
Oracle Fusion Middleware Domains
It is required that you migrate the entire Oracle WebLogic
domain. When the domain is migrated, all components in the domain
are also migrated.
Note:
■
■
Oracle Instances
Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) database schema created using
Oracle Repository Creation Utility (RCU)
Note:
You must migrate both the schema and the middle tier.
When you run Patch Assistant tool, the configuration files contained in the Oracle
Fusion Middleware 11g Release 1 (11.1.1.1.0) domain and Instance directories are
copied to the new directories in the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) installation. The Middleware home is the full path of the Oracle directory
that contains the Oracle Fusion Middleware installation, and MW_HOME will be used in
this documentation to refer to the directory where the product is installed.
MW_HOME must be replaced with the full path name of the
installed Oracle Fusion Middleware instance.
Note:
C.2 Migration Process
Figure C–1 illustrates the migration process. Review this chart to get familiar with the
steps you are required to take, based on your existing Oracle Fusion Middleware
environment.
C-2 Oracle Fusion Middleware Patching Guide
Preparing to Migrate
Figure C–1 Flow Chart of the Migration Process
C.3 Preparing to Migrate
This section contains important information you should read before you migrate.
C.3.1 Evaluating and Reviewing your Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) Environment
The first step in the migrating process is to evaluate your current Oracle Fusion
Middleware 11g Release 1 (11.1.1.1.0) environment. During the migration process, the
topology of the deployment must not change, the port configuration must be retained,
and there must be minimal changes in namespaces. All the changes in the namespaces
are encapsulated by the properties in the patchMaster.properties file, which is
included in the fmw11gR1ps1_patchassist.zip file.
For a list of products included in this patch set, see Section C.4.7, "Oracle Fusion
Middleware Components Supported by Patch Assistant".
C.3.2 Preparing to Migrate Your Configuration
This section discusses the following topics:
■
Prerequisites
■
Extracting the Contents of Patch Assistant
■
Setting Up the Patch Assistant Environment
■
Stopping Oracle Fusion Middleware
■
Setting Logging Properties
C.3.2.1 Prerequisites
This section describes the general and product-specific prerequisites for running Patch
Assistant.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C-3
Preparing to Migrate
This section discuss the following topics:
■
General Prerequisites
■
Product-Specific Prerequisites
C.3.2.1.1 General Prerequisites The following are the general prerequisites for running
Patch Assistant:
■
■
■
■
Ensure that Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) is installed and
configured.
Ensure that you install 11.1.1.2.0 on the same operating system used by the
11.1.1.1.0 installation.
Ensure that the system configuration meets the recommended system
configuration described in your product documentation. For more information,
see
http://www.oracle.com/technology/software/products/ias/files/fusion_
certification.html.
Ensure that you have Apache Ant 1.7.0 and Java JDKs (Java SE 6 1.6.0_11 and
jrockit_160_05_R27.6.2-20), which are packaged with Oracle WebLogic Server.
If you are using Oracle Internet Directory, Oracle Virtual
Directory, Oracle HTTP Server, or Oracle Web Cache as standalone
Oracle Fusion Middleware installations, you must install and
configure Apache Ant separately. For more information, see Installing
Ant at http://ant.apache.org/manual/installlist.html and
Section C.3.2.3, "Setting Up the Patch Assistant Environment".
Note:
■
■
■
■
■
■
Make a detailed note of the topology used for the Oracle Fusion Middleware 11g
Release 1 (11.1.1.1.0) installation.
Ensure that you do not change the port configuration and instance names in your
existing Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0) installation.
Ensure that the environment variables for tmp and temp directories for Microsoft
Windows are set, as described in the Oracle Fusion Middleware Administrator's
Guide.
Back up your Oracle software, inventory, schema, and domain before applying
this patch set, or before making any other changes to your existing Oracle
software. Refer to your product administrator's guide for instructions on backing
up your Oracle software and inventory. For more information, see the "Advanced
Administration: Backup and Recovery" part in the Oracle Fusion Middleware
Administrator's Guide.
On Windows, it is recommended that you edit the patchMaster.properties file in
a Notepad. If you are using any other text editor, such as Windows WordPad, then
save the file as Text Document. Do not save the file in Rich Text Format.
On Windows, you must delete the service name for Oracle Fusion Middleware 11g
Release 1 (11.1.1.1.0) before installing Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) because both the installations use the same service name. To do so, run
the following Ant task on the command line:
ant master-opmn-delete-service
Enter the required information when prompted by the Ant task.
C-4 Oracle Fusion Middleware Patching Guide
Preparing to Migrate
If you want to abort the migration and revert to the 11.1.1.1.0
deployment, run the following Ant task on the command line:
Note:
ant master-opmn-create-service
■
Heterogeneous nodes in a Cluster (one in 11.1.1.2.0, other in 11.1.1.2.0) is not
supported during the migration process. You must migrate all nodes to 11.1.1.2.0
before environment can be used.
C.3.2.1.2 Product-Specific Prerequisites Depending on your Oracle Fusion Middleware
component, you may have to meet additional prerequisites as follows:
■
Oracle Fusion Middleware Audit Framework
■
Oracle Directory Integration Platform
■
Oracle Internet Directory and Oracle Virtual Directory
■
Oracle WebCenter
■
Oracle Portal
Oracle Fusion Middleware Audit Framework
For Oracle Fusion Middleware Audit Framework, the audit policy is configured for
Java components in Oracle Fusion Middleware 11g Release 1 (11.1.1.1.0), you must
export the configuration before running Patch Assistant, as follows:
1.
Log in to Oracle Enterprise Manager 11g Fusion Middleware Control.
2.
Expand WebLogic Domain on the left pane, and select your domain.
Your selected domain page is displayed.
3.
From the WebLogic Domain, select Security, and then Audit Policy.
The Audit Policy page is displayed.
4.
Select the Audit Policy, and click Export.
5.
Save the AuditConfiguration file to your machine.
Oracle Directory Integration Platform
For the Oracle Directory Integration Platform, do the following:
1.
Ensure that your Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) Oracle
Internet Directory is up and running in SSL No-Auth mode.
2.
Extend the Oracle WebLogic domain created during the Oracle Internet Directory
11g Release 1 (11.1.1.2.0) installation, by running the following command:
Windows
config.cmd (Located at: ORACLE_HOME\bin)
UNIX
config.sh (Located at: ORACLE_HOME/bin)
The Oracle Fusion Middleware Configuration Wizard appears. Enter the Oracle
Internet Directory 11g Release 1 (11.1.1.2.0) connection details and credentials.
3.
Stop the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) domain.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C-5
Preparing to Migrate
Oracle Internet Directory and Oracle Virtual Directory
Depending on your installation, complete the following prerequisites:
■
If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual
Directory created with a new Oracle WebLogic domain, then choose the Create a
new WebLogic domain option on the Welcome screen of the Oracle Fusion
Middleware Configuration Wizard when configuring the 11.1.1.2.0 domain.
During the configuration of 11.1.1.2.0, if you select the Create a new WebLogic
domain option, then you must deselect Oracle Internet Directory and Oracle
Virtual Directory, and select Oracle Directory Services Manager.
■
■
If your Oracle Internet Directory and Oracle Virtual Directory are not registered to
any Oracle WebLogic domain in your 11.1.1.1.0 configuration, then 11.1.1.2.0
configuration is not required. You must set the property
patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a
new directory for the instance. Ensure that you retain the same instance name
used in 11.1.1.1.0.
If your 11.1.1.1.0 configuration has Oracle Internet Directory and Oracle Virtual
Directory registered to an existing Oracle WebLogic domain, then 11.1.1.2.0
configuration is not required. You must set the property
patchMaster.Oracleinstancenewlist in the patchMaster.properties file to a
new directory and register the instance with the existing 11.1.1.2.0 WebLogic
domain using Ant target. Ensure that you retain the same instance name used in
11.1.1.1.0.
Oracle WebCenter
To migrate Oracle WebCenter, you may choose either of these approaches:
■
Keep two parallel instances of Oracle WebCenter, that is 11.1.1.1.0 as well as
11.1.1.2.0. To do this, you must perform a complete installation of Oracle
WebCenter 11.1.1.2.0. You can then migrate your Oracle WebCenter 11.1.1.1.0 data
into the new WebCenter instance by using the export and import utilities. This
approach enables you to use both instances of Oracle WebCenter, if required. For
example, you may run the two instances in parallel to minimize downtime or to
ensure that the 11.1.1.2.0 instance is set up to the same level as the 11.1.1.1.0
instance before you switch over to the 11.1.1.2.0 instance completely.
For more information, refer to the following resources in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library on the Oracle
Technology Network (OTN):
■
–
Refer to the Oracle Fusion Middleware Installation Guide for Oracle WebCenter
Portal for information about how to install Oracle WebCenter 11g Release 1
(11.1.1.2.0).
–
Refer to the "Managing Export, Import, Backup, and Recovery of WebCenter"
in the Oracle Fusion Middleware Administering Oracle WebCenter Portal for
information about export and import utilities for Oracle Fusion Middleware
11g Release 1 (11.1.1.2.0).
Migrate the Oracle WebCenter 11.1.1.1.0 repository and mid-tier completely to
Oracle WebCenter 11.1.1.2.0. This approach preserves your Oracle WebCenter
11.1.1.1.0 repository data and enables you to reuse the repository.
This guide describes the tasks required to implement this migration approach for
Oracle WebCenter.
C-6 Oracle Fusion Middleware Patching Guide
Preparing to Migrate
Oracle Portal
Before upgrading, you should backup your OmniPortlet and WebClipping
customizations.
C.3.2.2 Extracting the Contents of Patch Assistant
You can download the fmw11gR1ps1_patchassist.zip, which is included in the Oracle
Fusion Middleware 11g Release 1 Patch Set 1 Patch Scripts media. The zip file is
available in the same media pack as Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) on Oracle Technology Network (OTN) at the following URL:
http://oracle.com/technology
After downloading this zip file, extract its contents to its own location, in your local
machine, where the old and new Oracle Fusion Middleware components are installed.
Ensure that the same operating system is used for the 11.1.1.1.0 and 11.1.1.2.0
installations. The zip file includes the following files:
■
README – Describes the environment.
■
patchMaster.properties - The user input file.
■
build.xml – The master build file. Each Oracle Fusion Middleware component has
its own build.xml file.
C.3.2.3 Setting Up the Patch Assistant Environment
To set up the Patch Assistant environment for Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0), you must set up ANT_HOME, add it to your PATH, set the JAVA_HOME and the
permgen size.
For example, on Windows:
set
set
set
set
ANT_HOME=MW_HOME\modules\org.apache.ant_1.7.0
PATH=%PATH%;%ANT_HOME%\bin
JAVA_HOME=MW_HOME\jdk160_14_R27.6.4-18
ANT_OPTS=-Xmx512M -XX:MaxPermSize=512m
For example, on UNIX:
setenv
setenv
setenv
setenv
setenv
MW_HOME ##set mw home here##
ANT_HOME $MW_HOME/modules/org.apache.ant_1.7.0
PATH $ANT_HOME/bin:$PATH
JAVA_HOME $MW_HOME/jdk160_14_R27.6.5-32
ANT_OPTS "-Xmx512M -XX:MaxPermSize=512m"
C.3.2.4 Stopping Oracle Fusion Middleware
Before you run Patch Assistant, you must stop the following:
■
Oracle WebLogic Server
■
Administration Servers
■
Managed Servers
■
Oracle Management Agent
■
Java EE Applications
■
High Availability Environments
For more information, see the Starting and Stopping Oracle Fusion Middleware
chapter in the Oracle Fusion Middleware Administrator's Guide.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C-7
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.3.2.5 Setting Logging Properties
You can use the log file to verify the migration or to detect any errors after running
Patch Assistant. Patch Assistant creates a time stamp file in the Patch Assistant home.
You can specify the following logging levels:
■
info (This is the default setting)
■
error
■
warning
■
verbose
■
debug
The debug and the verbose options may display sensitive
information in the logs, and they are not recommended for typical use.
Note:
Before you use your log file, you must set the logging properties as follows:
Open the patchMaster.properties file in a text editor, and upgrade the following
properties:
# Description: Specifies the directory where the log files go
patchMaster.Logdir=${patchMaster.Dir}
Specifies the default location where the log file is saved.
# Description: Specifies the logging level to be recorded in the log file
patchMaster.Loglevel=info
Sets the logging level.
To override the default patchMaster.properties Log level, run the command as
shown in the following example:
ant -DpatchMaster.Loglevel=error
You can override the patchMaster.properties by setting
properties on the command line. If the debug or verbose options are
used on the command line, they override the logging level property
set in the patchMaster.properties file. For more information, see
Section C.4.6.1, "Overriding Properties Set in the
patchMaster.properties File".
Note:
C.4 Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
This sections contains migration instructions. The following topics are covered:
■
Migration Roadmap
■
Migration Procedure
■
Post-Migration Configuration for Oracle Fusion Middleware Components
■
Installation Process
■
Configuration Process
■
Properties in the patchMaster.properties File
C-8 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
■
Oracle Fusion Middleware Components Supported by Patch Assistant
C.4.1 Migration Roadmap
Table C–1 describes the high-level tasks for migrating from Oracle Fusion Middleware
11.1.1.1.0 to 11.1.1.2.0. The table also provides information on where to get more details
on each task.
Table C–1
Tasks in the Migration Procedure
Mandatory or
Optional?
Task
Description
Documentation
Task 1 - Prepare
Environment with
General
Prerequisites, such
as Backing Up
Existing
Configuration and
Retaining Ports
and Instance
Names
Complete all general prerequisites
for running Patch Assistant.
For more information, see
Section C.3.2.1.1, "General
Prerequisites".
Mandatory
For more information, see
Section C.3.2.1.2, "Product-Specific
Prerequisites".
Optional
Complete all product-specific
Task 2- Prepare
Environment with prerequisites for running Patch
Product-Specific
Assistant, as applicable.
Prerequisites, if any
Task 3 - Stop All
Oracle Fusion
Middleware
11.1.1.1.0 Domains
and Instances
Ensure that you stop all Oracle
Fusion Middleware 11.1.1.1.0
domains and instances.
Mandatory
For more information, see
Section C.3.2.4, "Stopping Oracle Fusion
Middleware" and Section C.4.2.1,
"Stopping the Old Domain".
Task 4 - Install
Software (Oracle
WebLogic Server,
Repository
Creation Utility,
and Oracle
Products) for
11.1.1.2.0
Install Oracle software, including
Oracle WebLogic Server,
Repository Creation Utility, and
Oracle products for 11.1.1.2.0. Do
not create or configure a WebLogic
domain at this stage of the
migration process.
For instructions about installing the
Oracle WebLogic Server version
required for Oracle Fusion Middleware
11g Release 1 (11.1.1.2.0), refer to the
Installing and Configuring Oracle
WebLogic Server and Coherence in the
Oracle Fusion Middleware 11g Release
1 (11.1.1.2.0) documentation library on
OTN.
Install the Oracle Fusion
Middleware 11g Release 1
(11.1.1.2.0) and its components in a
separate Middleware home on the
same host as the Oracle Fusion
Middleware 11g Release 1 (11.1.1)
MW_HOME. Ensure that you stop the
Oracle Fusion Middleware
components for 11.1.1.1.0, before
you begin the installation. This
will enable the 11.1.1.2.0
installation to retain the same
11.1.1.1.0 port number, host name,
and machine name.
Task 5 - Download Download the Patch Assistant zip
the Patch Assistant file and extract its contents.
Zip File
After unzipping, configure Patch
Assistant before editing the
properties.
Mandatory
For system requirements information,
go to:
http://download.oracle.com/docs/ht
ml/E18558_01/fusion_
requirements.htm
For certification information, go to:
http://www.oracle.com/technetwork/
middleware/ias/downloads/fusion-ce
rtification-100350.html
For information about installing Oracle
products, refer to the product-specific
installation guides.
For more information, see
Section C.4.2.3, "Downloading Patch
Assistant".
Mandatory
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0)
C-9
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–1 (Cont.) Tasks in the Migration Procedure
Description
Task 6 - Set Up the
patchMaster.prop
erties File and
Run Patch
Assistant for
Schema Only
For more information, see
Mandatory
Ensure that the Oracle database
that contains the 11.1.1.1.0 schemas Section C.4.2.4, "Migrating the Schema".
is up and running. This will allow
access to the SCHEMA_VERSION_
REPOSITORY table by Patch
Assistant.
Specify the schema-related
properties in the
patchMaster.properties file, and
run the ant master-patch-schema
command to migrate the schema
only.
Note: For Oracle Portal, you must
complete the steps in Task 7, 8, and
9, and then follow the steps to
migrate the schema. It is
recommended that you refer to the
following topics in the Oracle
Fusion Middleware Upgrade Guide
for Oracle Portal, Forms, Reports, and
Discoverer before you run Patch
Assistant to migrate the schema:
■
■
■
■
■
Understanding the Impact of
the Oracle Portal Schema
Upgrade
Checking for Invalid Objects
in the Database Where the
Oracle Portal 10g Schema
Resides
Backing Up the Database
Where the Oracle Portal 10g
Schema Resides
Verifying the Required
Database Parameters for
Oracle Portal 11g
Verifying That the Database
and Oracle Internet Directory
Are Running
Log files specific to Oracle Portal
migration are generated in the
upgrade.log and precheck.log
files in the ORACLE_
HOME/upgrade/logs directory
(UNIX).
If your Oracle Portal repository is
not stored in the Oracle Metadata
Repository, and is instead installed
in a separate database, then do not
use the procedures in this section.
Instead, refer to "Upgrading an
Oracle Portal Repository in a
Customer Database" in Oracle
Fusion Middleware Upgrade Guide
for Oracle Portal, Forms, Reports, and
Discoverer.
C-10 Oracle Fusion Middleware Patching Guide
Documentation
Mandatory or
Optional?
Task
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–1 (Cont.) Tasks in the Migration Procedure
Mandatory or
Optional?
Task
Description
Documentation
Task 7 - Use the
Oracle Fusion
Middleware
Configuration
Wizard
(config.sh) to
Create and
Configure a
WebLogic Domain
for 11.1.1.2.0
Create and configure a WebLogic
administration domain for your
11.1.1.2.0 installation. Ensure that
you configure the domain as it was
in your 11.1.1.1.0 installation.
For more information, see
Section C.4.2.5, "Creating a WebLogic
Domain for 11.1.1.2.0" and the
product-specific installation guides.
Task 8 - Set Up the
patchMaster.prop
erties File and
Run Patch
Assistant for
Domain
Specify the domain-related
For more information, see
Mandatory
properties in the
Section C.4.2.6, "Migrating the Domain".
patchMaster.properties file, and
run the ant master-patch-domain
command to migrate the
WebLogic domain.
Mandatory
You must patch all products in the
domain being migrated.
Task 9 - Set Up the
patchMaster.prop
erties File and
Run Patch
Assistant for
Oracle Instance
Specify the instance-related
For more information, see
Optional
properties in the
Section C.4.2.7, "Migrating an Instance".
patchMaster.properties file, and
run the ant
master-patch-oinstance
command to migrate the instances.
Task 10 - Run Patch
Assistant for
Registering
Instance
After migrating the instances, run For more information, see
Section C.4.2.8, "Registering the
the ant
master-register-oinstance
Instance".
command to register the instances.
Mandatory
Task 11 - Start
11.1.1.2.0 Domains
and Instances
For more information, see
Run the ant
Section C.4.2.9, "Starting or Stopping
master-start-domain-new
the 11.1.1.2.0 Domain".
command to start the new
11.1.1.2.0 domain. In addition, start
the new instances.
Mandatory
Task 12 - Prepare
Environment with
Product-Specific
Post-Migration
Requirements
Perform any product-specific
post-migration tasks.
Mandatory if
your Oracle
product
requires any
post-migration
configuration.
Task 13 Decommission
11.1.1.1.0
Installation
Deinstall the 11.1.1.1.0 installation. For more information, see
Section C.4.2.11, "Decommissioning the
11.1.1.1.0 Installation".
For more information, see Section C.4.3,
"Post-Migration Configuration for
Oracle Fusion Middleware
Components".
Optional
C.4.2 Migration Procedure
Migrating your existing configuration from 11.1.1.1.0 to 11.1.1.2.0 involves the
following tasks:
1.
Stopping the Old Domain
2.
Installing Oracle Software for 11.1.1.2.0
3.
Downloading Patch Assistant
4.
Migrating the Schema
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-11
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
5.
Creating a WebLogic Domain for 11.1.1.2.0
6.
Migrating the Domain
7.
Migrating an Instance
8.
Registering the Instance
9.
Starting or Stopping the 11.1.1.2.0 Domain
10. Completing Post-Migration Tasks
11. Decommissioning the 11.1.1.1.0 Installation
C.4.2.1 Stopping the Old Domain
To stop the old 11.1.1.1.0 domain, complete the following steps:
You can also use Fusion Middleware Control, Oracle
WebLogic Server Administration Console, or WLST or OPMN
commands to stop the Oracle Fusion Middleware components.
Note:
1.
Open the patchMaster.properties file (Located in your patchMaster directory) in
a text editor, and specify the following properties in the patchMaster.properties
file, as applicable:
patchMaster.Oraclehomeold
patchMaster.Oracleinstanceoldlist
patchMaster.Domainadminhost
patchMaster.Domainadminport
If the patchMaster.Domainadminhost property is not specified, the default value
local host is used. If the patchMaster.Domainadminport property is not specified,
the default value 7001 is used. After editing the properties, save the file and close.
For more information about properties in the patchMaster.properties file, see
Section C.4.6, "Properties in the patchMaster.properties File".
If you have multiple Oracle products installed, then you must
run Patch Assistant once for each product and setting the
patchMaster.Oraclehomeold for each product.
Note:
2.
Run the following command on the command line:
ant master-stop-domain-old
3.
Enter the domain user name and password, when prompted.
C.4.2.2 Installing Oracle Software for 11.1.1.2.0
You must install Oracle WebLogic Server, Repository Creation Utility (RCU), and
Oracle products for 11.1.1.2.0:
■
Create a new Middleware home directory.
■
Install Repository Creation Utility.
■
Perform a software-only installation of the product bundle.
Ensure that your system environment meets the general installation requirements for
Oracle Fusion Middleware. Some Oracle Fusion Middleware Components require
C-12 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
schemas that must be installed in an Oracle database. It is recommended that you do
not install any new schemas for your existing 11g R1 (11.1.1.1.0) products. However, in
the same environment, you can add new products for which you may have to create
the appropriate schemas. For such products, you can create and load the schemas in
your database by using RCU. Ensure that you have a supported Oracle database up
and running. See
http://www.oracle.com/technology/software/products/ias/files/fusion_
certification.html for more information.
Ensure that same instance name used in 11.1.1.1.0 and 11.1.1.2.0.
When you migrate the mid-tier, you are installing a fresh
mid-tier in your new 11.1.1.2.0 environment. Patch Assistant migrates
the middle tier configuration to this new instance.
Note:
For information about the installation process, including Cluster scenarios, see
Section C.4.4, "Installation Process".
C.4.2.3 Downloading Patch Assistant
For information about downloading Patch Assistant and extracting its contents, see
Section C.3.2.2, "Extracting the Contents of Patch Assistant".
C.4.2.4 Migrating the Schema
Before you can upgrade the repository, ensure that your 11.1.1.1.0 domain is
configured and it includes tables populated from running the Repository Creation
Utility (RCU).
You can choose to install Oracle Content Server while
installing Oracle WebCenter, or later by performing a standalone
installation. In Oracle Fusion Middleware 11.1.1.1.0, if you performed
a standalone installation of Oracle Content Server, then before you
migrate the schemas, you must rename the Oracle Content Server's
schema so that it contains the standard suffix, OCSERVER. For
information, see Section C.4.2.4.1, "Renaming the Oracle Content
Server Schema"
Note:
To migrate the schema, complete the following steps:
1.
Open the patchMaster.properties file (Located in your patchMaster directory) in
a text editor, and specify the following schema-related properties in the
patchMaster.properties file:
patchMaster.Schemaurl
patchMaster.Schemauser
patchMaster.Schemaprefix
patchMaster.Mwhomenew
patchMaster.Mwhomeold
patchMaster.Componentlist
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-13
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Note: The patchMaster.Componentlist property is optional, if you
are migrating the schema for a single component. For Oracle Portal, in
addition to the above properties, you must specify the
patchMaster.Oraclehomenew property.
In patchMaster.Componentlist, include Oracle Content Server as a
component only if you created the server's schema using RCU. If you
did not create the schema using RCU, then list the server in
patchMaster.Componentlist only after completing the schema
renaming process described in section Section C.4.2.4.1, "Renaming
the Oracle Content Server Schema"
After editing the properties, save the file and close. For more information about
properties in the patchMaster.properties file, see Section C.4.6, "Properties in the
patchMaster.properties File".
2.
Run the following command on the command line to migrate the database
schema, and provide the required user name and password when prompted:
ant master-patch-schema
Patch Assistant can only migrate one set of component schemas that share the
same prefix. If different components in your deployment have different prefixes
and you have multiple schemas sharing a repository, then you must invoke Patch
Assistant multiple times, once for each prefix.
If you migrate the Metadata Services schema for one
component, it also affects all the other components using the same
Metadata Services schema. If you are using Oracle SOA, you must
enter ant -q master-patch-schema on the command line to migrate
the schema.
Note:
During the schema migration, exceptions may occur. Some of these exceptions can be
ignored. The following example shows one such exception:
[java] SEVERE: Error while registering Oracle JDBC Diagnosability MBean.
[java] java.security.AccessControlException: access denied
(javax.management.MBeanTrustPermission register)
[java]
at
java.security.AccessControlContext.checkPermission(AccessControlContext.java:323)
Patch Assistant ensures that all required properties are set for
each of the operations.
Note:
Patch Assistant attempts to migrate all Oracle Fusion Middleware
components. If a component is not installed or configured in the
deployment, log messages indicating these attempts are generated.
Log files specific to Oracle Portal migration are generated in the
upgrade.log and precheck.log files in the ORACLE_
HOME/upgrade/logs directory (UNIX).
C.4.2.4.1 Renaming the Oracle Content Server Schema In Oracle Fusion Middleware
11.1.1.1.0, if you performed a standalone installation Oracle Content Server, then
C-14 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
before migrating the schemas, you must rename the Oracle Content Server's schema so
that it contains the standard suffix, OCSERVER. You must also rebuild indexes on Oracle
Content Server.
To rename the Oracle Content Server schema:
1.
Create a new schema (for example, DEV_OCSERVER) using the RCU. Ensure that you
use the same password as that of your existing Oracle Content Server schema.
2.
Export the existing schema (for example, IDC_IR10).
3.
Import data into the new schema you created (DEV_OCSERVER).
Before you import data into the newly created schema, ensure
that all the seeded database objects are removed from that schema.
Note:
4.
Open the config/config.cfg file from the installation directory of your Oracle
Content Server.
5.
Change the Oracle Content Server schema name listed in the configuration file to
the newly created schema. (for example, rename IDC_IR10 to DEV_OCSERVER)
6.
Access the Oracle Content Server administration console and ensure that the data
exists.
After renaming the Oracle Content Server schema, you must migrate the schema, as
described in the beginning of this section.
After migrating the schemas, you must rebuild the indexes on Oracle Content Server.
To re-create the index:
1.
Log on to Oracle Content Server as a system administrator.
2.
Access Repository Manager from the Admin Console by navigating to
Administration > Admin Applets > Repository Manager.
3.
Click the Indexer tab.
4.
In the Collection Builder Cycle section, click Start. If the collection rebuild is
already in progress, do not choose to restart the operation. First stop the collection
rebuild operation, and then start the operation. Note that the collection rebuild
operation is a time-consuming task.
C.4.2.5 Creating a WebLogic Domain for 11.1.1.2.0
Create a WebLogic domain for 11.1.1.2.0 as follows:
1.
Run the MW_Home/oracle_common/common/bin/config.sh command (on UNIX) or
the MW_Home\oracle_common\common\bin\config.cmd command (on Windows) on
the command line. The Oracle Fusion Middleware Configuration Wizard appears.
For Oracle Portal, Oracle Forms, Oracle Reports, and Oracle Discoverer the
config.sh command is located at ORACLE_HOME/bin (on UNIX) and the
config.cmd is located at ORACLE_HOME\bin (on Windows).
2.
On the Welcome screen, select the Create a new WebLogic domain option. Click
Next. The Select Domain Source screen appears.
3.
On the Select Domain Source screen ensure that the Generate a domain
configured automatically to support the following products: option is selected.
Select templates for the products that are included in your existing 11.1.1.1.0
installation. For example, if the domain in your 11.1.1.1.0 installation had SOA
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-15
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
configured, you must configure the new domain with SOA in 11.1.1.2.0. Click
Next. The Select Domain Name and Location screen appears.
4.
Enter a name and a location for the domain to be created, and click Next. Ensure
that the domain name is same as the 11.1.1.1.0 domain. Click Next. The Configure
Administrator User Name and Password screen appears.
5.
Configure a user name and a password for the administrator. The default user
name is weblogic. Click Next.
6.
Choose a JDK in the Configure Server Start Mode and JDK screen.
7.
Configure JDBC Component Schemas and ensure that you retain the same
11.1.1.1.0 topology during this configuration.
8.
On the Select Optional Configuration screen, select the Administration Server and
Managed Servers, Clusters, and Machines, and Deployments and Services check
boxes. Click Next.
9.
Configure the Administration Server, Managed Servers, Clusters, Machines, as
required. Ensure that you retain the same 11.1.1.1.0 topology during this
configuration.
10. On the Configuration Summary screen, review the domain configuration, and
click Create to start creating the domain.
The WebLogic domain with your configuration attributes is created.
Patch Assistant ensures that all required properties are set for
each of the operations.
Note:
Patch Assistant attempts to migrate all Oracle Fusion Middleware
components. If a component is not installed or configured in the
deployment, log messages indicating these attempts are generated.
For more information about the configuration process, including Cluster scenarios, see
Section C.4.5, "Configuration Process".
C.4.2.6 Migrating the Domain
Before you can migrate the WebLogic domain, ensure that the database schemas are
migrated, the new 11.1.1.2.0 products are installed, the new 11.1.1.2.0 domain is
configured (as it was configured in the previous 11.1.1.1.0 installation), and all the
WebLogic domains are shut down. When you migrate the 11.1.1.1.0 domain, the
products configured in the domain are also migrated to the new 11.1.1.2.0 domain.
If you have multiple Oracle products installed, then you must
run Patch Assistant once for each product and setting the
patchMaster.Oraclehomeold property for each product. You must
patch all products in the domain being migrated.
Note:
To migrate the WebLogic domain, complete the following steps:
1.
Open the patchMaster.properties file (Located in your patchMaster directory) in
a text editor, and specify the following domain-related properties:
patchMaster.Domainhomenew
patchMaster.Domainapplicationshomenew
patchMaster.Domainhomeold
C-16 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
patchMaster.Domainusername
patchMaster.Oracleinstanceoldlist
patchMaster.Oraclehomeold
After editing the properties, save the file and close. For more information about
properties in the patchMaster.properties file, see Section C.4.6, "Properties in the
patchMaster.properties File".
2.
Run the following command on the command line to migrate the WebLogic
domain:
ant master-patch-domain
Patch Assistant ensures that all required properties are set for
each of the operations.
Note:
Patch Assistant attempts to migrate all Oracle Fusion Middleware
components. If a component is not installed or configured in the
deployment, log messages indicating these attempts are generated.
For the Oracle Directory Integration Platform, you only need to enter
the above target to complete the migration process. If you are using
Oracle SOA, you must enter ant -q master-patch-domain on the
command line to migrate the WebLogic domain.
If you are using a Cluster environment, ensure that the database schemas are
migrated, the new 11.1.1.2.0 products are installed in a Cluster environment, the new
11.1.1.2.0 domain is configured (as it was configured in the previous 11.1.1.1.0
installation) in a Cluster environment, and all the WebLogic domains are shut down.
C.4.2.7 Migrating an Instance
Before you can migrate the Oracle Instances, ensure that the database schemas are
migrated, the new 11.1.1.2.0 products are installed, the new 11.1.1.2.0 domain is
configured (as it was configured in the previous 11.1.1.1.0 installation), the domain is
migrated, and the Oracle Instances are shut down.
For Oracle Business Intelligence Discoverer in a High
Availability (clustered) environment with multiple Managed Servers,
you can override the default value WLS_DISCO by specifying the
following java properties on the command-line:
Note:
■
srcDiscoMgdServer
■
destDiscoMgdServer
For example:
ant -DsrcDiscoMgdServer=WLS_DISCO1 -DdestDiscoMgdServer=WLS_DISCO1
master-patch-oinstance
To migrate an instance, complete the following steps:
1.
Open the patchMaster.properties file (Located in your patchMaster directory) in
a text editor, and specify the following properties related to your Oracle Instance
homes:
patchMaster.Oracleinstanceoldlist
patchMaster.Oracleinstancenewlist
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-17
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
After editing the properties, save the file and close. For more information about
properties in the patchMaster.properties file, see Section C.4.6, "Properties in the
patchMaster.properties File".
2.
Run the following command on the command line to migrate the Oracle Instances:
ant master-patch-oinstance
Patch Assistant ensures that all required properties are set for
each of the operations.
Note:
Patch Assistant attempts to migrate all Oracle Fusion Middleware
components. If a component is not installed or configured in the
deployment, log messages indicating these attempts are generated.
C.4.2.8 Registering the Instance
After migrating an instance, you must register the instance by completing the
following steps:
Before registering the instance, ensure that your
Administration Server is up and running.
Note:
1.
Open the patchMaster.properties file (Located in your patchMaster directory) in
a text editor, and specify the following properties in the patchMaster.properties
file, as applicable:
patchMaster.Oracleinstancenewlist
After editing the properties, save the file and close. For more information about
properties in the patchMaster.properties file, see Section C.4.6, "Properties in the
patchMaster.properties File".
2.
Run the following command on the command line:
ant master-register-oinstance
3.
Enter the domain user name and password, when prompted.
Patch Assistant ensures that all required properties are set for
each of the operations.
Note:
Patch Assistant attempts to migrate all Oracle Fusion Middleware
components. If a component is not installed or configured in the
deployment, log messages indicating these attempts are generated.
C.4.2.9 Starting or Stopping the 11.1.1.2.0 Domain
Starting or stopping the new 11.1.1.2.0 domain requires the
patchMaster.Domainhomenew property to be specified in the patchMaster.properties
file.
To start the new 11.1.1.2.0 domain, run the following command on the command line:
ant master-start-domain-new
C-18 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
To stop the new 11.1.1.2.0 domain, run the following command on the command line:
ant master-stop-domain-new
C.4.2.10 Completing Post-Migration Tasks
For information about post-migration tasks specific to your product, see Section C.4.3,
"Post-Migration Configuration for Oracle Fusion Middleware Components".
When the Oracle Portal, Forms, Reports, and Discoverer
installation is performed on a Windows machine, the System PATH is
upgraded so that the ORACLE_HOME\bin for that installation precedes
PATH. You cannot run Oracle Forms from the first installation, by
default. To access the 11.1.1.1.0 components, right-click on My
Computer and then Properties, select the Advanced tab, and click the
Environment Variables button. Edit the System variable PATH so that
the ORACLE_HOME\bin that you want to use is the one that precedes
PATH.
Note:
C.4.2.11 Decommissioning the 11.1.1.1.0 Installation
After migrating to 11.1.1.2.0, you can deinstall Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0). For more information, refer to the following:
■
■
■
■
■
"Deinstalling Oracle Identity Management 11g Release 1 (11.1.1)" chapter in the
Oracle Fusion Middleware Installation Guide for Oracle Identity Management.
"Deinstalling Oracle Portal, Forms, Reports and Discoverer" chapter in the Oracle
Fusion Middleware Installation Guide for Oracle Portal, Forms, Reports and Discoverer.
"Deinstalling Oracle SOA Suite" chapter in the Oracle Fusion Middleware Installation
Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
"Deinstalling Oracle WebCenter" chapter in the Oracle Fusion Middleware
Installation Guide for Oracle WebCenter Portal.
"Deinstalling Oracle Web Tier" chapter in the Installing and Configuring Oracle
HTTP Server.
When you deinstall 11.1.1.1.0, the Installer removes the
previously created 11.1.1.2.0 windows service. Use the Ant
command-line utility to re-create that service for each instance as
follows:
Note:
ant master-opmn-create-service
Enter the required information when prompted by the Ant task.
C.4.3 Post-Migration Configuration for Oracle Fusion Middleware Components
After running the Patch Assistant, you must manually configure some of the Oracle
Fusion Middleware Components:
■
Post-Migration Configuration for Oracle Fusion Middleware Audit Framework
■
Post-Migration Configuration for Oracle Business Intelligence Discoverer
■
Post-Migration Configuration for Oracle Directory Integration Platform
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-19
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
■
Post-Migration Configuration for Oracle Identity Federation
■
Post-Migration Configuration for Oracle Platform Security Services
■
Post-Migration Configuration for Oracle Reports
■
Post-Migration Configuration for Oracle SOA
■
Post-Migration Configuration for Oracle User Messaging Service
■
Post-Migration Configuration for Oracle WebCenter
■
Post Migration Configuration for Oracle Web Services Manager
C.4.3.1 Post-Migration Configuration for Oracle Fusion Middleware Audit Framework
After running Patch Assistant for Oracle Fusion Middleware Audit Framework, you
must complete the following tasks:
■
Upgrade the Translation Table in Audit Schema
■
Migrating Audit Policy Configuration for Java Components
■
Creating the Audit Data Source
C.4.3.1.1 Upgrade the Translation Table in Audit Schema If the IAU_DISP_NAMES_TL audit
event translation data is defined in the 11.1.1.1.0, then you can migrate them to the
11.1.1.2.0, by completing the following steps:
1.
Run SQLPlus, and connect to the database as the system user. For example:
sqlplus sys as sysdba
2.
Run SQL commands in the following order:
SQL> alter session set current_schema=<Name_of_Your_Audit_Schema>;
SQL> delete from iau_disp_names_tl;
SQL> @disp_names.sql;
disp_names.sql is located at fmw11gR1ps1_patchassist\Audit folder.
To avoid scrambled characters, a Unicode-supported database
is required to store the translation data. In addition, to ensure proper
character set conversion between SQL*Plus and the database server, a
compatible character set, such as UTF8 or AL32UTF8, needs to be set for
the NLS_LANG environment variable before running disp_names.sql.
Note:
For the complete list of legal NLS_LANG values, see the Oracle
Database Documentation Library at:
http://www.oracle.com/technology/documentation/database.html
C.4.3.1.2 Migrating Audit Policy Configuration for Java Components If the audit policy is
configured for Java components in 11.1.1.1.0, you must import the configuration file
after running Patch Assistant, as follows:
1.
Log in to the Oracle Enterprise Manager 11g Fusion Middleware Control.
2.
Expand the WebLogic Domain on the left pane, and select your domain.
Your selected domain page is displayed.
3.
From the WebLogic Domain, select Security, and then Audit Policy.
C-20 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
The Audit Policy page is displayed.
4.
Select the Audit Policy, and click Import.
5.
Click Browse, and specify the path where your AuditConfiguration file is located.
6.
Click Ok.
C.4.3.1.3 Creating the Audit Data Source If the audit data source is used in Oracle Fusion
Middleware 11.1.1.1.0, then you must re-create the audit data store used in 11.1.1.2.0.
To do so, perform the following steps:
1.
Log in to the Oracle WebLogic Server administration console:
http://host:7001/console
2.
Under JDBC, click the Data Sources link.
The Summary of JDBC Data Sources page is displayed.
3.
Click New to create a new data source.
The Create a New JDBC Data Source page is displayed.
4.
Enter the following details for the new data source:
■
Name: Enter a name such as Audit Data Source-0
■
JNDI Name: jdbc/AuditDB
■
Database Type: Oracle
■
Database Driver: Oracle's Driver (Thin XA) Versions: 9.0.1, 9.0.2, 10, 11
If deploying to a managed cluster server, check AdminServer. This selection
ensures that the data source is listed in the audit store when switching from file to
database store.
5.
Click Next.
The Transaction Options page is displayed.
6.
Click Next.
The Connection Properties page is displayed.
7.
In the Connection Properties page, enter the following information:
■
Database Name: Enter the name of the database to which you will connect.
This usually maps to the SID.
■
Host Name: Enter the hostname of the database.
■
Port: Enter the database port.
■
■
Database User Name: This is the name of the audit schema that you created in
RCU. The suffix is always IAU for the audit schema. For example, if you gave
the prefix as test, then the schema name is test_iau.
Password: This is the password for the audit schema that you created in RCU.
Click Next.
8.
The next page lists the JDBC driver class and database details. Accept the default
values, and click Test Configuration to test the connection. If you see the message
"Connection established Successfully", click Next. If it displays any error, go back
and check the connection details.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-21
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
9.
In the Select Targets page, select the servers where this data source must be
configured, and click Finish.
C.4.3.2 Post-Migration Configuration for Oracle Business Intelligence Discoverer
After running Patch Assistant, ensure that all your existing Oracle BI Discoverer Plus
OLAP users have proper access privileges to the Oracle BI Discoverer 11g Release 1
(11.1.1.2.0) Discoverer Catalog. To set proper access privileges, perform the following
tasks using the command-line utilities:
■
Authorizing a New User to Access the Discoverer Catalog
■
Upgrading the Privileges of an Existing Discoverer Catalog User
C.4.3.2.1 Authorizing a New User to Access the Discoverer Catalog Use the following
commands to authorize one or more users so they can access the Discoverer Catalog:
java -classpath path_to_d4o_jar_file load . java -classpath path_to_d4o_jar_file
authorize -h hostname -po portname
-sid database_SID -p d4osyspasswd -u user
For example. on Windows:
java -classpath C:\temp\d4o.jar load . java -classpath C:\temp\d4o.jar authorize
-h sys42.example.com -po 1521
-sid disco_db1 -p nPword432 -u jones
For example, on UNIX:
java -classpath /home/abc/temp/d4o.jar load . java -classpath
/home/abc/temp/d4o.jar authorize -h sys42.example.com -po 1521
-sid disco_db1 -p nPword432 -u jones
In this example, you must run the load command only once before authorizing any
number of users. For example, if you want to authorize 10 users, run the load
command once, and then run the authorize command once for each user.
C.4.3.2.2 Upgrading the Privileges of an Existing Discoverer Catalog User To upgrade the
user's privileges to access all private and shared folders, use the following command:
java -classpath path_to_d4o_jar_file updatePrivileges -h hostname -po portname
-sid database_SID -p d4osyspasswd -u user
For example, on Windows:
java -classpath C:\temp\d4o.jar updatePrivileges -h sys42.example.com -po 1521
-sid disco_db1 -p nPword432 -u jones
For example, on UNIX:
java -classpath /home/abc/d4o.jar updatePrivileges -h sys42.example.com -po 1521
-sid disco_db1 -p nPword432 -u jones
In this example, if you specify the -u option, then the privileges are upgraded only for
that user. If you do not specify the -u option, then the privileges are upgraded for all
users.
C.4.3.3 Post-Migration Configuration for Oracle Directory Integration Platform
After running Patch Assistant, start your Oracle Directory Integration Platform 11g
Release 1 (11.1.1.2.0) domain. For more information, see the "Starting and Stopping
C-22 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Oracle Fusion Middleware " in the Oracle Fusion Middleware Administrator's Guide and,
then complete the following steps:
1.
Log in to Oracle Enterprise Manager Fusion Middleware Control.
2.
In the Oracle Enterprise Manager home page, select Farm, and then
Agent-Monitored Targets.
The Agent-Monitored Targets page is displayed.
3.
From the Targets table, select the target used by the Oracle Directory Integration
Platform, and click Configure.
The Configure Target page is displayed.
4.
Click Change Agent and, then select the Oracle Internet Directory Agent URL
from the drop-down box.
5.
Click Ok.
6.
Click Apply.
7.
Log out of Oracle Enterprise Manager.
8.
Log in to Oracle Enterprise Manager again.
9.
Unregister the ASInstance created during Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) Directory Integration Platform configuration by running the following
command:
Windows:
ORACLE_INSTANCE\bin\opmnctl unregisterinstance -adminHost -adminPort
-adminUserName
UNIX:
$ORACLE_IMSTANCE/bin/opmnctl unregisterinstance -adminHost -adminPort
-adminUserName
10. Delete the ASInstance created during Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) Directory Integration Platform Configuration by running the following
command:
Windows:
ORACLE_HOME\opmn\bin\opmnctl deleteinstance -oracleInstance <Oracle instance
root directory>
UNIX:
$ORACLE_HOME/opmn/bin/opmnctl deleteinstance -oracleInstance <Oracle instance
root directory>
C.4.3.4 Post-Migration Configuration for Oracle Identity Federation
After running Patch Assistant, your Credential Store Framework (CSF) is not migrated
to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), if you are using an LDAP store.
You must migrate the credentials manually from a source repository to a target
repository by using the WLST command migrateSecurityStore.
For information, see "Migrating with the Script migrateSecurityStore" in Securing
Applications with Oracle Platform Security Services in the Oracle Fusion Middleware 11g
Release 1 (11.1.1.2.0) documentation library on OTN.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-23
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.4.3.5 Post-Migration Configuration for Oracle Platform Security Services
You must manually migrate your existing Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) policy store because the corresponding schema changes when you install
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). During this migration, any
existing 11.1.1.1.0 installation policies are upgraded to 11.1.1.2.0 policies. You will find
the existing 11.1.1.1.0 data provisioned in the 11.1.1.2.0 LDAP store.
However, you must redeploy your applications after installing Oracle Fusion
Middleware (11.1.1.2.0), but the provisioned policies are already in the migrated LDAP
store.
When redeploying your applications, you should not migrate
the policies as they already exist in the policy store.
Note:
Note that Oracle WebLogic Server domains are containers of application policy data
that is used by Oracle Platform Security Services. Typically, a domain is identified by
its name, as in the following example:
Relative DN(RDN)cn=MyDomain,cn=JpsContext,cn=JpsTestNode
The Relative DN (RDN) cn=MyDomain is the node on the LDAP server that
corresponds to a domain. All data under such a domain, including Credential Store
and Policy Store data, is preserved.
If you are using Oracle WebLogic Server LDAP, then you must
re-create the user. For more information, see "Security Data Migration"
section in Developing Security Providers for Oracle WebLogic Server in the
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) documentation
library
Note:
Migration Scenarios
If you are migrating Oracle Platform Security Services 11.1.1.1.0 Policy Store to 1.1.1.2.0
Policy Store, consider the following migration scenarios:
■
■
Migrating File-Based Policy and Credential Store
Migrating Oracle Internet Directory Policy and Credential Store and Reusing an
Existing Oracle Internet Directory Server
C.4.3.5.1 Migrating File-Based Policy and Credential Store To migrate your existing
file-based policy and credential store from 11.1.1.1.0 to 11.1.1.2.0, you must install
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), which is configured to use the
file-based policy (XML), credential (wallet) stores, and then migrate the credentials
and application policies by using the WebLogic Scripting Tool (WLST) command
migrateSecurityStore. For more information, see the "Migrating Credentials with the
Command migrateSecurityStore" section in the Oracle Fusion Middleware Security Guide
in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) documentation library.
C.4.3.5.2 Migrating Oracle Internet Directory Policy and Credential Store and Reusing an
Existing Oracle Internet Directory Server To migrate your existing Oracle Internet
Directory policy and credential store from Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0), start the servers in
your Oracle Fusion Middleware domain and then complete the following steps:
C-24 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Ensure that your Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) installation has applications deployed on a single domain
and configured with LDAP or credential store. In addition, make sure
that you do not have any resource catalog information provisioned.
Note:
1.
Reconfigure the LDAP authenticator to use the same LDAP server used in the
11.1.1.1.0 installation. For information, see the Securing Applications with Oracle
Platform Security Services in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library.
For information on reconfiguring the LDAP authenticator to
use the same LDAP server used in Oracle WebCenter 11.1.1.1.0
installation, see the "Reassociating the Identity Store with an External
LDAP" section in the Oracle Fusion Middleware Administrator's Guide for
Oracle WebCenter in the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) documentation library.
Note:
2.
Upgrade the Java Platform Security (JPS) LDAP schema in the LDAP store by
using the WLST reassociateSecurityStore command. The reassociation creates a
temporary node under a pre-existing jps root node. The temporary data is the
domain, you specified during reassociation. The domain needs to be a new
temporary name and the jpsroot should have the same name that contains the
domain you are migrating from 11.1.1.1.0.
For information, see "reassociateSecurityStore" in Securing Applications with Oracle
Platform Security Services in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library.
This command creates a temporary domain that will be deleted later. For example:
reassociateSecurityStore(domain="ps1_tmp_domain",admin="cn=orcladmin",
password="welcome1", ldapurl="ldap://example.com:3060", servertype="OID",
jpsroot="cn=jpsroot_r1_name")
Set a temporary name for the domain, and ensure that the
jpsroot has the same name as in 11.1.1.1.0.
Note:
3.
Ensure that the Oracle WebLogic Administration Server is stopped to change the
server configuration. To stop the server, run the following command:
Windows:
MW_HOME\user_projects\domains\<domain_name>\bin\stopWebLogic.cmd
username password admin_url
UNIX:
$ MW_HOME/user_projects/domains/<domain_name>/bin/stopWeblogic.sh
username password admin_url
4.
Rebuild the Oracle Internet Directory catalog by running the following catalog
commands from the Oracle Internet Directory machine:
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-25
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Before you start using the Oracle Identity Management
command-line tools, you must configure your environment. This
involves setting the appropriate environment variables as follows:
Note:
■
■
■
ORACLE_HOME - The location of non-writable files in your
LDAP-based identity store installation.
ORACLE_INSTANCE - The location of writable files in your
LDAP-based identity store installation.
TNS_ADMIN - The location of tnsnames.ora file in your Oracle
home.
Ensure that the tnsnames.ora file (Located at ORACLE_
HOME/network/admin) contains the conn_str that will be used in
the catalog command.
■
PATH - Add the following directory locations to your PATH:
ORACLE_HOME/bin
ORACLE_HOME/ldap/bin
ORACLE_HOME/ldap/admin
Drop the catalog first before re-creating it as follows:
catalog connect="conn_str" delete=true
catalog connect="conn_str" delete=true
catalog connect="conn_str" delete=true
catalog connect="conn_str" delete=true
catalog connect="conn_str" delete=true
orclJpsResourceTypeActionNames
attribute=
attribute=
attribute=
attribute=
attribute=
createtimestamp
modifytimestamp
orclJpsResourceName
orclJPSObjGUID
Then add the following:
catalog
catalog
catalog
catalog
catalog
connect="conn_str"
connect="conn_str"
connect="conn_str"
connect="conn_str"
connect="conn_str"
add=true
add=true
add=true
add=true
add=true
attribute=
attribute=
attribute=
attribute=
attribute=
createtimestamp
modifytimestamp
orclJpsResourceName
orclJPSObjGUID
orclJpsResourceTypeActionNames
For more information, see "Performing Bulk Operations" in Oracle Fusion
Middleware Administrator's Guide for Oracle Internet Directory in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
5.
Delete the temporary domain, created in step 1, by performing the following:
a.
Disable the Server Entry Cache. For more information, see "Tuning
Recommendations for Server Entry Cache" in Oracle Fusion Middleware
Administrator's Guide for Oracle Internet Directory in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
b.
Stop Oracle Internet Directory by running the following command:
Windows
ORACLE_INSTANCE\bin\opmnctl stopall
UNIX
ORACLE_INSTANCE/bin/opmnctl stopall
c.
Run the following command:
C-26 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
bulkdelete connect="connect string" basedn="cn=ps1_tmp_
domain,cn=JPSContext,cn=jpsroot_r1_name"
Do not use JXplorer or any other LDAP browser to delete the
JPS root node.
Note:
For more information, see "Deleting Entries or Attributes of Entries by Using
bulkdelete" in Oracle Fusion Middleware Administrator's Guide for Oracle Internet
Directory in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library.
d.
Start Oracle Internet Directory by running the following command:
Windows
ORACLE_INSTANCE\bin\opmnctl startall
UNIX
ORACLE_INSTANCE/bin/opmnctl startall
e.
Enable the Server Entry Cache. For more information, see the "Tuning
Recommendations for Server Entry Cache" section and the "Attributes of the
Instance-Specific Configuration Entry" section in the Oracle Fusion Middleware
Administrator's Guide for Oracle Internet Directory in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
f.
Stop and start Oracle Internet Directory by running the following commands:
Windows
ORACLE_INSTANCE\bin\opmnctl stopall
ORACLE_INSTANCE\bin\opmnctl startall
UNIX
ORACLE_INSTANCE/bin/opmnctl stopall
ORACLE_INSTANCE/bin/opmnctl startall
6.
Open the jps-config.xml file (located in your MW_HOME\user_
projects\domains\<DomainName>\config\fmwconfig directory) in a text editor
and replace the 11.1.1.2.0 domain name with 11.1.1.1.0 domain name. For example,
replace cn=ps1_tmp_domain with cn=R1_domain_name.
7.
Migrate the default system policies from the XML store to the LDAP store by
using the WLST Command migrateSecurityStore.
For more information, see the "Migrating Credentials with the Command
migrateSecurityStore" section in the Securing Applications with Oracle Platform
Security Services in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library.
In the jps-config.xml file, add the entries to specify the source and the
destination source JPS context. The source JPS context must be the one that uses
the XML store as the policy store, and the destination JPS context must be the one
that uses the LDAP store. For example, add the following entries in the
jps-config.xml file:
<jpsContext name="filestore">
<serviceInstanceRef ref="policystore.xml"/>
</jpsContext>
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-27
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
<jpsContext name="ldapstore">
<serviceInstanceRef ref="policystore.ldap"/>
</jpsContext>
Ensure that the policystore.xml service instance in jps-config.xml file refers to
the shipped system-jazn-data.xml file (out-of-the-box), as in the following
example:
<serviceInstance location="./system-jazn-data.xml"
provider="policystore.xml.provider" name="policystore.xml">
<description>File Based Policy Store Service Instance</description>
</serviceInstance>
Migrate the system policies by using the WLST migrateSecurityStore command,
as shown in the following example:
migrateSecurityStore(type="globalPolicies", configFile="<domain level
jpsconfig.xml file loc>", src="filestore" ,dst="ldapstore")
For more information about the migrating system policies, see "Migrating Policies
to the Domain Policy Store" in Securing Applications with Oracle Platform Security
Services in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) documentation
library.
8.
Ensure that the LDAP server contains the Role Categories entry under your
application policy node.
a.
Run the ldapsearch command to search for this Role Categories entry from
the Oracle Internet Directory machine:
LDAP_OH/bin/ldapsearch -h <host> -p <port> -D "<Admin DN>" -w password -b
"cn=Role Categories,cn=<app name>,cn=<domain
name>,cn=JpsContext,cn=<jpsroot name>" -s base "(objectclass=*)"
Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory.
Example:
LDAP_OH/bin/ldapsearch -h oid.example.com -p 3060 -D "cn=orcladmin" -w
password -b "cn=Role
Categories,cn=appname,cn=domainname,cn=JpsContext,cn=jpsroot" -s base
"(objectclass=*)"
For detailed syntax, see the "ldapsearch" topic in the Oracle Fusion Middleware
Reference for Oracle Identity Management in the Oracle Fusion Middleware 11g
Release 1 (11.1.1.2.0) documentation library.
If the Role Categories entry is not available, the following
message is displayed:
Note:
ldap_search: No such object
b.
If the Role Categories entry is not present, create an LDIF file named
rolecat.ldif with the following content:
dn: cn=Role Categories,cn=<app name>,cn=<domain
name>,cn=JPSContext,cn=<jpsroot name>
objectclass: top
objectclass: orclContainer
cn: Role Categories
C-28 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Example:
dn: cn=Role Categories,cn=webcenter,cn= R1_domain_
name,cn=JPSContext,cn=jpsroot_r1_name
objectclass: top
objectclass: orclContainer
cn: Role Categories
c.
Run the ldapadd command to add this node to the application policy store as
follows:
LDAP_OH/bin/ldapadd -p <port> -h <host> -D "<Admin DN>" -w <password> -vf
rolecat.ldif
Where LDAP_OH/bin is the OID/IdM IDM_ORACLE_HOME/bin directory.
Example:
LDAP_OH/bin/ldapadd -p 3060 -h oid.example.com -D "cn=orcladmin" -w
password -vf rolecat.ldif
For detailed syntax, see the "ldapadd" topic in the Oracle Fusion Middleware
Reference for Oracle Identity Management in the Oracle Fusion Middleware 11g
Release 1 (11.1.1.2.0) documentation library.
If the node exists, the output of the ldapadd command
indicates that the object already exists.
Note:
Note: The ldapadd command for Role Categories must be run for
every application that uses LDAP as policy store.
9.
Start the Oracle WebLogic Administration Server, as shown in the following
example:
MW_HOME/user_projects/domains/domain_name/bin/startWebLogic.sh
-Dweblogic.management.username=weblogic
-Dweblogic.management.password=password
For more information, see "Starting and Stopping Oracle Fusion Middleware" in
Oracle Fusion Middleware Administrator's Guide.
10. Redeploy any user applications that were deployed in 11.1.1.1.0.
C.4.3.6 Post-Migration Configuration for Oracle Reports
After running Patch Assistant, your Oracle Internet Directory Policy and Credential
Store (CSF) is not migrated to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). For
information about migrating the Oracle Internet Directory Policy and Credential Store
(CSF), see Section C.4.3.5.2, "Migrating Oracle Internet Directory Policy and Credential
Store and Reusing an Existing Oracle Internet Directory Server".
C.4.3.7 Post-Migration Configuration for Oracle SOA
After running Patch Assistant, you must perform the following:
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-29
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Notes: Service Engine configuration has moved from file to the
database in 11.1.1.2.0.
The procedures in this chapter are for installing and configuring
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). As a result, for all
cross-references in this section, refer to the Oracle Fusion Middleware
11g Release 1 (11.1.1.2.0) documentation library.
1.
Re-deploy your J2EE applications, including TaskDetail Application used in
Human Workflow Applications. For more information, see "Deploying SOA
Composite Applications" chapter in the Administering Oracle SOA Suite and Oracle
Business Process Management Suite.
2.
Reconfigure any changes made to configuration files (For example:
soa-infra-config) and component-level configuration files in 11.1.1.1.0 must be
reconfigured for 11.1.1.2.0 using the Oracle Enterprise Manager Fusion
Middleware Control.
3.
Reconfigure the log level settings using the Oracle Enterprise Manager Fusion
Middleware Control. For more information, see "Configuring Logging" section in
the Administering Oracle SOA Suite and Oracle Business Process Management Suite.
4.
Re-create the seeding of the Workflow users.
5.
Reconfigure the Secure Sockets Layer (SSL) for the SOA composite application. For
more information, see "Securing SOA Composite Applications" in Administering
Oracle SOA Suite and Oracle Business Process Management Suite.
6.
If you have configured the Oracle HTTP Server for 11.1.1.1.0, then you must
reconfigure it for 11.1.1.2.0.
7.
For composites involving BPEL Sensors with sensor action as JMS Queue, JMS
Topic, JMS Adapter (remote JMS), re-create the JMS Queue, JMS topic, and the
remote JMS set up.
8.
Configure the identity and policy provider, as described in Section C.4.3.5.2,
"Migrating Oracle Internet Directory Policy and Credential Store and Reusing an
Existing Oracle Internet Directory Server".
9.
Configure the SSO provider for 11.1.1.2.0.
10. Configure the adapters as follows:
■
■
■
■
Create the data source for the AQ adapter by following the steps described in
the "Configuring the Data Sources in the Oracle WebLogic Server
Administration Console" section in the Understanding Technology Adapters.
Configure AQ JMS in Oracle WebLogic Server Administration Console. For
more information, see the Understanding Technology Adapters.
Create the foreign server for the AQJMS again and restart the server.
After migration, if the log was showing Queue Manager not available (with
MQ reason code: 2059), you must modify the JNDI, which is used by the
composite deployed to point to the Queue Manager, which was used for
pre-upgrade. After making this change, you must restart SOA.
11. Migrate the B2B for 11.1.1.2.0 as follows:
a.
Import previously exported repository from 11.1.1.1.0 with the Replace
Existing MetaData flag.
C-30 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
b.
Upgrade the key store password and restart the B2B server.
c.
Select the certificate alias in delivery channel and save.
d.
Deploy the B2B agreements.
C.4.3.8 Post-Migration Configuration for Oracle User Messaging Service
After running Patch Assistant, you must perform the following:
■
Migrating Configuration for Additional Custom-Deployed Drivers
■
Migrating Configuration for User Messaging Service Worklist Driver
C.4.3.8.1 Migrating Configuration for Additional Custom-Deployed Drivers If your Oracle
Fusion Middleware 11g Release 1 (11.1.1.1.0) domain has configuration files for
additional User Messaging Service driver deployments beyond those provisioned at
install time, then you must migrate them to Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0). Run the following Ant command on the command-line:
ant -f UMS/build.xml patch-ums-driver-config -Ddriver.name=<driver_name>
Where <driver_name> is the deployment name of the custom driver. The build.xml
file is located in your patchMaster directory.
This command only migrates the configuration to Oracle
Fusion Middleware (11.1.1.1.2.0) domain and will not deploy the
driver.
Note:
C.4.3.8.2 Migrating Configuration for User Messaging Service Worklist Driver If your Oracle
Fusion Middleware 11g Release 1 (11.1.1.1.0) domain has the User Messaging Service
Worklist Driver installed and configured, then the configuration of the Worklist Driver
is automatically migrated by the Patch Assistant. Patch Assistant does not install this
additional driver. You must re-install the driver in the Oracle Fusion Middleware 11g
Release 1 (11.1.1.2.0) domain.
For more information, see "Install the Worklist Driver" section in the Administering
Oracle SOA Suite and Oracle Business Process Management Suite in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
C.4.3.9 Post-Migration Configuration for Oracle WebCenter
This section describes the tasks involved in getting your Oracle WebCenter 11.1.1.2.0
up and running after you have migrated the mid-tier.
C.4.3.9.1 Overview of Tasks for Configuring Oracle WebCenter Post Mid-Tier Migration
Table C–2 describes the tasks involved in configuring Oracle WebCenter 11.1.1.2.0 after
the Patch Assistant script has been executed. The table also specifies whether these
tasks are optional or mandatory.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-31
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–2
Post Mid-Tier Migration Tasks for Oracle WebCenter
Task
Description
Mandatory/Optional?
Reconfiguring
Oracle WebCenter
Identity Store and
Migrating the
Application Policy
to the WebCenter
Policy Store
Configure the identity store to use the
same configuration as Oracle
WebCenter 11.1.1.1.0. Also, run the
updateSpacesPolicy.py script to
update the application store to include
appropriate security permissions for
WebCenter Spaces.
Mandatory
Note: You must run
updateSpacesPolicy.py even if your
Oracle WebCenter uses the embedded
LDAP identity store.
Configuring Oracle
WebCenter for
Secure Sockets
Layer (SSL)
Configure Oracle WebCenter 11.1.1.2.0
to use the same SSL configuration and
keystore as Oracle WebCenter
11.1.1.1.0.
Mandatory if SSL is configured
in Oracle WebCenter 11.1.1.1.0
Configuring Oracle
WebCenter for
Single Sign-On
(SSO)
Configure your single sign-on (SSO)
solution to use the same SSO
configuration as Oracle WebCenter
11.1.1.1.0.
Mandatory if SSO is
configured in Oracle
WebCenter 11.1.1.1.0
Refreshing Group
Space Data in
WebCenter Spaces
Refresh the group space data and the
data about group space members.
Mandatory
Reapplying
Configuration
Changes
Reapply any configuration changes
made to Oracle WebCenter 11.1.1.1.0.
Mandatory
Importing Wiki
Templates and
Attachments
Migrate templates and attachments to
the database repository of Oracle
WebCenter Wiki and Blog Server.
Mandatory if Oracle
WebCenter Wiki and Blog
Server is configured for Oracle
WebCenter 11.1.1.1.0
Migrating Oracle
Content Server
Run the WebCenter configuration
script wc_contentserverconfig to
migrate to Oracle Content Server
10.1.3.5.1. Also, configure a JPS user
provider in place of the existing LDAP
user provider.
Mandatory if Oracle Content
Server is configured for Oracle
WebCenter 11.1.1.1.0
Configuring Oracle
WebCenter
Discussions for
WebCenter Spaces
Configure Web Services Security
Mandatory
(WS-Security) if you want to use Oracle
WebCenter Discussions with Oracle
WebCenter Spaces.
Migrating Custom
WebCenter
Applications
Migrate custom WebCenter
applications to Oracle WebCenter
11.1.1.2.0.
Mandatory
C.4.3.9.2 Reconfiguring Oracle WebCenter Identity Store and Migrating the Application Policy to
the WebCenter Policy Store You must migrate your existing identity store and credential
store. Before doing so, be sure to start all the servers in your WebCenter domain.
If you are using the embedded LDAP based policy and credential store, for
information about the tasks that you need to perform, see the "Exporting and
Importing a File-based Policy Store" and "Exporting and Importing a File-based
Credential Store" sections in the Oracle Fusion Middleware Administrator's Guide for
Oracle WebCenter in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library.
C-32 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
When Oracle WebCenter 11.1.1.1.0 is configured to use an external LDAP-based
identity store, then post mid-tier migration you must migrate your identity store and
credential store to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0). For information
about how to migrate Oracle Internet Directory policy and credential store, see
Section C.4.3.5.2, "Migrating Oracle Internet Directory Policy and Credential Store and
Reusing an Existing Oracle Internet Directory Server."
After migrating the identity and credential store, you must run the
updateSpacesPolicy.py script to update the WebCenter Spaces application policy to
include appropriate security permissions. If you do not run this script, WebCenter
Spaces users will not be able to access their profile information or the service tabs in
group spaces.
You must run the updateSpacesPolicy.py script even if your
Oracle WebCenter uses the embedded LDAP identity store.
Note:
To execute updateSpacesPolicy.py:
1.
Launch WLST with this command:
WC_ORACLE_HOME/common/bin/wlst.sh
Where WC_ORACLE_HOME refers to the Oracle WebCenter installation directory.
2.
At the WLST command prompt, enter the following command to connect to the
Administration Server:
wls:/offline> connect('user_name,'password, 'host_name:port_number')
For example, use the following command:
connect('weblogic','weblogic', 'myhost.example.com:7001')
3.
Use the following command to run the updateSpacesPolicy.py script:
wls:/weblogic/serverConfig> execfile('WC_ORACLE_
HOME/webcenter/scripts/updateSpacesPolicy.py')
4.
Ensure that there are no errors logged on the console. If there are errors, use the
error message as a guide and inspect the updateSpacesPolicy.py script to
determine the grant command that failed. You must fix errors, if any, and run the
grant command manually.
5.
Restart the Administration Server and the WLS_Spaces Managed Server.
C.4.3.9.3 Configuring Oracle WebCenter for Secure Sockets Layer (SSL) Secure Sockets Layer
(SSL) provides additional security for connections between WebCenter applications or
components by providing an additional authentication layer, and by encrypting the
data exchanged. During mid-tier migration, the SSL configuration does not get
migrated. After running the Patch Assistant script, you must reconfigure SSL for
Oracle WebCenter and, if required, for various WebCenter Services integrated into
your WebCenter applications.
For information about how to configure SSL for WebCenter applications and
WebCenter Services, see the "Configuring WebCenter Applications and Components
to Use SSL" section in Oracle Fusion Middleware Administrator's Guide for Oracle
WebCenter in the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) documentation
library.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-33
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
For example, in Oracle WebCenter 11.1.1.1.0, if secured portlets were used in
WebCenter Spaces, then your keystore must have been set to the Custom Identity and
Java Standard Trust keystore and you would have imported the required portlet
certificates in the Java standard trust keystore (typically cacerts). Now, post mid-tier
migration, you must configure the WLS_Spaces server, in your Oracle WebCenter
11.1.1.2.0 instance, to use the Custom Identity and Java Standard Trust keystore and
other SSL-specific settings that were configured for Oracle WebCenter 11.1.1.1.0. Also,
you must reimport all your portlet certificates into the trust keystore to access secured
portlets in Oracle WebCenter 11.1.1.2.0.
C.4.3.9.4 Configuring Oracle WebCenter for Single Sign-On (SSO) For single sign-on (SSO)
authentication, your Oracle WebCenter 11.1.1.1.0 may be configured to use Oracle
Access Manager (OAM), Oracle Single Sign-on (OSSO), or a SAML-based single
sign-on solution for WebCenter applications only. After mid-tier upgrade, you may
need to perform the following configuration, depending on the SSO solution used.
For each of these cross-references, refer to the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) documentation library:
■
■
■
Configuring OAM: Configure the authenticator and the OAM asserter to use the
same configuration as used in Oracle WebCenter 11.1.1.1.0. For information, see
the "Configuring Oracle Access Manager (OAM)" section in the Oracle Fusion
Middleware Administrator's Guide for Oracle WebCenter.
Configuring OSSO: Configure the authenticator and the OSSO asserter to use the
same configuration as used in Oracle WebCenter 11.1.1.1.0. For information, see
the "Configuring Oracle Single Sign-On (OSSO)" section in the Oracle Fusion
Middleware Administrator's Guide for Oracle WebCenter.
Configuring SAML-based SSO: You must set up your entire SAML-based SSO
solution. For information, see the "Configuring SAML-based Single Sign-on"
section in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
Note: If WebCenter is running with SSO, the OmniPortlet producer
receives an authorization exception when it tries to store connection
information in the Credential Store Framework (CSF) wallet. For
information about how to resolve this issue, see the "OmniPortlet
Producer Authorization Exception in SSO Environment" section in the
Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
C.4.3.9.5 Refreshing Group Space Data in WebCenter Spaces After mid-tier migration, you
must refresh the group space data. Also, refresh the member data for each group space
individually.
To refresh the group space data:
1.
Log on to WebCenter Spaces as an administrator.
2.
Click the Administration link, and go to the Group Spaces tab.
3.
Click the Refresh icon.
To refresh the member data for a group space:
1.
Log on to WebCenter Spaces as an administrator.
2.
Go to the desired group space, open the Settings tab, and then the Members tab.
3.
Click the Refresh icon in the Manage Group Space Members section.
C-34 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
You must perform this procedure for each group space individually.
In your migrated WebCenter instance if access is denied to a
group space, ensure that the credential store has been migrated
successfully and the group space data has been refreshed.
Note:
After you upgrade from Oracle WebCenter 11.1.1.1.0 to Oracle
WebCenter 11.1.1.2.0, you may initially see a group space GUID in
Activity Stream in lieu of a group space name in WebCenter Spaces.
This can occur when you configure an Activity Stream task flow
instance and select to display activity from a group space that was
upgraded. You can work around this issue by generating some
activity in that group space, like adding or removing a member. This
refreshes the Activity Stream instance with the group space display
name.
C.4.3.9.6 Reapplying Configuration Changes If you want the same configuration as
defined in your Oracle WebCenter 11.1.1.1.0, then you must reapply the configuration
changes in Oracle WebCenter 11.1.1.2.0. Configuration changes may relate to the any
of the following. All references are to the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) documentation library:
■
■
■
■
■
WebCenter Portlet Producers: Any changes made to the provider.xml file of a
portlet producer, like changing a proxy server, require that post mid-tier migration
you reconfigure those changes, redeploy the portlet producer EAR application,
and restart WLS_Portlet Managed Server. For information about redeploying
portlet producers, see the "Managing Portlet Producers" chapter in the Oracle
Fusion Middleware Administrator's Guide for Oracle WebCenter.
WebCenter Services: While installing Oracle Fusion Middleware 11.1.1.2.0, if you
changed the host and port number of the back-end servers on which your
WebCenter Services rely, you must reconfigure the required service connections to
use the new server configuration. For information about specific services, see the
"Managing Services, Portlet Producers, and External Applications" part in the
Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
WebCenter Wikis and Blogs: Any configuration changes made to your Oracle
WebCenter Wiki and Blog Server 11.1.1.1.0, such as changing the theme or setting
the attachment size, require that you reapply those changes in Oracle WebCenter
Wiki and Blog Server 11.1.1.2.0. To reconfigure settings, use Administration mode
of your Oracle WebCenter Wiki and Blog Server. For information, see the "Oracle
WebCenter Wiki and Blog Server - Configuration" section in the Oracle Fusion
Middleware Administrator's Guide for Oracle WebCenter.
WebCenter Spaces and Workflows: The WebCenter Spaces workflows
functionality requires sca_CommunityWorkflows.jar and
WebCenterWorklistDetailApp.ear to be deployed to a SOA server. If WebCenter
Spaces workflows were enabled in Oracle WebCenter 11.1.1.1.0, you must
redeploy these applications to the SOA server post mid-tier migration. For
information, see the "Back-End Requirements for WebCenter Spaces Workflows"
section in the Oracle Fusion Middleware Installation Guide for Oracle WebCenter.
WebCenter Spaces profile settings: In WebCenter Spaces, profile settings set on the
WebCenter Administration > Services > Profile screen are not retained when you
upgrade from Oracle WebCenter 11.1.1.1.0 to Oracle WebCenter 11.1.1.2.0. After
the upgrade, you must reapply the required profile settings on the WebCenter
Administration > Services > People Connections > Profiles screen.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-35
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.4.3.9.7 Importing Wiki Templates and Attachments In Oracle WebCenter Wiki and Blog
Server 11.1.1.1.0, regardless of the repository type configured for the server, templates
and attachments are stored in a file-based repository. Oracle WebCenter Wiki and Blog
Server 11.1.1.2.0 supports only a database repository; templates and attachments are
also stored in the database repository.
If your Oracle WebCenter Wiki and Blog Server 11.1.1.1.0 used a database repository,
then during migration templates and attachments are migrated to the database
repository configured for Oracle WebCenter Wiki and Blog Server 11.1.1.2.0. If your
Oracle WebCenter Wiki and Blog Server 11.1.1.1.0 used a file-based repository, then
during migration wiki templates and attachments are migrated to a file-based
repository. To make these templates and attachments available in Oracle WebCenter
Wiki and Blog Server 11.1.1.2.0, you must manually migrate them to the database
repository.
To import attachments for a wiki page, the user who owns that wiki page or you as an
administrator must reupload the attachments on the wiki page. When you reupload an
attachment, the attachment gets stored in the database repository. Note that
attachments must be reuploaded for each wiki page individually.
To migrate templates:
1.
Log on to Oracle WebCenter Wiki and Blog Server 11.1.1.2.0 as an administrator.
2.
Click the Administration link to open Administration mode.
3.
Click Templates.
4.
Click import.
5.
On the Import Templates page, in the Folder field, enter the path to templates. For
example:
$APPLICATIONS_DIRECTORY/owc_wiki/templates.
Where, $APPLICATIONS_DIRECTORY is the directory where you installed Oracle
WebCenter Wiki and Blog Server 11.1.1.2.0. That is, $APPLICATIONS_DIRECTORY =
MW_HOME/user_projects/applications/DOMAIN_NAME.
6.
Click Import Templates. The existing file-based templates are individually
re-created in the wiki database repository.
C.4.3.9.8 Migrating Oracle Content Server Oracle WebCenter 11.1.1.2.0 is compatible with
Oracle Content Server 10.1.3.5.1. To migrate your existing Oracle Content Server and
prepare it to work with Oracle WebCenter 11.1.1.2.0, you must perform the following
tasks. All references are to the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library:
■
■
Run the WebCenter configuration script, wc_contentserverconfig. This script is
available on the Universal Content Management (UCM) media shipped with
Oracle WebCenter. For information about how to run the script, see the "Oracle
Content Server - Installation" section in the Oracle Fusion Middleware Installation
Guide for Oracle WebCenter.
Reconfigure the identity store for Oracle Content Server. To connect to an
LDAP-based identity store, Oracle Content Server 10.1.3.5.1 requires a JPS user
provider, instead of an LDAP user provider. Therefore, you must configure a JPS
user provider and ensure that the existing LDAP user provider for Oracle Content
Server is disabled. For information, see the "Configuring the Identity Store" section
in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.
C-36 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.4.3.9.9 Configuring Oracle WebCenter Discussions for WebCenter Spaces When you
migrate from Oracle Fusion Middleware 11.1.1.1.0 to Oracle Fusion Middleware
11.1.1.2.0, the patch assistant script migrates the database schema of your Oracle
WebCenter Discussions server. Out-of-the-box, Oracle WebCenter Discussions
11.1.1.2.0 is configured to use the embedded LDAP identity store of Oracle WebLogic
Server.
You must configure Web Services Security (WS-Security) if you want to use Oracle
WebCenter Discussions with WebCenter Spaces.
To configure Oracle WebCenter Discussions:
1.
Log on to the Oracle WebCenter Discussions 11.1.1.2.0 server as an administrator
by using the following URL format:
http://host:port/owc_discussions/admin
Where host:port refer to the host name and port number of the system where
Oracle WebCenter is installed.
2.
To verify that Oracle WebCenter Discussions has been migrated successfully, in
Jive Forums Admin Console, ensure that "Jive Forums Silver 5.5.20.2-oracle" is
displayed in the top-right corner.
3.
Configure WS-Security trusted authentication if you want to use Oracle
WebCenter Discussions with WebCenter Spaces. For information about how to
configure WS-Security, see "Configuring WS-Security" in the Oracle Fusion
Middleware Administrator's Guide for Oracle WebCenter in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
4.
Reconfigure SSO for Oracle WebCenter Discussions, if required. For information,
see the "Configuring a WebCenter Application to Use Single Sign-On" section in
the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter in the
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) documentation library.
C.4.3.9.10 Migrating Custom WebCenter Applications To make your custom WebCenter
applications available in Oracle WebCenter 11.1.1.2.0, you must migrate them from
your Oracle WebCenter 11.1.1.1.0 instance. You do not need to migrate the metadata of
these applications because Oracle WebCenter 11.1.1.2.0 schemas are an in-place patch
of your Oracle WebCenter 11.1.1.1.0 schemas for MDS, PORTLET, and WEBCENTER.
All references in this section are to the Oracle Fusion Middleware 11g Release 1
(11.1.1.2.0) documentation library.
To migrate a custom WebCenter application:
1.
Open the application in Oracle JDeveloper 11.1.1.2.0.
This invokes the migration wizard that automatically migrates your application to
Oracle WebCenter 11.1.1.2.0.
2.
Save the application.
3.
Create a WebLogic Managed Server instance and provision it with a required set of
shared libraries. For information, see the "Creating and Provisioning a WebLogic
Managed Server Instance" section in the Oracle Fusion Middleware Administrator's
Guide for Oracle WebCenter.
4.
Create and register the Metadata Service (MDS) repository for your application on
the WebLogic Domain's Administration Server instance. For information, see the
"Creating and Registering the Metadata Service Repository" section in the Oracle
Fusion Middleware Administrator's Guide for Oracle WebCenter.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-37
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
5.
Deploy the application to a Managed Server. For information, see the "Deploying
the Application to a WebLogic Managed Server Instance" section and the
"Deploying Portlet Producer Applications" section in the Oracle Fusion Middleware
Administrator's Guide for Oracle WebCenter.
Your custom WebCenter applications may have WebCenter Services integrated that
rely on back-end servers. For example, Discussions and Search services rely on Oracle
WebCenter Discussions and Oracle SES, respectively. While installing Oracle Fusion
Middleware 11.1.1.2.0, if you changed the host or port number of your back-end
servers, you must reconfigure the required WebCenter Services to use the new server
configuration. For information about specific services, see the "Managing Services,
Portlet Producers, and External Applications" part in the Oracle Fusion Middleware
Administrator's Guide for Oracle WebCenter.
C.4.3.10 Post Migration Configuration for Oracle Web Services Manager
To migrate Oracle Web Services Manager (WSM), perform the following tasks:
■
Purging the Policy Usage Analysis Information from the Metadata Services
Repository
■
Migrating the Oracle WSM Policies in the MDS Repository
■
Migrating Custom Policy Accessor Properties
Before you can migrate Oracle WSM, you must migrate
components of the security environment, such as the identity store
and key store configurations. For more information, see
Section C.4.3.5, "Post-Migration Configuration for Oracle Platform
Security Services".
Note:
C.4.3.10.1 Purging the Policy Usage Analysis Information from the Metadata Services
Repository In this release, the same Oracle Metadata Services (MDS) repository can be
used to manage policies across multiple domains. In previous releases, an MDS
repository could only be used by a single domain.
If you have analyzed policy usage using the Oracle Fusion Middleware 11g Release 1
(11.1.1.1.0) installation, you will need to purge the policy usage analysis information
from the MDS repository to ensure that accurate usage results are reflected for the
Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0) version.
To purge the policy usage analysis information from the MDS repository, use the
deleteMetadata MDS command as follows:
deleteMetadata(application='wsm-pm',server='server_name',
docs='/policyAttachments/**')
server_name specifies the name of the server on which the Oracle WSM policy
manager is running.
After purging the policy usage analysis information, you must restart the server.
For more information about managing MDS repositories, see "Maintaining the MDS
Repository" section in the Administering Web Services in the Oracle Fusion Middleware
11g Release 1 (11.1.1.2.0) documentation library.
C.4.3.10.2 Migrating the Oracle WSM Policies in the MDS Repository In Oracle WSM 11g
Release 1 (11.1.1), predefined and custom Oracle WSM policies are stored in the Oracle
MDS repository. In this patch set, there are two new predefined policies available:
C-38 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
■
oracle/wss_saml_or_username_token_over_ssl_service_policy
■
oracle/wss11_saml_or_username_token_with_message_protection_service_
policy
You can use Oracle WebLogic Scripting Tool (WLST) commands to upgrade the
repository with the new predefined policies. You can also refresh the repository by
deleting all Oracle WSM policies from the repository, including custom policies, and
then repopulating it using the predefined policies provided in your installation. All of
the policies in the repository are also revalidated when you upgrade the repository.
For more information, see "Upgrading the Oracle WSM Policies in the MDS
Repository" in Administering Web Services in the Oracle Fusion Middleware 11g Release
1 (11.1.1.2.0) documentation library.
C.4.3.10.3 Migrating Custom Policy Accessor Properties If you have customized the policy
accessor properties, you must re-apply the policy manager connection information
once you have migrated your installation. For more information, see "Configuring
Platform Policy Properties" in the Administering Web Services in the Oracle Fusion
Middleware 11g Release 1 (11.1.1.2.0) documentation library.
C.4.4 Installation Process
Table C–3 describes the 11.1.1.2.0 installation process that must be completed during
the migration process.
Table C–3
Scenario
Installation Process
Description and Steps
Installing products in a new Before you can install 11.1.1.2.0 products in a new Middleware
Middleware home
home, ensure that the repository is upgraded and the 11.1.1.1.0
schema is migrated to the 11.1.1.2.0 schema.
To install products, complete the following steps:
1.
Install Oracle WebLogic Server. This step is not required for
Web tier.
2.
Run product-specific Installers to install the new products.
For more information, see the Oracle Fusion Middleware
Installation Planning Guide and the product installation guides in
the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library for the products you are installing and
configuring.
Installing products in a new Before you can install 11.1.1.2.0 products in a new Middleware
Middleware home, on a
home, ensure that the repository is upgraded and the 11.1.1.1.0
second machine, in a
schema is migrated to the 11.1.1.2.0 schema.
Cluster environment
To install products in a Cluster environment, complete the
following steps:
1.
Install Oracle WebLogic Server. This step is not required for
Web tier.
2.
Run product-specific Installers to install the new products.
Ensure that Middleware home on the second machine must
be at the same file path as the first machine.
For more information, see the Oracle Fusion Middleware
Installation Planning Guide and the product installation guides in
the Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
documentation library for the products you are installing and
configuring.
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-39
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.4.5 Configuration Process
Table C–4 describes the 11.1.1.2.0 configuration process that must be completed during
the migration process.
Table C–4
Configuration Process
Scenario
Description and Steps
Configuring Oracle
Instances in a new
Middleware home
Before you can configure Oracle Instances in a new Middleware
home, ensure that the repository is upgraded, the 11.1.1.1.0
schema is migrated to the 11.1.1.2.0 schema, all 11.1.1.2.0
products are installed, and the WebLogic domain is migrated.
To configure Oracle Instances, run the ant
master-patch-oinstance command.
Configuring Oracle
Instances in a new
Middleware home, on a
second machine, in a
Cluster environment
Before you can configure Oracle Instances in a new Middleware
home, ensure that the repository is upgraded, the 11.1.1.1.0
schema is migrated to the 11.1.1.2.0 schema, all 11.1.1.2.0
products are installed in the Cluster environment (on a second
machine), and the WebLogic domain is migrated.
To configure Oracle Instances, run the ant
master-patch-oinstance command.
Configuring products in a
new WebLogic domain
Before you can configure 11.1.1.2.0 products in a new WebLogic
domain, ensure that the repository is upgraded, the 11.1.1.1.0
schema is migrated to the 11.1.1.2.0 schema, and the 11.1.1.2.0
products are installed in a new Middleware home.
To configure products in a new WebLogic domain, complete the
following steps:
C-40 Oracle Fusion Middleware Patching Guide
1.
Start the Oracle Fusion Middleware Configuration Wizard
from your new Middleware home.
2.
Choose product templates to match components on the old
11.1.1.1.0 domain.
3.
For the new domain, choose the same domain name as the
old 11.1.1.1.0 domain.
4.
Configure servers, machines, or clusters to match the old
11.1.1.1.0 topology.
5.
Create domain.
6.
Optional: Start Node Manager.
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–4 (Cont.) Configuration Process
Scenario
Description and Steps
Configuring products in a
new WebLogic domain, on a
second machine, in a
Cluster environment
Before you can configure 11.1.1.2.0 products in a new WebLogic
domain, ensure that the repository is upgraded, the 11.1.1.1.0
schema is migrated to the 11.1.1.2.0 schema, and the 11.1.1.2.0
products are installed in a new Middleware home on a second
machine in the Cluster environment.
To configure products in a new WebLogic domain, complete the
following steps:
1.
Start the Oracle Fusion Middleware Configuration Wizard
from your new Middleware home.
2.
Choose product templates to match components on the old
11.1.1.1.0 domain.
3.
For the new domain, choose the same domain name as the
old 11.1.1.1.0 domain.
4.
Configure servers, machines, or clusters to match the old
11.1.1.1.0 topology.
5.
Create domain.
6.
Optional: Start Node Manager.
7.
Run the pack command on the new domain on the first
machine.
8.
Run the unpack command on the second machine.
C.4.6 Properties in the patchMaster.properties File
Table C–5 describes the properties that you can set in the patchMaster.properties
file. All the properties are not mandatory. For the list of properties that are required for
specific components, see Table C–6.
Note: On Windows, you must use / as the delimiter to specify the
property path. For example:
c:/my/path/file
Table C–5
Patch Master Properties
Properties
Description
patchMaster.Componentlist
List the Fusion Middleware components, you want
to patch from 11.1.1.1.0 to 11.1.1.2.0.
Example:
patchMaster.Componentlist=Audit,BAM,DIP,Disco
verer,Forms,JPS
patchMaster.Schemaurl
Specify the connection string to a single repository
being patched.
Example:
patchMaster.Schemaurl=jdbc:oracle:thin:@local
host:1521:orcl
patchMaster.Schemauser
Specify the system user for the repository specified
by patchMaster.Schemaurl.
Example:
patchMaster.Schemauser=SYS AS SYSDBA
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-41
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–5 (Cont.) Patch Master Properties
Properties
Description
patchMaster.Schemaprefix
Specify the repository schema metadata namespace.
Example:
patchMaster.Schemaprefix=DEV
For Oracle Portal users, if you upgraded your
Oracle Portal 10g to Oracle Portal 11g R1 (11.1.1.1.0),
you must specify the schema prefix as APPSERVER.
For Oracle Internet Directory, you must specify the
schema prefix as ODS.
patchMaster.Mwhomenew
Specify the path where your 11.1.1.2.0 home is
installed.
Example:
patchMaster.Mwhomenew=/scratch/newhome
patchMaster.Mwhomeold
Specify the path where your 11.1.1.1.0 home is
installed.
Example:
patchMaster.Mwhomeold=/scratch/oldhome
patchMaster.Domainhomenew
Specify the Oracle WebLogic Server domain
11.1.1.2.0 home.
Example:
patchMaster.Domainhomenew=/scratch/newhome/us
er_projects/domains/newDomain
patchMaster.Domainapplicationshome
new
Specify the Oracle WebLogic Server domain
applications; 11.1.1.2.0 home.
Example:
patchMaster.Domainapplicationshomenew=/scratc
h/newhome/user_
projects/applications/newDomain
patchMaster.Domainhomeold
Specify the Oracle WebLogic Server domain
11.1.1.1.0 home.
Example:
patchMaster.Domainhomeold=/scratch/oldhome/us
er_projects/domains/oldDomain
patchMaster.Domainusername
Specify the Oracle WebLogic Server domain user
name.
Example:
patchMaster.Domainusername=currentuser
patchMaster.Syspassword
Specify the password for the Oracle Weblogic
domain. This property is not available, by default.
You may add and set this property. If the property is
not present, Patch Assistant prompts you to enter
the password.
Example:
patchMaster.Syspassword=welcome1
patchMaster.Oracleinstancenewlist
List the paths to 11.1.1.2.0 Oracle instances.
Example:
patchMaster.Oracleinstancenewlist=/scratch/ne
winst1,/scratch/newinst2
C-42 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–5 (Cont.) Patch Master Properties
Properties
Description
patchMaster.Oracleinstanceoldlist
List the paths to 11.1.1.1.0), Oracle instances
corresponding to 11.1.1.2.0, Oracle instance paths.
Example:
patchMaster.Oracleinstanceoldlist=/scratch/ol
dinst1,/scratch/oldinst2
patchMaster.Oraclehomenew
Specify the path of 11.1.1.2.0 Oracle home.
Example:
patchMaster.Oraclehomenew=/scratch/myOhomenew
patchMaster.Oraclehomeold
Specify the Path of 11.1.1.1.0 Oracle home.
Example:
patchMaster.Oraclehomeold=/scratch/myOhome
Note: You can patch only one Oracle home at once.
Do not specify multiple Oracle homes in the
properties file for this entry.
patchMaster.Logdir
The default directory where the log file will be
saved.
Example:
patchMaster.Logdir=${patchMaster.Dir}
patchMaster.Loglevel
Specify the logging level to be recorded in the log
file. The default log level is info. The other options
are error, warning, verbose, and debug.
Example:
patchMaster.Loglevel=info
patchMaster.Domainadminhost
This is either the 11.1.1.1.0 or 11.1.1.2.0
Administration Server host depending on the
operation. It is used for starting or stopping domain
and instance registration.
Example:
patchMaster.Domainadminhost=localhost
patchMaster.Domainadminport
This is either the 11.1.1.1.0 or 11.1.1.2.0
Administration Server port depending on the
operation. It is used for starting or stopping domain
and instance registration.
Example:
patchMaster.Domainadminport=7001
See Appendix D, "Sample Patch Master Properties File", for a
sample patchMaster.properties file.
Note:
Product-Specific Properties Required in the patchMaster.properties File
Table C–6 lists the properties required by Oracle Fusion Middleware components in
the patchMaster.properties file.
Patch Assistant validates properties based on operations only.
It does not validate properties at the individual product level.
Note:
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-43
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–6
Properties Required in patchMaster.properties File
Product
Oracle Fusion Middleware Audit
Framework
Oracle Business Intelligence
Discoverer
Oracle Directory Integration
Platform
C-44 Oracle Fusion Middleware Patching Guide
Required Properties
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Componentlist
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Statusfile
■
patchMaster.Failonerror
■
patchMaster.Componentlist
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Domainadminhost
■
patchMaster.Domainadminport
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–6 (Cont.) Properties Required in patchMaster.properties File
Product
Required Properties
Oracle Internet Directory
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Failonerror
■
patchMaster.Componentlist
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Failonerror
■
patchMaster.Componentlist
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Oraclehomenew
Oracle Virtual Directory
Oracle Java Required Files
Oracle Metadata Services
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-45
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–6 (Cont.) Properties Required in patchMaster.properties File
Product
Required Properties
Oracle Platform Security Services
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainapplicationshomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Domainadminhost
■
patchMaster.Domainadminport
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Statusfile
■
patchMaster.Failonerror
■
patchMaster.Componentlist
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Failonerror
Oracle Portal
Oracle Reports
C-46 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–6 (Cont.) Properties Required in patchMaster.properties File
Product
Required Properties
Oracle User Messaging Service
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Statusfile
■
patchMaster.Failonerror
■
patchMaster.Componentlist
■
patchMaster.Mwhomenew
■
patchMaster.Mwhomeold
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Domainusername
■
patchMaster.Oracleinstancenewlist
■
patchMaster.Oracleinstanceoldlist
■
patchMaster.Oraclehomenew
■
patchMaster.Oraclehomeold
■
patchMaster.Componentlist
■
patchMaster.Schemaurl
■
patchMaster.Schemauser
■
patchMaster.Schemaprefix
■
patchMaster.Domainhomeold
■
patchMaster.Domainapplicationshomenew
■
patchMaster.Componentlist
■
patchMaster.Domainhomenew
■
patchMaster.Domainhomeold
■
patchMaster.Logdir
■
patchMaster.Loglevel
■
patchMaster.Statusfile
■
patchMaster.Failonerror
Oracle Web Cache
Oracle WebCenter
Oracle Web Services Manager
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-47
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C.4.6.1 Overriding Properties Set in the patchMaster.properties File
You can use the Ant command-line utility to override the properties set in the
patchMaster.properties file. You must specify the required property on the
command line as follows:
ant -D<property>=<value>
For example, to select components to patch, enter the following command on the
command line:
ant -DpatchMaster.Componentlist=SOA,UMS,WebCenter
master-patch-schema
Note that master-patch-schema, in the above example, is the command that uses the
new values.
Refer to Table C–5 for complete information about properties that you can specify on
the command line or in the patchMaster.properties file.
When you override the patchMaster.Schemauser property to
specify the system user by using the command-line utility, ensure that
you use double quotation marks, as in the following example:
Note:
ant -DpatchMaster.Schemauser="SYS AS SYSDBA"
Do not enter the double quotation marks if you edit the
patchMaster.properties file directly.
C.4.7 Oracle Fusion Middleware Components Supported by Patch Assistant
Table C–7 lists Oracle Fusion Middleware components that are supported by Patch
Assistant.
Table C–7
Oracle Fusion Middleware Components Supported by Patch Assistant
Component Name
Release
Oracle Fusion Middleware Audit Framework
11.1.1.2.0
Oracle BPEL Process Manager
11.1.1.2.0
Oracle Business Rules
11.1.1.2.0
Oracle Business-to-Business Integration
11.1.1.2.0
Oracle Business Activity Monitoring
11.1.1.2.0
Oracle Business Intelligence Discoverer
11.1.1.2.0
Oracle Internet Directory
11.1.1.2.0
Oracle Directory Integration Platform
11.1.1.2.0
Oracle Identity Federation
11.1.1.2.0
Oracle Virtual Directory
11.1.1.2.0
Oracle Directory Services Manager
11.1.1.2.0
Oracle Forms
11.1.1.2.0
Oracle Platform Security Services
11.1.1.2.0
Oracle Java Required Files
11.1.1.2.0
Oracle Metadata Services
11.1.1.2.0
Oracle Access Manager
11.1.1.2.0
C-48 Oracle Fusion Middleware Patching Guide
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
Table C–7 (Cont.) Oracle Fusion Middleware Components Supported by Patch Assistant
Component Name
Release
Oracle TopLink
11.1.1.2.0
Oracle Dynamic Monitoring System (DMS)
11.1.1.2.0
Oracle Java Object Cache
11.1.1.2.0
Oracle Enterprise Manager Fusion Middleware Control
11.1.1.2.0
Oracle HTTP Server
11.1.1.2.0
Oracle Reports
11.1.1.2.0
Oracle Portal
11.1.1.2.0
Oracle Portlet Producers
11.1.1.2.0
Oracle User Messaging Service
11.1.1.2.0
Oracle Web Cache
11.1.1.2.0
Oracle WebCenter Spaces
11.1.1.2.0
Oracle WebCenter Discussions
11.1.1.2.0
Oracle WebCenter Portlets
11.1.1.2.0
Oracle WebCenter Wiki and Blogs
11.1.1.2.0
Oracle Content Server
10.1.3.5.1
Oracle WebLogic Server
10.3.1.0
Oracle Wallet Manager
11.1.1.2.0
Oracle Web Services Manager
11.1.1.2.0
Using Patch Assistant to Migrate from 11g Release 1 (11.1.1.1.0) to Release 1 (11.1.1.2.0) C-49
Migrating to Oracle Fusion Middleware 11g Release 1 (11.1.1.2.0)
C-50 Oracle Fusion Middleware Patching Guide
D
Sample Patch Master Properties File
D
This appendix shows a sample patchMaster.properties file.
[10]
# This is the property file for the 11gR1-11ps1 patchMaster.
# Set values for the properties below to the desired value.
# If a property is not needed, it must be commented out.
# Description: List of components to patch from 11gR1 to 11ps1
# Example:
patchMaster.Componentlist=Audit,BAM,DIP,Discoverer,Discussions,Forms,JPS,JRF,MDS,M
odplsql,OAM,OCServer,ODL,ODSM,OHS,OID,OIF,Opmn,OVD,OWSM,Portal,Portlet,Reports,SOA
,UMS,WebCenter,Webcache,Webservices,Wiki
patchMaster.Componentlist=Audit,BAM,DIP,Discoverer,Discussions,Forms,JPS,JRF,MDS,M
odplsql,OAM,OCServer,ODL,ODSM,OHS,OID,OIF,Opmn,OVD,OWSM,Portal,Portlet,Reports,SOA
,UMS,WebCenter,Webcache,Webservices,Wiki
# Description: Connection string to a single repository being patched.
# Example: patchMaster.Schemaurl=jdbc:oracle:thin:@localhost:1521:orcl
patchMaster.Schemaurl=jdbc:oracle:thin:@<host>:<port>:<sid>
# Description: A system user for the repository specified by patchMaster.Schemaurl
# Example: patchMaster.Schemauser=SYS AS SYSDBA
# patchMaster.Schemauser=<Value Unspecified>
# Description: The optional repository schema metadata namespace.
# Example: patchMaster.Schemaprefix=DEV
# patchMaster.Schemaprefix=<Value Unspecified>
# Description: Fusion Middleware 11ps1 home.
# Example: patchMaster.Mwhomenew=/scratch/newhome
# patchMaster.Mwhomenew=<Value Unspecified>
# Description: Fusion Middleware 11gR1 home.
# Example: patchMaster.Mwhomeold=/scratch/oldhome
# patchMaster.Mwhomeold=<Value Unspecified>
# Description: WLS domain 11ps1 home.
# Example: patchMaster.Domainhomenew=/scratch/newhome/user_
projects/domains/newDomain
# patchMaster.Domainhomenew=<Value Unspecified>
# Description: WLS domain applications 11ps1 home.
# Example: patchMaster.Domainapplicationshomenew=/scratch/newhome/user_
projects/applications/newDomain
# patchMaster.Domainapplicationshomenew=<Value Unspecified>
# Description:
WLS domain 11gR1 home.
Sample Patch Master Properties File
D-1
# Example: patchMaster.Domainhomeold=/scratch/oldhome/user_
projects/domains/oldDomain
# patchMaster.Domainhomeold=<Value Unspecified>
# Description: WLS domain username.
# Example: patchMaster.Domainusername=currentuser
# patchMaster.Domainusername=<Value Unspecified>
# Description: List paths to 11ps1 Oracle instances.
# Example: patchMaster.Oracleinstancenewlist=/scratch/newinst1,/scratch/newinst2
# patchMaster.Oracleinstancenewlist=<Value Unspecified>
# Description: List paths to 11gR1 Oracle instances corresponding to 11ps1 Oracle
instance paths.
# Example: patchMaster.Oracleinstanceoldlist=/scratch/oldinst1,/scratch/oldinst2
# patchMaster.Oracleinstanceoldlist=<Value Unspecified>
# Description: Path to 11ps1 Oracle home.
# Example: patchMaster.Oraclehomenew=/scratch/mynewOhome
# patchMaster.Oraclehomenew=<Value Unspecified>
# Description: Path to 11gR1 Oracle home.
# Example: patchMaster.Oraclehomeold=/scratch/myOhome
# patchMaster.Oraclehomeold=<Value Unspecified>
# Description: Specifies the directory where the log files go if a custom
#
location is desired.
# Example: patchMaster.Logdir=/scratch/patchMasterDir
# patchMaster.Logdir=<Value Unspecified>
# Description: Specifies the logging level to be recorded in the log file
# Values={error|warning|info|verbose|debug} Default=info
patchMaster.Loglevel=info
# Description: WLS domain Adminserver hostname. This is *either* the R1 or PS1
Adminserver host
# depending the operation. Used for start/stop domain and instance registration.
# Example: patchMaster.Domainadminhost=localhost
# patchMaster.Domainadminhost=<Value Unspecified>
# Description: WLS domain Adminserver port number. This is *either* the R1 or PS1
Adminserver port
# depending the operation. Used for start/stop domain and instance registration.
# Example: patchMaster.Domainadminport=7001
# patchMaster.Domainadminport=<Value Unspecified>
D-2 Oracle Fusion Middleware Patching Guide
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising