1. Service application framework service model
   1. fundamental
   2. flexible
   3. scalable
   4. extensible
   5. managed within ca
2. Service Application Components
   1. Services
      1. on same server or spread and load balance
   2. Service Application
      1. instance of a service
      2. multiple instances in a farm
      3. application pool is associated with sa
   3. Service application connections
      1. connection between sa and web appl
      2. proxy
   4. Service application connection groups
   5. web applications
3. Service Applications
   1. components
      1. virtual directory: new web site in IIS (GUID)
      2. Application pools
         1. each virtual directory is associated with appl pool
      3. databases
      4. physical instance
         1. actual process or web service
      5. administrative interface
   2. create
      1. farm configuration wizard
      2. manual configuration
         1. Ca
         2. Powershell
            1. New-SPAccessservcieAPplication
   3. Provisioning
      1. deploy service applications to differten app pools to achieve process isolation
      2. for performance: deploy service appl to only one appl pool
      3. physical isolation: different appl pools for the service appl (only if significant business need)
4. Service application Connections
   1. application proxy or proxy
   2. connection between web appl and service appl
   3. web parts, sp obj model use proxies to connect to service appl
   4. created automatically
5. Service application connection groups
   1. collection of service applications that use the same proxy
   2. sp creates default
   3. create custom for data isolation
   4. ca or powershell
   5. scenarios
      1. single farm - single service application group
         1. default service appl group used for all web appl, all sites have access to all service applications
         2. voordelen
            1. simple - use farm setup wizard
            2. all service appl available for all web appl
            3. all servcie appl managed centrally in one farm
            4. best us of resources: one instance of each service group is needed
         3. nadelen
            1. cannot isolate service appl data
            2. individual departements/teams connot manage service appl on their own
         4. recommendations
            1. best for single company on same farm
            2. optimize resources
      2. Single medium sized farm, multiple service appl groups
         1. default is used for most web appl
         2. advantages
            1. main web appl have access to the service appl they need
            2. own instance of service appl for stricter data policy
            3. service appl can be managed separately (by departements)
         3. disadvantages
            1. needs more farm resources because multiple instances of service appl run at the same time
         4. Recommendations
            1. for organizations that require that specific departements have their own isolated data
            2. you don't need process isolation (appl pools)
      3. multiple farms, multiple service appl groups
         1. default group can be used for most web appl
         2. advantages
            1. web appl have access to only sa that they need
            2. departements with stricter data policy can have theri own instance
            3. sa can be maanged by departement
            4. data and sa can be shared across farms
         3. disadvantages
            1. most taxing on farm resources: multiple instances run at the same time
            2. requires more hardware
         4. recommendations
            1. for content sharing across farms
            2. for isolation certain departement data from the rest of the farms
6. Planning
   1. balance between performance and isolation
   2. typical dedicated services (<> cross farm)
      1. excel
      2. managed metadata
         1. to allow a team to manage their own taxonomy
         2. sp combines the multiple MMS sa so that taxonomies etc can be shared
      3. business data connectivity
         1. teams can integrate with their own LOB data and keep data isolated
   3. cross farm service applications
      1. user profile
      2. managed metadata
      3. BDC
      4. Search
      5. Secure Store Service
      6. Web analytics
      7. werkwijze
         1. Use certificates between two farms
            1. consuming farm must provide two trust certifciates to the publishing farm
            2. root certificate
            3. Security Token Service certficate
            4. publishing farm must provide certificate
            5. root certificate
            6. powershell can export and copy certificates
         2. permissions
            1. configure permissions on the Shared Service appl
            2. configure permissoins on the applciation discovery and load balancer service app
         3. publish the sa
         4. connect to cross farm sa
            1. creates connection on consumer farm that can be added to appl conn groups
         5. note
            1. farms in different domains: set up two-way trust for user profile or bdc services to be shared
   4. Single farm SA
      1. Usage and health Data Collection
      2. State Service
      3. Project server
      4. Performance Point
      5. Excel Services
      6. Access services
      7. Visio graphics service
      8. Word automation service
      9. Word viewing service
      10. Powerpoint service