Infrastructure and deployment
This topic provides an overview of hosting environments, infrastructure, and deployment.
Optimizely will provision and maintain two hosting environments: Sandbox and Production. All infrastructure is hosted on Amazon Web Services. The Sandbox environment supports customer UAT testing scenarios, while the Production environment is the live site where commerce is conducted. The implementation team must host all development and test environments.
Basic Pipeline


Delivery Pipeline


Integration
Hosting and maintaining the Windows Integration Service (WIS) used for integrating backend systems such as ERPs is the responsibility of the implementation team in coordination with the customer. The WIS relies on a direct connection to those systems and uses push/pull requests to transfer data between backend systems and the commerce application.
For more information on integration and how-tos, review the Integrations and Jobs article.
Database Requests
Optimizely Implementation teams may request a copy of a Sandbox database with written permission from the customer. Direct access to the database is not available, only copies. Please submit database requests in the support portal at the Optimizely Support site.
Code Deployment
In order to ensure a smooth process for conducting deployments to Optimizely Hosting environments, the ensuing guidelines should be followed:
Target Environment | Description |
---|---|
Sandbox | Implementation team pushes changes to the sandbox branch.
|
Production | Base code updates/releases will be deployed via a set schedule.
|
Setting up the local development environment
See B2B Commerce Cloud Developer Setup.
Deploying to B2B Commerce Cloud
See B2B Commerce Cloud Deployment Process.
Deployment Support
All prioritized requests should be submitted to and marked according to the status indicated below.
Priority | Timeline |
---|---|
Urgent - Impacting Critical Business Process | Less than 2 business hours |
High - Interruption to Business Process | Less than 4 business hours |
Normal - Interruption to Workflow | Less than 12 business hours |
Low - Non-Impact | Less than 2 business days |
Updated 4 months ago