Contents x
    Web Protection Upgrade Scenarios
    • 26 Dec 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Contents

    Web Protection Upgrade Scenarios

    • Updated on 26 Dec 2024
    • 2 Minutes to read
    • Print
    • Dark
      Light
    • PDF
    Article summary

    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)

    1. Stop the application process. Example: Stop Tomcat
    2. Stop the provisioning of the associated Application in CMS
    3. Perform the upgrade steps for the Business Application
    4. Start the provisioning of the associated Application in CMS
    5. Start the application process. Example: Start Tomcat


    Option 2 - By restarting VSP Services

    1. Stop the application process. Example: Stop Tomcat
    2. Stop the VSP services in the probe system. This internally stops the application provisioning
      1. Linux: 
        Shell
        service vsp stop
      2. Windows: Stop the VSP Probe service
    3. Perform the upgrade steps for the Business Application 
    4. Start the VSP Service in the probe system. This internally starts the application provisioning
      1. Linux: 
        Shell
        service vsp start
      2. Windows: Start the VSP Probe service
    5. Start the application process. Example: Start Tomcat

     

    Option 3 – For advanced user

    1. Perform the upgrade steps for the Business Application
    2. Ensure that the VSP provisioning changes are intact. Example:
      1. Start script of the application
      2. VSP-specific files including the config files in the deployment folders
    3. 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:

    1. The application in CMS is no longer functional. It is not in “Normal” state. This application can be deleted in CMS
    2. Initiate the auto-discovery process (a scan) by executing the below command on the application server(s):
      Shell
      vsp-cli start fde
    3. 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:

    1. Containers: After the upgrade, ensure that the CI/CD scripts are executed. Redeploy the container
    2. VMs: After the upgrade, ensure the below:
      1. Stop the provisioning of the associated Application in CMSBusiness Application-Stop Provisioning
      2. Start the provisioning of the associated Application in CMSBusiness Application Upgrade - Start Provisioning
    3. Restart the business application
    Was this article helpful?
    What's Next