upgrading to oracle soa suite 11g while maintaining 100% uptime

Ahmed Aboulnaga

Technical Director

Raastech, Inc.

Upgrading to Oracle SOA Suite 11g While Maintaining 100% Uptime

December 6th, 2011

14:40-15:25

Paper ID #6589

Hall 7B

of 32 © Raastech, Inc. 2011 | All rights reserved.

1. Introduction

2. Is Uptime Overrated?

3. Overview of SOA Suite 11g High Availability

4. The Cutover Approach

5. The Multi-Repository Integration Architecture

6. Summary

Agenda


IS UPTIME OVERRATED?


What is Uptime?

“Uptime is a measure of the time a machine has been

up without any downtime.” http://en.wikipedia.org/wiki/Uptime

Systems administrators and operations directors are

often judged by the uptime they’re able to demonstrate.

Applies to servers, databases, and applications.


Do you really need 100% uptime?

Customers claim to want 99.999% uptime

− You really can’t afford 5.26 minutes of downtime per year?

Would you be willing to be 6x more to move from 99.9%

uptime to 99.99% uptime? Be realistic

Most customers who believe they are “highly available”

in reality have numerous single points of failure


Do you really need 100% uptime?

Bank of America has over 20 million customers, yet they

still have unplanned downtime for days on end.

Capital One’s online banking site says that you may

“use the Services seven days a week, twenty-four hours

a day, except for any scheduled or unscheduled

interruptions in the Services.”


Who needs uptime? The Galactic Empire

In Star Wars: The Phantom Menace, the droid

communicator ship was destroyed

The droid army loses communication and fail – one of

them even has its head fall off

No available secondary ship? Bad design!


Who needs uptime? Alien Computers

In Star Trek, Captain Kirk only asks an alien computer:

Explain. The. Human emotion. Known. As… Love.

The computer goes into a bizarre loop where its logical

systems can’t compute and explodes…


Who needs uptime? Our Customer

Our customer

$1 million of orders placed every hour… in only 1 market


What is SOA Suite?

Oracle SOA Suite 11g (11.1.1.5)

Based on Oracle Fusion Middleware*

Designed for running integration services and processes

High-performance, standards based, open technologies


What This Presentation Is Not

The effort from moving from Oracle SOA Suite 10g to

11g is both an upgrade and a migration

…and eventually a cutover.

Upgrade – The upgrade is result of moving to a new

version of the same product, namely to Oracle

SOA Suite 11g.

Migration – The migration is the process of

converting existing SOA Suite 10g code to enable

it to deploy and execute on SOA Suite 11g.

Cutover – This presentation.


OVERVIEW OF SOA SUITE 11G HIGH AVAILABILITY


Most customers implement the standard 2-node cluster

This satisfies the majority of cases

Traditional SOA Suite 11g High Availability

SOA Suite

RAC Database

Load Balancer

OHS OHS

SOA Suite

http://loadbalancer/soa-infra/services/default/HelloWorld_ep


The “Enterprise Deployment Guide” has a as-best-as-it-

can-do-one-size-fits-all architecture for HA

− Oracle Fusion Middleware High Availability Guide 11g

Release 1 (11.1.1) E10106-02

− Oracle Fusion Middleware Enterprise Deployment Guide for

Oracle SOA Suite 11g Release 1 (11.1.1) E12036-01

Consider customizing it to your environment

Enterprise Deployment Guide


THE CUTOVER APPROACH


Oracle’s Cutover Approach

Load Balancer

SOA 10g SOA 10g SOA 11g SOA 11g

OHS OHS OHS OHS

The cutover is architecturally straightforward

But…


Oracle’s Cutover Approach

But WSDL URLs have changed!

10g http://vip:80/orabpel/default/HelloWorld2/HelloWorld2?wsdl

11g http://vip:80/soa_infra/services/default/HelloWorld2/HelloWorld2_ep.wsdl

Client applications must be reconfigured

Load Balancer


OHS OHS OHS OHS

Client

