Technical data

Facilities for Monitoring WebLogic Server

Configuring and Managing WebLogic Server 9-3

Obtaining Server Health Programmatically

You can check the self-reported health state of a server instance programmatically by

calling the

getHealthState() method on the ServerRuntimeMBean. Similarly, you

can obtain the health state of a registered WebLogic Server subsystem by calling the

getHealthState() method on its MBean. The following MBeans automatically

! JMSRuntimeMBean

! JMSServerRuntimeMBean

! JTARuntimeMBean

! TransactionResourceRuntimeMBean

See the Javadocs for WebLogic Classes for more information on individual MBeans.

Messages and Log Files

WebLogic Server records information about events such as configuration changes,

deployment of applications, and subsystem failures in log files. The information in log

files is useful for detecting and troubleshooting problems, and monitoring performance

and availability.

For detailed information about log files and the WebLogic Server logging subsystem,

see “Logging” in Administration Console Online Help.

WebLogic Server outputs status and error messages to:

! Standard Out—By default, a WebLogic Server instance prints all messages of

WARNING severity or higher to standard out—typically the command shell

window in which you are running the server instance. You can control what

messages a server instance writes to standard out using the Server

→Logging tab.

If you start a Managed Server with Node Manager, Node Manager redirects the

server instance’s standard out to a file. In this case, you can view the Managed

Server’s output using

Domain→Server→Remote Start Output→View Server output.

! Standard Error—A WebLogic Server instance writes errors to standard error—

typically the command shell window in which you are running the server

instance.