Merge pull request #190197 from dlepow/wsdl

[APIM] WSDL dependencies

Author: GitHubber17

articles/api-management/api-management-api-import-restrictions.md

@@ -5,24 +5,19 @@ description: Details of known issues and restrictions on Open API, WSDL, and WAD
 services: api-management
 documentationcenter: ''
 author: dlepow
-manager: vlvinogr
-editor: ''
 
-ms.assetid: 7a5a63f0-3e72-49d3-a28c-1bb23ab495e2
 ms.service: api-management
-ms.workload: mobile
-ms.tgt_pltfrm: na
-ms.topic: article
-ms.date: 10/26/2021
+ms.topic: conceptual
+ms.date: 03/02/2022
 ms.author: danlep
 ---
 
 # API import restrictions and known issues
 
 When importing an API, you might encounter some restrictions or need to identify and rectify issues before you can successfully import. In this article, you'll learn:
 * API Management's behavior during OpenAPI import. 
-* Import limitations, organized by the import format of the API. 
-* How OpenAPI export works.
+* OpenAPI import limitations and how OpenAPI export works.
+* Requirements and limitations for WSDL and WADL import.
 
 ## API Management during OpenAPI import
 
@@ -181,14 +176,16 @@ For each operation, its:
 
 ## <a name="wsdl"> </a>WSDL
 
-You can create SOAP pass-through and SOAP-to-REST APIs with WSDL files.
+You can create [SOAP pass-through](import-soap-api.md) and [SOAP-to-REST](restify-soap-api.md) APIs with WSDL files.
 
 ### SOAP bindings 
 - Only SOAP bindings of "document" and “literal” encoding style are supported.
 - No support for “rpc” style or SOAP-Encoding.
 
-### WSDL:Import
-Not supported. Instead, merge the imports into one document.
+### Unsupported directives
+`wsdl:import`, `xsd:import`, and `xsd:include` aren't supported. Instead, merge the dependencies into one document. 
+
+For an open-source tool to resolve and merge `wsdl:import`, `xsd:import`, and `xsd:include` dependencies in a WSDL file, see this [GitHub repo](https://github.com/Azure-Samples/api-management-schema-import).
 
 ### Messages with multiple parts 
 This message type is not supported.

articles/api-management/import-soap-api.md

@@ -1,66 +1,60 @@
 ---
-title: Import SOAP API using the Azure portal | Microsoft Docs
-description: Learn how to import a standard XML representation of a SOAP API, and then test the API in the Azure and Developer portals.
+title: Import SOAP API to Azure API Management using the portal | Microsoft Docs
+description: Learn how to import a SOAP API to Azure API Management as a WSDL specification. Then, test the API in the Azure portal.
 author: dlepow
 ms.service: api-management
 ms.topic: how-to
-ms.date: 02/10/2022
+ms.date: 03/01/2022
 ms.author: danlep
 
 ---
-# Import SOAP API
+# Import SOAP API to API Management
 
-This article shows how to import a standard XML representation of a SOAP API. The article also shows how to test the API Management API.
+This article shows how to import a WSDL specification, which is a standard XML representation of a SOAP API. The article also shows how to test the API in API Management.
 
 In this article, you learn how to:
 
 > [!div class="checklist"]
-> * Import SOAP API
+> * Import a SOAP API
 > * Test the API in the Azure portal
 
+[!INCLUDE [api-management-wsdl-import](../../includes/api-management-wsdl-import.md)]
+
 ## Prerequisites
 
 Complete the following quickstart: [Create an Azure API Management instance](get-started-create-service-instance.md)
 
 [!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-navigate-to-instance.md)]
 
-## <a name="create-api"> </a>Import and publish a back-end API
-
-1. Navigate to your API Management service in the Azure portal and select **APIs** from the menu.
-2. Select **WSDL** from the **Add a new API** list.
-
-    ![Soap api](./media/import-soap-api/wsdl-api.png)
-3. In the **WSDL specification**, enter the URL to where your SOAP API resides.
-4. The **SOAP pass-through** radio button is selected by default. With this selection, the API is going to be exposed as SOAP. Consumer has to use SOAP rules. If you want to "restify" the API, follow the steps in [Import a SOAP API and convert it to REST](restify-soap-api.md).
-
-    ![Screenshot shows the Create from W S D L dialog box where you can enter a W S D L specification.](./media/import-soap-api/pass-through.png)
-5. Press tab.
+## <a name="create-api"> </a>Import and publish a backend API
 
