Table of contents
- Deployment of the Applications
- Pre-Requisites
- 1. Login and Set Active Subscription
- 2. Publish the Applications
- 3. Create Release for UI with Public Configuration
- 4. Retrieve the Deployable .Zip File
Deployment of the Applications
This guide outlines the steps to deploy the ILAP Analytics applications using Azure CLI and PowerShell. Follow the instructions below to publish the API, BackgroundJobs, and UI components.
Pre-Requisites
Ensure the following are installed and configured on your system:
PowerShell (version 7 or higher): Download PowerShell
Azure CLI Tools for PowerShell: Install Azure CLI
1. Login and Set Active Subscription
Steps:
Open PowerShell and log in to Azure:
az loginThis will redirect you to a web browser for authentication.
Set your active Azure subscription:
$SUBSCRIPTION = "your_subscription" az account set --subscription $SUBSCRIPTION
2. Publish the Applications
Before starting, we recommend using the az webapp deploy command with the zipdeploy option for deploying your applications. For more information on how this works, refer to the Microsoft Learn article.
2.1. Publish ILAP Analytics API
Download the latest version of
Ilap.Analytics.Apias a.zipfile.Navigate to the folder where the artifact is downloaded:
cd path\to\downloaded\artifactRun the following command to deploy the API:
$RESOURCE_GROUP = 'your_resource_group' $WEBAPP_NAME = 'app_name_for_api' az webapp deploy --type zip --resource-group $RESOURCE_GROUP --name $WEBAPP_NAME --src-path (Get-Item .\app-ilapanalytics-api-generic-prod.zip).FullName
2.2. Publish ILAP Analytics BackgroundJobs
Download the latest version of
Ilap.Analytics.BackgroundJobsas a.zipfile.Navigate to the folder where the artifact is downloaded:
cd path\to\downloaded\artifactRun the following command to deploy BackgroundJobs:
$RESOURCE_GROUP = 'your_resource_group' $WEBAPP_NAME = 'app_name_for_backgroundjobs' az webapp deploy --type zip --resource-group $RESOURCE_GROUP --name $WEBAPP_NAME --src-path (Get-Item .\app-ilapanalytics-backgroundjobs-generic-prod.zip).FullName
2.3. Publish ILAP Analytics UI
Download the latest version of
Ilap.Analytics.UIas a.zipfile.Navigate to the folder where the artifact is downloaded:
cd path\to\downloaded\artifactRun the following command to deploy the UI:
$RESOURCE_GROUP = 'your_resource_group' $WEBAPP_NAME = 'app_name_for_ui' az webapp deploy --type zip --resource-group $RESOURCE_GROUP --name $WEBAPP_NAME --src-path (Get-Item .\app-ilapanalytics-ui-generic-prod.zip).FullName
3. Create Release for UI with Public Configuration
3.1. Prepare Public Configuration
Create the PublicConfiguration.js file for the UI with the following structure:
// Do not modify any keys, modify only values.
const publicConfigurations = {
analyticsApiUrl: "your-ilapanalytics-api-base-url/api",
authenticationAuthority: "https://login.microsoftonline.com/your_tenant_id/",
authenticationClientId: "application client id of UI app registration",
authenticationScopes: "comma separated scopes from your API app registration",
authenticationRedirectUri: "your-ilapanalytics-ui-base-url",
};
// Do not modify this line.
window["publicConfigurations"] = publicConfigurations;3.2. Upload Public Configuration
Upload the
PublicConfiguration.jsfile to the pipeline secure file in Azure DevOps. This will ensure secure access during deployment.
3.3. Create Release Pipeline
Set up a release pipeline in Azure DevOps for the UI.
Link it to the build pipeline (e.g.,
prod-generic-analytics-ui).If the release does not run automatically upon creation, trigger it manually.
4. Retrieve the Deployable .Zip File
Once the release pipeline runs successfully, locate the generated
.zipfile in the ILAP Analytics container.Use this
.zipfile for subsequent deployments or updates.
This streamlined guide ensures each step is clear and actionable, minimizing confusion while providing necessary details for successful deployment. Let me know if further refinements are needed!
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article