Partner Webcast – Business Continuity with Oracle Weblogic 12c

Stay Connected

BLOGS.ORACLE.COM/IMC

TWITTER.COM/ORACLEIMC

YOUTUBE.COM/ORACLEIMCTEAM

FACEBOOK.COM/ORACLEIMC

http://blogs.oracle.com/imc

http://twitter.com/oracleimc

https://www.youtube.com/OracleIMCTeam

https://www.facebook.com/OPN.PartnerHub.Migration.Center

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

Business Continuity with Oracle WebLogic 12c

Emin Askerov FMW Technology Consultant ISV Migration Center December 4, 2014

Presented by


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.

4


Agenda

• Introducing Oracle WebLogic 12c

• Oracle WebLogic 12c HA Options Overview

• Integration with Oracle RAC: Active GridLink Overview and Benefits

• Application Continuity: Masking Database Outages

• Demo

• Q&A

5


Agenda





• Demo

• Q&A

6


Business Continuity

7

Business Continuity - capability of the

organization to continue delivery of

products or services at acceptable

predefined levels following disruptive

incident (Source: ISO 22301:2012)

Image source: http://www.thebci.org


Why Oracle WebLogic Server?

WebLogic Server, proven globally in all

verticals and geographies #1 on Gartner’s 2013 Application Platform

Market Share: All Software Markets, Worldwide, 2013, March 2014

37.7%

WebLogic, leader 6+ years

8


Oracle Cloud Application Foundation

Oracle WebLogic Server 12c Release 12.1.3

Oracle Coherence 12c Release 12.1.3

Oracle Enterprise Manager 12c

Oracle Development Tools 12c

Deployment

Productivity & Management

Oracle Tuxedo 12c

Cloud Application Foundation

WebLogic Server

Application Services

Exalogic Private & Public IaaS

Coherence Tuxedo

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


Oracle Cloud Application Foundation WebLogic & Coherence Delivery Platforms and Focus Areas S

tra

teg

ic

Fo

cu

s

Multitenancy for Density/Utilization

#1 HIGH PRODUCTIVITY

Java EE

Java SE

HTML5

Mobile, Developer Productivity

Cloud Scale Management

and Operations High Availability and

Performance

Engineered Systems (Exalogic, SuperCluster)

Conventional On-premise Public, Private, 3rd Party Cloud

Pla

tfo

rm

Ch

oic

e

10


WebLogic Server 12.1.3 Mobile, Developer Productivity

WLS12.1.3 Clients

HTM

L5

clien

ts

ADF Mobile

Proxies

OTD

Apache

OHS

Web Sockets (JSR 356)

TopLink Data Services

Server-Sent Events

JAX-RS 2.0

WebSocket Emulation

We

bSo

cket Em

ulatio

n

JAX-RS 2.0, WebSocket 1.0

JSON Programming API

JPA 2.1

Server-Sent Events

WebSocket Emulation

JPA-RS

JPA

Change Notification

Database

JSON Programming API

HTTP/S, JSON/XML WebSocket, Server-Sent

Events, Long polling

Java EE 7 APIs

Additional WebLogic Value-Add

11 11


Seamless Upgrade

Prior WebLogic

Server Versions

JBoss

WebSphere

Migration Services

GlassFish

Simple Upgrade Redeployment

Internet

Application Server

Automated Tooling


Agenda





• Demo

• Q&A

13


Key Concepts Clusters

•Can have zero or more clusters in a domain

•Clusters can have one or more servers

• Some servers in a domain may not belong to any cluster

Example domain: 2 clusters - 1 for hosting “UI” part (front end) of a distributed app,1 for “Business Logic” (back end)

14


Data Failure Human Error

Hardware Failure

Site Disaster Software Failure

UNPLANNED DOWNTIME Failures & Solutions

Integration with Oracle RAC, Active GridLink

Dynamic, Static Clusters Service Migration

WAN Clusters for Disaster Recovery

Dynamic, Static Clusters Server & Service Migration

WebLogic High Availability


Application Upgrades

Server Upgrades

Configuration Changes

PLANNED DOWNTIME Operations & Solutions

Hot redeployment Side By Side Deployment

Dynamic changes

WebLogic High Availability

Rolling Cluster Upgrade


Dynamic Clusters – Simplified Scalability for the Cloud

17

Zero Reconfiguration to Scale, Shrink Clusters

Dynamic Clusters with Automated Ports, Naming

