« New ways to surface data from SharePoint 2010 | Main | Performance of range queries on a Windows Azure Table Vs a Normal Database Table »

Configuring Azure development storage for team development scenarios

While developing applications in a team environment, it is important that the development team has access to a shared data store. And if you are building cloud applications targeting the Windows Azure platform, dev fabric along with the dev storage are the key components which stimulate the Azure platform aka cloud on the local development environment. However, as far as the dev storage goes, the default storage endpoints are configured to listen for requests received to the local host (127.0.0.1). As a result of which the dev storage is not accessible from remote locations.

By default the Azure development fabric is configured as follows:

•Blob Service: http://127.0.0.1:10000
•Queue Service: http://127.0.0.1:10001
•Table Service: http://127.0.0.1:10002

To access the Azure development storage from another machine, follow these steps:

1.Open the devstore configuration file ~Program Files\Windows Azure SDK\v1.3\bin\devstore\DSService.exe.config:
<services>
  <service name="Blob" url="http://[IPAddress]:10000/"/>
  <service name="Queue" url="http://[IPAddress]:10001/"/>
  <service name="Table" url="http://[IPAddress]:10002/"/>
</services>

2.Update "IPAddress" tag of the Blob,Queue and Table URLs, pointing to the machine running the devstorage
<services>
  <service name="Blob" url="http://202.75.100.89:10000/"/>
  <service name="Queue" url="http://202.75.100.89:10001/"/>
  <service name="Table" url="http://202.75.100.89:10002/"/>
</services>

3. Shutdown / Start the Development Fabric

The development teams are now in a position to access a shared dev storage from their local development environments

Note: Check the devstore on the remote machine is in a "Running" state before trying to access it from your application

TrackBack

TrackBack URL for this entry:
http://www.infosysblogs.com/apps/mt-tb.cgi/4486

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter