In a switch deployment, a site’s repository and file assets are updated as follows:
Repository assets are updated on the site’s inactive database while the site’s active database continues to run undisturbed. When updates to the inactive database are complete, the site’s
SwitchingDataSourceswitches its underlying data source to the updated database. The newly inactive database is updated to reflect the same deployment.File assets are updated on the site’s staging directory while the site’s live directory continues to run undisturbed. When updates to the staging directory are complete, the site switches to use the staging directory: the staging directory becomes the live directory, and the live directory becomes the staging directory. The new staging directory is updated to reflect the same deployment.
Note: Switch deployment of JSPs to a Web application is not supported because the staging directory where JSPs are first deployed can only contain the JSPs that are managed in and deployed from the ATG Content Administration environment. Because most Web applications include other resource such as servlets, a staging directory cannot be used.