Oracle Cloud, Private Cloud Elasticity

Simplify Cluster Configuration and Scaling Dynamic Clusters


• “Elastic scaling” for cloud environments • New option to simplify scaling of WebLogic

clusters

• Eliminates reconfiguration required to scale clusters

• How it works • User creates a cluster with dynamic servers

and a server template

• Defines server-specific attributes calculated when scaling

• Server name, listen ports, machines…..

• Standard mechanisms used to start/stop servers to scale cluster

Dynamic Clusters - *new in WLS 12.1.2

18


Key Concepts • Server Templates

– Define common, non-default attributes that can be applied to different server instances

– Change in one place, percolated to all server instances

• Dynamic Servers

– Instances which are not individually configured

– Get their configuration from a Server Template

• Dynamic Clusters

– Clusters that include Dynamic Servers


Server Templates

• Configuration can be done via

• Admin Console

• WLST

• Defining Server Template

• Specify common attributes for a group of server instances

• Each server instance can be linked to a Server Template

• If needed, attributes can be overridden

• Macros can be used for any string attribute (and not for integers or references to other configuration elements)


Using Server Templates

• Primary use is with Dynamic Clusters

– Also usable with configured managed servers

• Servers inherit changes dynamically

• Tokens for server-specific configuration:

– ${id} instance id

– ${serverName}

– ${clusterName}

– ${domainName}

– ${system-property-name}

21


Dynamic Clusters

• Configuration can be done via

– WLST

– Admin Console

• Contains one or more Dynamic Servers

• Based on a single, shared Server Template

• Helps in easily scaling up the number of Dynamic Servers in a domain

• Specify the number of server instances anticipated at peak load

• If additional servers needed, then create new servers based on the Server Template

• Following attributes are key for the configuration

– Server Name, Listen Ports, Machines, Network Access Point


Typical Use Cases

• Quick cluster for development

• Cluster that needs to be scaled out at will

• Cluster spread across specific machines in a data center

23


HA with Whole Server Migration Application and Resource Recovery with Continuous Capacity

• Automatic migration of failed servers within a cluster

• Effectively a server restart and recovery on another machine

Domain

Machine 3 Machine 2 Machine 1

Administration Server

Managed WLS 2

Resources 2

Managed WLS 3

(Cluster Master)

Resources 3

Database or Consensus Leasing Storage Area Network

Spare Capacity

Managed WLS 2

Resources 2

Detect Failure

Migrate Server

Managed WLS 2

Resources 2

WebLogic Cluster

24


HA with Service Migration Resource Recovery with Fast Recovery

• HA for singleton services

• Restart and recover services on another running server in the cluster

Domain

Machine 3 Machine 2 Machine 1

Administration Server

Managed WLS 2

Resources 2

Managed WLS 4

Resources 4

Managed WLS 3

(Cluster Master)

Resources 3

Resources 2

Detect Failure

Migrate Service

Managed WLS 2

Resources 2

Storage Area Network

WebLogic Cluster

Database or Consensus Leasing

25


Cluster Managed Server 1

Domain

Managed Server 2

HA with WebLogic State Replication Surviving a Failed WebLogic Server

WAN State Replication

MAN State Replication

Global Load

Balancer

Local Load Balancer

Local Load Balancer

Cluster 1

State 1

State 2

Cluster 2

State 3

State 4

Global Load

Balancer

Local Load Balancer

Local Load Balancer

Cluster 1

State 1

State 2

Cluster 2

State 3

State 4

State 1

State 2

Domain State Replication

In Memory or Database Backed Asynch or Synch

In Memory Database Backed Asynch

Load Balancer


HA with Side by Side Deployment Zero Application Downtime

Newer version of application deployed side-by-side with older version in same JVM

Clients already connected continued to be served by older version

New clients connect to newer version

• Test versions before opening up to users

• Rollback to previous versions

• Automatic retirement – graceful or timeout

Managed WebLogic Server

Single Java VM

Application Version

One

Existing External Client Connections

New External Client Connections

When Activated

Application Version

Two

Internal Client Connections

Test First in Administrative Mode

27


HA with Rolling Upgrade Zero Server Infrastructure Downtime

• Upgrade a running cluster with a patch, maintenance pack, or minor release without shutting down the entire cluster

• During the rolling upgrade of a cluster, each server in the cluster is individually upgraded and restarted while the other servers in the cluster continue to host your application

