Designing service applications architecture

1,245 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
1,245
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • 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

    1. 1. 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: nguyenthuan@ict24h.net<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    2. 2. I’m focusing on SharePoint 2010 for ITProand Business Adoption by using SharePoint 2010.<br />Specialties<br /><ul><li>SharePoint 2010 ITPro
    3. 3. Business Adoption
    4. 4. Writting</li></ul>2ND SHAREPOINT SATURDAY VIETNAM<br />
    5. 5. Session Objects<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    6. 6. Farewell to the Shared Services Provider<br />SSP<br />Profiles<br />Search<br /><ul><li>Not extensible
    7. 7. Not flexible</li></ul>Excel Calc<br />BDC<br />Monolithic architecture<br />http://hrweb/<br />http://itweb/<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    8. 8. 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 />
    9. 9. Farewell to Shared Service Provider<br />Welcome to Service Application<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    10. 10. SERVICE APPLICATION<br /><ul><li>Extensible
    11. 11. Flexible</li></ul>Search<br />UserProfiles<br />Excel Calc<br /><ul><li>Single farm
    12. 12. 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 />
    13. 13. Service Applications is buffet<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    14. 14. 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 />
    15. 15. SERVICE APPLICATIONS<br />
    16. 16. Single Farm services vesus Cross-Farm services<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    17. 17. 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 />
    18. 18. 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 />
    19. 19. 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
    20. 20. 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
    21. 21. Create a custom proxy group by selecting
    22. 22. Which SA proxies should be included</li></ul>The custom proxy group for one web app cannot be reused with a different web app<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    23. 23. Hosting multiple tenants in 2010<br />The ability to uniquely separate each customer on a shared environment<br />1<br />2<br />SA<br />WA<br />Tenant 1<br />Tenant 2<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />SC<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    24. 24. Multi-Tenant for Hosting Provider<br /><ul><li>Services can be configured to “share” data across Tenants or to “partition” data for each tenant (data isolation)
    25. 25. Allows multiple organizations to be ‘hosted’ on the same SharePoint configuration, but keeps their data isolated
    26. 26. Configurable ‘per-service’ to allow for “Mixed-Mode Partitioning”</li></ul>Data<br />Partition A<br />Partition B<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    27. 27. DESIGNING SERVICE APPLICATION ARCHITECTURE<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    28. 28. IT COMES TO BUSINESS REQUIREMENT<br />Can you?<br />I can<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    29. 29. Planning?<br />Service Application Dependencies<br />Service Application Components<br />“Translate” Business Requirement to SA<br />Logical Architecture for Service Application<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    30. 30. Service Application Dependencies<br />Just example<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    31. 31. Service Application Components<br />Service Application Connection <br />(aka Proxy)<br />Service Application Proxy Group<br />Service Application Databases<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    32. 32. Where is your pen and paper?<br />Worksheet 1<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    33. 33. Worksheet 2<br />0 = No √ = Yes<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    34. 34. LOGICAL ARCHITECTURE<br />Using Planning Worksheet for designing Logical architecture<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    35. 35. Small – Medium Organization<br /><ul><li>< 5000 users
    36. 36. Mainly uses Collaboration, Search
    37. 37. 1 – 3 IT Staff spanning multiple roles.</li></ul>Business Requirement<br /><ul><li>Enterprise Content Management
    38. 38. Search content
    39. 39. Collaboration
    40. 40. Isolation isn’t requirement</li></ul>Indentifying Service Application<br /><ul><li>Access Service
    41. 41. Excel Service
    42. 42. Managed Metadata Service
    43. 43. User Profile
    44. 44. Business Data Connectivity
    45. 45. Secure Store Service
    46. 46. Search</li></ul>Indentifying Web Application<br /><ul><li>Publishing Intranet (App Pool A)
    47. 47. My Site (App Pool B)
    48. 48. Team Site (App Pool B)</li></ul>2ND SHAREPOINT SATURDAY VIETNAM<br />
    49. 49. Access<br />Service<br />Excel<br />Service<br />User<br />Profile<br />Managed Metadata<br />Search<br />Service<br />Business<br />Data Connectivity<br />Secure<br />Store Service<br />Default Group<br />Web Application <br />Publish Intranet<br />Web Application <br />Team Site<br />Web Application <br />My Site<br />Application Pool<br />Application Pool<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    50. 50. Managed Metadata<br />Excel<br />Service<br />User<br />Profile<br />Access<br />Service<br />Search<br />Service<br />Excel<br />Service<br />Business<br />Data Connectivity<br />Secure<br />Store Service<br />Default Group<br />Custom Group<br />Web Application <br />Department Site<br />Web Application <br />My Site<br />Web Application <br />Publish Intranet<br />Application Pool<br />Application Pool<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    51. 51. Medium – Large Organization<br /><ul><li>10.000 – 50.000 Users.
    52. 52. Using all or some SharePoint workloads.
    53. 53. 5 – 10 IT Staff spanning multiple roles.</li></ul>Business Requirement<br /><ul><li>Enterprise Content Management
    54. 54. Search content
    55. 55. Social Network
    56. 56. Isolate Accounting or Finance boundary</li></ul>Indentifying Service Application<br /><ul><li>Access Service
    57. 57. Excel Service
    58. 58. Managed Metadata Service
    59. 59. User Profile
    60. 60. Business Data Connectivity
    61. 61. Secure Store Service
    62. 62. Search</li></ul>Indentifying Web Application<br /><ul><li>Publishing Intranet (App Pool A)
    63. 63. My Site (App Pool B)
    64. 64. Team Site (App Pool B)
    65. 65. Isolation site (App Pool C)</li></ul>2ND SHAREPOINT SATURDAY VIETNAM<br />
    66. 66. Managed Metadata<br />Managed Metadata<br />Excel<br />Service<br />User<br />Profile<br />Excel<br />Service<br />Access<br />Service<br />Business<br />Data Connectivity<br />Secure<br />Store Service<br />Search<br />Service<br />Business<br />Data Connectivity<br />Custom Group<br />Default Group<br />Custom Group<br />Finance<br />Site<br />Published Intranet<br />Team Site<br />My Site<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    67. 67. Large Organization - Organizational<br /><ul><li>> 50.000 Users
    68. 68. Using all or some SharePoint workloads
    69. 69. Optimize administrative tasks
    70. 70. Flexible and Scalable architecture
    71. 71. Organizational boundaries
    72. 72. Dedicated IT Departments</li></ul>Business Requirement<br /><ul><li>Distributed Service Central
    73. 73. Dedicated Collaboration
    74. 74. Implement solutions: Search, ECM, Social Network and so on..
    75. 75. Published Content
    76. 76. Isolate Department for security policy</li></ul>2ND SHAREPOINT SATURDAY VIETNAM<br />
    77. 77. Farm 1 – Enterprise farm<br />User Profile<br />Search<br />Managed Metadata<br />Secure Store Service<br />Business Data Connectivity<br />Farm 4 <br />Department<br />Farm 2 <br />Published content<br />Default Group<br />Published Intranet<br />Excel Service<br />Farm 3 <br />Collaboration farm<br />Visio Graphic <br />Excel Service<br />InfoPath<br />Default Group<br />Managed Metadata<br />Default Group<br />Word Automation<br />Visio Graphic <br />Access Service<br />Usage and Heath Data Collection<br />Access Service<br />Usage and Heath Data Collection<br />PowerPoint<br />Department<br />Sites<br />My Site<br />Team Site<br />
    78. 78. Q & A<br />2ND SHAREPOINT SATURDAY VIETNAM<br />
    79. 79. Thanks you for attending<br />2ND SHAREPOINT SATURDAY VIETNAM<br />

    ×