Skip to main content

WSO2 Gadget Server 1.4.0 Released !!!

The WSO2 Gadget Server team is pleased to announce the release of version 1.4.0 of the WSO2 Gadget Server.

The WSO2 Gadget Server is an enterprise grade portal, which is available under the Apache Software License v2.0. With the WSO2 Gadget Server, you can offer your execs, employees, partners, or customers a way to get all the information in one place that they need. Each user's dashboard is individualized, allowing him/her to add, customize, and rearrange gadgets, as well as group them into tab sets. The open "Web" model means users can select gadgets not only from your enterprise, but also from Google and many others. 

Google Gadget development is an easy, standards-based process - 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 Gadget Repository. Accessing enterprise Web services through a gadget is easy, reliable, and secure. And the WSO2 platform provides many options for connecting with diverse data sources-from the WSO2 Data Services Server connecting to data bases and spreadsheets to the WSO2 Mashup Server connecting and collating data from multiple sources (which might include external cloud services and even Web pages).

You can download this distribution from http://wso2.org/downloads/gadget-server and give it a try.

Key Features of WSO2 Gadget Server

  • Enterprise class Portal interface - Users get to organise gadgets in a familiar portal interface. Sets of gadgets can be organised using tabs. Individual gadgets can be moved between tabs as well as cloning an entire tab to be used as the foundation for a new tab.
  • Client Side Gadgets - Any gadget adhering to the Google Gadget Specification can be added to the portal. These gadgets are basically HTML and Javascript embedded in XML. They can be hosted in any publicly accessible Web Server. The URL of the gadget XML is used to add them to the Portal.
  • Enterprise Gadget Repository - Organisations can maintain a central repository of gadgets. Portal users can browse and add gadgets from this repository to their individual portals, while rating and commenting on individual gadgets.
  • Anonymous Mode - Users can experience most of the Portal's functionality 'excluding' the gadget Repository even before registration and sign in. All data in this mode will be stored in the user's browser.
  • OAuth Support for Gadgets - Gadget Server enables to add OAuth keys for gadgets to communicate with external APIs such as Google GData, Twitter etc.
  • Inter-gadget Communication - Gadget Server allows inter gadget communication.
  • I18n Support for Gadget - Gadget Server supports internationalization of gadgets.
  • User registration, sign-in and external user stores - User registration and sign in can be done using OpenID or Infocards in addition to the traditional user name and password based scheme. Also the Gadget can be integrated to a external user stores such as LDAP and AD.
  • Management Console - Helps configure and manage the server, its users and the Enterprise Gadget Repository via an intuitive browser based administrative interface.
  • Custom Layouts for Tabs - Gadget Server users can choose a desired layout form six different layouts when creating a new tab.
  • Role Based Permissions - Gadgets can be restricted based on users role.
  • Make SOAP Request Support - Not only REST style requests, gadgets written for WSO2 Gadget Server can consume SOAP only web service via make SOAP Request.
  • Theming Support - Gadget Server users can create custom templates for the portal UI, and add them via Gadget Server management console.
  • Gadget Archive Deployment - With WSO2 Carbon Application deployment, users can, write gadgets using Carbon Studio and deploy the gadget archive in to the Gadget server. 
  •  

