locked
Does the User Profile Service Application have a required dependency on the Managed Metadata Service? RRS feed

  • Question

  • I'm trying to find out of the Managed Metadata Service is required to exist in the farm (or be consumed from another farm) in order for the User Profile Service Application to function, noting however that none of the social features of the UPA that would require Managed Metadata are required and:

    • Notes and tagging are disabled
    • There are no My Sites in the farm
    • There is no need to share content types
    • There is no business need for terms, term sets, or enterprise keywords

    Basically there is no business requirement for the Manged Metadata service and it is desired to not have to create the service if it's not needed. However I'm not 100% sure as to whether the User Profile Service Application has a requirement for the service, even if you are not using the dependant features.

    The User Profile service application overview (SharePoint Server 2010) says that metadata is related but doesn't say whether it is required even if you're not making use of the service.

    The confusion is because in an out of the box farm with metadata and user profiles configured, terms from the Job Title profile property get populated into the metadata service. This happens automatically with no configuration (beyond setting up the two services and the profile synchronization). Are there issues if the metadata service does not exist? Will the user profile service application complain?


    Jason Warren
    Infrastructure Specialist


    • Edited by Jason Warren Thursday, May 31, 2012 3:18 PM added link to documentation
    Thursday, May 31, 2012 3:14 PM

All replies

  • Hi Jason,

    When deploying full range of social computing features in SharePoint, you SHOULD use Managed Metadata functionality together. In this case, Managed Metadata Service application is responsible for serving terms already associated to an user's profile when you need to complete an user profile information in My Site, such as Ask Me About, Country....

    1. Are there issues if the metadata service does not exist? >>> In my humble opinion, there is not any issue if you don't even enable Managed Metadata service. For example, I don't want to build a taxonomy architecture. I just want to combine User Profile with Search Service application because my boss needs to search People. However, it would be good if he can use terms in Ask Me About like SharePoint, Leadership Skill, Finance, Accounting ..
    2. Will the user profile service application complain? >>> The User Profile service application will not complain. I have never got any complaint so far from User Profile service application whilst not using Managed Metadata service application

      User Profile can be run independently. It doesn't depend on Managed Metadata, vice versa. However, to maximum utilize SharePoint capability namely Social Computing solution, you should combine these service applications together. Search Service application is required if you want to integrate Searching People for Social functionality purpose as well.

      My $.02

      Regards,

      T.s


      SharePoint Vietnam | Blog | Twitter


    Thursday, May 31, 2012 3:45 PM
  • Thanks Thuan, your thoughts match up to my understanding. What I can't seem to figure out is whether the user profile service application needs the metadata service to function.

    Let me be clear: The decision is the farm will be limited by design. None of the features that the metadata service offered are desired in this particular farm, nor are the user profile features that rely on the managed metadata service.

    My observations however show that in an out of the box installation with no additional configuration, the user profile service application will create terms in the metadata service without any intervention or configuration from the user (the example I'm using are values that are synchronized from the Job Title attribute in Active Directory). What I'm trying to understand is if this behaviour is required for the user profile service to function, and whether the decision to not create a managed metadata service in the farm will cause issues with the user profile service application (beyond the obvious reduction of features) if the user profile service application needs to create these terms.



    Jason Warren
    Infrastructure Specialist

    Thursday, May 31, 2012 3:56 PM
  • Hi Jason,

    The answer is 'No'. The Managed Metadata service is not required for the User Profile Service to function. However, "If the Managed Metadata service is not associated with the User Profile service application, features such as social tagging and properties backed by managed terms do not work."

    Cheers,

    Yousef

    Thursday, May 31, 2012 6:59 PM
  • Are there any details around the adding of profile property values into the metadata service? Will the user profile service application still attempt this if there is no associated managed metadata service (specifically if it doesn't exist)?

    Jason Warren
    Infrastructure Specialist

    Thursday, May 31, 2012 7:33 PM
  • Sorry, to clarify, it's not the social features that I am worried about. There appears to be some integration between the two services (the values of synchronized user properties appear in the managed metadata service) and I feel that without understanding or acknowledging this (what appears to me) undocumented connection, the simple answer of "no" doesn't hold up.

    Jason Warren
    Infrastructure Specialist

    Thursday, May 31, 2012 11:29 PM