This document summarizes a presentation given by Félix Mondelo, an Integration Solution's Architect at Kabel, at the 2017 IBM Madrid conference. The presentation covered the evolution of integration from on-premises to cloud-based approaches using Infrastructure as a Service (IaaS), Platform as a Service (PaaS), and serverless computing. It discussed how Logic Apps can be used for serverless integration and orchestration of workflows. It also provided an overview of how the Enterprise Integration Pack in Azure can be used to implement enterprise integration patterns like B2B using standards like AS2 and EDI. The presentation concluded with a demo of using Logic Apps along with an Integration Account to receive an XML order request

1. 2017 - Madrid
Logic Apps, the power
of new Integration
Félix Mondelo
Integration Solution’s Architect, Kabel

2. Who am I?
Félix Mondelo
Integration Solution’s Architect, Kabel
(34) 696 48 67 39
FMondelo@kabel.es
http://felixmondelo.blogspot.com
https://twitter.com/felixmondelo
https://www.linkedin.com/in/felixmondelo

3. Agenda

4. #GIBMad2017

5. Evolution of the Cloud
Pre-Cloud Number of servers
OS to install
Periodicity to patch the server
Size of the servers to buy Plan to backup the server
Deploy new code
Time to provision a new server
The location of the servers is secure?
What happens if the power goes out?
Right size of the servers to my business
Who has physical access to the servers?
Media to keep backup
Type of storage
Scale the application
Plan to hardware failure
Dynamically configure the application
Who monitors the servers
Application monitoring

6. Evolution of the Cloud
Pre-CloudIaaS Number of servers
OS to install
Periodicity to patch the server
Size of the servers to buy Plan to backup the server
Deploy new code
Time to provision a new server
The location of the servers is secure?
What happens if the power goes out?
Right size of the servers to my business
Who has physical access to the servers?
Media to keep backup
Type of storage
Scale the application
Plan to hardware failure
Dynamically configure the application
Who monitors the servers
Application monitoring

7. Evolution of the Cloud
Pre-CloudPaaS Number of servers
OS to install
Periodicity to patch the server
Plan to backup the server
Deploy new code
Right size of the servers to my business
Scale the application
Dynamically configure the application
Application monitoring

8. Evolution of the Cloud
Pre-CloudServerless Number of servers
Scale the application
Right size of the servers to my business

9. What is Serverless and their Benefits
Pay per excution
• Consumption Billing
• Users are only charged for runtime and resources that the function consumes.
• There is no longer any concept of under or over provisioning
Ease of scale
• If the load on the function grows, the infrastructure will create copies of the function
and scale to meet demand
• It will scale as long as you can pay for it
Do less Manage less
• Servers are fully-abstracted
• No more do you need to set up a server or procure one
• Not require fixed infrastructure to be pre-provisioned in order for it to be used

10. Logic Apps and Serverless
Pay per Action
• e.g. If you set up a Logic App to poll for data once every minute over the course of 10
days, that App would generate 14,400 billable actions
• e.g. If that same Logic App also included 500 workflow steps per day as part of the daily
polling, the Logic App would generate an additional 5,000 billable actions
Don’t worry about resources
• Think about billable actions
Don’t worry Virtual Machines, PaaS VMs, …
• Not require infrastructure to be provisioned
Don’t worry about the platform
• Focus on code, deployment and managing the app

11. #GIBMad2017

12. Microsoft Azure iPaaS

13. Logic Apps and Integration
Implement and orchestrate visually designed integration workflows
• Azure Portal or Visual Studio
• Azure SDK + Azure Logic Apps Visual Studio Tools
Orchestrate distributed microservices
• Rich ways to process and manipulate data than can be obtained or pushed via
different connectors
• Expose your integrations as microservices
B2B Integrations with AS2 and EDI
• Enterprise Integration Pack (EIP)
100+ Connectors
• Protocols, Hybrid, SaaS, …

14. Logic Apps and Integration (Connectors)
SaaS

15. Logic Apps and Integration (Connectors)
Protocols / Native Hybrid Azure Services and Power Apps Connectors
B2B? AS2? EDI? XML?

16. #GIBMad2017

