User Experience design has always been, and continues to be, a field riddled with ambiguous labeling and nomenclature. We hear all sorts of conjecture and debate as to what terms have what specific meaning. Are profiles and personas the same thing? When exactly do wireframes become mock-ups? Is “mock-up” supposed to hyphenated? These are issues […]
Blog Post by: Matt Donahue
On the latest version of BizTalk (2013): a new adapter was introduced for natively working with REST endpoints, using WCF technology: the WCF-WebHttp Adapter. After the beta version was released we could find some very good articles about this adapter, but since it is a new adapter there’s a lot of ground to cover.
With the new WCF-WebHttp Adapter that shipped in BizTalk Server 2013 we now have the ability to specify which HTTP verbs to use – this opens up the possibility of invoking RESTful style applications. In this post, I’ll investigate how we can RESTfully invoke an endpoint that exposes data via JSON using the GET verb […]
Blog Post by: Nick Heppleston
May 6th and 7th: BizTalk Boot Camp 2013 in Charlotte BizTalk Boot Camp is a free 2 days technical event conducted by Microsoft to focus on some of the new offering in Microsoft BizTalk Server 2013, Windows Azure BizTalk Services and BizTalk server in VM Role (Azure IaaS). In these 2 days, attendees will learn […]
The post BizTalk360 Tour of America appeared first on BizTalk360 Blog.
Blog Post by: Saravana Kumar
In an AppFabric Cache you can segregate your cached data into regions. You create a region using the CreateRegion() method of the DataCache object.
Working on a recent project I was asked How do I check if a cache exits ? There is no RegionExits() method on the DataCache object.
To check if a region exists you can make use of the CreateRegion() method.
The CreateRegion returns a bool. As per the documentation a value of true indicates that the region created successfully. A value of false indicates that the region already exists.
Blog Post by: Shinva
This month I will be introducing two BizTalk community members from France. Almost two weeks ago I introduced Maxime Labelle and today the story will be on J%u00e9r%u00e9my Ronk.
J%u00e9r%u00e9my is a young married man, who lives near Paris. He is an active swimmer and likes to hike in the mountains. In his spare time he does all sorts of things like studying other technologies than BizTalk such as StreamInsight,
While looking into purchasing MSDN licenses for a client here’s what I found:
For the US:
Now when you change the drop down from US to Australia we get these prices (given
that $AUD 1 = (approx) $USD 1
So for e.g. take a MSDN – VS.NET Test.
Aussie Dollar = $3,460 US= $2,170 which
equates to $AUD 1 = $USD 0.627
this is what happens when living in a 3rd world country. –
absolutely outrageous.
Blog Post by: Mick Badran
Published By: Bill Chesnut
I have just finished a series of BizTalk 2013 Environment Installs and was testing one of my new development environments and deploy the HelloWorld SDK Sample (issues with the samples will be covered in another blog post) and dropped a couple of sample message in and then opened the BizTalk 2013 Admin Console, clicked on the Group Hub and then click Completed instances and to my surprise nothing. I proceeded to go through my normal checks, application started, hosts started and looking in the output folder, the output message was there but still not tracking. I then looked at the ports and turned tracking on, but that should not be necessary, submitted a couple more message and still nothing in the Completed instances.
I then looked at the default pipelines to make sure tracking was turned on
I opened the PassThruReceive and the tracking was on
I then opened the XMLReceive and No Tracked Events were enable, found the cause of my missing Completed instances
I enabled the tracking on the PassThruTransmit, XMLReceive and XMLTransmit. I think submitted some more messages, I now have the Tracked events for the pipelines, still missing the ones from Orchestration, not sure whether this is a binding issue with HelloWorld SDK sample of a new default.
I opened the Tracking page on the HelloWorld Orchestration and it was turned off also, turned on Track Events and now I have what I was expecting.
Hope this helped you figure out your issues with BizTalk 2013 Tracking.
*** THIS EVENT IS CURRENTLY GOING ON WORLD WIDE even as we speak! ***
The wrap up of the day:
Saturday morning was nothing short of sensational in Sydney today, early morning sun,
bright blue skies, smell of coffee and a city that felt like it was snoozing and waking
for some playtime.
I walked into a room of curious minds, eager eyes and folks that were thinking of
possibilities in technology. This technology was Windows Azure.
We were above capacity & for the first time I would be relieved if there were
a few ’no-shows’but none happened. Even at 5pm we nearly had a full house.
Firstly I’ve got to thank – you the students for a great day, fantastic questions
and giving your precious weekend time.
Secondly the expert speakers that have huge experience in the field.
and finally all the sponsors & people that helped enable us to
bring this to you:
What were the plans for the day:
The Agenda was set to:
|
SYDNEY |
Start |
Duration |
Speaker |
|
Introductions |
9:15:00 |
15 |
|
|
Compute |
9:30:00 |
30 |
Mark |
|
SQL |
10:00:00 |
30 |
Don |
|
Lab |
10:30:00 |
60 |
|
|
Cloud |
11:30:00 |
30 |
Mick |
|
Building |
12:00:00 |
45 |
Olaf |
|
Lab |
12:45:00 |
60 |
|
|
Virtual |
1:45:00 |
30 |
Mark |
|
Connecting |
2:15:00 |
30 |
Mick |
|
Lab |
2:45:00 |
60 |
|
|
Q&A |
4:15:00 |
Some Interesting facts:
– we had 3 MVPs in the room (that I knew of)
– we had 2 Microsoft VTSPs
– a student drove 3.5hrs one way to be here with us during the day, then back to Canberra
again after class. Massive commitment.
– we all came with Azure Subscriptions ready to go.
– a student created a WebSite, Database + Worker role working in a solution together
during the day.
– Olaf has his Mobile Services demo fail (even though it worked at 10pm last night)
due to the recent Azure Portal update at 2am this morning. He did have a PlanB, the
autogenerated code from the Portal during the Mobile Services Application creation,
generates un-compilable code for now. Well done Olaf, some nice tap dancing.
(Olaf working his magic)
(looking out to the North Wing)
Thanks to Magnus a fellow Azure MVP – for setting all this up world wide and good
luck to all the other countries.
If you blog about it – then be sure to use the hashtag #globalwindowsazure.
Mick out.
Blog Post by: Mick Badran
Something that you’ve always wanted at your finger tips all the public IP ranges for
the Azure Data Centers.
http://www.microsoft.com/en-us/download/details.aspx?id=29840
<!–Below address ranges are represented using CIDR notation–>
<!–For detail on how to interpert CIDR notation refer http://en.wikipedia.org/wiki/CIDR_notation–>
<regions>
<region name=”Europe”>
<subregion name=”North Europe”>
<network>213.199.160.0/20</network>
<network>213.199.184.0/21</network>
<network>137.116.224.0/19</network>
<network>157.55.230.160/27</network>
<network>157.55.3.0/24</network>
<network>168.61.80.0/20</network>
<network>168.61.96.0/19</network>
<network>168.63.32.0/19</network>
<network>168.63.64.0/20</network>
<network>168.63.80.0/21</network>
<network>168.63.92.0/22</network>
<network>65.52.224.0/22</network>
<network>65.52.228.0/22</network>
<network>65.52.248.0/21</network>
<network>65.52.64.0/20</network>
<network>94.245.104.0/21</network>
<network>94.245.112.0/20</network>
<network>94.245.88.0/21</network>
<network>137.116.224.0/19</network>
<network>157.55.230.160/27</network>
<network>157.55.3.0/24</network>
<network>168.61.80.0/20</network>
<network>168.61.96.0/19</network>
<network>168.63.32.0/19</network>
<network>168.63.64.0/20</network>
<network>168.63.80.0/21</network>
<network>168.63.92.0/22</network>
<network>65.52.224.0/22</network>
<network>65.52.228.0/22</network>
<network>65.52.248.0/21</network>
<network>65.52.64.0/20</network>
<network>94.245.104.0/21</network>
<network>94.245.112.0/20</network>
<network>94.245.88.0/21</network>
<network>137.135.128.0/17</network>
</subregion>
<subregion name=”West Europe”>
<network>157.55.10.0/27</network>
<network>157.55.10.32/27</network>
<network>157.55.10.64/26</network>
<network>157.55.12.0/28</network>
<network>157.55.9.112/28</network>
<network>137.116.192.0/21</network>
<network>137.116.200.0/21</network>
<network>157.55.8.128/28</network>
<network>157.55.8.144/28</network>
<network>157.55.8.160/28</network>
<network>157.55.8.64/26</network>
<network>168.63.0.0/19</network>
<network>168.63.96.0/19</network>
<network>213.199.128.0/21</network>
<network>213.199.136.0/22</network>
<network>213.199.180.112/28</network>
<network>213.199.180.192/26</network>
<network>213.199.180.32/28</network>
<network>213.199.180.96/28</network>
<network>213.199.183.0/24</network>
<network>65.52.128.0/19</network>
<network>94.245.97.0/24</network>
<network>137.117.128.0/17</network>
<network>168.61.56.0/21</network>
</subregion>
</region>
<region name=”Asia”>
<subregion name=”East Asia”>
<network>111.221.64.0/22</network>
<network>111.221.69.0/25</network>
<network>137.116.160.0/20</network>
<network>168.63.128.0/19</network>
<network>168.63.192.0/19</network>
<network>207.46.67.160/27</network>
<network>207.46.67.192/27</network>
<network>207.46.72.0/26</network>
<network>207.46.77.224/28</network>
<network>207.46.87.0/24</network>
<network>207.46.89.16/28</network>
<network>207.46.95.32/27</network>
<network>65.52.160.0/19</network>
</subregion>
<subregion name=”South East Asia”>
<network>111.221.16.0/21</network>
<network>111.221.80.0/20</network>
<network>111.221.96.0/20</network>
<network>137.116.128.0/19</network>
<network>168.63.160.0/19</network>
<network>168.63.224.0/19</network>
<network>207.46.48.0/20</network>
</subregion>
</region>
<region name=”USA”>
<subregion name=”South Central US”>
<network>157.55.103.32/28</network>
<network>157.55.103.48/28</network>
<network>157.55.153.224/28</network>
<network>157.55.176.0/20</network>
<network>157.55.192.0/22</network>
<network>157.55.196.0/22</network>
<network>157.55.200.0/22</network>
<network>157.55.80.0/22</network>
<network>157.55.84.0/22</network>
<network>168.62.128.0/19</network>
<network>65.52.32.0/21</network>
<network>65.54.48.0/21</network>
<network>65.55.64.0/20</network>
<network>65.55.80.0/20</network>
<network>70.37.160.0/21</network>
<network>70.37.48.0/20</network>
<network>70.37.64.0/18</network>
</subregion>
<subregion name=”North Central US”>
<network>157.55.136.0/21</network>
<network>157.55.151.0/28</network>
<network>157.55.160.0/20</network>
<network>157.55.208.0/21</network>
<network>157.55.216.0/22</network>
<network>157.55.220.0/22</network>
<network>157.55.24.0/21</network>
<network>157.55.252.0/22</network>
<network>157.55.60.224/28</network>
<network>157.55.60.240/28</network>
<network>157.55.73.32/28</network>
<network>157.56.12.0/22</network>
<network>157.56.24.160/28</network>
<network>157.56.24.176/28</network>
<network>157.56.24.192/28</network>
<network>157.56.28.0/22</network>
<network>157.56.8.0/22</network>
<network>168.62.224.0/20</network>
<network>168.62.96.0/19</network>
<network>207.46.192.0/20</network>
<network>209.240.220.0/23</network>
<network>65.52.0.0/19</network>
<network>65.52.106.128/27</network>
<network>65.52.106.16/28</network>
<network>65.52.106.160/27</network>
<network>65.52.106.192/27</network>
<network>65.52.106.224/28</network>
<network>65.52.106.240/28</network>
<network>65.52.106.32/27</network>
<network>65.52.106.64/27</network>
<network>65.52.106.96/27</network>
<network>65.52.107.0/28</network>
<network>65.52.192.0/19</network>
<network>65.52.232.0/22</network>
<network>65.52.236.0/22</network>
<network>65.52.240.0/22</network>
<network>65.52.244.0/22</network>
<network>65.52.48.0/20</network>
<network>168.61.128.0/17</network>
</subregion>
<subregion name=”East US”>
<network>137.117.32.0/19</network>
<network>137.117.64.0/18</network>
<network>157.56.176.0/21</network>
<network>168.61.32.0/20</network>
<network>168.61.48.0/21</network>
<network>168.62.160.0/19</network>
<network>168.62.32.0/19</network>
<network>137.116.0.0/17</network>
</subregion>
<subregion name=”West US”>
<network>137.117.0.0/19</network>
<network>137.135.0.0/18</network>
<network>157.56.160.0/21</network>
<network>168.61.0.0/19</network>
<network>168.61.64.0/20</network>
<network>168.62.0.0/19</network>
<network>168.62.192.0/19</network>
<network>168.63.88.0/24</network>
</subregion>
</region>
</regions>
Blog Post by: Mick Badran