BUSINESS APPLICATION MANAGEMENT
This section describes the actions to be performed during the below upgrade scenarios:
BUSINESS APPLICATION UPGRADE (VMs ONLY)
There are three options available when there is any update on the Business Application. Follow any one of the methods:
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