According to Wikipedia the first Weblogic version was released in November 1997 by the name of  „WebLogic Tengah“ (happy 20th Birthday mate !!!). With so much history behind, it is difficult to elaborate a list with only 5 not so popular features. But since the first article was getting pretty big and you readers don’t like to scroll much, here is a list of 5 more Weblogic features your probably didn’t know.

Number 5: The Weblogic Session Cookies

What is it about ?

Let’s start with an easy one. With this feature you can define how Weblogic stores the admin console session cookies in the browser.

When to use it ?

Have you ever had to work with two or more Weblogic admin consoles in the same browser? In those cases you will experience how your session gets immediately invalidated the moment you switch between consoles. The reason behind this phenomenon is that Weblogic stores the session cookies with the same name. Use this feature to change the name and you will be able to work with multiple admin consoles in the same browser.

How to use it?

Configure a different cookie name for each of your domains. To do this simple go to administration console -> domain -> general -> advanced and change the ‚console cookie name‘.

More information

 

Number 4: JNDI Tree Console

What is it about ?

Sometimes overlooked, Weblogic lets you view the JNDI Tree of the managed servers (also the admin server) in order to check the registered objects. It will also let you secure the whole JNDI tree or just parts of it.

When to use it

Every time you get a NameNotFoundException but you are sure you used the correct JNDI name or if you want to check under what name your resource got registered. Also, as mentioned above, you can secure the whole JNDI tree or only some branches in order to avoid unauthorized access.

How to use it?

In the Weblogic admin console, go to Environment -> Servers and pick one server. There you can see the ‚View JNDI Tree ‚ link. In this console you can navigate the tree and check out the registered objects. Take a look at my other blog to see how to secure the JNDI tree.

More information

 

Number 3: Rebranding of the Weblogic Admin Console

What is it about?

Weblogic lets you change the look and feel of some of the administration console components by developing an additional console extension.

When to use it?

This is very practical if you are operating multiple Weblogic domains and want to distinguish them right away. Simply changing some layout colors will let you quickly identify the domain you are working on. It is always better to be completely sure that the changes you are doing are in the correct domain. Also, you can use this extension to customize to replace the Oracle logos with the ones from your enterprise.

How to use it?

First expand the ‚look and feel‘ template using Apache Ant. Then modify the logs and stylesheets according to your need. Afterwards create a NetUI extension which is like a deployment descriptor for this extension. Finally, package the extension into a WAR file and deploy it.

More information

 

Number 2: Weblogic smart rules

What is it about?

Weblogic smart rules are one of the most interesting parts of the  Weblogic Diagnostic Framework (WLDF). This feature provides a set of predefined rules that represent the most common monitored events in Weblogic domains. Based on this rules you can define actions that get executed if the correspondent rule was not fulfilled. Also, it allows you to define your own generic rule  based on Weblogic MBeans or costume ones.

When to use it?

No Cloud Control or Nagios? Don’t worry. Smart rules provide a very complete set of options to build a lightweight monitoring system for your Weblogic domain. You can automatically send emails if an interesting event happens such as  Stuckthreads or overloaded datasources.

How to use it?

Smart rules are comprised of two things: actions and policies. Policies are the events that are being monitored, like „High Average Stuck Threads“. If a policy is not fulfilled, then the action will be executed. Actions include sending an email, creating a Thread Dump or executing a custom script.

More information

 

Number 1: Harvester

What is it about?

Similar to number 2, this component is part of WLDF and is used to monitor running domains. The main idea of the havester is to collect information form the different mbeans over a specific period of time.

When to use it?

Use this if you have some metrics based on Weblogic MBeans or custom MBeans. Let the harvester collect the data and watch it later on the Monitoring Dashboard.

How to use it?

To configure the harvester you need a Diagnostic Module which you can create in the admin console or with WLST. After that you can got to the ‚Collected Metrics‘ tab to define your haverster. You can either choose one MBean that Weblogic provides or a custom one. Once you defined your harvesters, you can use the Monitorig Dashboard to track them.

More information