Charitha's Web Log

Service or system monitoring and management are essential components of any SOA framework. WSO2 WSAS provides two different mechanisms to manage and monitor web services. 1. Ajax based GUI console 2. JMX based monitoring facility In this post, I'm going to demonstrate the second option, JMX based service and system monitoring component. You can find more information about WSAS GUI console from here . JMX (Java Management Extension) provides a set of tools and APIs for applying a standard client/server-based architecture to monitoring and management of a Java application. J2SE version 5.0 adds core support for the Java Management Extensions (JMX) into the Java standard libraries. We are going to use Jconsole, included in jdk1.5 or newer versions, to explore the management and monitoring capabilities provided by WSO2 WSAS. Pre-Requisites Download and install WSO2 WSAS-2.2.1 or later Step 1 JMX port is disabled by default in WSAS. Open WSO2WSAS_HOME/conf/server.xml and uncomment t

"java.security.InvalidKeyException:illegal Key Size" error is a common issue which occurs when you try to invoke a secured web service in an environment where the provision for java unlimited security jurisdiction is not done. This can be avoided by installing Java Cryptography Extension (JCE) unlimited strength jurisdiction policy files. 1. Suppose you are using jdk15. Go to http://java.sun.com/javase/downloads/index_jdk5.jsp 2. Go to the Other Downloads section and click on download link next to "Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 5.0" 3. Download jce_policy-1_5_0.zip and extract it in to a directory. 4. You will find local_policy.jar and US_export_policy.jar files there in the extracted directory. Copy these two files to $JAVA_HOME/jre/lib/security directory. (These files will already be there. you may replace them) 5. Restart WSO2 WSAS and invoke your secured service again. You will not encounter the "invalidk

I recently published a tutorial at WSO2 Developers portal - Oxygen Tank , which demonstrates six different mechanisms to invoke a publicly available web service. This tutorial explains each mechanism using a set of simple steps and mainly focused on beginners to the web services. See the complete tutorial here

I have demonstrated the steps to deploy Apache Axis2 on BEA WebLogic , IBM WebSphere , JBoss and Resin application servers in my previous posts. This series is not complete unless the steps to deploy Axis2 on GlassFish server are explained. Lets see how Axis2 can be deployed on GlassFish server. It is quite straightforward and similar to the other application servers we have discussed so far. Pre-requisites: Download and install the latest version of GlassFish server from here . Step 1 Start GlassFish server. i.e:- Go to GlassFish_Home/bin and run asadmin script as follows. asadmin start-domain domain1 This will start GlassFish server in domain1. Step 2 Download Axis2.war from here Step 3 Access GlassFish administration console (In a browser, access http://localhost:4848). Log in to administration console (Default username=admin, password=adminadmin). Step 4 In the left navigation menu of the GlassFish admin console, select Enterprise Applications and click on Deploy. You will be

Apache TCPMon is an utility that allows the messages to be viewed and resent. It is very much useful as a debug tool. If you don't know much about this tool, you can find more information here , here or here . I found an extension of this great tool, which can be included as an Eclipse plugin so that developers can monitor message transmission within their workspace without opening a separate tcpmon instance. It is very cool indeed. Saliya Ekanayake , a colleague at WSO2 has developed this utility as part of his university project. Lets see how this tcpmon plugin can be used in Eclipse WTP. 1. If you haven't done yet, download and install Eclipse WTP 2. Download tcpmonitor-1.0.0.jar from here 3. Copy tcpmonitor-1.0.0.jar in to Eclipse_home/plugins directory 4. Start eclipse 5. Select Window --> Show View --> Other --> Tcp Monitor --> TCP Monitor 6. Tcp monitor will be added as an view tab. Now you can configure the necessary port settings and trace message tran