¿Cómo funciona la API SOAP en Azure?

How does the SOAP API work in azure?

Analytics for SOAP APIs in Azure API Management work in just the same way as REST APIs. A few quick notes on working with SOAP. Firstly, we now give you the ability in policy expressions to access the SOAP Body: You can also use our management API to upload WSDLs, rather than the publisher portal:

Many of our customers have requested the ability to use Azure API Management to create a proxy for their SOAP APIs in the same way that we allow them to for REST/HTTP APIs, enabling developer portal integration, analytics, policies etc. This article will take you through how to set a SOAP API up and show you how the new API works.

On the Application gateway blade, select the HTTP settings. Select the HTTP setting you created. In the Request Timeout (seconds) box, enter a higher value, such as 120. Or, enter a value that is greater than the number of seconds that your server takes to return the response to every request. Click Save.

If the back-end pool is empty, and there is no server to forward the request, the application gateway returns an “HTTP 502” error message to the client. To resolve this issue, follow these steps to add back-end servers to back-end pool: In Azure portal, select All resources, and then select the application gateway.

API Management supports SOAP out-of-the-box using WSDL. However, we have to know that API Management has some restrictions of using WSDL. In other words, some SOAP-based webservices having complex structure might not be suitable for using API Management. What about Logic Apps?

Go to your Azure API Management instance in the Azure portal. Select APIs on the Overview page or from the menu on the left. Click next to the API that you want to append another API to. Select Import from the drop-down menu. Select a service from which to import an API.