BEA Logo BEA Log Central Release 5.0

  Corporate Info  |  News  |  Solutions  |  Products  |  Partners  |  Services  |  Events  |  Download  |  How To Buy

 

   Log Central Doc Home   |   Configuration Guide   |   Previous Topic   |   Next Topic   |   Contents   |   Index

Configuration Files

 

The following sections describe the Log Central configuration files:

Messaging Configuration File

Trap Configuration File

 


Messaging Configuration File

The following sections describe the messaging configuration file:

Overview of the Messaging Configuration File

Example Messaging Configuration File

LC_GLOBAL

MANAGED_NODE

DEFINE_FILTER

DEFINE_MSG_MAPPINGS

DEFINE_LOG_MONITOR

Overview of the Messaging Configuration File

The default Log Central messaging configuration file is install_dir/etc/messaging.conf, where install_dir is the directory where you installed Log Central. You can specify a different file when you run lc_config, which is described in Commands. If you use a nondefault location, set the BEA_LC_HOST_CONF environment variable, which is described in Environment Variables.

The messaging configuration file must include the LC_GLOBAL entry and can also include the following optional entries:

Do not use tabs in the messaging configuration file. They can cause the character positions reported to be inaccurate.

Example Messaging Configuration File

DEFINE_FILTER "BankTrap"
if (MSGID == 11)
{
TRAPID = 5001
}

DEFINE_FILTER "DropInfo"
if (MSGID == 8)
{
REMOTE = "NO"
}

DEFINE_FILTER "Notify"
if (MSGBODY >= "network")
{
COMMAND = "/usr/mybin/notify_admin"
}

LC_GLOBAL
{
CENTRAL_HOST = "MyHost"
LOGPREFIX = "/usr/lclog"
BACKUP_HOST = "MyBackup"
BACKUP_LOGPREFIX = "/usr/backuplog"
FILTER = "BankTrap"
}

MANAGED_NODE
{
HOSTNAME = "MyNode"
FILTER = "DropInfo"
FILTER = "Notify"
GLOBAL_FILTER = "NO"
LOG_MONITOR="MyLogMonitor"
}

DEFINE_MSG_MAPPINGS "MyMappings"
{
MAPPING = "-S |! -o %F8 -p sony -b %F12 -T %F10"
MAPPING = "-S |! -I %F6 -u %F7 -b %F11 -x error"
MAPPING = "-S |! -m %F3%V=%C30S| -n %F8%F10 -b %F11 -D %F2"
}

DEFINE_LOG_MONITOR "MyLogMonitor"
{
LOG_FILENAME = "MyLogFile.txt"
MSG_MAPPING = "MyMappings"
MONITORING_INTERVAL = 2
FIRST_MATCH = "YES"
SELECT_PATTERN = "error"
DISCARD_PATTERN = "ttyp0"
}

LC_GLOBAL

At the minimum, the messaging configuration file must contain an LC_GLOBAL entry with CENTRAL_HOST and LOGPREFIX statements. The LC_GLOBAL entry configures parameters for the central host and all managed nodes. The following table describes the statements in an LC_GLOBAL entry.

Table G-1 LC_GLOBAL Statements

Statement

Data Type

Optional

Description

BACKUP_HOST

String

Optional

Name of the machine that the secondary Central Collector runs on. This value can include dots, underscores, and dashes.

BACKUP_LOGPREFIX

String

Optional

LOGPREFIX value for the secondary Central Collector. If this directory is on a remote file system, Log Central performance can be adversely affected.

CENTRAL_HOST

String

Not optional

Name of the central host. This value can include dots, underscores, and dashes.

ESCALATION_DIR

String

Optional

Directory for temporary log files on managed nodes. If this directory is on a remote file system, Log Central performance can be adversely affected. On UNIX, the default is /tmp. On Windows NT, the default is the directory specified by the TMP environment variable, which usually specifies C:\tmp. To determine the value of TMP on your system, run the SET TMP command.

FILTER

String

Optional

Name of a global filter. You can include multiple FILTER statements. For information about filtering, see Creating Filters.

INIFILE

String

Optional

Log Central initialization file. The default is install_dir/etc/msg_processor.ini, where install_dir is the directory where you installed Log Central. You can specify a different file when you run lc_config. For the command syntax, see Commands. For a description of the initialization file, see Initialization File.

IPCKEY

String

Optional

Interprocess communication (IPC) key for Log Central. If you are running multiple Log Central systems, each system needs a different value for its IPC key. IPCKEY must be the same as BEA_LC_IPCKEY. The default is 0xeeee0000. For more information about BEA_LC_IPCKEY, see Environment Variables.

LOGPREFIX

String

Not optional

Directory and file prefix for the intermediate files that the Message Receiver creates. If the directory is on a remote file system, Log Central performance can be adversely affected.

TALK_SERVICE

String

Optional

