This chapter includes the following sections:
This document describes how you use WebLogic Server logging services to monitor server, subsystem, and application events. It explains how you configure WebLogic Server to write messages to log files and listen for the log messages that WebLogic Server broadcasts. It also describes how to view log messages through the WebLogic Server Administration Console.
This document is a resource for system administrators who configure WebLogic logging services and monitor server and subsystem events, and for Java Platform, Enterprise Edition (Java EE) application developers who want to integrate their application logs with WebLogic Server logs. This document is relevant to all phases of a software project, from development through test and production phases.
This document does not address application logging or localization and internationalization of log message catalogs. For links to information on these topics, see Related Documentation.
It is assumed that the reader is familiar with Java EE and Web technologies, object-oriented programming techniques, and the Java programming language.
The document is organized as follows:
Introduction and Roadmap describes the scope of this guide and lists related documentation.
Understanding WebLogic Logging Services discusses the logging process, log files, and log messages.
Configuring WebLogic Logging Services describes basic configuration scenarios and tasks.
Filtering WebLogic Server Log Messages describes how to specify which types of messages WebLogic Server writes to its logs and to standard out.
Subscribing to Messages describes how WebLogic Server instantiates and subscribes a set of message handlers that receive and print log messages.
The corporate Web site provides all documentation for WebLogic Server. Specifically, View and configure logs in Oracle WebLogic Server Administration Console Online Help describes how to view and configure log files that a WebLogic Server instance generates, and Using Message Catalogs with WebLogic Server in Adding WebLogic Logging Services to Applications Deployed on Oracle WebLogic Server describes how you can use WebLogic Server message catalogs, non-catalog logging, and servlet logging to produce log messages from your application or a remote Java client, and describes WebLogic's support for internationalization and localization of log messages.
In addition to this document, Oracle provides a variety of logging code samples that show logging configuration and API use.
MedRec is an end-to-end sample Java EE application shipped with WebLogic Server that simulates an independent, centralized medical record management system. The MedRec application provides a framework for patients, doctors, and administrators to manage patient data using a variety of different clients.
MedRec demonstrates WebLogic Server and Java EE features, and highlights recommended best practices. MedRec is optionally installed with the WebLogic Server installation. You can start MedRec from the
\user_projects\domains\medrec directory, where
ORACLE_HOME is the directory you specified as Oracle Home when you installed Oracle WebLogic Server. For more information, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.
The MedRec domain installed with WebLogic Server is configured to enable Log4j logging. Several action classes and MedRec utility classes use the
weblogic.logging.log4j.Log4jLoggingHelper class to create a new logger, access a Log4j Appender, and register the Appender with the logger. Classes extending the base classes then use the logger to write informational messages to the WebLogic Server log file.
WebLogic Server optionally installs API code examples in
ORACLE_HOME represents the directory in which you installed WebLogic Server. For more information about the WebLogic Server code examples, see Sample Applications and Code Examples in Understanding Oracle WebLogic Server.
In this release of WebLogic Server, you can configure
java.util.logging logger levels. This allows you to use the
java.util.logging APIs to log messages without having to manage the logging configuration. For more information, see Configuring java.util.logging Logger Levels.
Additionally, the Server Logging Bridge has been added to the root logger of the
java.util.logging logger tree when WebLogic Server starts. This eliminates the need to explicitly configure the Server Logging Bridge in your environment.
The use of Log4j, as an alternative to Java logging, with the WebLogic logging service is deprecated as of WebLogic Server 12.1.3.
For a comprehensive listing of the new WebLogic Server features introduced in this release, see What’s New in Oracle WebLogic Server 220.127.116.11.0.