Last updated: Jun 20 2017

DXC Service self-deployment guide

This topic describes how to access the DXC Service management portal, and the steps to deploy changes between the Integration and Preproduction environments, when using the Episerver Digital Experience Cloud Service

Note: You need to contact Episerver to deploy to Production when going live.

Prerequisites

Account and access

You need an organizational email address like firstname.lastname@company.com, associated with an enabled business Microsoft Live account. If your organization already has a verified Microsoft Azure AD domain account, you can also use this. See Microsoft Associate Azure subscriptions.  

Note: Generic accounts like access@somedomain.com, or private hotmail-type accounts like my-private-mail@live.com, cannot be used. The self-deployment portal works best with browsers Chrome or Firefox.

Verifying site access before deployment

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.

Deployment steps

  1. Go to the DXC Service management portal on https://paasportal.episerver.net and log in with your account credentials.
  2. When logged in, you will be taken to the Organizations section. Locate the organization and project for which you want to deploy changes, and click on the project name to open it.
     

     
  3. The upper part of the Project page provides the deployment options. The lower part provides information about provisioned environments, site URLs for site verifications, and access to application logs for troubleshooting.
      

       
  4. Before deploying, ensure that the source site (Integration), is up and running. Select the environment in the drop-down, and use the displayed URL to browse to the site. When you have verified that it works, you can deploy.
       

       
  5. Click Deploy to start the deployment. In the dialog that appears, select applicable options:
    • If the deployment includes database schema updates or changes to content types, select Use maintenance page, to display a maintenance page while the site is offline.
    • If it is a first-time deployment to the target environment, select Include Blobs & DB to copy these items over. If this option is not selected, only code will be copied.
      Note: Existing BLOBS and database will be overwritten if the option is selected.
    • In case of multiple web applications, you can select which ones to deploy.
         

        
  6. Click Start Now. A progress bar displays the progress of the deployment. Click View output log to see deployment step details. See Deployment process, for an explanation of the procedure. You can also click Cancel to stop the deployment and roll back the changes.
      

       
  7. When the first part of the deployment is done, you will see a confirmation message in the portal, and an email will be sent to the technical contact for the target site. The email contains a link to the slot - Slot URL(s), where the site(s) can be verified before going live. Click the link(s) to verify that the site is working as expected. 

    Note: DO NOT continue with the deployment if a site in a slot cannot be verified.   

       
  8. When you have successfully verified the site(s) in the previous step, click Go Live to complete the deployment. Alternatively, if the deployment did not succeed, click Reset to revert the changes, and continue to step 11.

      
  9. The progress bar appears, and the site in the slot is swapped into the Preproduction environment.
  10. When completed, the project page will display the Deploy option again. Click the information icon next to the environment name to see when the latest deployment was completed.
        

       
  11. If you clicked Reset in step 8, 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.
      

       
  12. Verify that the Preproduction environment works as expected.

Troubleshooting deployments

In case of an unsuccessful deployment, 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.

Deployment job log output

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 Job Log Details Email 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.

Log Stream

The Log Stream options allows you to 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. Here 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.

Log stream view