Migrating e-Business Classic (Non-CMS) to Azure App Service

Owned by Madhuri Dange (Unlicensed)
Last updated: Apr 28, 2023
1 min read

To begin with the migration of e-Business Classic (Non-CMS) to Azure App Service, follow the below instructions.

  1. Log in to the on-premises environment where you have e-Business Classic (Non-CMS) installed and configured

  2. Take the backup of e-Business Classic (NON-CMS) site hosted on IIS.

  3. Go to Kudu services and click Tools->Zip Push Deploy, delete all the folders and drag-and-drop the backup of eBusiness Classic Non-CMS site contents for the app service.

  4. Once, the site contents have been uploaded on Kudu, open the web.config file and make the following changes.

    1. Under <configSections>, add the following to declare the exceptionManagement section,

      <section name="exceptionManagement" type="Aptify.Framework.ExceptionManagement.ExceptionManagerSectionHandler,AptifyExceptionManagement" />

    2. Below the end of <configSections>, add the following section to enable exception logging in the APTIFY database (ERRORLOG table),

      <exceptionManagement mode="on" defaultseverity="0"> <publisher mode="on" assembly="AptifyExceptionManagement" type="Aptify.Framework.ExceptionManagement.DatabasePublisher"/> </exceptionManagement>

    3. Update the value of the key, “Aptify.Framework.ObjectRepository.AptifyObjectRepository.DefaultObjectCachePath“, to the path of the site contents “bin“ folder on Kudu.

    4. Update the values of “AptifyDBServer“, “AptifyEBusinessSQLLogin“, “AptifyEBusinessSQLPWD“ and “AptifyEBusinessSQLIsTrusted“, according to the SQL Managed Instance on Azure.

  5. Run the application using the URL of the app service.