Upgrading to Oracle SOA Suite 12c: Tips and Best Practices

Upgrading to Oracle SOA Suite 12c: Tips and Best Practices

Session: CON7349

David Shaffer, Managing Partner, Middleworks

Jay Kasi, Product Manager, Oracle

Sireesha Beeram, Sr SOA Developer, IEEE

Faisal Farooqui, Lead Software Architect, MultiPlan Inc

SOA SUITE 12C UPGRADE

David Shaffer

Managing Partner, Middleworks

[email protected]

We make middleware work for you | www.middleworks.com

• Many new capabilities:

– Integration Debugger in JDev

– SCA/BPEL & Service Bus

converged design-time / arch

– API Management

– Stream Explorer

– Cloud Adapters

– Mobile

– MFT for file integration

– SOA for Healthcare

– Much richer purge support and

OOB performance tuning

3

Why Upgrade? (Besides support policies…)

– SOA Cloud Service (SOACS)

– Enterprise Scheduler

– Real-Time Integration Business

Insight (option)

– New SAP, Peoplesoft, JDE, Siebel

adapters (non-OEM)

– 12.2.1: Continuous Availability,

Circuit Breaker, in-memory SOA

options, XSLT debugger

– Maven support, REST/JSON

– Based on Java 8

– Significant EM performance

enhancementsCopyright © 2016, Middleworks. All rights reserved.

Agenda

1

2

Useful docs / content

12c Upgrade Basics

Upgrade Best Practices

4

3

12c Base Upgrade Docs and Presos

• Previous SOA Expert Series upgrade webinar:www.middleworks.com/soa-expert/#12cUpgradeWebinar

• SOA Suite 12.2.1 Upgrade doc: http://docs.oracle.com/middleware/1221/core/FUPSS(tip: can get to a single PDF of doc at

http://docs.oracle.com/middleware/1221/core/FUPSS.pdf)

• Upgrade videos: http://docs.oracle.com/middleware/1221/cross/upgrade_videos.htm

5Copyright © 2016, Middleworks. All rights reserved.

Other Useful Upgrade Content

• Support Knowledgebase Documents 1958724.1 & 2084555.1

• Best practices upgrade blogs from Oracle: blogs.oracle.com/SOA/entry/comparison_of_inplace_and_side

blogs.oracle.com/SOA/entry/soa_suite_12c_topology_suggestions

blogs.oracle.com/SOA/entry/best_practices_for_soa_11g

blogs.oracle.com/SOA/entry/soa_suite_12c_upgrade_updatesoa

• Many other blogs available, e.g.: blogs.oracle.com/soacommunity/entry/upgrading_oracle_soa_suite_from

mp3muncher.wordpress.com/2015/07/10/from-aia-to-soa-suite-12c/

etc…


Surveys: 12c Upgrade and Feedback

• When you upgrade or prepare to upgrade, please fill out:

– www.surveymonkey.com/r/soa-12c-upgrade

• Some interesting trends from responses so far:

– Most people do side-by-side upgrade, go straight to 12.2.1

– Some challenges around configurations for upgrade (probably a

side effect of above…) and SRs for earliest adopters

– Easiest things are code migration and new install for side-by-side

– Most common components to upgrade SCA/BPEL, Service Bus

and OWSM, followed by Rules and BAM, smattering of B2B/other


Agenda

1

2


12c Upgrade Basics


8

3

Copyright © 2014 Oracle and/or its affiliates. All rights reserved. |

SOA Suite 11g -> 12c Upgrade Basics

• Great doc at http://www.middleworks.com/soaexpert/upgrade/4.Danilo-12cUpgradeTips.pdf

(excerpted here)

• Choose in-place domain upgrade and re-configuration or side-by-side upgrade with new install / config / deploy

• Can upgrade to 12.1.3 or straight to 12.2.1.x (recommend latter)

• Prerequisites:

