Deploy Project Web App with a new site collection (Project Server Subscription Edition, 2019, or 2016)
Summary: Learn how to deploy an instance of Project Web App along with a Project Web App site in a new site collection.
Applies to: Project Server Subscription Edition, Project Server 2019, Project Server 2016
Create a top-level web site
If a top-level web site does not exist for the web application where you want to create a Project Web App site, you must first create one. Use the following procedure to create a top-level web site if needed.
To create a top-level Web site
In the SharePoint Central Administration website, in the Application Management section, click Create site collections.
Choose a Web application from the Web Application drop-down menu.
Type a title for the site collection in the Title box.
In the Template Selection section, choose a template for the site.
Note
Project Servers Subscription Edition, 2019, or 2016 does not require a specific template. You can choose one appropriate for your organization.
In the Primary Site Collection Administrator section, type the name of the account that you want to use for the site administrator.
Click OK.
After you have created the top-level web site, you must grant users access to the site. Use the following procedure to grant read access to the top-level site.
To set Read permissions on the top-level Web site
Navigate to the root site (that is, https://<servername>).
At the top of the page, click Share.
On the Share dialog box, click Show Options.
From the Select a group or permission level, choose <site> Visitors [Read].
In the Enter names or email addresses text box, typeEveryone.
Click Share.
Create a Project Web App site
Important
When you create a new Project Web App site in conjunction with a new site collection, we recommend that you use a separate SharePoint Server Subscription Edition, 2019, or 2016 content database for the Project Web App site and its associated project workspaces. To correctly isolate the Project Web App site in its own content database, you must deploy Project Web App at a time when other administrators are not creating new sites on the Web application where you are deploying Project Web App.
By putting Project Web App and its associated project workspaces in a separate content database, you greatly simplify site migration and backup and restore procedures.
Creating a Project Web App site takes five basic steps:
Create a content database to host the Project Web App site and its associated project workspaces.
Create the Project Web App site itself.
Lock down the Project Web App content database to prevent additional site collections being added.
Important
Ensure that no other administrators are adding site collections to the Web application where you plan to deploy Project Web App while you are performing the procedures in this section.
To create a content database
In SharePoint Central Administration, in the Application Management section, click Manage content databases.
Click Add a content database.
In the Web Application section, choose the Web application where you plan to deploy the Project Web App site.
In the Database Name and Authentication section, type the database server name where you plan to deploy your Project Web App databases, and type a name for the database.
Click OK.
After the content database has been created and configured, the next step is to create the Project Web App site itself.
To create a Project Web App site in a new site collection, you run the New-SPSite Microsoft PowerShell cmdlet to create the site in the content database that you created, and then run Enable-SPFeature to turn on the Project Web App site collection features.
Verify that you have the following memberships:
- securityadmin fixed server role on the SQL Server instance.
- db_owner fixed database role on all databases that are to be updated.
- local Administrators group on the server on which you are running the PowerShell cmdlets.
From the PowerShell command prompt, run the following commands to create the Project Web App site.
New-SPSite -ContentDatabase ContentDBName -URL SiteCollectionURL/PWASiteName -Template pwa#0 -OwnerAlias domain\user
Enable-SPFeature pwasite -URL SiteCollectionURL/PWASiteName
For example:
New-SPSite -ContentDatabase PWA_Content -URL https://contoso-appsrv1/sites/PWA -Template pwa#0 -OwnerAlias domain\user
Enable-SPFeature pwasite -URL https://contoso-appsrv1/sites/PWA
After the Project Web App site has been provisioned, verify that it was created in the content database that you created. Use the Get-SPSite cmdlet, passing the new content database as a parameter:
To verify the Project Web App site location
From the PowerShell command prompt, type the following command and then press ENTER:
Get-SPSite -ContentDatabase <ContentDatabaseName>
The command should return the URL for your Project Web App site and no other URLs.
Note
If additional URLs beyond that of the Project Web App site are listed in the content database, delete the Project Web App site and restart the procedure with a new content database.
After the Project Web App site is in the desired content database, you must lock down the database to prevent SharePoint Server from adding additional site collections to the database. This is performed by configuring the maximum number of sites for the content database to one.
Note
Configuring this setting does not prevent new project workspace sites from being created.
To lock down the content database
In SharePoint Central Administration, in the Application Management section, click Manage content databases.
In the Database Name column, click the link for the content database that you created.
In the Database Capacity Settings section:
In the Number of sites before a Warning event is generated box, type0.
In the Maximum number of sites that can be created in this database box, type1.
Click OK.
You can now access the new Project Web App site.