To deploy our application to Windows Azure we would require the following steps.

1- Create a new Hosted Service.
2- Create a new Storage Storage Account.
3- Create and configuring management Certificates.
4- Pre-publishing steps.
5- Publishing the solution from Visual Studio 2012.
6- Changing runtime configurations after deployment (Not mandatory for publishing)

1- Create a new Hosted Service

To deploy our application containing a Web and a Worker role we would need Storage Service and Hosted Service. First we would create a Hosted Service which is to host our Web and Worker role services. Click on New Hosted Service and the below popup would open. In the dialog you can choose a subscription and enter the name of your Hosted Service. Choose a URL prefix for your service I am naming it HelloWorldAzureAbdul. For the solution I am creating and affinity group which is going to have my Hosted Service in the East Asia Data Center region.

Choose Do not deploy and click OK. You can see in the Hosted Services we have a Hosted Service called “HelloWorldAzureAbdul” which we created.

2- Create a new Storage Storage Account

To create a new storage account go to “Storage Accounts” and then on the top click “New Storage Account”. In the dialog give choose a subscription and enter the URL. I will enter the same URL helloworldazureabdul and choose the affinity group which was created in Step 1. Click OK and then you can see that the new Storage Account is created.

3- Create and configuring management Certificates.

To enable Visual Studio deploy the solution to my Windows Azure solutions we need to configure the management certificates so that I can enable my account to accept deployment from my machine which has the SSL certificate. In Visual Studio go to the Server Explorer (CTRL+W, L) where you can see the Windows Azure Compute and Windows Azure Storage Node which is installed by the Windows Azure SDK.

Right Click “Windows Azure Compute” and Click “Add Deployment Environment”.

Since I don’t have any existing deployment environment Click “Manage”. In the Authentication Settings dialog click “New” which would ask you to create a new certificate on your local machine.

Enter a friendly name of the certificate, I would name it “HelloWorldAzureAbdulCert” and then click OK. You can enter the name of these credentials I would name them “HelloWorldAzureAbdulAccount”. In the second textbox you need to enter your subscription ID which you can get from the portal.

In the above dialog click “Copy the full path” of the certificate you created. Click OK and you will be able to see the Account with the Solution Environment.

In the management portal go to Management Certificates and select your subscription. Then on the top click “Add Certificate”.

Click Browse to upload the certificate from your local PC. Since we already copied the full path of the certificate created we can just paste it and click Open.

Click Ok and then in the portal you will be able to see the uploaded certificate.

4- Pre-publishing steps

Before publishing the application to the cloud we need to make sure about the dependencies that are locally present on the machine but they won’t be available in the cloud. We need to check for the referenced assemblies connection strings and application configurations. If there are any third party assemblies or your local project assemblies so set the Copy Local property of the assemblies to True.

If you look at the worker and web role settings in the Windows Azure project it is having connection strings being used by diagnostics so you can uncheck the option to remove these diagnostic connection strings so that there are no dependencies.

5- Publishing from Visual Studio 2012

Now that everything is set up we can publish the solution to the cloud from VS. Right click the Windows Azure project and then click Publish. It will open the Windows Azure publish wizard in the first step Choose the subscription.

Click Next and in the Common Settings tab choose the cloud service solution, choose the staging/production environment. In the Advanced Settings tab label the deployment and select the Storage Account. Click next to finish the publishing steps and go to the summary page.

The deployment will start and the deployment progress can be seen in the Windows Azure Activity log window in Visual Studio.

After sometime you can notice in the Server Explorer that the Web and Worker role VM’s are created in the staging environment of the deployment but will be in the stopped state.

In the Server Explorer after some time it can be noticed that the VM’s are starting.

Once the deployment is completed the status will be updated to completed and the Website URL with a GUID will be created.

You can then go the the website URL generated and see the application. In the portal you can see that the solution is deployed.

6- Changing runtime configurations after deployment.

In the previous post we added a configuration key “Message” so that it can be changed after deployment into the cloud and re-deployment can be avoided. We can change the configuration from the portal, Select the Deployment and then click Configure in the top menu. A dialog having the configuration XML will appear in which the Message value can be changed.

After changing the value click OK as shown below and the changes will take effect in each instance of the web role.

You can refresh the browser where the application in the cloud was opened and see the updated message.

