Configuring the Central Host

 

The Log Central Host Configuration Utility helps you configure the central host. The utility creates the initialization file and the messaging configuration file. For information about these files, see Initialization File, and Configuration Files.

To configure the central host:

1. Determine the value for each field described in the following table. The values in the "Field #" column correspond to the callout numbers in Figure 3-1.

   Table 3-1 Fields in the Log Central Host Configuration Utility

   Field #	Field	Description
   1	Central Host Name	Name of the central host. This is the value returned when you run hostname on the central host. (hostname is a standard DOS command and a standard UNIX command.) Equivalent value in the message configuration file: CENTRAL_HOST
   2	Intermediate File Prefix	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. Equivalent value in the message configuration file: LOGPREFIX
   3	Port Number	Port number on which the Message Processor listens for requests from the Log Central Console Equivalent value in the initialization file: LC.Server.dbPort
   4	Database Vendor Name	Name of the database vendor. Possible values: MSSQL ORACLE Equivalent value in the initialization file: LC.DBVendor
   5	Type of Database Connection	Native JDBC or JDBC-ODBC bridge. This selection specifies the default values that the Log Central Host Configuration Utility displays in the Database URL and Database Driver Class Name fields.
   6	Database URL	URL for accessing the database. For more information, see your database vendor's documentation. Equivalent value in the initialization file: LC.URL
   7	Database Driver Class Name	Name of the database driver class. For more information, see your database vendor's documentation. Equivalent value in the initialization file: LC.driver
   8	JDBC Driver File Path	Path for the location of the JDBC driver. The Log Central Host Configuration utility copies the JDBC driver file to install_dir/bin/JDBCDrvrForLC.zip, where install_dir is the directory where you installed Log Central.
   9	Database User Name	User that you created in step 2 of the Log Central setup procedure. The Log Central Host Configuration utility uses this user name to create and populate the tables in the Log Central database. Equivalent value in the initialization file: LC.userName
   10	Database User Password	Password for the database user. Equivalent value in the initialization file: LC.password

2. Run the Log Central Host Configuration utility, lc_config, on the central host. For the command syntax, see Commands.

   Figure 3-1 Log Central Host Configuration Utility

   

3. Enter the field values and click OK.

4. If desired, configure a secondary Central Collector.

   You can modify the messaging configuration file to create a secondary Central Collector. For information about the messaging configuration file, see Configuration Files. In the messaging configuration file, the LC_GLOBAL entry contains values for the central host and all managed nodes. To specify a secondary Central Collector, add the following lines to the LC_GLOBAL entry:

   BACKUP_HOST = hostname
   BACKUP_LOGPREFIX = log_file_dir/prefix

   For example:

   LC_GLOBAL
           {
           CENTRAL_HOST = "quahog"
           LOGPREFIX = "/usr/lclog"
           	BACKUP_HOST = "orca"
           BACKUP_LOGPREFIX = "/usr/backuplog"
           }

5. If desired, make additional changes to the messaging configuration file. See Configuration Files.

6. If desired, run show_config -c -f config_file to check the messaging configuration file for syntax errors. For the command syntax, see Commands.

7. If desired, modify the initialization file. See Initialization File.

8. Create service entries for the UDP services if they do not exist.

   Log Central uses two UDP services for communication between the Log Central processes on the central host and Log Central processes on the managed nodes. The service entries are lc_talk, which has a default port of 7012, and lc_conf, which has a default port of 7011. These services need to be available on the central host and managed nodes. For more information, see your network administrator. Service entry examples:

   lc_conf        7011/udp
   lc_talk        7012/udp

   On Windows NT, these entries are in system_root\drivers\etc\services where system_root is probably similar to C:\winnt\system32. On UNIX, these entries are in the YP services table, which is in the /etc/services file.

 

Copyright © 2000 BEA Systems, Inc. All rights reserved. Required browser: Netscape 4.0 or higher, or Microsoft Internet Explorer 4.0 or higher.