Using a stand-alone collator

Working With Log Files > Collating event log files > Using a stand-alone collator

If you do not want the log collation server to be a Content Gateway node, you can install and configure a stand-alone collator (SAC) which can dedicate more of its power to collecting, processing, and writing log files.


	Note The stand-alone collator is currently available for the Linux platform only.

1.	Configure your Content Gateway nodes as log collation clients. See Configuring Content Gateway to be a collation client.

2.	Copy the sac binary from the Content Gateway bin directory (/opt/WCG/bin) to the machine serving as the stand-alone collator.

3.	Create a directory called config in the directory that contains the sac binary.

4.	Create a directory called internal in the config directory you created in Step 3. This directory will be used internally by the stand-alone collator to store lock files.

5.	Copy the records.config file (/opt/WCG/config) from a Content Gateway node configured to be a log collation client to the config directory you created in Step 3 on the stand-alone collator.

The records.config file contains the log collation secret and port you specified when configuring nodes to be collation clients. The collation port and secret must be the same for all collation clients and servers.

6.	Open the records.config file on the stand-alone collator and edit the following variable:


Variable	Description
proxy.config.log2.logfile_dir	Specify the directory where you want to store the log files. You can specify an absolute path to the directory or a path relative to the directory from which the sac binary is executed. Note: The directory must already exist on the machine serving as the stand-alone collator.