Oracle Fusion Middleware 12c (12.2.1) New Features – WebLogic
.
As Oracle ACE Atul Kumar has opened his next Oracle Fusion Middleware (FMW) Training course (next batch starts on 5th March 2016) I thought We should cover Fusion Middleware 12c new features in this post. Over next few months, We’ll be adding more and more FMW 12c features & Hands-On Exercises related to SOA/OHS 12c in this course.
Oracle release Fusion Middleware 12c (12.2.1) in November 2015 with many exciting new features and updates for products such as the WebLogic Server, SOA , Coherence, Oracle Traffic Director, OHS, Webcenter Suite, etc.
This post will list a summary of the new features with a reference to the complete documentation for WebLogic Server (in subsequent posts, We’ll be adding new features introduced in other FMW components like SOA, OHS etc)
1. WebLogic Server: Since WebLogic serves as a platform for the entire Fusion Middleware stack, the new features in the application server product are the most important ones for the entire suite.
- Multitenancy Support— The WebLogic domain can now be split between partitions, which are logically associated to a tenant. Tenants can be different companies or departments, basically different users communities. The partitions are administrative parts of the domain as they can contain isolated resources (applications, data sources etc) as well as runtime components as partitions can be started and stopped, thus starting associated applications together with all their dependencies.
- Continous Availability— Big improvements in how customers can define their Disaster Recovery strategy, fault tolerant architectures and migration or rollout plans. Some of the new features include cross domain transaction recovery, zero downtime patching and resource groups migration, which means that a group of related artifacts (applications, data sources, etc) can be quickly targeted to new runtime components (servers or clusters).
- Resource Consumption Management— Since resources can be shared between partitions, they must not be depleted by a misbehaving application in one partition. The Resource Managers can define either Triggers and Actions that act when a certain threshold of resources (Open files, Heap retained or CPU consumption) is reached, or Fair Share which allow the resources to be allocated to partitions based on usage patterns or when it’s not clear what are the exact required values for a specific resource.
- Elasticity for Dynamic Clusters— The elasticity capabilities leverage the WebLogic 12c Dynamic Clusters for on-Demand scaling (or manual scaling) and the WLDF Policies and Actions (the same as Watches and Notifications from previous versions) to implement auto scaling. When a certain Policy is met a Scale up or Scale down Action can be triggered.
- RESTful Management Services — Extended and enhanced management with RESTful services, now enabled by default
- Named Concurrent Edit Sessions— In 12.2.1 there is no longer a single global Edit lock on the administrative changes being executed in a domain. With Named Concurrent Edit Sessions, multiple administrators can now have concurrent edit sessions. This is especially useful in a multitenant scenario where different partitions are managed by different administrators.
- WebLogic Management Framework– Besides the traditional WebLogic Server domains, Fusion Middleware 12.2.1 introduces Standalone domains which are administrative units for system components such as Oracle HTTP Server or the Oracle Traffic Director. Lifecycle of the system components can now be controlled using the Node Manager even in the absence of a WebLogic server installation and WLST scripting is also available. Of course the administration console and the Fusion Middleware EM still requires a WebLogic Administration Server.
- WebLogic is certified with Docker containers— This is currently supported in two scenarios: having a traditional WebLogic cluster with Administration and Managed server,which is supported on a single Docker host, or multiple Docker hosts supported only in a topology where a generic application server is running in each Docker container, i.e. a WebLogic Administration Server where all the applications and dependencies are deployed. This can be considered clustered at Docker level. However, a third solution (not currently supported) would be to use either 3rd party solutions or recent Docker developments such as Docker Machine together with Docker Swarm to configure traditional WebLogic cluster spreading over multiple hosts. Here is an example of such an exercise using Docker Swarm and 3rd party tool Weave:
Many other new features listed and described in the WebLogic Server 12.2.1 Documentation
In next post I am going to cover new features introduced in SOA Suite 12c
If you want to learn more in Oracle Fusion Middleware products Implementation, register for our Oracle Fusion Middleware Training (next batch starts on 5th, March 2016).
We are so confident on quality and value of our training that We provide 100% Money back guarantee so in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money.
FREE Webinar on
Oracle Fusion Middleware Concepts / HA
Live Webinar with Oracle ACE Atul Kumar on Oracle Fusion Middleware Concepts like Java VS System Component, HA Setup for SOA and Live Q/A
Click here to register FREE Live Webinar on 27th Feb 2016
About the Author Brijesh
I'm 10gR2 RAC Oracle certified professional, working from last 6 year in the field of database.