About This Online Help

About This Online Help

About This Online Help

This help guide describes how to use the BEA® Log Central application to manage log messages. The guide is organized as follows:

Overview describes the Log Central architecture.
Introducing the Log Central Console explains how to start the Log Central Console.
Managing Log Messages explains how to monitor log messages.
Changing Message Definitions and Subsystem Descriptions explains how to modify message definitions and subsystem descriptions.
Generating Reports explains how to generate reports.
Configuring SNMP Traps explains how to configure SNMP traps.
Managing the Database and Intermediate Files explains how to manage database files and intermediate files.
Testing and Debugging explains how to test and debug.
Log Central Message and Message Definition Formats describes the Log Central message format.
Commands describes the Log Central commands.
SNMP Traps describes the SNMP traps that Log Central defines.

What You Need to Know

This document is written for system administrators and network administrators who set up and manage Log Central. It assumes a working knowledge of relational databases and JDBC. If you use the SNMP feature, then you also need to have a working knowledge of SNMP.

e-docs Web Site

BEA product documentation is available on the BEA corporate Web site. From the BEA Home page, click Product Documentation or go directly to the e-docs Product Documentation page at http://www.oracle.com/technology/documentation/index.html.

How to Print the Document

You can print a copy of this document from a Web browser, one file at a time, by using the File—>Print option on your Web browser. (Be sure to first click anywhere within the HTML content frame you want to print, so that that frame is selected.)

The Log Central Online Help is also available as a PDF in the Log Central online documentation set, which is available on the e-docs Web site and also on the Log Central product CD. You can open the PDF in Adobe Acrobat Reader and print the entire document (or a portion of it) in book format. To access the PDFs, open the Log Central documentation Home page, click the PDF files button and select the document you want to print.

If you do not have the Adobe Acrobat Reader, you can get it for free from the Adobe Web site at http://www.adobe.com/.

Related Information

For more information about Log Central, see the Log Central online documentation set which is available on the Log Central product CD and at the e-docs Product Documentation page at http://www.oracle.com/technology/documentation/index.html.

Contact Us!

Your feedback on the BEA Log Central documentation is important to us. Send us e-mail at docsupport@bea.com if you have questions or comments. Your comments will be reviewed directly by the BEA professionals who create and update the Log Central documentation.

In your e-mail message, please indicate that you are using the documentation for the BEA Log Central 5.0 release.

If you have any questions about this version of BEA Log Central, or if you have problems installing and running BEA Log Central, contact BEA Customer Support through BEA WebSupport at http://www.bea.com. You can also contact Customer Support by using the contact information provided on the Customer Support Card, which is included in the product package.

When contacting Customer Support, be prepared to provide the following information:

Your name, e-mail address, phone number, and fax number
Your company name and company address
Your machine type and authorization codes
The name and version of the product you are using
A description of the problem and the content of pertinent error messages

Documentation Conventions

The following documentation conventions are used throughout this document.

Convention
Item

boldface text

Indicates terms defined in the glossary.

Ctrl+Tab

Indicates that you must press two or more keys simultaneously.

italics

Indicates emphasis or book titles.

monospace text

Indicates code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard.
Examples:
#include <iostream.h> void main ( ) the pointer psz
chmod u+w *
\tux\data\ap
.doc
tux.doc
BITMAP
float

monospace boldface text

Identifies significant words in code.
Example:
void commit ( )

monospace italic text

Identifies variables in code.
Example:
String expr

UPPERCASE TEXT

Indicates device names, environment variables, and logical operators.
Examples:
LPT1
SIGNON
OR

{ }

Indicates a set of choices in a syntax line. The braces themselves should never be typed.

[ ]

Indicates optional items in a syntax line. The brackets themselves should never be typed.
Example:
buildobjclient [-v] [-o name] [-f file-list]... [-l file-list]...

|

Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.

...

Indicates one of the following in a command line:
That an argument can be repeated several times in a command line
That the statement omits additional optional arguments
That you can enter additional parameters, values, or other information
The ellipsis itself should never be typed.
Example:
buildobjclient [-v] [-o name] [-f file-list]... [-l file-list]...

.
.
.

Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.

Convention	Item
boldface text	Indicates terms defined in the glossary.
Ctrl+Tab	Indicates that you must press two or more keys simultaneously.
italics	Indicates emphasis or book titles.
monospace text	Indicates code samples, commands and their options, data structures and their members, data types, directories, and file names and their extensions. Monospace text also indicates text that you must enter from the keyboard. Examples: #include <iostream.h> void main ( ) the pointer psz chmod u+w * \tux\data\ap .doc tux.doc BITMAP float
monospace boldface text	Identifies significant words in code. Example: void commit ( )
`monospace italic text`	Identifies variables in code. Example: String `expr`
UPPERCASE TEXT	Indicates device names, environment variables, and logical operators. Examples: LPT1 SIGNON OR
{ }	Indicates a set of choices in a syntax line. The braces themselves should never be typed.
[ ]	Indicates optional items in a syntax line. The brackets themselves should never be typed. Example: buildobjclient [-v] [-o name] [-f `file-list`]... [-l `file-list`]...
\|	Separates mutually exclusive choices in a syntax line. The symbol itself should never be typed.
...	Indicates one of the following in a command line: That an argument can be repeated several times in a command line That the statement omits additional optional arguments That you can enter additional parameters, values, or other information The ellipsis itself should never be typed. Example: buildobjclient [-v] [-o name] [-f `file-list`]... [-l `file-list`]...
. . .	Indicates the omission of items from a code example or from a syntax line. The vertical ellipsis itself should never be typed.