-    The following fields get filled up with the info from the SOAP API: Display name, Name, Description.
-6. Add an API URL suffix. The suffix is a name that identifies this specific API in this API Management instance. It has to be unique in this API Management instance.
-7. Publish the API by associating the API with a product. In this case, the "*Unlimited*" product is used.  If you want for the API to be published and be available to developers, add it to a product. You can do it during API creation or set it later.
+1. From the left menu, under the **APIs** section, select **APIs** > **+ Add API**.
+1. Under **Create from definition**, select **WSDL**.
 
-    Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. Developers must first subscribe to a product to get access to the API. When they subscribe, they get a subscription key that is good for any API in that product. If you created the API Management instance, you are an administrator already, so you are subscribed to every product by default.
+    ![SOAP API](./media/import-soap-api/wsdl-api.png)
+1. In **WSDL specification**, enter the URL to your SOAP API, or click **Select a file** to select a local WSDL file.
+1. In **Import method**, **SOAP pass-through** is selected by default. 
+    With this selection, the API is exposed as SOAP, and API consumers have to use SOAP rules. If you want to "restify" the API, follow the steps in [Import a SOAP API and convert it to REST](restify-soap-api.md).
 
-    By default, each API Management instance comes with two sample products:
+    ![Create SOAP API from WDL specification](./media/import-soap-api/pass-through.png)
+1. The following fields are filled automatically with information from the SOAP API: **Display name**, **Name**, **Description**.
+1. Enter other API settings. You can set the values during creation or configure them later by going to the **Settings** tab. 
 
