Charitha's Web Log

In a previous blog post , I explained the steps to deploy a web service in Apache Axis2 , secure it with HTTP basic authentication and invoke it using Apache Jmeter .  In this post, we will repeat the same using different set of tools and frameworks which are comparatively easy-to-use and user-friendly. We will secure a simple SOAP based web service which is hosted in WSO2 Application Server , configure an authentication security policy and invoke the service using HTTP basic auth through soapUI . Pre-Requisites:  Download and install WSO2 Application Server-5.0.0   Download and install soapUI 4.0.1 or later version Step 1: Start WSO2 Application Server by running wso2server.sh startup script. Access the management console url (https://localhost:9443/carbon) and log in with the default administrator credentials (username=admin, password=admin) Step 2: Go to the Deployed Services page and you will find "HelloService" is deployed by default. Click on the servi

The latest version of WSO2 Carbon (Carbon-4.0.0) platform ( WSO2 ESB-4.5.0 , WSO2 Application Server-5.0.0 , WSO2 Governance Registry - 4.5.0 etc) supports a new deployment model which allows you to setup product clusters with separated worker and management nodes. In a worker/manager separated cluster setup, the management node(s) is used to deploy and configure the deployment artifacts where as the worker nodes are used to serve the requests received by clients. I'm not going to spend much time on a detailed explanation about this new deployment approach since my objective is to take you through the minimum worker/manager deployment setup of WSO2 Application Server cluster as quickly as possible. You can find more about the theoretical aspects of this new deployment model in Afkham Azeez's blog . Deployment diagram We are going to setup the minimum cluster setup in our local machines. Thus, we will use 3 product instances as follows. Load Balan