BUSINESS APPLICATION MANAGEMENT
This section describes the actions to be performed during the below upgrade scenarios:
SEAMLESS BUSINESS APPLICATION UPGRADE (VMs ONLY)
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:
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 - Through restarting the VSP Services
-
Stop the application process. Example: Stop Tomcat
-
Stop the VSP services in the probe system. This internally stops the application provisioning
-
Linux: 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: 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