Dynamics NAVAX

This is the final post of this series. Web Api App for AX 2012 to Azure–Intro Deploy a Web Api App for AX 2012 to Azure–part 1 Application settings - Web Api App for AX 2012 to Azure-part 2 Authentication - Web Api App for AX 2012 to Azure-part 3 Hybrid connection - Web Api App for AX 2012 to Azure-part 4 (this one) In this post we will set up a Hybrid Connection. This is basically a listener that sits on your on-premise server. It will expose internal port to Azure. More information on Hybrid connection on Microsoft’s site. https://docs.microsoft.com/en-us/azure/biztalk-services/integration-hybrid-connection-overview In your Api App, click on Networking. Then click on “Configure your hybrid connection endpoints”. First download the connection manager. Install this on your on-premise server that you want to install the listener. You don’t have to run the connection manager just yet. Set up the hybrid connection by clicking on the “Add hybrid connection” Click on the “Create new hybrid...

Lets set up the authentication in this post. You should always secure your application and never leave it exposed out to the web. Click on Authentication menu and turn it on. In the drop down, select Azure Active Directory. In the Authentication providers click on Azure Active Directory to start configuring it. Select the Express mode. This will create an web App registration. Once authentication is configured. Lets set up a native Application registration. This step is only required if you are trying to communicate to the web service via a desktop applications, mobile application, third party tools to access your web services. More information on application permissions and authentication on the Microsoft article. https://docs.microsoft.com/en-au/azure/active-directory/develop/active-directory-authentication-scenarios Navigate the the Active directory menu and click on Application permissions. You will see the “Web app/API” application registration. We will create a Native application...

Last post showed how to publish your solution to Azure. This post will show you where to modify the the application settings. In visual studio you would be modifying the web config file. In the cloud you will modify the Application settings. Find your Api App. Click on Application settings. Scroll down to App settings.

Continuation from previous post. In this post I will show how  publish your solution to Azure. I assume you have followed the instruction from the GitHub wiki to download and configure. https://github.com/ffilardi/AxaptaAPI/wiki Now that you have done that. Lets deploy. Create a new Api App. You might have to search for it if its not available on the menu. Give it a name and select a Resource Group. Obviously pick a data centre location that is close to your AOS. If I am not sure, I like to use this site to find the closest with the lowest latency. http://www.azurespeed.com/ Now you have an empty Api App. Grab the Publish file by clicking the “Get publish profiles”. This is not necessary but if you have other developers who don’t have access but you want them to publish. This one of the ways. In Visual Studio right click on your project and click Publish. Follow the wizard. You can sign in and select the Azure resource to deploy it to. Otherwise, use the publish file to import and ...

Last year I did a plug for a colleague who had developed this super nice solution which you can use to expose your AIF SOAP services as RESTful services. http://dynamicsnavax.blogspot.com.au/2016/04/expose-ax-2012-aif-services-soap-as.html Fabio has done a great job in sharing a great piece of work and also documenting it really well. What is missing is to take it to the next level. So, in a series of posts, I will show how to deploy this to Azure via Azure Api App and communicate with your on premise AOS. There are many benefits to this solution in the cloud Integration with Azure Logic Apps – this uses swagger and Logic Apps will work really nicely Expose for 3rd parties to securely integrate with your AX solution No need setting up complicated IIS/Firewalls/DMZ servers etc. Use Azure Authentication without a need to build anything Scale easily with the cloud Allows you to build mobile apps