Guide of SharePoint Server Installation and AddIn Environment Configuration
After Windows Server Installation
-
Set up Active Directory in Window Server
Reference Youtube Video Setting up Active Directory in Windows Server 2019 (Step By Step Guide)
Install Active Directory Domain Services and DNS Server
-
Install SharePoint Server
Reference Link Installing SharePoint 2019
- Install Microsoft SQL Server
- Install SharePoint Server
After SharePoint Server Installation
ensure that the following services are started- User Profile Service Application
- App Management Service
- Subscription Settings Service
Central Administration -> Application Management -> Manage service applications
First two services can be created and started at Central Administration -> Application Management -> Manage service applications
Reference Link How to configure User Profile Service Application in SharePoint 2019
Last one should be created and started by commands on SharePoint Management Shell
Reference Links link1, Create Subscription Settings Service Application For Add-In Development In SharePoint 2016
-
Syntax
> $account = Get-SPManagedAccount [Domain\User] > $appPool = New-SPServiceApplicationPool -Name [Application Pool Name] -Account $account > $serviceApp = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPool -Name [Application Name] -DatabaseName [Database Name] > $serviceAppProxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $serviceApp
-
Example
PS C:\Users\Administrator> $account = Get-SPManagedAccount JSGURU\Administrator PS C:\Users\Administrator> $appPool = New-SPServiceApplicationPool -Name SubscriptionServiceAppPool -Account $account PS C:\Users\Administrator> $serviceApp = New-SPSubscriptionSettingsServiceApplication -ApplicationPool $appPool -Name "Subscription Settings Service Application" -DatabaseName SubscriptionSettingsDB PS C:\Users\Administrator> $serviceAppProxy = New-SPSubscriptionSettingsServiceApplicationProxy -ServiceApplication $serviceApp
-
SharePoint Server AddIn Environment Configuration
(SharePoint Hosted and Provider Hosted)Reference Link SharePoint 2016 AddIn Environment Configuration
If you get a 403 (forbidden) message when the remote web application calls SharePoint by using a self-signed certificate, please turn off the HTTPS requirement.
Reference Link Create high-trust SharePoint Add-ins
PS C:\Users\Administrator> $serviceConfig = Get-SPSecurityTokenServiceConfig PS C:\Users\Administrator> $serviceConfig.AllowOAuthOverHttp = $true PS C:\Users\Administrator> $serviceConfig.Update()
-
Why / What Addin?
Reference Link Develop your first SharePoint Add-In
-
Give Provider Hosted AddIn the SharePoint look-and-feel
Reference Link Give the remote web application the look and feel of SharePoint
-
Create SharePoint Hosted AddIn In SharePoint Server
Prerequisites: Setting up Active Directory in Windows Server 2019Reference Links
Setting Up Add-In Development Environment In SharePoint Server 2016
Set up an On-Premise development environment for SharePoint Add-in or Apps developement in SharePoint 2016/2013
SharePoint Server 2016 AddIn Environment Configuration -
Create Event Receiver
Reference Link Creating Simple Event Receiver in SharePoint 2013
-
Create Remote Event Receiver on Provider Hosted AddIn
Reference Link Working with Remote Event Receivers in a Provider Hosted App
-
Custom SharePoint list definition
Reference Link How to create a custom SharePoint list definition using Visual Studio 2012
-
Create SharePoint farm database on SharePoint Management Shell
- Syntax
> New-SPConfigurationDatabase –DatabaseName [config db name] –DatabaseServer [sql server name] –AdministrationContentDatabaseName [content db name] –Passphrase (ConvertTo-SecureString [your password] –AsPlaintext –Force) –FarmCredentials (Get-Credential) -localserverrole SingleServerFarm
- Example
PS C:\Users\Administrator> New-SPConfigurationDatabase –DatabaseName SharePoint_Config –DatabaseServer WIN-JC2B1V15KM5 –AdministrationContentDatabaseName SharePoint_Content –Passphrase (ConvertTo-SecureString Qwerty@12345 –AsPlaintext –Force) –FarmCredentials (Get-Credential) -localserverrole SingleServerFarm
- Syntax
-
Shell commands
- Checking solutions installed in the farm
> Get-SPSolution
- Delete solution
Replace mysolution.wsp with your real solution name
> (Get-SPSolution mysolution.wsp).Delete()
- Disconnect the local server computer from the farm
> Disconnect-SPConfigurationDatabase
- Get the token issuer id
> Get-SPTrustedSecurityTokenIssuer
- Checking solutions installed in the farm