One of Victoria's largest councils had a compliance requirement to keep a legacy Health and Safety application running for several years to come. Like so many councils, keeping legacy applications running across multiple business units is a constant battle.
Olikka decided that moving the legacy ASP Classic application onto Platform as a Service was the best solution. This way, the app continues to run without the customer having to manage infrastructure ongoing.
Unfortunately, Azure App Service does not support ASP Classic natively, and it was Olikka's recommendation to containerise the application with its dependencies.
These are the steps Ollika took to containerise the application
- Completed a discovery exercise to understand the customer's environment and application
- Create a Dockerfile (a script composed of various commands used for organising items that help with the deployment) for the ASP Classic application
- Replaced Windows Auth with Azure AD
- Utilised Azure functions to problem solve external dependencies
- Replaced COM+ library (not supported in Azure App Service) with native code
- Pushed the Image to Azure Container Registry (ACR)
- Deployed the application on Azure App Service (Web App for Container)
Outcome
Olikka successfully moved the application to Azure App Service. The antiquated application needed several components to be replaced by native Azure services like Azure AD and Azure functions.
The customer doesn't have to manage the environment anymore, and the application is now available to more users.
Duration
8-9 Days
