Hosting multiple virtual applications in Azure Web Role

Web role can be used for hosting different virtual application. The web role supports running a virtual application within a site.
Same web site project added in solution can be used to host as a multiple virtual application within web role. Service definition file in Azure Cloud service project is used for this purpose. The <sites> element in ServiceDefinition.csdef file helps us to host multiple virtual applications within a web role application. Following is the description how you can achieve it.
Open VS2010 and create Azure Cloud Service Project. Add a simple web role in it. Once done, right click on solution and click on “Add” to add another new project in the same solution. So the final solution s07ucture in VS2010 will be as shown below. Here I have added another web application within my cloud service solution. You can add a simple web site also instead of web application.

Now when you run web role in development environment; web site gets created in IIS as shown below. This means I need to add virtual directory within the web site that gets created in IIS for a web role.

To create a virtual application under web role, we need to add <virtualApplication> tag under <sites> tag in ServiceDefinition.csdef file as shown below –

Also we need to know, which application we are running therefore I added following code in master page file of VirtualApp project under <h1> tag. Here I am 07ying to create 3 virtual application in web role application.

Now I run my project by pressing F5. I making my web role project run on port 80. Therefore the web role URL I got here is - http://127.0.0.1/Default.aspx
If you are running on port 81 the URL for your web role will be - http://127.0.0.1:81/Default.aspx. Similarly URL will change depending on port being used.
Now I can access virtual application 1 by running URL - http://127.0.0.1/virtualapp/
Similarly other virtual applications can be accessed as - http://127.0.0.1/virtualapp2/ and http://127.0.0.1/virtualapp3/ . Screenshot below shows VirtualApp2

IIS s07ucture will be as follows -


Now if you deploy this project on Azure management portal then the URL of virtual applications will be as follows –
http://YourHostedService.cloudapp.net/virtualapp/
http://YourHostedService.cloudapp.net/virtualapp2/
http://YourHostedService.cloudapp.net/virtualapp3/
Hope this helps.
Cheers…
Happy Virtualization!!!

Comments

Post a Comment

Popular posts from this blog

The request has both SAS authentication scheme and 'Bearer' authorization scheme. Only one scheme should be used

Image
While doing testing after doing a POC on Securing Logic App with Azure Active Directory authentication , where I have put logic app behind APIM and before passing the request to logic app, apim does validation of the token.  I was encountered with an error "The request has both SAS authentication scheme and 'Bearer' authorization  scheme.  Only one scheme should be used." Why it happened After validating the token which is part of the header i.e. Authorization, APIM forwards the request as it is to backend. As  Logic app is configured as  back end , it's url already consist of SAS signature plus the request also has Authorization section and this is the problem. By default every request endpoint on a logic app has a Shared Access Signature (SAS) in the endpoint's URL, which follows this format: https://<request-endpoint-URI>sp=<permissions>sv...
Read more

Getting Started with Logic Apps - AS2

Image
What is AS2? Every enterprise requires some kind of product, service or counselling from another enterprises thus there happens a B2B(business to business) communications, some of the communication is unique whereas most of the communications are common for most of the enterprises e.g., Purchase Order. But every enterprise has there own way(format) of sending the messages, leading to difficult management when number of partners increased.  Considering this the Enterprise leaders decided to have some standards/rules defined across the communication leading to B2B protocol standards which provide guidelines for trading partners to follow when conducting business between enterprises. EDI X12, EDIFACT, TRADACOM etc. AS2 stands for Applicability Statement 2 and is a B2B messaging protocol used to transmit Electronic Data Interchange (EDI)/Business documents from one organization to another. So EDI standards define how to format data and AS2 specifies how to securely transport...
Read more

How to Debug and Trace request in Azure APIM - Portal, Postman, RequestBin

Image
Introduction  APIM is a great option to expose API's with out of box features for applying restrictions, preprocessing, postprocessing etc. You can leverage existing API's,  by importing it and it gets added as a new API with all the operations associated with it. And based on the requirements you  apply policies at the stage/level (Inbound,Backend/Outbound) and you are ready to use the API. Before it is shared, we do some testing to make sure everything is working as per the expectation and this is where Debugging and Tracing request becomes important. APIM does provide a way to Trace a call with the help of  Ocp-Apim-Trace http header. So whichever request/call is to be traced, it needs to include this in header  with the value set to true and it has dependency on another header, so that also needs to be passed i.e.  Ocp-Apim-Subscription-Key Note: The api on which Tracing is to applied , it requires the subscription key to be en...
Read more