Skip to main content

WebLogic Admin Console

WebLogic Admin Console

The WebLogic Admin Console is a web-based, user interface used to configure and control a set of WebLogic servers or clusters (i.e. a "domain"). In any logical group of WebLogic servers there must exist one admin server, which hosts the WebLogic Admin Console application and manages the associated configuration files.

WebLogic Administrators will use the Administration Console for a number of tasks, including:
  • Starting and stopping WebLogic servers or entire clusters.
  • Configuring server parameters, security, database connections and deployed applications.
  • Viewing server status, health and metrics.
Note: It is not strictly necessary to use the Weblogic Admin Console to perform these tasks, as they can be scripted using WLST (the WebLogic Scripting Tool).

Accessing the Admin Console

WebLogic Admin Console Url: http://hostname:port/console.

To access the WebLogic Administration Console, assuming the admin server has been started, goto the above url. Where hostname and port is the listen address/port specified when creating the WebLogic domain. Eg. http://localhost:7001/console.

Evolution of the WebLogic Admin Console

The Weblogic Admin Console has changed considerably in the time since it was first included in the WebLogic product. Early WebLogic versions (prior to version 6) did not have an administration console. Its initial form was fairly consistent from version 6 through 8 (example below).


With the introduction of WebLogic 9, the Administration Console was completely redesigned. Now using WebLogic Portal technologies it was more customizable and featured better configuration control. A common complaint from users moving to the newer version was its slower performance and need for more memory.



The latest versions of the WebLogic Admin Console have been rebranded (BEA was aquired by Oracle) and a number of usability improvements have been made.


Learning to use the Administration Console

Oracle provides a number of introductry articles in the WebLogic documentation (see links below). There are also a number of WebLogic Administration courses offered by Oracle and training vendors.

Disabling the Admin Console

By default the WebLogic Admin Console is enabled. For security reasons, you may require to disable it. This can be done by executing the following WLST script (WebLogic 8.1 SP6 or later).

connect("t3://hostname:port", "username","password")
edit()
startEdit()
cmo.setConsoleEnabled(false)
save()
activate()
disconnect()

Note: You will need to restart the admin server for this to take effect.

References

http://download.oracle.com/docs/cd/E13222_01/wls/docs90/intro/console.html
http://download.oracle.com/docs/cd/E13222_01/wls/docs60/notes/new.html

Labels:

Comments

Post a Comment

Popular posts from this blog

NullPointerException

java.lang.NullPointerException NullPointerException is described in the javadoc comments as: Thrown when an application attempts to use null in a case where an object is required. These include: Calling the instance method of a null object. Accessing or modifying the field of a null object. Taking the length of null as if it were an array. Accessing or modifying the slots of null as if it were an array. Throwing null as if it were a Throwable value. Applications should throw instances of this class to indicate other illegal uses of the null object. author: unascribed version: 1.19, 12/19/03 since: JDK1.0 Where is this exception thrown? Following, is a list of exception messages cross-referenced to the source code responsible for throwing them. Click on the method link to view the code and see how the exception is thrown. The message ' java.lang.NullPointerException: ' is thrown within the method: com.sun.corba.se.impl.interceptors.ClientRequestInfoImpl.get_r
Post a Comment
Read more

Connection refused: No available router to destination

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators. Symptom The following exception occurs in WebLogic server logs. Most likely to occur during WebLogic server start-up, but similar exceptions may occur at other times. java.net.ConnectException: t3://myserver:8000: Destination unreachable; nested exception is: java.net.ConnectException: Connection refused: connect; No available router to destination] at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:49) at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:773) at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:363) at weblogic.jndi.Environment.getContext(Environment.java:307) at weblogic.jndi.Environment.getContext(Environment.java:277) Cause This message (Connection refused: connect; No available
Post a Comment
Read more

Recovering WebLogic Passwords

In one of my previous articles ( here ) I explained that the SerializedSystemIni.dat file in WebLogic contains the key used to encrypt and decrypt passwords. If you're not currently keeping this file secure I suggest you do, as with it someone can (to name a few things): Decrypt the WebLogic admin username and password from boot.properties. Recover database passwords, if JDBC Connection pools are configured, from config.xml. Recover the keystore passwords from config.xml and obtain SSL certificates stored in the jks keystores. Essentially, they can do whatever they want, so if you don't know who can read your SerializedSystemIni.dat files, look... now. In this article I will show how easy it is for this file to be used to recover lost passwords via a simple WLST script. The Script The script I use to decrypt passwords is incredibly short, and it works with WebLogic 8, 9 and 10 (probably for version 7 too). To use it, just create a new file called decryptpwd.py and paste the fol
16 comments
Read more