Export (0) Print
Expand All
0 out of 1 rated this helpful - Rate this topic

Connect to service applications on remote farms in SharePoint 2013

Published: September 25, 2012

Summary: Learn how to connect to and consume a published service application in SharePoint 2013.

Applies to:  SharePoint Server 2013 | SharePoint Foundation 2013 

In SharePoint 2013, you can publish some service applications to make them available over remote connections. By publishing a service application, you can optimize resources and avoid redundancy, and provide enterprise-wide services without installing a dedicated enterprise services farm.

You can connect to a service application that has been shared by another farm if you know the address of the farm's discovery service or the address of the service application. Be aware that you can only connect to a service application on a remote farm if the farm administrator for the remote farm has published the service application. For more information about the process of sharing service applications across farms see Share service applications across farms in SharePoint 2013.

In this article:

Before you begin

Before you begin this operation, review the following information about prerequisites:

note Note:

Because SharePoint 2013 runs as websites in Internet Information Services (IIS), administrators and users depend on the accessibility features that browsers provide. SharePoint 2013 supports the accessibility features of supported browsers. For more information, see the following resources:

To connect to a service application on a remote farm by using Central Administration

  1. Verify that you are a member of the Farm Administrators SharePoint group.

  2. On a server in the consuming farm, on the SharePoint Central Administration website, click Application Management, and then click Manage service applications.

  3. On the ribbon, click Connect.

  4. On the Connect drop-down menu, click the kind of service application to which you want to connect.

  5. On the Connect to a Remote Service Application page, type the appropriate URL in the Farm or Service Application address text box, and then click OK.

    note Note:

    You can obtain the URL from the administrator of the publishing farm. For more information, see Publish service applications in SharePoint 2013. There are two kinds of URLs that you can use in this step: either the URL of the service application or the URL of the remote farm’s topology service application. If you use the URL of the service application, only the corresponding service application will be listed in Step 6 of this procedure. If you use the URL of the topology service, all service applications in the farm will be listed in Step 6 of this procedure.

  6. The new Connect to a Remote Service Application dialog box displays the service applications that match the URL that you typed in Step 5. Click the row that contains the name of the service application, and then select the check box to add the service application connection to the farm’s default list of service application connections (that is, the default proxy group). Click OK.

  7. You are prompted to change the connection name. Type a new name into the Connection Name text box or leave the default name, and then click OK.

  8. We recommend that you use the instructions in Exchange trust certificates between farms in SharePoint 2013 to establish trust between the two farms.

  9. After the new connection is created, you must click OK to complete the procedure.

  10. Associate the new service application connection with a local Web application. For information about how to do this, see Add or remove service application connections from a web application in SharePoint 2013.

To connect to a service application on a remote farm by using Windows PowerShell

  1. Verify that you have the following memberships:

    • securityadmin fixed server role on the SQL Server instance.

    • db_owner fixed database role on all databases that are to be updated.

    • Administrators group on the server on which you are running the Windows PowerShell cmdlets.

    • Add memberships that are required beyond the minimums above.

    An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

    note Note:

    If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions. For additional information about Windows PowerShell permissions, see Add-SPShellAdmin.

  2. Start the SharePoint 2013 Management Shell.

    • For Windows Server 2008 R2:

      1. On a server in the consuming farm, on the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

    • For Windows Server 2012:

      • On a server in the consuming farm, on the Start screen, click SharePoint 2013 Management Shell.

        If SharePoint 2013 Management Shell is not on the Start screen:

      • Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

    For more information about how to interact with Windows Server 2012, see Common Management Tasks and Navigation in Windows Server 2012.

  3. At the Windows PowerShell command prompt, type the following command:

    Receive-SPServiceApplicationConnectionInfo -FarmUrl <PublishingFarmTopologyURL>
    

    Where:

  4. At the Windows PowerShell command prompt, type the following command:

    New-SP*ServiceApplicationProxy -Name " <ServiceApplicationProxyName>" -Url "<PublishingFarmTopologyURL>"
    

    Where:

    • <ServiceApplicationProxyName> is a unique name for a service application connection on the consuming farm.

    • <PublishingFarmTopologyURL> is the service application topology URL that was also used in the previous command.

    Each kind of service application has a specific Windows PowerShell 3.0 cmdlet that should be used instead of New-SP*ServiceApplicationProxy. (These cmdlets are listed in the See Also section.) For example, the following command creates a new Managed Metadata service application proxy named "MetadataServiceProxy1" that connects to the service application located at the stated URL.

    New-SPMetadataServiceApplicationProxy -Name "MetadataServiceProxy1" -Uri "
    urn:schemas-microsoft-com:sharepoint:service:9c1870b7ee97445888d9e846519cfa27#authority=urn:uuid:02a493b92a5547828e21386e28056cba&authority=https://ua_powershell:32844/Topology/topology.svc  "
    
  5. You must associate the new service application connection with a local Web application. For information about how to do this, see Add or remove service application connections from a web application in SharePoint 2013.

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.