You may have noticed it. There is a new Windows Azure Service released on the Windows Azure portal: Windows Azure BizTalk Services. This blog posts helps you getting started.
It explains the different steps you need to take in order to get you up and ready to begin development.
The official tutorials are to be found online: here.
Get the SDK
To download the SDK, adapter service and other items, you can go to this link. There you can download the following items for the Windows Azure BizTalk Services preview:
- BizTalk Adapter Service x64
- BizTalk Adapter Service x86
- BTMMigrationTool (this is to migrate BizTalk mappings to the new mapper)
- MicrosoftEdiXsdTemplates (all X12/EDI schemas)
- WindowsAzureBizTalkServices SDK
Once you have everything installed, your local machine is ready for WABS development
Register for the Windows Azure BizTalk Services preview
You should go to the Azure account portal and log on with your Microsoft account, linked with the subscription that you want to get registered for WABS. On the portal, select the Preview Features button and you can register for the BizTalk Services preview. After a while (depending on the available preview slots), you can be allowed to the program.
Create a BizTalk Service
Once you are registered and allowed to the preview program, you can go to the management portal and create a BizTalk Service
It is not a trivial process, so here you have some tips and a step by step guide:
Step 1: go to the BizTalk Services tab
Click on the BizTalk Services tab and you will be able to click the ‘Create a BizTalk Service’ link.
Step 2: specify your service settings
In the first step of the wizard, you’ll have to specify some settings:
- BizTalk Service name: the prefix to the .biztalk.windows.net that will be used for your service DNS
- Edition: the specific edition you will chose. Important! : the edition influences your costs, so be aware of this. The details on the editions will be discussed later on. Developer is the one you should use for all your PoC / play ground
- Region: the data center where your services will be running
- Tracking database: this is a database on your own server that will be used for all tracking information! This database can be used for your own tracking queries. You can add it on a new server, or an existing server.
It is strongly advised to run the database in the same data center as your service!
- Subscription: the subscription where you will deploy your service.
Step 3: Database settings
In the database settings, you can provide a new database, or link to an existing one. Here you need to specify some settings, based on your selection.
Step 4: Access Control namespace and monitoring settings
Here it becomes tricky. You need to specify an ACS namespace that will be used to create items in, by the Windows Azure BizTalk Service account.
When creating a new namespace, you will have to do this through the Active Directory tab and create an ACS namespace there.
- To get the user and password settings, you need to click on the Manage button in the Access Control Namespace section of the Active Directory module in the Azure portal. This will bring you to the ‘old’ ACS management portal where you can get your user.
- This should be done by selecting the ‘Management Service’ link on the left.
- Then either use the existing ManagementClient service account or create a new one
- Click the service account you want to use and then click the Password link.
- To get the password, you can click the Show Password button.
The user name is the name of the service account.
Step 5: SSL Certificate
In the last step before creation, you need to upload the private key of an SSL certificate (pfx) that is linked with your DNS.
You can change this later and use a self-signed cert for now, by executing the following in the developer command prompt:
makecert -pe -r -n "CN=<yourservicename>.biztalk.windows.net" -e "01/01/2015" -ss my
After doing this, you can export your PFX from your certificate store and upload it here.
Step 6: Be patient
Once you click create, it can take up to 30 minutes to have your service generated.
Step 7: Register the service on the ‘Silverlight’ portal
And just when you thought everything was finished, then you have to register your service in the BizTalk management portal. This portal is a Silverlight portal that is there during the preview.
Click on the Manage button and you will be taken to the Silverlight portal
On this portal, you have to specify three settings:
- BizTalk Service: the name of the BizTalk Service you specified in the first step
- Issuer name: the name of an ACS user that belongs to your ACS namepsace
- Issuer secret: the shared secret key of that user
More blog posts coming soon
As a launch partner, we have been working with Windows Azure BizTalk Services for more than a year now and we have prepared a number of blog posts. In the coming days there will be blog posts on the architecture and features of this brand new service.