Downloading and installing Wookie
See downloading and installing Wookie
Using the Administration web interface
To access the administrators interface in the development server, go to
http://\{your server}/wookie/admin
By default, and when Wookie is running in "standalone" mode, the Wookie server admin username and password are both "java".
Adding and removing widgets
Adding widgets using the admin interface
Adding widgets using a watched folder
Wookie supports the "hot deployment" of widgets by adding .wgt files to a watched folder. The location of the folder is determined by the widget.deployfolder property. Hot-deploy functionality is enabled by default; you can disable it if desired by setting widget.hot_deploy=false. Note that only widgets that have a .wgt file extension will be deployed automatically.
Removing widgets
Widget services (categories)
Whitelist
Server configuration
User management
The Wookie server comes with a built-in user called "java" linked to the "widgetadmin" role. These are defined in the roles.properties and users.properties files located in WEB-INF/classes. These can be removed in a standard application server environment, and another user added to "widgetadmin" role, for example in tomcat-users.xml in a Tomcat installation.
Login configuration settings can be found in the web.xml file located in wookie/WEB-INF.
Integration with Shindig
Proxy configuration
In order for widgets running in Wookie to communicate with external web services using Ajax, requests must be redirected through a server-side proxy. The proxy configuration is located in WEB-INF/classes/widgetserver.properties.
The following parameters can be set:
widget.proxy.usewhitelist=true|false
Set this to true to enable a whitelist; this only works with the Wookie built-in proxy service.
widget.proxy.checkdomain=false|true
If this is set to true, the Wookie built-in proxy will only handle requests where the requesting domain is the same as the proxy server domain.
widget.proxy.scheme=
widget.proxy.hostname=
widget.proxy.port=
widget.proxy.path=
These allow you to set a custom proxy server location. To use the Wookie built-in proxy service, you only need to set widget.proxy.path=/wookie/proxy. To use instead the proxy service bundled with Apache Shindig, you need to set widget.proxy.path=/gadgets/proxy
widget.proxy.username=
widget.proxy.password=
widget.proxy.usentlmauthentication=false|true
Use these settings to configure access control for the proxy. By default no authentication is set.
Mail setup
Wookie enables users to request API keys for their applications; these are then sent to their email address. The email service is configured as follows:
widget.email.server=your_mail_server
widget.email.port=25
widget.email.username=username
widget.email.password=password
Username and password are optional. You can use localhost if your server is set up to send email, e.g. using PostFix.