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..
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.
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.
Well, when developing custom transports for WSO2 ESB I was recommended to use Axis2 version specific to WSO2 (1.6.1-wso2v5). Does anybody know if this version somehow differs from the "standard" 1.6.1 version? And what was the motivation for this "branching"?
AFAIK this was because some changes were done that was needed for wso2 specific details. Hence a separate wso2 version was created to cater this need.
WSO2 API manager has 4 components
API Gateway
API Publisher
API Store
API Key Manager Server
I would like to run each of these components on separate boxes. While doing so on box where I have API Publisher component I want to remove other 3 components from the api manager so on with other components. By this I would like to achieve that only 1 component exists at run time of each instance of wso2 api manger.
I would like to know how can we remove each of these components from wso2 api manager?
You can remove the relevant features from the product via Carbon Feature Management (Or you can add necessary features as well).
You can find more information regarding how to uninstall a particular feature here.
You can also find more information regarding feature management for WSO2 Carbon products here.
HTH,
Lasantha
To add to Lasantha's answer, this article describes how these 4 components can be deployed separately in a cluster with an ELB.
Installing High Level components is supported from API Manager 1.5.0 onwards. If you want to start API Manager as one of the components, that can be achieved by starting as a server profile. You can find more information here.
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