Day 2 is an exciting day i think for most of the participants in the conference since most of the topics as the title implies are deep dives of most of the technologies.
Here are the excerpts of some of the bits and pieces on day 2 in my perspective.
Divya and Amit did an excellent job by presenting a tool were it is seems easy to migrate from Biztalk set up into an integration account where the artifacts are directly set up on within it’s particular unit i.e. biztalk maps goes to integration account maps, and BizTalk schemas goes into integration account schemas.
It was quite impressive to see that even within internally, MS uses Logic apps as a ground tool for this.
Aside from a short disruption from the fire alarm exercise and a little lag from the demo, in the end it did worked!
Vladimir shows different set of patterns to address security policies in APIM. It was a good tip to see how he manage to do a demo within VS Code with the http plugin and do all the different security stuffs within and see the policies works out in APIM.
Kevin and Derek did an excellent job with showing the possiblities of logic apps and a gallery of best practices of which exception handling is one of them. This is quite interesting since, although Biztalk has exception handling capabilities, some solutions don’t take this into account and it’s good to mention this now in logic apps.
This is maybe the most talked topic just now specially within the Biztalk community since as most of the participants on the conference anticipated that MS seems didn’t care so much on the roadmap for Biztalk instead more focus has been into the Azure integration components… and of course Azure Integration Services (the new meaning of IaaS?)!
Day 3 has even other exciting events… of course including our own Mathias Lögdberg within amazing ’handwritten’ drawings.
Some of the events topics of which one of my favorite speakers, Richard Seroter is already out.
Even a familiar face and an impressive presentation of Dan Toomey is as well out.
Saravana stepped on stage to showboat his products BizTalk360 and Servicebus360. He started off with BizTalk360 and gave us a brief tour, he showed us how it could be used for administrating and monitoring BizTalk server environments. It comes with customizable dashboards that can in a simple way show you how your BizTalk environment are doing. BizTalk360 offers some actions in the product such as Auto Correct. Auto Correct function enables you to automatically start a resource that has been disabled. You can easily configure and set up alarms to be sent if an incident occurs such as suspended messages, ports been disabled or an SQL jobs fails. You can make actions directly in the interface, for suspended messages you can download, resume and terminate. I found the interface intriguing, and very user friendly.
They have also added the capability of monitoring some Azure Services.
Saravana didn’t go in depth and therefore left a lot to our imagination.
Saravana moved on to ServiceBus360 and quickly announced that it will be renamed to Serverless360. Servicebus360 wishes to gather all your resources that defines your integration in an “Application”. Resources can be a logic apps, queue, functions etc. It doesn’t matter if they work over different subscriptions. Serverless360 gathers all the resources and monitors them as a whole. Saravana talked a lot about the security issues in Azure and how it much easier it could be handled in Serviceless360. He talked about feature request that soon can be realized, he mentioned an edit and resubmit function that would seem useful when dealing with messages on for example a dead letter queue.
Saravana presented Atomic Scope and basically he explained that it enables you to track messages through out the integration. He said it provides an end to end visualization of the integration. It was clear that they put the business user experience before the technician. Using xpath or json etc it is possible to extract values within the message body making them searchable. Atomic scope saves the messages from BizTalk in to a separate database and makes it possible to archive messages for a long time. Its also possible to set up alarms if a message fails to reach its destination, the alarms are not customizable.