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.
Related
I linked some existing back-end APIs to the API Publisher.
Due to some reasons, I need to create an API without any existing back-end API for it in a specific route (for example in .../myAPI/ path). The API should do something and then return a response to user.
how can I do this using WSO2 API manager? Do I need to write a handler for it? Thanks for any help.
I have an API deployed in API Manager, deployed one interface in cloud hub with API auto discover option.
In API manager, i gave cloudhub link as implementation url. so i thought both are linked up.
But when i apply SLA tier to API it is not getting applied. is there anything need to be done ?
Please first apply Auto discovery properly on the app. Create one API in the API manager. copy API ID into autodiscover configuration in the app. please find below link for details explanation.
Auto discovery article from dzone
I created a RAML file in API Design, then deployed in API manager and implemented in API runtime manager. It is clear no issues now.
Now i got change in raml file. I did changes in API Design and published into exchange with v2.
The problem here is how to import the v2 API into API manager ?
after importing the new api do i need to add all policies applied on v1 API to v2 API again ?
or is there any automatic option ?
I don't find any options in API manager, please help me..,
Yes, we need to apply policies again. Even when there is the same API version have 2 instances.
If you do not have major change then you can just go to action and upgrade to next assent version of the same API. Else you need to apply policies.
Ranveer
I have created one application in mulesoft, I'm trying to create an api for that application in api manager, can anyone provide the steps for integrating both?
You can follow the steps given in this doc, use your application endpoint as backend while creating the API
https://docs.wso2.com/display/AM200/Create+and+Publish+an+API
I have created some APIs in API management layer, which are essentially proxies between the calling client and an underlying web api.
I did this by importing the swagger file of the underlying API, and then adding the newly created API to a Product, repeating this for each separate proxy that I needed. This means then that the underlying API could be called but not without the subscriber key of the product that the newly created API was attached to.
Is it possible to do something similar with API apps, i.e. creating API apps using just the swagger file from the underlying API in the azure portal, that act as proxies between the calling client and an underlying web api (as below)?
Do you mind expanding on why do you need to have API Apps acting as proxies?
I am not aware of such capability for API Apps specifically. There are Swagger-based code generation tools available, for example on http://swagger.io/open-source-integrations/. So perhaps you will be able to find something that would work for you.