Communication service that the Message Senders and Message Receiver use to communicate with each other. The default is lc_talk. For more information about how to configure communication services, see Configuring the Central Host, and Configuring Multiple Instances of Log Central.

MANAGED_NODE

The MANAGED_NODE entry is a list of filter assignments for a managed node. A MANAGED_NODE entry is required only if you want to specify non-global filters or if you want to start Log Monitors automatically when you start Log Central. No more than one MANAGED_NODE entry may be specified for each managed node. The following table describes the statements in a MANAGED_NODE entry.

Table G-2 MANAGED_NODE Statements

Statement

Data Type

Optional

Description

FILTER

String

Optional

Name of a local filter. You can include multiple FILTER statements. For information about filtering, see Creating Filters.

GLOBAL_FILTER

String

Optional

Indicates whether or not to turn off global filters for the managed node. Possible values:

YES = Turn on global filters for this node.

NO = Turn off global filters for this node.

The default is NO.

HOSTNAME

String

Not optional

Central host for this managed node. This value can include dots, underscores, and dashes.

LOG_MONITOR

String

Optional

Name of a Log Monitor defined by a DEFINE_LOG_MONITOR entry. The MANAGED_NODE entry can contain multiple LOG_MONITOR statements. Include this statement only for Log Monitors that you want to start automatically when you start Log Central with the start_messaging command, which is described in Commands.

DEFINE_FILTER

For information about the DEFINE_FILTER statement, see Creating Filters.

Note: The maximum number of filters that you can define is 50. If the messaging configuration file contains more than 50 filters, the Log Central behavior becomes unpredictable.

DEFINE_MSG_MAPPINGS

The DEFINE_MSG_MAPPINGS entry is a list of log mappings. For information about log mappings, see Creating Log Mappings.

The following rules apply to the name of the DEFINE_MSG_MAPPINGS entry. The entry:

The following rules apply to each MAPPING statement. The statement:

DEFINE_LOG_MONITOR

The DEFINE_LOG_MONITOR entry configures parameters for a Log Monitor.

The following rules apply to the name of the DEFINE_LOG_MONITOR entry:

The following table describes the statements in a DEFINE_LOG_MONITOR entry.

Table G-3 DEFINE_LOG_MONITOR Statements

Statement

Data Type

Optional

Description

LOG_FILENAME

String

Not optional

Name of the log file that the Log Monitor is monitoring. It can be up to 256 characters long.

MSG_MAPPING

String

Not optional

Name of the DEFINE_MSG_MAPPINGS entry to use.

MONITORING_
INTERVAL

Integer

Optional

Length of time to wait between forwarding each log message. The default is one second. Use 0 to forward once and then stop. Using 0 causes the Log Monitor to run as a daemon.

FIRST_MATCH

String

Optional

Flag that indicates whether or not to apply the log mappings to a log message only up to the first match. Possible values:

YES = Apply the log mappings only up to the first match.

NO = Apply the log mappings to the entire log message.

The default is NO.

SELECT_PATTERN

String

Optional

Tells the Log Monitor to forward a log message only if it contains the specified pattern. This value is the same as the -p mapping option which is described in Creating Log Mappings.

DISCARD_PATTERN

String

Optional

Tells the Log Monitor to discard a log message if it contains the specified pattern. The message can still be forwarded if it satisfies another mapping in the messaging configuration file. This value is the same as the -x mapping option which is described in Creating Log Mappings.

 


Trap Configuration File

The following sections describe the trap configuration file:

Overview of the Trap Configuration File

Example Trap Configuration File

TRAP_HOST

Overview of the Trap Configuration File

On UNIX, the default Log Central trap configuration file is /etc/lc_trap.conf. On Windows NT, the default Log Central trap configuration file is C:\etc\lc_trap.conf. If you use a nondefault location, set the BEA_LC_TRAP_CONF environment variable, which is described in Environment Variables. For information about SNMP management, see Integrating SNMP.

The trap configuration file consists of TRAP_HOST entries.

Example Trap Configuration File

TRAP_HOST   snmp_mgr_host1   162   public
TRAP_HOST snmp_mgr_host2 183 public

TRAP_HOST

The TRAP_HOST entry configures a destination for SNMP traps. The trap configuration file requires a TRAP_HOST entry for each destination. If you do not define any trap destinations, Log Central uses the local host as the default destination.

The following table describes the values in a TRAP_HOST entry.

Table G-4 TRAP_HOST Values

Value

Data Type

Optional

Description

host_name

String

Not optional

Name of the destination machine for the trap notifications. This value can include dots, underscores, and dashes.

port

Integer

Not optional

The port number of the destination machine.

community

String

Not optional

Relationship between an SNMP agent and a set of SNMP managers that defines authentication, access control, and proxy characteristics. Standard values are:

PUBLIC (read-only)

ADMIN (read-write)