Jeremy Treague of Schreiber Foods discusses their experience upgrading their Oracle SOA Suite from version 11g Patch Set 5 to Patch Set 6 in October 2014. Key reasons for the upgrade were to use the new User Messaging Service adapter and align their SOA and ADF development efforts on a common version. The upgrade process took around 90 minutes and involved stopping services, backing up files and schemas, upgrading WebLogic Server, applying patches, upgrading schemas, and verifying services. Lessons learned include backing up data, paying close attention to post-patch procedures, and resolving issues like missing JMS queues. Future plans include upgrading the SOA database in 2015 and potentially moving to SOA 12c in 2016.

1. SOA Suite 11g Upgrade
Experience
Jeremy Treague
Lead Technical Developer
IS Application Development

2. About Schreiber Foods
▶ Customer brand dairy manufacturer
▶ Founded in 1945
▶ Diverse customer base and product mix
▶ Global production and distribution
operations (26 domestic, 10 international)
▶ Employee owned (7,000 “partners”)

3. About Schreiber Foods
New Home Office (Green Bay, WI)
June 2014

4. Oracle Technologies
▶ Fusion:
▶ Oracle SOA Suite 11g
▶ WebLogic Server 11g
▶ Business Intelligence
▶ WebCenter Content
▶ WebCenter Portal 11g
▶ Identity Management
▶ Others:
▶ Oracle Database (10g & 11g)
▶ Oracle E-Business Suite (R12.1 & R12.2)
▶ Oracle Enterprise Manager 12c Cloud Control

5. SOA 11g PS6 Upgrade
▶ April 2012: Implemented SOA Suite 11g Patch
Set 5 (11.1.1.6)
▶ October 2014: Upgraded to 11g Patch Set 6
(11.1.1.7)
▶ Aligned SOA and ADF development efforts on
common version of JDeveloper (11.1.1.7)
▶ Key Driver: User Messaging Service (UMS)
Adapter
▶ Ability to poll mailbox and process e-mail
▶ “Tech Preview” Designation in 11.1.1.6 (blog)
▶ Officially supported in 11.1.1.7
(documentation)

6. UMS Adapter

7. Upgrade Steps
▶ Documentation (HERE)
▶ Stop all services (managed servers, AdminServer, OHS)
▶ Back up MW_HOME and SOA Database Schemas
▶ Upgrade Weblogic Server (we were already at 10.3.6)
▶ Apply FMW 11.1.1.7 Patch Set to MW_HOME
▶ Upgrade SOA Database Schemas using PSA (MDS,
SOAINFRA, OPSS, ORASDPM)
▶ Apply Latest SOA 11g Bundle Patch (Doc ID 1485949.1)
▶ Start services and verify

8. Tips & Lessons Learned
▶ Remember to take backup (and test it)
▶ Downtime: 90 minutes (clustered topology)
▶ Oracle’s documentation was very good
▶ Didn’t have to re-deploy any composites
▶ Pay close attention to post-patching procedures
▶ “soa-infra” deployment started in “Warning”
status due to missing JMS queue for Case
Management (BPM )
<Oct 19, 2014 5:10:13 AM CDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Oct 19, 2014 5:10:14 AM CDT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: CaseEventMDB is unable
to connect to the JMS destination: jms/bpm/CaseEventQueue. Oracle Doc ID 1584300.1

9. Future SOA Upgrades / 12c?
▶ Upgrade SOA database in FY15
▶ 11.2.0.2 -> 11.2.0.4
▶ Consider moving to SOA 12c in FY16
▶ Developer Productivity, REST Support
▶ Continue to learn via SOA Beta, CAB, User
Experience Programs,
User Groups, SOA Blogs
& Forums
https://blogs.oracle.com/soa/