Since its first version, Weblogic has had a great numbers of features that has just been growing over the years. As new Weblogic versions are being released, some of these features get slowly forgotten while the new ones get the spotlight . Here is a list of  5 Weblogic features, old and new, that you probably haven’t heard of.

Number 5: Accessing Weblogic logs via Rest

What is it about ?

Everybody is doing REST right now, why shouldn’t you? This new 12c Weblogic feature lets you  access several different server logs using a simple REST API.

When to use it ?

The most common scenario is when somebody wants to access the log files but doesn’t have access to the physical server. Also if you want an automated process to check the logs and react based on some entries. Even machine learning could be an interesting topic for this feature: https://logz.io/blog/machine-learning-log-analytics/

How to use it?

First enable the Enable the RESTful management interface. Then use one of the provided URLs (like this one for example: http://localhost:7001/management/wls/latest/servers/id/AdminServer/logs/id/ServerLog) to access the logs.

More information

  • https://docs.oracle.com/middleware/1221/wls/WLRUR/overview.htm
  • http://www.munzandmore.com/2015/ora/log-files-restful-management

Number 4: Callbacks for JDBC connection initialization

What is it about ?

This one is a very technical feature. It allows you to add your custom code every time  Weblogic initializes a JDBC connection.

When to use it

This feature was implemented to support the Application Continuity (AC) by allowing to re-initialize the JDBC connection with the desired state. It centralizes this configuration in order to have it in the datasource and not spread across different applications.

How to use it?

First create a Java Class that implements the oracle.ucp.jdbc.ConnectionInitializationCallback interface. Then package the class and put it in the classpath. Finally, registered on the datasource configuration page.

More information

 

Number 3: Weblogic Classloading Analysis Tool

What is it about?

This application lets you view at runtime if a class was loaded, by which classloader and from which jar.

When to use it?

If you are having classpath problems or in other words, if you are in the middle of JAR Hell. Rather than analysing the start parameters, you can use this tool if you have to be sure if a class was loaded  and from which jar it is being referenced.

How to use it?

CAT (Classloading Analysis Tool) needs to be deployed before using it. It is a simple WAR and it can be found under ‚WL_HOME/server/lib/wls-cat.war‘. Afterwards it can be access under ‚http://wls-host:port/wls-cat/‘

More information

 

Number 2: Support for Glassfish deployment descriptors

What is it about?

Every JEE application has to deliver specific deployment descriptors in order to be deployed to the target application server. WebLogic Server offers support for a subset of GlassFish deployment descriptors meaning that you can take your already working JEE application from Glassfish to Weblogic. In most cases.

When to use it?

In case you need to deploy a Glassfish application into Weblogic. The documentation is clear that only a subset is supported, so it is recommendable to test the deployment first.

How to use it?

Just deploy your Glassfish application in Weblogic. And hope it works !!

More information

 

Number 1: Panic Action

What is it about?

Apart of having a flashy and attractive name, this one could really save your system if your server becomes overloaded. Its main objective is to act on faulty states by providing an action that will be executed if one of those states occurs. In case of a Stuckthread or an Out-Of-Memory exception, you can instruct your server to shutdown itself. Also, with the proper configuration on the Nodemanager,  the server will restart itself without any human intervention.

When to use it?

This one should actually be part of a checklist after a Weblogic domain has been configured. It is a task of the administrator to define in which scenarios he actually wants the server to restart automatically. But with it, he can easily say goodbye to the servers in a fault state that cannot work but are still alive.

How to use it?

Fitsr go to Environment -> Servers in the Weblogic console. Choose the server that you want to configure and go to ‚Overload‘ in the Configuration Tab. You can also use WLST to do this change.

More information