Re: [Dev] [Architecture] [DEV] [VOTE] Release WSO2 API Manager Tooling v3.1.0 RC4
Hi all Tested apictl with followings. 1. Install k8s api-operator and wso2am-operator in a k8s cluster 2. Tested API Operator scenarios with the apictl 3. Added environments and import the APIs 4. Generated keys for the imported APIs 5. Uninstall the API Operator using apictl No blockers found *[+] Stable - Go ahead and release* *Thanks* On Sat, Apr 4, 2020 at 11:50 AM Pubudu Gunatilaka wrote: > Hi, > > Tested the apictl for the basic use cases of K8s API Operator. No blockers > found. > > [+] Stable - Go ahead and release > > Thank you! > > On Sat, Apr 4, 2020 at 9:36 AM Renuka Fernando wrote: > >> Hi all >> >> Tested apictl with followings. >> >>1. Install k8s api-operator in a k8s cluster >> - Batch mode (non interactive) with registry types: HTTP private >> registry, DockerHub >> - Interactive mode with registry types: GCR, AWS ECR >>2. Install k8s wso2am-operator >>3. Add a new API to k8s cluster using the "apictl add api" command. >> - With one replica >> - With two replicas >>4. Add a new API with multiple swaggers to k8s cluster using the "apictl >>add api" command. >>5. Update an API in k8s cluster. >>6. Change docker registry type for adding API to the k8s cluster. >> - Batch mode (non interactive) with registry types: AWS ECR >> - Interactive mode with registry types: AWS ECR >> >> >> No blockers found >> >> *[+] Stable - Go ahead and release* >> >> Thanks >> Best Regards >> >> *Renuka Fernando* | Software Engineer | WSO2 Inc. >> (m) +9476 6678 752 | Email: ren...@wso2.com >> <http://wso2.com/signature> >> >> >> On Fri, Apr 3, 2020 at 7:10 PM Uvindra Dias Jayasinha >> wrote: >> >>> Tested the following: >>> >>> Various scenarios involving super tenant, tenant, secondary user store >>> users >>> >>> 1. Generate Keys >>> 2. Export Apps >>> >>> No blockers found >>> >>> [+] Stable - Go ahead and release >>> >>> On Fri, 3 Apr 2020 at 14:16, Naduni Pamudika wrote: >>> >>>> Hi All, >>>> >>>> WSO2 Api Manager team is pleased to announce the fourth release >>>> candidate of WSO2 API Manager Tooling 3.1.0 version. >>>> >>>> The WSO2 API Manager tooling provides the capability to import and >>>> export APIs and Applications across multiple environments seamlessly. Hence >>>> it provides greater flexibility to create CI/CD pipelines for APIs and >>>> applications. >>>> >>>> Apart from migrating APIs and applications, it supports Kubernetes API >>>> operator to deploy and manage APIs in the Kubernetes cluster by reducing >>>> additional overheads for the DevOps. >>>> >>>> Please find the improvements and fixes related to this release in Fixed >>>> Issues >>>> <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aissue+is%3Aclosed+label%3A3.1.0> >>>> . >>>> >>>> Download the API Manager Tooling Distribution from here >>>> <https://github.com/wso2/product-apim-tooling/releases/tag/v3.1.0-rc4>. >>>> >>>> The tag to be voted upon is >>>> https://github.com/wso2/product-apim-tooling/releases/tag/v3.1.0-rc4 >>>> >>>> Documentation: >>>> https://apim.docs.wso2.com/en/next/learn/api-controller/getting-started-with-wso2-api-controller/ >>>> >>>> Please download, test the tool and vote. >>>> >>>> >>>> *[+] Stable - Go ahead and release* >>>> >>>> *[-] Broken - Do not release *(explain why) >>>> >>>> >>>> >>>> Best Regards, >>>> WSO2 API Manager Team >>>> >>>> -- >>>> *Naduni Pamudika* | Senior Software Engineer | WSO2 Inc. >>>> (m) +94 (71) 9143658 | (w) +94 (11) 2145345 | (e) nad...@wso2.com >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>>> >>> >>> -- >>> Regards, >>> Uvindra >>> >>> Mobile: 33962 >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Pubudu Gunatilaka* | Technical Lead | WSO2 Inc. > (m) +94774078049 | (w) +94112145345 | (e) pubu...@wso2.com > <http://wso2.com/signature> > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [Vote] Release of WSO2 API Manager 3.1.0 RC3
;>>>>> >>>>>>>>>>>> We are pleased to announce the third release candidate of WSO2 >>>>>>>>>>>> API Manager 3.1.0. >>>>>>>>>>>> >>>>>>>>>>>> This release fixes the following issues. >>>>>>>>>>>> >>>>>>>>>>>>- Fixes : product-apim >>>>>>>>>>>> >>>>>>>>>>>> <https://github.com/wso2/product-apim/issues?q=is%3Aissue+is%3Aclosed+closed%3A2019-11-01..2020-03-20+label%3A3.1.0+> >>>>>>>>>>>>- Fixes : analytics-apim >>>>>>>>>>>><https://github.com/wso2/analytics-apim/milestone/20?closed=1> >>>>>>>>>>>> >>>>>>>>>>>> Source and distribution, >>>>>>>>>>>> Runtime : >>>>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v3.1.0-rc3 >>>>>>>>>>>> Analytics : >>>>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v3.1.0-rc3 >>>>>>>>>>>> >>>>>>>>>>>> Please download, test the product and vote. >>>>>>>>>>>> >>>>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>>>> >>>>>>>>>>>> Thanks, >>>>>>>>>>>> WSO2 API Manager Team >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> >>>>>>>>>>>> *Krishan Wijesena* >>>>>>>>>>>> Senior Software Engineer | WSO2 >>>>>>>>>>>> >>>>>>>>>>>> Email : krish...@wso2.com >>>>>>>>>>>> Mobile : +94776219923 >>>>>>>>>>>> WSO2 Inc : http://wso2.com >>>>>>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> *Tharindu Dharmarathna*Technical Lead >>>>>>>>>>> WSO2 Inc.; http://wso2.com >>>>>>>>>>> lean.enterprise.middleware >>>>>>>>>>> >>>>>>>>>>> mobile: *+94779109091* >>>>>>>>>>> ___ >>>>>>>>>>> Dev mailing list >>>>>>>>>>> Dev@wso2.org >>>>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> *Sanjula Madurapperuma* | Software Engineering Intern | WSO2 Inc. >>>>>>>>>> (m) +94 768877766 | (e) sanj...@wso2.com >>>>>>>>>> <http://wso2.com/signature> >>>>>>>>>> ___ >>>>>>>>>> Architecture mailing list >>>>>>>>>> architect...@wso2.org >>>>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> *Nuwan Dias* | Senior Director | WSO2 Inc. >>>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>>>>>>>> ___ >>>>>>>>> Dev mailing list >>>>>>>>> Dev@wso2.org >>>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> >>>>>>>> *Krishan Wijesena* >>>>>>>> Senior Software Engineer | WSO2 >>>>>>>> >>>>>>>> Email : krish...@wso2.com >>>>>>>> Mobile : +94776219923 >>>>>>>> WSO2 Inc : http://wso2.com >>>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Krishan Wijesena* >>>>>>> Senior Software Engineer | WSO2 >>>>>>> >>>>>>> Email : krish...@wso2.com >>>>>>> Mobile : +94776219923 >>>>>>> WSO2 Inc : http://wso2.com >>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>> ___ >>>>>>> Architecture mailing list >>>>>>> architect...@wso2.org >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rukshan C. Premathunga | Associate Technical Lead | WSO2 Inc. >>>>>> (m) +94711822074 | (w) +94112145345 | Email: ruks...@wso2.com >>>>>> GET INTEGRATION AGILE >>>>>> Integration Agility for Digitally Driven Business >>>>>> ___ >>>>>> Dev mailing list >>>>>> Dev@wso2.org >>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc. >>>>> +94 710 618 178 >>>>> GET INTEGRATION AGILE >>>>> Integration Agility for Digitally Driven Business >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> *Vithursa Mahendrarajah* | Senior Software Engineer | WSO2 Inc >>> (m) +94 766 695 643 | (e) vithu...@wso2.com >>> >>> * <http://wso2.com/signature>[image: https://wso2.com/signature] >>> <https://wso2.com/signature>* >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Kavishka Fernando* >> *Senior Software Engineer | WSO2* >> Email: kavis...@wso2.com >> Mobile: +94773838069 >> Web: http://wso2.com >> Blog: https://medium.com/@kavishkafernando >> >> <http://wso2.com/signature> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > > *Sachini De Silva* > Senior Software Engineer - WSO2 > > Email : sachi...@wso2.com > Mobile : +94714765495 > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] API Operator for Kubernetes 1.0.0 Released!
*API Operator for Kubernetes 1.0.0 Released!* As microservices are increasingly being deployed on Kubernetes, the need to expose these microservices as well documented, easy to consume, managed APIs is becoming important to develop great applications. The API operator for Kubernetes makes APIs a first-class citizen in the Kubernetes ecosystem. Similar to deploying microservices, you can now use this operator to deploy APIs for individual microservices or compose several microservices into individual APIs. With this users will be able to expose their microservice as managed API in Kubernetes environment without any additional work. *Distribution & Documentation* The distribution of the API Operator can be found in API Operator GitHub <https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.0> repository. Quick Start Guide <https://github.com/wso2/k8s-apim-operator/blob/v1.0.0/docs/GettingStarted/quick-start-guide.md> Documentation <https://github.com/wso2/k8s-apim-operator/tree/v1.0.0/docs> Bug Fixes And Improvements in API Operator 1.0.0 Fixed issues <https://github.com/wso2/k8s-apim-operator/issues?utf8=%E2%9C%93=is%3Aissue+is%3Aclosed+label%3A1.0.0> Known Issues All the open issues pertaining to WSO2 Kubernetes APIM Operator are reported at GitHub <https://github.com/wso2/k8s-apim-operator/issues> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> *User Forum:* StackOverflow <https://stackoverflow.com/questions/tagged/wso2-am> *WSO2 APIM Slack <https://wso2-apim.slack.com/>: *Join <https://join.slack.com/t/wso2-apim/shared_invite/enQtNzEzMzk5Njc5MzM0LTgwODI3NmQ1MjI0ZDQyMGNmZGI4ZjdkZmI1ZWZmMjNkY2E0NmY3ZmExYjkxYThjNzNkOTU2NWJmYzM4YzZiOWU?src=sidebar> Reporting Issues We encourage you to report issues, improvements and feature requests regarding API Operator through GitHub <https://github.com/wso2/k8s-apim-operator/issues> *Important:* And please be advised that security issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager Tooling 3.0.0 is Released!
*The WSO2 API Manager team is pleased to announce the release of version 3.0.0 of API Manager Tooling.* The WSO2 API Manager tooling provides the capability to import and export APIs and Applications across multiple environments seamlessly. Hence it provides greater flexibility to create CI/CD pipelines for APIs and applications. Apart from API and application migration, it supports for Kubernetes API operator to deploy and manage APIs in the Kubernetes cluster by reducing additional overheads for the DevOps. *Distributions & Documentation* API Manager Tooling Distribution <https://wso2.com/api-management/tooling/> API Manager Tooling Documentation <https://apim.docs.wso2.com/en/latest/Learn/CICDPipeline/initializing-projects-using-the-cli-tool/> Bug Fixes And Improvements in API Manager Tooling 3.0.0 Fixed issues <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aissue+is%3Aclosed+label%3A3.0.0> Known Issues All the open issues pertaining to WSO2 API Manager Tooling are reported at GitHub <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aopen+is%3Aissue> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive - User List: u...@wso2.org | Subscribe | Mail Archive *User Forum:* StackOverflow <https://stackoverflow.com/questions/tagged/wso2-am> *WSO2 APIM Slack <https://wso2-apim.slack.com/>: *Join <https://join.slack.com/t/wso2-apim/shared_invite/enQtNzEzMzk5Njc5MzM0LTgwODI3NmQ1MjI0ZDQyMGNmZGI4ZjdkZmI1ZWZmMjNkY2E0NmY3ZmExYjkxYThjNzNkOTU2NWJmYzM4YzZiOWU?src=sidebar> Reporting Issues We encourage you to report issues, improvements and feature requests regarding WSO2 API Manager Tooling through tooling GitHub repository <https://github.com/wso2/product-apim-tooling/issues/new>. *Important:* And please be advised that security issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the WSO2 Security Vulnerability Reporting Guidelines <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting the security issues. *-- The WSO2 API Manager Team --* *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Kubernetes APIM Operator v1.0.0-Beta is Released!
*The WSO2 API Manager team is pleased to announce the release of version 1.0.0-Beta of Kubernetes APIM Operator.* WSO2 API Manager is a full lifecycle API Management solution with monetization and policy enforcement. WSO2 API Microgateway is a cloud-native, developer-centric and decentralized API gateway for microservices. Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications. The intention of this project is to provide cloud-native full API management by seamless integration with Kubernetes. With this native API Management support on K8s, this targets to improve the developer/devOps experience. *Distribution & Documentation* WSO2 Kubernetes APIM Operator Distribution <https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.0-beta> Documentation <https://github.com/wso2/k8s-apim-operator/blob/v1.0.0-beta/README.md> Bug Fixes And Improvements in WSO2 APIM Kubernetes Operator v1.0.0-Beta Fixed issues <https://github.com/wso2/k8s-apim-operator/issues?q=label%3Av1.0.0-beta+is%3Aclosed> Known Issues All the open issues pertaining to WSO2 Kubernetes APIM Operator are reported at GitHub <https://github.com/wso2/k8s-apim-operator/issues> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 Kubernetes APIM Operator through k8s-apim-operator <https://github.com/wso2/k8s-apim-operator/issues>. Please be advised that the *s*ecurity issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the security vulnerability reporting guide <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 Kubernetes APIM Operator v1.0.0-Alpha is Released!
*The WSO2 API Manager team is pleased to announce the release of version 1.0.0-Alpha of Kubernetes APIM Operator.* WSO2 API Manager is a full lifecycle API Management solution with monetization and policy enforcement. WSO2 API Microgateway is a cloud-native, developer-centric and decentralized API gateway for microservices. Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications. The intention of this project is to provide cloud-native full API management by seamless integration with Kubernetes. With this native API Management support on K8s, this targets to improve the developer/devOps experience. *Distribution & Documentation* WSO2 Kubernetes APIM Operator Distribution <https://github.com/wso2/k8s-apim-operator/releases/tag/v1.0.0-alpha> Documentation <https://github.com/wso2/k8s-apim-operator/blob/v1.0.0-alpha/README.md> Bug Fixes And Improvements in WSO2 APIM Kubernetes Operator v1.0.0-Alpha Fixed issues <https://github.com/wso2/k8s-apim-operator/issues?q=label%3Av1.0.0-alpha+is%3Aclosed> Known Issues All the open issues pertaining to WSO2 Kubernetes APIM Operator are reported at GitHub <https://github.com/wso2/k8s-apim-operator/issues> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 Kubernetes APIM Operator through k8s-apim-operator <https://github.com/wso2/k8s-apim-operator/issues>. Please be advised that the *s*ecurity issues must be reported to secur...@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the security vulnerability reporting guide <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] WSO2 API Manager Tooling v3.0.0-Alpha is Released!
*The WSO2 API Manager team is pleased to announce the release of version 3.0.0-Alpha of API Manager Tooling.* Major improvements include supporting token generation for APIs for testing purposes. Also, it includes support for Kubernetes APIM operator to deploy and manage APIs in the Kubernetes cluster. Further, APIM CLI supports API updates and exporting applications with consumer key and secrets. Also, this release provides greater flexibility to create CI/CD pipelines for APIs. *Distributions & Documentation* APIM CLI Distributions <https://github.com/wso2/product-apim-tooling/releases/tag/v3.0.0-alpha> APIM CLI Documentations <https://github.com/wso2/product-apim-tooling/blob/v3.0.0-alpha/import-export-cli/docs/apimcli.md> Bug Fixes And Improvements in API Manager Tooling v3.0.0-Alpha Fixed issues <https://github.com/wso2/product-apim-tooling/labels/apim-v3-alpha> Known Issues All the open issues pertaining to WSO2 API Manager Tooling are reported at GitHub <https://github.com/wso2/product-apim-tooling/issues?q=is%3Aopen+is%3Aissue> How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/dev/> - User List: u...@wso2.org | Subscribe | Mail Archive <http://mail.wso2.org/mailarchive/architecture/> Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Tooling through the public API Manager Tooling Git Repo. <https://github.com/wso2/product-apim-tooling/issues> If it is a security issue then it must be reported to secur...@wso2.com, not as a GitHub issue. We strongly advise following the security vulnerability reporting guide <https://docs.wso2.com/display/Security/WSO2+Security+Vulnerability+Reporting+Guidelines> when reporting security issues. *-- The WSO2 API Manager Team --* -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [DEV] [VOTE] Release WSO2 API Microgateway 3.0.1 RC3
t; >>>>>>> >>>>>>> Documentation: https://docs.wso2.com/display/MG301/ >>>>>>> >>>>>>> Best Regards, >>>>>>> WSO2 API Manager Team >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> *Rajith Roshan* | Associate Technical Lead | WSO2 Inc. >>>>>> (m) +94-717-064-214 | (e) raji...@wso2.com >>>>>> >>>>>> <https://wso2.com/signature> >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> *Praminda Jayawardana* | Senior Software Engineer | WSO2 Inc. >>>>> (m) +94 (0) 716 590918 | (e) prami...@wso2.com >>>>> GET INTEGRATION AGILE >>>>> Integration Agility for Digitally Driven Business >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> >>>> *Menaka Jayawardena* >>>> Senior Software Engineer | WSO2 Inc. >>>> +94 71 350 5470 | +94 76 717 2511 | men...@wso2.com >>>> >>>> <https://wso2.com/signature> >>>> >>>> ___ >>>> Architecture mailing list >>>> architect...@wso2.org >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>> >>> >>> -- >>> Malintha Amarasinghe >>> *WSO2, Inc. - lean | enterprise | middleware* >>> http://wso2.com/ >>> >>> Mobile : +94 712383306 >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> >> -- >> *Hasunie Adikari* >> Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> blog http://hasuniea.blogspot.com | https://medium.com/@Hasunie/ >> Mobile:+94713095876 >> >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > *Viraj Salaka Gamage* | Software Engineer | WSO2 Inc. > +94 710 618 178 > GET INTEGRATION AGILE > Integration Agility for Digitally Driven Business > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Native API Management support for K8s
Hi all, This thread is to initiate the discussion on providing native API Management support for K8s. The intention of this is to make convenient managing APIs in Kubernetes cluster in a cloud-native manner. This email contains the basic design and flow of the process. Following diagram depicts the overview design of the intended implementation. [image: apimoperatos.jpg] *Design overview* WSO2 API Microgateway[1] will be used and backed for managing APIs ( proxying, throttling, security etc). To cater to the above, four custom resource definitions(CRDs) for K8s cluster will be introduced as mentioned below. 1. API Kind - This will be deploying the API with the user given swagger definition. It will pass the swagger definition to the micro-gateway toolkit with the API name so that the given API will be exposed in the Kubernetes cluster via micro-gateway. 2. Endpoint Kind - The endpoint can be given either as an endpoint URL or docker image. If it is defined as a docker image, the controller will create k8s artefacts (deployments/services) for the endpoint using the details mentioned in the endpoint kind. This will be referred from the API swagger definition using vendor extensions. 3. Rate-limiting Kind - Contains the throttle policy details which would ultimately create a policy.yaml file. This will generate the necessary policies source files once mounted to the micro-gateway project(toolkit). 4. Security Kind - It defines the API security. Accept user credentials and certificates followed by adding credentials to the micro-gateway config file and add the certificates to the micro-gateway trust store. After applying all the above resources including the API operator in k8s cluster, an API can be exposed in a k8s cluster with a simple command as "*kubectl add api --from-file=".* The ultimate result would be k8s deployments using the micro-gateway docker image exposing the service for the given API definitions. Once the final micro-gateway docker image is built, it will be pushed to a docker registry so that it can be used across different environments (QA, Dev, Pre-prod, Production etc) and spin up necessary APIs in the k8s cluster efficiently. Since docker images are built inside k8s cluster, we are using a Google container tool "Kaniko" [1]. Kaniko builds container images from a Dockerfile, inside a container of a Kubernetes cluster. *Implementation details of APIM Controller/operator:* 1. The operator reads the swagger definition from the config map and resolves if it refers to other kinds( such as endpoints/security etc). 2. The resolved swagger definition will be mounted to the kaniko[2] pod along with the other necessary artefacts (micro-gw.cong, policies.yaml, certificates) to generate the micro-gateway image(micro-gateway executable with micro-gateway runtime). 3. Kaniko container uses Dockerfile, build context etc to build the final docker image and pushes to a destination registry. - Dockerfile which is used in Kaniko will be a multi-staged docker file. - Stage 1: - Run the micro-gateway toolkit and generate the micro-gateway executable file - Stage 2: - Pass the generated executable file to the micro-gateway runtime and start the service - The created docker image's name would be in the format of */:* 4. If the relevant docker image is already available in the registry, the operator would avoid running the Kaniko Pod. Instead, it will create the k8s deployments and services using the relevant available docker images. [1] https://wso2.com/api-management/api-microgateway/ [2] https://github.com/GoogleContainerTools/kaniko/blob/master/README.md Thanks, DinushaD -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] upgrading to analytics 6.4.0
stgres databases. >>> Now I see there are more then 10 databases preconfigured in the default >>> analytics 6.4.0 config (conf/dashboard/deployment.yaml >>> and conf/worker/deployment.yaml). >>> Well, … this is suggesting me lot of questions. >>> >>> First of all, is it still recommended (like it is for ESB databases) >>> to do *not* use local H2 databases in production environment ? >>> This question comes because the 6.4.0 analytics seems to me to be used >>> as it is, out of the box, lot of DBs and no documentation for a any >>> configuration as it was for previous versions. >>> >> Yes. We still recommend NOT to use the embedded H2 databases. >> >>> >>> If we need to create external DBs for all the stuffs, what exactly are >>> each DB for ? >>> >> Please refer Configuring Datasources >> <https://docs.wso2.com/display/SP430/Configuring+Datasources> >> >>> >>> Is there any migration tool and/or documentation about migrating from >>> analytics 6.3.0 to 6.4.0 ? ( >>> https://docs.wso2.com/display/EI640/Upgrading+from+WSO2+EI+6.3.0 does't >>> talk about that) >>> >> >> >>> Any matching between former 4 DBs and the 6.4.0 new ones ? >>> >> ANALYTICS_CARBON_DB - In-order to use/ migrate this database the previous >> analytics, please answer the following questions >> >> Seems, you are not using a usr-mgt database, Do you have add additional >> users? If not its not necessary to migrate the carbon db. You just can move >> on with a new db >> >> ANALYTICS_METRICS_DB - Metrics values stored in the DB depends on the >> node that we run. But IMO since this is a new version of the product, there >> is no use of migrating the older metrics data into the new one. >> ANALYTICS_EVENT_STORE_DB and ANALYTICS_PROCESSED_DATA_STORE_DB - This is >> replaced by aggregation tables. And aggregation >> <https://wso2.github.io/siddhi/documentation/siddhi-4.0/#aggregate-function> >> will be done via Siddhi <https://wso2.github.io/siddhi/> >> >>> >>> Is there a way to keep (transfer into 6.4.0) datas we collected with >>> previous analytics version ? >>> >> We are currently looking at several methods in-order to migrate the >> ANALYTICS_EVENT_STORE_DB and ANALYTICS_PROCESSED_DATA_STORE_DB data and we >> will update you on that regard. >> >>> >>> Thanks, >>> Bernard >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> >> Best Regards, >> Ramindu. >> -- >> *Ramindu De Silva* >> Senior Software Engineer >> WSO2 Inc.: http://wso2.com >> lean.enterprise.middleware >> >> email: ramin...@wso2.com >> mob: +94 719678895 >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- *Dinusha Dissanayake* | Senior Software Engineer | WSO2 Inc (m) +94 71 293 9439 | (e) dinus...@wso2.com <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API statistics
Hi Shibsankar, Yes. You need to download WSO2 APIM Analytics server. Please refer to the docuementation[1] to configure analytics. It will contain the information for you to download the WSO2 APIM analytics server as well. After downloading the Analytics server, you can simply follow the steps mentioned in the document to enable the analytics for API Manager. After that, once you invoke the APIs, after a few minutes the relevant data will get populated in the stat DB and you can see them via publisher and store portals. [1] https://docs.wso2.com/display/AM250/Configuring+APIM+Analytics Thanks, DinushaD On Wed, Sep 19, 2018 at 2:47 PM shibsankar wrote: > Also when I click Analytics and API usage menu I get this screen > > What I should do to get the analytics? > > On Wed, Sep 19, 2018, 2:38 PM shibsankar wrote: > >> Checked that link. It talks about APIM configuration first. >> >> I am not clear, do I need to install any package for this? >> >> Or >> >> Do I need to set the Enabled property under Analytics to true in >> api-manager.xml only? >> >> On Wed, Sep 19, 2018, 12:52 PM Dinusha Dissanayake >> wrote: >> >>> Hi Shibsankar, >>> >>> Please follow the documentation below[1] to understand API statistics. >>> It contains the details of the available visualizations/graphs. >>> >>> [1] https://docs.wso2.com/display/AM250/Viewing+API+Statistics >>> >>> Thanks, >>> DinushaD >>> >>> On Wed, Sep 19, 2018 at 12:45 PM shibsankar wrote: >>> >>>> Is there any way to find wso2 hit statistics , request/response etc >>>> when I call my API? >>>> >>>> Any UI or graph in wso2 which shows that information? >>>> _______ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>> >>> >>> -- >>> Dinusha Dissanayake >>> Software Engineer >>> WSO2 Inc >>> Mobile: +94712939439 >>> <https://wso2.com/signature> >>> >> -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API statistics
Hi Shibsankar, Please follow the documentation below[1] to understand API statistics. It contains the details of the available visualizations/graphs. [1] https://docs.wso2.com/display/AM250/Viewing+API+Statistics Thanks, DinushaD On Wed, Sep 19, 2018 at 12:45 PM shibsankar wrote: > Is there any way to find wso2 hit statistics , request/response etc when I > call my API? > > Any UI or graph in wso2 which shows that information? > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] Dev][VOTE] Release of WSO2 API Manager 2.6.0 RC3
>> Tested the following. >>>>>>>> >>>>>>>> Basic API creation by creator role >>>>>>>> Publishing by publisher role >>>>>>>> User sign up >>>>>>>> Creation and invocation of SOAP APIs >>>>>>>> Microgateway VM mode >>>>>>>> Microgateway docker mode >>>>>>>> >>>>>>>> [+] Stable - go ahead and release >>>>>>>> >>>>>>>> Thanks, >>>>>>>> NuwanD. >>>>>>>> >>>>>>>> On Sat, Sep 15, 2018 at 10:34 AM Chamila Adhikarinayake < >>>>>>>> chami...@wso2.com> wrote: >>>>>>>> >>>>>>>>> Microgateway RC3 can be found in >>>>>>>>> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc3 >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks >>>>>>>>> Chamila >>>>>>>>> >>>>>>>>> On Sat, Sep 15, 2018 at 7:04 AM, Chamila Adhikarinayake < >>>>>>>>> chami...@wso2.com> wrote: >>>>>>>>> >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> We are pleased to announce the third release candidate of >>>>>>>>>> WSO2 API Manager 2.6.0. >>>>>>>>>> >>>>>>>>>> This release fixes the following issues. >>>>>>>>>> >>>>>>>>>> Fixes : carbon-apimgt >>>>>>>>>> <https://github.com/wso2/carbon-apimgt/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15+-label%3A%22APIM+3.0.0%22> >>>>>>>>>> Fixes : product-apim >>>>>>>>>> <https://github.com/wso2/product-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15+-label%3A%223.0.0%22> >>>>>>>>>> Fixes : analytics-apim >>>>>>>>>> <https://github.com/wso2/analytics-apim/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15> >>>>>>>>>> Fixes : product-microgateway >>>>>>>>>> <https://github.com/wso2/product-microgateway/issues?utf8=%E2%9C%93=is%3Aclosed+closed%3A2018-07-16..2018-09-15> >>>>>>>>>> >>>>>>>>>> Source and Distribution, >>>>>>>>>>- Runtime : >>>>>>>>>> https://github.com/wso2/product-apim/releases/tag/v2.6.0-rc3 >>>>>>>>>>- Analytics : >>>>>>>>>> https://github.com/wso2/analytics-apim/releases/tag/v2.6.0-rc3 >>>>>>>>>>- Tooling : >>>>>>>>>> https://github.com/wso2/devstudio-tooling-apim/releases/tag/v2.6.0-rc1 >>>>>>>>>>- Microgateway : >>>>>>>>>> https://github.com/wso2/product-microgateway/releases/tag/v2.6.0-rc2 >>>>>>>>>> >>>>>>>>>> Please download, test the product and vote. >>>>>>>>>> >>>>>>>>>> [+] Stable - go ahead and release >>>>>>>>>> [-] Broken - do not release (explain why) >>>>>>>>>> >>>>>>>>>> Thanks, >>>>>>>>>> ~ WSO2 API Manager Team ~ >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>>>>> Regards, >>>>>>>>>> Chamila Adhikarinayake >>>>>>>>>> Associate Technical Lead >>>>>>>>>> WSO2, Inc. >>>>>>>>>> Mobile - +94712346437 >>>>>>>>>> Email - chami...@wso2.com >>>>>>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> Regards, >>>>>>>>> Chamila Adhikarinayake >>>>>>>>> Associate Technical Lead >>>>>>>>> WSO2, Inc. >>>>>>>>> Mobile - +94712346437 >>>>>>>>> Email - chami...@wso2.com >>>>>>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>>>>> *Nuwan Dias* | Director | WSO2 Inc. >>>>>>>> (m) +94 777 775 729 | (e) nuw...@wso2.com >>>>>>>> [image: Signature.jpg] >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> *Sanjeewa Malalgoda* >>>>>>> Software Architect | Associate Director, Engineering WSO2 Inc. >>>>>>> (m) +94 712933253 | (e) sanje...@wso2.com >>>>>>> >>>>>>> GET INTEGRATION AGILE <https://wso2.com/signature> >>>>>>> Integration Agility for Digitally Driven Business >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Rajith Roshan >>>>>> Senior Software Engineer, WSO2 Inc. >>>>>> Mobile: +94-7 <%2B94-71-554-8430>17-064-214 >>>>>> >>>>>> ___ >>>>>> Architecture mailing list >>>>>> architect...@wso2.org >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> Regards, >>>>> Chamila Adhikarinayake >>>>> Associate Technical Lead >>>>> WSO2, Inc. >>>>> Mobile - +94712346437 >>>>> Email - chami...@wso2.com >>>>> Blog - http://helpfromadhi.blogspot.com/ >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards >>>> >>>> *Chaminda Jayawardena* >>>> WSO2 Inc. - http://wso2.com >>>> +94-77-7725234 >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> *Naduni Pamudika* >>> Software Engineer | WSO2 >>> >>> Mobile: +94 719 143658 <+94%2071%20914%203658> >>> LinkedIn: https://lk.linkedin.com/in/naduni-pamudika >>> Blog: https://medium.com/@naduni_pamudika >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> ___ >>> Architecture mailing list >>> architect...@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >> >> >> -- >> >> *Tharindu Dharmarathna*Associate Technical Lead >> WSO2 Inc.; http://wso2.com >> lean.enterprise.middleware >> >> mobile: *+94779109091* >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > Vithursa Mahendrarajah > Software Engineer > WSO2 Inc. - http ://wso2.com > Mobile : +947*66695643* <+94%2077%20819%201300> > > > * <http://wso2.com/signature> <http://wso2.com/signature> > <http://wso2.com/signature>* > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Caching and Intermediate Request Handling
Hi Amitha, > One-to-many mapping from one in-sequence to many back-end APIs > > To me, this sounds like a dynamic endpoint[1]. You can achieve this via > in-sequence. > You can use default endpoint, which will send the request to the endpoint > in "To" header. You can create "To" header during the mediation. Following > is a example scenario. > > > Can the to header used to call multiple back-ends simultaneously? > > Say I have multiple back-ends. Once a user sends a request, API Manager > calls the said back-ends simultaneously (sequentially or in parallel - > requirement is to send call multiple back-ends in a single request) and > collect responses from each back-end and compose a response to be sent. > > Example: > > A hotel chain has multiple back-ends running for multiple purposes. If a > web UI requests details of a destination, say the request is sent to, 1. a > back-end for analytics purposes - no response is received, 2. receive > weather data of the location 3. booking back-end. > > Response: Booking related information of the destination including the > weather data in a single response. Say the response is prepared at the > out-sequence. > > How can such a scenario be handled? > You can use Aggregate mediator for this purpose. You can refer the docuementation for aggregrate mediatror[1] and sample scenario[2]which I have mentioned the links below. [1] https://docs.wso2.com/display/EI600/Aggregate+Mediator [2] https://docs.wso2.com/display/EI600/Sample+62%3A+Routing+a+ Message+to+a+Dynamic+List+of+Recipients+and+Aggregating+Responses -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Caching and Intermediate Request Handling
Hi Amitha, > >1. Request not passing through back-end - API manager being able to >handle straight-forward requests; i.e in-sequence mediation decides to send >the request directly to out-sequence by without having to expect a response >from the back-end by following an implemented logic. Response is generated >within itself. > > For this, I think you can use Response mediator [1] within the mediation(in-sequence), which will send response back to the client based on your logic. Please refer the documentation [1] for more details. [1] https://docs.wso2.com/display/ESB480/Respond+Mediator Thanks, DinushaD -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] API Manager Caching and Intermediate Request Handling
Hi Amitha,
>
> I am evaluating WSO2 API Manager in order to use it in an application. I
> encountered with the following scenarios and could not find documentation
> on those.
>
>
>1. Caching of request information - in a scenario of not wanting to
>send all the parameters to the back-end, caching those at the in-sequence
>mediation; once the back-end response is received, out-sequence mediation
>uses the cached data to build the response.
>
> You can set the relvant properties to the message context within the
in-sequence you want to use in the outsequence. Following is an example of
setting the values. Here the scope has been set as default(synapse) which
makes this property available in both in and out sequences.
Set the property:
>
>
> Read the property
>1. One-to-many mapping from one in-sequence to many back-end APIs
>
> To me, this sounds like a dynamic endpoint[1]. You can achieve this via
in-sequence.
You can use default endpoint, which will send the request to the endpoint
in "To" header. You can create "To" header during the mediation. Following
is a example scenario.
http://localhost:{port}/services/',
'Test')"/>
[1] https://docs.wso2.com/display/AM250/Working+with+Endpoints
Thanks,
DinushaD
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager Microgateway Toolkit 2.5.0 RC2
Hi all, Tested the below 1. Test analytics filter by enabling and disabling. 2. Test uploading task by enabling and disabling. 3. Test request, execution and response data generation in successful invocation. 4. Test throttle data generation in throttled out scenarios. 5. Test with fault backend to generate fault invocation data. 6. Tested if file rotation happen in defined time span. 7. Tested if uploading task happen in defined time span. No blockers found. [+] Stable - go ahead & release. Thanks. On Sat, Jul 7, 2018 at 4:03 AM, Rajith Roshan wrote: > Hi All, > > Tested below scenarios. > > >1. Default version of API >2. Subscription validation for jwt token >3. Subscription validation for oauth2 token >4. Scope validation for oauth2 token >5. Scope validation for jwt token >6. Basic ballerina service generation for APIs > > No blockers found. > > [+] Stable - go ahead and release > > Thanks! > > > On Fri, Jul 6, 2018 at 1:03 PM Malintha Amarasinghe > wrote: > >> Tested below scenarios: >> >> 1. Testing API invocation with an OAuth2 access token and JWT token >> generated from Store. >> 2. Response caching. >> 3. Disabling HTTP/HTTPs transports per API (Publisher manage page). >> 4. Testing code generation and API invocation with wildcard resources, >> path, and query parameter combinations and check whether params are >> properly sent to backend upon invocation. >> 5. Tested load balanced and failover endpoints. >> >> [+] Stable - go ahead and release >> >> Thanks! >> >> >> On Fri, Jul 6, 2018 at 7:41 PM, Rukshan Premathunga >> wrote: >> >>> Hi All, >>> >>> We are pleased to announce the second release candidate of WSO2 API >>> Manager Microgateway Toolkit 2.5.0. >>> >>> This release fixes the following issues. >>> >>>- Fixes: product-microgateway >>> >>> <https://github.com/wso2/product-microgateway/issues?q=is%3Aissue+milestone%3A2.5.0+is%3Aclosed> >>> >>> Distribution : >>> *https://github.com/wso2/product-microgateway/releases/download/v2.5.0-rc2/wso2am-micro-gw-toolkit-2.5.0-RC2.zip >>> <https://github.com/wso2/product-microgateway/releases/download/v2.5.0-rc2/wso2am-micro-gw-toolkit-2.5.0-RC2.zip>* >>> >>> Please download, test the product and vote. >>> >>> [+] Stable - go ahead and release >>> [-] Broken - do not release (explain why) >>> >>> Thanks, >>> WSO2 API Manager Team >>> >>> -- >>> Rukshan Chathuranga. >>> WSO2, Inc. >>> +94711822074 >>> >> >> >> >> -- >> Malintha Amarasinghe >> *WSO2, Inc. - lean | enterprise | middleware* >> http://wso2.com/ >> >> Mobile : +94 712383306 >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > > -- > Rajith Roshan > Senior Software Engineer, WSO2 Inc. > Mobile: +94-717-064-214 > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [APIM] Error when trying to setup micro-gw
Hi Dinusha, Can you check if micro-gw-resources/projects//target/ contains the relevant distribution and zip with the corresponding lable name? I got the same error, which I think is expected ( please correct me if I am wrong), and yet I could see the relevant artifacts and run them without any issue. Thanks, DinushaD On Tue, Jun 26, 2018 at 11:13 AM, Dinusha Senanayaka wrote: > Hi APIM team, > > Executed following command as per doc [2] to build generated source and > got error [1]. Do we need to include any libraries ? (using micro-gw alpha > release). > > micro-gw build -l marketing_store > > > [1] could not find package wso2/gateway:* > > [2] https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway# > ConfiguringtheAPIMicrogateway-GeneratingaMicrogatewaydistribution > > Regards, > Dinusha > > -- > Dinusha Dilrukshi > Technical Lead > WSO2 Inc.: http://wso2.com/ > Mobile: +94764069991 > Blog: http://dinushasblog.blogspot.com/ > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [VOTE] Release of WSO2 API Manager 2.5.0 RC4
>>>>> WSO2 API Manager Team. >>>>> >>>>> -- >>>>> Chamin Dias >>>>> Mobile : 0716097455 >>>>> Email : cham...@wso2.com >>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Krishan Wijesena* >>>> Software Engineer | WSO2 >>>> >>>> Email : krish...@wso2.com >>>> Mobile : +94776219923 >>>> WSO2 Inc : http://wso2.com >>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>> >>> >>> >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : cham...@wso2.com >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Thanks & Regards, >> >> *Chamalee De Silva* >> Senior Software Engineer >> *WS**O2* Inc. :http://wso2.com/ >> >> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> > > > -- > *Tharika Madurapperuma* > Software Engineer | WSO2, Inc. > > Email : thar...@wso2.com > Mobile : +94777875624 > Web : http://wso2.com > > <http://wso2.com/signature> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] [VOTE] Release of WSO2 API Manager 2.5.0 RC3
;>> WSO2 API Manager Team >>>>> >>>>> -- >>>>> Chamin Dias >>>>> Mobile : 0716097455 >>>>> Email : cham...@wso2.com >>>>> LinkedIn : https://www.linkedin.com/in/chamindias >>>>> >>>>> >>>>> ___________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Thanks & Regards, >>>> >>>> *Chamalee De Silva* >>>> Senior Software Engineer >>>> *WS**O2* Inc. :http://wso2.com/ >>>> >>>> Office :- *+94 11 2145345 <%2B94%2011%202145345>* >>>> mobile :- *+94 7 <%2B94%2077%202782039>1 4315942* >>>> >>>> >>> >>> >>> -- >>> Chamin Dias >>> Mobile : 0716097455 >>> Email : cham...@wso2.com >>> LinkedIn : https://www.linkedin.com/in/chamindias >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Vithursa Mahendrarajah >> Software Engineer >> WSO2 Inc. - http ://wso2.com >> Mobile : +947*66695643* <+94%2077%20819%201300> >> >> >> * <http://wso2.com/signature> <http://wso2.com/signature> >> <http://wso2.com/signature>* >> ___ >> Architecture mailing list >> architect...@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> > > ___ > Architecture mailing list > architect...@wso2.org > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] APIM CLI simplify endpoint url configs
Hi Rukshan, Would we need to consider here the uploading endpoint of the analytics data files as well? Currently we are planing to include it in conf file. Thanks, DinushaD. On Mon, Jun 18, 2018 at 2:37 PM, Rukshan Premathunga wrote: > Hi, > > Here the additional details user need to provide as argument when setup > CLI tool. > >- Publisher Endpoint >- Registration Endpoint >- Admin Endpoint >- Token Endpoint >- Trust Store path >- Trust Store password > > > From them, Publisher, Registration, Admin and Token endpoints hostname > can be same. In such cases we can introduce a command argument --*URL. * If > URL is provided those urls are derived from that. In case if those apps are > in diffrent host, user need to edit them in default config file. Since this > a one time task and not likely to change much, i think it is fine. > Since all of these configs are mandatory we maintain some default values. > When user enter setup command, if those configs are not provided, prompt > user to enter values. If user didn't input any values default values are > use. Once all the setup execution is complete succesfully, user input save > to the config file and use next time onward. > > Here the few examples flow, ex:1 show *setup* command with all the > mandatory arguments and ex: 2 show without mandatory arguments. Hence > ex:2 prompt them from user. > > 1) > $ ./micro-gw *setup* --user amuser --*password* pass --label account -- > *url* https://localhost:9443/ --*path* /home/user/workspace --*truststore* > path/to/truststore --*truststorePass* password > $ Completed > > 2) > $ ./micro-gw *setup* --user amuser --*password* pass --*label* account -- > *path* /home/user/workspace > $ Enter *url* [ default https://localhost:9443/ ] : > https://apim.wso2.com:9443/ > $ Enter *truststore* [ default path/to/truststore ] : different/path/to/ > truststore > $ Enter *truststorePass* [ use default? ] : password > $ Completed > > > Any suggestions? > > Thanks and Regards > > > > On Mon, Jun 18, 2018 at 11:18 AM, Rukshan Premathunga > wrote: > >> I guess you are referring to the Microgateway CLI and not the APIM CLI. >> >> Yes. It should be Microgateway CLI >> >> >> On Mon, Jun 18, 2018 at 11:15 AM, Nuwan Dias wrote: >> >>> I guess you are referring to the Microgateway CLI and not the APIM CLI. >>> >>> On Mon, Jun 18, 2018 at 11:11 AM, Rukshan Premathunga >>> wrote: >>> >>>> Hi All, >>>> >>>> Currently CLI auto generate endpoints from defautl values and user have >>>> to edit it in order to work if endpoints are diffrent. As a solution we >>>> thought to provide urls as arguments for setup command. >>>> But here we have 4 endpoints(store, publisher, admin and token) to get >>>> as arguments. But making all of them as mandatory, user experience may get >>>> reduce, So we need to have a mechanism to derive them. >>>> >>>> One option is to use one host for apps in same node(store, pub, admin). >>>> If it is changed, provide the optional arguments to override them. >>>> >>>> So can you also share some idea please. >>>> >>>> Thanks and Regards >>>> -- >>>> >>>> Rukshan Chathuranga. >>>> WSO2, Inc. >>>> +94711822074 >>>> >>> >>> >>> >>> -- >>> Nuwan Dias >>> >>> Software Architect - WSO2, Inc. http://wso2.com >>> email : nuw...@wso2.com >>> Phone : +94 777 775 729 >>> >> >> >> >> -- >> Rukshan Chathuranga. >> Software Engineer. >> WSO2, Inc. >> +94711822074 >> > > > > -- > Rukshan Chathuranga. > Software Engineer. > WSO2, Inc. > +94711822074 > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 and LDAP
Hi Shib,
Redirection URL should be the url of the OAuth application requesting the
access token.
Following document[1] contains an example explaining an application (WSO2
playground) obtaining the access token with implicit grant type.
Please go through the document for further details.
[1] https://docs.wso2.com/display/AM210/Implicit+Grant
Thanks,
DinushaD
On Mon, Jun 11, 2018 at 9:49 PM, shibsankar wrote:
> Okay. I guess there is no user validation APIM API then. No problem.
>
>
> I would like to try your suggestion
>
> *" ...I think it would be best to use implicit grant type for this
> purpose. Basically, when someone wants to login to the your application
> they will be redirected to APIM which they will prompt the login screen..."*
>
> What is the APIM redirection url? Is it this URL ?https://
> :9443/carbon/admin/index.jsp
> or
> some other url?
>
>
>
> *"...After successful authentication, they will obtain a token and
> redirect back to your application. "*
>
> How to configure here to obtain token and redirect back to my application?
> Could you please post configuration steps for this part.
>
>
> Regards
> Shib
>
>
>
>
>
>
>
>
>
>
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> Virus-free.
> www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
> <#m_590248786326008946_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Mon, Jun 11, 2018 at 5:36 PM, shibsankar wrote:
>
>> Your suggestion is good,
>>
>> However, I don't want to redirect my application to APIM and prompt the
>> login screen.
>>
>> Rather, *as an alternative*, I'd like to invoke user validation APIM
>> API ( *exist ?*) for authentication. Do we have user validation
>> APIM API?
>>
>>
>>
>> *something like this ...*
>>
>>
>> // invoke APIM LDAP user authentication API
>>
>> *// Request JSON payload data:*
>>
>> {
>> "credentials": {
>> "username": "userx",
>> "password": "mypass"
>> }
>> }
>>
>> *// Response data:*
>>
>> {
>> "response": {
>> "status": "true"
>> }
>> }
>>
>>
>> Do we have similar such facility?
>>
>> Regards
>> Shib
>>
>>
>>
>> On Mon, Jun 11, 2018 at 5:01 PM, Harsha Kumara wrote:
>>
>>>
>>>
>>> On Mon, Jun 11, 2018 at 2:57 PM shibsankar wrote:
>>>
>>>> Let me explain in detail what I plan to achieve.
>>>>
>>>>
>>>> Step 1: User will login to my web application (angular js front end).
>>>>
>>>> *Step 2: I want to validate these users against LDAP User Store
>>>> configured in WSO2*
>>>>
>>> I think it would be best to use implict grant type for this purpose.
>>> Basically when someone want to login to the your application they will be
>>> redirect to APIM which they will prompt the login screen. After successful
>>> authentication they will obtain a token and redirect back to your
>>> application.
>>>
>>>> Step 3: Once these users are authenticated, I plan to invoke token API
>>>> with password grant to obtain an OAuth 2 token.
>>>>
>>>> Step 4: Once I receive the OAuth2 token, I would invoke APIM to get a
>>>> response from backend rest API.
>>>>
>>>>
>>>> I'm at *Step 2. * Can we authenticate logged in users against WSO2
>>>> LDAP user store? whats the curl command for this?
>>>>
>>>> Regards
>>>> Shib
>>>>
>>>>
>>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>> Virus-free.
>>>> www.avast.com
>>>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail>
>>>> <#m_590248786326008946_m_-2480271623769723822_m_8422013387296300243_m_4987511863897348861_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>>
>>>> On Mon, Jun 11, 2018 at 2:34 PM, Dinusha Dissanayake >>> > wrote:
>>>>
>>>>> Hi Shib,
>>>>>
>>>>> I guess you are authenticating the user to perform certain operations
>>>>> in APIM through rest APIs ?.
>>>>> Please refer the documentation[1] which includes de
Re: [Dev] WSO2 and LDAP
Hi Shib, I guess you are authenticating the user to perform certain operations in APIM through rest APIs ?. Please refer the documentation[1] which includes details of our REST APIs (store/publisher and admin portal). There it has explained what you have to do to get the necessary access tokens before invocation those rest APIs. Please refer the "Getting started" section of any of the subsections (eg [2] ) for necessary details. [1] https://docs.wso2.com/display/AM210/RESTful+APIs [2] https://docs.wso2.com/display/AM210/apidocs/store/#guide On Mon, Jun 11, 2018 at 2:21 PM, shibsankar wrote: > I have configured LDAP as a User Store in WSO2 (*screenshot attached*). > This is okay. > > Now I plan to send an LDAP user id & password through *Postman *to WSO2 > server to verify successful authentication. > > Could you please tell which WSO2 URL to invoke and what parameters to pass > through *Postman* to test successful authentication? > > Regards > Shib > > > On Mon, Jun 11, 2018 at 12:46 PM, Dinusha Dissanayake > wrote: > >> Hi Shib, >> >> Yes you can. But you may need to configure LDAP as a user store first. >> >> Please follow the document[1] to configure use stores. >> >> [1] https://docs.wso2.com/display/AM210/Configuring+User+Stores >> >> Thanks, >> DinushaD >> >> On Mon, Jun 11, 2018 at 12:42 PM, shibsankar wrote: >> >>> Hi, >>> I have an LDAP with user credentials. >>> >>> Can I use LDAP user credentials as password grant to generating Oauth 2 >>> token? >>> >>> >>> *Please see the screenshot attached.* >>> >>> Regards >>> Shib >>> >>> >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> Virus-free. >>> www.avast.com >>> <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> >>> <#m_4045808147317074170_m_3545910350936696630_m_-7733728954474898531_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >>> >> >> >> >> -- >> Dinusha Dissanayake >> Software Engineer >> WSO2 Inc >> Mobile: +94712939439 >> <https://wso2.com/signature> >> > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 and LDAP
Hi Shib, Yes you can. But you may need to configure LDAP as a user store first. Please follow the document[1] to configure use stores. [1] https://docs.wso2.com/display/AM210/Configuring+User+Stores Thanks, DinushaD On Mon, Jun 11, 2018 at 12:42 PM, shibsankar wrote: > Hi, > I have an LDAP with user credentials. > > Can I use LDAP user credentials as password grant to generating Oauth 2 > token? > > > *Please see the screenshot attached.* > > Regards > Shib > > > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > Virus-free. > www.avast.com > <https://www.avast.com/sig-email?utm_medium=email_source=link_campaign=sig-email_content=webmail> > <#m_-7733728954474898531_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Duplicate Context Value
Hi Shib, Yes. If it doesn't allow you to delete just in case because this API_ID is a foreign key of AM_API_LC_EVENT table, you have to first delete the records in AM_API_LC_EVENT table with those API_IDs and then try deleting entries from AM_API tables. Below are the queries. DELETE FROM AM_API_LC_EVENT WHERE API_ID = 7 AND API_ID = 12; DELETE FROM AM_API WHERE API_ID=7 AND API_ID =12; Regards DinushaD On Fri, Jun 8, 2018 at 4:50 PM, shibsankar wrote: > Yup. I can see the AM_DB now. > > Please see screenshot attached. > > I believe I should delete these records now. This should resolve > duplicate context value issue . right ? > > DELETE FROM AM_API > WHERE API_ID=7 AND API_ID=12; > > Is this okay ? > > Regards > Shib > > > > > > > > On Fri, Jun 8, 2018 at 4:36 PM, Dinusha Dissanayake > wrote: > >> Could you please logout from h2 console and try with >> *jdbc:h2:repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE* as JDBC >> URL. >> Then you'd be able to see the tabls in the AM_DB. >> >> Regards, >> DinushaD >> >> On Fri, Jun 8, 2018 at 4:33 PM, shibsankar wrote: >> >>> Okay. Now I have connected H2 database through Web UI. >>> >>> But I don't see AM_DB , AM_API table there to verify >>> CONTEXT_TEMPLATE as per earlier replies. >>> >>> How to find that ? >>> >>> Please see the screenshot attached. >>> >>> >>> Regards >>> Shib >>> >>> >>> >>> >>> >>> On Fri, Jun 8, 2018 at 2:49 PM, Dinusha Dissanayake >>> wrote: >>> >>>> Hi Shib, >>>> >>>> Yes. By default it is using embedded H2 database even though it is >>>> commented in carbon.xml. >>>> To browse though the database, please follow the instructions given in >>>> above provided document.[1] >>>> [1] https://docs.wso2.com/display/ADMIN44x/Browsing+the+H2+Database. >>>> >>>> Thanks, >>>> DinushaD >>>> >>>> On Fri, Jun 8, 2018 at 2:43 PM, shibsankar wrote: >>>> >>>>> I'm using default installation. I see is >>>>> *commented* in my WSO2/repository/conf/carbon.xml. Does it mean its >>>>> using embedded H2 DB? >>>>> >>>>> carbon.xml attached. >>>>> >>>>> Regards >>>>> Shib >>>>> >>>>> On Fri, Jun 8, 2018 at 2:13 PM, Nirothipan Mehalingam < >>>>> nirothi...@wso2.com> wrote: >>>>> >>>>>> Hi Shib, >>>>>> >>>>>> If you are using embedded H2 DB you may follow >>>>>> https://docs.wso2.com/display/ADMIN44x/Browsing+the+H2+Database. >>>>>> >>>>>> Thanks >>>>>> Nirothipan >>>>>> >>>>>> On Fri, Jun 8, 2018 at 2:09 PM, shibsankar wrote: >>>>>> >>>>>>> How do I connect to this DB and view the rows of the mentioned >>>>>>> table? Can it be viewed from API management web-UI? >>>>>>> >>>>>>> Regards >>>>>>> Shib >>>>>>> >>>>>>> On Fri, Jun 8, 2018 at 1:50 PM, Dinusha Dissanayake < >>>>>>> dinus...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Shib, >>>>>>>> >>>>>>>> Probably there should be an database entry of the same "context" >>>>>>>> you are defining here. As above replies explain, this could be due to >>>>>>>> partially deleted APIs. >>>>>>>> Could you please check AM_API table in AM_DB and see whether there >>>>>>>> is a CONTEXT_TEMPLATE with the same context you are trying to define >>>>>>>> here? >>>>>>>> >>>>>>>> Thanks, >>>>>>>> DinushaD. >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 8, 2018 at 12:50 PM, shibsankar >>>>>>>> wrote: >>>>>>>> >>>>>>>>> There is no API in publisher application. >>>>>>>>> >>>>>>>>> I'm still getting * Duplicate Context Value *when trying to add a >>>>>>>>> new API in Design page. >>>>>>>>
Re: [Dev] Duplicate Context Value
Could you please logout from h2 console and try with *jdbc:h2:repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE* as JDBC URL. Then you'd be able to see the tabls in the AM_DB. Regards, DinushaD On Fri, Jun 8, 2018 at 4:33 PM, shibsankar wrote: > Okay. Now I have connected H2 database through Web UI. > > But I don't see AM_DB , AM_API table there to verify > CONTEXT_TEMPLATE as per earlier replies. > > How to find that ? > > Please see the screenshot attached. > > > Regards > Shib > > > > > > On Fri, Jun 8, 2018 at 2:49 PM, Dinusha Dissanayake > wrote: > >> Hi Shib, >> >> Yes. By default it is using embedded H2 database even though it is >> commented in carbon.xml. >> To browse though the database, please follow the instructions given in >> above provided document.[1] >> [1] https://docs.wso2.com/display/ADMIN44x/Browsing+the+H2+Database. >> >> Thanks, >> DinushaD >> >> On Fri, Jun 8, 2018 at 2:43 PM, shibsankar wrote: >> >>> I'm using default installation. I see is >>> *commented* in my WSO2/repository/conf/carbon.xml. Does it mean its >>> using embedded H2 DB? >>> >>> carbon.xml attached. >>> >>> Regards >>> Shib >>> >>> On Fri, Jun 8, 2018 at 2:13 PM, Nirothipan Mehalingam < >>> nirothi...@wso2.com> wrote: >>> >>>> Hi Shib, >>>> >>>> If you are using embedded H2 DB you may follow https://docs.wso2.com/d >>>> isplay/ADMIN44x/Browsing+the+H2+Database. >>>> >>>> Thanks >>>> Nirothipan >>>> >>>> On Fri, Jun 8, 2018 at 2:09 PM, shibsankar wrote: >>>> >>>>> How do I connect to this DB and view the rows of the mentioned table? >>>>> Can it be viewed from API management web-UI? >>>>> >>>>> Regards >>>>> Shib >>>>> >>>>> On Fri, Jun 8, 2018 at 1:50 PM, Dinusha Dissanayake >>>> > wrote: >>>>> >>>>>> Hi Shib, >>>>>> >>>>>> Probably there should be an database entry of the same "context" you >>>>>> are defining here. As above replies explain, this could be due to >>>>>> partially >>>>>> deleted APIs. >>>>>> Could you please check AM_API table in AM_DB and see whether there is >>>>>> a CONTEXT_TEMPLATE with the same context you are trying to define here? >>>>>> >>>>>> Thanks, >>>>>> DinushaD. >>>>>> >>>>>> >>>>>> On Fri, Jun 8, 2018 at 12:50 PM, shibsankar wrote: >>>>>> >>>>>>> There is no API in publisher application. >>>>>>> >>>>>>> I'm still getting * Duplicate Context Value *when trying to add a >>>>>>> new API in Design page. >>>>>>> >>>>>>> Please see the screenshot attached. >>>>>>> >>>>>>> Regards >>>>>>> Shib >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 8, 2018 at 10:51 AM, Dushani Wellappili < >>>>>>> dusha...@wso2.com> wrote: >>>>>>> >>>>>>>> Hi Shib, >>>>>>>> >>>>>>>> If you have deleted the API from the management console, then it is >>>>>>>> likely you are getting this issue since deleting api in the >>>>>>>> management console does not delete the whole api. It removes the data >>>>>>>> in >>>>>>>> the registry (meta data). To delete api use publisher application. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> *Dushani Wellappili* >>>>>>>> Software Engineer - WSO2 >>>>>>>> >>>>>>>> Email : dusha...@wso2.com >>>>>>>> Mobile : +94779367571 >>>>>>>> Web : https://wso2.com/ >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Fri, Jun 8, 2018 at 10:01 AM Krishan Wijesena >>>>>>>> wrote: >>>>>>>> >>>>
Re: [Dev] Duplicate Context Value
Hi Shib, Yes. By default it is using embedded H2 database even though it is commented in carbon.xml. To browse though the database, please follow the instructions given in above provided document.[1] [1] https://docs.wso2.com/display/ADMIN44x/Browsing+the+H2+Database. Thanks, DinushaD On Fri, Jun 8, 2018 at 2:43 PM, shibsankar wrote: > I'm using default installation. I see is > *commented* in my WSO2/repository/conf/carbon.xml. Does it mean its > using embedded H2 DB? > > carbon.xml attached. > > Regards > Shib > > On Fri, Jun 8, 2018 at 2:13 PM, Nirothipan Mehalingam > wrote: > >> Hi Shib, >> >> If you are using embedded H2 DB you may follow https://docs.wso2.com/d >> isplay/ADMIN44x/Browsing+the+H2+Database. >> >> Thanks >> Nirothipan >> >> On Fri, Jun 8, 2018 at 2:09 PM, shibsankar wrote: >> >>> How do I connect to this DB and view the rows of the mentioned table? >>> Can it be viewed from API management web-UI? >>> >>> Regards >>> Shib >>> >>> On Fri, Jun 8, 2018 at 1:50 PM, Dinusha Dissanayake >>> wrote: >>> >>>> Hi Shib, >>>> >>>> Probably there should be an database entry of the same "context" you >>>> are defining here. As above replies explain, this could be due to partially >>>> deleted APIs. >>>> Could you please check AM_API table in AM_DB and see whether there is a >>>> CONTEXT_TEMPLATE with the same context you are trying to define here? >>>> >>>> Thanks, >>>> DinushaD. >>>> >>>> >>>> On Fri, Jun 8, 2018 at 12:50 PM, shibsankar wrote: >>>> >>>>> There is no API in publisher application. >>>>> >>>>> I'm still getting * Duplicate Context Value *when trying to add a new >>>>> API in Design page. >>>>> >>>>> Please see the screenshot attached. >>>>> >>>>> Regards >>>>> Shib >>>>> >>>>> >>>>> On Fri, Jun 8, 2018 at 10:51 AM, Dushani Wellappili >>>> > wrote: >>>>> >>>>>> Hi Shib, >>>>>> >>>>>> If you have deleted the API from the management console, then it is >>>>>> likely you are getting this issue since deleting api in the >>>>>> management console does not delete the whole api. It removes the data in >>>>>> the registry (meta data). To delete api use publisher application. >>>>>> >>>>>> Thank you. >>>>>> >>>>>> Regards, >>>>>> >>>>>> *Dushani Wellappili* >>>>>> Software Engineer - WSO2 >>>>>> >>>>>> Email : dusha...@wso2.com >>>>>> Mobile : +94779367571 >>>>>> Web : https://wso2.com/ >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Fri, Jun 8, 2018 at 10:01 AM Krishan Wijesena >>>>>> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> On Thu, Jun 7, 2018 at 6:50 PM, shibsankar wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> I have *deleted *published API, subscribed API from WSO2. Now >>>>>>>> there is no more API in WSO2. >>>>>>>> You cannot delete API if active subscriptions exists, which >>>>>>>> apporach did you used to delete the API? >>>>>>>> >>>>>>> because basically this error occur if previous API have same >>>>>>> context value and it's partally deleted. >>>>>>> >>>>>>>> >>>>>>>> Restarted the WSO2 server. >>>>>>>> >>>>>>>> >>>>>>>> Now when I try to add a New API , I'm still getting *Duplicate >>>>>>>> context value *in API design page. >>>>>>>> >>>>>>>> Why is this happening? How to fix this? >>>>>>>> >>>>>>>> Please see the screenshot attached. >>>>>>>> >>>>>>>> WSo2 version is 2.1 >>>>>>>> >>>>>>>> Regards >>>>>>>> Shib >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> ___ >>>>>>>> Dev mailing list >>>>>>>> Dev@wso2.org >>>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> >>>>>>> *Krishan Wijesena* >>>>>>> Software Engineer | WSO2 >>>>>>> >>>>>>> Email : krish...@wso2.com >>>>>>> Mobile : +94776219923 >>>>>>> WSO2 Inc : http://wso2.com >>>>>>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>>>>>> ___ >>>>>>> Dev mailing list >>>>>>> Dev@wso2.org >>>>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>>>> >>>>>> >>>>> >>>>> ___ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dinusha Dissanayake >>>> Software Engineer >>>> WSO2 Inc >>>> Mobile: +94712939439 >>>> <https://wso2.com/signature> >>>> >>> >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> >> M.Nirothipan >> Software Engineer >> WSO2 Inc. http://wso2.com , >> *Mobile : +94 77 2172692* >> >> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Duplicate Context Value
Hi Shib, Probably there should be an database entry of the same "context" you are defining here. As above replies explain, this could be due to partially deleted APIs. Could you please check AM_API table in AM_DB and see whether there is a CONTEXT_TEMPLATE with the same context you are trying to define here? Thanks, DinushaD. On Fri, Jun 8, 2018 at 12:50 PM, shibsankar wrote: > There is no API in publisher application. > > I'm still getting * Duplicate Context Value *when trying to add a new > API in Design page. > > Please see the screenshot attached. > > Regards > Shib > > > On Fri, Jun 8, 2018 at 10:51 AM, Dushani Wellappili > wrote: > >> Hi Shib, >> >> If you have deleted the API from the management console, then it is >> likely you are getting this issue since deleting api in the management >> console does not delete the whole api. It removes the data in the registry >> (meta data). To delete api use publisher application. >> >> Thank you. >> >> Regards, >> >> *Dushani Wellappili* >> Software Engineer - WSO2 >> >> Email : dusha...@wso2.com >> Mobile : +94779367571 >> Web : https://wso2.com/ >> >> >> >> >> On Fri, Jun 8, 2018 at 10:01 AM Krishan Wijesena >> wrote: >> >>> >>> >>> On Thu, Jun 7, 2018 at 6:50 PM, shibsankar wrote: >>> >>>> Hi, >>>> I have *deleted *published API, subscribed API from WSO2. Now there >>>> is no more API in WSO2. >>>> You cannot delete API if active subscriptions exists, which apporach >>>> did you used to delete the API? >>>> >>> because basically this error occur if previous API have same context >>> value and it's partally deleted. >>> >>>> >>>> Restarted the WSO2 server. >>>> >>>> >>>> Now when I try to add a New API , I'm still getting *Duplicate >>>> context value *in API design page. >>>> >>>> Why is this happening? How to fix this? >>>> >>>> Please see the screenshot attached. >>>> >>>> WSo2 version is 2.1 >>>> >>>> Regards >>>> Shib >>>> >>>> >>>> >>>> >>>> ___ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> >>> -- >>> >>> *Krishan Wijesena* >>> Software Engineer | WSO2 >>> >>> Email : krish...@wso2.com >>> Mobile : +94776219923 >>> WSO2 Inc : http://wso2.com >>> [image: http://wso2.com/signature] <http://wso2.com/signature> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >> > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] WSO2 Publish & Subscribe
Hi Shib,
When you are creating the API you are using the actual backend URL of the
service as the production endpoint of the API.
But when you are using API Manager, you actual backend is getting proxy and
the service is exposed via APIM gateway with security and throttling
facilities for the API.
Hence now the service is exposed via the APIM gateway.
That is why you see two different URLs in publisher and store production
endpoints.
(http://{host}:8280 and https://{host}:8243 are gateway urls.)
Since you are unable to obtain a response, there seems to be an issue.
Could you please send us the error log in the server when invoking the API.
That would help us to narrow down the issue.
Thanks,
DinushaD.
On Wed, Jun 6, 2018 at 5:43 PM, shibsankar wrote:
> Hi,
>
> *My Objective: *
>
> I have published a service in WSO2 Publish. Now I am trying to test
> this service from WSO2 Store API console.
>
> *Issue : * API console in WSO2 Store not returning result when invoking
> service.
>
>
> *Troubleshooting :*
>
> To my surprise, when I view the published service from WSO2 store, I see
> different production URL of the service than what is in Publishing. What
> has gone wrong ?
>
>
> For your convenience, I'm attaching a screenshot of Publish and Store.
> Could you please help to fix this issue.
>
>
> Regards
> Shib
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [Architecture] WSO2 API Manager 2.5.0-Alpha Released!
Hi all, Link to wso2-am-2.5.0-Alpha distribution is incorrect in the above mail. Please find the correct distribution links below. Distributions wso2am-2.5.0-Alpha.zip <https://github.com/wso2/product-apim/releases/download/v2.5.0-Alpha/wso2am-2.5.0-Alpha.zip> wso2am-analytics-2.5.0-Alpha.zip <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> Sorry for the inconvenience caused. Thanks, DinushaD On Sat, Jun 2, 2018 at 3:34 PM, Dinusha Dissanayake wrote: > The WSO2 API Manager team is pleased to announce the release of version > 2.5.0-Alpha of API Manager. > > WSO2 API Manager is a platform for creating, managing, consuming and > monitoring APIs. It employs proven SOA best practices to solve a wide > range of APImanagement challenges such as API provisioning, API gover > nance, API security and API monitoring. It combines some of the most > powerful and mature components of the WSO2's state-of-the-art Carbon > platform to deliver a smooth and end-to-end API management experience > while catering to both API publisher and API consumer requirements. > > WSO2 API Manager is comprised of several modules. > >- API Provider: Define new APIs and manage them >- API Store: Browse published APIs and subscribe to them >- API Gateway: The underlying API runtime based on WSO2 ESB >- API Key Manager: Performs Key Generation and Key Validation >functionalities >- API Traffic Manager: Performs Rate Limiting of API Requests > > For more information on WSO2 API Manager please visit http://wso2.com > /products/api-manager. Also, take a look at the online product > documentation > <https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>. > > Distributions > wso2am-2.5.0-Alpha.zip > <https://github.com/wso2/product-apim/archive/v2.5.0-Alpha.zip> > wso2am-analytics-2.5.0-Alpha.zip > <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> > > How to Run > >1. Extract the downloaded zip >2. Go to the bin directory in the extracted folder >3. Run the wso2server.sh or wso2server.bat as appropriate >4. Launch a web browser and navigate to https://localhost:9443/publ >isher to access the API publisher webapp >5. Navigate to https://localhost:9443/store to access the API store >6. Navigate to https://localhost:9443/admin to access Admin Portal >7. Use "admin", "admin" as the username and password to login as an >admin > > Bug Fixes And Improvements in 2.5.0-Alpha > >- GitHub *(Product-apim ><https://github.com/wso2/product-apim/milestone/46?closed=1>*) >- GitHub (Carbon-apimgt ><https://github.com/wso2/carbon-apimgt/milestone/20?closed=1>) >- GitHub (Analytics-apim ><https://github.com/wso2/analytics-apim/milestone/6?closed=1>) > > Known Issues > > All the open issues pertaining to WSO2 API Manager are reported at the > following location: > >- GitHub (Product-apim ><https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue>), >(Carbon-apimgt > > <https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>), >(Analytics-apim ><https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) > > How You Can ContributeMailing Lists > > Join our mailing list and correspond with the developers directly. > >- > >Developer List: dev@wso2.org | Subscribe | Mail Archive >- > >User List: u...@wso2.org | Subscribe | Mail Archive > > Reporting Issues > > We encourage you to report issues, documentation faults, and feature > requests regarding WSO2 API Manager through the public API Manager Git > Repo <https://github.com/wso2/product-apim/issues>. > -- The WSO2 API Manager Team -- > > -- > Dinusha Dissanayake > Software Engineer > WSO2 Inc > Mobile: +94712939439 > <https://wso2.com/signature> > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] [Architecture] WSO2 API Manager 2.5.0-Alpha Released!
The WSO2 API Manager team is pleased to announce the release of version 2.5.0-Alpha of API Manager. WSO2 API Manager is a platform for creating, managing, consuming and monitoring APIs. It employs proven SOA best practices to solve a wide range of APImanagement challenges such as API provisioning, API governance, API security and API monitoring. It combines some of the most powerful and mature components of the WSO2's state-of-the-art Carbon platform to deliver a smooth and end-to-end API management experience while catering to both API publisher and API consumer requirements. WSO2 API Manager is comprised of several modules. - API Provider: Define new APIs and manage them - API Store: Browse published APIs and subscribe to them - API Gateway: The underlying API runtime based on WSO2 ESB - API Key Manager: Performs Key Generation and Key Validation functionalities - API Traffic Manager: Performs Rate Limiting of API Requests For more information on WSO2 API Manager please visit http://wso2.com /products/api-manager. Also, take a look at the online product documentation <https://docs.wso2.com/display/AM2XX/WSO2+API+Manager+Documentation>. Distributions wso2am-2.5.0-Alpha.zip <https://github.com/wso2/product-apim/archive/v2.5.0-Alpha.zip> wso2am-analytics-2.5.0-Alpha.zip <https://github.com/wso2/analytics-apim/releases/download/v2.5.0-Alpha/wso2am-analytics-2.5.0-Alpha.zip> How to Run 1. Extract the downloaded zip 2. Go to the bin directory in the extracted folder 3. Run the wso2server.sh or wso2server.bat as appropriate 4. Launch a web browser and navigate to https://localhost:9443/publisher to access the API publisher webapp 5. Navigate to https://localhost:9443/store to access the API store 6. Navigate to https://localhost:9443/admin to access Admin Portal 7. Use "admin", "admin" as the username and password to login as an admin Bug Fixes And Improvements in 2.5.0-Alpha - GitHub *(Product-apim <https://github.com/wso2/product-apim/milestone/46?closed=1>*) - GitHub (Carbon-apimgt <https://github.com/wso2/carbon-apimgt/milestone/20?closed=1>) - GitHub (Analytics-apim <https://github.com/wso2/analytics-apim/milestone/6?closed=1>) Known Issues All the open issues pertaining to WSO2 API Manager are reported at the following location: - GitHub (Product-apim <https://github.com/wso2/product-apim/issues?q=is%3Aopen+is%3Aissue>), ( Carbon-apimgt <https://github.com/wso2/carbon-apimgt/issues?q=is%3Aopen+is%3Aissue+label%3A%22APIM+2.2.0%22>), (Analytics-apim <https://github.com/wso2/analytics-apim/issues?q=is%3Aopen+is%3Aissue>) How You Can ContributeMailing Lists Join our mailing list and correspond with the developers directly. - Developer List: dev@wso2.org | Subscribe | Mail Archive - User List: u...@wso2.org | Subscribe | Mail Archive Reporting Issues We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager through the public API Manager Git Repo <https://github.com/wso2/product-apim/issues>. -- The WSO2 API Manager Team -- -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] passthrough worker thread keep-alive
Hi, I believe you are doing a tuning in the gateway. However the default recommendation of the worker_thread_keepalive_sec is 60 sec. Anyhow, this value should be less than the socket timeout value. You can find more info by following the documentation[1]. [1] https://docs.wso2.com/display/AM210/Tuning+Performance Thanks, DinushaD On Wed, Apr 4, 2018 at 12:13 PM, 김대경 <dkg@gmail.com> wrote: > Hi, > > I'm using wso2am-2.1.0 > > I changed worker_thread_keepalive_sec to 30. > But PassThroughMessageProcessor keep connection over that time. > > I think that connection is close only if target endpoint close connection. > > How can I set the keep-alive timeout? > > Thanks. > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
[Dev] Siddhi long value comparison
Hi all,
I came across with an issue regarding comparing a long value.
My intention was to check if the time difference is greater that 30 days,
and then insert the corresponding values to target stream.
I tested this behavior with APIM Analytics 2.0.0.
However I noticed an unusual behavior.
I have mentioned an example stream below.
*@Import('demoConditions:1.0.0')*
*define stream democondition (timediff long, status bool);*
*@Export('finalStream:1.0.0')*
*define stream finalStream (timediff long, status bool);*
*from democondition[timediff > 30*24*60*60*1000]*
*select timediff, status*
*insert into finalStream;*
Ideally, If I give a value greater than 30*24*60*60*1000 only, values
should be inserted into finalStream.
However I observed even if I give 1 as timeDiff, the values in timeDiff and
status get inserted into finalStream.
When I check the validity of the execution plan through the admin console,
it gets success.
However I replaced the value 30*24*60*60*1000 with 259200 and it
produces and error.
However when I append the "l" add the end (259200l), it got worked.
I tried to use the same with 30*24*60*60*1000 -> 30l*24l*60l*60l*1000l and
I couldn't get it worked since it produce an error while validating the
script.
The reason I am using 30*24*60*60*1000 is because I want the value "30" to
be configured. It should be changed using the template manager.
Please advice on how should I get it into working?
Thanks,
DinushaD.
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439 <+94%2071%20293%209439>
<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] [ESB] SourceHandler I/O error
Hi Senuwa, The reason for this is the certifiacte has not been approved from the browser. So I think this could be fixed when certificate is accepted from browser. Please check if logging to EI from a new tab and trust the cert from the browser would solve this issue Thanks, DinushaD. On Tue, Dec 12, 2017 at 5:33 PM, Dilusha Alphonso <dilu...@wso2.com> wrote: > Hi Senuwan, > > This looks like certificate error.I think this exception is happening when > invoking API in EI. Could you tell how to use curl command when invoking > API? > > Thanks > Dilusha > > On Tue, Dec 12, 2017 at 4:36 PM, Senuwan Withana <senu...@wso2.com> wrote: > >> Hi Team, >> >> I got below error in EI Console. I would like to know why this error is >> happened? >> >> >> [2017-12-12 16:32:11,766] [EI-Core] ERROR - SourceHandler I/O error: >> Received fatal alert: certificate_unknown >> javax.net.ssl.SSLException: Received fatal alert: certificate_unknown >> at sun.security.ssl.Alerts.getSSLException(Alerts.java:208) >> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1666) >> at sun.security.ssl.SSLEngineImpl.fatal(SSLEngineImpl.java:1634) >> at sun.security.ssl.SSLEngineImpl.recvAlert(SSLEngineImpl.java:1800) >> at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1083) >> at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907) >> at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781) >> at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624) >> at org.apache.http.nio.reactor.ssl.SSLIOSession.doUnwrap(SSLIOS >> ession.java:245) >> at org.apache.http.nio.reactor.ssl.SSLIOSession.doHandshake(SSL >> IOSession.java:280) >> at org.apache.http.nio.reactor.ssl.SSLIOSession.isAppInputReady >> (SSLIOSession.java:410) >> at org.apache.http.impl.nio.reactor.AbstractIODispatch.inputRea >> dy(AbstractIODispatch.java:119) >> at org.apache.http.impl.nio.reactor.BaseIOReactor.readable(Base >> IOReactor.java:159) >> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv >> ent(AbstractIOReactor.java:338) >> at org.apache.http.impl.nio.reactor.AbstractIOReactor.processEv >> ents(AbstractIOReactor.java:316) >> at org.apache.http.impl.nio.reactor.AbstractIOReactor.execute(A >> bstractIOReactor.java:277) >> at org.apache.http.impl.nio.reactor.BaseIOReactor.execute(BaseI >> OReactor.java:105) >> at org.apache.http.impl.nio.reactor.AbstractMultiworkerIOReacto >> r$Worker.run(AbstractMultiworkerIOReactor.java:586) >> at java.lang.Thread.run(Thread.java:748) >> >> >> Regards, >> >> *Senuwan Withana* >> Software Engineer - Support Team | WSO2 >> >> Email : senu...@wso2.com >> Mobile: 94773212853 >> Web: http://www.wso2.com >> >> >> >> ___ >> Dev mailing list >> Dev@wso2.org >> http://wso2.org/cgi-bin/mailman/listinfo/dev >> >> > > > -- > > > *Best Regards,Dilusha Alphonso* > > *Software Engineer - Support Team* > > > *WSO2* > *Mobile : * > > *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature] > <http://wso2.com/signature>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <+94%2071%20293%209439> <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Expose the data as webservices
Hi Dilusha, You can also use EI 6.1.1 to create a data service. I hope the following documentation[1] will help. I have tried exposing RDBMS as a data service by following document[2] and I could do that successfully. [1] https://docs.wso2.com/display/EI611/Creating+a+Data+Service+from+Scratch [2] https://docs.wso2.com/display/EI611/Exposing+an+RDBMS+as+a+Data+Service Thanks, DinushaD. On Fri, Dec 8, 2017 at 10:59 AM, Dilusha Alphonso <dilu...@wso2.com> wrote: > No, I didn't observe any exception in the log. > > Thanks > Dilusha > > On Fri, Dec 8, 2017 at 10:16 AM, Chanika Geeganage <chan...@wso2.com> > wrote: > >> Hi Dilusha, >> >> Is there any exception in the log? If so, can you please post it? >> >> Thanks >> >> On Fri, Dec 8, 2017 at 10:03 AM, Dilusha Alphonso <dilu...@wso2.com> >> wrote: >> >>> Hi All, >>> >>> According to my scenario, I have the database. I have to expose that >>> data as web services. For that, I am using WSO2 DSS ( Data Service Server) >>> and followed that step of this document [1]. But I could not deploy service >>> on the server. >>> >>> Can anyone please help on this or suggest If I am doing wrong. >>> >>> [1].https://wso2.com/library/articles/2015/02/how-to-write-a >>> -web-application-backed-by-wso2-middleware-part-1/ >>> >>> >>> Thanks >>> Dilusha >>> >>> >>> >>> >>> *Best Regards,Dilusha Alphonso* >>> >>> *Software Engineer - Support Team* >>> >>> >>> *WSO2* >>> *Mobile : * >>> >>> *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature] >>> <http://wso2.com/signature>* >>> >>> ___ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Best Regards.. >> >> Chanika Geeganage >> +94773522586 <+94%2077%20352%202586> >> WSO2, Inc.; http://wso2.com >> >> > > > -- > > > *Best Regards,Dilusha Alphonso* > > *Software Engineer - Support Team* > > > *WSO2* > *Mobile : * > > *+94766837098 <+94%2076%20683%207098>[image: http://wso2.com/signature] > <http://wso2.com/signature>* > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <+94%2071%20293%209439> <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Error popup on API Manager Worker node.
Hi Senuwan,
If it is not related with port conflicts, you can also refer the following
documentations[1] and check whether you have configured your distributed
deployment correctly.
[1] https://docs.wso2.com/display/AM210/Distributed+
Deployment+of+API+Manager
Thanks,
DinushaD.
On Wed, Dec 6, 2017 at 11:36 AM, Chamin Dias <cham...@wso2.com> wrote:
> Hi,
>
> Can you try out the solution provided in [1] and see? This might occur due
> to a port conflict as Dinusha mentioned.
>
> [1] https://stackoverflow.com/questions/42384492/errors-
> while-starting-wso2-api-manager-2-1-0
>
> On Tue, Dec 5, 2017 at 7:49 PM, Senuwan Withana <senu...@wso2.com> wrote:
>
>> Hi Guys,
>>
>> Thanks for replying. Well I have used below configuration to GW to
>> communicate with the KM
>>
>>
>> https://:9443/services/
>> ${admin.username}
>> ${admin.password}
>> ...
>>
>>
>> Regards,
>>
>> *Senuwan Withana*
>> Software Engineer - Support Team | WSO2
>>
>> Email : senu...@wso2.com
>> Mobile: 94773212853
>> Web: http://www.wso2.com
>>
>>
>>
>> On Tue, Dec 5, 2017 at 5:02 PM, Pubudu Gunatilaka <pubu...@wso2.com>
>> wrote:
>>
>>> Hi Senuwan,
>>>
>>> Make sure you have configured APIKeyValidator in
>>> api-manager.xml pointing to APIM key manager. At the server startup,
>>> gateway nodes retrieve key templates from the KM.
>>>
>>> Thank you!
>>>
>>> On Tue, Dec 5, 2017 at 4:34 PM, Dinusha Dissanayake <dinus...@wso2.com>
>>> wrote:
>>>
>>>> Hi Senuwan,
>>>>
>>>> Could you please check if there is any port conflict? Looks like
>>>> connection has not been established.
>>>>
>>>> Thanks,
>>>> DinushaD.
>>>>
>>>> On Tue, Dec 5, 2017 at 4:09 PM, Senuwan Withana <senu...@wso2.com>
>>>> wrote:
>>>>
>>>>> Hi Team,
>>>>>
>>>>> When I up my API Manager worker node, I got below error. Is there any
>>>>> way to resolve the below error. I have followed up [1] document as
>>>>> reference.
>>>>>
>>>>> [1] - https://docs.wso2.com/display/AM210/Distributed+Deployment
>>>>> +of+the+Gateway#5a69bb14f904452ab5c678035c21178e
>>>>>
>>>>> [2017-12-05 15:46:15,469] ERROR - KeyTemplateRetriever Exception when
>>>>> retrieving throttling data from remote endpoint
>>>>> java.net.ConnectException: Connection refused (Connection refused)
>>>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>>>> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSock
>>>>> etImpl.java:350)
>>>>> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPl
>>>>> ainSocketImpl.java:206)
>>>>> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocket
>>>>> Impl.java:188)
>>>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>>>> at java.net.Socket.connect(Socket.java:589)
>>>>> at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668)
>>>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>>>> ocketFactory.java:522)
>>>>> at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket(SSLS
>>>>> ocketFactory.java:401)
>>>>> at org.apache.http.impl.conn.DefaultClientConnectionOperator.op
>>>>> enConnection(DefaultClientConnectionOperator.java:178)
>>>>> at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoo
>>>>> lEntry.java:144)
>>>>> at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(Abs
>>>>> tractPooledConnAdapter.java:131)
>>>>> at org.apache.http.impl.client.DefaultRequestDirector.tryConnec
>>>>> t(DefaultRequestDirector.java:610)
>>>>> at org.apache.http.impl.client.DefaultRequestDirector.execute(D
>>>>> efaultRequestDirector.java:445)
>>>>> at org.apache.http.impl.client.AbstractHttpClient.doExecute(Abs
>>>>> tractHttpClient.java:863)
>>>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>>>> eableHttpClient.java:82)
>>>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
>>>>> eableHttpClient.java:106)
>>>>> at org.apache.http.impl.client.CloseableHttpClient.execute(Clos
Re: [Dev] Error popup on API Manager Worker node.
Hi Senuwan, Could you please check if there is any port conflict? Looks like connection has not been established. Thanks, DinushaD. On Tue, Dec 5, 2017 at 4:09 PM, Senuwan Withana <senu...@wso2.com> wrote: > Hi Team, > > When I up my API Manager worker node, I got below error. Is there any way > to resolve the below error. I have followed up [1] document as reference. > > [1] - https://docs.wso2.com/display/AM210/Distributed+Deployment > +of+the+Gateway#5a69bb14f904452ab5c678035c21178e > > [2017-12-05 15:46:15,469] ERROR - KeyTemplateRetriever Exception when > retrieving throttling data from remote endpoint > java.net.ConnectException: Connection refused (Connection refused) > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net.AbstractPlainSocketImpl.doConnect( > AbstractPlainSocketImpl.java:350) > at java.net.AbstractPlainSocketImpl.connectToAddress( > AbstractPlainSocketImpl.java:206) > at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java: > 188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:668) > at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket( > SSLSocketFactory.java:522) > at org.apache.http.conn.ssl.SSLSocketFactory.connectSocket( > SSLSocketFactory.java:401) > at org.apache.http.impl.conn.DefaultClientConnectionOperato > r.openConnection(DefaultClientConnectionOperator.java:178) > at org.apache.http.impl.conn.AbstractPoolEntry.open( > AbstractPoolEntry.java:144) > at org.apache.http.impl.conn.AbstractPooledConnAdapter.open( > AbstractPooledConnAdapter.java:131) > at org.apache.http.impl.client.DefaultRequestDirector.tryConnect( > DefaultRequestDirector.java:610) > at org.apache.http.impl.client.DefaultRequestDirector.execute( > DefaultRequestDirector.java:445) > at org.apache.http.impl.client.AbstractHttpClient.doExecute( > AbstractHttpClient.java:863) > at org.apache.http.impl.client.CloseableHttpClient.execute( > CloseableHttpClient.java:82) > at org.apache.http.impl.client.CloseableHttpClient.execute( > CloseableHttpClient.java:106) > at org.apache.http.impl.client.CloseableHttpClient.execute( > CloseableHttpClient.java:57) > at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever. > retrieveKeyTemplateData(KeyTemplateRetriever.java:83) > at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever. > loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111) > at org.wso2.carbon.apimgt.gateway.throttling.util. > KeyTemplateRetriever.run(KeyTemplateRetriever.java:54) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > Exception in thread "Timer-5" java.lang.NullPointerException > at java.util.Objects.requireNonNull(Objects.java:203) > at java.util.Arrays$ArrayList.(Arrays.java:3813) > at java.util.Arrays.asList(Arrays.java:3800) > at org.wso2.carbon.apimgt.gateway.throttling.util.KeyTemplateRetriever. > loadKeyTemplatesFromWebService(KeyTemplateRetriever.java:111) > at org.wso2.carbon.apimgt.gateway.throttling.util. > KeyTemplateRetriever.run(KeyTemplateRetriever.java:54) > at java.util.TimerThread.mainLoop(Timer.java:555) > at java.util.TimerThread.run(Timer.java:505) > [2017-12-05 15:57:04,008] INFO - AndesRecoveryTask Running DB sync task. > > Regards, > > *Senuwan Withana* > Software Engineer - Support Team | WSO2 > > Email : senu...@wso2.com > Mobile: 94773212853 > Web: http://www.wso2.com > > > > ___ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] Problem with IP level throttling in distributed setup
Hi Buddhimala, Did you observe this behavior only for IP based throttle condition or with other conditions as well (eg. header condition, IP range condition )? Thanks, DinushaD. On Wed, Nov 29, 2017 at 11:47 AM, Buddhimala Ranasinghe <buddhim...@wso2.com > wrote: > Hi All, > > I have a distributed deployment in API Manager which contains > > 1GW > Pub+Store+TM > Is as KM > > I tried to implement IP level throttling for my API in this setup. I have > put 20 as my default equest limit and under IP condition I gave request > count as 5. I gave my local IP address as the IP condition to thrttle out. > But when I invoked the API, it throttles out at the 21st request and not > at 6th request. > > I also tried the same with another pack where only IS was configured as KM > (Pub,Store,GW,TM+IS as KM). There I could successfully throttle out at the > 6th request. > > What can be the reason for this behaviour? Can you please help me to > resolve this problem? > > > Thanks > -- > > > *Buddhimala Ranasinghe* > Software Engineer-Support Team | WSO2 > Emil: buddhim...@wso2.com > Mobile:+94771563138 <+94%2077%20156%203138> > Web:http://wso2.com > [image: https://wso2.com/signature] <https://wso2.com/signature> > > ___________ > Dev mailing list > Dev@wso2.org > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Dinusha Dissanayake Software Engineer WSO2 Inc Mobile: +94712939439 <https://wso2.com/signature> ___ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
Re: [Dev] REST API resource name
Hi Viduranga,
I think the last part in the endpoint would be better if you use
*sdk-gen-languages
*instead of *sdkgenlanguages*. So the resource name would be
*{basePath}/sdk-gen-languages*.
Thanks,
DinushaD.
On Tue, Aug 22, 2017 at 5:23 PM, Viduranga Gunarathne <vidura...@wso2.com>
wrote:
> Hi everyone,
>
> I'm implementing a REST API endpoint to retrieve a list of programming
> language names (java, python, android, ...) which are the supported
> languages for swagger-codegen, in generating SDKs for APIs in WSO2 API
> Manager Store.
>
> The resource name I came up with is *"basePath/sdkgenlanguages"*
>
> Appreciate suggestions on this!
>
> Thanks in advance.
> --
> Regards,
>
> *Viduranga Gunarathne*
>
> *Software Engineer Intern*
>
>
> *WSO2*
> Email : vidura...@wso2.com
> Mobile : +94712437484 <+94%2071%20243%207484>
> Web : http://wso2.com
> [image: https://wso2.com/signature] <https://wso2.com/signature>
>
--
Dinusha Dissanayake
Software Engineer
WSO2 Inc
Mobile: +94712939439
<https://wso2.com/signature>
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev
