Skip to main content

Summarizing WSO2 Gadget Server

Near after eight months,that I have joined WSO2 team,I feel it's the better time to share some information regarding the product,that I have almost contributed there.It's non other than WSO2 Gadget Server-The Enterprise Information Portal,which provides a framework built on top of the Google gadget specification.For more information regarding Google gadget specification visit .

Simply saying,the key idea of GS is to keep all the relevant information in a single place in a well organized manner according to the portal user's preference.And the user can change this web space as a dynamical information store or either static information store according to his/her requirements.

Accepting the idea of one picture could say more than 1000 words,before going to deep on it,below shows the screen-shot of the portal view of GS.



Highlighted features of Gadget Server...
  • Embedded Gadget Repository
It is to store gadget xml files and add them to portal once user required.Gadget repository view of GS,provides information of how many users using the gadget,whether it is already added to the portal,gadget description and its ratings.


  • Allow two ways of adding gadgets to the portal
-- Store the gadget xml in WSO2 gadget repository ,and add it to GS portal.


-- Link to a gadget xml in different location and add it to GS portal.
  • Maintain role-based gadgets
Once a gadget stored in GS embedded registry,access to that gadget can be limited by setting permissions as below,in gadget permissions part.

  • Portal Theming Support
Upto now,users could able to customize portal theme from three different customized themes.

  • Portal custom layout support
Currently portal,supports six layout templates (such as one column layout,2-column layout,3- column layout,2- column 2-row layout,etc).Following is an example for a portal view having such a custom layout template.


Above mentioned are not all the features provide by GS,but a part from that stack.You can get more information from;

Comments

Popular posts from this blog

Convert an InputStream to XML

For that we can use DocumentBuilder class in java. By using the method parse(InputStream) ; A new DOM Document object will return. InputStream input; DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance(); DocumentBuilder parser = factory.newDocumentBuilder(); Document dc= parser.parse(input); In the above code segment,by using the created Document object,the corresponding XML file for the inputStream can be accessed. References: http://www.w3schools.com/dom/dom_intro.asp http:// download.oracle.com/javase/1.4.2/docs/api/javax/xml/parsers/DocumentBuilder.html

Concat two xml values with XSLT

The use-case described in this blog-post,is there's an WSO2 ESB node setup to proxy an incoming message to a particular back-end endpoint.  Before delivering the message to the back-end endpoint,from the ESB node itself,this incoming message need to processed and change its inside xml payload format. For eg: Below is the incoming message <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"> <OwnerData> <Name>John Smith</Name> <openedDate>12/12/80</openedDate> <quality>good</quality> </OwnerData> <CinemaHallData> <rows>100</rows> <seats> <seat>50</seat> <seat>60</seat> </seats> </CinemaHallData> </CinemaHall> This message need to be changed as  below; <?xml version="1.0" encoding="UTF-8"?> <CinemaHall name="liberty"...

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage  as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...