Deploying Java Function in Azure that uses Azure CLI

Create Functions

1. Search for Azure Function App in the Search bar in the Azure services console.
2. Click Create.
3. Select Consumption as the hosting option.
4. Click Select.
5. Edit the following details under the Basics tab in the Instance Details section:
   • Function App Name. Enter a name that describes the purpose of your function. For example, azureagent
   • Runtime stack. Choose Java as the language to write your function.
   • Version. Choose 17.0 as the version.
   • Operating System. Choose Windows.
6. Click Review + Create.

   If you require extra configurations such as Storage, Networking, you can navigate to the respective sections and configure.

7. Click Create.

   This step takes a few minutes to create the Function, azureagent.

   Once created, azureagent is listed in the Function App.

Configure the Environment variables

Environment variables include Azure API Management service, agent, and federated API management configurations. These configurations are required to connect Azure API Management Service with federated API management.

1. Open azureagent in the Function App.
2. Click Settings > Environment variables from the left navigation pane.
3. Click Add and specify the following in the Add/edit application settings page:
   • Name. Enter the name of the environment variable.
   • Value. Specify a value for the property.

   • Click Apply.

   For details about the environment variables and recommended values, see Environment variables applicable for Azure API Management Service.

4. Click Apply in the Environment variables page.

   The next step is to deploy your Azure agent code into Azure Functions.

Deploying Azure agent code into Azure Functions by using Azure CLI

You can deploy by using Azure CLI.

Configuring event-based trigger for AssetsHandler function by using Azure Subscription service

1. Go to the Home page in your Azure account.
2. Search for Subscriptions in the Search bar in the Azure services console.
3. Select the subscription name in which your Azure API Management service is hosted.
4. Click Resource providers from the left navigation pane.
5. Select Microsoft.EventGrid from the dropdown.
6. Enable Microsoft.EventGrid and click Register.

Configure the Event subscription in your Azure API Management Service

1. Open the Azure API Management Service from which you want to establish a connection to federated API management.
2. Click Events.
3. Click + Event Subscription.
4. The Create Event Subscription page appears.
5. Enter the following details under the Basics tab in the Create Event Subscription page:
   • Name. Name of the event subscription.
   • Event Types. Select the following in the Filter to Event Types checkbox.
     • API Management Service Created
     • API Management Service Updated
     • API Management Service Deleted Each time that the corresponding activity occurs in the Azure API Management service. An event is created that triggers the AssetsHandler function.
   • Endpoint Type. Select Azure Function.
   • Endpoint. Associate this event subscription with the Azure Function, azureagent. Edit the following fields as required in the Select Azure Function screen:
     • Subscription. Select the subscription in which your Azure account is hosted.
     • Resource group. Select the corresponding resource group name.
     • Function app. Select the Function App, to which the event subscription must associate with. For example, azureagent.
     • Function. Choose the function as AssetHandler.
     • Click Confirm Selection.
6. Click Create.

   This triggers the AssetsHandler function whenever the activities that are chosen in the Event subscription occurs in the Azure API Management Service. When the Functions trigger based on the cron expression and event subscription, the application logics of the respective functions are executed automatically, establishing the connection between the Azure API Management Service and federated API management. Also, if you want to troubleshoot the executions of the Azure functions, the tab within the Azure function enables you to monitor the logs and the Metrics section in your Azure API Management Service enables you to analyze all the metrics.

7. Verify whether Azure API Management Service (runtime) is registered with the federated API management and if the APIs and metrics are published and synchronized with federated API management respectively.
   1. Open the federated API management application.
   2. Click the Runtimes tab.
   3. Check whether the runtime is registered with federated API management by verifying whether the AZURE_API_MANAGEMENT_SERVICE_NAME (specified in the .env file) is listed in the Runtimes tab of the Catalog page. If the runtime is listed, it indicates that the runtime is successfully registered with the federated API management.
   4. Check whether the runtime's health status is sent to federated API management by verifying the status of that corresponding runtime in the Status column. The status appears green only if the runtime is up and the heartbeats (status) are received successfully by federated API management.
   5. Check whether the APIs are published from the runtime to federated API management by clicking Action menu > Details of the corresponding runtime that you want to verify whether its APIs are published to federated API management.
   6. Click Relations tab.

      A list of all the APIs associated with the runtime appears. You can also view the runtimes and its associated APIs in the APIs tab of the Catalog page.

   7. Check whether the API metrics are synchronized from the runtime to federated API management by clicking the icon under the Action column corresponding to the runtime for which, you want to verify whether the metrics are published to federated API management.
   8. Click Insights tab.

      The Runtime-specific monitor page renders the metrics of that runtime pertaining to a specified time interval. It lists the metrics such as Transactions, Error rate, Availability, Response time. For details, see Monitoring performance of runtimes in federated API management.