17. Enterprise Integration Pack - Intro
Microsoft’s cloud-based solution to enable Enterprise Integration Scenarios
• B2B workflows
• Industry standard protocols: AS2, X12, EDIFACT.
• Flat Files and XML
• Secure messages with encryption and digital signatures.
Based on Integration Accounts
• Cloud-based containers that store all our artifacts: schemas, partners, certificates,
maps and agreements.
Different artifacts
• Schemas
• Maps
• Agreements
• Partners
• Certificates

18. Enterprise Integration Pack - Connectors
XML Validation
XML Transform
Flat file encoding
Flat file decoding
AS2 decoding
AS2 encoding
X12 decoding
X12 encoding
EDIFACT decoding
EDIFACT encoding

19. Enterprise Integration Pack – Get Started
Create and
Integration
Account in
the Azure
Portal
Add Partners,
Schemas,
Certificates,
Maps and
Agreements
Create a
Logic App
Link the Logic
App to the
Integration
Account
Use the
artifacts
stored in the
Integration
Account in
your Logic
App
What you need
• An Azure subscription
• An Integration Account
• Visual Studio 2015, to create maps and schemas (you can reuse maps and schemas of your BizTalk
Solutions)
• Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0

20. Enterprise Integration Pack – Step by Step
Create an Integration Account on Azure Portal

21. Enterprise Integration Pack – Step by Step
Add Partners, Schemas, Maps, Certificates and Agreements

22. Enterprise Integration Pack – Step by Step
Create a Logic App

23. Enterprise Integration Pack – Step by Step
Link the Logic App to the Integration Account

24. Enterprise Integration Pack – Step by Step
Use the artifacts stored in the Integration Account in your Logic App

25. #GIBMad2017

26. BizTalk Architecture
Orchestration
Subscribe
Receive Port
Receive
Location(s)
Receive Pipeline
Map(s)
Publish
Adapter
Send Port
Send Pipeline
Subscribe
Map(s)
Tracking
BizTalkDTADb
Configuration
BizTalkMgmtDb
MessageBox
(BizTalkMsgBoxDb)
Publish
Adapter

27. BizTalk to Azure iPaaS
Adapters
• Description: “An adapter is a software component that enables you to easily send
messages out of or receive messages into BizTalk Server with a delivery mechanism that
conforms to a commonly recognized standard, such as SMTP, POP3, FTP, or Microsoft
Message Queuing (MSMQ). As Microsoft BizTalk Server has evolved, the need for
adapters that quickly enable connectivity with commonly used applications and
technologies has increased”
Connectors
• Standard connectors
e.g. IBM DB2, SQL Server, OneDrive, Twitter, …
• Custom API Apps within the Logic App
https://blog.geist.no/custom-connectors-taking-azure-logic-and-api-apps-for-a-spin-
part-2/

28. BizTalk to Azure iPaaS
Pipelines
• Description: “Pipelines are a component of Microsoft BizTalk Server that provides an
implementation of the Pipes and Filters integration pattern. During the receiving and
sending of messages, there are business reasons to perform transformations on
messages to prepare them to enter or leave BizTalk Server.”
Logic Apps
• Building a simple Logic App that implements Pipes and Filters pattern like pipelines

29. BizTalk to Azure iPaaS
Pipeline Components
• Description: “A general pipeline component takes a single message, performs some
processing, and emits zero or more messages. If it does not produce any message
output, it is called a consuming component.”
Connectors
• Standard connectors
e.g. Parse JSON, XML Validation, Flat File decoding, AS2 encoding, …
• Custom API Apps within the Logic App

30. BizTalk to Azure iPaaS
Orchestration
• Description: “An orchestration is a flexible, powerful tool for representing an executable
business”
Logic Apps
• Building a complex Logic App that implements a business process.

31. BizTalk to Azure iPaaS
Publish / Subscribe
• The model implemented in BizTalk Server is often called content-based publish/subscribe

32. iPaaS Architecture

33. #GIBMad2017
Logic Apps with Enterprise Integration Pack

34. Demo Scenario
IntegrationAccountfor schemas and maps
Add ContactInsightly
Receive XML
(CreateOrderRequest)
Azure Service Bus
(queueneworders) Logic App
Azure Service Bus
(queueneworder_json)
Send JSON orders
Invalid XML Request

35. Microsoft Ignite#GIBMad2017
Thanks!