New Features of the WSO2 Gadget Server 1.4.0

  • Based on Carbon 3.2.0 - Gadget Server release is based on Carbon "Middleware a' la carte" which is an OSGi based SOA platform version 3.2.0 by WSO2 Inc.
  • Optimized Performance - Gadget Server users can now experience better performance in dashboard and gadget loading due to asynchronous gadget rendering.
  • Search Enabled Gadget Repository - Search enabled gadget repository now allow users to search for gadgets inside gadget repository.
  • Improved UI to Pick Gadgets - Gadget Server users can now pick gadget XML from registry, File system or from external repositories.
  • Enhanced Permission Model for Theming - Now gadget server supports new permission model for theming usage where the administrator could set permission for different users to use different themes.
  • Improved Gadget Source Editor - Now users can edit gadget source at the gadget repository itself using the user friendly gadget source editor. 
  •  

    Issues Fixed in This Release


      Known Issues


        How to Run

        1. Extract the downloaded zip
        2. Go to the bin directory in the extracted folder
        3. Run the wso2server.sh or wso2server.bat as appropriate
        4. Point your browser to the URL https://localhost:8443/carbon
        5. Use "admin", "admin" as the username and password to login as an admin and create a user account
        6. Assign the required permissions to the user through a role
        7. If you need to start the OSGi console with the server use the property -DosgiConsole when starting the server. The INSTALL.txt file found on the installation directory will give you a comprehensive set of options and properties that can be passed into the startup script 

          How You Can Contribute

          Mailing Lists

          Join our mailing list and correspond with the developers directly.

          Reporting Issues

          WSO2 encourages you to report issues and your enhancement requests for the WSO2 Gadget Server using the publicJIRA. You can also watch how they are resolved, and comment on the progress..

          Discussion Forums

          Alternatively, questions could be raised using the forums available. WSO2 Gadget Server Forum : Discussion forum for WSO2 Gadget Server developers/users

          Support

          WSO2 Inc. offers a variety of development and production support programs, ranging from Web-based support up through normal business hours, to premium 24x7 phone support. For additional support information please refer to http://wso2.com/support/ For more information on WSO2 Gadget Server, visit the WSO2 Oxygen Tank (http://wso2.org) We welcome your feedback on this implementation. Thank you for your interest in WSO2 Gadget Server.


          -- The WSO2 Gadget Server Team --

          Comments

          Popular posts from this blog

          How to install IBM WebSphere MQ on Ubuntu (Linux)

          Following are the steps to install IBM WebSphere MQ version 8 on Ubuntu 14.04. 1) Create a user account with name "mqm" in Ubuntu. This should basically create a user called "mqm" and usergroup called "mqm" 2) Login to "mqm" user account and proceed with next steps 3) Increase the open file limit for the user "mqm" to "10240" or higher value. For this open "/etc/security/limits.conf" file and set the values as bellow. mqm       hard  nofile     10240 mqm       soft   nofile     10240 4) Increase the number of processes allowed for the user "mqm" to "4096" or higher value. For this open "/etc/security/limits.conf" file and set the values as bellow. You will need to edit this file as a sudo user. mqm       hard  nproc      4096 mqm       soft   nproc      4096 5) Install "RPM" on Ubuntu if you already don't have it. sudo apt-get install rpm   6) Download

          How to use Dynamic Registry Keys with WSO2 ESB Mediators

          From this post I will going to briefly introduce about one of the new features provided by WSO2 ESB . Earlier WSO2 ESB supported static registry keys where users can select a key for the mediator as a static value. But from ESB 4.0.0 users can use dynamic registry keys where users can define XPath expression to evaluate the registry key in run time. For an example let's consider XSLT mediator. With earlier static registry key based method user have to define only single XSLT file for transformation. With the use of dynamic registry key, user will be able to use XPath expressions to dynamically generate the registry key, based on the message context. So with that user can have multiple XSLT files and based on the evaluated key mediator will be able to select the required XSLT file in run time. Following is a sample usage of static and dynamic registry keys and user can use both of them according to situation.   Static Registry Key – define the exact path to find the xslt fil

          Creating a Simple Axis Service(.aar file) and Deploy it in WSO2 Application Server

          In this post I am explaining how to Create a Simple Axis Service(.aar file) and Deploy it in WSO2 Application Server using a simple sample. And also at the end I am describing how to do the same thing with creation of a Jar Service. Lets assume "sample-home" as our parent directory and inside that we can create following folder structure. With this folder structure we can include our external libraries (jar files) inside lib folder and  the "services.xml" file inside "META-INF" folder. Following is the sample services.xml definition which I used with this sample creation. < service name = "HelloService" > < Description > This is a sample service to explain simple aar service </ Description > < messageReceivers > < messageReceiver mep = "http://www.w3.org/2006/01/wsdl/in-out" class = "org.apache.axis2.rpc.receivers.RPCMessageReceiver" /> </ messageReceivers > < parame