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

CORS support from WSO2 API Manager 2.0.0

Cross-origin resource sharing (CORS) is a mechanism that allows restricted resources  on a web page to be requested from another domain outside the domain from which the first restricted resource was served. For example, an HTML page of a web application served from http://domain-a.com makes an <img src >  request for a different domain as 'domain-b.com' to get an image via an API request.  For security reasons, browsers restrict cross-origin HTTP requests initiated from within scripts as in above example and only allows to make HTTP requests to its own domain. To avoid this limitation modern browsers have been used CORS standard to allow cross domain requests. Modern browsers use CORS in an API container - such as  XMLHttpRequest  or Fetch - to mitigate risks of cross-origin HTTP requests.Thing to  note is it's not only sufficient that the browsers handle client side of cross-origin sharing,but also the servers from which these resources getting need to handl

[WSO2 AM] APIStore User Signup as an approval process

In previous versions of WSO2 APIManager before 1.6.0, it was allowed any user who's accessible the running APIStore come and register to the app.But there will be requirement like,without allowing any user to signup by him/her self alone,first get an approve by a privileged user and then allow to complete app registration.Same requirement can be apply to application creation and subscription creation as well.To fulfill that,we have introduced workflow extension support for  WSO2 APIManager  and you can find the introductory post on this feature from my previous blog post on " workflow-extentions-with-wso2-am-160 " . From this blog-post,I'll explain how to achieve simple workflow integration with default shipped resources with  WSO2 APIManager 1.6.0 and WSO2 Business Process Server 3.1.0 with targeting "user-signup" process. Steps First download the WSO2 APIManager 1.6.0[AM] binary pack from product download page . Extract it and navigate to