• You can also roll back the patch, maintenance pack, or minor release in a similar fashion

IP Unicast

Node 3

Managed Server

Node Mgr

App 1

Node 4

Managed Server

Node Mgr

App 1

Node 1

Managed Server

Node Mgr

Node 3

Managed Server

Node Mgr

App 1

Maint Pack x.y Maint Pack x.y

Maint Pack x.y Maint Pack x.y

App 1


WebLogic Server 12.1.3 High Availability and Performance

29

Dynamic Cluster

Server 1 Server 2

Server 3 Server 3

JMS JMS

JMS JMS

WebLogic WebLogic

Oracle

Database

12c RAC

• Continued Database Integration

• Bundle 12c driver

• AQ JMS Database 12c support

• High-Availability

• No TLOG option – Phase 1

• XA Transaction Recovery Across Sites

• Exalogic Optimizations

• Density - Memory Optimizations

• Performance – JMS


WebLogic Server 12.1.3 – XA Without TLOGs

30

• Improve performance, manageability of XA apps

• No TLOG I/O – up to 3x throughput improvement

• No TLOG replication requirements for DR

• How it works

• Define “determiner” resource - last to prepare/commit

• Tx recovery based on resource state and determiner

• Single TM w/no LLR or JTS – no TLOG required

• Multiple TM – reduced writing to TLOG

• Multi-phase delivery of this features

• Multiple TM XA in with no TLOG in 12.2.1

Managed Server Managed Server

TM TM

DS1 DS2 DS1 DS2

Determiners


WebLogic Server 12.1.3 – Cloud Scale Management Dynamic Clusters Update

31

WebLogic 12.1.2 dynamic clusters support JMS

WebLogic 12.1.3 adds Whole Server Migration Support

Roadmap for providing ASM, UOO, SAF in 12.2.1

Simplify Configuration of HA JMS Clusters Dynamic Clusters


Availability, Multitenancy, Scalability Oracle WebLogic and Database 12c Integration

32

WebLogic, Database

Integration

Application Availability with Transaction Guard

Support for Multi-Tenant Database

Scalability with Database Resident Connection Pooling

Application Continuity

Database Resident

Connection Pool

Global Data Services

Multi-Tenant

Database

WebLogic Server


Agenda





• Demo

• Q&A

33


GridLink

WebLogic

GridLink

WebLogic

WebLogic Integration with Oracle RAC

Up to 3X Better Performance with Active GridLink for RAC

• Integrated WebLogic and Database RAC clusters

• Dynamic load balancing of requests to RAC nodes

• RAC node transaction affinity for data locality

• Continuous connection availability regardless of RAC changes

80% 20%

RAC Node Load Aware Connection Requests

GridLink

WebLogic

GridLink

WebLogic

RAC Node Affinity For Transactions

XA

GridLink

WebLogic

GridLink

WebLogic

Continuous Connections Regardless of RAC Changes

34


Active GridLink For RAC - Configurability

Old: Multi Data Source • Enables load balancing with XA

on old RAC versions but…. •Data source (DS) per RAC node

•Map DS to RAC nodes •Grouped DS into MDS •Configuration scaling issues

New: GridLink Data Source

• Leverages RAC technology • Single data source per cluster • SCAN address

• Simpler •More scalable

Machine 1

RAC

Node 1

RAC Cluster

Oracle Database Service

GridLink Data Source

Local

Listener

ONS

Machine 2

RAC

Node 2

Local

Listener

ONS

WebLogic Cluster

Machine 2

Managed

Server 2

RAC SCAN

Machine 1

Managed

Server 1

Machine 1

RAC

Node 1

RAC Cluster


Multi Data Source

Local

Listener

ONS

Machine 2

RAC

Node 2

Local

Listener

ONS

WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Data

Source 1

Data

Source 2

Single Data Source

Multiple Data Sources

35


Active GridLink For RAC - Manageability GridLink isolates WebLogic from RAC changes Consider adding RAC node 1. Multi Data Source (MDS)

•Undeploy MDS •Add data source 3 on all servers •Update MDS list

•Redeploy MDS •Coordinate across servers

2. GridLink •Automatically detects RAC node •No WebLogic config changes • Simpler

•More reliable, no downtime RAC Cluster



WebLogic Cluster

Machine 2

Managed

Server 2

RAC SCAN

Machine 1

Managed

Server 1

Machine 1

RAC

Node 1

RAC Cluster


Multi Data Source

