Technical data
9 Monitoring a WebLogic Server Domain
9-4 Configuring and Managing WebLogic Server
If you start a Managed Server with Node Manager, Node Manager redirects the
server instance’s standard error to a file. In this case, you can view the Managed
Server’s output using
Domain→Server→Remote Start Output→View Server error output.
! Server Logs—Each WebLogic Server instance writes all messages from its
subsystems and applications to a log file on its host machine. You can configure
logging behavior using the Server
→Logging→Server tab. You can view a server
instance’s log file using the View server log link on any server tabs page.
! Domain Log—By default, each server instance in a domain forwards all
messages from its subsystems and applications to the Administration Server for
the domain. The Administration Server writes a subset of the messages to the
Domain Log. You can control whether or not a server instance sends its
messages to the Administration Server, and configure filters that control which
messages it sends using the Server
→Logging→Domain tab. You can view the
Domain Log using the View domain log link on any domain tab page.
! Node Manager Logs—Node Manager writes startup and status messages to a
log file in the
NodeManagerLogs\NodeManagerInternal subdirectory. Node
Manager log files are named
NodeManagerInternal_timestamp,where
timestamp indicates the time at which Node Manager started.
! HTTP Logs—By default, each server instance maintains a log of HTTP
requests. You can disable HTTP logging, or configure logging behavior using
the Server
→Logging→HTTP tab.
! JTA Logs—You can configure a server instance to maintain a JTA transaction
log using the Server
→Logging→JTA tab.
! JDBC Logs—You can configure a server instance to maintain a JDBC log using
the Server
→Logging→JDBC tab.