In preparation for a talk I’m giving soon I thought I’d show a quick walkthrough of
setting up the newer BizTalk Services (preview) in Azure.
In order to setup BizTalk Services it helps to have the following
things created first (the BizTalk Services creation wizard will walk you creating
a few of them,
but it failed for me many times, so easier to create them prior)
- A Storage account in the region where the BizTalk Services are to be located.
- An Azure SQL Server in which to create a Tracking Database on.
-
An Access Control Service Namespace – do this through Azure Management -> Active
Directory. -
The BizTalk Services Creation Wizard will ask you for a User/Pass in which to interact
with ACS through – the simple approach
is to use the ManagementClient user + pass. (it’s auto created for
you :)) -
An Exported X509 Certificate with Private Keys present – a *.pfx
file.
NOTE – the Subject name must match your BizTalk Services ServiceName
** The Cert should not have an expiry of more than 5 years! **
-
e.g. C:\>makecert -r -pe -n “CN=breezebizsvcdev.biztalk.windows.net” -ss
My -e “01/01/2015” -
then export it out from the User certificate store and you’ve got your certificate
file. - TO GET BUILDING – Grab the latest SDK from here http://www.microsoft.com/en-us/download/details.aspx?id=39087&utm_source=feedburner&utm_medium=twitter&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29#tm
The Access Control Services
Right – let’s walk through the BizTalk Services Creation Wizard.
Let’s fire up the Wizard and get grooving.
Wizard – Page 1
So farso good, opened up the wizard and filled in Page 1 details – note I decided
to create a SQL Server here (I’d actually forgotten the password of another one we
use)
It’s also important to note the Region – WEST US. (make sure that
whatever else you create is in that region as well, otherwise things might take *alot*
longer
than anticipated.
Wizard – Page 2
Time to hit NEXT Arrow – all pretty straight forward.
Wizard – Page 3
The Access Control Namespace was something I created earlier and the ManagementClient user
is an auto created user in ACS.
(I omitted the password here – but you get that from the ACS management portal).
Locations – all important.
Wizard – Page 4
Finally the SSL Certificate with the Expiry of no more than 5 years.
The important thing here is that clients will connect to BizTalk Services via TLS/SSL.
If this is a home grown cert – as this one is, keep in mind that clients will need
to
’trust’ this certificate.
Hit the tick and you’re on your way
Stay tuned for the next post where we turn this into something REAL! 🙂
More info for you –
Windows Azure BizTalk Services or WABS (we can’t have a new thingy without a new acronym):
– forums
– detailed
steps on BizTalk Services
Blog Post by: Mick Badran