What is the purpose of an upgrade site?
Oracle B2C Service
A full production clone is automatically created when an update begins. That clone is then updated to the targeted version and known as the "upgrade site". The upgrade site is a complete copy of the production database and configuration files, but excludes file attachments. The upgrade site is destroyed when the production site cuts over to the targeted version. The B2C Service update mechanics require an upgrade site. When a production B2C Service site is updated to a new version, the production database is merged with the upgrade site configuration files. Therefore, a test site cannot replace an upgrade site during an update.
The upgrade site is ideal for testing, providing a non-production site on the targeted Oracle B2C Service version. Please consider watching Oracle's Quarterly Webinar: Everything You Ever Wanted to Know About Service Cloud Updates
The following components are generally tested on the upgrade site:
- Service emails and incident management
- Customer Portal functionality in addition to "look and feel"
- External integrations & Chat
- Installation of the updated .NET agent console to ensure workstation requirements are met
- Best practices for testing
There are important differences between a test site and an upgrade site even though both site types are non-production. Some customers elect to perform some or all testing in their test site instead of in their upgrade site. Customers taking this unconventional approach should ensure their test site is kept up to date with production. Test sites are managed by the customer via the Configuration Assistant. In summary, if the site name contains "upgrade", then the site is an upgrade site. The site name can be seen in the URL when installing the .NET agent console and also in the Customer Portal URLs. See Test Site vs. Upgrade Site for more information.