Open Space

Each WSO2 product [eg: WSO2 ESB,GReg] provides specific and different functionalities which can be consume via product UI-admin console. But there are cases,where users want to use those functionalities,not from UI, but from their custom client implementations.That's where the importance of Carbon Admin Services come into the picture.  WSO2  Admin Services can be considered as SOAP web service endpoints which provide wso2 product specific functionalities. The admin services are not visible via the Carbon management console.  You can access the service description of the admin services[WSDL] if you know the admin service.  Before accessing the wsdl of a particular admin service,you need to enable the property < HideAdminServiceWSDLs > of carbon.xml as 'false'. You can find the admin services expose by a WSO2 product,by following below two steps. Run the server in OSGI mode ./wso2server.sh -DosgiConsole Once the server starts,type the command 'li...

WSO2 Products developed on top of the core WSO2 Carbon platform.WSO2 Carbon is a componentized Service Oriented Platform(SOA) which is built on OSGI framework,which defines a dynamic component system for Java.Bundle is the unit of modularization in OSGI.  If I described on how a WSO2 product is created ,first there are a set of components introduced and implemented as OSGI bundles.You can find such developed set of components from here .Then we group a set of components as a feature.And there are such pre-defined features which can be found from here .Then with selecting a relevant set of features,the product have been built.For example this pom.xml under the svn location contains the features set used by the product WSO2 API Manager product.And most importantly,one more advantage of this approach is at later time,product can be customize by adding more  features from wso2 feature manager at runtime. The main focus of this blog post is to guide on some OSGi leve...

This blog-post is mainly focus on API subscription process through API-Store  as described in here . Say there's a hosted WSO2 APIStore instance running in an organization.Once an app developer login to APIStore as an API Subscribe, browse  for available APIs and when he decided to use a set of APIs from his developed external application[eg: mobile/web-based application],he will  add an application to map with his developing app and then he'll subscribe each API to his created application in the APIStore. When the developer subscribe an API for an application,following three values will be generated on behalf of application.And importantly these three values are generated according to OAuth2 specification. Access Token -  The OAuth2 token which can be use to authenticate an API invocation.This token is only for the app developer [unless he shared the tokens with others(eg:3rd party users of his developed mobile app)] to use with API invocations from...

From this blog-post,I'm going to dig into the implementation of monitoring support provide by WSO2 API Manager with WSO2 BAM integration.First you need to know how to configure WSO2 AM with BAM to start with.You can find about the related configuration details from our product documentation .  However,before continue with this post,I think its better if I explain one step of above configuration.It's the AM Stats toolbox[API_Manager_Analytics.tbox] deployment in BAM server.This toolbox can be found from {AM_Home}/Statistics folder.A toolbox can be defined as an installable archive in BAM[1].This AM Stats toolbox contains below artifacts. Stream Definitions -These are the  descriptions of streams of data to be sent to WSO2 BAM in order to perform analytics. Analytics- Analytics include the hive scripts to be deployed in WSO2 BAM. Below diagram shows the main flow of the integration between WSO2 API Manager and WSO2 BAM.I will go through each step by step. ...

As the starting blog-post for 2013,I thought of summarizing about the implementation of key features of WSO2 API Manager as security,throttling,monitoring aspects by explaining a bit of API template.In WSO2 API Manager,once a API creator create the API from publisher app UI and change its status as 'PUBLISHED' ,a template xml for that API will be generated with its input attributes of name,version,context,endpoint,etc. You can find that generated template from '{AM_Home}/repository/deployment/server/synapse-configs/default/api'.Below is such a generated sample API template. When you observe that API,you'll notice for each API resource there's a separate in sequence and an out sequence created.And additionally apart from the input data added by the creator,you'll notice for an API ,four handlers have been engaged to each published API. Each of the above handlers contain the implementation of key providing features of WSO2 API Manager.Y...

This requirement came from some of the users who are already using WSO2 API Manager product and from WSO2 AM 1.3.0 on wards [released on today],this feature has implemented.You can find WSO2 AM 1.3.0 binary pack from here . Basically for the two apps [Publisher/Store] in WSO2 API Manager,now a developer can change app labels/messages according to the set language in the web browser. From this blog-post,I'll explain the steps to localize publisher app to Spanish,which contains unicode charactors. 1. First set the browser language to your preferred language.  Eg: In Google chrome navigate to Settings->Show advanced settings->;Languages and select your preferred language. 2. set the browser encoding type as UTF-8. 3. Then let's change the publisher app accordingly, Extract your downloaded pack and navigate to the deployed publisher app from the location "AM_Home}/repository/deployment/server/jaggeryapps/publisher". 4. We hav...

WSO2 API Manager provides a complete solution for publishing APIs,creating and managing a developer community and a scalable routing API trafic .If you are already familiar with this product,you are familiar with its one of basic component -'API Store'. A deployed API Store provides a single place to all third party and internal API consumers to browse available APIs and subscribe to them as they want.If such a consumer follow the subscription process of this store-front UI,he'll notice it's a process of subscribing a selected set of APIs into a application and  giving a result with generated three keys as access token,consumer key and consumer secret adhreing to OAuth 2.0 spec. In other words,it's the process of an Application developer [Say John a mobile app developer] select the APIs which needed to use from his application and subscribe to those APIs from his created application.As the result of this subscription process the application developer,John is...