In SharePoint 2013, some service applications can be shared across server farms.
By publishing a service application, you can optimize resources, avoid redundancy, and provide enterprise-wide services without installing a dedicated enterprise services farm. You can publish the following service applications in a SharePoint 2013 farm:
Additionally, a SharePoint 2010 farm can consume services from a SharePoint 2013 Server farm. This allows for upgrade of multi-farm environments in which a farm hosting service applications is upgraded first. In this scenario, the service applications and features that the SharePoint 2010 farm experiences are limited to those that are available in SharePoint 2010. For example, a SharePoint 2010 farm cannot consume the Machine Translation service application from a SharePoint Server 2013 farm and does not benefit from the new features of the User Profile service application.
The User Profile service must reside in the same datacenter as the content it supports — The performance of social features require the User Profile service application to be located in the same datacenter as My Sites, team sites, and community sites.
The farm that contains the service application and publishes the service application so that other farms can consume the service application is known as the publishing farm. The farm that connects to a remote location to use a service application that the remote location is hosting is known as the consuming farm.
Exchange trust certificates between the farms.
To start, an administrator of the consuming farm must provide two trust certificates to the administrator of the publishing farm: a root certificate and a security token service (STS) certificate. Additionally, an administrator of the publishing farm must provide a root certificate to the administrator of the consuming farm. By exchanging certificates, each farm acknowledges that the other farm can be trusted.
By default, a new service application connection is added to the farm’s Default group of service application connections when you create the service application by using Central Administration. You can override this default membership. If a new service application is created by using Windows PowerShell 3.0 instead of by using Central Administration, the new service application does not automatically become a member of the Default service application connections group unless the default parameter is supplied.
To edit a service connection group by using Central Administration
Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
Start SharePoint 2013 Central Administration.
For Windows Server 2008 R2:
Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
For Windows Server 2012:
On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.
For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.
On the Central Administration Home page, click Application Management.
On the Application Management page, in the Service Applications section, click Configure service application associations.
On the Service Application Associations page, select Web Applications from the View drop-down menu.
In the list of Web applications, in the Application Proxy Group column, click the name of the service application connection group that you want to change.
To add a service connection to the group, select the check box that is next to the service application that you want to add to the connection group. To remove a service application connection from the connection group, clear the check box next to the service application that you want to remove from the connection group. When you have made the changes that you want, click OK.
By publishing a service application, you can optimize resources, avoid redundancy, and provide enterprise-wide services without installing a dedicated enterprise services farm. You can publish the following service applications in a SharePoint 2013 farm:
Additionally, a SharePoint 2010 farm can consume services from a SharePoint 2013 Server farm. This allows for upgrade of multi-farm environments in which a farm hosting service applications is upgraded first. In this scenario, the service applications and features that the SharePoint 2010 farm experiences are limited to those that are available in SharePoint 2010. For example, a SharePoint 2010 farm cannot consume the Machine Translation service application from a SharePoint Server 2013 farm and does not benefit from the new features of the User Profile service application.
The User Profile service must reside in the same datacenter as the content it supports — The performance of social features require the User Profile service application to be located in the same datacenter as My Sites, team sites, and community sites.
The farm that contains the service application and publishes the service application so that other farms can consume the service application is known as the publishing farm. The farm that connects to a remote location to use a service application that the remote location is hosting is known as the consuming farm.
Exchange trust certificates between the farms.
To start, an administrator of the consuming farm must provide two trust certificates to the administrator of the publishing farm: a root certificate and a security token service (STS) certificate. Additionally, an administrator of the publishing farm must provide a root certificate to the administrator of the consuming farm. By exchanging certificates, each farm acknowledges that the other farm can be trusted.
By default, a new service application connection is added to the farm’s Default group of service application connections when you create the service application by using Central Administration. You can override this default membership. If a new service application is created by using Windows PowerShell 3.0 instead of by using Central Administration, the new service application does not automatically become a member of the Default service application connections group unless the default parameter is supplied.
To edit a service connection group by using Central Administration
Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
Start SharePoint 2013 Central Administration.
For Windows Server 2008 R2:
Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.
For Windows Server 2012:
On the Start screen, click SharePoint 2013 Central Administration.
If SharePoint 2013 Central Administration is not on the Start screen:
Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.
For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.
On the Central Administration Home page, click Application Management.
On the Application Management page, in the Service Applications section, click Configure service application associations.
On the Service Application Associations page, select Web Applications from the View drop-down menu.
In the list of Web applications, in the Application Proxy Group column, click the name of the service application connection group that you want to change.
To add a service connection to the group, select the check box that is next to the service application that you want to add to the connection group. To remove a service application connection from the connection group, clear the check box next to the service application that you want to remove from the connection group. When you have made the changes that you want, click OK.
