Steps
-
Open a command prompt or PowerShell on the Log Server machine.
-
Navigate to the SQL directory (C:\Program Files\Websense\Web Security\SQL, by default).
-
Enter the following command:
createdbu -ip <IP_address> -name <db_name> -user <user_name> -pass <password>
For example:
createdbu -ip 10.123.123.123
-name wslogdb70 -user sa -pass testpassword
This prompts the utility to create or upgrade the database “wslogdb70” on the SQL Server machine at 10.123.123.123. The
SQL Server “sa” account is used, and the password is “testpassword.”
- Additional parameters can be used to customize database creation. See Database creation utility parameters.
- Each parameter must be preceded by a dash (-) and followed by a space and value (argument).
- There is no mandatory order for parameters.
-
Wait for the database to be created. This process can take several minutes.
- The catalog database is created first, followed (after a few minutes) by the partition database, and then the threats partition.
- If an error occurs, see Database creation utility errors.
- If the process completes successfully, optionally use Microsoft SQL Server Management Studio to verify that the database and its jobs were created as expected. See Using
SQL Server Management Studio to verify database creation.
-
Enter database connection information on the page in the Web Security module of the Forcepoint Security Manager, then click OK and Save and Deploy.
Log Server creates the ODBC connection and provides connection information for the other reporting components.
-
If Log Server stopped because of database problems, use the Component List tab of the page to start Log Server.
Next steps
Once product installation is complete and policy enforcement has started, data should begin to appear in your reporting tools. Use Real-Time Monitor, dashboard charts, investigative
reports, or presentation reports to verify that reporting data is being recorded. If no data or incomplete data appears in reporting tools, see Incorrect or missing data in reports.