– Starting point: SOA Suite 11.1.1.6, 11.1.1.7 or 11.1.1.9 or 12.1.3

– 64-bit OS and JVM – must be supported version

– Dehydration store DB must be supported version – 11g or 12c

– OPSS 12c must use DB or LDAP based policy store

9


• In-Place Upgrade

– Install SOA Suite 12c software in a new

Oracle Home

– Upgrade domain and DB in-place

– Rewire domain to new Oracle Home

– No need to redeploy composites

– See support note 2084555.1 if you have AIA

• Side by Side Upgrade

– Install SOA Suite 12c software in a new Oracle Home.

– Create new DB schemas

– Create new domain

– Configure domain and DB from scratch

– Deploy all composites

– Switch clients/load balancer to new domain

10

Options for Upgrade


Upgrade Options Comparison

In Place

Less Work Keeps History

Keeps Running Processes

Side by Side

Less Downtime

Lower Risk

All Components

(BAM)

Allows Topology Change

Oracle Confidential – Internal/Restricted/Highly Restricted 11

Used most often when you have

long-lived processesTypically preferred otherwise

© OPITZ CONSULTING GmbH 2016 Slide 1212c Upgrade Experience

Upgrade Process | Step-by-Step Overview

1. Understand the upgrade process

2. Define a To-Be Topology

3. Decide on an upgrade strategy that fits to your requirements

4. Pre-Upgrade Tasks

5. Install 12c Software

6. Create or upgrade schemas

7. Domain (Re-) Configuration

8. Upgrade the projects (and deploy if needed)

9. Post Upgrade Steps

10. Verify Upgrade Results (Test)

PREPARATION

INFRASTRUCTU

RE SETUP

CODE UPGRADE


Upgrade Process | Step-by-Step – Preparation

1. Understand the upgrade process

� Understand upgrade concepts

� Understand the Basic 12c Upgrade Tasks

� Understand the SOA Cluster Upgrade Topology

� Understand the Oracle Service Bus Upgrade to 12c

� Understand an Upgrade to Business Activity Monitoring in 12c

� Understand SOA Domain Upgrade Restrictions

2. Define a To-Be Topology

� Understand new and changed features of 12c (12.2.1)

� Understand an Enterprise Deployment

� Decide on components (e.g. SOA, OSB, BAM, etc.)

� Shared Weblogic Domain (for OSB / SOA / BAM) vs. separate Weblogic Domains

� Non Cluster vs. Cluster


Upgrade Process | Step-by-Step – Preparation (2)

3. Select an upgrade strategy that fits your requirements

� In-Place Upgrade

� Schemas and domain directory upgrades are performed "in place" (updates existing 11g files)

� Oracle Home binaries are upgraded "out of place" (binaries are installed in a new directory)

� No need to redeploy composites after upgrade

� Suitable for long running instances which should resume after upgrade

� Side-by-Side Upgrade

� New installation of schemas and domains

� New deployment & configuration of the existing 11g projects

� Suitable in stateless & short-running scenarios

� Appropriate if the targeted sytem architecture should be diferent than with 11g or if the current topology is not

supported


Upgrade Process | Step-by-Step - Infrastructure

4. Pre-Upgrade Tasks� Complete all applicable tasks from the Pre-Upgrade Checklist

� Check if your To-Be Topology is supported

� Perform General Pre-Upgrade Tasks

� Perform the SOA-Specific Pre-Upgrade Tasks

� Perform the Pre-Upgrade Tasks for Oracle BAM

� Perform the Pre-Upgrade Tasks for Oracle Service Bus (OSB)

� Validate your starting point which has to be 11.1.1.6 (PS5) or 11.1.1.7 (PS6)

� Calculate system requirements (Memory, Disk Space, Network, OS)

� Make a complete backup of your existing environment

� Make sure that DB, OS and JVM are supported and apply recommended database parameters on the new

installation

� Save copies of customized start scripts, configuration files, policies

� More details: Upgrade Planning Guide and Interoperability and Compatibility Guide


Upgrade Process | Step-by-Step - Infrastructure (2)

5. Install 12c Software

� Download the Oracle Fusion Middleware Infrastructure distribution from the Oracle ADF download page on

OTN or from the Oracle Software Delivery Cloud

� Download the production distribution for Oracle SOA Suite and Business Process Management from the Oracle

Software Delivery Cloud

� Download the production distribution for Oracle Service Bus from the Oracle Software Delivery Cloud

� Roadmap for Installing and Configuring the Standard Installation Topologies

� Verify the Installation Checklist

� Install Infrastructure distribution and the appropriate components

� Verify the Installation

� For a development or evaluation distribution, see "Downloading Oracle Fusion Middleware 12c (12.2.1)

Development Distributions“


Upgrade Process | Step-by-Step - Infrastructure (3)

6. Database Schemas

� Create the required Database Schemas

� Preparing to Upgrade SOA Schemas (In-Place Upgrade only)

� Upgrade Schemas with the Upgrade Assistant (In-Place Upgrade only)

7. Domain (Re-) Configuration

� Configure the Domain (Side-by-Side Upgrade)

� Reconfigure the Domain using the Reconfiguration Wizard (In-Place Upgrade)

� Upgrade the Domain Component Configurations using the Upgrade Assistant (In-Place Upgrade)


Upgrade Process | Step-by-Step - Code Upgrade

8. Upgrade the projects (and deploy if needed)� Open projects in JDeveloper 12c, the Migration Assistent migrates the project files

� or Upgrade JDeveloper Projects in Bulk

� Migrate Oracle Service Bus Resources from Previous Releases

� Deploy Applications (Side-by-Side Upgrade)

9. Post Upgrade Steps� General Post-Upgrade Tasks

� Post-Upgrade Tasks for Oracle Service Bus

� Post-Upgrade Tasks for Clusters

� Post-Upgrade Tasks for BAM


Upgrade Process | Step-by-Step - Code Upgrade

10. Verify your results (Test)� Testing before and after the upgrade is the key to success!

� Define and document all testcases in advance

� Make sure that you have a complete test approach in place bevore you start your upgrade

� Esablish a test approach that covers all relevant test layers (Elementary Unit Tests, Component Tests, End-to-End Tests)

� Be aware of SOA Composite test framework: http://www.oracle.com/pls/topic/lookup?ctx=fmw122110&id=SOASE1263

� We decided to build our own OC testing framework based on JUnit Standard and SOA Suite APIs to integrate it within

other implementations and to establish a proper test-driven development

� This allows us to

� use the same test approach for BPEL, BPMN, OSB, Java, Human Tasks, XSLT and XQuery…

� re-route external references to a mock service implemented in the same framework (in Java) including changing

references to standard web services so that database or file adapters can also be mocked

� Human task handling (finishing the human task with a predefined outcome and predefined values)

� Smooth integration into continuous integration environment

� More details are available at http://thecattlecrew.net

Agenda

1

2


12c Upgrade Basics


20

3

Upgrade Suggestions

• If upgrading now, go to 12.2.1.1 – Many compatibility fixes to allow

XSLTs to upgrade without change. Need following two properties set

at startup to turn on backward compatibility mode:-Doracle.xdkjava.compatibility.version=11.1.1

-Doracle.soa.compatibility.version=11.1.1

• Perform pre-analysis for upgrade areas of complexity:

– Do you use custom DB scripts for purge, partitioning, etc? (will

have to be re-mapped to 12 – mostly don’t need…)

– Custom code using SOA locator APIs

– Do you have significant performance tuning in 11g? (re-do

performance tuning exercise with 12c)



A Few Component-Specific Comments

• Instance Data Upgrade

– UA upgrades active instances to continue execution in 12c

– Purge strongly recommended prior to upgrade

– Stale instances not upgraded, completed instances can be upgraded during upgrade or later, during downtime

