All communication uses WCF, so there is no direct access to the service application databases. By default, communication between Web servers and serviceapplications in a farm takes place by using HTTP (port 32843), but you can select either HTTP (port 32843) or HTTPS (port 32844). Third-party companies that develop service applications can also implement NetTcpBinding (port 32845) toprovide high-performance communications with WCF clients. NetTcpBinding is generally the best option for services operating inside a firewall, such as on an intranet site. Administrators can use the Service Applications page to change the protocol and port binding for each service application.Communication between service applications and Microsoft SQL Server® takesplace over the standard SQL Server ports or the ports that you configure for SQLServer communication.
Some dependencies are more obvious than others, such as that between functionssuch as People Search and the User Profile Service. If you do not have the ability toimport user information from external sources, such as HR systems, you will notbe able to make the best use of People Search. Others are less obvious. Forexample, Excel Services is dependent on the State Service to provide temporarystorage.
Designing service applications architecture
DESIGNING SERVICE APPLICATIONS IN SHAREPOINT 2010<br />Targer: IT Pros<br />Thuan Nguyen – ICT24H Team<br />Founder of http://sharepointvn.net/<br />Blog: http://thuansoldier.net<br />Twitter: @nnthuan<br />Email: email@example.com<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
I’m focusing on SharePoint 2010 for ITProand Business Adoption by using SharePoint 2010.<br />Specialties<br /><ul><li>SharePoint 2010 ITPro
Share Service Provider in SharePoint 2007<br />The monolithic design meant that all services were available to all Web applications. <br />You could not have a separate service for one Web application<br />There was only one SSP for each farm, which meant that there was a single point of failure. If this SSP failed, all users lost all SSP functionality<br />You could not implement granular services to individual business groups<br />SSP limited the security functionality of SSP<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
Farewell to Shared Service Provider<br />Welcome to Service Application<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
Shared across farms</li></ul>BCS<br />Visio <br />WAC<br />3rd party Service<br />http://itweb/<br />http://hrweb/<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
Service Applications is buffet<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
Service Application in SharePoint 2010<br />Deploy granular services, delivering only the services that are requested for each Web application<br />Design a flexible deployment that provides scalable resilience and security through the implementation of multiple instances of service applications<br />Manage performance by deploying multiple instances of a service application for the same Web application<br />Minimize central IT overheads and provide more effective local management by delegating administration of serviceapplications<br />Share service applications across Web applications.<br />Extend service functionality by deploying third-party service applications such as Microsoft Project Server 2010<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
Service Application Architecture<br />Service: A set of bits installed on a farm that’s capable of providing some functionality.<br />Service Application: A specific farm-level configuration of the Service in SharePoint.<br />Service Instance: An instance of the Service running on an Application server.<br />Service Application Proxy: A pointer to a Service Application that exists on the WFE.<br />Service Consumer: A SharePoint feature, such as a web-part, that talks with the service and makes its functionality available to an end user.<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
SA Proxies<br />A proxy is automatically created for an SA when the SA is created via central admin.<br />It’s a virtual link used to connect web apps to SAs<br />Proxies in the local farm are not created by admins, but they appear along with the SAs in central admin <br />Some proxies might include settings that can be modified<br />- For example, for the Managed Metadata SA, you must indicate which proxy is the default taxonomy store<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
SA Proxy Groups<br />A proxy group is a group of SA proxies that are selected for a web app<br />By default, all SA proxies are included in the default proxy group.<br /><ul><li>You can remove them of course
A single proxy can be in multiple Proxy Groups</li></ul>When you create a web app you can:<br /><ul><li>Select the default proxy group