{"id":281,"date":"2021-03-10T00:00:00","date_gmt":"2021-03-10T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/deliver-java-apps-quickly-using-custom-connectors-in-power-apps"},"modified":"2025-06-26T03:45:56","modified_gmt":"2025-06-26T10:45:56","slug":"deliver-java-apps-quickly-using-custom-connectors-in-power-apps","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/deliver-java-apps-quickly-using-custom-connectors-in-power-apps\/","title":{"rendered":"Deliver Java apps quickly using Custom Connectors in Power Apps"},"content":{"rendered":"\n

In 2021, each month we will be releasing a monthly blog covering the webinar of the month for the Low-code application development (LCAD) on Azure solution. LCAD on Azure is a new solution to demonstrate the robust development capabilities of integrating Low-code Microsoft Power Apps and the Azure products you may be familiar with.  
This month\u2019s webinar is Deliver Java apps quickly using Custom Connectors in Power Apps<\/a>. In this blog, I will briefly recap Low-code application development on Azure, how the app was built with Java on Azure, app deployment, and building the app\u2019s front end and user interface (UI) with Power Apps.<\/p>\n\n\n\n

What is Low-code application development on Azure?<\/h2>\n\n\n\n

Low-code application development (LCAD) on Azure<\/a> was created to help developers build business applications faster with less code, leveraging the Power Platform, and more specifically Power Apps, yet helping them scale and extend their Power Apps with Azure services.  <\/p>\n\n\n\n

For example, a pro developer who works for a manufacturing company would need to build a line-of-business (LOB) application to help warehouse employees track incoming inventory. That application would take months to build, test, and deploy. However, with Power Apps\u2019 it can take hours to build, saving time and resources. <\/p>\n\n\n\n

However, say the warehouse employees want the application to place procurement orders for additional inventory automatically when current inventory hits a determined low. In the past, this would require another heavy lift by the development team to rework their previous application iteration. Due to the integration of Power Apps and Azure, a professional developer can build an API in Visual Studio (VS) Code, publish it to their Azure portal, and export the API to Power Apps integrating it into their application as a custom connector. Afterward, that same API is re-usable indefinitely in the Power Apps\u2019 studio for future use with other applications, saving the company and developers more time and resources. To learn more, visit the LCAD on Azure page<\/a>, and to walk through the aforementioned scenario try the LCAD on Azure guided tour<\/a>.<\/p>\n\n\n\n

Java on Azure Code<\/h2>\n\n\n\n

In this webinar the sample application will be a Spring Boot application, or a Spring application on Azure, that is generated using JHipster and will deploy the app with Azure App service. The app\u2019s purpose is to catalog products, product descriptions, ratings, and image links, in a monolithic app. To learn how to build serverless PowerApps, please refer to last month\u2019s Serverless Low-code application development on Azure<\/a> blog for details. During the development of the API Sandra used H2SQL, and in production, she used MySQL. She then adds descriptions, ratings, and image links to the API in a JDL studio. Lastly, she applies the API to her GitHub repository prior to deploying to Azure App service.<\/p>\n\n\n\n

Deploying the Sample App<\/h2>\n\n\n\n

Sandra leverages the Maven plug-in in JHipster to deploy the app to Azure App service. After providing an Azure resource group name due to her choice of \u2018split and deploy\u2019 in GitHub Actions, she only manually deploys once, and any new Git push from her master branch will be automatically deployed. Once the app is successfully deployed, it is available at myhispter.azurewebsites.net\/V2APIdocs, where she copies the Swagger API file into a JSON, which will be imported into Power Apps as a custom connector.<\/p>\n\n\n\n

Front-end Development<\/h2>\n\n\n\n

The goal of the front-end development is to build a user interface that end-users will be satisfied with, to do so the JSON must be brought into Power Apps as a custom connector so end users can access the API. The first step is to import the open API into Power Apps; note that much of this process has been streamlined via the tight integration of Azure API management with Power Apps. To learn more about this tighter integration watch a demo on integrating APIs via API management into Power Apps<\/a>.<\/p>\n\n\n\n

After importing the API, you must create a custom connector and connect that custom connector with the Open API the backend developer built. After creating the custom connector, Dawid used Power Apps logic formula language to collect data into a dataset, creating gallery display via the collected data. Lastly, Dawid will show you the data in a finalized application and walk you through the process of sharing the app with a colleague or making them a co-owner. Lastly, once the app is shared, Dawid walks you through testing the app and soliciting user feedback via the app.<\/p>\n\n\n\n

Conclusion<\/h2>\n\n\n\n

To conclude, professional developers can rapidly build the back and front ends of the application using Java, or any programming language with Power Apps. Fusion development teams, professional developers, and citizen developers can collaborate on apps together, reducing much of the lift for professional developers. Please watch the webinar<\/a> and complete the survey<\/a> so we can improve these blogs and webinars in the future.<\/p>\n\n\n\n

Resources<\/h2>\n\n\n\n