Websense bulk copy program

When this parameter is set to Yes , self-signed SSL certificates may be used to encrypt the connection to the database. In this case, the certificate is generated by the SQL Server machine and shared by all components needing to connect to the database. If you have a large or distributed environment that requires multiple Log Server instances, you can configure each Log Server to record data to a separate Log Database.

If you do not need a central repository of reporting data that can be used to generate organization-wide reports, this may be the most efficient deployment option. If you, however, you need a single Log Database in order to store all reporting data in a central location, you have 2 options:. Configure all Log Server instances to independently record their data in the same Log Database.

Configure distributed Log Server instances to pass their data to a central Log Server, which then records all log records from all instances into the Log Database. The first option does not require special configuration steps.

You need only ensure that each Log Server instance points to the same database both database engine IP address or hostname and database instance name. The second option requires more planning and configuration detail, as outlined in the sections that follow. Note that centralized log processing is not as fast as local logging.

Expect a delay of 4 or 5 minutes before the files from remote Log Servers appear in the cache processing directory on the central Log Server. Identify or create a domain user account to use for running each Log Server service.

For example:. This ensures that permissions are consistent for all instances, and facilitates communication between distributed Log Server instances and the central instance.

All remote Log Server instances must be able to communicate with the central Log Server machine. If you have multiple Log Servers that forward their data to a primary Log Server, disk space is tracked for the primary Log Server only. If there is insufficient disk space, logging stops.

Although logging continues, you should clear disk space on the machine as soon as possible to avoid loss of log data. If you enable consolidation, also specify the Consolidation time interval.

This represents the greatest allowable time difference between the earliest and latest records combined to make one consolidation record. Decrease the interval to increase granularity for reporting.

Increase the interval to maximize consolidation. Be aware that a larger interval can also increase usage of system resources, such as memory, CPU, and disk space. For example, suppose a user visited the following sites and all were categorized in the shopping category. Under Hits and Visits, use the Enable visits check box to indicate the level of granularity recorded for each user Internet request.

It is best to create a new database partition prior to changing the method of logging between visits and hits.

When this option is not selected, a separate log record is created for each HTTP request generated to display different page elements, including graphics, advertisements, embedded videos, and so on. Also known as logging hits, this creates a much larger Log Database that grows rapidly. When this option is selected, Log Server combines the individual elements that create the web page such as graphics and advertisements into a single log record that includes bandwidth information for all elements of the visit.

With Websense Web Security Gateway Anywhere , when visits are enabled, numbers shown in reports that include traffic blocked by scanning are lower than the numbers shown on scanning-specific reports. Configure User Service communication. Click the User Service Connection button, then use the User and group update interval field to indicate how often Log Server connects to User Service to retrieve full user name and group assignment information ever 12 hours, by default.

Activity for a user whose user name or group information has changed continues to be reported with the original user name or group assignment until the next update occurs. Copyright Forcepoint LLC. All rights reserved. Specify a Log Server connection method:.

Note Increasing the number of connections can increase processing speed for log records, but could impact other processes in the network that use the same SQL Server. When you finish your configuration updates, click OK to cache your changes.

Changes are not saved until you click Save and Deploy. If you make changes to the database connection, after saving and deploying the changes, also restart the Websense TRITON - Web Security service on the management server machine to update the database connection for all reporting tools.

In multiple Log Server environments, the settings configured on this page apply to the Log Server instance assigned to the Policy Server whose IP address appears on the Web module toolbar.

Verify basic Log Server details. If necessary, use the Port field to update the port over which Log Server communicates with Filtering Service , by default. Configure the Log Database connection. Enter the name of the Default database wslogdb70, by default.

When SSL encryption is enabled:. BCP cannot be used to add records to the Log Database. Log Database connections are slower, affecting reporting performance. See your SQL Server documentation for information about database encryption. By default, SQL Server authentication is selected. Alternatively, you can use a Windows trusted connect network logon account.

The Websense Log Server service must be configured to run as this account. Click Test Connection to verify that it is possible to connect to the Log Database using the credentials provided. For information about the tests performed when you click the button, see Testing the Log Database connection. Specify how log records are processed into the database.

If you select this option, also set the Maximum number of connections to specify how many internal connections can be made between Log Server and the database engine.