diff --git a/guides/m2devgde/v1.0.0.0/integration/integration-auth.md b/guides/m2devgde/v1.0.0.0/integration/integration-auth.md index 356fadff009..34cdf9fc860 100644 --- a/guides/m2devgde/v1.0.0.0/integration/integration-auth.md +++ b/guides/m2devgde/v1.0.0.0/integration/integration-auth.md @@ -5,7 +5,7 @@ title: Understanding Integration Authorization

Understanding Integration Authorization

-

Help us improve this page 

+

Help us improve this page 

There are two ways to authenticate the third-party system with Magento: diff --git a/guides/m2devgde/v1.0.0.0/integration/integration-code.md b/guides/m2devgde/v1.0.0.0/integration/integration-code.md index 96643be3566..c917942fec3 100644 --- a/guides/m2devgde/v1.0.0.0/integration/integration-code.md +++ b/guides/m2devgde/v1.0.0.0/integration/integration-code.md @@ -5,7 +5,7 @@ title: Coding Your Integration

Coding Your Integration

-

Help us improve this page 

+

Help us improve this page 

This topic discusses how to code your integration with Magento. Eventually, you will be able to market your integration as an extension on Magento Connect; however, it's not possible to do that now for Magento 2 integrations. diff --git a/guides/m2devgde/v1.0.0.0/integration/integration-create-man.md b/guides/m2devgde/v1.0.0.0/integration/integration-create-man.md index fa7e7f3a353..d34fe486a78 100644 --- a/guides/m2devgde/v1.0.0.0/integration/integration-create-man.md +++ b/guides/m2devgde/v1.0.0.0/integration/integration-create-man.md @@ -5,7 +5,7 @@ title: Manually Creating an Integration Using the Magento Admin

Manually Creating an Integration Using the Magento Admin

-

Help us improve this page 

+

Help us improve this page 

Creating a new integration manually implies that the administrative user previously contacted the third-party system's developers and got all necessary information. @@ -17,13 +17,13 @@ To create a new integration: The Integrations page displays, as shown in the following figure. - ![Click **System** > **Integrations** to start]({{ site.baseurl }}/common/images/integration.png) + ![Click **System** > **Integrations** to start]({{ site.baseurl }}common/images/integration.png) -3. Click ![Click the plus icon to add an integration]({{ site.baseurl }}/common/images/integration_plus.png). +3. Click ![Click the plus icon to add an integration]({{ site.baseurl }}common/images/integration_plus.png). The New Integration page displays as shown in the following figure. - ![Integration information consists of a unique name, optional e-mail address, and identity information]({{ site.baseurl }}/common/images/integration_new_info.png) + ![Integration information consists of a unique name, optional e-mail address, and identity information]({{ site.baseurl }}common/images/integration_new_info.png) 4. Enter the following information: @@ -61,7 +61,7 @@ To create a new integration: The API tab page displays as the following figure shows. - ![Select which resources to grant on the API tab page]({{ site.baseurl }}/common/images/integration_roleResources.png) + ![Select which resources to grant on the API tab page]({{ site.baseurl }}common/images/integration_roleResources.png) Defining the access to right resources for the third-party systems is critical for effective and secure work of your online store. There are two ways of how you can limit the access to your store for the third-party systems or some user roles: diff --git a/guides/m2devgde/v1.0.0.0/integration/integration-maintain.md b/guides/m2devgde/v1.0.0.0/integration/integration-maintain.md index cd7dc689577..734fb814a68 100644 --- a/guides/m2devgde/v1.0.0.0/integration/integration-maintain.md +++ b/guides/m2devgde/v1.0.0.0/integration/integration-maintain.md @@ -5,7 +5,7 @@ title: Maintaining an Integration

Maintaining an Integration

-

Help us improve this page 

+

Help us improve this page 

Only integrations created manually using the Magento Admin can be edited; integrations created automatically from configuration files are not editable. @@ -15,8 +15,8 @@ To edit or delete an integration: 2. Click **System** > **Integrations**. -3. To edit the integration, click ![Click the pencil icon to edit an integration]({{ site.baseurl }}/common/images/integration_pencil.png) next to the integration to edit. +3. To edit the integration, click ![Click the pencil icon to edit an integration]({{ site.baseurl }}common/images/integration_pencil.png) next to the integration to edit. -4. To delete the integration, click ![Click the trash can icon to delete an integration]({{ site.baseurl }}/common/images/integration_trash.png). +4. To delete the integration, click ![Click the trash can icon to delete an integration]({{ site.baseurl }}common/images/integration_trash.png). 5. Save your changes. \ No newline at end of file diff --git a/guides/m2devgde/v1.0.0.0/integration/what-is-integration.md b/guides/m2devgde/v1.0.0.0/integration/what-is-integration.md index 606820e64e0..89952a89905 100644 --- a/guides/m2devgde/v1.0.0.0/integration/what-is-integration.md +++ b/guides/m2devgde/v1.0.0.0/integration/what-is-integration.md @@ -5,7 +5,7 @@ title: What is an Integration?

What is an Integration?

-

Help us improve this page 

+

Help us improve this page 

All third-party systems integrating with Magento must be authenticated and authorized to access Magento resources securely. To make both procedures easier, we changed the workflow for authorizing the API calls. You can now authorize your third-party system using either secure, cloud-based key exchange or by creating the keys locally on the merchant's Magento system. diff --git a/guides/m2devgde/v1.0.0.0/svcs-framework/build-svc.md b/guides/m2devgde/v1.0.0.0/svcs-framework/build-svc.md index 3674c2ba632..4b10b6cfcf1 100644 --- a/guides/m2devgde/v1.0.0.0/svcs-framework/build-svc.md +++ b/guides/m2devgde/v1.0.0.0/svcs-framework/build-svc.md @@ -5,7 +5,7 @@ title: Basics of Building a Service # Basics of Building a Service -

Help us improve this page 

+

Help us improve this page 

A _service_ is basically a contract between code that uses the service and an integration that implements the service. The service itself is PHP code—typically one or more interfaces, classes, and methods. To review the properties of a service, see Understanding the Properties and Responsibilities of a Service. diff --git a/guides/m2devgde/v1.0.0.0/svcs-framework/svc-how-to-use.md b/guides/m2devgde/v1.0.0.0/svcs-framework/svc-how-to-use.md index 60d72d704f6..cddcb8c794a 100644 --- a/guides/m2devgde/v1.0.0.0/svcs-framework/svc-how-to-use.md +++ b/guides/m2devgde/v1.0.0.0/svcs-framework/svc-how-to-use.md @@ -5,7 +5,7 @@ title: How a Client Uses a Service

How a Client Uses a Service

-

Help us improve this page 

+

Help us improve this page 

Before interacting with a service, you must be familiar with the service interface, including input/output data structures defined by the corresponding schema. Services are defined by PHP interfaces, so developers can simply acquire an instance of the service and invoke the appropriate method directly. You can also access services using REST and SOAP calls.