The new Oracle WebLogic Sever 12c (WLS 126.96.36.199.0) was released on 11 July 2013. Since I read lots of documents, announcements, and information regarding this new version, I want to inform you about some new features that have an impact and/or changed my daily work as a WebLogic Server administrator.
Some general information
Here are a couple of new features that are good to know even if I do not use them for the time being. For instance, although I am not a developer, knowing that the zipped software package size for the developer is only 168 mb instead of 1 gb for the full 11g distribution can help when you have to install it.
Let’s list some of these new features:
- WLS 12.1.2 has been designed and optimized to be deployed for a conventional System, an Engineered System, and obviously for the private and public cloud (the “c” letter after the 12).
- The development is also simplified: there are less classes, less coding, and less XML files – meaning more development productivity. You can develop your application and deploy it to the normal hardware platform. Later on, in case this is needed, you can deploy it to your private or to the public cloud.
- WLS 12c is also integrated and has been optimized for Oracle Traffic Director – the Oracle load balancer software. And you can always use the Apache or Oracle http plugin.
- Full support for Java SE6 and Java SE7
- Performance optimization with Active GridLink for Oracle Real Application Cluster (RAC)
- WLS 12c works with the Oracle Database 12c pluggable databases
- Better performance with Exalogic
- Oracle Coherence can be managed using the WebLogic Framework: You can therefore use the WLS administration console, WLST, the JMX framework, the FMW admin console and the Enterprise Manager Cloud Control console.
For your daily WebLogic tasks
Now it is time to list some new features that may help you in your daily WebLogic Server Administrator tasks.
With the WLS version prior to 12.1.2, it was necessary to define the managed server, the listen port, the machines, and add the servers to the cluster (etc.) before building a cluster. With the new version, it should be very easy to manage a cluster as the definition of the ports, server names, machine configurations (etc.) is automated. Also, we can assign all the requested resources in the cluster as a single dynamic entity.
Unified Installation and Patching Framework
Prior to release 12.1.2, we had to use the BEA technologie to install patches. Now, the installation has been standardized for Oracle patching tools.
Flexible Scaling of Java Messaing Services (JMS)
Before 12.1.2, JMS and associated file store had to be targeted to each Managed Server within the cluster. Now you can target the JMS and the file stores directly to a cluster.
Upgrade path and tools to use
- Reconfiguration Wizard tool – you can perform the upgrade accross multiple releases:
9.2 -> 10gR3 -> 11g -> 12c
- SmartUpgrade tool to upgrade an Oracle Internet Application Server 10gR2 and 10gR3 to WLS12c
- Glassfish Web deployment descriptors to redeploy GlassFish application to WLS12c
- Migration Services to migrate JBoss and WebSphere to WLS12c
In the next couple of weeks, I will test the new features and hope they will make my work easier!
Another tool I am using is Oracle Enterprise Manager Cloud Control 12c. There is also an new release (OEM 12cR3) which I will look into to discover its advantages and benefits. Let’s see!