Lakmali Erandi Baminiwatta’s blog

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 API management challenges such as API provisioning, API governance, API security and API monitoring. You can download API Manager latest version from: http://wso2.com/products/api-manager and find the online documentation from: http://docs.wso2.org/wiki/display/AM130/WSO2+API+Manager+Documentation With WSO2 API Manager 1.3.0 release you can track your API invocations through Google Analytics! First let me explain you what is google analytics. Google analytics is a service offered by Google which tracks vists to a web site and generates detailed statistics based on those visits. Now WSO2 API Manager latest 1.3.0 release fascilitates you to integrate with Google Analytics to track run time statistics for API invocations. Here is the step by step guide to do this. 1. Setup a

Enable remote access to mySQL database server 1. Open the MySQL server configuration file my.cnf. sudo gedit /etc/mysql/my.cnf 2. Change the bind-address value to your MySQL server ip. If the MySQL server IP=10.100.2.200, change it as follows, save and close my.cnf file. bind-address=10.100.2.200 3. Now Grant access to remote IP. If the remote IP=10.100.2.180   Grant permission to a specific database (ex: testbd) GRANT ALL ON testdb.* TO testuser@'10.100.2.180' IDENTIFIED BY 'test123'; Grant all permissions GRANT ALL PRIVILEGES ON *.* TO testuser@'10.100.2.180'  IDENTIFIED BY 'test123'  WITH GRANT OPTION; 4. Open port 3306, if firewalls are enabled. Following is a sample iptables rule to open Linux iptables firewall. /sbin/iptables -A INPUT -i eth0 -p tcp --destination-port 3306 -j ACCEPT 5. logout of mysql. 6. Connect from remote host mysql -u root -h 10.100.2.200 -p

With the new Smooks Persistence cartridge in Smooks 1.2, we can directly use several entity persistence frameworks from within Smooks (Hibernate, JPA etc). So in this blog post let's try out the Hibernate sample specified in here . Since smooks have given the basic configurations only, this blog post is going to assist the peolple who need full implementation. What we are going to do is process the following XML message and store the product information to a bean and persist the order information. input.xml ------------ <order> <ordernumber>1</ordernumber> <customer>123456</customer> <order-items> <order-item> <product>11</product> <quantity>2</quantity> </order-item> <order-item> <product>22</product> <quantity>7</quantity> </order-item> </order-items> </or

WSO2 ESB version - 4.0.3 WSO2 PayLoad Factory Mediator is for transforming or replacing message content in between the client and the backend server. Incomming message from client can be transformed by the Payload Factory mediator into the format expected by the service. Then the response message can be formatted into which is expected by the client. Each argument in the mediator configuration could be a static value or an XPath expression. When an expression is used, argument value is fetched at runtime by evaluating the provided XPath expression against the existing SOAP message. Also the format of the request or response message can be configured which is mapped with the arguments provided in order. For instance in the following the values for format parameters Code & Price will be assigned with values evaluated from args given in the specified order. <payloadFactory> <format> <m:checkpriceresponse xmlns:m="http://services.sam