by stephen-w-thomas | Oct 9, 2016 | Stephen's BizTalk and Integration Blog
In May, I gave a session at Integrate 2016 titled Azure IaaS Essentials for the BizTalk Developer (watch online now).
In that session I outlined that prices for Azure resource vary by data center.
In case you did not know, the price you pay for Azure resources in a US datacenter can vary from that in Brazil (expensive) , Japan, Indian, and so on.
What is interesting though, is that event data centers in the United States have different prices.
From what I’ve seen, the East 2 and West 2 data centers seem to have better prices than a lot of the other US data centers.
I checked some prices on Virtual Machines and Storage – not all Azure resource – but some prices were as much as 13% lower!
If you use a lot of Azure saving up to 13% or maybe more can really add up.
The key take-a-way is to ensure you check the prices of the resources in multiple data centers if you have the ability to do so for your scenario.
by Rene Brauwers | Jul 23, 2013 | BizTalk Community Blogs via Syndication
So you need a multi-server BizTalk Environment, and you want it automagically provisioned in one click?
A zip file with some powershell scripts which will perform the following tasks for you (all in one click) 🙂
1.Basic configured Virtual Network
includes creation of an affinity group if not available
includes creation of storage if not available
2. Configured Domain Controller
includes Active Directory Installation
includes BizTalk Service Accounts
includes BizTalk Groups
3. Configured SQL Server joined to the domain
includes firewall changes
includes msdtc changes
includes sql protocol changes
ensures domain admin to be added to the sql-server sysadmin role
4. Fully Configured! BizTalk Server joined to the domain
includes all BizTalk Features with exception of BAM Alerts
includes firewall changes
includes msdtc changes
includes configuration of hosts / host instances and adding them to the adapters
1. Download the powershell scripts here
2. Unzip
3. Download your azure publisher profile here
4. Open the script in your favorite editor using Administrative Privileges
5. Modify the script named Start_BizTalk_Multi_Server_Azure_Provisioning_v1.0.ps1
6. Run the script and wait.
Powershell executing
<embed width=”425″ height=”355″ type=”application/x-shockwave-flash” src=”http://www.youtube
allemagne viagra.com/v/dSIsRK0gJa0&hl=en” />
BizTalk Server End Result
Special thanks and credits go out to:
Peter Borremans, who wrote the following article which got me going
Jeremie de Villard, I used his adapted BizTalk Configuration Tool and Task-Schedule script to auto-configure BizTalk
Scott Banwart, I used his powershell script as basis for configuring the BizTalk Hosts, Host Instances and Adapters
Please note; the scripts are as is; go ahead and play with it. Most definitely you can clean it up more and make it more efficient 😉 If you make any modifications, feel free but be nice and SHARE!! 🙂
This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-ShareAlike 3.0 Unported License. http://creativecommons.org/licenses/by-/3.0/
Cheers
René
by stephen-w-thomas | Oct 9, 2012 | Downloads
This tool is intended to get you moving in the right direction and not intended to solve all your problems out of the box. You will need to use the Windows Azure REST API Reference guide when working with this tool.
I have provided a few sample Request Body templates for Creating a Hosted Service, Creating an Azure Storage Account, Adding a Virtual Machine Disk, and Creating a Virtual Machine (note to create a VM is a multi-step process, see below). Others can easily be added by using the online reference guide.
To use this sample tool you need to configure some basic information inside the App.Config file. You need to set the path to your management certificate, your subscription id, and the path to the folder location of your POST bodies.
<!-- Enter the full path to the Windows Azure Management Certificate. More details at http://msdn.microsoft.com/en-us/library/windowsazure/ee460782.aspx -->
<add key='CertificatePath' value='C:\DemoFolder\yourcert.cer'/>
<!-- Subscription ID for the account and must match Management Certificate -->
<add key='Subscription' value='your account id' />
<!-- Default folder location of REST API Post Bodies. This exists to save time selecting the Post Body file. -->
<add key='PostBodiesFolder' value='C:\DemoFolder\WindowsAzureRESTApiHelper\WindowsAzureRESTApiHelper\RESTAPIBodies\'/>
How to Use this Sample Tool
1. Once the App.config is setup simply launch the tool. It was built with Visual Studios 2010 but should upgrade to 2012 without issues.
2. Select one of the GET, POST, or DELETE radio buttons.
3. Select your basic action from the drop down or paste in your URL into the text box.
4. Click on “Make A REST Service Call” to complete your request.
5. If you are doing a POST, you will be prompted to select the body of your request.
6. If you do a POST or a DELTE that is an asynchronous process a Request ID is returned in the Response Header. The tool will detect this and auto populate a URL to check the result of the request.
7. You can keep clicking the “Make REST Service Call” button to check the results of the submitted operation until it is competed.
It is that simple!!! Like I said before, this tool is intended to be a starting point for someone new to working with the Windows Azure REST API’s.
Other useful pieces of information
1. To create a new Virtual Machine you need to do the following: First, create the Service using Create Hosted Service. Second, you can use the Quick Create using that Service to create the Virtual Machine.
2. If you plan to work with Virtual Machines using the API, read this blog post about the URLs.
3. If you run into issues the best way to confirm the URL and Post Body is to perform the actions using PowerShell with Fiddler running. This will show the URL and exact Post Body.
by stephen-w-thomas | Oct 9, 2012 | Stephen's BizTalk and Integration Blog
Windows Azure has a few different, somewhat disjointed, toolsets available to create new artifacts and maintain existing ones. The best known is the Web Portal. Very quickly when working with the web portal you discover the portal is not able to do all the tasks needed to support development and maintenance. This brings into play Windows Azure PowerShell Commands, a .Net SDK, and REST API.
If you are new to working with the Windows Azure REST API or if you are looking for sample code working with the Windows Azure REST API, this tool can help you.
This tool is intended to get you moving in the right direction and not intended to solve all your problems out of the box. You will need to use the Windows Azure REST API Reference guide when working with this tool.
I have provided a few sample Request Body templates for Creating a Hosted Service, Creating an Azure Storage Account, Adding a Virtual Machine Disk, and Creating a Virtual Machine (note to create a VM is a multi-step process, see below). Others can easily be added by using the online reference guide.
Download: Windows Azure REST API Sample Tool
To use this sample tool you need to configure some basic information inside the App.Config file. You need to set the path to your management certificate, your subscription id, and the path to the folder location of your POST bodies.
<!-- Enter the full path to the Windows Azure Management Certificate. More details at http://msdn.microsoft.com/en-us/library/windowsazure/ee460782.aspx -->
<add key='CertificatePath' value='C:\DemoFolder\yourcert.cer'/>
<!-- Subscription ID for the account and must match Management Certificate -->
<add key='Subscription' value='your account id' />
<!-- Default folder location of REST API Post Bodies. This exists to save time selecting the Post Body file. -->
<add key='PostBodiesFolder' value='C:\DemoFolder\WindowsAzureRESTApiHelper\WindowsAzureRESTApiHelper\RESTAPIBodies\'/>
.csharpcode, .csharpcode pre
{
font-size: small;
color: black;
font-family: consolas, “Courier New”, courier, monospace;
background-color: #ffffff;
/*white-space: pre;*/
}
.csharpcode pre { margin: 0em; }
.csharpcode .rem { color: #008000; }
.csharpcode .kwrd { color: #0000ff; }
.csharpcode .str { color: #006080; }
.csharpcode .op { color: #0000c0; }
.csharpcode .preproc { color: #cc6633; }
.csharpcode .asp { background-color: #ffff00; }
.csharpcode .html { color: #800000; }
.csharpcode .attr { color: #ff0000; }
.csharpcode .alt
{
background-color: #f4f4f4;
width: 100%;
margin: 0em;
}
.csharpcode .lnum { color: #606060; }
How to Use this Sample Tool
1. Once the App.config is setup simply launch the tool. It was built with Visual Studios 2010 but should upgrade to 2012 without issues.
2. Select one of the GET, POST, or DELETE radio buttons.
3. Select your basic action from the drop down or paste in your URL into the text box.
4. Click on “Make A REST Service Call” to complete your request.
5. If you are doing a POST, you will be prompted to select the body of your request.
6. If you do a POST or a DELTE that is an asynchronous process a Request ID is returned in the Response Header. The tool will detect this and auto populate a URL to check the result of the request.
7. You can keep clicking the “Make REST Service Call” button to check the results of the submitted operation until it is competed.
It is that simple!!! Like I said before, this tool is intended to be a starting point for someone new to working with the Windows Azure REST API’s.
Download: Windows Azure REST API Sample Tool
Other useful pieces of information
1. To create a new Virtual Machine you need to do the following: First, create the Service using Create Hosted Service. Second, you can use the Quick Create using that Service to create the Virtual Machine.
2. If you plan to work with Virtual Machines using the API, read this blog post about the URLs.
3. If you run into issues the best way to confirm the URL and Post Body is to perform the actions using PowerShell with Fiddler running. This will show the URL and exact Post Body.
