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

Comments

Popular posts from this blog

BAD_CERTIFICATE - A corrupt or unuseable certificate...

This is a simple symptom-cause-solution blog entry only. I hope these blogs will help fellow administrators.
Symptom
In wls_utc, when trying to test a webservice using SSL, the following error message is received: javax.net.ssl.SSLKeyException: FATAL Alert:BAD_CERTIFICATE - A corrupt or unuseable certificate was received.
If SSL debugging is enabled, the following error also appears in the logs: ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)' <1254822672320>>
verification failed because RSA key public exponent [3] is too small
Cause
The certificate encryption is of a weaker strength than expected by newer versions of Java.
Solution
Add the flag "-Dweblogic.security.SSL.allowSmallRSAExponent=true" to the server startup parameters.
References


None.

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 router to destination) is a kind of "catch…

BEASVC.EXE - WebLogic as a Windows Service

I remember the first time I had to work out why WebLogic wouldn't run as a service. It was a frustrating experience. There were no error messages. No Windows error dialog. No console output.

How do you troubleshoot something like this??!!

This short article will show you. For simplicity I'll talk about the node manager, but the same principles apply for running an admin or managed server as a service.

First Steps

First, you still have your server logs. Sure the console output is better, but it's a starting point. Check this log for errors and especially take note of the start up variables such as PATH and CLASSPATH. If the server log isn't being created, that tells you WebLogic probably isn't even being started. (Check that you have a license file if you haven't already.)

Ok, so the logs were no help. The next step is to look at how the service is trying to start WebLogic.

When you install WebLogic as a service, you're really setting up beasvc.exe as the service.…