Book Image

Enterprise Integration with Azure Logic Apps

By : Matthew Bennett
Book Image

Enterprise Integration with Azure Logic Apps

By: Matthew Bennett

Overview of this book

Logic Apps are a visual flowchart-like representation of common programming actions, and are a flexible way to create logic without writing a single line of code. Enterprise Integration with Azure Logic Apps is a comprehensive introduction for anyone new to Logic Apps which will boost your learning skills and allow you to create rich, complex, structured, and reusable logic with instant results. You'll begin by discovering how to navigate the Azure portal and understand how your objects can be zoned to a specific environment by using resource groups. Complete with hands-on tutorials, projects, and self-assessment questions, this easy-to-follow guide will teach you the benefits and foundations of Logic App logic design. As you advance, you'll find out how to manage your Azure environment in relation to Logic Apps and how to create elegant and reliable Logic Apps. With useful and practical explanations of how to get the most out of Logic App actions and triggers, you'll be able to ensure that your Logic Apps work efficiently and provide seamless integration for real-world scenarios without having to write code. By the end of this Logic Apps book, you'll be able to create complex and powerful Logic Apps within minutes, integrating large amounts of data on demand, enhancing your systems, and linking applications to improve user experience.
Table of Contents (17 chapters)
1
Section 1: Logic App Fundamentals
7
Section 2: Logic App Design
13
Section 3: Logic App Maintenance and Management

Using a logic app action to call a child logic app

As your logic develops, you might notice that certain sections need to be called multiple times, or that they might need to be called by several logic apps that are similar. The term orchestrator refers to a logic app that will take a trigger action and, depending on what logic is required, route the data message to the appropriate child logic app for the message to be dealt with correctly and for the correct fields to be populated.

Let's look at a real-life example. I am taking data from an old, closed system that does not contain any Web APIs (web-based RESTful web programming interfaces) that can be used to send data or a direct link that will allow me to obtain data in Azure. I do some Read APIs that allow me to obtain data, but not the other way around. By writing a C# app that will query the closed system's audit logs, I might not be able to get to the actual data, but I can understand which action has just taken...