Integrate 2022

INTEGRATE 2022 – Day 3 Recap

BizTalk360

Events

Jun 15, 2022

Table of contents

  1. Getting Started Migrating from BizTalk to Azure
  2. Long lasting build and release for integration
  3. Introducing Document360
  4. Data Mapping in the Microsoft Cloud
  5. My 10 favorite Azure API Management tips and tricks!
  6. Automated Testing of Logic Apps
  7. DevOps with Azure Integration Services
  8. INTEGRATE 2022 – Closing note

After an exciting Day 1 and Day 2 at INTEGRATE 2022, the stage was perfectly set for the last day of the event.

Before you proceed further, we recommend you take a read at the following links – Day 1, Day 2.

#1: Getting Started Migrating from BizTalk to Azure – (Stephen W. Thomas)

Stephen W Thomas, one of the speakers of Integrate started the session “Getting started migrating from BizTalk to Azure” with a short introduction about himself.  

Stephen explained his current project related to migration from BizTalk server 2013 to Azure. His primary goal is to shut down the BizTalk environment. This session is based on two secrets related to BizTalk migration. Let’s see:

  • Building courage
  • Attacking the problem

Building courage

Most Azure experts are usually not interested in learning BizTalk, but BizTalk experts are usually excited to learn Azure.

BizTalk Supported features

There are a few kinds of stuff that are supported by BizTalk

  • Logic Apps
  • Service Bus
  • Blob storage
  • Event Hub

Azure Integration features

There are a few kinds of stuff that are supported by Azure

  • Integration account
  • WCF – relay
  • API management
  • Key Vault
  • Functions
  • On Prem Gateway

Three focus areas

  • Logic Apps
  • Service bus
  • API management

Stephen shared some resources which you can get started with:

  1. AZ-204 Developing solutions for Microsoft Azure
  2. Guru has great resources and learning paths
  3. Pluralsight courses
    • Microsoft Azure Developer: Enterprise Messaging and Eventing
    • Microsoft Azure Developer: Creating Enterprise Logic Apps
    • Azure Logic Apps: Getting started
    • Azure Logic Apps: Fundamentals
  4. Quick Learn – AIS
  5. Live and instructor-led
    • Through BizTalk360 BizTalk Server 2020 Hybrid options

Do not get confused

Consumption vs Standard

  • Start with consumption
  • Move to Standard tier

Attacking the problem

Why Azure Migration

You can lower or remove upgrade and software assurance costs. More security is provided and you can also reduce or remove on-premises resources. Further he explained some of the architecture scenarios.

Find the Right balance

  • Solutions usually vary for every client
  • Existing components
  • Disaster Recovery

The session ended with exciting questions and answers.

#2: Long lasting build and release for integration – (Mattias Logdberg)

Mattias presented the session on Long-lasting build and release for Integration focusing on the integration developers. Integration developers, build more services than any other team and they also want to have as little maintenance as possible. This could mean it takes years before they come back and revisit something they built. At that time, they really want to have that deep understanding and confidence to make the change swiftly without spending a lot of investigation.

Mattias started the session by giving a glimpse of how his life started as a consultant and his experience in providing build and release for different organizations. He also threw light on the support required for organizations during a long-lasting build and explained the efforts and parameters involved in it. This session primarily focused on integration developers encouraging them to develop along with lasting build and release setup.

Integration developers

The session was a full-fledged demo presentation. To make the session more interesting Mattias created a live environment. He explained the working principle of each component involved in it and its role in the architecture. The demo session was complete coverage of the build, testing, and execution of a real-time infrastructure with a long life.

key takeaways

Mattias concluded the session with an overview of Managed Identities and a few resources on how to achieve an efficient build and release for integration.

#3: Introducing Document360 – (Saravana Kumar)

Our Founder and CEO, Saravana Kumar, briefly introduced Document360 and its features to the attendees at INTEGRATE 2022. Saravana explained how Kovai.co has been using Document360 internally, and how other companies can take advantage of it. He remarked how the company is literally being run using Microsoft Teams and Document360.

While sharing Kovai.co’s homepage on Document360, where knowledge bases of our various products—including Biztalk360, Serverless360, Document360, Atomic Scope, and Cerebrata, he chose to display Biztalk’s knowledge base page.

Introducing Document360 Document360 features

Kovai.co has been using Document360 for all their product documentation requirements. The product has an intuitive search engine, that enables easy retrieval of relevant articles. Granular level access can be implemented in the system, where you classify sections for private or public access with additional controls.

BizTalk360 knowledge base

Recalling how most enterprise companies earlier managed knowledge bases on Word docs or OneNote, where it would often get overcrowded and information may even get lost. This was especially hard when multiple teams had to collaborate on a document.

Document360 solves most of these issues, as every document is maintained within an internal platform. The workspace has a tab ‘versions’—where editing history and editor details can be viewed. It also has an extensive security mechanism that detects all the security gaps within your knowledge base.

The knowledge base created using Document360 helps streamline the entire documentation process by creating documents for organizational silos.   “The product was born out of our own frustration of not finding the right documentation tool in the market for software documentation.  Document360 is easy to use, allowing you to create a new category title or an article.

Recently, Document360 introduced the freemium model allowing users to try the product. The paid subscription starts as low as $99.  

#4: Data Mapping in the Microsoft Cloud – (Dan Toomey)

Dan Toomey, Microsoft Azure MVP started the session by answering one of the most commonly asked questions “Why transformation?”

Data Mapping

Transformation in Azure Integration Services

Azure Logic Apps, Functions, API Management, Event Grid, Service Bus, and Data Factory are the main Azure Integration Services. Still, among these, he mentions that only 4 services can help you perform the transformation.

The rest of his talk focuses on 6 different scenarios involving the Azure integration Services that are highlighted in the below image.

Azure Integration Services

Method #1: Logic Apps / BizTalk Maps (Export & Upload a BizTalk Map)

This would be helpful if you are looking to migrate BizTalk Server to the cloud. The notable features of BizTalk Maps include a graphical editor, 80+ functoids, self-documenting & more. He mentioned that BizTalk Maps are intuitive for creating transformations as you can also host them in Azure using Logic Apps.

Dan then detailed the steps to migrate those Maps to Logic Apps Standard or Consumption. One thing to note here is you cannot have .NET-based functoids in the Standard version

Logic Apps / BizTalk Maps

Method #2: Logic Apps / XSLT (Upload manually coded XSLT)

It follows almost a similar method as BizTalk Maps, but here you can try using XSLT 2.0 or 3.0 to solve the problem with unsupported functoids. He showcased a recorded demo to perform transformation using XSLT templates and Logic Apps.

Method #3: Logic Apps / Liquid (Execute a Liquid Template)

Liquid is a templating language that can display data using placeholder tags. It supports iteration, conditional logic, etc. Also, it works best for JSON, XML and text (e.g., CSV). Liquid templates in Logic Apps support 4 major actions: Transform JSON to JSON, JSON to text, XML to JSON, and XML to text.

Method #4: Azure Function

Azure Functions supports Liquid templates, XSLT 2.0 / 3.0 and unit test/debugging is easy to perform. So, here he mainly explained how to perform transformation using XSLT, Liquid Template or just plain code along with a live demo.

Method #5: API Management

In this method, transformation can be done using API policies where you can convert XML to JSON, JSON to XML, execute XSLT, find and replace string or the message body. It can be used in different types of scopes and policy sections like Inbound, outbound, and on-error.

Method #6: Data Factory (Transform using Mapping Data Flows)

It allows transforming data as part of an ETL or ELT flow. Data Factory can perform a variety of transformations, including Aggregate, Conditional Split, Filter, Lookup, Stringify and Flatten. It also supports chaining multiple transformations.

#5: My 10 favorite Azure API Management tips and tricks! – (Toon Vanhoutte)

The fourth session of Day 3 was taken over by Toon Vanhoutte, sharing his “Top 10 favorite Azure API Management tips and tricks”. During the session, he kept people interacting with him by conducting a poll to get their responses and stated the right way to respond to the corresponding scenario. He also shared the links to blogs to know about the execution of each tip and trick in detail. The blogs seem to explain the need for it, the method of handling, and the result that could be expected.

1. Disaster Recovery

Automatic Backups for Azure API Management

Azure API Management tips Disaster Recovery

2. Contracts

Dynamically Expose Open API definitions in Azure API Management

The best contract is to set up your own definition for API’s that you share with the customers, expose your Open API Definition, using the options below for the specification

  • Download from the Azure Portal
  • Export from the Developer Portal
  • Dynamically expose your own API Connection by creating them for specific requirements.
  • Contracts

3. Troubleshooting

Send API Inspector Traces to Application Insights

To Troubleshoot the issues in production, Application Insights is a better way. To have a record of every policy being executed, one can configure the verbosity from the Azure resource manager, this will eventually help one to identify the errors made with a policy with ease.

Azure API Management tips Troubleshooting

4. Stack Traces

Hide Stack Traces in a smart way in Azure API Management

Azure API Management tips Stack Traces

5. Reporting

Emit Custom Metrics from Azure API management

  • On the monitoring side, reporting on APIM is very important. Emit custom metrics from Azure APIM can be used to have your own multi-dimensional metrics, which can let the user know more about the API consumer.
  • Reporting

6. Architecture & Design

Layered API Design in Azure API Management

Azure API Management tips Architecture & Design

7. Connecting in a Secure Way

Use Azure Policy to Enforce HTTPS in Azure API Management

Azure API Management tips Connecting in a Secure Way

8. Access Control

Protect your Azure API Program with Single Azure AD RBAC Policy

  • The best practice is to implement APIM in the central hub, so it could be accessible at different levels in the architecture.
  • A combination of O-auth2 + Subscription key can be used to secure the API in the way.
  • Azure API Management tips Access Control

9. Global Policies and its Scopes

Enforce the Global Policy in Azure API Management

