1. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Fusion Middleware Upgrade: Best Practices & Strategy Renga Rengarajan - Oracle Director of Product Management and Architecture Michael Rubino – Oracle Senior Director Software Engineering September 30, 2014

2. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Safe Harbor Statement The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.

3. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Program Agenda Introduction & Strategy - Developing an upgrade strategy Upgrading to the latest 11g patch release Upgrading to the 12c release 1 2 3

4. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Before we get started… Who is using Fusion Middleware 11g?Who is using Fusion Middleware 12c?What products are you using? SOA, WebCenter, Business Intelligence, Forms, Reports, Portal?

5. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Terminology Upgrade – Moving from a previous major version to a new major version, (ie: 11g to 12c) OR a minor version to a new minor version (ie: 12.1.2 to 12.1.3) Patching – Copies a small number of files over an existing installation. – Updating from one patchset release to another patchset (ie: 11.1.1.4.0 to 11.1.1.5.0) Migration – Migration typically involves moving from a third-party (non-Oracle) product to an Oracle product or across hardware platforms.

6. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 12c Upgrade – Features

7. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Developing an Upgrade Strategy 1.Familiarize yourself with the Oracle Upgrade documentation. 2.Consider compatibility and interoperability requirements 3.Review the valid upgrade starting points 4.Identify the tools needed for upgrade 5.Understand the differences between source and target topologies (ie:FMW11g, FMW 12c) 6.Develop a backup plan And finally…. ….try the upgrade on a cloned production environment before an actual upgrade!

8. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Documentation Library

9. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Documentation Library

10. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Documentation Library On Oracle Technology Network (OTN) – http://www.oracle.com/technetwork – Select Support – Select Product Documentation – Scroll to Fusion Middleware – Select Current Releases of Fusion Middleware Documentation

11. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Consider Compatibility & Interoperability Requirements  Collect the release and version numbers for installed products  Check the “Supported Configurations” matrix (Available on Oracle Technology Network)Oracle Technology Network  Understand which components installed in your deployment will be upgraded  Not all the Oracle Fusion Middleware 11g products are available in Oracle Fusion Middleware 12c (12.1.3)  Decide when components will be upgraded  Check that any dependent databases are supported by the FMW release you are upgrading to. Upgrade underlying DB’s first. Currently (12.1.0.1+, 11.1.0.7+,11.2.0.3+)

12. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Starting Points You can upgrade to Oracle Fusion Middleware Release 12c (12.1.3) from the following previous versions of Oracle Fusion Middleware – Oracle Fusion Middleware 12c Release 2 (12.1.2) – Oracle Fusion Middleware 11g Release 1 (11.1.1.7.0) – Oracle Fusion Middleware 11g Release 1 (11.1.1.6.0) WLS Domain Upgrade Starting Point – Your WLS domain must be at least version 10.3.5 HTTP Server Upgrade Starting Point – You can upgrade your Oracle HTTP Server 11g (11.1.1.6.0, 11.1.1.7.0, 12.1.2)

13. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Tools Used During the Upgrade Process Oracle Universal Installer (OUI) – The upgrade process begins by installing a new 12c product set Repository Creation Utility (RCU) – Use this tool to create schemas in your database. Certain schemas may need to be created before attempting an upgrade Oracle FMW Upgrade Assistant (UA) - Use this tool to upgrade your supported schemas and WebLogic domain component configurations Oracle Reconfiguration Wizard - Use this tool to reconfigure the domain when upgrading WLS

14. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Key Differences Between 11g & FMW 12c  Redefinition of the Oracle home and elimination of the Middleware home – One OH for all FMW products on a host. (Binaries, libraries, oracle common & product directories)  OPMN is no longer used in Oracle Fusion Middleware, replaced by Node Manager – Node Manager is a utility that allows you to perform common operations for a Managed Server  Oracle Web Cache is no longer part of Oracle Fusion Middleware  Review the “Understanding Oracle Fusion Middleware Concepts” guide for more information

15. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Develop a Backup Plan Consider backing up your freshly installed 12.1.3 Oracle home directory and any other created artifacts. After stopping the 11g* servers and processes, back up your 11g environment, including…. – Middleware Oracle home directory, including the Oracle product home directories – Local Domain home directory, your local Oracle instances, and remote Domain home and Oracle instances Schema Upgrades – Often the underlying database must be upgraded first. Always backup the DB before upgrading the schemas. Post Upgrade Backup – Consider a backup immediately following upgrade so that you can restore to a newly upgraded state, if ever needed *or 12.1.2 servers, if upgrading from release 12

16. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Program Agenda Introduction & Strategy - Developing an upgrade strategy Upgrading to the latest 11g patch release Upgrading to the 12c release 1 2 3

17. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Patching Terminology Use OPATCH for… – Interim Patch – For customers who can’t wait for the next scheduled patch of release (Old terms: MLR, One-Off, Hotfix….) – Bundled Patch – A collection of fixes used between patch sets (Old terms: Service pack, Cumulative patch, MLR) – Security Patch Update – One or more security specific fixes released quarterly (Old terms: Critical Patch Update, CPU) – Patch Set Update – One or more fixes specifically for Weblogic Server, released quarterly Patch Sets – A patch set contains a large number of merged patches, changes the version of the product it is applied to, and may introduce new functionality.

18. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Tools For Patching and 11g Patchset Updates ToolDescription OPATCHOpatch copies a small collection of files over your existing installation WebLogic Server Upgrade InstallerUpdates your existing Oracle WebLogic Server installation to the latest available version Patch Set InstallerUpdates an existing product to the latest version. (ie: update to 11.1.1.7.0) Patch Set AssistantUpdates database schemas to prepare them for use with the latest version of Oracle Fusion Middleware software.

19. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 11gR1 Patchset Updates (ie: Release 11.1.1.7.0) General Process – Shut-down servers – Backup ( Database, Middleware home directory, local Domain home directory, & remote domain home and instances) – Update of the 11gR1 installation through patchset installers – Perform in-place update of schemas through Patch Set Assistant – Start-up servers Note – No requirement to rebuild custom binaries (SOA composites, ADF applications, etc…) – Best effort to minimize schema updates & manual updates at the domain level

20. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle SOA Suite 11g Patchset Update 1 2 3 4 5

21. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Which Schemas Need to be Updated? Refer to the patching guide for the release you are upgrading to – Ie: Oracle® Fusion Middleware Patching Guide 11g Release 1 (11.1.1.7.0) – Locate the table “ Schemas That Require Updating for the Latest Release” – If a schema is not listed in the table, no upgrade is needed – Be sure to update any listed schema, and dependent schema that you might have installed in your enterprise

22. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Program Agenda Introduction & Strategy - Developing an upgrade strategy Upgrading to the latest 11g patch release Upgrading to the 12c release 1 2 3

23. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 12c Upgrade – High Level Flow

24. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | FMW 12c Upgrade Assistant FMW Upgrade Assistant redesigned for Release 12c – Complete separation of installation from upgrade – Complete separation of mid-tier upgrade from schema upgrade – Two-phase upgrades through examination phase – Simplify – Combine UA & PSA into single tool Full GUI support for upgrading & patching – Highlight upgrade dependencies Choosing SOA, highlights need for dependent MDS upgrade – Ability to upgrade more than one schema at a time – Upgrade Assistant supports Edition Based Redefinition (EBR) for FMW DB schemas to provide high availability upgrade of FMW components.

25. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 12c Upgrade – “In-place” and “out-of-place” Binary installation is out-of-place Schema upgrades are in-place Standalone System component config upgrades from 11g to 12c are out- of-place – Upgrade copies 11g source configuration to the 12c domain JEE component configuration upgrades, including the domain, are upgraded in-place – Creation of a parallel destination configuration (domain, system components, etc… is no longer required) – Existing domains can be reconfigured as part of the in-place upgrade flow Note: If desired, an “out-of-place” upgrade may be accomplished by creating a comparable target destination, and running an upgrade in that environment

26. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Candidates The UA provides a list of components that are candidates for upgrade Run the UA from the oracle_common/upgrade/bin directory of your FMW 12c installation where the admin server is installed – For schema upgrade: The UA examines install directories and identifies all possible candidate schemas to be upgraded. When a schema is chosen, any dependent schema will also be selected – For component configuration upgrades: The UA prompts for the domain directory for the domain to be upgraded

27. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | 12c Upgrade – Directory Structure Oracle Home ODI Product Home SOA Product Home Oracle Common UA Binaries Point SOA Binaries SOA UA Plugin ODI Binaries ODI UA Plugin UA Descriptor files $OH/upgrade/bin directory $OH/plugins/upgrade/ UA Descriptor files UA Descriptor files Infrastructure UA Plugins UA Descriptor files $OH/plugins/upgrade/

28. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Upgrade Assistant will be installed into the oracle_common area of the FMW home in the oracle_common/upgrade/bin directory. On Unix, start the UA by typing:./ua UA will provide a list of all schemas available for upgrade Choose one or more schemas Schema Selection Schema Upgrade

29. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | This option is available when the UA is run from an Oracle home that contains managed WebLogic domain components Enter the domain directory In release 12 use this option to upgrade: – Oracle HTTP Server – Oracle Web Services Manager – Oracle Data Integration – And others… All candidates are upgraded when performing a configuration upgrade Weblogic Component Configuration Component Configuration Upgrade

30. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | This option is available if running the UA from an Oracle home that contains standalone system components. Standalone components are not associated with a managed WebLogic domain in 11g OHS, for example, may be configured to run standalone Standalone Components Standalone System Component Upgrade

31. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | In addition to creating a domain, you must create a new node manager Specify the credentials for the node manager to be created Node Manager Standalone System Component Upgrade (2)

32. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | The UA examines and verifies that components are ready for upgrade. You should ensure all components are ready for upgrade before proceeding Examine is a “read-only” operation. No changes are made to the source or target Examine Phase Examining Components

33. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Review the “Upgrade Summary” screen carefully, ensuring the correct components and options are selected Select the “Save Response File” option to create a response file for later use Click “Upgrade” to start the process Performing the upgrade Upgrading Components

34. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Response files collect all the information entered through the UA GUI, and can perform them later -response (specifies response file name) -examine (Optionally perform examine phase only) -loglevel, –logdir (Optional logging parameters to specifiy level of log detail and directory) Using UA Response files Silent Upgrades With Response Files

35. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Ensure all components were successfully upgraded Check the documentation to see if any post upgrade manual operations are required Verify that the upgraded environment functions as expected Completing the upgrade Post Upgrade Steps & Verification

36. Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Looking ahead…..