Configuring Multiple Instances of Log Central

 

The following sections describe the conditions for configuring multiple instances of Log Central and explain how to configure multiple instances:

When To Configure Multiple Instances

Configuring Multiple Instances

 

---

When To Configure Multiple Instances

A single instance of Log Central consists of software integrated across one central host and one or more managed notes. You need to configure multiple instances of Log Central if all the following are true:

• A set of log messages generated by a set of managed resources is independent of another set of log messages generated by another set of managed resources.

• Both sets of managed resources share at least one physical machine.

• You need to administer the sets of managed resources separately.

For example, if you have more than one BEA Tuxedo domain and you need to administer them separately, then you need a separate instance of Log Central for each BEA Tuxedo domain.

 

---

Configuring Multiple Instances

To configure multiple instances of Log Central, for each additional instance perform the following steps on the central host:

1. Define two communication services in the services database similar to lc_conf and lc_talk, using the following format:

   conf_service        port_number1/udp
   msg_service          port_number2/udp

   Make sure the domains are unused ports.

   For example:

   lc_conf_dom2        9011/udp
   lc_talk_dom2        9012/udp

2. Make a copy of the Log Central messaging configuration file. For example, install_dir/etc/messaging.conf.dom2, where install_dir is the directory where you installed Log Central.

3. Make a copy of the Log Central initialization file. For example, install_dir/etc/message_processor.ini.dom2, where install_dir is the directory where you installed Log Central.

4. Edit the LC_GLOBAL entry in the copied messaging configuration file.

   • Set TALK_SERVICE to the new msg_service.

   • Set IPCKEY to a value that is different from the value of any other instance.

   • Set INIFILE to the name of the copied initialization file.

     For example:

     LC_GLOBAL
             {
             CENTRAL_HOST = "quahog"
             LOGPREFIX = "/usr/lclog"
             TALK_SERVICE = "lc_talk_dom2"
             IPCKEY = 0xee220000
             INIFILE = "install_dir/etc/message_processor.ini.dom2"
             }

5. Run lc_config to configure the new files. For example:

   lc_config -conffile install_dir/etc/messaging.conf.dom2 -inifile install_dir/etc/message_processor.ini.domw

   where install_dir is the directory where you installed Log Central.

6. Set environment variables.

   • Set BEA_LC_IPCKEY to the IPCKEY value set in step 4.

   • Set BEA_LC_CONF_SERVICE to the new conf_service. For example, lc_conf_dom2.

     For information about environment variables, see Environment Variables.

7. On each managed node, perform the previous steps using the same values.

Note: Use the -i inifile parameter for all database commands, such as lc_user_list.

 

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