I have PizzaV1.0.0 API, which strategy does it use to generate a new V2.0.0 version and keep both in ESB.
If version the CAR, the duplicity of APIs and Sequences.
I have not found a way to version the APIs in eclipse, I need to version the API and some sequences that have changed.
In API Manager I created a new version, now I have two versions published.
What versioning strategy do you use in ESB to stay in sync with API Manager?
Maybe this post can help you
http://nandikajayawardana.blogspot.com.br/2014/02/proxy-service-version-management-with.html
I do what they describe and it is working great.
Related
I would like to implement automatic rules of API Goverment in a WSO2 API Manager platform like, for example, validating context with a regular expresion, or version numbering or API name or API resources endpoint naming or parameters, etc.
I checked in version 2.6.0 (and previous versions of major 2) that it can be done in jaggery apps of publisher, but this is a mix of data and presentation (view structure with js and html) and it is not a clear and right way to implement it.
Is there any rules engine or other dedicated mechanism to do it? If not, is it in the roadmap of WSO2 AM to add this kind of features? It would be great.
APIM 3.x onwards UIs are implemented using react and backend services are exposed via REST APIs. SO from this version onwards, this is clearly separated. UI level validations can be changed in the React and if there are any additional validations required, REST API interceptors or workflow interceptors can be used to enforce any validations.
Can I publish an agent version on an environment using the Dialogflow V2 API?
I can't find any documentation on how to do that.
The doc about versions and environments only mentions doing this using the console (https://cloud.google.com/dialogflow/docs/agents-versions).
And the API doc of the agent environments resource only contains a list method (https://cloud.google.com/dialogflow/docs/reference/rest/v2/projects.agent.environments).
Does it mean that every change done using the API is automatically reflected in production?
Or does it mean that every change done by API is staged, and can only go to production by manually accessing the console and publishing the new version?
Both options seems terrible by the way.
Currently, it's not possible to manage agent versions through the Dialogflow API, it seems that this feature is already being contemplated to be integrated to Dialogflow; however, there is no an ETA for its implementation. You can follow up this request here.
I am exploring options to pass custom/standard headers to downstream service using WSO2 Api Manager.
I have gone through mediation documentation, and had play around with WSO2 developer studio as well.
I see that the documentation of the latest version of API Manager- 3.0.0 and the actual product vary a lot and I ran into different issues as the WSO2 developer studio is still designed for older version of API Manager.
Can you guide me to proper documentation which holds true for API Manager 3.0.0 or a simple way to achieve header mapping for request and response from API Manager.
I need to create a API in wos2am and its httpmethod is PATCH.
How can I let wso2am to support PATCH? or do I need to add some custom features?
Currently the API Manager does not support the Patch method. There is a plan to support it in future, but I cannot tell a release timeline. It should be first supported by the underlying Synapse.
APIM manager uses synapse as is underlying mediation engine which currently supports OPTIONS,GET, POST, PUT, DELETE..
I have a working system with ESB (non-WSO2 product) already. I'm now trying to integrateWSO2 API Manager into my working system for 3rd party developer.
Is it possible to replace WSO2 ESB in API Manage with existing non-WSO2 ESB?
Yes, you can do that.
The ESB functionality is transparent no matter what is the brand of underlying product implementing it. The API Manager is going to store the endpoints, WSDLs, etc. and those are the same for every ESB implementation.
That's the "beauty" of SOA, its service-oriented, not vendor-oriented.
You can keep the ESB you are using as it is in your setup and use the API Manager to publish/subscribe/manage the API. Its perfectly a valid scenario
Regards,
/Nuwan