Advantages of SharePoint 2010 Service Application over SSP

In SharePoint 2010, Shared Service Providers (SSP's) are replaced by Service Applications. Services are no longer combined into a SSP. They run independently as a service application. The service application architecture is now also built into Microsoft SharePoint Foundation 2010, in contrast to the Shared Services Provider (SSP) architecture that was only part of Office SharePoint Server 2007.

A key benefit here is that all services are installed by default and there is no SSP setup.

• The services architecture is extensible, allowing third-party companies to build and add services to the platform.
• Services are managed directly in Central Administration (rather than a separate administration site).
• Services can be monitored and managed remotely.
• Services can be managed and scripted by Windows PowerShell.
• Shared services communications take place over HTTP(S). Shared services do not directly access databases across farms.
• Most new services are built on the Windows Communications Framework. They have optimization built into their protocol, using binary streams instead of XML for data transfer. Test results show improvements in network throughput with this change.

Advantages of Service Applications over SSP

The key limitation of the SSP architecture was that it was configured by using a set of services, and all web applications associated with the SSP bore the overhead of all the services even if they weren't being used. To change the service configuration for a particular Web application, a new SSP would have to be created.

The service application architecture on the other hand, allows a set of services to be associated with a given Web application and a different set of services to be associated with another Web application. Also, the same service application can be configured differently in different Web applications; therefore, Web sites can be configured to use only the services that are needed, rather than the entire bank of services.

One major advantage to this new architecture is the flexibility in scaling service applications up and out. Another advantage is that service application to other farms. To do this you simply install the service application's proxy in the other farm and point it to a specific URI provided by Central Administration when you publish the service application. This enables enterprises to have dedicated service farms that can be specially configured based on the services that are provided. They could then share these service offerings with other SharePoint farms in the enterprise or with customer farms.

Reference:

http://www.c-sharpcorner.com/uploadfile/Roji.Joy/advantages-of-sharepoint-2010-service-application-over-ssp/

How to connect to a Service Application on a remote form in SharePoint 2010

In this article we will be seeing how to connect to a Service Application on a remote form in SharePoint 2010.

The Publisher farm is the farm in which the Service application is running and the Consumer farm is the farm which will consume data from the publishing farm.

Connect to a service application on a remote farm:

I. In the consuming farm, go to the Central Administration->Application Management->Manage Service Applications.


ii. In the Ribbon click on Connect.



iii. Enter the URL that we got when we published the Managed Metadata Service in the publishing farm.


iv. Click OK.


v. Click the Managed Metadata Service and check the Add this service application's proxy to the farm's default proxy list.

vi. Click OK.


vii. Enter the Connection Name and click OK.

viii. Now go and check it in the Central Administration->Application Management->Manage Service Applications.


ix. You could see the Service application that we have published in the publishing farm.

Thus we have successfully connected to a Service application on a remote farm in SharePoint 2010.

Reference:

http://www.c-sharpcorner.com/uploadfile/anavijai/how-to-connect-to-a-service-application-on-a-remote-form-in-sharepoint-2010/

Introduction to Service Application Framework in SharePoint 2010

What is Service Application Framework?

• Replacement for the Shared Services Provider  in MOSS 2007
• API provided by backend application servers and consumed by front-end application servers.
• Used for developing middle-tier applications that are hosted in SharePoint and provide data and resources to other SharePoint features
• Enables services to be shared between computers on a server farm
• Load balance and manage services
• Out of the box - 20 built in services
• Certain objects automatically backed up and restored
• Ideal for deploying, managing and discovering WCF service clients and endpoints.
• Windows Powershell support
• Timer job infrastructure available at Service-scope
• Use of SharePoint configuration store and support for storing data in SharePoint managed custom database is available.

Load Balancing

• Use Round robbing load balancing
• Service application proxy method invocations must be routed thru the front end web server to an appropriate app server by using a load balancing tool.
• Calls between frontend and app servers to require separate external load balancer than the load balancing for front-end web servers
• SPRoundRobinServiceLoadBalancer can be enhanced or replaced by third party

Management and Administration

• Services plug their management UI into SharePoint Service Management page
• Common admin tools such as upgrade, backup, restore and account management
• Common UI to manage, start, stop, group, associate, federate and backup SharePoint services.
• Can define specialized admin roles and can be delegated to users who are not farm admins
• Security trimmed

Security

• Claims-based identity model

Example - Search service
Benefits
The Service Application Framework allows developers to provide load balanced middle-tier resources that can be managed through SharePoint and leverage the full power of SharePoint 2010.
NOTE: These notes are based on the Microsoft documentation on SharePoint 2010 and is subject to change.
Reference:

http://www.c-sharpcorner.com/uploadfile/DipalChoksi/introduction-to-service-application-framework-in-sharepoint-2010/

How to publish a Service Application in SharePoint 2010

In this article we will be seeing how to publish a Service Application in SharePoint 2010.

In MOSS 2007 we had SSP that cannot be shared across farm levels. But in SharePoint 2010 a new feature have been introduced "Service Applications" which can be shared across farm levels, for that we need to create a Service Application and that has to be published so that it can be used by other farms. In this we will be seeing how to publish a Managed Metadata Service.

Publish a Service Application:

I. Go to the Central Administration->Application Management->Manage Service Applications.



ii. Select Managed Metadata Service.

iii. In the Ribbon click on Publish.

iv. Publish Service application model popup will be opened.


v. Select the Connection Type that you want from the drop-down list.

vi. If you want the service application to be available to remote farms, select the check box for Publish this Service Application to other farms.

vii. In the Trusted farms column click the link you could see the trust relationship between farms that you have created(How to create Trust relationship go to this article)

viii. Copy the Published URL which should be provided by the consuming farm when connecting to the publishing farm.

ix. The Publisher farm is the farm in which the Service application is running and the Consumer farm is the farm which will consume data from the publishing farm.

x. Click OK.

Set permission to the published service application for a consuming farm:

I. In the publishing farm go to Start menu.

ii. Go to SharePoint 2010 Management Shell and select Run as Administrator.

iii. In the command prompt, type each of the following commands.



iv. The above command is used to get the farm id.

v. Save the farm id.

vi. Go to the Central Administration->Application Management->Manage Service Applications.



vii. Click on Managed Metadata Service.



viii. In the Ribbon select Permissions.



ix. Enter the farm id that you got from step 3 and click Add.

x. In Permissions for Local Farm, select the Full Access to Term Store.

xi. Click OK.

Thus we have published a Managed Metadata Service Application; the other farms can connect to this Service Application. This is one of the best features in SharePoint 2010 so that we no need to create the same service application in another farm.

Reference:

http://www.c-sharpcorner.com/UploadFile/anavijai/how-to-publish-a-service-application-in-sharepoint-2010/

Connecting a Service Between Publishing SharePoint 2013 and Consuming SharePoint 2010 Farm

This article defines how to connect a service between publishing a SharePoint 2013 and consuming a SharePoint 2010 Farm.
The first step: You need to establish a trust relationship between the two farms:

1. On SharePoint 2010 Farm Application Server
   Export the Farm and STS certificates from the SharePoint 2010 farm:
    
   $rootCertificate = (Get-SPCertificateAuthority).RootCertificate
   $rootCertificate.Export("Cert") | Set-Content C:\Certificates\2010FarmRoot.cer -Encodingbyte
   $stsCertificate = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate
   $stsCertificate.Export("Cert") | Set-Content C:\Certificates\2010FarmSTS.cer -Encodingbyte
   
   
    
2. On SharePoint 2013 Application Server
   Export the Farm certificate from the SharePoint 2013 Farm:
    
   $rootCertificate = (Get-SPCertificateAuthority).RootCertificate
   $rootCertificate.Export("Cert") | Set-Content C:\Certificates\2013FarmRoot.cer -Encodingbyte
   
   
     
3. Import the SharePoint 2013 certificate into the SharePoint 2010 Farm:
   On the SharePoint 2010 Farm Application Server execute the following commands:
    
   $trustCertificate = Get-PfxCertificate C:\Certificates\2013FarmRoot.cer
   New-SPTrustedRootAuthority"2013 Trust"-Certificate $trustCertificate
   
   
    
4. Import the SharePoint 2010 into the SharePoint 2013 Farm:
   On the SharePoint 2013 Farm Application server execute the following commands:
    
   $trustCertificate = Get-PfxCertificate C:\Certificates\2010FarmRoot.cer
   New-SPTrustedRootAuthority"2013 Trust" -Certificate $trustCertificate
   $stsCertificate = Get-PfxCertificate C:\Certificates\2010FarmSTS.cer
   New-SPTrustedServiceTokenIssuer"2013 Trust" -Certificate $stsCertificate
   
   

Second Step: You need to publish the Search Service Application and set the permissions:
Publishing a Service Application

1. Go to a publishing server whose service you want to publish and use in other farms, open Central Administration. (here SharePoint 2013)
2. Go to Application Management and then move to Manage Service Applications.
3. Click to the right of the service application that you want to publish, clicking on the application will open its features; be sure to click on it right.
4. On the SharePoint Ribbon, click on the Publish. Feature.
   
   
   
5. On the next page check the option "Publish this Service Application to other farms" .
   
   
   
6. Now we must copy the entire URL: It will begin with "urn:" and end with ".svc".
   urn:schemas-microsoft-com:sharepoint:service:ff3af89454dd41c1bb484a393e008d61#authority=
   urn:uuid:2ea153147ceb4afa86104ff5f8f1b6a1&authority=https://xxxxx:32844/Topology/topology.svc 
   
   
7. Make it ok and proceed.
8. Again do the same step as step C.
9. On the SharePoint Ribbon, click on Permission.
   
   
   
10. Provide the Farm Id of the consuming farm, you can find it as:  In Powershell type. (Here in the SharePoint 2010 farm.)
    
    Get-SPFarm | Select Id
    Result :-  xxxxx-xxxxx-xxxxx-xxxxxxx
     
11. Add the same into the SharePoint 2013 farm.
12. Click the farm id you entered, for the permission.
    
    
    
13. Add the same into the SharePoint 2013 Farm.
14. Click the farm id you entered, for the permission.

Now the part of publishing farm is over, we must enter the URL in the consuming farm to use the service:

1. Go to a Consuming server where the publishing service needs to be used, open Central Administration.
2. Go to Application Management and then move to Manage Service Applications.
3. On the SharePoint Ribbon, click on Connect.
4. Pass the URL for the service application you have taken in Step (f) of the publishing server and press OK.
   
   
   
5. Highlight the service application by clicking on it.
6. Here you have an option to choose, whether or not to include this service application in the default service application group. Click OK once done.
   
   

Now when all the stuff is over you can use the service application of a farm just as a locally hosted service application of your farm.

Now, go into your 2013 SSA, add a SharePoint 2010 content source and run a full crawl. Once the crawl is completed, you will be able to search the content using your 2010 Search Center.


To edit a service connection group using Central Administration (on the consuming farm) (in our case the SharePoint 2010 Farm):

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2. On the Central Administration Home page, click Application Management.
3. On the Application Management page, in the Service Applications section, click Configure service application associations.
4. On the Service Application Associations page, select Web Applications from the View drop-down menu.
5. 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.
6. 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.
   
   

Search result in SharePoint 2010 site using SharePoint 2013 Farm Search Service application

Reference:

http://www.c-sharpcorner.com/UploadFile/0d4a67/connecting-a-service-between-publishing-sharepoint-2013-and/