About Gadget Server

The WSO2 Gadget Server (GS) is a 100% open source, light-weight, enterprise-grade gadget repository and portal solution available under the Apache Software License 2.0. It can be run on your infrastructure or on the Cloud to facilitate hosting and managing gadgets, data, users and permission though a user friendly interface. This interface offers simple, drag-and-drop layout of gadgets, per-gadget settings and different tabs for gadget categorization among others. The WSO2 Gadget Server's enterprise gadget repository allows business users to pick and choose additional, recommended gadgets to be added to their individual portal pages. This repository helps enterprises govern the gadgets exposed to the end-users, while the users get to rate and comment on each gadget found in the repository.

Gadgets deployed in the WSO2 Gadget Server are HTML and JavaScript wrapped in XML adhering to the Google Gadgets Specification. As a result, they are compatible with SOA and web-oriented distributed systems and are self-contained, ready-to-use, task-specific and lightweight. They can be hosted anywhere, downloaded through the Web and leveraged by a wide range of users. They are also easily scalable and allow organizations to leverage existing services and code to satisfy new user requirements.

Google gadget development is an easy, standards-based process where any Web developer with basic skills in HTML, Javascript, and XML can develop and deploy a custom gadget. These gadgets can be hosted at any URL, or stored and advertised within the Gadget Server's repository. Accessing enterprise Web services through a gadget is easy, reliable, and secure. The WSO2 platform provides many options for connecting with diverse data sources, from the WSO2 Data Services Server connecting to databases and spreadsheets to the WSO2 Mashup Server connecting and collating data from multiple sources (which might include external cloud services and even Web pages).

Known Issues

For a list of known issues in the WSO2 Gadget Server version 1.4.0, refer to the following links in the WSO2 Oxygen Tank:

Community Resources

WSO2 is willing to provide you guidance for any technical issues or questions regarding the Gadget Server product. You can communicate with the WSO2 Gadget Server development team directly using the relevant mailing lists mentioned here: http://wso2.org/mail.

WSO2 encourages you to report issues and enhancement requests for WSO2 Gadget Server using the publicJIRA available at https://wso2.org/jira/browse/GS. You can also track their resolutions and comment on the progress.

Questions regarding the Gadget Server can also be raised through http://stackoverflow.com. Ensure that you tag the question with appropriate keywords such as WSO2 and Gadget Server so that our team can easily find your questions and provide answers.

For tutorials, articles, Webinars and similar resources, visit the WSO2 Oxygen Tank and search under the Resources menu.

Support Options

WSO2 also offers a variety of development and production support programs, ranging from Web-based support during normal business hours, to premium 24x7 phone support. WSO2 is committed to ensuring that your enterprise middleware deployment is completely supported from evaluation to production. Our unique approach ensures that support leverages the open development methodology and is provided by the very same engineers who build the products. For additional support information please refer to http://wso2.com/support.

Get Involved

WSO2 invites you to contribute by checking out the source from SVN using the following commands. This project uses Subversion to manage its source code. Instructions on Subversion can be found at http://svnbook.red-bean.com.

The WSO2 Gadget Server release 1.4.0 is based on Carbon 3.2.0.

Anonymous Checkout

The complete source including the Carbon platform can be checked out anonymously from SVN with this command:

$ svn checkout http://svn.wso2.org/repos/wso2/branches/carbon/3.2.0 wso2carbon

The list of commands that can be run are as follows. If you only want to build the Application Server, you have to always use the option "-Dproduct=gs".


mvn clean install -Dproduct=gs	To create the complete release artifacts of WSO2 Gadget Server including the binary and source distributions.
mvn clean install -Dmaven.test.skip=true -Dproduct=gs	To create the complete release artifacts of WSO2 Gadget Server including the binary and source distributions, without running any of the unit tests.
mvn clean install -Dmaven.test.skip=true -Dproduct=gs -o	To create the complete release artifacts of WSO2 Gadget Server including the binary and source distributions, without running any of the unit tests, in offline mode. This can be done only if you've already built the source at least once.

Developer Access

Everyone can access the Subversion repository via HTTPS, but Committers must checkout via HTTPS. The Carbon framework related source code can be checked out using the following commands.

$ svn checkout https://svn.wso2.org/repos/wso2/branches/carbon/3.2.0/wso2carbon

The Carbon core project is the root project of the OSGi platform on which the Java product stack is built. The Carbon components contain all the components not just the Application Server specific ones. Therefore, you need to build just the set of components required by the Application Server, using the following command:

$ mvn clean install -Dproduct=gs

Execute the following command to commit your changes (SVN will prompt you for password).

$ svn commit --username your-username -m "A message"

Access through a Firewall

If you are behind a corporate firewall which is blocking http access to the Subversion repository, you can try the developer connection:

$ svn checkout https://svn.wso2.org/repos/wso2/trunk/carbon carbon

Access through a Proxy

The Subversion client can be configured to access through a proxy.

1) Specify the proxy to use in the "servers" configuration file in:

"~/.subversion" directory for Linux/Unix
"%APPDATA%\Subversion" hidden directory for Windows. (Try "echo %APPDATA%")

2) There are comments in the file explaining what to do. If you don't have this file, get the latest Subversion client and run any command. It will create the configuration directory and template files.

Example : Edit the 'servers' file and add something similar to:

[global]
http-proxy-host = your.proxy.name
http-proxy-port = 312