So, if you’re looking for alternatives there are several other nice projects out there. YAJSW is super easy to configure and use no native code.

You can generate a config file from a running Java process by giving the process ID. Found that it’s easy to start from here and then tweak the system paths according to your setup.

Following wrapper.conf file can be used to start any WSO2 Carbon product as a service in Windows. In the following configuration I’ve hard coded the working dir but that can easily be set to take from an environment variable just like the JVM path. I’ve removed comments from wrapper.conf for brevity.

wrapper.working.dir=C:\\test\\wso2greg-4.1.1

wrapper.java.app.mainclass= org.wso2.carbon.bootstrap.Bootstrap

wrapper.console.loglevel=INFO

wrapper.console.title="WSO2 G-Reg"

wrapper.ntservice.name="WSO2GREG"

wrapper.ntservice.displayname="WSO2 GREG"

wrapper.ntservice.description="Governance Registry"

wrapper.daemon.run_level_dir=${if (new File('\/etc\/rc0.d').exists()) return '\/etc\/rcX.d' else return '\/etc\/init.d\/rcX.d'}

wrapper.tray = true

wrapper.tray.port = 15002

wrapper.on_exit.0=SHUTDOWN
wrapper.on_exit.default=RESTART

wrapper.filter.trigger.0=Exception
wrapper.filter.script.0=scripts\/trayMessage.gv
wrapper.filter.script.0.args=Exception

placeHolderSoGenPropsComeHere=
wrapper.java.command = ${JAVA_HOME}\\bin\\java
wrapper.java.classpath.1 = .\\lib
wrapper.java.classpath.2 = ${JAVA_HOME}\\lib\\tools.jar
wrapper.java.classpath.3 = .\\bin\\org.wso2.carbon.bootstrap-3.2.2.jar
wrapper.java.classpath.4 = .\\lib\\endorsed
wrapper.app.parameter.1 = RUN
wrapper.app.parameter.2 = -Dcarbon.registry.root=\/
wrapper.app.parameter.3 = -Dcarbon.home=c:\\test\\wso2greg-4.1.1
wrapper.app.parameter.4 = -Dwso2.server.standalone=true
wrapper.app.parameter.5 = -Djava.command=${JAVA_HOME}\\bin\\java
wrapper.app.parameter.8 = -Dcarbon.xbootclasspath=;.\\lib\\xboot\\org.wso2.carbon.xboot-3.2.0.jar
wrapper.app.parameter.9 = -Djava.io.tmpdir=.\\bin\\..\\tmp
wrapper.app.parameter.10 = -Dwso2.carbon.xml=.\\bin\\..\\repository\\conf\\carbon.xml
wrapper.app.parameter.11 = -Dwso2.registry.xml=.\\bin\\..\\repository\\conf\\registry.xml
wrapper.app.parameter.12 = -Dwso2.user.mgt.xml=.\\bin\\..\\repository\\conf\\user-mgt.xml
wrapper.app.parameter.13 = -Dwso2.transports.xml=.\\bin\\..\\repository\\conf\\mgt-transports.xml
wrapper.app.parameter.14 = -Djava.util.logging.config.file=.\\bin\\..\\lib\\log4j.properties
wrapper.app.parameter.15 = -Dcarbon.config.dir.path=.\\bin\\..\\repository\\conf
wrapper.app.parameter.16 = -Dcarbon.logs.path=.\\bin\\..\\repository\\logs
wrapper.app.parameter.17 = -Dcomponents.repo=.\\bin\\..\\repository\\components
wrapper.app.parameter.18 = -Dcom.atomikos.icatch.file=.\\bin\\..\\lib\\transactions.properties
wrapper.app.parameter.19 = -Dcom.atomikos.icatch.hide_init_file_path=true
wrapper.app.parameter.20 = -Dorg.apache.jasper.runtime.BodyContentImpl.LIMIT_BUFFER=true
wrapper.app.parameter.21 = -Dcom.sun.jndi.ldap.connect.pool.authentication=simple
wrapper.app.parameter.22 = -Dcom.sun.jndi.ldap.connect.pool.timeout=3000
wrapper.app.parameter.23 = -Dcarbon.classpath=.\\lib;${JAVA_HOME}\\lib\\tools.jar;;.\\bin\\org.wso2.carbon.bootstrap-3.2.2.jar;
wrapper.java.additional.1 = -Xbootclasspath\/a:;.\\lib\\xboot\\org.wso2.carbon.xboot-3.2.0.jar
wrapper.java.additional.2 = -Xms256m
wrapper.java.additional.3 = -Xmx512m
wrapper.java.additional.4 = -XX:MaxPermSize=256m
wrapper.java.additional.5 = -Dimpl.prefix=Carbon
wrapper.java.additional.6 = -Dcom.sun.management.jmxremote
wrapper.java.additional.7 = -Djava.endorsed.dirs=.\\lib\\endorsed;

