Cloud customer launch checklist
Provides a checklist for customers preparing for their initial launch of Configured Commerce Cloud.
Context and goal
The following checklist of events, notes, and owning groups:
- is meant to provide a general outline and checklist for initial Site Launches of Optimizely Commerce Cloud to Production
- should be adequately vetted against the specific additional considerations and/or projects needs by the implementation Partner to account for any unique considerations due to a given Site Implementation
- is meant to be universal but should be broadly applicable to any Cloud Site Launch
- should continue to be updated and reviewed over the course of Platform updates.
- is not a reflective list for a Site Upgrade
Pre-launch events
Event | Owning | Estimated Lead Time | Dependencies | Notes, Needs, Considerations |
---|---|---|---|---|
Request Production Site Setup | Partner | 2 weeks | Go-Live with Configured Commerce Cloud This is done via a Zendesk ticket, minimum 2 weeks before launch date Request for Production Site Setup should include the following:
| |
Create Production Site | Optimizely Hosting | 2 week |
|
|
Approve SSL Certificate for Domain | Customer | 1-2 days | Optimizely to provide DNS/TXT records from Cloudflare | Customer will insert DNS/TXT records provided by Optimizely team. Cloudflare can then automatically confirm the domain and generate the SSL certificates. |
Add DNS Records for Mailgun | Customer | 1-2 days |
|
|
Review TTL Setting Length | Customer | 1 day |
| |
Install/Configure WIS | Partner/Customer | 1-5 days |
| |
Determine Launch Communication Strategy | Partner | 1-2 weeks |
| |
Determine Range & Load Up Order/Invoice History | Partner/Customer | 1-2 day |
| |
Configure and run Integrations | Partner | Estimate by partner |
| |
Production Settings Audit | Partner | 1 week |
| |
Clear Sandbox Transactional and History Data from Production DB | Partner | 1 day |
| |
Make sure Theme and latest .Extensions .DLL have been pushed to the site | Partner | 1 day |
| |
Configure Robots.txt file | Partner | 1 day |
| |
Determine Google Analytics Needs | Partner/Customer | 1 day |
| |
Determine URL Redirect Strategy and Load in Desired Redirects | Customer | 1-2 weeks |
| |
Follow Articles | Partner/Customer | 1 day |
| |
Code Lock | Partner/Customer | 2 weeks |
| |
Performance Review | Optimizely Engineering | 2 weeks |
|
|
Settings to review in production site after it is created
Field Name | Value | Notes |
---|---|---|
Computers Allowed for Integration | See Notes | Determined when the Production WIS is installed |
Computers Allowed for Integration | paws-prm2-int1 | Replaces aws-stg-int1 |
Website Domain Names | localhost and prod domains | The localhost value is needed for Identity Server. Any production domains will need to be included as well. |
Test Email | See Notes | Once the site is officially launched (ie: fully live and prod testing is finished) this should be blank The Implementation team and Customer need to coordinate on when the appropriate time for this setting to change is so emails don't inadvertently go out to Live Customer's during Production testing |
Automatically Apply Theme | No | This value needs to be changed to No from Yes for Production Sites |
Launch team events and hand-off sequence
Event | Owning Group | Timing | Notes, Needs, Considerations |
---|---|---|---|
Configure Production Specific Site Settings | Partner | Once Code is deployed | Adjust any settings that may need to be different from Production to Sandbox |
Request Default Domain Deployment | Partner | Before DNS cutover | Sometime before the DNS Cutover, make a request with Optimizely support to change the default domain on the production environment to the preferred production domain. |
Change DNS Entries to Production Site | Customer | Upon Testing Completion | Once site has been tested and confirmed Customer is free to change their DNS Records for Production; Remove /etc/hosts entries; DNS info will be provided in the Project Initiation ticket. |
Naked Domain SSL Preparation | Partner/Customer | After DNS Records Created | If you are specifically using our redirect server for the naked domain, SSL certificates are not created ahead of time. Please submit a support ticket to have the job run manually, or the job runs every night at midnight CT automatically. This step is not necessary if you are not using the naked domain. |
Run Sitemap Integration Job | Partner/Customer | After launch | Run this job and verify the robots.txt file is correct in order for crawlers to reach the sitemap. |
Production Health Check | Partner | After launch | Partners should submit a support ticket to notify Optimizely once the DNS has been switched over in order to add the site to be monitored by Optimizely. |
Updated 6 days ago