-    * **Starter**
-    * **Unlimited**   
-8. Enter other API settings. You can set the values during creation or configure them later by going to the **Settings** tab. The settings are explained in the [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
-9. Select **Create**.
+    For more information about API settings, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
+1. Select **Create**.
 
 ### Test the new API in the portal
 
-Operations can be called directly from the administrative portal, which provides a convenient way to view and test the operations of an API.  
+Operations can be called directly from the portal, which provides a convenient way to view and test the operations of an API.  
 
 1. Select the API you created in the previous step.
 2. Press the **Test** tab.
 3. Select some operation.
 
-    The page displays fields for query parameters and fields for the headers. One of the headers is "Ocp-Apim-Subscription-Key", for the subscription key of the product that is associated with this API. If you created the API Management instance, you are an administrator already, so the key is filled in automatically. 
+    The page displays fields for query parameters and fields for the headers. One of the headers is **Ocp-Apim-Subscription-Key**, for the subscription key of the product that is associated with this API. If you created the API Management instance, you're an administrator already, so the key is filled in automatically. 
 1. Press **Send**.
 
-    Backend responds with **200 OK** and some data.
+    When the test is successful, the backend responds with **200 OK** and some data.
 
 ## Wildcard SOAP action
 

articles/api-management/restify-soap-api.md

@@ -1,30 +1,26 @@
 ---
-title: Import a SOAP API and convert to REST using the Azure portal | Microsoft Docs
-description: Learn how to import a SOAP API, convert it to REST with API Management, and then test the API in the Azure and Developer portals.
+title: Import SOAP API to Azure API Management and convert to REST using the portal | Microsoft Docs
+description: Learn how to import a SOAP API to Azure API Management as a WSDL specification and convert it to a REST API. Then, test the API in the Azure portal.
 services: api-management
-documentationcenter: ''
 author: dlepow
-manager: cfowler
-editor: ''
 
 ms.service: api-management
-ms.workload: mobile
-ms.tgt_pltfrm: na
-ms.topic: tutorial
-ms.date: 11/22/2017
+ms.topic: how-to
+ms.date: 03/01/2022
 ms.author: danlep
 
 ---
-# Import a SOAP API and convert to REST
+# Import SOAP API to API Management and convert to REST
 
-This article shows how to import a SOAP API and convert it to REST. The article also shows how to test the APIM API.
+This article shows how to import a SOAP API as a WSDL specification and then convert it to a REST API. The article also shows how to test the API in API Management.
 
 In this article, you learn how to:
 
 > [!div class="checklist"]
 > * Import a SOAP API and convert to REST
 > * Test the API in the Azure portal
-> * Test the API in the Developer portal
+
+[!INCLUDE [api-management-wsdl-import](../../includes/api-management-wsdl-import.md)]
 
 ## Prerequisites
 
@@ -34,41 +30,34 @@ Complete the following quickstart: [Create an Azure API Management instance](get
 
 ## <a name="create-api"> </a>Import and publish a back-end API
 
-1. Select **APIs** from under **API MANAGEMENT**.
-2. Select **WSDL** from the **Add a new API** list.
+1. From the left menu, under the **APIs** section, select **APIs** > **+ Add API**.
+1. Under **Create from definition**, select **WSDL**.
 
     ![SOAP API](./media/restify-soap-api/wsdl-api.png)
-3. In the **WSDL specification**, enter the URL to where your SOAP API resides.
-4. Click **SOAP to REST** radio button. When this option is clicked, APIM attempts to make an automatic transformation between XML and JSON. In this case consumers should be calling the API as a RESTful API, which returns JSON. APIM is converting each request into a SOAP call.
+1. In **WSDL specification**, enter the URL to your SOAP API, or click **Select a file** to select a local WSDL file.
+1. In **Import method**, select **SOAP to REST**. 
+    When this option is selected, API Management attempts to make an automatic transformation between XML and JSON. In this case, consumers should call the API as a RESTful API, which returns JSON. API Management converts each request to a SOAP call.
 
     ![SOAP to REST](./media/restify-soap-api/soap-to-rest.png)
 
-5. Press tab.
-
-    The following fields get filled up with the info from the SOAP API: Display name, Name, Description.
-6. Add an API URL suffix. The suffix is a name that identifies this specific API in this APIM instance. It has to be unique in this APIM instance.
-9. Publish the API by associating the API with a product. In this case, the "*Unlimited*" product is used.  If you want for the API to be published and be available to developers, add it to a product. You can do it during API creation or set it later.
-
-    Products are associations of one or more APIs. You can include a number of APIs and offer them to developers through the developer portal. Developers must first subscribe to a product to get access to the API. When they subscribe, they get a subscription key that is good for any API in that product. If you created the APIM instance, you are an administrator already, so you are subscribed to every product by default.
-
-    By default, each API Management instance comes with two sample products:
+1. The following fields are filled automatically with information from the SOAP API: **Display name**, **Name**, **Description**.
+1. Enter other API settings. You can set the values during creation or configure them later by going to the **Settings** tab. 
 
-    * **Starter**
-    * **Unlimited**   
-10. Select **Create**.
+    For more information about API settings, see [Import and publish your first API](import-and-publish.md#import-and-publish-a-backend-api) tutorial.
+1. Select **Create**.
 
 ## Test the new API in the Azure portal
 
 Operations can be called directly from the Azure portal, which provides a convenient way to view and test the operations of an API.  
 
 1. Select the API you created in the previous step.
-2. Press the **Test** tab.
-3. Select some operation.
+2. Select the **Test** tab.
+3. Select an operation.
 
-    The page displays fields for query parameters and fields for the headers. One of the headers is "Ocp-Apim-Subscription-Key", for the subscription key of the product that is associated with this API. If you created the APIM instance, you are an administrator already, so the key is filled in automatically. 
+    The page displays fields for query parameters and fields for the headers. One of the headers is **Ocp-Apim-Subscription-Key**, for the subscription key of the product that is associated with this API. If you created the API Management instance, you're an administrator already, so the key is filled in automatically. 
 1. Press **Send**.
 
-    Backend responds with **200 OK** and some data.
+    When the test is successful, the backend responds with **200 OK** and some data.
 
 [!INCLUDE [api-management-navigate-to-instance.md](../../includes/api-management-append-apis.md)]
 

includes/api-management-wsdl-import.md

@@ -0,0 +1,16 @@
+---
+
+title: Include file
+description: Include file
+services: api-management
+author: dlepow
+
+ms.service: api-management
+ms.topic: include
+ms.date: 03/01/2022
+ms.author: danlep
+ms.custom: Include file
+---
+
+> [!NOTE]
+> WSDL import to API Management is subject to certain [limitations](../articles/api-management/api-management-api-import-restrictions.md#-wsdl). WSDL files with `wsdl:import`, `xsd:import`, and `xsd:include` directives aren't supported. For an open-source tool to resolve and merge these dependencies in a WSDL file, see this [GitHub repo](https://github.com/Azure-Samples/api-management-schema-import).