You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-enterprise-integration-overview.md
+18-29Lines changed: 18 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,58 +14,47 @@ ms.date: 08/01/2019
14
14
15
15
# Enterprise integration solutions with Azure Logic Apps and Enterprise Integration Pack
16
16
17
-
For business-to-business (B2B) workflows and seamless communication with Azure Logic Apps, you can enable enterprise integration scenarios with Microsoft's cloud-based solution, the Enterprise Integration Pack. Organizations can exchange messages electronically, even if they use different protocols and formats. The pack transforms different formats into a format that organizations' systems can interpret and process. Organizations can exchange messages through industry-standard protocols, including [AS2](../logic-apps/logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](../logic-apps/logic-apps-enterprise-integration-edifact.md). You can also secure messages with both encryption and digital signatures.
17
+
For business-to-business (B2B) solutions and seamless communication between organizations, you can build automated scalable enterprise integration workflows by using the Enterprise Integration Pack (EIP) with [Azure Logic Apps](../logic-apps/logic-apps-overview.md). Although organizations use different protocols and formats, they can exchange messages electronically. The EIP transforms different formats into a format that your organizations' systems can process and supports industry-standard protocols, including [AS2](../logic-apps/logic-apps-enterprise-integration-as2.md), [X12](logic-apps-enterprise-integration-x12.md), and [EDIFACT](../logic-apps/logic-apps-enterprise-integration-edifact.md). You can also secure messages with both encryption and digital signatures. The EIP supports these [enterprise integration connectors](../connectors/apis-list.md#integration-account-connectors) and these industry standards:
18
18
19
-
If you are familiar with BizTalk Server or Microsoft Azure BizTalk Services,
20
-
the Enterprise Integration features are easy to use because most concepts are similar. One major difference is that Enterprise Integration uses integration accounts to simplify the storage and management of artifacts used in B2B communications.
19
+
* Electronic Data Interchange (EDI)
20
+
* Enterprise Application Integration (EAI)
21
21
22
-
Architecturally, the Enterprise Integration Pack is based on "integration accounts". These accounts are cloud-based containers that store all your artifacts, like schemas, partners, certificates, maps, and agreements. You can use these artifacts to design, deploy, and maintain your B2B apps and also to build B2B workflows for logic apps. But before you can use these artifacts, you must first link your integration account to your logic app. After that, your logic app can access your integration account's artifacts.
22
+
If you're familiar with Microsoft BizTalk Server or Azure BizTalk Services, the EIP follows similar concepts, making the features easty to use. However, one major difference is that the EIP is architecturally based on "integration accounts" to simplify the storage and management of artifacts used in B2B communications. These accounts are cloud-based containers that store all your artifacts, such as partners, agreements, schemas, maps, and certificates.
23
23
24
-
## Why should you use enterprise integration?
24
+
## Why use the Enterprise Integration Pack?
25
25
26
-
* With enterprise integration, you can store all your artifacts in one place - your integration account.
26
+
* With the EIP, you can store all your artifacts in one place - your integration account.
27
27
28
28
* You can build B2B workflows and integrate with third-party software-as-service (SaaS) apps, on-premises apps, and custom apps
29
-
by using the Azure Logic Apps engine and all its connectors.
29
+
by using Azure Logic Apps and connectors.
30
30
31
31
* You can create custom code for your logic apps with Azure functions.
32
32
33
-
## How to get started with enterprise integration?
33
+
## How do I get started?
34
34
35
-
You can build and manage B2B apps with the
36
-
Enterprise Integration Pack by using the Logic App Designer
37
-
in the Azure portal. You can also manage your logic apps with Visual Studio and [PowerShell](https://docs.microsoft.com/powershell/module/az.logicapp).
35
+
Before you can start building B2B logic app workflows with the EIP, you need these items:
38
36
39
-
Here are the high-level steps you must take before you can create apps in the Azure portal:
* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
44
38
45
-
Enterprise Integration supports these industry standards:
39
+
* An [integration account](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md) with the artifacts that you want to use
46
40
47
-
* EDI - Electronic Data Interchange
48
-
* EAI - Enterprise Application Integration
41
+
* To create maps and schemas, you can use the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0](https://aka.ms/vsmapsandschemas) and Visual Studio 2015.
49
42
50
-
## Get started
43
+
After you create an integration account and add your artifacts, you can get started with building B2B logic app workflows that interact with these artifacts by creating a logic app in the Azure portal. To use these artifacts, make sure that you first link your integration account to your logic app. After that, your logic app can access your integration account's artifacts. You can also create, manage, and deploy logic apps by using Visual Studio or [PowerShell](https://docs.microsoft.com/powershell/module/az.logicapp).
51
44
52
-
* An Azure subscription. If you don't have an Azure subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/).
53
-
* An [integration account](../logic-apps/logic-apps-enterprise-integration-create-integration-account.md)
45
+
Here are the high-level steps that you must complete before you can create logic apps:
54
46
55
-
To create maps and schemas, you can use the [Microsoft Azure Logic Apps Enterprise Integration Tools for Visual Studio 2015 2.0](https://aka.ms/vsmapsandschemas) and Visual Studio 2015.
47
+
56
48
57
-
## Try it now
49
+
## Try now
58
50
59
51
[Deploy a fully operational sample AS2 send & receive logic app](https://github.com/Azure/azure-quickstart-templates/tree/master/201-logic-app-as2-send-receive) that uses the B2B features for Azure Logic Apps.
0 commit comments