1 / 35

Oracle Fusion Middleware Upgrade: Best Practices & Strategy

Oracle Fusion Middleware Upgrade: Best Practices & Strategy. Renga Rengarajan - Oracle Director of Product Management and Architecture Michael Rubino – Oracle Senior Director Software Engineering.

kesia
Télécharger la présentation

Oracle Fusion Middleware Upgrade: Best Practices & Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Oracle Fusion Middleware Upgrade: Best Practices & Strategy RengaRengarajan- Oracle Director of Product Management and Architecture Michael Rubino– Oracle Senior Director Software Engineering

  2. 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. Program Agenda • Introduction & Strategy • Developing an upgrade strategy • Using the Upgrade Assistant • Upgrading to the latest 11g patch release • Upgrading to the 12c release

  4. 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.

  5. 12c Upgrade – Features

  6. Developing an Upgrade Strategy • Familiarize yourself with the Oracle Upgrade documentation. • Consider compatibility and interoperability requirements • Review the valid upgrade starting points • Identify the tools needed for upgrade • Understand the differences between source and target topologies (ie:FMW11g, FMW 12c) • Develop a backup plan

  7. Upgrade Documentation Library

  8. Consider Compatibility & Interoperability Requirements • Collect the release and version numbers for installed products • Check the “Supported Configurations” matrix (Available on Oracle Technology Network) • Understand which components installed in your deployment will be upgraded • 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.

  9. Upgrade Starting Points • You can upgrade to Oracle Fusion Middleware Release 12c (12.1.2) from the following previous versions of Oracle Fusion Middleware 11g: • 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)

  10. 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 11g schemas and WebLogic domain component configurations • Oracle Reconfiguration Wizard - Use this tool to reconfigure the domain when upgrading WLS

  11. Key Differences Between 11g & FMW 12c • OPMN is no longer used in Oracle Fusion Middleware, replaced by Node Manager • Redefinition of the Oracle home and elimination of the Middleware home • Oracle Web Cache is no longer part of Oracle Fusion Middleware

  12. Develop a Backup Plan • Consider backing up your freshly installed 12.1.2 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.

  13. Program Agenda • Introduction & Strategy • Developing an upgrade strategy • Using the Upgrade Assistant • Upgrading to the latest 11g patch release • Upgrading to the 12c release

  14. Tools For Patching and 11g Patchset Updates

  15. 11gR1 Patchset Updates • General Process • Shut-down servers • 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 • Best effort to minimize manual updates at the domain level

  16. Oracle SOA Suite 11g Patchset Update 1 5 3 2 4

  17. Program Agenda • Introduction & Strategy • Developing an upgrade strategy • Using the Upgrade Assistant • Upgrading to the latest 11g patch release • Upgrading to the 12c release

  18. Tools For Upgrading to 12c

  19. 12c Upgrade – High Level Flow

  20. 12c Upgrade – “In-place” and “out-of-place” • Binary installation is out-of-place • As in previous releases, schema upgrades are either in-place or out-of-place, depending on the schema being upgraded – this is automatically determined by the system • Config 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

  21. FMW 12c Upgrade Assistant • FMW Upgrade Assistant redesigned for 12.1.2 release • 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.

  22. 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 (12.1.2) installation • 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, and connects to the WebLogic Administration Server to determine the list of components that are configured and candidates for upgrade.

  23. 12c Upgrade – Directory Structure Oracle Home SOA Product Home Oracle Common ODI Product Home UA Binaries SOA Binaries ODI Binaries $OH/upgrade/bin directory SOA UA Plugin ODI UA Plugin $OH/plugins/upgrade/ Point Infrastructure UA Plugins $OH/plugins/upgrade/ UA Descriptor files $OH/plugins/upgrade/ UA Descriptor files UA Descriptor files $OH/plugins/upgrade/ UA Descriptor files

  24. Schema Upgrade • Schema Selection • 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

  25. Component Configuration Upgrade • Weblogic Component Configuration • This option is available when the UA is run from an Oracle home that contains managed WebLogic domain components • Enter credentials for the domain you want to upgrade • In release 12.1.2 use this option to upgrade: • Oracle HTTP Server • Oracle Web Services Manager • All candidates are upgraded when performing a configuration upgrade

  26. Standalone System Component Upgrade • Standalone Components • 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

  27. Standalone System Component Upgrade (2) • Node Manager • In addition to creating a domain, you must create a new node manager • Specify the credentials for the node manager to be created

  28. Examining Components • Examine Phase • 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

  29. Upgrading Components • Performing the upgrade • 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

  30. Silent Upgrades With Response Files • Using UA Response files • 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)

  31. Post Upgrade Steps & Verification • Completing the upgrade • 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

  32. Graphic Section Divider

More Related