Skip to main content

A Technical Talk on Microservices and Cloud Deployment

This is a full-length session of microservices development using Microsoft .Net Core WebAPI(C#.Net) and Mongo DB as backend. The session presentation available below   The source code of session available in GitHub , feel free to share your feedback and contribute to this project Full session video Prerequisites for development MongoDB (you can download from here ) Visual Studio 2019 DotNet Core 3.1.x SDK Postman (for API Testing)

How to check the Hybrid Connection in Azure Website (Webapp)

Introduction

Hi, this article will helpful for you to check the hybrid connection in Azure Website (Web App).

Scenario

Lets assume we have 2 Web Apps and 2 On-Premises database servers, Both the webapps required on-premises database access, for this scenario we can use Azure Hybrid connection.


Architecture of Web apps and Hybrid connection



  • Website 1 : Wants to access DB Server 1 & DB Server 2
  • Website 2 : Wants to access DB Server 1 only
To achieve this we need to create two hybrid connections for each db and we can share it with websites.

Troubleshooting

Once you successfully created hybrid connection and configured listener setup. we need to ensure whether our website connected to our DB Server or not. So open the Azure portal (old or new).

1. Select the website

2. Click Browse website
      * Lets assume our website URL is https://myweb.azurewebsites.net
      * Change the URL to https://myweb.scm.azurewebsites.net

3. Now you will enter into Kudu management portal

4. Select Debug console -> CMD

5. We are in the remote console of our VM (dedicated to our web app now, we can't take remote of this)

6. To check the DB Server connection status type nameresolver.exe  
      ex: nameresolver.exe dbserver1

if website able to identify the DB server it will show as above


if website not able to identify DB server it will show above error
 7. In case it shows "Can't find" error, make sure your are created the proper hybrid connection, listener setup and added to our website.


Comments

Popular posts from this blog

Know more about Azure Website KUDU?

KUDU  is the web tool for analyzing and troubleshooting azure websites. Benefits of Kudu Know about operating system Environment variables Processors & cores Applications settings Connection strings Process explorer (running instances) Debugging console (Command prompt & PowerShell) Diagnostics Log (view & download) Site extensions management and more Environment details Command prompt Are your wondering to use KUDU?, its very simple open browser and type https://{ your azure website name }.scm.azurewebsites.net . To access KUDU you need to have your azure deployment credentials! Example Your azure website : https://textingwebsite.azurewebsites.net/ Kudu URL : https://textingwebsite.scm.azurewebsites.net/ for more information about Kudu click here

A Technical Talk on Microservices and Cloud Deployment

This is a full-length session of microservices development using Microsoft .Net Core WebAPI(C#.Net) and Mongo DB as backend. The session presentation available below   The source code of session available in GitHub , feel free to share your feedback and contribute to this project Full session video Prerequisites for development MongoDB (you can download from here ) Visual Studio 2019 DotNet Core 3.1.x SDK Postman (for API Testing)

Resource Explorer (DLL/Exe) using C#

After long time we are with the Resource Explorer. This is verymuch usefull for the resource management in the Application/DLL. Purspose     You are having the images/icon in other dll then you can load and use that particular image/icon using the below concept Source Code: public partial class frmAssemblyHandling : Form { public frmAssemblyHandling() { InitializeComponent(); } private void btnSelectDLL_Click( object sender, EventArgs e) { //the required resources to filter from the available ArrayList arImageFilter = new ArrayList (); arImageFilter.AddRange( new string [] { ".png" , ".ico" , ".bmp" , ".png" }); OpenFileDialog fd = new OpenFileDialog (); fd.Filter = "DLL Files (*.Dll)|*.dll|Application Files (*.exe)|*.exe" ;