Can someone send me link / pdf which samples the API Design Document. API can be RESTFul or SOAP. Help is much appreciated, please.
Regards, Sreedhar
If video tutorials can assist you better, you can find them in [1]. These tutorials were recorded using the SaaS version of API Manager (API Cloud), they do apply to an on-premise deployment of API Manager as well.
[1] - https://www.youtube.com/playlist?list=PLp0TUr0bmhX49rEwMR7BDX2O9-iQHOOzN
You can have a look on this quick start guide to create APIs in API Manager. We provide a sample API with API Manager which will help you in understanding how API Manager works with APIs
Related
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
We are using WSO2 API Manager for exposing and securing our API's.
Its working fine.
Now we have actually a lot of API's in WSO2 API Manager. It looks like a long list of API's. Now its hard to find an API and do some changes.
Is there any best practices for organizing them in API manager?May be group them based on functionality or url or anything like that.
Any inbuild support or suggestions?
I am new to WSO2 and we are planing to use WSO2 in our product. Our requirement is to communicate with other system through TCP(socket) and rest web services. I did not find any help regrading to my requirement.
I need a step by step guide or any tutorial about my requirements or any sample projet. Thanks
You can use WSO2 ESB to connect systems with TCP and HTTP(rest). You can go through WSO2 ESB documents and find enough samples on that. TCP[1][2], rest api[3]. If you are going to manage the rest apis then you can use the WSO2 API Manager[4]
[1]https://docs.wso2.com/display/ESB500/Setting+Up+the+ESB+Samples#SettingUptheESBSamples-ConfiguringWSO2ESBtousetheTCPtransport
[2] https://docs.wso2.com/pages/viewpage.action?pageId=33136069
[3] https://docs.wso2.com/display/ESB500/Using+REST+with+APIs
[4] https://docs.wso2.com/api-manager-documentation
I'm trying to integrated wso2 api manager in our organization. We are using Open AM as out Single sign on. I tried to search for some documentation for it but couldn't find any for wso2 API manager authentication and possibly authorization piece integration with Open AM. Is there any extension or plugin available to integrate it?
Appreciate if have any idea about this. Thanks in advance!
Regards,
Jayesh
Please refer this blog post in [1]. Here I done it for WSO2 BAM. Same as you can do it for WSO2 AM.
[1] http://manulachathurika.blogspot.com/2013/10/configure-opensso-for-wso2-business.html
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.