The Windows Azure SDK for .NET can be downloaded from here for VS2012/VS2010. After installing the SDK you would get the Windows Azure tools and Emulator to develop and test cloud solutions locally. After installing the SDK you can see the cloud template under C# as shown below. You can see the cloud service by selecting framework 4.0 and then selecting “Windows Azure Cloud Service”.

In the dialog box below you can select the different roles that are required for the cloud solution. In our scenario since we are making a simple MVC 4 application so a MVC 4 web role would be enough but to do more with the solution in the future I am adding a worker role. A web role is the front end of the azure service which can be assumed that it will be on a web server (IIS) in the cloud whereas a worker role can be assumed as a Windows Service which can be used for background processing.

The web and worker roles will be renamed from the default and click OK. After that the template for MVC 4 application will appear and we will choose the internet application.

As you can see in the solution there are three more projects along with the MVC 4 project. One is the Unit test project for the MVC. In the MVC project you can see that most of the files are the same but with one more additional file WebRole.cs. If you open this file you can see the entry point. This is the entry point which is going to start everything before the web application starts executing.

If you go to the worker project and open the WorkerRole.cs you can see the Run method and the OnStart method. The Run method will have the implementation of your code in which you can fire some events like call WCF service, monitor for storage etc.

The third Windows Azure project you can see a Web Role and a Worker Role configuration file. If you open the HelloWorldMvcWebRole file you can see the below configurations. In this configuration files we can specify how many web role instances we want in the cloud and the size of the VM. The VM size has different billing cost so we will specify the extra small VM since we don’t need much memory and processing. I will specify two instances for high availability and load balancing the web role.

In the settings tab I will add another configuration called “Message” in which I will specify a string value “Hello Windows Azure”. The advantage of this configuration is after deploying the solution in the cloud we can change the value and it would reflect in the application at runtime. Otherwise without configuration these changes would require redeployment in the cloud. So keeping these kind of settings in the configuration is an important decision while developing Azure solutions.

If you open the ServiceConfiguration.Cloud.csfg file you can see all the settings in the XML format which we specified above in the interface.

Now lets open the HelloWorldWorkerRole file and you will find the same GUI and configurations. Right now we are not doing any background processing so I will keep the instance count 1 and the VM size as Extra Small.

Now lets change some code in the Home Controller in the MVC Web role project as in the below screen and put a break point. We are just reading the “Message” configuration key from the Windows Azure project as shown in the code below. Lets hit F5 and run the project. Make sure that the “Compute Emulator” and the “Storage Emulator” which was installed with the SDK is started and the status is in the Running State in the task bar.

The output can be seen on the browser and note the URL that it is running locally on the PC with the Windows Azure Emulators.

You can open the Windows Azure Compute Emulator from the taskbar and see the deployment. You can see the two instances of the Web Role and one instance of the Worker Role as shown below. The Emulator runs on the local PC emulating the cloud and using the local storage. You can open the local store as shown below in the screen.

He has done a marvelous job writing this book, the contents of the book can be viewed at Packt Website.

The book is mainly for Developers and Administrators who can gain their knowledge in Development, Maintaining, Monitoring & Deployment of BizTalk Solutions. The book has step by step implementations (recipe) of BizTalk Solutions which follows industry best practices & patterns.

I had the honor to be one of the official technical reviewer of the book along with Randal van Splunteren, Sandro Pereira & Rene Brauwers

I have enjoyed reviewing the book specially the recipes related to Monitoring and deployment, of which most of the developers and administrators are unaware.

Congratulations Steef, it has been an outstanding effort from you authoring the book so well.

Hope this year brings the same success to me as the previous years. Happy New Year to everyone.

I used to wait for the news on the new year but this time I was really busy and my family reminded me of the award renewal date. So today I just checked my inbox for the email from Microsoft.

The demand for the web version of the BizTalk Administration console has been around by the community so I decided to develop it.

Project Description
BizTalk 2010 Web Console allows administrators/operators to perform operations below from the browser.

• Stop/Start/Restart Host Instances
• View Status of Service Instances by applying queries to the group.
• Stop/Start/Unenlist Orchestrations, Send Ports and Send Port Group
• Stop/Start Receive Locations

It works on Single/Multi-Server environment and has been tested on BizTalk Server 2009 and BizTalk Server 2010.

To deploy the application check the release notes on codeplex.

