I have created instance in Azure API management service and want to import 200+ APIs. Is there any way to automatically import the APIs in portal by writing script or any other way also want to create a product and group the imported APIs?
You can automate deployment of API's by using Azure APIM REST API. You will find everything there. Basically whatever you do in Azure Portal on APIM resource by clicking you can do by calling this REST API.
If you don't feel like calling REST API, you can always use Az.ApiManagement PowerShell Module or az apim Azure CLI - they have more or less the same functionality.
I guess that is it, the question is too broad to give you more specifics.
Related
I am trying to integrate the dialog flow agent with a middleware bot. However, due to some issue, I am not able to use service account keys and have to find some alternate method for communication of APIs, Can we use API keys for this purpose?
One solution is to use a solution such as Cloud Endpoint or API Gateway (which is a Cloud Endpoint fully managed, same configuration, same features for now).
I wrote an article on Coud Endpoint with ESPv2 on Cloud Run
I'm working on a Java project, using SparkJava framework. I made REST web services, and now I'm trying to place WSO2 API Manager in front of my services.
The problem is that I don't know how to import the backend service description into WSO2 API MANAGER. I saw that this is often done with WADL, but in WSO2 APIM documentation (v2.5.0) there is nothing about this.
My goal is to generate some file which contains my Backend service description (I don't know what format should it be, or what tool must I use to do this), and be able to import it in WSO2 API MANAGER as my API documentation.
Is there a way to do this ?
WADL was used sometime back, but now the common and the standard and way of representing a RESTful API is swagger/OAS.
In WSO2 APIM there are several ways you can create a proxy API for your backend service.
1) If you already have a swagger/OAS spec for your backend service, you can import it to APIM.
2) Create API from the scratch. In this approach, you can define resources and there parameters/headers etc. using the publisher UI.
I have multiple API's which I have exposed it via Azure API Management.
I am using one instance for across various environments. So currently I am adding / updating the API's / operations manually. Also I am setting cache, rewrite url for few of these operations. But now managing these are becoming a bit of too much work.
Is there a way, when any operation contracts changes in an API, I can then build / refresh the APIM and also setup the cache, re-write url, policies etc without manual intervention in APIM?
You can consider use Swagger, the OPEN API in Azure to control the data flow with Azure API policy for security and using Azure provided REST API to provision the APIm service and use the App Service to build the backend.
General Concept Flow
AGW <> APIM <> API <> App Service
Supposed that customer only provides me the URL end point of their existing API. They don't have swagger file for us to import the APIs.
Customer wants to use API Connect to publish their API to users to use.
I did that successfully with API Management. Now API Management is deprecated by API Connect, but that feature is still in API Connect. I failed to make it work with API Connect. How can we use API Connect to publish the existing REST API of customer not using swagger? Please shed the light. I'm greatly appreciated with your help.
Regards,
Quyen Tran
To publish an API into an IBM API Connect catalog, and to have access to that API managed by the API Gateway, you will need a Swagger (OpenAPI) document.
If you don't have a Swagger document, you will need to author one e.g. using the API Designer or API Manager tooling. You will need to know the URL of the existing endpoint but also the schema of any data that needs to be sent to or received from that URL.
If you made it work with IBM API Management then it should be no different with IBM API Connect.
We successfully launch Wso2 API management solution. One of the main functionality of our project is to orchestrate several simple API and make one Meta API. Then we want to publish this Meta API into Wso2 API Management Publisher and make it available to use.
Is any solution to this requirement?
You can do this. If I understand you correct, you only want to publish the meta api as a managed api. Other simple apis won't be published. If so, things are pretty easy.
WSO2 API Manager uses Apache Synapse as the mediation engine (which is used by WSO2 ESB too). This allows to do the chaining. Please go through the following articles.
http://wso2.com/library/articles/2014/03/batch-api-api-chaining-scenario/
https://docs.wso2.com/display/ESB470/Service+Chaining+Example
http://wso2.com/library/articles/2012/09/get-cup-coffee-wso2-way/