• Service Bus 12c Upgrade

– Export project before upgrade and import after upgrade

– Migration from Eclipse to JDeveloper happens with Import/Export – prepare for this change

• BAM 12c Upgrade

– Major architecture changes in 12c – Data Objects migrated but not dashboards/alerts

– Can either create new dashboards and alerts in 12c or keep 11g BAM dashboards running and connect to it via supported interop between BAM 11g �� SOA 12c

22


• Need to export and delete all Service Bus metadata before upgrade and import after upgrade

• Need to deploy OWSM before upgrade

• Need to use OWSM policies instead of WLS WS-Security policies

– WLS policies in wsdl in 11g

• Need to use OWSM auth policies instead of Xacml

– Xacml policies visible in 11g console

• Run time may work without changes, but not design time

Benefits:

– Integrated JDeveloper experience after upgrade

– Oracle standard ADF UI for console after upgrade

– FMWControl like other Oracle products to manage

– Service Bus included in JDev integrated server for easier development

23

Service Bus manual steps for In-Place Upgrade


Side by Side Upgrade – Best Practices

• Need to systematically copy over configurations from the old domain to the new domain

– JMS artifacts config

– Datasource config

– JCA adapter config

– Work Manager/threads config

– Custom J2EE apps

– WLS config

– SOA config

– SOA shared metadata

– SOA composites/Service Bus projects

– DT@RT customizations

– Custom OWSM Policies

– Custom OPSS policies/roles/keys/certs

• If you already have automation in place to create new domain and deploy all the config, you could leverage this

