...
Once deployed, you need to setup Wookie as follows:
In \ [WOOKIE\]/WEB-INF/classes/widgetserver.properties, set widget.metadata.url to point to the Shindig metadata service (if you've set up Shindig at Root, this is already set) Wiki Markup
In \ [WOOKIE\]/WEB-INF/classes/opensocial.properties, set opensocial.enable to true to start sending Shindig security tokens with rendered widgets/gadgets. Wiki Markup
Shindig/Wookie features
You can use Wookie to manage the preferences of your Gadgets; to do this you must replace the standard Shindig Features jar with one with some additional Wookie javascript code and make an adjustment to the web.xml for Wookie to allow calls between the two applications.
...
(You can also avoid this problem by merging the Wookie and Shindig applications into a single webapp, combining the web.xml files into one.)
Proxy configuration
Note that both Wookie and Shindig come with proxy implementations. You can use either or both of these. The setting for W3C widgets can be found in \ [WOOKIE\]/WEB-INF/classes/widgetserver.properties. The setting for Google Gadgets/OpenSocial Apps can be found in \ [SHINDIG\]/WEB-INF/classes/containers/default.container.js. In each case you can set the proxy URL to either: Wiki Markup
\[WOOKIE\]/proxy
\ Wiki Markup
[SHINDIG\]/gadgets/proxy