Listener

ONS

WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Data

Source 1

Data

Source 2

Machine 3

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Data

Source 3

Machine 1

RAC

Node 1

Listener

ONS

Machine 3

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Configuration

changes

No

changes

36


Active GridLink For RAC - Performance

• Runtime Connection Load Balancing (RCLB) • RAC workload aware

• Avoid busy RAC nodes • Multiple apps, backups

• Multi Data Source (MDS)

• Round-robin load balancing • New connections to busy node • Bottlenecks, performance

impact

• GridLink • RCLB distributes runtime

connections to least busy nodes • Up to 2-3x performance

• More predictable performance

RAC Cluster


WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Machine 1

RAC

Node 1

RAC Cluster

Multi Data Source

Listener

ONS

WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Data

Source 1

Data

Source 2

Machine 3

BUSY

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Data

Source 3

Machine 1

RAC

Node 1

Listener

ONS

Machine 3

BUSY

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Uneven

workload

Balanced

workload

37


Active GridLink For RAC - Availability

• Fast Connection Failover • Faster failure detection and

failover

• Multi Data Source (MDS) • Periodic polling for node failure • Latency in failure detection

• No awareness of planned shutdown

• GridLink • Failure notification via ONS

• New connections to surviving nodes (no WebLogic polling)

• Recovery notifications • Graceful RAC node shutdown

RAC Cluster


WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Machine 1

RAC

Node 1

RAC Cluster

Multi Data Source

Listener

ONS

WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Data

Source 1

Data

Source 2

Machine 3

DOWN

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Data

Source 3

Machine 1

RAC

Node 1

Listener

ONS

Machine 3

Down

RAC

Node 3

Listener

ONS

Machine 2

RAC

Node 2

Listener

ONS

Polling and

delayed

detection

Rapid

notification

via ONS

Available? Available? Available?

Node 3

Down

38


Agenda





• Demo

• Q&A

39


Application Continuity – JDBC Replay Improved Resiliency for Better User Experience

RAC Cluster


WebLogic Cluster

Machine 2

Managed

Server 2

Machine 1

Managed

Server 1

Machine 1 RAC

Node 1

Listener

ONS

Machine

3 Down

RAC

Node 3

Listener

ONS

Machine 2 RAC

Node 2

Listener

ONS

1. FAN Down Event: “Node 3 Down”

2. Create Connection to Surviving Node; Replay if safe

• Leverage feature supported in DB 12c

– Generic and GridLink datasources

• DB exceptions captured at datasource layer

– Examples: RAC node failure, transient DB problem

• Automatically replay requests – Transparent to application

– Read and write requests supported

– No XA Transaction support

• Benefit: Better end user experience


Application Continuity Notes • Active Gridlink and Generic datasources, 12c driver only

(bundled with WebLogic 12.1.3)

• Leverages JDBC replay, re-implemented in 12c DB

• Enabled with use of oracle.jdbc.replay.OracleDataSourceImpl driver class

– When connection is taken from pool, “begin” is called

– JDBC calls are “remembered” through commit

– When connection is put back in the pool, “end” is called

• On failure, new connection is automatically created

– Transparent to application!

– Replay is already complete when connection is given to app

How it Works in WebLogic

Limitations :cannot use with

XA, PLSQL, proxy authentication, DRCP


Demo

42


Q&A

43

Emin Askerov Oracle ISV Migration Center Consultant [email protected] ISV Migration Center blog: http://blogs.oracle.com/imc ISV Migration Center email: [email protected]



mailto:[email protected]


Oracle Partner Hub ISV Migration Center

Oracle.com Partner Hub

Team Info, Events/Activities Schedule, etc

Migration Center Team Blog

Webcasts, Howto, Demos, Guides, etc Youtube: OracleIMCteam

Slideshare: Oracle_IMC_team

twitter.com/OracleIMC

plus.google.com/+OracleIMC

facebook.com/OracleIMC

linkedin.com/groups/Oracle-Partner-Hub-Migration-Center-4535240

feeds.feedburner.com/oracleimc

[email protected]

44

http://oracle.com/partners/goto/hub-ecemea

http://oracle.com/partners/goto/hub-ecemea


http://www.slideshare.net/oracle_imc_team






https://plus.google.com/108612216492389783792






http://linkedin.com/groups/Oracle-Partner-Hub-Migration-Center-4535240












http://feeds.feedburner.com/oracleimc






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