2Oracle Fusion Middleware Upgrade: Best Practices & Strategy Renga Rengarajan - Oracle Director of Product Management and ArchitectureMichael Rubino – Oracle Senior Director Software Engineering
3The following is intended to outline our general product direction 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.
4Program Agenda Introduction & Strategy Using the Upgrade Assistant Developing an upgrade strategyUsing the Upgrade AssistantUpgrading to the latest 11g patch releaseUpgrading to the 12c release
5TerminologyUpgrade 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: to )PatchingCopies a small number of files over an existing installation.Updating from one patchset release to another patchset (ie: to )MigrationMigration typically involves moving from a third-party (non-Oracle) product to an Oracle product or across hardware platforms.Describe the differences between patching and upgrade. Explain that “Migration” is generally a different process.
6Preservation of Artifacts 12c Upgrade – FeaturesUpgrade ProcedureSimplified upgrade steps with complete automationConsistent steps across all productsAggregate handling – upgrading domain as a wholeUser ExperienceNo need for parallel infrastructure – “in-place” upgradeSeparation of installation from upgradeSeparation of mid-tier upgrade from schema upgradeError recovery – re-runnable (idempotent) upgrade operationsPreservation of ArtifactsComplete preservation of user deployed artifacts – no redeploymentComplete preservation of transactions and state information – no data lossCompatibilityComplete public API backward compatibilityComplete binary compatibility – no need to recompile
7Developing an Upgrade Strategy Familiarize yourself with the Oracle Upgrade documentation.Consider compatibility and interoperability requirementsReview the valid upgrade starting pointsIdentify the tools needed for upgradeUnderstand the differences between source and target topologies (ie:FMW11g, FMW 12c)Develop a backup planRemind audience that a successful upgrade depends on having a sound upgrade plan and strategy. Remind that a dry or test run is always part of good practice
8Upgrade Documentation Library Explain how the 12c upgrade documentation library has been restructured. Highlight the new books and explain how they are meant to be used. Explain that there are product specific books
9Consider Compatibility & Interoperability Requirements Collect the release and version numbers for installed productsCheck the “Supported Configurations” matrix (Available on Oracle Technology Network)Understand which components installed in your deployment will be upgradedDecide when components will be upgradedCheck that any dependent databases are supported by the FMW release you are upgrading to. Upgrade underlying DB’s first.A possible method to determine if there will be compatibility and interop issues
10Upgrade 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 ( )Oracle Fusion Middleware 11g Release 1 ( )WLS Domain Upgrade Starting PointYour WLS domain must be at least versionHTTP Server Upgrade Starting PointYou can upgrade your Oracle HTTP Server 11g ( , )Explain what an upgrade starting point is. Explain the valid 11gstarting points available for a 12c upgrade. Explain that you must first upgrade to one of these valid starting points if at a previous version
11Tools Used During the Upgrade Process Oracle Universal Installer (OUI) – The upgrade process begins by installing a new 12c product setRepository Creation Utility (RCU) – Use this tool to create schemas in your database. Certain schemas may need to be created before attempting an upgradeOracle FMW Upgrade Assistant (UA) - Use this tool to upgrade your supported 11g schemas and WebLogic domain component configurationsOracle Reconfiguration Wizard - Use this tool to reconfigure the domain when upgrading WLS
12Key Differences Between 11g & FMW 12c OPMN is no longer used in Oracle Fusion Middleware, replaced by Node ManagerRedefinition of the Oracle home and elimination of the Middleware homeOracle Web Cache is no longer part of Oracle Fusion MiddlewareOPMN - OPMN is no longer used in Oracle Fusion Middleware. system components are managed by the WebLogic Management Framework.MW Home – This term is no longer used. It is replaced by Oracle Home, and the OH contains product directories. The term “instance” and “farm” are no longer part of the 12c vocabulary
13Develop a Backup PlanConsider backing up your freshly installed 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 directoriesLocal Domain home directory, your local Oracle instances, and remote Domain home and Oracle instancesSchema UpgradesOften the underlying database must be upgraded first. Always backup the DB before upgrading the schemas.Explain that an upgrade process starts by installing a new oracle home. Recommend that this should be backed up before an upgrade, as a restore can be quicker than a new install, should something go wrong.
14Program Agenda Introduction & Strategy Using the Upgrade Assistant Developing an upgrade strategyUsing the Upgrade AssistantUpgrading to the latest 11g patch releaseUpgrading to the 12c release
15Tools For Patching and 11g Patchset Updates DescriptionOPATCHOpatch copies a small collection of files over your existing installationWebLogic Server Upgrade InstallerUpdates your existing Oracle WebLogic Server installation to the latest available versionPatch Set InstallerUpdates an existing product to the latest version. (ie: update to )Patch Set AssistantUpdates database schemas to prepare them for use with the latest version of Oracle Fusion Middleware software.Explain that the UA is used to upgrade from 10g to the latest 11g patch release.Explain that the PSA is used to upgrade to the latest 11g release, from a prior 11g patch release.Explain that these two tools are combined into one for 12c
1611gR1 Patchset Updates General Process Shut-down servers Update of the 11gR1 installation through patchset installersPerform in-place update of schemas through Patch Set AssistantStart-up serversNoteNo requirement to rebuild custom binaries (SOA composites, ADF applications, etc…)Best effort to minimize schema updatesBest effort to minimize manual updates at the domain level
18Program Agenda Introduction & Strategy Using the Upgrade Assistant Developing an upgrade strategyUsing the Upgrade AssistantUpgrading to the latest 11g patch releaseUpgrading to the 12c release
19Tools For Upgrading to 12c DescriptionOracle Universal InstallerUsed to install 12c Fusion Middleware Productsincluding WebLogic ServerRepository Creation Utility (RCU)Used to create schemas in the database. Certain schemas may need to be created before attempting an upgradeUpgrade Assistant (UA)Updates database schemas as well as Fusion Middleware component configurationReconfig WizardUpdates the WebLogic Server domain configuration for the latest release
2012c Upgrade – High Level Flow PrepareStop all 11g serversTake a complete backup of 11g environmentPre-upgradeInstall 12c products into a new Oracle HomeCreate any new schemas – RCUUpgradeUpgrade Schemas – Upgrade AssistantReconfigure domain – Reconfig WizardStart Admin ServerUpgrade Config – Upgrade AssistantPost-upgradePropagate upgraded domain config to other nodes – Pack/UnpackStart the upgraded servers
2112c Upgrade – “In-place” and “out-of-place” Binary installation is out-of-placeAs 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 systemConfig upgrades, including the domain, are upgraded in-placeCreation 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 flowNote: If desired, an “out-of-place” upgrade may be accomplished by creating a comparable target destination, and running an upgrade in that environment
22FMW 12c Upgrade Assistant FMW Upgrade Assistant redesigned for releaseComplete separation of installation from upgradeComplete separation of mid-tier upgrade from schema upgradeTwo-phase upgrades through examination phaseSimplify – Combine UA & PSA into single toolFull GUI support for upgrading & patchingHighlight upgrade dependenciesChoosing SOA, highlights need for dependent MDS upgradeAbility to upgrade more than one schema at a timeUpgrade Assistant supports Edition Based Redefinition (EBR) for FMW DB schemas to provide high availability upgrade of FMW components.
23Upgrade CandidatesThe UA provides a list of components that are candidates for upgradeRun the UA from the oracle_common/upgrade/bin directory of your FMW 12c (12.1.2) installationFor 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.
25Schema 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: ./uaUA will provide a list of all schemas available for upgradeChoose one or more schemasRemind users that they must run domain reconfiguration AFTER running the UA to upgrade schemas
26Component Configuration Upgrade Weblogic Component ConfigurationThis option is available when the UA is run from an Oracle home that contains managed WebLogic domain componentsEnter credentials for the domain you want to upgradeIn release use this option to upgrade:Oracle HTTP ServerOracle Web Services ManagerAll candidates are upgraded when performing a configuration upgradeRemind users that they must first reconfigure the domain BEFORE running the UA again
27Standalone System Component Upgrade Standalone ComponentsThis 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 11gOHS, for example, may be configured to run standaloneExplain when you would choose “Create a New Domain” vs “Update Existing”, ie: First time through, you must create a domain for the standalone systems to be associated. Explain that this is notA true WLS domain.
28Standalone System Component Upgrade (2) Node ManagerIn addition to creating a domain, you must create a new node managerSpecify the credentials for the node manager to be created
29Examining Components Examine Phase The UA examines and verifies that components are ready for upgrade.You should ensure all components are ready for upgrade before proceedingExamine is a “read-only” operation. No changes are made to the source or targetExplain the purpose of the examine phase, and the concept/benefits of a 2 phase upgrade. Users should understand the value of correcting an error now, before proceeding with an upgrade.There are 5 status states from examine (succeeded, failed, pending, in-progress, not-needed)
30Upgrading Components Performing the upgrade Review the “Upgrade Summary” screen carefully, ensuring the correct components and options are selectedSelect the “Save Response File” option to create a response file for later useClick “Upgrade” to start the processTalk about response files, and running the UA in “batch mode” at a later time. Response files can be created and edited.Emphasize that nothing happens until the upgrade button is pressed, but once pressed, the upgrade has begun and restoration from backup may be needed in the event of an error/failure
31Silent Upgrades With Response Files Using UA Response filesResponse 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)
32Post Upgrade Steps & Verification Completing the upgradeEnsure all components were successfully upgradedCheck the documentation to see if any post upgrade manual operations are requiredVerify that the upgraded environment functions as expected