This topic describes how to access the DXC Service Management Portal, and the steps to deploy changes between the Integration, Preproduction, and Production environments, with Episerver Digital Experience Cloud Service.
In this topic
You need an Episerver cloud account to access the self-services for Episerver DXC Service. See Creating an Episerver cloud account how to get an account.
Note: Generic accounts like firstname.lastname@example.org, or private hotmail-type accounts like email@example.com, cannot be used. The self-deployment portal works best with browsers Chrome or Firefox.
Before starting a deployment, make sure the site in the source environment is running by accessing it in a browser. If the site has IP restrictions preventing you from navigating to it, ask the technical contact for the site to add your IP address in the exclusions list.
If you cannot reach the site, something is probably wrong and deployment cannot be done. Contact the technical contact for the site to solve the issue, and try again. When you have verified site availability, you can start the deployment.
This example deploys from the Integration to Preproduction environments, but the procedure is similar when deploying from Preproduction to Production.
If you have issues when deploying to Production and need urgent assistance, contact Episerver (24/7): Worldwide: +46 8 555 827 50; North America: 1-(877)-383-0885 (Toll Free); United Kingdom: +44 800 066 4784 (Toll Free); Australia: +61 2 9248 7215.
Existing BLOBS and database are overwritten if you select the Include Blobs & DB option. If this option is not selected, only code will be copied.
An email is also sent to the technical contact for the target site, with link(s) to the slot URL(s) that can be used for site verification.
Note: DO NOT continue with the deployment if a site in a slot cannot be properly verified.
Alternatively, if the deployment did not succeed, click Reset to revert the changes. The Preproduction environment will be reverted to its initial state if a site did not work as expected in the first deployment part. Click Reset in the confirmation dialog, to complete the reset, and go to the troubleshooting section below to solve the issues.
Notifications may appear at the top of the screen sent by the system administrator. Also, support information is provided in case you have any issues during deployment.
If an unsuccessful deployment occurs, you will see an error message in the Project page.
Click error log for detailed information, to see a summary of the deployment issues.
If the information here is not sufficient to identify the issues, click View Job Log to open the Job output view. This contains detailed deployment information as described below.
This view provides information about the site(s) and environments involved in the deployment. You can also find exceptions, error messages, warnings and deployment output steps, useful when troubleshooting deployment issues.
Click Get Detailed Log to receive the same information in an email. This is useful if you want to share the information with someone without access to the portal.
The Log Stream options lets you view output from Episerver log files to help in troubleshooting deployment errors. This option requires diagnostics logging to a BLOB storage being enabled, as described in the article Enable diagnostics logging for web apps in Azure App Service.
Click Open Log Stream Window to access the log stream. You can hook on the Episerver logs to monitor the live log stream from all sites instances. Click Pause or Resume to stop or continue the streaming of log information. Click Clear to remove the recent log output.
Last updated: Feb 04, 2019