A production target that is configured for switch deployment requires a pair of databases for the same set of repository assets: one that is active and the other inactive at any given time. Similarly, the same target requires a pair of active and inactive directories for the same set of file assets.
A switch deployment updates a target site’s repository and file assets as follows:
Repository assets are updated on the site’s inactive database while the site’s live database continues to run undisturbed. When updates to the inactive database are complete, the site’s SwitchingDataSource switches 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 inactive directory while the site’s live directory runs. When updates to the inactive directory are complete, the site switches to it: the inactive directory becomes the live directory, and vice-versa. The inactive directory is then updated to reflect the same deployment.
Note: Switch deployment of JSPs to a Web application is not supported: the inactive directory where JSPs are first deployed can only contain the JSPs that are managed in and deployed from the ATG Content Administration environment. This excludes most Web applications, which include other resources such as servlets.
