This topic describes first-time onboarding deployment of an existing Commerce website to the Integration environment, as part of the Episerver DXP.
When is this applicable?
This is an onboarding scenario for an existing site which you want to move to a cloud-based environment for the first time, for further development and maintenance there. In this case you already have a database with content, and you will need to get that restored to the correct application, which will be done by Episerver.
This topic uses Visual Studio with the Episerver extensions and publish profiles. However, you can also use other deployment methods.
Note: If not already done, remember to change the default login credentials (admin/store) provided in the Commerce installation, before deploying. See Installing Episerver.
To deploy from your local development environment, you need to create a set of output files, and provide these to Episerver for deployment to the Integration environment.
A Commerce solution consists of two websites, a front-end site and the back-end Commerce Manager site, and two databases: one for CMS and one for Commerce. So, there will be additional output components compared to a plain CMS site.
The following output is needed for deployment of a Commerce site:
Open your solution in Visual Studio, and repeat steps 1-4 in this section for the front-end site, and for the back-end Commerce Manager site, to create the output files for the web application.
Note: For the Commerce Manager site you need to include the Apps folder manually in the zip file.
In MS SQL Server Studio, repeat steps 1-4 below for the front-end site database, and for the back-end Commerce Manager database, to create the bacpac output files.
For the front-end site, follow the steps below to create the output file for the media/BLOB content.
When you have created the output files, contact Episerver, and follow the instructions provided to upload them to the assigned area. The deployment will then be finalized by Episerver.
Last updated: Apr 02, 2020