Demo

Because I read the NDA I can’t tell the level of simplicity Well I prepared a lot for EDI and RFID and I was a bit better than before. For the rest of the sections I didn’t had to prepare as I could answer them easily. In my opinion anyone working for 3+ years can pass the exam.

I have passed BizTalk 2006 and BizTalk 2006 R2 previously but they were retired on 30 June 2011.

So my passion for BizTalk compelled me to register for BizTalk 2006 R2 exam with BizTalk 2010. Even though it is retiring it was worth taking BizTalk R2 because no one is perfect and I was able to discover my weakness in BizTalk extended capabilities (RFID, AS2, EDI). So when preparing for BizTalk 2010 I am focusing on EDI and RFID which also helped me in BizTalk 2006 R2 exam.

After that I had to configure single server configuration on the destroyed cluster node. One of the Node had no issues and BizTalk was configured correctly on the other machine I was having MSDTC errors which are quite common and a lot of KB, blog posts and forum topics can be found.

First I tried to remove MSDTC by removing registry entries and then uninstalling and installing the MSDTC. By this I was able to see all the tabs instead of two in the Component Services console. Before I could see only two tabs but after deleting the keys and re-installing MSDTC I could see all the tabs (General, Options, Default Properties, Default protocols, COM Security, MSDTC). When component services management console is opened by the (dcomcnfg), I was getting the same errors by accessing the Default Protocols and MSDTC tab. Also noticed that My computer (icon was red). When I tried to open Default Properties tab I was getting the error below.

MSDTC Service
—————————
There are no more endpoints available from the endpoint mapper.

When I tried to open the MSDTC tab I got the error below and it was still showing MSDTC as a clustered resource.

—————————
Catalog Error
—————————
An error occurred while processing the last operation.

Error code 8004E00F – COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator.

When I went to the server manager I wanted to remove the Failover Cluster Manager feature and I got the error below.

[Window Title]
Remove Features Wizard

[Main Instruction]
Cannot remove Failover Clustering

[Content]
This server is an active node in a failover cluster.  Uninstalling the Failover Clustering feature on this node may impact the availability of clustered services and applications.  It is recommended that you first evict the server from cluster membership.  This can be done through the Failover Cluster Management snap-in by expanding the console tree under Nodes, selecting the node, clicking More Actions, and then clicking Evict.

It is evident that the eviction of the node, removal of the resources and destruction of the clustered was not done cleanly. I didn’t miss anything I guess as the other node was fine after removing the DNS entry from the domain. I found Symon Perriman’s post mentioning that all the nodes has to be online before evicting the nodes and destroying the cluster.

Well thanks to powershell we can force the node to be removed from the cluster. 

cluster.exe node –NodeName /force

MSDTC is healthy again and I am able to configure BizTalk on this node. Lesson learnt!

Every BizTalk/.NET developer would be familiar with the Build Action property of each item in VS. With the BizTalk project the artifacts has two options BTSCompile and None (which are self explanatory). In order to use the WCF SQL adapter metadata has to be generated as I did for this lab.

I renamed the orchestration file and type as it was mentioned in the lab, I didn’t notice the Build Action property. I deployed the projects the orchestration was not appearing in the application. I deleted the application two times, verified the assembly was in the GAC, I checked the resources of the application it had the assembly as a resource so where was the orchestration?

I checked the type of the orchestration, Type modifier everything was fine. I saw the orchestration property it was set to Content. This is the first time I have seen this, I thought something new in BTS2010, I clicked the dropdown and there were only two “usual” options without Content. I tried to reproduce this again and again, now I regret that I would have taken a screenshot before changing it.

Well after changing it to BTSCompile I could see the orchestration in the application. Did anyone of you faced the same issue?

Last year I gained knowledge, experience and more insight in BizTalk which includes SWIFT accelerator, ESB Toolkit, worked with more adapters, developed some pipelines, lots of services etc.. In the beginning of the year I worked as a sharepoint developer/administrator but BizTalk turned out to be my destiny and I got a chance in a financial institution to be with a very good BizTalk team. We delivered successful middleware projects and had effectively used the combination of BizTalk, WCF and Windows Application Fabric technologies to follow the principles of SOA. 

Hope I have a more prosperous year and I continue to serve the BizTalk community more effectively with the best of my knowledge and experience.