Saturday, February 9, 2013

SharePoint 2010 Social Aspect

new Social  service app :

when we creating a new instance UPS(user Profile service) app then 3 databases  gets created :
1.Synch database
2.Profile database
3.Social/tagging database.

Have to app pool to run in.
have to deal also with permission

Publish the same .




social2(above)  shows us the how/which to select while picking users from repositories.
Dont do a 'select all' while doing an import from AD etc.
You can specify other filters too.




social1.(above) give the option of 'Synchronization' .
1.There we cans select 'Connection'
and specify the user respository and username/password for the same.
also filters.

2. Profile Import is another  area that can be specified : Incremental/FullSynch.

Behind the scenes its a ForeFront Indentity Mgr that is used  for the  synch work.


socialFIM(above) gives us the location for running the service and how to see the same .
You can see the UI there by dbclicking on it .


socialFIM2(above) gives another shot.






socialWPActivation(above). tells us that the webpart in question can be deployed in 2 ways :

No activation : The wsp solution doesnt get activated
Default : The wsp solution  gets activated on the target site on  deployment .

40:00 to 50:00 tells us all about the deployment and packaging of web parts etc.



socialDllAdding4(above) is used for adding the dlls that are used for User profile service.

system.web
Microsoft.SharePoint.dll
Office.Server
Office.Server.User Profile

WSP builder is a separate toll that can be used for builing for SP2007 and 2010












 
socialCoding5(above) tells us the code that is reqd for the web parts.




socialSynch6(above) gives code for the changes that can accesssed using the
UserProfileChangeToken
UserProfileChangeQuery
objects

So we get the capacbility to go and look at the changed data.
Using the code one can put inplcae queries and also filters for filtering content that needs to be filtered during
any updates/sych etc.



MVP Mathew McDermot. MSDN sample  published

 
socialTimer7(above)

Now we should have an automated way to update data that can be fetched from outside services/systems.Finding twitter feed/linked in profile etc with the right webservice .
So its the idea of having  a Timer Job that will run at the times and look at things -- we can define some character and put in a particular field .eg. ### etc.

Sample shows how to get the connection to linkedin etc. and log the info there at a regular interval.

when to


No comments:

Post a Comment