Posts

Showing posts from June, 2009

Business activity monitoring (BAM) with WSO2 Governance Registry

Image
BAM refers to the aggregation, analysis, and presentation of real time information about activities inside organizations and involving customers and partners. The main benefits of BAM are to enable an enterprise to make better informed business decisions, quickly address problem areas, and re-position organizations to take full advantage of emerging opportunities. BAM solutions often present information on dash boards using various graphs. WSO2 Governance Registry provides with BAM functionality which enables users to aggregate various web services data and visualize them using dashboard gadgets. In this post, I'll describe how you can add a remote server for monitoring and generate graphs. Pre-requisites: Download and install (Unzip the binary) WSO2 Governance Registry-3.0.0-beta1 release from here We will refer to the unzipped directory, Greg_Home Step 1 Start WSO2 Governance Registry server by running wso2server.bat{sh} from Greg_Home/bin Step 2 Access the management console o

WSO2 SOA Summer School - Security in SOA

Prabath Siriwardana , a colleague at WSO2, doing a webinar on Security in SOA on 2nd of July 2009. You can register from here

Importance of defect isolation

A problem well stated is half solved True! A good bug report should provide with the information to reproduce the issue. It is QA tester's responsibility to specify the exact steps of bug recreation. Isolating the environment and conditions at which the issue occurred are extremely important components of a defect report. Sadly I have seen some people ignore these important practices due to tight schedules and rush testing processes. No! In any case, even with management push towards quicker feedback of the products under test, ignoring these vital practices are totally unacceptable. Your bug report mirrors the professionalism of software QA testing job. Developers do not waste time or jump in to assumptions by reading your bug report. It provides all the necessary details. It consists of logs, screen shots when they are required. A good QA tester must isolate the issue first. He never reports bugs just by seeing an exception in server console. He attempts multiple instances to rec