Installing Windows Azure BizTalk Services Part II
With our Windows Azure BizTalk Service now running in the cloud, we need to setup our developing environment so that we can start deploying stuff to the Cloud!!
The prerequisites for installing the SDK is:
- Visual Studio 2012
- .NET Framework 3.5.1 (Features enabled)
- .NET Framework 4.5
Because WABS also have the ability to talk to on-premise systems (such as SQL Server), you should also install the folllowing:
- SQL Server 2012
Download Windows Azure Service Bus SDK
Go to the following URL and download the latest SDK.
The SDK contains the following:
- Tools.zip (BTMMigrationTool, TPMMigrationTool)
The Edi files contains all the X12 Schemas included with WABS (from version 204 to 503).
The BTMMigrationTool is used for migrating existing BizTalk Server maps to the new WABS maps (much more on mapping in a later blog).
The TPMMigrationTool is used for migration BizTalk Server Party/Agreement setups to the new WABS EDI setup (more about EDI in WABS in a later blog).
Choose the Setup exe version according to your OS (most likely x64), and extract it.
Install the SDK
- Once extracted, run WindowsAzureBizTalkServicesSetup.exe
- Accept and click Next
- Choose everyting and click Next and then Install.
After installing all the packages needed, we will now be asked to configure a Management Service for using the LOB Services used for communicating from our BizTalk Service to our on-premise systems (SQL, SAP, Oracle, Siebel -> using the BizTalk Server Adapter Pack).
Although we will not use this for now, we might as well configure it immediately.
- For the identity of the Application Pool used by the Management Service, choose Network Service.
- In the Configuration Store Database setup, specify our local SQL Server and click Next.
- Choose a Password for the master key used for encrypting sensitive data in the Configuration Store Database (note: if this is anything but a sandbox environment, you need to remember this password). Click Next
- Keep port 8080 and un check the use of SSL communication with your management service (unless this is production and you already have an existing SSL certificate on the server).
- Configure the Management Service, and our setup should now be complete.
With both our WABS running in the cloud and the SDK installed on our development environment, we are now ready to deploy our first solution to Azure!
First confirm that everything is installed correctly by opening Visual Studio 2012, and verifying that you are now able to create BizTalk Services projects:
In the next blog post we will create our first simple bridge that accepts all types of messages and routes them to an FTP folder, all residing in Azure and no local services etc. needed. Stay tuned..