Skip to main content

Setting up a managed metadata service application to server one or more web applications

Found article at
http://www.lamber.info/post/2010/12/12/Setting-up-a-managed-metadata-service-application-to-server-one-or-more-web-applications.aspx


Assigning two or more managed metadata service applications to a single web application

You are also able to assign multiple service applications to a single web application. When doing so with a managed metadata service application, however, you have to consider some settings before proceeding.
Imagine that you have to maintain two separate managed metadata service applications for two different departmental projects. You can do this by creating two separate managed metadata service applications and assign them to the corresponding web applications. After a while, you need to combine both service applications for a single web application. You can do this by following the same steps as seen in the previous scenario. Choose the service applications that you want to consume in your web application by selecting a proxy group or defining your custom selections.
You can do this, however, you have to consider following when assigning multiple managed metadata service applications to a single web application:
  1. both term stores (service applications) with managed terms are available for your web application
  2. both term stores can provide content-type hub syndication
  3. the already stored enterprise keywords of both term stores are served to your web application, however, only one term store of both can be your default storage location for your keywords
  4. the already stored column specific term sets of both term stores are served to your web application, however, only one term store of both can be your default storage location of your column specific term sets
Everything except the storage of enterprise keywords and column specific term sets function properly. This happens if both managed metadata service applications are configured to be the default term stores. You might encounter following error message when inserting a new enterprise keyword:
Therefore, plan carefully before separating managed metadata service applications. You have to ensure that only one of both term stores is the default term store for the web application. You can make the changes in the managed metadata service connection settings:
  • open the central administration
  • Application management –> Manage service applications
  • select the row of type Managed Metadata service Connectionof your metadata service application
  • press Properties in the ribbon bar
  • choose This service application is the default storage location for Keywords and This service application is the default storage location for column specific term sets
If you already have a default term store in the farm you will get this error message:

Now, it is up to you to ensure that you do not use two default term stores on the same web application. Please note that disabling these settings is a farm wide setting.

Comments

Popular posts from this blog

How to get SPUser or SPGroup from Person or Group field

You have person or group field in SharePoint list and you want to programmatically get the user or person. The below code to gets SPUser from User or Group field in the list when multiple choice and Groups are not allowed in the field: //get SPUser SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValue userFieldValue = (SPFieldUserValue)userField.GetFieldValue(item["Users"].ToString()); SPUser user = userFieldValue.User; This part of code would help you to get SPUser when multiple choice is allowed and groups are not allowed: //Multiple choices are allowed SPFieldUser userField = (SPFieldUser)item.Fields.GetField("Users"); SPFieldUserValueCollection userFieldValueCollection = (SPFieldUserValueCollection)userField.GetFieldValue(item["Users"].ToString()); foreach (SPFieldUserValue userFieldValue in userFieldValueCollection) {     Console.WriteLine("     " + userFieldValue.User.LoginName); } And when group...

SharePoint publishing page scheduling

In SharePoint 2010 publishing enabled team site collection is not showing schedule button in publish ribbon. Solution: Here is how to enable it  though the UI: Locate the SharePoint Server Web site on which you want to enable content approval and item scheduling. Click  Site Actions , click  Site Settings , and then click  Modify Pages Library Settings . Under  General Settings , click  Versioning Settings . Click  Yes  next to  Content Approval , and then click  OK . Click  Manage item scheduling .   Click to enable the  Enable scheduling of items in this list  check box, and then click  OK .

Changing Content Type Hub URL

Change the Hub URL through powershell by using: Set-SPMetadataServiceApplication -Identity " " -HubURI " " For Ex: Set-SPMetadataServiceApplication -Identity "Managed Metadata Service" -HubURI "http://contenttype.Domain.Com" When you try to do this you get this rather scary message: This is SharePoint telling you that this is a major thing so be careful! Essentially all your content types that you have published out will be removed if they can, and you have to republish all of your content types out again which can cause some issue.