Previous page

Next page

Locate page in Contents

Print this page

Possible Scenario

Conditions. The Controller is implemented so that it stores all the data used and created during the application instance creating, reconfiguring, and upgrading, excluding the data related to the installation-only settings. Also, the Controller stores the application metadata and scripts at the instance-specific locations.

Starting Point. Disabling service instance is initiated.

Step 1. The Controller executes respective configuration script.

Sub-step 1.1. From the application metadata stored on the site, the Controller gets information about configuration script language ("/application/service/provision/configuration-script/script-language"), and checks if there is an appropriate interpreter in the system and if it can be used on the environment to run the configuration script.

Sub-step 1.2. Gets all the application data created during the instance creation, upgrades and changes, such as the settings data (excluding installation-only settings), data about resources allocated to the instance and other changes made by the Control Panel to the system (web server configuration, permissions, etc.). Basing on this data, the Controller creates environment variables as defined by the Specification.

Sub-step 1.3. Using the interpreter, the Controller runs the configuration script with the disable argument, and passes to it all the environment variables it created on the previous sub-step.

Sub-step 1.4. If the script invocation fails, the Controller returns an error, stops disabling service and displays to the user the error message.

See Also

Enabling and Disabling Service

Please send us your feedback on this help page