Azure Integration in Production with Logic Apps and more
Download as PPTX, PDF4 likes2,167 views
The document outlines the use of Azure Integration, particularly focusing on Logic Apps and its implementations for production systems. It discusses the initial integration requirements between local systems and CRM online, as well as the advantages and disadvantages of using Logic Apps compared to BizTalk Services. Key topics include specific implementations, challenges faced, and future plans for multi-project integrations.
Azure Integration in Production with Logic Apps and more
- 1. Sponsored & Brought to you by Azure Integration in Production with Logic Apps and more Alex Murov & Kelvin van Geene http://www.twitter.com/AlexMurov https://nl.linkedin.com/in/oleksandr-murov-a4a31012 https://nl.linkedin.com/in/kelvinvangeene
- 2. Azure Integration Solution Logic apps and more in Production
- 3. Who are we?
- 4. Who are we?
- 5. Avanade
- 6. What will we share with you today? Azure App Service API Apps Logic App BizTalk Services Cloud Services Service Bus (Queues) AS2 on Azure BizTalk Services vs Logic App Connector
- 7. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 8. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 9. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 10. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 11. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 12. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 13. What will we share with you today? First steps First Production Product Implementation shift Introduction of Logic Apps Specific implementations Lessons learned Future
- 14. How it all started About 2,5 years ago
- 15. How it all started About 2,5 years ago Integration was required between local systems and CRM Online
- 16. How it all started About 2,5 years ago Integration was required between local systems and CRM Online Assumptions: 1. No Custom Development on CRM side 2. SAP-PI will be used as on-premise middleware system 3. AS2 connection must be used to integrate with SAP-PI 4. Costs for development and operations must be kept to the bare minimum
- 17. How it all started About 2,5 years ago Integration was required between local systems and CRM Online Selection fell on Azure BizTalk Services for realizing of PoC
- 18. How it all started About 2,5 years ago Integration was required between local systems and CRM Online Selection fell on Azure BizTalk Services for realizing of PoC so we started building…
- 19. SAP-PI On-premise ERP BI Other LOB System CRM online CRM Online HTTPS connection CRM OrganizationServiceCRM OrganizationService Azure Cloud On-premise CRM Online
- 20. SAP-PI On-premise ERP BI Other LOB System CRM online CRM Online HTTPS connection CRM OrganizationServiceCRM OrganizationService Azure Cloud On-premise CRM Online AS2 Agreement BizTalk Services
- 22. BizTalk Services SAP-PI On-premise ERP BI Other LOB System CRM online XML message CRM Online HTTPS connection CRM OrganizationServiceCRM OrganizationService Azure Cloud On-premise CRM Online Service Bus (Queue’s) AS2 Agreement BizTalk Services Service Bus (Queue’s)
- 26. BizTalk Services SAP-PI On-premise ERP BI Other LOB System XML message CRM online XML message CRM Online HTTPS connection CRM OrganizationServiceCRM OrganizationService Azure Cloud On-premise CRM Online Service Bus (Queue’s) XML message AS2 Agreement BizTalk Services Cloud Services Service Bus (Queue’s)
- 31. X
- 32. Logic App
- 33. Logic Apps
- 34. Design simple but effective workflow with ease What are Logic Apps?
- 35. Design simple but effective workflow with ease Initiates based on a Trigger on which Actions are taken What are Logic Apps?
- 36. Design simple but effective workflow with ease Initiates based on a Trigger on which Actions are taken Extensible with Custom API Apps What are Logic Apps?
- 37. Why start with Logic Apps? Simplicity / Flexibility
- 38. Why start with Logic Apps? Simplicity / Flexibility Most common adapters are already available
- 39. Why start with Logic Apps? Simplicity / Flexibility Most common adapters are already available Azure BizTalk Services deprecation
- 40. Advantages over Cloud Services Cost efficient
- 41. Advantages over Cloud Services Cost efficient Quick to deploy Start and Stop almost instantly
- 42. Advantages over Cloud Services Cost efficient Quick to deploy Start and Stop almost instantly Reusability of components
- 43. Advantages over Cloud Services Cost efficient Quick to deploy Start and Stop almost instantly Reusability of components Operations Monitoring in portal UI
- 44. Disadvantages of Logic Apps Not easy to retrieve information if something goes wrong Formatting of data in web viewer
- 45. Disadvantages of Logic Apps Not easy to retrieve information if something goes wrong Formatting of data in web viewer Simple Visual Studio integration (V1, V2 is better) Settings / Configuration management
- 46. Disadvantages of Logic Apps Not easy to retrieve information if something goes wrong Formatting of data in web viewer Simple Visual Studio integration (V1, V2 is better) Settings / Configuration management Still in preview, regular changes
- 48. Master data flowMaster data flow Logic App
- 51. Big Data (volume data) Amount of data involved Process flow Why not use logic apps Long running processes Timeouts on SQL VolumeDataReportFlow Data Warehouse Web App – 1xPer OpCo WebJob – Process Accounts WebJob – Upsert Account Service Bus Queue – New Account Notification Message Storage blob – New Account Object DocumentDB – 1x Account per Staging/ Production 1x Collection Per OpCo SQL database – Staging / Production SSIS Web App – API App Windows App
- 52. Sales Orders
- 53. Sales Orders
- 54. Sales Orders Windows app App Back-end (CRM Online) Azure Service Bus queue Azure Logic App SAP-PI ( on-premise integration platform) OpCo FTP location Azure Cloud on- premise E-mail to the disctibutor OpCo FTP location OpCo FTP location
- 56. Message Validation ApptoAzuretoSAP-PIApptoAzuretoSAP-PI SimpleOrderCapturing InterfacingMasterDatafromApptoSAP-PIInterfacingMasterDatafromApptoSAP-PI InterfacingOrderstoon-premiseLOBsystems New Account In App back-end (CRM Online) Send to SAP-PI Update Account In App back-end (CRM Online) Send to SAP-PI Account Create message is send to Azure via Azure aware plugin Service endpoint configuration Does the message for account create contains hsem_externalid Yes Ignore No Any OpCo specific business rules? Yes Process OpCo business requerments No Need to be encoded as base64 string? For character specific issues in SAP-PI No Yes Encode to base64 string Need to be encoded as base64 string? For character specific issues in SAP-PI Encode to base64 string Yes No Is validation On for this Message Type and this OpCo No Yes Validate and Send Results to SQL Azure Database Is validation On for this Message Type and this OpCo Validate and Send Results to SQL Azure Database Yes No New Orders In App back-end (CRM Online) Send To SAP-PI Check if Order Headers have Status Confirmed Yes No Get complete orders, their order- lines and distributors from CRM. Send orders in one xml batch file to SAP-PI system Is the distributor E-mail only reachable? Filter out all orders for E-mail only and e-mail them to their specified addresses Yes No Is validation On for this Message Type and this OpCo Validate and Send Results to SQL Azure Database No Yes
- 57. Future
- 58. Multi project Integration SeparationMulti project Integration Separation
- 59. Multi project Integration SeparationMulti project Integration Separation
- 60. Multi project Integration SeparationMulti project Integration Separation
- 61. Multi project Integration SeparationMulti project Integration Separation • Different types of integration • Multiple development and operation teams • Different contracts
- 62. Full Logic App Implementation
- 63. Full Logic App Implementation
Editor's Notes
- #59: Client is scaling up with multiple types Azure/Integration projects, done by multiple external parties Different types of contracts Only 1 PI endpoint
- #60: Client is scaling up with multiple types Azure/Integration projects, done by multiple external parties Different types of contracts Only 1 PI endpoint
- #61: Client is scaling up with multiple types Azure/Integration projects, done by multiple external parties Different types of contracts Only 1 PI endpoint