Logo
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
EPL Standings
 
 
Windows Server

Sharepoint 2013 : Service Application Fundamentals (part 1) - The Connection Structure -Service Application Groups

- 2015 Chevrolet Camaro Z28 - The Legend Returns
- Wagon Audi Allroad Vs. Subaru Outback
- 996 Carrera 4S is Driving Perfection
3/24/2014 1:38:32 AM

The preceding section is just a simplified overview of how services work in SharePoint, of course. Before you can effectively put service applications to work, it is important to understand the connections and relationships of services to web applications. The following sections explore the glue that binds service applications. While conceptually it is easy to see that service applications provide capabilities to the web applications, in reality there is a lot going on to make those connections work. To effectively troubleshoot and support the SharePoint farm going forward, you need to learn those details.


TOMATO OR TAMAHTO?
There are some key pieces of service applications that use different terminology depending if you are looking at TechNet, Central Administration, or PowerShell. The key to it is not to over think things. For the sake of this conversation anything that refers to a group is the same thing, anything that refers to a connection is just that. For example:
  • Service application connection group = proxy group = group
  • Service application connection = proxy = connection
The best plan is don’t think too hard; the obvious answer is the right answer.

1. The Connection Structure

Service applications are not offered directly to web applications, as you might have assumed from the preceding section. Instead, a series of connections and associations determine how services are offered, as shown in Figure 1.

FIGURE 1

image

SharePoint web applications are associated with service application groups. These groups are composed of one or more service application connections. Service application connections act as a bridge, admitting the service applications into the service application groups. A service application consumes one or more service application services, some of which may have databases for storage. If this sounds confusing, the following sections should help clarify how these components are integrated.

Service Application Groups

You already know what a web application is at this point. The service application group specifies how services are associated with a web application. When you created the web application, you used SharePoint’s default service application group (see Figure 2). Notice that all the check boxes are grayed out when the default group of connections is chosen. You cannot edit the default group in this dialog as you create a web application.

FIGURE 2

image

The default group is automatically provisioned for you. If you used the initial Farm Configuration Wizard, then all the service applications are part of this group. When you manually create a service application, you can choose to include it in the default group or not by using the check box shown in Figure 3.

FIGURE 3

image

This group enables you to associate a web application with a collection of service applications. If the default group doesn’t meet your needs, you can you can use the [custom] option to specify which service applications you want to use for the web application. Keep in mind that although [custom] appears in the group drop-down menu, you cannot reuse this “group.” When you create a web application and specify [custom], you choose the service applications available to that web application. If you then create a second web application and select [custom], you will not see the service applications you chose for the first web application selected. Each usage of [custom] is a unique instance, and not reusable.

Proxy groups or application proxy groups are other terms you may hear used for service application groups. This is how they are referred to in the SharePoint 2013 Management Shell and in the object model (OM).


NOTE To create a group you can reuse, you need to use the SharePoint 2013 Management Shell and run the New-SPServiceApplicationProxyGroup cmdlet. 
Top Search -----------------
- Windows Server 2008 R2 : Work with RAID Volumes - Understand RAID Levels & Implement RAID
- Windows Server 2008 R2 Administration : Managing Printers with the Print Management Console
- Configuring Email Settings in Windows Small Business Server 2011
- Windows Server 2008 R2 : Configuring Folder Security, Access, and Replication - Implement Permissions
- Monitoring Exchange Server 2010 : Monitoring Mail Flow
- Windows Server 2008 R2 :Task Scheduler
- Windows Server 2008 R2 : File Server Resource Manager
- Windows Server 2008 R2 : Installing DFS
- Exchange Server 2010 : Managing Anti-Spam and Antivirus Countermeasures
- Windows Server 2008 R2 : Configuring Folder Security, Access, and Replication - Share Folders
Other -----------------
- Sharepoint 2013 : Understanding Service Applications - A History of Service Applications in SharePoint
- Microsoft Exchange Server 2007 : Consolidating a Windows 2000 Domain to a Windows Server 2003 Domain Using ADMT (part 5) - Migrating Computer Accounts
- Microsoft Exchange Server 2007 : Consolidating a Windows 2000 Domain to a Windows Server 2003 Domain Using ADMT (part 4) - Migrating User Accounts
- Microsoft Exchange Server 2007 : Consolidating a Windows 2000 Domain to a Windows Server 2003 Domain Using ADMT (part 3) - Migrating Groups
- Microsoft Exchange Server 2007 : Consolidating a Windows 2000 Domain to a Windows Server 2003 Domain Using ADMT (part 2) - Installing a Password Migration DLL on the Source Domain
- Microsoft Exchange Server 2007 : Consolidating a Windows 2000 Domain to a Windows Server 2003 Domain Using ADMT (part 1) - Modifying Default Domain Policy on the Target Domain
- Microsoft Exchange Server 2007 : Upgrading Separate AD Forests to a Single Forest Using Mixed-Mode Domain Redirect (part 2)
- Microsoft Exchange Server 2007 : Upgrading Separate AD Forests to a Single Forest Using Mixed-Mode Domain Redirect (part 1)
- Windows Server 2012 : Provisioning and managing shared storage (part 7) - Managing shared storage - Managing volumes, Managing shares
- Windows Server 2012 : Provisioning and managing shared storage (part 6) - Managing shared storage
 
 
Most view of day
- Microsoft PowerPoint 2010 : Animating Slide Content (part 2) - Special Options for Text Animation
- Windows Server 2008 R2 : Managing Computers with Domain Policies (part 4) - Deploying Printers
- Troubleshooting Network Problems : Repairing a Network Connection
- Microsoft Visio 2010 : Annotating Visio diagrams with issues
- Data Bindings : Give and Take
- Windows Phone 7 : Sensors - Creating a Seismograph
- Using Advanced System Management Tools : Editing the Registry (part 1)
Top 10
- Microsoft Exchange Server 2010 : Defining Email Addresses (part 3) - Email Address Policies - Creating a New Email Address Policy
- Microsoft Exchange Server 2010 : Defining Email Addresses (part 2) - Email Address Policies - Changing an Existing Policy
- Microsoft Exchange Server 2010 : Defining Email Addresses (part 1) - Accepted Domains
- Microsoft Exchange Server 2010 : Basics of Recipient Management - Exchange Recipients
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 7) - Using iSCSI Initiator - Creating volumes
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 6) - Using iSCSI Initiator - Establishing a connection
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 5) - Using iSCSI Initiator - Discovering targets
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 4) - Using iSCSI Initiator - Configuring iSCSI Initiator
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 3) - Configuring iSCSI Target Server - Creating iSCSI virtual disks
- Windows Server 2012 : File Services and Storage - Configuring iSCSI storage (part 2) - Configuring iSCSI Target Server - Installing the iSCSI Target Server role
Windows XP
Windows Vista
Windows 7
Windows Azure
Windows Server
Windows Phone
2015 Camaro