Chapter 7 – Understanding the Service Application Architecture

Wrox – Professional SP 2010 Admin: page 167

MOSS 2007’s SSP – associate each web app with all SSP’s = has to get all services, which is a nightmare.

In SP 2010, each service can assoicated with each web application.

If HR needs their own BDC, you need to:
(1) Create a new web app for HR,
(2) Create a new provision of BDC (named “HR Only BDC”) and then associate the new web app with this service app.

Service Application Fundamentals –

** Web application > Service App Group > Service App Connection > Service App > Service App Service + Service App Database

Service Application Groups –

When a web app is created, it is defaulted to use the default service app group.

Web application group is also called [proxy groups] or [application proxy groups].

When you choose to crate a new [custom] service app group for a new web application, you cannot reuse the service application group. (not reusable)

** To create a new service application group that you can reuse, you need to use this cmdlet:
New-SPServiceApplicationProxyGroup

Service Application Connections –

Connects the web service that runs for the service application and accepts requets fro the web application to the service application group.

In IIS, the web site named “Sharepoint Web services” has all service application connections (in web services).

Service Applications database –

Each service application needs a single database; for example, BDC service application and an HR-only-BDC service application will take 2 databases.

Service Application Services –

Connecting across farms –

Some service application can be pulished or consumed across farms. Before so, you nned to establish a [farm trust] – by using Powershell to create and register certificates between two farms. After that, go to your service application, click Publish button and then you will get an URL for accessing the published service.

Create a new instance of a service application –

HR is asking for their own Managed Metadata service:

(1) Central Admin App Management Manage service app. New Managed Metadata service.

(2) Setting up a delegated admin – Click Administrator button to add someone from HR so they can manage the managed metadata by themselves.

User added in this sceanrio is added to a special user group called [Delegated Administrators].

Managing Service Application Group –

Central Admin App management Configure service application association: To manage the association of Web Application and Service Application Groups.
From here you can add or remove individual service applications to/from the default service application group.

In the same application service group, if there are

GET-Command *serviceapplication*

returns all command that has the keyword [service application]

Creating a new service application group –

** You cannot creat reusable service application group in Central Admin. But you can with powershell:
New-SPServiceApplicationProxyGroup – name YourCustomGroup

To add service applications (or [service application connections]) to the new group, first query the GUID of each service application —
GET-SPServiceApplicationProxy

Then to add each of the the services to the new group, do this:
Add-SPServiceApplicationProxyGroupMember YourCustomGroup –member [GUID of the service application].

An easier way to add service applications – from the web interface.

Multi-tenant capabilities – built-in SP 2010.

Site subscription –

Enable you to group together site collections that are part of the same web application; it’s a logical group of site collections that can share settings, features and service data.

Site subscriptions are identified with a subscription ID. Characters of Site Subscription –

  • A site can be a member of only one site subscription at a time.
  • No central admin interface for managing site subscripotion. Must use powershell.
  • Sites can only join a site group in the same web app as that specific site subscription. Can’t join site groups associated with other Web Application.
  • Site subscriptions can span multiple content database.

Partitioned service application – site collections in the same site subscripotion, the service applications can be provisioned such that their functions and data are kept separate from other tenants who may be consuming that service application.

Feature sets —

In SP 2010, you can group Features together and call Freature Sets. Features sets are logical groupings of Features that are then made available for activation to s site subscription by an admin of that site subscription.

Partitioning of service Application –

If doesn’t use disk space, cannot be partitioned.

When a feature is installed and activated at wen app level, it is automatically available for activation at the site collection level.

Once a site subscription is created and site are asooicated with it, the sites are managed through a new site templatecalled a Tenant Admin site.

To create a new site subscription: New-SPSiteSubscription

 

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: