You can use the Cloud Connector Connection Manager UI to establish your connection or the follwing xml-based sample connection file for replication:
<?xml version="1.0" encoding="utf-8" ?>
<connection xmlns="http://www.layer2.de/schemas/cloudConnections" interval="60" version="1.2" enabled="true">
selectStatement="Select * from FriendsTimeline">
User [email protected]
<fieldMappings autoMapping="true" >
<field entity="Twitter" name="Text"/>
<field entity="SharePointDestination" name="Title" />
Twitter API and RSSBus provider has changed.
For current connection string options see here:
The RSSBus Twitter Driver for ADO.NET is used as 3rd party data source provider. You can use several views to access certain feeds, search for keywords, connect the followers list or the list of persons you are follow. See documentation for this. This example uses an Office 365 list as data destination. Updates are every hour in this case, but can be done more frequently if required.
Fig.: Twitter feed fully integrated in a native SharePoint list.
- After synchronization with Cloud Connector you have the Twitter content in a native SharePoint list, on-premise or in the cloud. That means, you have full integration with search, lookups, workflow, RSS, email notification etc. You can place list web parts wherever you want. In this way you have a much deeper integration, compared to web parts that display tweets only.
- Starting with V3.6 you can use the "disable delete" option on the SharePoint data entity to not delete previous entries, e.g. to implement a Twitter feed archive.
In the same way you can replicate almost any data sources to almost any destinations using the Cloud Connector. Here is a sample configuration file entry, that replicates Twitter to a SQL Server table TwitterFeed:
connectionString="Data Source=srvsql01; Initial Catalog=Northwind; User Id=MyUserID; Password=MyPassword"
selectStatement="Select * from TwitterFeed">