Azure API Management tips Global Policies and its Scopes

10. Security

Password-less last mile security with Azure API Management

  • For better security within azure, using the Managed identity can be helpful.
  • Security

Thus, the session by Toon Vanhoutte deliberately gave vast information about the things that can be done to keep the API and Environment secure and reliable. He shared his thoughts as a best practice to have a dedicative team write the API Policies and whereas other members can be provided with access to view them and use it as per the requirement.

#6: Automated Testing of Logic Apps – (Michael Stephenson)

Michael Stephenson Coach and Consultant of Connected Systems Consulting Limited who is also a freelancer Cloud guy presented on the topic of Automated Testing of Logic Apps.

With great pleasure, Michael gave an introduction on himself and started briefing about Logic App and its Standards, where he said, Automated testing of logic Apps is more about reducing risks and improving agility.

Testing of Logic Apps

Integration of History

He over-viewed the approach of Automated testing of Logic App and explained how automation of logic apps took its place in the market with an example.

Overview Overview

Two ways of Logic App Standards

Integration Playbook

 Test logic Apps when deployed to Azure.

 Advantages

  • Tests the app when it’s deployed like that of the real world.
  • Can be used in the development/build and also in other test environments.

Disadvantages

  • Needs the app deployed to Azure.
  • Can’t mock in the more advanced scenarios.

Microsoft Sample on GitHub

Self-host Logic Apps in Func.exe on the dev machine.

Advantages

  • Can do more complex test scenarios. Eg: mocking

Disadvantages

  • More complicated.
  • Tests take a longer time to run.
  • Only applies to the development and build environments.

The Scenarios with Demo using Visual Studio and Azure DevOps

Scenario 1

Real-world-like test.

Scenario 1

Scenario 2

What if it is not triggered by HTTP.

Scenario 2

Scenario 3

Mocking with the unit test sample.

Scenario 3

Scenario 4

Running tests in pipeline.

Scenario 4

Scenario 5

Living Document.

Scenario 5

Top Tips

Adding to the scenarios, Stephenson gave a few tips and tricks to be followed while in automation.

  • Build testable workflows:
    • Break out loops and conditions when things get complicated
    • Child workflows
    • Separate logic for some triggers.
  • Define your requirements as tests.
  • Do it from Day 1.
  • It’s not about being ‘perfect’ it’s about reducing risks and improving agility.

Eventually, Michael walked through on what’s good and what needs work when it comes to Automation of Logic Apps and shared a piece of enlightened information which had links to ‘How to get started with Automated Testing of Logic Apps’ which was set as the final point of talk for the session.

Testing of Logic Apps

#7: DevOps with Azure Integration Services – (Alessandro Moura)

Alessandro Moura, integration platform lead from Fisher & Paykel who is a first-time speaker in the Integrate event shared his knowledge on DevOps and a demo with Azure Integration Service on how they have deployed on their organization.

DevOps in general

He started the session with the general DevOps like where it can be used and what are the necessary items need to take care of or consider before the development, testing, and monitoring.

Also, he gave a few suggestions on the source control repository followed by the branch strategy that they have used in the development.

Azure Integration Services

Followed by the strategies, Alessandro also mentioned the Specific solution code that they have used to build like,

  • Service Bus – To deploy queues, topics, subscriptions, and filters
  • Key Vault – Shared resources, secrets, and keys during deployment
  • Storage Account – New storage

API Management

He also mentioned the API Management and environment configuration that they have used, since it will take a long time to deploy they are only deploying the policies that were created/changed (he showed during the demo).

He also mentioned the usage of function Apps and Logic Apps for workflow, testing, and monitoring as well.

Monitoring

Then the most awaiting demo was given under the below topics

  • Checking the shared resources previous executions
  • Deploying a new endpoint in API Management
  • Deploying a function app to several environments
  • Azure DevOps

He ended the session with a few interesting takeaways and best practices like,

  • Automate the deployment of everything
  • Use templates to facilitate the developer life
  • Use stages to represent the environments you have

#8: INTEGRATE 2022 – Closing note – (Saravana Kumar)

Saravana greeted and thanked the attendees for staying till the end of the event.

This time at INTEGRATE 2022 we had – 

  • 755 participants
  • 26 Speakers
  • 26 Sessions
  • 8458 Views
  • 4648 Unique Views
  • 1497 Replays

There were several social media posts from participants across the globe.

Attendees and Remote participants are given access to the online portal where they can view the session recording.

The Team

Saravana introduced the Team that worked from India

India Team

INTEGRATE Live Team:

INTEGRATE Live Team

Special Thanks to

Special Thanks to

That’s the wrap of the INTEGRATE 2022 Remote.

At this juncture, we would like to extend my sincere thanks to all the attendees, speakers, partners, and sponsors for supporting us in successfully running the 2022 edition of INTEGRATE.

We hope to count on your support in the future as well.

This blogpost was prepared by:

Amritha
Modhana
Christhini
Devaprakash
Dharshini
Sivaramakrishnan
Nithyapraksh
Pratiksha