- 23 Jan 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
Web Protection Upgrade Scenarios
- Updated on 23 Jan 2025
- 2 Minutes to read
- Print
- DarkLight
- PDF
About this Article
This article provides information about Web Protection Maintenance including business application upgrade, operating system upgrade and CMS/Probe upgrade steps.
Business Application Upgrade (Only for VMs)
Version 2.9 and Above supports Seamless Business Upgrade. VSP monitors the business application deployment directory for any changes related to provisioning configuration. If any changes are discovered, VSP restores the VSP configuration to the one that existed before the upgrade. This ensures a seamless business application upgrade providing immediate VSP protection without manual intervention. In scenarios where the provisioning status is not "Normal" after upgrade, follow one of the below options
Follow any one of the methods for Business Application Upgrade in Versions below 2.9:
Option 1 - Through CMS – Execute these steps in cases where any application parameter is modified on CMS. Example: deployment folder, start-up script, framework version (PHP 7.3 to PHP 7.4)
Stop the application process. Example: Stop Tomcat
Stop the provisioning of the associated Application in CMS
Perform the upgrade steps for the Business Application
Start the provisioning of the associated Application in CMS
Start the application process. Example: Start Tomcat
Option 2 - By restarting VSP Services
Stop the application process. Example: Stop Tomcat
Stop the VSP services in the probe system. This internally stops the application provisioning
Linux:
Shell
service vsp stop
Windows: Stop the VSP Probe service
Perform the upgrade steps for the Business Application
Start the VSP Service in the probe system. This internally starts the application provisioning
Linux:
Shell
service vsp start
Windows: Start the VSP Probe service
Start the application process. Example: Start Tomcat
Option 3 – For advanced user
Perform the upgrade steps for the Business Application
Ensure that the VSP provisioning changes are intact. Example:
Start script of the application
VSP-specific files including the config files in the deployment folders
Start the application process. Example: Start Tomcat
Operating System/ Framework Upgrade
After the upgrade of OS/Framework/application server or removal of the deployment directory:
The application in CMS is no longer functional. It is not in “Normal” state. This application can be deleted in CMS
Initiate the auto-discovery process (a scan) by executing the below command on the application server(s):
Shell
vsp-cli start fde
The application is auto-discovered in CMS again. Configure the desired security policies in CMS and restart the business application. Refer Application Auto-Discovery for more information
CMS/Probe Upgrade
When CMS and/or Probe is upgraded, ensure that the steps below are followed:
Containers: After the upgrade, ensure that the CI/CD scripts are executed. Redeploy the container
VMs: After the upgrade, ensure the below:
Stop the provisioning of the associated Application in CMS
Start the provisioning of the associated Application in CMS
Restart the business application