Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Running TestLogServer
Using TestLogServer | Web Protection Solutions |v8.4.x, v8.5.x | 28-Feb-2018
In order to screen log traffic with TestLogServer without interrupting the flow of log records to Log Server, first launch the utility using parameters that forward all traffic to Log Server, then use the Forcepoint Web Security module of the Forcepoint Security Manager to configure Filtering Service to pass log traffic to TestLogServer.
On the Log Server machine, open a command prompt or PowerShell and navigate to the bin directory (C:\Program Files\Websense\Web Security\bin, by default).
testlogserver -port 5555 -forward <IP address>:55805
-file <filename.txt>
-onlyip <IP address>
The first parameter allows you to redirect traffic to a file for review, rather than having it scroll rapidly across the console. The file is created by default in the bin directory.
The second parameter allows you to monitor traffic only from the IP address specified.
Initially, when the utility launches, no traffic appears. Traffic must still be redirected to TestLogServer, as described in the steps that follow.
Log on to the Security Manager and navigate to the Web > Settings > General > Logging page.
Change the port to 5555 (or the value you've selected).
Click Check Status to verify the connection to TestLogServer.
Click OK and then Save and Deploy.
When you are finished, first return to the Settings > General > Logging page, and change the logging port back to its original value (55805, by default). Remember to click OK and Save and Deploy to cache and then implement your change.
At this point, traffic is sent directly to Log Server and stops appearing in TestLogServer.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Copyright 2017 Forcepoint. All rights reserved.