Configuration and Installation
No configuration is required to get Tweetal up and running, simply drop the war into Tomcat/webapps and register it. There is some optional configuration you can perform, if you so choose (see below).
Optional configuration
By default, Twitter updates will appear to come from Tweetal (as Tweetal is a registered Twitter application). If you want updates to come from a different 'source', you You need to register an application with Twitter and provide the settings to the portlet. Fill out this form: http://twitter.com/oauth_clients/new
Be sure to choose 'client' as the Application type, NOT 'browser'. When user's link their account they will be prompted to enter a code into Tweetal, that will then be verified and their own access token and secret stored as preferences. Once you have filled out the form, add the key and secret supplied to your application as belowportlet using Config mode:
Code Block | ||||
---|---|---|---|---|
| ||||
<init-param>
<name>consumerKey</name>
<value>YOUR_CONSUMER_KEY_HERE</value>
</init-param>
<init-param>
<name>consumerSecret</name>
<value>YOUR_CONSUMER_SECRET_HERE</value>
</init-param> |
Code Block | ||||
---|---|---|---|---|
| ||||
<context-param>
<param-name>consumerKey</param-name>
<param-value>YOUR_CONSUMER_KEY_HERE</param-value>
</context-param>
<context-param>
<param-name>consumerSecret</param-name>
<param-value>YOUR_CONSUMER_SECRET_HERE</param-value>
</context-param>
|
DO NOT reset these keys without updating the values in the portlet, as the integration will no longer function if they are out of sync (they are essentially your application's username and password).
When user's link their account they will be prompted to enter a code into Tweetal, that will then be verified and their own access token and secret stored as preferences.