Subscription Settings Service Application In SharePoint 2016

In this blog you will learn about Subscription Settings Service Application, step-by-step, in SharePoint 2016.

This service application is not new for us; we have learned about this in previous versions of SharePoint 2010/2013.This service supports site subscriptions. It has some characteristics in common with IIS Web Services inasmuch as it is a WCF Web service and the object that represents it at run time is an SPIisWebService -derived object. However, it does not implement the Service Application Framework .

In SharePoint 2010, SharePoint uses this service application for Multi-Tenant Mode or sites that use site subscriptions. In a multi-tenant environment, this service application stores the subscriptions settings and configuration data.

In SharePoint 2013, Introduction of App Management Service Application and Subscription Settings Service Application is one of the prerequisites of it. The App Management Service is inherently Subscription aware and does NOT need to be provisioned in Partitioned Mode.

The same is the case with SharePoint 2016.

Known facts about this:

• There is no GUI to provision this Service Application
• Provisioned via PowerShell only
• This Service Application has own Content Database.

Today, I will walk through the steps of provisioning a Microsoft SharePoint Foundation Subscription Settings Service Application. Let’s start:

Configure the Subscription Settings service application by using PowerShell

You can start the Microsoft SharePoint Foundation Subscription Settings Service Application from Central admin first, then provision it via PowerShell or simply run the PowerShell and it will start and Provision the service application.

1. If you go Central Admin > System Settings > manager Service on the farm. You will see this.
   
   
2. Please make sure of the following things.
   
   
1. Login with a Domain Account which should be Local Admin on Server
2. security admin fixed server role on the SQL Server instance.
3. db_owner fixed database role on all databases that are to be updated.
   
   
3. Now start the SharePoint PowerShell Window (Run as Administrator).
   
4. Run the following Script
   
   
1. # Gets the name of the managed account
   
   $manaccount = Get-SPManagedAccount Krossfarm\kfadmin
   
   
2. # Creates an application pool for the Subscription Settings service application using the Managed Account just get step 1.
   
   $appPoolService = New-SPServiceApplicationPool -Name "SS-AppPool" -Account $manaccount
   
   
3. # Creates the Subscription Settings service application, using the variable to associate it with the application pool that was created earlier.
   
   $appService = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPoolService -Name SettingsServiceApp -DatabaseName "SS-ContentDB"
   
   
4. # Creates a proxy for the Subscription Settings service application, supply the SS service variable use at step 3.
   
   $proxyService = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $appService
   
   
   
   
5. Once it is successfully completed go the Central admin and you will see it is started.
   
   
   
   
6. If you go Manager Service Application you will See it is provisioned here.