Documentation | Support

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Server Administration for Web Protection Solutions > Working with Policy Server > Changing the Policy Server IP address
Changing the Policy Server IP address
Administrator Help | Forcepoint Web Security and Forcepoint URL Filtering | v8.5.x
Before changing the IP address of the Policy Server machine, stop all web protection services on the machine.
After changing the IP address, you must manually update web protection configuration files used by the Forcepoint Security Manager, Policy Server, and other web protection services before policy enforcement resumes.
Step 1: Update Forcepoint Security Manager configuration
Update the Security Manager to use the new IP address to connect to Policy Server.
1.
On the management server, stop the Websense Web Reporting Tools and Websense TRITON - Web Security services (if necessary).
If the Forcepoint Security Manager and Policy Server are installed on this same machine, these services should already be stopped.
2.
Navigate to the following directory:
Websense\Web Security\tomcat\conf\Catalina\localhost\
3.
Locate the mng.xml file, and then make a backup copy of the file in another directory.
4.
Open mng.xml in a text editor (like Notepad) and replace each instance of the old Policy Server IP address with the new one.
The Policy Server IP address appears twice: as the ps/default/host value and the psHosts value.
5.
When you are finished, save and close the file.
Do not restart any services until you have completed the remaining configuration updates in this section.
Step 2: Update Policy Server configuration
Update the Policy Server configuration file, and the initialization file used to configure communication between web protection components.
1.
If you have not already done so, stop all web protection services on the Policy Server machine (see Stopping and starting web protection services).
2.
Navigate to the bin directory (C:\Program Files\Websense\Web Security\bin or /opt/Websense/bin/, by default).
3.
Locate the config.xml file, and then make a backup copy of the file in another directory.
4.
Open config.xml in a text editor and replace each instance of the old Policy Server IP address with the new one.
5.
When you are finished, save and close the file.
6.
In the bin directory, locate the websense.ini file, and then make a backup copy in another directory.
7.
Open websense.ini in a text editor and replace each instance of the old Policy Server IP address with the new one.
8.
When you are finished, save and close the file.
Step 3: Verify the Log Database connection
Use the Windows ODBC Data Source Administrator on the Policy Server machine to verify the ODBC connection to the Log Database.
1.
Open the Data Sources tool:
*
Windows Server 2016: Go to Start, then select All Programs > Windows Administrative Tools > ODBC Data Sources (64-bit).
*
Windows Server 2012: Go to Server Manager > Tools > ODBC Data Sources 64-bit.
*
Windows Server 2008: Go to Start > Administrative Tools > Data Sources (ODBC).
2.
On the System DSN tab, select the appropriate data source name (by default, wslogdb70), and then click Configure.
3.
Verify that the correct database server machine is selected, and then click Next.
4.
Enter the credentials used to connect to the database, and then click Next.
5.
Accept the defaults on the next 2 screens, and then click Test Data Source.
 
* 
Note 
If the test fails, check the database server machine name and try again.
If the machine name is correct, but the test continues to fail, verify that the correct connection port is being used, and that the firewall allows communication on the selected port.
Step 4: Restart web protection services
1.
Reboot the Policy Server machine. Make sure that all web protection services on the machine restart normally.
2.
If the Security Manager used to configure this Policy Server is installed on another machine, restart the Websense Web Reporting Tools and Websense TRITON - Web Security services on that machine.
 
* 
Note 
If the Forcepoint Security Manager is installed on the same machine as Policy Server, administrators must use the new IP address to log on.

Go to the table of contents Go to the previous page Go to the next page View or print as PDF
Server Administration for Web Protection Solutions > Working with Policy Server > Changing the Policy Server IP address
Copyright 2022 Forcepoint. All rights reserved.