I am studying Open source API manager implementation on microservices and I start with WSO2 API Manager 3.1.0 using the available documentation but many solutions mentioned in the document doesn't work.
For example, I checked a forum where people are trying to remove some parts of Response headers especially server: WSO2 Carbon Server. As per documentation it says update <API-M_HOME>/repository/deployment/server/synapse-configs/default/sequences/main.xml and add lines mentioned here https://apim.docs.wso2.com/en/3.1.0/learn/api-gateway/message-mediation/removing-specific-request-headers-from-response/#removing-specific-request-headers-from-response. This did not work for me.
Is this something only available in licensed version or what is the correct process?
Related
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'm using WSO2's API Manager version 2.5.0 (https://github.com/wso2/product-apim/tree/v2.5.0).
Problem:
I create a REST API then create a SOAP API. When I edit the REST API looking at the first page (Design), it shows a SOAP endpoint instead of the REST endpoints. If I then create a websocket API and view the design page of the REST and SOAP APIs, the endpoints aren't shown indicating they are now websocket APIs. If I then create another REST API, viewing the design page of the other APIs shows they are now back to normal.
Question:
What is causing this to happen? Is there a fix for it? Does anyone have information about this? I've done extensive research looking through their docs, their github, stackoverflow, and google searches with no luck.
This is a known issue in 2.5.0 and fixed in 2.6.0.
Edit: My bad. It seems it's fixed after 2.6.0 release.
You can use the development branch[1].
[1] https://github.com/wso2/product-apim/tree/2.x
Halo everybody (maybe Asela? :),
Can anyone guide me how can I implement Oracle Coherence as a Cache provider with WSO2 Identity Server 5.0.0 clustered using with WSO2 ELB?
I found some very useful links on that topic, from which I consider this one as a good start: Clustering Identity Server
But I cannot find a way how to find solution for changing Hazelcast cache provider for any other provider.
I also realized, WSO2 is not using javax.caching implementation from JDK (since it was introduced in 1.7 and later), it is using its own based on JSR-107 (from which JSR I suppose Java JDK JCache is originated.
This article shows, that there is a way, how to somehow implement user JSR 107 JCache, but I don't see it configured for whole Identity Server:
WSO2 Multi-tenant Cache: JSR-107 (JCache)
I'm expecting answer which will guide me, what to change or add (for instance to carbon core) and where to setup / configure those changes, to make them global used within WSO2 Identity Server 5.0.0.
I hope it is relevant question and since this Carbon based platform is very rich and configurable, I hope this will be possible with some time invested.
Thank you in advance,
Josef
Coherence supports the real JCache APIs, so if WSO2 uses JCache, it should be easy to integrate Coherence!
This is regarding wso2 APM
Is there a getting started guide for those who wanted to start contributing to WSO2 API Manager.
Any feature request page where I can see community voted new features on which contribution is required ?
Thanks.
To get an understanding about the jaggery application structure in the API manager (The UI parts) you can read following tutorials
http://wso2.com/library/tutorials/2012/09/customizing-api-store-publisher-part1/
http://wso2.com/library/tutorials/2013/08/customizing-api-storepublisher-jaggery-applicationspart2/
this is the structure followed in api manager store, publisher and admin-dashboard jaggery application.
You can read http://wso2.com/library/tutorials/writing-custom-hostobject/ to see how the jaggery application is connected with the java code.
These will give you a basic understanding about the code base of the api manager.
Is there a getting started guide for those who wanted to start
contributing to WSO2 API Manager.
WSO2 API Manager is 100% open source API Management solution. You can find the component source code in github, component repo and product repo
Any feature request page where I can see community voted new features
on which contribution is required ?
You can find those information in the following mailing list
dev#wso2.org is a mailing list to discuss about all WSO2 products.
I went thorough the features of WSO2 ESB. I noticed WSO2 Coud Connectors like Twitter, LinkedIn ..
I would like to know about any documents, wiki which supports this. I have the Auth Keys from Twitter. I want to do a simple twitter integration using WSO2 ESB.
Please share your thoughts.
Regards,
Guru
#gnanagurus
This is a new feature that will be released with WSO2 ESB 4.5.0. You can do 3rd party API integration very easily with this new feature. For example once the Twitter Connector Library is deployed in the ESB , you can feed the relevant OAuth keys directly and connect to Twitter Cloud seamlessly. Currently there are no publicly available docs. But please await we will be releasing this documentation soon with upcoming releases.
You can find the documentation on connectors from here. Twitter specific documentation can be found here.