Switch deployment deploys updated assets to off-line areas, and then swaps these with assets on the live site as a single transaction. Production sites should always use switch deployment.
Note: If you have installed ATG Service using CIM and are running Oracle ATG Web Commerce, the switching data sources will be configured for Commerce only. You must manually configure the ATG Service switching data sources as outlined in this section.
Switch deployments require two databases, where the repository assets are updated on the target site’s inactive database while its live database runs undisturbed. These databases should begin with identical content. To accomplish this, you can use the tools provided by your database vendor to make the second database identical to the first database. Alternatively, after you configure the target for switch deployments, you can perform a full deployment to the target.
ServiceSwitchingDataSource_production is the switching data source that always points to the offline production data source. The repository components used to deploy solutions and other versioned data to production are configured to use this data source. This data source is used exclusively by Knowledge Manager and exclusively for publishing deployment.
ServiceSwitchDataSource_read is the switching data source that always points to the live production data source. The repository components used by both Knowledge Manager and Self Service to read production data for use in the applications are configured to use this data source. For information about configuring switching data sources, refer to Configure Switch Deployment.
Switching Data Source Architecture
