How to manage billing with WSO 2 AM (2.0.0) - wso2

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.

Related

swagger url for WSO2 Governance registry5.4.0 REST API

I am exploring the WSO2 Governance registry version 5.4.0. I would like to get the swagger url for WSO2 governance registry REST API so that I can call the rest apis to create/update/delete/get resources in Publisher portal.
I have installed the WSO2 Governance registry 5.4.0 locally on my windows 10 machine.
Please help me with this. Thanks a lot in advance.
First of all this is not a programming issue but support. Please refer below documentations provided by WSO2:
Invoking a REST Service Using the In-built Swagger UI
Adding a
REST Service
For this case you better subscribe to WSO2 mailing list and mail them your query. They will surely reach you.

WSO2 analytics confusion

I would like to generate visualization(charts) on the usage of API accessed via WSO2 API Manager. I see many products and versions and cannot find right one. What is the difference between these products ?
API M Analytics 2.2
API DAS server 3.2
API Streaming processer 4.1
I'm using API manager 2.2 version and need real time analytics so which one is suitable for this purpose and the corresponding documentation to setup ?
Thanks in advance.
With APIM 2.2.0 you should use APIM Analytics 2.2.0. It's a DAS with some custom code specific to APIM.
For statistics, APIM out of the box supports batch analytics only. However, it supports alerts.
You can read this for analytics configurations.

WSO2 AM2.0.0 monetization - Error wso2carbon.log:No schema is available for table ORG_WSO2_APIMGT_STATISTICS_REQUEST

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

WSO2 API Manager - API Usage statistics by each user is missing in latest release 2.0.0

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 Cloud adapters

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.