Configuring Content Gateway to be a collation client

Navigate to Configure > Subsystems > Logging > Collation.

In the Collation Mode section, enable the Be a Collation Client option to set the Content Gateway node as a collation client and send the active standard formatted log entries (such as Squid and Netscape) to the log collation server.


	Note To send custom XML-based formatted log entries to the collation server, you must add a log object specification to the logs_xml.config file. See Custom format.

In the To Collation Server field, enter the hostname of the collation server. This could be the Content Gateway collation server or a stand-alone collation server.

In the Log Collation Port field, enter the port number used for communication with the collation server. The default port number is 8085.

In the Log Collation Secret field, enter the password used to validate logging data and prevent the exchange of arbitrary information. This must be the same secret you set on the collation server.

Enable the Log Collation Host Tagged option if you want to preserve the origin of log entries in the collated log files.

In the Log Collation Orphan Space field, enter the maximum amount of space (in megabytes) you want to allocate to the logging directory on the collation client for storing orphan log files. (Orphan log files are created when the log collation server cannot be contacted). The default value is 25 MB.

Click Apply.


	Important If you modify the collation port or secret after connections between the collation clients and collation server have been established, you must restart Content Gateway.