Installing Notifications Microservice in Azure

This section helps you to install the Notifications Microservice in Azure.

Prerequisite

Before deploying Microservice, ensure you have the following:

Setup Azure Command Line

This section helps you to setup the Azure Command Line Interface.

To setup the command line interface in azure, follow these steps:

Download and install AZURE CLI from https://docs.microsoft.com/en-us/cli/azure/install-azure-cli?view=azure-cli-latest
After successful installation, sign in to the Azure portal by using the following command:

az login -u <username> -p <password>

Notification microservice for Azure deployment is available as a single release bundle—

ms-notification-package-azure-<release.xxx>.zip

It consists of the ms-notification-package-azure-<release.xxx>.jar file and the installation related files.

The install.sh/install.bat script is used to deploy the Notification Microservices in the Azure environment

Procedure:

Follow the below steps to install the Notification Microservice into Azure. For configuration, refer to Azure Configuration.

Copy the generated.zip file (from the target folder) in the installation directory
Extract the zip file.
For multiple deployment instances, provide unique value to DEPLOYMENT_ENVIRONMENT property. The resource group will be named as the prefix.

For running sh scripts on a Windows machine, install Linux box or WSL.

Navigate to the installation directory in command prompt.
Modify the resourcegroup, location,app name and so on in the install.sh or install.bat script specific to the installation.
Change the FABRIC CONFIGURATION in the azure scripts, the app key, and secret for the identity service, KonyServicesResourcePath(Push event object service URL), BasePathKony(Base path of the fabric Identity service), konyUserId, and konyPassword (Creds from User Store Identity service), For Configuring fabric-related properties, refer to Notification Microservice - Integration with Fabric
As a prerequisite, ensure that this is first deployed before deploying the other two MS.
Execute the install.sh or the install.bat.
Once the installation is done the functions are created in Azure.
Login to Azure portal and check that the resourcegroup and functionapps are created.

The destroy.sh/destroy.bat script to stop Azure services and delete those services in the Azure environment.

Provide value for DEPLOYMENT_ENVIRONMENT in destroy.sh/destroy.bat as mentioned during deployment steps to match the resource group name for which undeployment needs to be done.
If DEPLOYMENT_ENVIRONMENT is not provided with any value during deployment process then no need to provide any value during undeployment as well.
Execute the destroy.sh/destroy.bat accordingly to delete the resources created in azure cloud

In this topic