I have configured WSO2 DAS & API manager. I need per user / api version stats. As per documentation there is direct navigation for per user stats which I am not able to find. Could you please help me to configure it.
When the API is created, API level usage can be seen based on Version and users. Screenshot is available at https://docs.wso2.com/display/AM1100/Viewing+API+Statistics under “API Publisher statistics”
Related
I am developing a web app which will be pulling data from Amazon Advertising API. I need as a user to see data for all of the sellers that has approved/registered for using their profile's data.
Is this scenario possible? If not, is there anything similar to it? If yes, how do I implement it, is there some documentation?
The Amazon Advertising API v2 was released late 2018, so it's pretty new but has some missing information in the official documentation. But to get started please follow the official documentation guide:
https://advertising.amazon.com/API/docs/v2/guides/get_started
A lot of other sources are outdated, so I suggest to stick to this guide.
The logic to handle multiple Amazon Seller Accounts you have to handle yourself.
But every Seller Account has to go through the consent workflow to give your console app the rights to get access to the shop data via API. Therefore you need to implement a 'Login with Amazon' button - That's the part that is not mentioned in the documentation. See https://login.amazon.com/
I have followed the article by #Ruks : [Article] Enabling Monetization of APIs with WSO2 API Manager and configured my WSO2 API Manager 2.0.0 and WSO2 API Manager Analytics 2.0.0 with monetization. Billing engine is working fine. There are two issues:
Issue 1. When user is redirected from API Manger to billing engine for payment information, after successful signUp or login it does not redirect back to API manger.
Issue 2. On Analytics logs i am getting following error continuously
No schema is available for table ORG_WSO2_APIMGT_STATISTICS_REQUEST\r\n","stream":"stdout","time":"2017-01-12T18:52:01.569122694Z"}
Please advise. what is wrong. Thanks.
The repo to the sample billing engine provided in the article may not compatible with APIM 2.0.0. Please refer follwing repo and checkout am-2.0 tag which is compatible with APIM 2.0.0.
Also note that in the hosted version of API Manager - WSO2 API Cloud - monetization just works out of the box because the engine has been pre-integrated with Stripe. You just enable the monetization feature in the Configure menu, set pricing for your tiers, and configure the Stripe account to send you the money. See the tutorial here: https://docs.wso2.com/display/APICloud/Enable+Monetization
I would like to combine WSO2 AM and DAS with billing function.
I tried to set it by referring to the following site, but the article did not correspond to WSO2 APIM(2.0.0).
http://wso2.com/library/articles/2016/07/article-enabling-monetization-of-apis-with-wso2-api-manager/
http://www.rukspot.com/Publishing_APIM_1100_Runtime_Statistics_to_DAS.html
I want to publish WSO 2 APIM(2.0.0) runtime statistics to DAS.
But,WSO2 AM(2.0.0) does not have admin-dashboard like WSO2 AM(1.10.X).
・Should I lower the WSO2 AM version?
・Is there a procedure / article based on WSO 2 AM (2.0.0)?
・Do you have my point should be noted?
Thanks a lot.
From 2.0.0 onwards, it's called admin portal, and the URL is https://localhost:9443/admin. However, analytics configurations are removed from Admin Portal UI. So you have to use api-manager.xml file to configure analytics.
Refer this doc to configure analytics in 2.0.0.
Also, note that online service based on API Manager - WSO2 API Cloud - has API monetization and billing integration available out-of-box - just configure your billing plans and bank account and start collecting money: https://docs.wso2.com/display/APICloud/Enable+Monetization
There´s a guide on the same blog that you linked
http://www.rukspot.com/configure_wso2_das_for_apim_analytics.html
This is for configuring DAS. If you only care about analytics data for apim I would recommend the new wso2am-analytics instead of the DAS. It's made specially for the apim and much easier to configure. See the guide that Bhatiya provided on how to configure wso2am-analytics.
The article is for APIM 1.10.0 and DAS 3.0.x. If you want to try this with APIM 2.0.0 you need to used the sample billing engine in this repo. checkout the tag am-2.0 and check.
I am using WSO2 API Manager 2.0.0 along with WSO2 DAS 3.0.1
Query : API Usage statistics in PUBLISHER STATISTICS does not have user-wise split in latest version. Based on the documentation and webinars of WSO2, looks like user-wise split for API usage statistics was available in earlier versions. Am i missing any configurations here? Please clarify.
If you are referring to APIM 1.10, then AFAIK there is no major difference in statistic bases in APIM 1.10 and 2.0. The statistics module in both versions is able to show publisher wise user statistics. For that you can use this guide.As in the documentation you can check the user statistics by clicking on the API and referring to its Users tab.
Hope this helps.
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.