On the 25th of October at Open World 2015, Oracle released the 12.2.1 version of SOA Suite 12c. This release is full of resiliency updates on the operation side of life.
The operations of integration are critical and Oracle listened to the business requirement of customers while developing this release. Here are few of these operations.
- Usually many hardware/software systems are managed by a small team.
- With minimum need for admin intervention an integration needs to run silently, automatically and smoothly.
- When things do go wrong, a console is needed that quickly allows identification and resolution of exceptions.
- Without a lot of admin training it should be relatively simple to manage integrations.
- An integration needs to scale, perform and provide continuous availability to process high workloads.
- Ability to patch applications/composites for emergency fixes.
It isn’t the first time in the life cycle of SOA Suite 12c that Oracle is working on the operations of the product.
SOA Operations in 12.1.3
In the previous 12.1.3 release Oracle already targeted the IT operations. Read my blog about it for more details. But for a quick reference, here are the major updates.
- Automated Operations
- Auto Purge: Old data past the retention point are periodically on schedule to be automatically be purged.
- Modularity Profile: Startup time and memoty is reduced by starting up components that are used (depends on the selected profile).
- Lazy Loading: Startup time is reduced by loading composites only on first use.
- Problem Identification & Resolution
- Centered Error Hospital: The EM is reworked to be centered around exception conditions instead of business as usual, including a centralised Error Hospital.
- Better Flow Trace: A flow trace with multiple composites shows both in a single trace for better troubleshooting.
- Simplified Tuning
- Work Managers: Simplify and improve thread tuning by switching to work managers. In 12.1.3 it is possible to assign a work manager per soa-infra partition.
SOA Operations in 12.2.1
Now in this 12.2.1 release Oracle has targeted the IT operations again, but with more focus on resiliency. First lets look at the major updates.
- Circuit Breaker: Improved resiliency when downstream services go down by suspending inbound services.
- In-Memory SOA: Optimize performance and scalability by reducing database growth.
- Integration Workload Statistics: Diagnostic tool for analysing performance similar to DB AWR.
- Parallel Deployment: Faster SOA and Service Bus startup time.
- Composite Instance Patching: Patch (long running) instances immediately without redeploying new composite version and stalling instances.
- Automatic Service Migration (ASM): Reduce the failover time and amount of machine resources needed for deployment.
Lets look at them in more details in same order as above.
A problem we all have experienced is when services more downstream get unavailable cause instances to failt and fill up the error hospital. Manual recovery is sometimes difficult and time consuming. These failing instances consume unnecessary resources.
Because of these failing instances the operational costs to recover instances in the error hospital are greater. There is also a potential instability of the system due to the errors on business critical instances.
In the 12.2.1 release Oracle introduces Circuit Breaker. It automatically suspend upstream inbound services and the messages are added in queues on disk for later processing. The inbound services automatically resume when the downstream service endpoint is up. Read the complete article here.
SOA & BPM Partner Community
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
Blog Twitter LinkedIn Facebook Wiki
Technorati Tags: SOA Community,Oracle SOA,Oracle BPM,OPN,Jürgen Kress,SOA Suite 12c,SOA Suite 12.2.1