- Overview
- Commerce
- Project scope
- Development
- Planning and governance
- Architecture and integrations
- Infrastructure and deployment
- Launch readiness
- Maintenance and support
- Best practices
- Overview
- Planning
- Overview
- Sites, stores, and store view configuration
- Reporting configuration
- Database configuration for cloud deployments
- MySQL slave connection configuration
- MySQL triggers usage
- Redis service configuration
- OPcache memory size
- Realpath cache size
- Categories
- Product
- Product variations
- Product options
- Product attributes
- Product listing pagination
- Product cart limit
- Promotions
- Extensions
- Partner escalations
- Payments storage processing
- Development
- Launch
- Maintenance
- Return to Operational Guides
Post-launch steps
Once the website is live, these activities would be performed as soon as possible to ensure the site was launched properly:
- Enable up-time monitoring tool (New Relic), activate checks, and monitor the site to ensure all services and access are in the green
- Enable Adobe Commerce security scan periodically
- Tag the cluster as live and create a support ticket to activate High SLA monitoring
- The CSE (Customer Success Engineer) and TAM (Technical Account Manager) perform the following tasks as soon as cutover is complete:
- Tag the cluster as High SLA for Adobe Commerce client and create a support ticket to activate it
- Activate the Pingdom checks for domain names
- Review monitoring state and ensure all items are in green
- Keep the stakeholders informed of the warranty duration and parameters by email on go-live day
Business.Adobe.com resources
Resources
Adobe Account
Change language
Copyright © 2023 Adobe. All Rights Reserved.