• If not, tools exist from vendors such as Rubicon Red’s MyST(http://myst.rubiconred.com/)

24


RubiconRed MyST for Side-by-Side Upgrade

• Some special features provided for upgrade

• For more info, see:www.middleworks.com/soaexpert/upgrade/rxr-soa12c-migration.pdf

• Automated provisioning tool for SOA/FMW with ability to extract existing configurations into a “blueprint”

Meet up after session

4:30-5:30PM RR booth:

#331, Moscone South


In-Place Upgrade – Best Practices

• Carefully check prerequisites

• Run the upgrade readiness check before starting (12.2.1)

• Plan carefully and thoroughly test upgrade on a system similar to production. Could use T2P to create it.

• Test composites thoroughly without redeploying after upgrade of test system and determine tuning to be applied.

• BAM upgrade is more complex – read documentation carefully and plan.

• Test composites thoroughly after migrating them in JDeveloper after upgrade of test system. Could use OjMigrate to bulk Migrate composites

• Speed up upgrade by purging unneeded instances before upgrade.

• Make sure enough disk space is available for upgrade.

• If issues are encountered, support can take time. Budget enough time.

26


Upgrade Troubleshooting Suggestions

• Reconfig of domain fails

– Have you read the prerequisites?

– Have you read the upgrade support notes on workarounds (example Knowledgebase Document 1958724.1)

– Are you using non standard configurations different from EDG? Focus of upgrade testing was EDG.

• Server does not start after upgrade

– Something went wrong in the upgrade.

– Have you read the upgrade support notes on workarounds?

– Did you carefully examine logs?

• Composites don’t behave the same after upgrade

– Maximum effort has been expended to make everything backwards compatible, but there may be corner cases.

– Service Infrastructure API are not all backwards compatible.

– Tuning is very different in 12c with use of work managers in SOA

– Flow ID changes may impact composites setting composite title

27


SOA Suite 12c Upgrade Q&A

• Please fill out the 12c Upgrade survey:

– https://www.surveymonkey.com/r/soa-12c-upgrade

• OOW slides uploaded | all slides plus extra content available at:

– www.middleworks.com/soa-expert/

– Leave a business card to be added to Middleworks / SOA Expert Series mailing list

• Casual meetup / follow-up discussion following session in Rubicon Red booth #331, Moscone South

• And thanks!!!

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. |

SOASuite 12c Side by Side Upgrade Best Practices and Roadmap

Oracle Service (SOA) & Cloud Integration Product Management

Oracle Copyright


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.


What is side by side upgrade (high level)?

• Create domain with same config/metadata as prod.

• Prepare new domain for production

• Cutover – new requests from client go to new domain.

• Wait until all long running instances and backlogged messages drain in old production

• Destroy old production.

Oracle Copyright


• CY2017

– Lift and shift (AppToCloud) from on premise to cloud for SOA or OSB in SOACS including side by side upgrade.

– Works across versions (say 11.1.1.7 onprem)

– Shift and provisioning is combined.

– Can change URLs as you shift.

• Other projects also being considered.

Key Upgrade related features in SOACS roadmap

Oracle Copyright

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Copyright

Loopback invokesCallbacks

WLS FE host/port

Loopback InvokesCallbacks

WLS FE host/port

Inactive

http Clienthttp Clienthttp Clienthttp Client

External httpcallbacks

External httpcallbacks

Adapters

DNSSwitch

LB

LB

inactive

Onprem

cloud


• Side by Side Upgrade– Minimum down time

– Rapid rollback.

– Active instances before cutover stay onprem and will run there

– Two consoles needed while preserving historical info

– No down time while you prepare your new cloud instance.

– Can test against test endpoints before cutover.

– A few minor limitations (message ordering, correlation sets)

Oracle Copyright

Benefits of Side by Side Upgrade - onprem to cloud

• What is automated? – Creating a soacs deployment with test endpoints

– Creating a soacs deployment with production endpoint.

– Cutover steps are manual/scripted by user.


• Approach 1:– Assumptions: New POD is tested with changes

applied. POD has test endpoints.

– Delete new POD and recreate with test endpoints again.

– Apply all changes and do sanity tests if possible.

– Cutover

• Disable inbound adapters in onprem system or redeploy composite with test inbound endpoint.

• Redeploy all composites with deployment plan with production endpoints in new POD. (and/or change token values). Inbound adapter addresses could be the same between onprem and cloud.

• Cutover HTTP clients

• Approach 2– Assumptions: New POD is tested with changes

applied. POD has test endpoints.

– Delete new POD with test endpoints and recreate POD with production endpoints. Inbound adapter addresses are different between onprem and cloud

– Apply all changes and do sanity tests if possible.

– Cutover

• Cutover adapter clients

• Cutover HTTP clients.

Oracle Confidential – Internal/Restricted/Highly Restricted 8

Cutover steps in SOA in SOACS (onprem to cloud side by side)


• Test after upgrade.

• Cutover adapters.

• Switch domain from test endpoints to production endpoints.

• Switch over clients. Are any client changes required?

• Disable inbound adapters

• Optimize Enterprise deployment creation. (cloud control?)

• Have long running instances complete properly in side by side domains.

Oracle Copyright

Side-by-side upgrade checklist (on-prem)

Document how you will:

Copyright © 2014, Oracle and/or its affiliates. All rights reserved. | Oracle Copyright


• When you no longer have a need to rollback to old production.

• When all long running instances in old production have completed.

• When you no longer need the history present in the old production. (best practice is frequent purges of history)

Oracle Copyright

When do you destroy the old production system in side by side?

• After you have cut over to new production system.

• When all backlogged messages in queues in old production has drained.


• Not all customers can tolerate concurrent side by side execution.

• Willing to take some down time.

• Have short lived instances.

• Alternative HTTP cutover

– Block HTTP traffic

– Let old domain drain.

– Shut down old domain.

– Cutover HTTP clients.

Oracle Copyright

Alternative to concurrent side by side execution (onprem)

IEEE SOA Suite 12C Upgrade

SOA Suite Upgrade from 11g to 12C

Sireesha Beeram

About me➢Sireesha Beeram

➢Sr. Programmer Analyst @ IEEE for SOA–[email protected]

➢Using Oracle SOA since 2011

➢Upgraded from SOA 11.1.6 to 12.2.1

Overview•Why Upgrade?

•IEEE SOA Architecture

–11g Environment Vs 12c

•Upgrade Strategy

•Upgrade Tasks

• Overview of 2 tasks

–Automatic Build

–BAM

•Benefits seen

•Specific Issues / Details

Why Upgrade

•Mobile Enable Services (REST/JSON)

•Increase in transaction volume/Customers (about 3X)

–More flexible coherence architecture to scale out (separate jvm)

•Browser Independent for BAM

•Automate deployment process

IBP SOA implementation: key stats➢ Web services:

➢ Over 120 OSB services exposed as both as REST JSON and SOAP.

–60 composites/~100 Bpel process/250 xslt/300 xqueries files

–25 BAM Dashboards, 5 DataObjects

➢ Consumers:➢ Internal consumers ~ 10

➢ External consumers ~20

➢ Cloud Integrations ~10

➢ Transactions during the peak season:

➢ Avg load: 250K transactions/hr

➢ Peak Load: 500K transactions/hr

12C Environments

Upgrade Strategy (12c)

➢ All transactions short-lived, so shut down inputs, let all complete, bring up new instance

➢ New installation of 12C (DB+SOA)

➢ Side-by-side, but without running production in parallel

– Update F5 virtual urls

Upgrade Tasks : Pre-Upgrade

➢ Prerequisites -> JDK1.8/11.1.6/DB..➢ Manually identify customizations and

settings

➢ SOA: EM

–System mbean Properties/Adapter settings/preferences

➢ OSB: EM

–Work managers/Timeouts/…➢ Weblogic:

–Domain configurations–Adapters/Certs

➢ Servers: –Script/Classpath changes (customizations)–Customization jars

Upgrade Tasks

➢ Full testing to identify any new release issues➢ Use SOAPUI to identify issues

➢ Split join Caching

➢ OSB->SCA->OSB->SCA issue (foreign key constraint)

➢ For those upgrading now, may see very few of these

➢ Leverage new functionality➢ REST, Automated Build using MAVEN

➢ Performance tests on QA environment

–Redefine timeouts

Automatic Build

1. Schedule: Mon/Wed/Friday

Application POM

Project POM

2.Maven

3.Deploy

BAM

1

3

2

4

Benefit Seen

➢Overall, upgrade easier than expected➢12c Auto-purge solves 90% out-of-the-box➢OSB/EM Console monitoring during Performance testing➢40% Code reduction: ➢ Removed Custom REST:Exposed pipeline to

REST➢ UMS Adapter replaced custom email code/jars➢ IEEE Customizations:Taxware client jars

removed➢Happy Customers➢ Can use any browser for BAM

➢Auto Deployment: Maven/Bamboo

➢ 20 hrs/wk savings (eliminate manual work and errors)

Specific Issues / Details· Audit trail is missing : Set completionPersistPolicy = immediate

· Title not appearing : Change setCompositeInstanceTitle to

oraext:setFlowInstanceTitle

· 12.2.1 : OSB->SOA->OSB->SCA : ORA-02291: integrity constraint

(SOAINFRA.FTCA_SCA_PARTITION_FK)

o Header information missing. Patch: 23138916

· BAM Adapter does not insert data into BAM DataObject : Use JMS queues/EMS

instead

· 12.2.1.0 : SalesForceAdapter : not working : Use 12.2.1.1

· Policies attached to ESS are not persisting after server restart : working with

Oracle to resolve

· OSB service faults will no longer return BEA- Error Codes: Set

Dcom.oracle.sb.MsgIdPrefixCompatibilityModeEnabled=true" is added to OSB

startup

· REST calls were not working: un-target the "API Manager Starter Application"

application on osb server

· OSB Result cache jars from 11g not working: Uses classes relating to :

com.bea.wli.sb.service.resultcache.ResultCache

· 12c purge missed dvl_message - working with Oracle to resolve

MultiPlan - SOA 12c migration path

Faisal Farooqui

IT-Director of Core Service

22

We are a cost containment company in healthcare space

Network –Based

Solutions

Analytics–Based Solutions

Waste, Abuse & Fraud

Solutions

● Negotiation Services● Data iSight● Viant IPR/OPR

● Non-Par● MultiPlan Claims● Clients’ Claims

● Primary PPO● Complementary Network● Specialty Networks

Network-Based Solutions Analytics-Based Solutions Waste, Abuse & Fraud Solutions

Who are we?

33

❏ Online Systems for Customer Service, Claim Entry and Data

Management

❏ Offline systems for Search ETL and Claim Pricing

❏ Three OSB Instances (200+ proxies) and One SOA Instance (50+

composites)

❏ SDLC Environments include DEV, QA, UAT, PRE-PRD, PRD, DR

How do we use SOA Suite

44

Offline BUS Enterprise BUS

ClaimsBUS SOA Suite

Messaging Server

Coherence

WebCenter Portals

External F5 Load Balancer

External Apache Web Servers

Firewall

Oracle Database

Internal F5 Load Balancer

Internal Apache Web Servers

Logical Layout

55

Reason for Upgrade❏ Integration

❏ REST

❏ Coherence adapter

❏ BiDirectional UMS adapter

❏ Reusability

❏ Templates

❏ Pipeline sharing

❏ Development Environment

❏ Integrated WLS

❏ Visual Debugging

❏ Performance

66

Planning❏ Early Adoption: migration from 11.1.1.7 to 12.1.3

❏ Prerequisites

❏ JVM upgrade to JDK 7

❏ Spent considerable time on building test suites

❏ RISK Management

❏ Staggered migration approach for each Bus followed by SOA

❏ Weblogic 12c upgrade was pushed to a later time

77

Execution❏ Switched from in-place to side-by-side upgrade

❏ OPSS security seeding to DB was failing (support note for

workaround with 12.2.1)

❏ Minimize down time

❏ Approach

❏ Runtime Upgrade - Export from 11g and import into 12c.

❏ Code Upgrade - Upgrade SVN project; build and deploy 12c

artifacts as needed.

88

Execution

❏ The migration process was fairly smooth; most of the issues were

uncovered while dealing with the first bus.

❏ Step highlighted in RED indicate some unplanned difficulties

Prepare Test Plan Provision VMs Setup New 12c Domains

Execute test plans on 11g Export from 11g and import into 12c

Execute test plans on 12cImport Code in JDEV

resolve Deploy to 12c

99

Issues❏ Request Entity too large

❏ XSLT Incompatibilities

❏ XDK Incompatibilities

❏ Rules syntax issues

❏ Async callback handling

❏ Temporary JMS Queue unreachable

❏ Build: Maven does not support encrypted password

1010

CutOver Day

❏ Paused All JMS Producers/Consumers and allow the messages to drain.

❏ Updated F5 to point to the new cluster addresses

1111

Lesson Learned❏ Ran a POC with Search Bus, most of the issues were resolved with

minimal systems impact.

❏ Migration to 12.2.1 would have been easier as it resolves most of the

issues uncovered

❏ Separation of Runtime vs Code upgrade was a very good approach as it

cut down the initial migration time.

❏ CI process was instrumental in getting the 12c code migration in time

1212

Build Automation

BAMBOO

DEV

STABLE

Build Artifact

Artifactory

DEV JDEV

SVN

JPR

Maven package

Maven deploy

Maven install

pom

Maven testEmail

Success/Fail

DEV Service NowChange Request(create)

DEVDEV

MGRService Now

Change Request

(approve)

DEV SQA

PROD

Oracle Fusion Middleware Environments

Weblogic/OSB/SOA

CI Solution for Reference

Date post:	31-Dec-2016
Category:	Documents
Upload:	vunguyet
View:	251 times
Download:	5 times