How to Use the PowerPoint Template - Oracle · for later processing. Automatically resume when...

OpenWorld 2015 Oracle Integration 12.2.1 Operations

Jayaram Kasi Director, SOA PM Aninda Sengupta Sr. Director, SOA Development Oct 25, 2015

Oracle Confidential – Internal/Restricted/Highly Restricted Copyright © 2015, Oracle and/or its affiliates. All rights reserved. |

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

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.

Oracle Confidential – Internal/Restricted/Highly Restricted 3


Oracle Cloud Platform

4

DATA MANAGEMENT

IT OPERATIONS MANAGEMENT

IDENTITY MANAGEMENT

CONTENT & PROCESS

APPLICATION DEVELOPMENT

INTEGRATION

MOBILE

BUSINESS ANALYTICS


What are integration business requirements?

5

• System should be able to handle changes for business requirements.

• System should be highly available and scalable at all times including peak times.

• Must have full operational visibility and control.

• Need business continuity (example disaster).


Why is Integration operations critical? What is needed?

• Need to have adequate tooling to troubleshoot problems and tune.

• Integration needs to scale, perform adequately and provide continuous availability to process the high workloads customers put on it.

• Need to be able to patch applications/composites quickly and immediately for emergency fixes.

6

• Companies have many hardware/software systems that are managed by a small team of admins.

• Integration needs to run silently, automatically and smoothly as much as possible with minimum need for admin intervention.

• When things do go wrong, need a console that quickly allows exception identification and resolution.

• Integration has to be relatively simple to manage. Cannot require a lot of admin training.


Oracle Integration 12c

• Largest deployed SOA and service integration platform globally

• Mission Critical and Business Critical– processes millions of business critical messages per day

• Exponential uptake of 12c

• Lots of feedback from customers. We learn from them.

• Unparalleled connectivity to the Cloud, Applications, Files etc.

• Heavy focus on developer productivity and operations

7

Oracle SOA Suite 12c – The Foundation for Cloud, Digital, Mobile & IoT

Messaging Loose Connectivity Hide Complexities Reuse Processes

73°


Next generation SOA OPS SOA in Cruise Control !!



SOA Operations in 12.1.3

• Target : Operations, IT

• Auto Purge: Automatically purge old data past the retention point periodically on schedule. AUTOMATED OPERATIONS.

• Modularity Profile: Reduce startup time and memory by starting up only components used (selected by selecting a profile). PERFORMANCE

• Lazy Loading: Reduce startup time by loading composites only on first use. PERFORMANCE IMPROVEMENT

• Exception centered management console: Rework of the EM console to be centered around exception conditions instead of business as usual. RAPID PROBLEM IDENTIFICATION/RESOLUTION.

• Work Managers: Switch to work managers to simplify and improve thread tuning. SIMPLIFIED TUNING.

• Flow Trace: Switch to flow trace where multiple composites are shown in a single trace for better troubleshooting. SIMPLIFIED TROUBLESHOOTING.


Introducing Continuous Availability with SOA Suite in 12.2.1



• Availability

– Composite Instance Patching – patch long running instances immediately.

– Automatic Service Migration (ASM) – faster failover

• Performance

– In-Memory SOA – Optimized performance, scalability, reduced database growth.

– Integration Workload Statistics – Performance Diagnostic tool similar to DB AWR.

– Parallel Deployment – faster startup

• Resiliency

– Circuit Breaker – Improved resiliency when downstream services go down.

Summary of SOA Operations in 12.2.1


Resiliency: Circuit Breaker



• Problem: Unavailable services downstream cause instances to fail and fill up the error hospital. Manual Recovery is cumbersome and time consuming. Failing instances consume unnecessary resources.

• Business Impact: More operational costs to recovery instances in the error hospital. Potential instability of system due to erroring of business critical instances.

• Solution: Automatically suspend upstream inbound services so the messages accumulate in queues on disk for later processing. Automatically resume when downstream endpoint is up.

• Unique differentiator for Oracle.

• Tangible benefit: Much less admin overhead and improved performance since failed instances are reduced.

Oracle Confidential – Internal 13





Suspend

Composite

Composite

Unavailable


Resiliency: Circuit Breaker • EM FMWC shows suspended inbound

upstream services and EDN subscribe.

• Downstream endpoint being up is auto detected by letting a few messages through periodically.

• Alerts can be defined when services are suspended/resumed.

• Log file has records for suspended/resumed endpoints.

• Enable/disable globally or per downstream service.

• Support for throttling when endpoints come back up




• Suspended Inbound upstream services include EDN, DB, MQ, UMS, E-Business Suite, SAP, file, ftp, AQ and JMS adapters. Web services will also be suspended and will return errors.

• Monitored downstream services are adapters and web service bindings.



Diagnostics: Integration Workload Statistics (IWS)



• Problem: Lack of tooling like DB AWR to help troubleshoot performance problems and tune the system

