The purpose of the demo is to show the function and advantage of the Azure Logic APP. Please note that it is not the final solution. the project solution will be designed after the requirement research and analysis.

Azure Logic App Instroduction

Azure Logic Apps is a cloud-based platform for creating and running automated workflows that integrate your apps, data, services, and systems. With this platform, you can quickly develop highly scalable integration solutions for your enterprise and business-to-business (B2B) scenarios. As a member of Azure Integration Services, Logic Apps simplifies the way that you connect legacy, modern, and cutting-edge systems across cloud, on premises, and hybrid environments.

Azure Logic App Architecture

Key Terms

1. Logic app: The Azure resource to create when you want to develop a workflow. Based on your scenario's needs and solution's requirements.
2. Workflow: A series of steps that defines a task or process, starting with a single trigger and followed by one or multiple actions.
3. Trigger: The first step that starts every workflow and specifies the condition to meet before running any actions in the workflow. For example, a trigger event might be getting an email in your inbox or detecting a new file in a storage account.
4. Action: Each subsequent step that follows after the trigger and runs some operation in a workflow.
5. Built-in trigger or action: A natively running Logic Apps operation that provides a way to control your workflow's schedule or structure, run your own code, manage or manipulate data, or complete other tasks in your workflow.
6. Managed connector: A prebuilt proxy or wrapper around a REST API that provides prebuilt triggers and actions for your workflow to access a specific app, data, service, or system. Before you can use most managed connectors, you must first create a connection from your workflow and authenticate your identity.
7. Integration account: The Azure resource to create when you want to define and store B2B artifacts for use in your workflows. After you link this account to your logic app, your workflows can use these B2B artifacts and exchange messages that comply with Electronic Data Interchange (EDI) and Enterprise Application Integration (EAI) standards.

How logic apps work

In a logic app, each workflow always starts with a single trigger. A trigger fires when a condition is met, for example, when a specific event happens or when data meets specific criteria. Many triggers include scheduling capabilities that control how often your workflow runs. Following the trigger, one or more actions run operations that, for example, process, handle, or convert data that travels through the workflow, or that advance the workflow to the next step.

Use case demos

1. Create TPA (via SFTP or AS2 – explain what is needed to establish connection with TP)
   a. Partner Profiles:
   • Partner Name
   • Qualifier & Value
   • Certificates
   • Endpoint Address
   b. Setup a partner, The partner can support EDIFACT, X12 or RosettaNet Solution.
   

c. Add a new Agreement

d. Edit receive setting

2. Show mapping tool (plus how to make batching), Mapping in the Visual studio or other XSLT tools
   

3. Workflow (build some simple transaction flow for instance to read EDI file, send ACK and transform data to XML)
   a.RosettaNet
   

b.EDI
c.EDI Batching

Data monitoring (dashboard),Data searching (by ICN, PO#, invoice# etc.), Are there any reports for certificate , events, TP ...?

Troubleshooting of issues

Is there any secure mechanism for this cloud solution. Who will help to manage and protect our Biztalk sever.

I want to know if we face some special Biztalk server issue or service issue. How to find solution for it.

Since it is cloud solution, Do we need to have any setup at cloud side to connect to our internal network?

Solution A:

Solutio B: