This document describes how you use WebLogic Server logging services to monitor application events. It describes WebLogic support for internationalization and localization of log messages, and shows you how to use the templates and tools provided with WebLogic Server to create or edit message catalogs that are locale-specific.
This section describes the contents and organization of this guide—Using Oracle WebLogic Logging Services for Application Logging.
This document is a resource for Java Platform, Enterprise Edition (Java EE) application developers who want to use WebLogic message catalogs and logging services as a way for their applications to produce log messages and 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 how you configure logging, subscribe to and filter log messages. 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:
Chapter 1, "Introduction and Roadmap," describes the scope of this guide and lists related documentation.
Chapter 2, "Application Logging and WebLogic Logging Services," discusses how to use WebLogic logging services to monitor application events.
Chapter 3, "Internationalization and Localization for WebLogic Server," summarizes the processes required for internationalization and localization.
Chapter 4, "Using Message Catalogs with WebLogic Server," describes message catalog types, message definitions, elements, and arguments.
Chapter 5, "Writing Messages to the WebLogic Server Log," describes how to create and use message catalogs and how to use the
NonCatalogLogger class to write log messages.
Chapter 6, "Using the WebLogic Server Message Editor," explains how to use the Message Editor that is included with WebLogic Server.
Chapter 7, "Using the WebLogic Server Internationalization Utilities," explains how to use the internationalization utilities included with WebLogic Server.
Appendix A, "Localizer Class Reference for WebLogic Server," describes
Localizer methods, key values for
Localizers, and lookup properties for
Appendix B, "Loggable Object Reference for WebLogic Server," describes
loggable objects and how they are used.
Appendix C, "TextFormatter Class Reference for WebLogic Server," provides an example of an application that uses a
Appendix D, "Logger Class Reference for WebLogic Server," describes
Logger classes and provides an example of a message catalog and its corresponding
The corporate Web site provides all documentation for WebLogic Server. Specifically, "View and configure logs" in the Oracle WebLogic Server Administration Console Online Help describes configuring log files and log messages that a WebLogic Server instance generates, and Configuring Log Files and Filtering Log Messages for Oracle WebLogic Server describes configuring WebLogic Server to write messages to log files, filtering message output, and listening for the log messages that WebLogic Server broadcasts.
For general information about internationalization and localization, refer to the following sources:
In addition to this document, we provide a variety of logging code samples and tutorials 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 included in the WebLogic Server distribution, and can be accessed from the Start menu on Windows machines. For Linux and other platforms, you can start MedRec from the
\samples\domains\medrec directory, where
WL_HOME is the top-level installation directory for WebLogic Server.
WebLogic Server optionally installs API code examples in
WL_HOME is the top-level directory of your WebLogic Server installation. You can start the examples server, and obtain information about the samples and how to run them from the WebLogic Server Start menu.
This example shows various methods for displaying localized text using simple message catalogs. Using any of the languages supported by the example requires the appropriate operating system localization software and character encoding. The package that contains this example is:
java examples.i18n.simple.HelloWorld [lang [country]]
lang is a two-character ISO language code (for example, en for English) and
country is a two-character ISO country code (for example, US for the United States).
The files are located in
WL_HOME is the top-level directory of your WebLogic Server installation. The default path is
c:\Oracle\Middleware\wlserver_12.1, however, you are not required to install this directory in the Oracle Middleware Home directory,
For a comprehensive listing of the new WebLogic Server features introduced in this release, see What's New in Oracle WebLogic Server.