• Business Impact: Much more training costs for IT staff for tuning/perf troubleshooting by querying DB or using other less convenient or suitable tools. No tool available at all for some problems.

• Solution: provide DB AWR like reports with key performance data.


• Tangible benefit: Customers can by themselves tune SOA or their applications.


Integration WorkLoad Statistics


Integration Workload Statistics (IWS)

• Helps with performance troubleshooting and tuning.

• Takes periodic snapshots of metrics at configured interval written to Database per managed server.

• Generates Reports by specifying user defined time range. Three report formats: XML, CSV and HTML.

• Example: Last Tuesday between 3 and 4, there were performance problems reported. Need to analyze.

19


Integration Workload Statistics – metrics collected

• Global Utilizations (CPU load, threads used by work manager, db connections used, heap and non heap memory used).

• Service/reference/wire metrics.

• Business process metrics including dehydration time, and total execution time.

• Backlogs and metrics for internal queues – EDN and BPEL invoke and callback queue.

• BPEL activity metrics.

• Supports both top down and outside in analysis.



SOA In-Memory



• Problem: SOA is DB intensive where DB is often the bottleneck limiting cluster scalability, requiring frequent purging to manage DB growth and impacting performance.

• Business Impact: If DB is the bottleneck, there are limited options for scaling affecting business.

• Solution: Use Coherence cache instead of a DB for dehydration and instance tracking data when applicable with write behind.


• Tangible benefit: if DB is the bottleneck they can now horizontally scale. Also major performance improvement. Lastly DB growth rate is significantly reduced.


In-Memory SOA


SOA In-Memory


Previous State

• Persist all state and flow data to Database at every dehydration point

• Requires regular purging to control database growth


SOA In-Memory


Overview of approach

• Choice to persist flow and instance data only for faulted instances and long running instances running longer than a cutoff time.

• Leverage coherence cache for running transactions (flow trace, BPEL state, audit trail and payloads)

• Defer writing to a database, and update in batches

• Configurable write behind thread


SOA In-Memory • Set at component level – allows for various persistence policies in a flow

• Non - XA transactions only

• Business processes with the persistence policy of ’faulted’ will not have audit details on successful completion

• Enterprise Manager flow trace will only read from dehydration database



Composite Instance Patching




• What if a instance fails due to a bug and you want to fix it and resubmit from EM?

• What if a small bug in your composite causes long running instances to fail?

• What if a small change in your flow (e.g. mapping) has to be applied to long running instances?

• You need the ability to make those changes in your composite and then apply to already running instances.


• Problem: No way previously to make small changes to composites and have running instances see the changes. Running instances could be long running for days or months.

• Business Impact: This could have huge implications to the business if critical fixes cannot be made across the board in a timely fashion.

• Solution: Support (limited changes) patching of same revision where long running instances see the change and resubmit of failed instance in BPEL sees the change.







Previous State

• Redeploy to an existing composite revision

• Stops the processing of long running instances

• Create a new composite revision

• Changes do not apply to existing long running instances


Composite Instance Patching - Scope

• Identify a set of compatible changes that can be made to a composite without invalidating existing long running in-flight instances

– For example: XSLT, assign activity, BPEL invoke without variable changes, etc.

– Design time tooling to ensure compatible changes.

• Patches preserve long running instances and transition them to the new metadata – No loss of runtime changes made in SOA Composer

– Runtime compatibility checks prior to the deployment of the changes

– Different approaches for regular deployment and patch deployment

• Supported only in production environment with database MDS


Additional operations features



Additional Features

• Target : Operations, IT

• Automatic Service Migration (ASM): In previous releases, SOA, Service Bus and MFT supported Whole Server Migration only. BAM supported ASM. From the 12.2.1 release onwards, SOA, Service Bus and MFT also support ASM. – reduces the failover time significantly. – reduces amount of machine resources needed for a

deployment. – In ASM, a service fails over from an unavailable managed

server to an already executing managed server.

• WebLogic Parallel Deployment: From version 12.2.1, WebLogic Server supports parallel deployment which should improve SOA and Service Bus startup time.

• Zero down time Patching: Zero down time Patching was introduced in earlier releases, but now there is better support for automating this in WebLogic server.

– Patch indicates if it supports online patching. Not all patches qualify. (E.g. patches requiring schema, data format changes)

– Use of automated orchestration of patch in WebLogic for SOA patches not yet supported.


#SOA12c

Copyright © 2014, Oracle and/or its affiliates. All rights reserved– Confidential Oracle Restricted .

33

Join the Community Visit us on Oracle Technology Network

Oracle SOA blog blogs.oracle.com/SOA

Oracle SOA Website http://bit.ly/soaotn

Connect with Oracle on Social Media

OR connect via the web


Safe Harbor Statement

The preceding 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.


How to Use the PowerPoint Template - Oracle · for later processing. Automatically resume when...

Documents

Transcript of How to Use the PowerPoint Template - Oracle · for later processing. Automatically resume when...