Load Balancer


An Alternative Cutover Approach

Load Balancer

Gateway Gateway Gateway Gateway


OHS OHS OHS OHS

To achieve 100% uptime during cutover without requiring

reconfiguration/redeployment of client applications,

service virtualization (e.g., OWSM 10g, OSB, OEG) may

be needed


BPEL Types of Transactions

Short-lived transactions

− Sync

− One-way async

Inbound messages

− JMS consume

− AQ dequeue

− File read

Long running processes

− Human workflow

− Callbacks

Request

Response

BPEL

Dequeue

BPEL BPEL

Worklist Application


Transactional Considerations – Short Lived

Gateway Gateway

SOA 10g SOA 10g

OHS OHS

Short-lived transactions can go through 10g and 11g until

10g is officially decommissioned

These can be sync or one-way async transactions

Load Balancer

Gateway Gateway

SOA 11g SOA 11g

OHS OHS

Load Balancer Load Balancer


Gateway Gateway

SOA 10g SOA 10g

OHS OHS

Load Balancer

Gateway Gateway

SOA 11g SOA 11g

OHS OHS


Transactional Considerations – Inbound

Inbound messages can be through inbound adapters

Includes JMS adapter, AQ adapter, file adapter, etc.


Transactional Considerations – Workflow

Human workflow is the biggest issue here

Must ensure that they are flushed out from 10g

Multiple layers of load balancing allow callbacks to be

received to the appropriate cluster

Gateway Gateway Gateway Gateway


OHS OHS OHS OHS

Load Balancer



THE MULTI-REPOSITORY INTEGRATION ARCHITECTURE


Not really

− 100% uptime, whether due to planned or unplanned

downtime, is not possible

The bottleneck here is the MDS, based on the Oracle

Database

− Rolling upgrades for the database is not always feasible with

certain types of upgrades, such as major releases

Other issues involve cluster related bugs

− They do exist!

− Will impact the entire cluster

Can you have 100% uptime with SOA Suite?


100% Available SOA Suite

Gateway Gateway

OHS OHS

Load Balancer

SOA 11g SOA 11g

Standard 2-node cluster

Satisfies the need of most organizations


100% Available SOA Suite

Gateway Gateway

OHS OHS

Load Balancer

Gateway

OHS

Gateway

OHS


4-node cluster, sharing the same MDS

Demonstrates the ability to scale


Load Balancer

10g

Load Balancer

Load Balancer Load Balancer Load Balancer Load Balancer

10g 11g 11g 10g 10g 11g 11g 10g 10g 11g 11g 10g 10g 11g 11g

100% Uptime Cutover

11g is brought in load and 10g is taken out of load


SUMMARY


100% availability

True rolling upgrades

Safer upgrades

Each 2-node cluster can be tested before being put back in

load

Improved leveraging of hardware resources

− Better to have 4 x 2-node clusters instead of 1 x 8-node cluster

Advantages of Multi-Repository Approach


Increased maintenance

− Code has to be deployed 4 times

More databases to administer

Complicated tracing of transactions

− You get used to it

− Can be alleviated using sensors

Human workflow and async w/ callbacks are not supported

Can only be supported by middleware technologies that do

not require data at rest, such as SOA Suite

Disadvantages of Multi-Repository Approach


Recap

Availability. Do you really need 100% uptime?

Standard SOA Suite clustering for high availability

Transactional considerations

− Short-lived transactions (e.g., sync & async)

− Inbound adapters (e.g., inbound JMS)

− Long running transactions (e.g., human workflow)

An approach to achieve 100% availability

Cutting over to 11g with 100% uptime

− From a standard 2-node 10g infrastructure

− From an already 100% available 10g infrastructure


Contact Information

Ahmed Aboulnaga

Technical Director

[email protected]

upgrading to oracle soa suite 11g while maintaining 100% uptime

Technology

oracle soa suite

overview of soa suite

b slide

market slide

existing soa suite

g high availability

uptime theyre able

open technologies slide