• Using WSO2 ESB with SAP ERP (Retail) by Harsha – John Keels Holding PLC is one of the largest conglomerate in Sri Lanka. As a public liability company it’s really interesting how they went about adopting open source middleware products into their core business processes. As the person who spearheaded the effort and provided guidance for the team, Harsha’s talk is going to be interesting providing practical insights into the whole project
• Building Cool Applications with WSO2 StratosLive by Shankar – Stratos provide a rich framework for building applications. Developers can concentrate on making cool applications without having to worry about a whole heap of infrastructure related aspects. They’re taken care of. Interesting to get a head start on application development from Shankar
• Open Source Adoption in the Enterprise by Prajod – Enterprises have been a big no no for open source software. However, it’s been changing really fast. Going to be interesting hearing more insights into open source adoption from Prajod
• Quality – The key to successful SOA by Charitha – Traditional software QA and testing what I read during my undergrad is from a different era. The projects those days usually ran for years. Now, project durations are measured in weeks. Project life cycles are getting shorter and you have to adjust testing and QA efforts accordingly. Have to adopt new methods. SOA testing is even tougher given plethora of possible integration scenarios with other products. Going to be great hearing QA and testing insights from Charitha
• Develop, Test and Deploy your SOA Application through a Single Platform by Chathuri – I’ll confess. I’m not an ardent fan of Eclipse. When you compare it with IntelliJ IDEA, Eclipse does feels like some one kicked you in the nuts. That’s just me I am thrilled to get to know more about Eclipse + Carbon Studio for application development for the WSO2 middleware platform

Full agenda.

P.S: Use a browser that supports HTML5.

Usually in technically adept circles you can hear virtualization being used more often than the term cloud computing, the technology that enable computers to evaporate into small H₂O particles and form clouds. Virtualization tools have been there for a while. It was, IMHO, got popular after Amazon slapped a Web services interface in front of Xen and said, try using this interface to start/stop and manage virtual machines. Having a separate service for persistent storage, again, is a brilliant marketing move. With big investments (such as Intel investing in Joyent) one can guarantee that the cloud space will get cloudier as time progress. This might make projects such as Simple Cloud more attractive.

Adoption rates for cloud computing is going to increase among the big guys. As a survey done by Forrester tells “one out of four large companies plan to use an external provider soon, or have already employed one”. When people are seriously considering moving to cloud platforms, you have to make sure that all the application programs are ready to be run on a virtualized environment. Specially SOA middleware products that the company is using should be compatible and must be able to take advantage of the services provided.

One advantage of moving to cloud computing is the ability to add/remove resources as and when it’s required. If your applications, or middleware products that you’re using is incapable of getting advantage of this elasticity (autoscaling to the inner techie in you) there’s no point, or no value gained by putting your stuff in the cloud. It’s one reason why WSO2 has “cloud enabled” all of the products line. Not only you can host all your services in the cloud using WSO2 middleware products, you can download pre-built images for VMware and KVM to run inside your private virtualized infrastructure. Give it a whirl and see!

$ export MAVEN_OPTS="-Xmx1024m -XX:MaxPermSize=128m"

First step, build Axis2 1.4.1 from the custom branch

$ svn co http://svn.wso2.org/repos/wso2/branches/axis2/v1.4.1 axis2-1.4.1-branch

Next find the revision of the branch,

$ cd axis2-1.4.1-branch
$ svn info
Path: .
URL: http://svn.wso2.org/repos/wso2/branches/axis2/v1.4.1
Repository Root: http://svn.wso2.org/repos/wso2
Repository UUID: a5903396-d722-0410-b921-86c7d4935375
Revision: 32422
Node Kind: directory
Schedule: normal
Last Changed Author: amila
Last Changed Rev: 30518
Last Changed Date: 2009-02-06 10:39:03 +0530 (Fri, 06 Feb 2009)

Revision 30518 have an inconsistency in modules/addressing/pom.xml where the addressing artefact ID is wrong. You have to get this patch and apply it. Download, save it somewhere and do the following to apply the patch.

$ cd modules/addressing
$ patch -p0 < /home/chintana/addressing-pom.patch
$ cd ../..

Now you're at the Axis2 root level. Before building at the root level you have to build two plugins,

$ cd modules/tool/axis2-mar-maven-plugin
$ mvn clean install
$ cd ../axis2-aar-maven-plugin/
$ mvn clean install
$ cd ../../..

Back at the root level, now you can build the project,

$ mvn clean install -Dmaven.test.skip=true

Next step is to build Rampart from the custom branch,

$ svn co http://svn.wso2.org/repos/wso2/branches/rampart/1.4.wso2 rampart-custom
$ cd rampart-custom
$ mvn clean install -Dmaven.test.skip=true

Build Sandesha from the custom branch,

$ svn co http://svn.wso2.org/repos/wso2/branches/sandesha2/1.4.wso2 sandesha-custom
$ cd sandesha-custom
$ mvn clean install -Dmaven.test.skip=true

Next up is Savan, again from a custom branch,

$ svn co https://svn.wso2.org/repos/wso2/branches/savan/1.0wso2v1 savan-custom
$ cd savan-custom
$ mvn clean install -Dmaven.test.skip=true

Now all the prerequisites are complete for the Carbon platform. Let's go ahead and build Carbon. It has 3 parts. carbon-orbit, carbon and carbon-components (for carbon I had to change the addressing.version property in root level pom.xml to 1.4.1),

$ svn co http://svn.wso2.org/repos/wso2/trunk/carbon-orbit
$ cd carbon-orbit
$ mvn clean install -Dmaven.test.skip=true
$ cd ..
$ svn co http://svn.wso2.org/repos/wso2/trunk/carbon
$ cd carbon
$ mvn clean install -Dmaven.test.skip=true
$ cd ..
$ svn co http://svn.wso2.org/repos/wso2/trunk/carbon-components
$ mvn clean install -Dmaven.test.skip=true

All righty! After this you can go ahead and build other products which are designed on top of Carbon such as WSO2 WSAS, WSO2 ESB etc...