iGoogle Gadget (featuring UWL,BPM,JSON & OAuth) – Part 3
This is the final blog about my iGoogle Gadget. In Part 1 (iGoogle Gadget (featuring UWL,BPM,JSON & OAuth) – Part 1) the retrieval of Universal Worklist tasks and present them as JSON was explained and in Part 2 (iGoogle Gadget (featuring UWL,BPM,JSON & OAuth) – Part 2) the creation of the OAuth Provider on SAP NetWeaver CE was described. In this blog I will explain how to create the iGoogle Gadget for retrieving the tasks and integrate the gadget in your iGoogle page. h3. *iGoogle Gadgets* I think everybody knows iGoogle. It’s a personalized start page were users can add web feeds and Google Gadgets. Popular gadgets include Weather, Calendar, Gmail, Twitter and Facebook. A cool thing to do is to develop your own Gadget, so you can decide yourself what you wanna show on your iGoogle page and that is what this blog is about. h3. *Gadgets API* For creating gadgets Google offers the Gadget API. With this API and by using XML, HTML, and JavaScript you are able to create your own gadget. Actually the Google Gadget API was the basis for the OpenSocial API, which is now an open platform for creating gadgets which can run in several containers (http://wiki.opensocial.org/index.php?title=Containers). Next to Google many websites already support OpenSocial like LinkedIn, MySpace and recently [SAP StreamWork | https://streamwork.com/api/opensocial/Overview.html] also joined. More info about this you can find in the recent blog (The specified item was not found.) by Richard Hirsch.My blog will only focus on iGoogle Gadgets and running them inside the iGoogle container. I have not tested it within another container. A good place to get familiar with creating iGoogle Gadgets is the documentation from Google. (http://code.google.com/intl/en/apis/gadgets/index.html) Here you can start with creating your “Hello, World” Gadget and embed d it into your own iGoogle Page. After creating the first application it needs to be hosted somewhere to make it accessible for iGoogle, this can be done by hosting it on a webhost. An easy way and suitable for this application is by using the Google Gadget Editor (GGE) , this is a tool for editing and hosting a gadgets with Google. You can use the Google Gadget Editor directly if you have a Gmail-account. [http://code.google.com/intl/en/apis/igoogle/docs/igoogledevguide.html#gadgethosting | http://code.google.com/intl/en/apis/igoogle/docs/igoogledevguide.html#gadgethosting] In this editor you can create several gadgets and test them. See the Hello World example below. ![image]()
For our gadget we create a new file and start. As starting point and example the OAuth Gadget (http://code.google.com/apis/gadgets/docs/oauth.html) from Google is used and adjustedHere we reference the 3 OAuth endpoints which are created in Part 2 (iGoogle Gadget (featuring UWL,BPM,JSON & OAuth) – Part 2):+http://gadget-doc-examples.googlecode.com/svn/trunk/opensocial- gadgets/popup.js+ and included in our web module from Part 2. Next is the javascript. Here I will explain some main parts and attach the whole source code at the end. h3. *Retrieving the data* The final xml for the gadget can be downloaded from here (http://dl.dropbox.com/u/5925403/uwl_gadget.zip). Store this XML file in your Google Gadget Editor. Name the file uwl.xml for example and save it. ![image]()
Right-click on the name and copy the shortcut. This link we can add to our iGoogle Page. You can do this by going to your iGoogle page and click on the Add Stuff link. In the next page click Add Feed or gadget and past the link to your gadget xml file. ![image]()
And there is the final result. The BPM Tasks from your Universal Worklist inside your iGoogle Page! 
D.
What would very cool would be to combine StreamWork data with the UWL/BPM data. Since StreamWork also supports OAuth you could use the OAuth support in OpenSocial (as shown in your blog) and combine the people-related data from StreamWork with the data coming from UWL. For example, maybe linking the subsitute data from a particular task to the StreamWork user's network.
D.
sounds really nice. But for some reason the layout of the blog is broken, also if I close all comments. Could you check?
As google gadgets is somewhat of a hobby to me, I'd like to mark this article...
Regards,
Benny
Can you explain the layout problem you have? I only get a layout problem when i zoom in with the browser. I did include some extra line breaks now, so maybe that helps.
Regards,
Leo
I wonder, why using "SIGNED" request (
params[gadgets.io.RequestParameters.AUTHORIZATION] = gadgets.io.AuthorizationType.SIGNED) while OAuth service is in use?
Did you plan to use OAuth after all (gadgets.io.AuthorizationType.OAUTH) ?
You are right. It should be
params[gadgets.io.RequestParameters.AUTHORIZATION] = gadgets.io.AuthorizationType.OAUTH;
Copy/Paste error i guess. I changed the blog and the attached file.
Thanks for the notification.
Leo
If you are interested in OpenSocial in the Enterprise context, I have recently published a new open-source named "gadglet". Gadglet is a complete end-to-end platform for Gadgets development. I will publish soon a blog post on how to integrate that into StremWorks... Is it possible to have an opensocial Gadget in any other SAP products ?
See dev.gadglet.com
thanks
Yes, i am very interested. Looking forward to your blog. As for as i know Streamwork is the only SAP product to support opensocial right now.
Cheers,
Leo
Hi Leo,
Thanks for this blog. Nice one.
I'm trying out the steps mentioned in this three part series. However, I couldn't find info about how to build / get the URLs for oAuth section (listed below) in the Gadget XML. Would be great if you can also share more details about how to build the "task_retrieval" object.
<Access url="http://<hostname>:50000/task_retrieval/access_token" method="GET"/>
<Request url="http://<hostname>:50000/task_retrieval/request_token" method="GET"/>
<Authorization url="http://<hostname>:50000/task_retrieval/authorize?oauth_callback=http://oauth.gmodules.com/gadgets/oauthcallback"/>