Microsoft Project Server Integration with SharePoint 2010

Microsoft Project Server Integration with SharePoint 2010 Microsoft Project Server 2010: brings together the business collaboration platform services of SharePoint Server 2010 with structured execution capabilities to provide flexible work management solutions. Project Server 2010 unifies project and portfolio management to help organizations align resources and investments with business priorities, gain control across all kinds of work, and visualize performance using powerful dashboards. Project Server 2010 incorporates the best-in-class portfolio management techniques of Microsoft Office Project Portfolio Server 2007. This eliminates the need for Project Server Gateway (which was required to push data between Office Project Portfolio Server 2007 and Microsoft Office Project Server 2007), and providing a consistent SharePoint Server user interface across the solution. Microsoft Project Professional 2010: Microsoft Project Professional 2010 delivers powerful, visually improved ways to simplify planning, collaboration, and resource management so managers can successfully tackle all kinds of projects. Connecting Project Professional 2010 with Project Server 2010 ensures that organizations can achieve the added business benefits of unified Project Portfolio Management. Project Server 2010 is built on SharePoint Server 2010 to provide true multi-tier architecture by using the new Service Application model. The Project Server architecture includes Project Professional 2010 and Microsoft Project Web App clients in the front-end tier. The front-end applications communicate with the middle tier only through the Project Server Interface (PSI) Web Services, which in turn communicate with the business object layer. Business objects use the databases through the data access layer. Client applications do not directly access the primary databases; Project Server hides business objects and the DAL from clients. Installation considerations Project Server 2010 installed to all servers in the farm: When you install Project Server 2010 to a farm, Project Server 2010 has to be installed to every application server and Web server in the farm. Therefore Project Server 2010 licenses are required for each server in the farm. When you apply updates to Project Server 2010, it is important to apply the same update to every application server and Web server in the farm to ensure that all servers in the farm are in a consistent state.

For more information about how to install Project Server 2010, see Deploy Project Server 2010 to a server farm environment. Application server fault tolerance: Project Server 2010 application servers in a farm have fault tolerance through round-robin load balancing. A non-functioning server will be skipped and the request will be serviced by the remaining application servers in the farm. This feature may negate the need for applying a hardware-based fault tolerance solution. Cross-farm services not supported: Sharing services across farms (cross-farm services) is not supported with Project Server 2010. Therefore careful planning must be done if Project Server 2010 is installed in a separate farm from the main content management farm. Additionally, Project Server 2010 does not have a mechanism to synchronize data between multiple instances of Project Web App. The following five services must be enabled to operate a Project Server 2010 server farm: Project Service Application (used to host Project Web App instances) Excel Services (used for Reporting) PerformancePoint Service (used for Reporting Secure Store Service (used for Reporting) State Service (used for Charting) To install Project Server 2010 1. On the Project Server 2010 DVD, run default.hta. The Setup menu opens. 2. On the Start page, click Install Project Server. 3. On the Enter your Product Key page, type your product key, and then click Continue. 4. In the End User License Agreement page, review the terms of the agreement. To accept the agreement, select the I accept the terms of this agreement check box. 5. Click Continue. 6. On the Choose a file location page, click Install Now. 7. When the installation is complete, clear the Run the SharePoint Products and Technologies Configuration Wizard now check box. 8. Click Close. Once the Project Server 2010 software has been installed on each application server in the farm, you must run the SharePoint Products Configuration Wizard to integrate Project Server with SharePoint Server 2010. You must run this wizard on each application server in the farm before you can start using Project Server.

Complete the following procedure on each application server in the farm. Run the SharePoint Products Configuration Wizard on one application server at a time. Do not run it on multiple servers at the same time. To run the SharePoint Products and Technologies Configuration Wizard 1. Click Start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Products Configuration Wizard. 2. At the Welcome to SharePoint Products and Technologies page, click Next. 3. A confirmation dialog message appears that displays a list of services that may have to be restarted. Click Yes. 4. On the Modify server farm Settings page, select the Do not disconnect from this server farm option, and then click Next. 5. If the server is hosting the Central Administration web site, the Modify SharePoint Central Administration Web Application Settings page will be displayed. Select the No, this machine will continue to host the web site option, and then click Next. 6. On the Completing the SharePoint Products Configuration Wizard page, click Next. 7. On the Configuration Successful page, click Finish. ******Configure document library files******* In order to be able to save documents to Project Server 2010 sites in SharePoint Server 2010, you must manually copy several files to the appropriate directory. Perform the following procedure on each application server in the farm. To copy document library files 1. Open Windows Explorer. 2. Navigate to the following folder: Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\DocumentLibrary\DocLib 3. Copy FileDlg.htm and EditDlg.htm. 4. Navigate to the following folder:

Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Template\Features\pwsdoclibs\pwsdoclib 5. Paste FileDlg.htm and EditDlg.htm. ************Configure services************* Once Project Server 2010 is installed, the following configuration steps are required before creating a Microsoft Project Web App site and using Project Server: Start the Project Application Service Create a Project Server service application Create a top level Web site Set Read permissions on the top-level Web site Before you create a Project Server service application, confirm that the Project Application Service is running. To start the Project Application Service 1. On the SharePoint Central Administration home page, in the System Settings section, click Manage services on server. 2. On the Services on Server page, select the server where you want to run the Project Application Service from the Server drop-down list. 3. If the Project Application Service is not running, on the Service list, click Start next to Project Application Service. Once you have started the Project Server service on the desired computers in the farm, you must create a Project Server service application. Note: While you can create more than one Project Server service application, doing so consumes additional system resources. We recommend that you create only one Project Server service application. A single service application supports multiple Project Web App sites. To create a Project Server service application 1. On the Central Administration home page, in the Application Management section, click Manage service applications. 2. On the Manage Service Applications page, on the ribbon, click New, and then click Project Server Service Application. 3. On the Create Project Web App service application page:

1. Type a name for the service application in the Project Web App service application name box. 2. In the Application Pool section, choose an existing application pool or type the name of the application pool you want to create in the Application pool name box. 3. Select the Configurable option, and choose the managed account that you want to use to run the application pool. 4. Click OK. The next step is to create a top-level Web site if one does not yet exist, and give users read permission to that site. If there is not yet a top level Web site, create one using the following procedure. To create a top-level Web site 1. In Central Administration, in the Application Management section, click Create site collections. 2. Choose a Web application from the Web Application drop-down menu. 3. Type a title for the site collection in the Title box. 4. In the Template Selection section, choose a template for the site. Note: Project Server 2010 does not require a specific template. You can choose one appropriate for your organization. 5. In the Primary Site Collection Administrator section, type the name of the account that you want to use for the site administrator. 6. Click OK. To set Read permissions on the top-level Web site 1. Navigate to the root site (that is, http://<servername>). 2. Click Site Actions. 3. Click Site Permissions. 4. Click Grant Permissions. 5. In the Users/Groups box, type NT AUTHORITY\Authenticated Users. 6. Under Grant Permissions, select the Add users to a SharePoint group (recommended) option, and then select <SiteName> Visitors [Read] from the dropdown list. 7. Click OK.

Create a Project Web App (PWA) site (Project Server 2010) Manually Create the Project DataBase (Optional) When you create a Microsoft Project Web App (PWA) site, the required databases are created automatically on the instance of Microsoft SQL Server that you specify. However, some organizations require that databases be created manually by a database administrator. This article contains the information that is required to manually create databases for Microsoft Project Server 2010. The table that follows describes the collations required for each database used by an instance of PWA. Database Project Server Archive Project Server Draft Project Server Published Project Server Reporting SharePoint Server Content Collation SQL_Latin1_General_CP1_CI_AS SQL_Latin1_General_CP1_CI_AS SQL_Latin1_General_CP1_CI_AS SQL_Latin1_General_CP1_CI_AS Latin1_General_CI_AS_KS_WS Have your database administrator create a set of databases, as described in the table, for each PWA site that you plan to deploy. Once the databases have been created, specify the names of these databases when you create the PWA site or the content database. Create a PWA site (Project Server 2010) Creating a Microsoft Project Web App (PWA) site creates the four Microsoft Project Server 2010 databases on the specified instance of Microsoft SQL Server. The Project Web App site requires a SharePoint Web application to host it. *************Very Important*****************

We highly recommend that you use a separate SharePoint Server 2010 content database for each PWA site and its associated project workspaces. To correctly isolate the PWA site in its own content database, you must deploy PWA at a time when other administrators are not creating new sites on the Web application where you are deploying PWA. By putting PWA and its associated project workspaces in a separate content database, you greatly simplify site migration and backup and restore procedures. Creating a PWA site takes five basic steps: 1. Create a content database to host the PWA site and its associated project workspaces. 2. Temporarily lock down existing content databases. 3. Create the PWA site itself. 4. Lock down the PWA content database to prevent additional site collections being added. 5. Unlock existing content databases. SharePoint Server 2010 uses a round-robin algorithm to determine the distribution of site collections across content databases. In order to deploy the PWA site to a specific content database, you have to lock down any existing content databases in the web application where you plan to deploy PWA. The process does not affect user access; it only affects the distribution of new site collections. Note: If you are deploying PWA to a new web application that will be dedicated to PWA, you can use the default content database created with that web application for PWA. In this case, there is no need to follow the following lockdown procedures. However, we do recommend that you set the Maximum number of sites that can be created in this database setting to 1 for that content database after you deploy PWA. This will help avoid additional site collections beyond PWA being created in that database in the future. To lock down your content databases, follow these steps for each content database associated with the Web application where you plan to deploy your PWA site. Important: Ensure that no other administrators are adding site collections to the Web application where you plan to deploy PWA while you are performing the procedures in this section.

To lock down a content database 1. In SharePoint Central Administration, in the Application Management section, click Manage content databases. 2. In the Current Number of Site Collections column, note the number of site collections for the database that you plan to lock down. 3. In the Database Name column, click the link for the content database that you want to lock down. 4. In the Database Capacity Settings section: 1. In the Maximum number of sites that can be created in this database box, type the existing number of site collection for this database (as noted in the Current Number of Site Collections column, earlier in this procedure). 5. Click OK. Note: Take note of the current value for this parameter; you will have to change it back to this value after the PWA site has been created. 2. In the Number of sites before a Warning event is generated box, type a lower number than the value that is used for Maximum number of sites that can be created in this database. Note: Take note of the current value for this parameter; you will have to change it back to this value after the PWA site has been created. To create a content database 1. In SharePoint Central Administration, in the Application Management section, click Manage content databases. 2. Click Add a content database. 3. In the Web Application section, choose the Web application where you plan to deploy the PWA site. 4. In the Database Name and Authentication section, type the database server name where you plan to deploy your PWA databases, and type a name for the database. 5. Click OK. Once the content database has been created and configured, the next step is to create the PWA site itself.

To create a PWA site 1. In SharePoint Central Administration, in the Application Management section, click Manage service applications. 2. On the Manage Service Applications page, click the Project Server Service Application. 3. On the Manage Project Web App Sites page, click Create Project Web App Site. 4. Complete the Create Project Web App Site page as designated in the following table: Option SharePoint Web Application to Host Project Web App Project Web App path Select a language Use Project Web App path as host header Administrator Account Primary database server Published database name Draft database name Archive database name Reporting database server Use primary database server Reporting database name Description The Web application for the PWA site. The path from the root site for this PWA site. The user interface language for this PWA site. Use this option if you want to host PWA on a root URL (for example, https://www.contoso.com). The user account that will be added to the Project Server Administrators security group in this instance of PWA. You must use this account the first time that you access PWA. The instance of SQL Server where you want to host the Project Server databases. If your database administrator has already created Project Web App databases, specify the names of those databases in the appropriate text boxes. If the databases were not previously created, they will be created automatically. The name of the Project Server Published database for this instance of PWA. The name of the Project Server Draft database for this instance of PWA. The name of the Project Server Archive database for this instance of PWA. The instance of SQL Server where you want to deploy the Reporting database (if different from the primary database server). Select the check box to deploy the Reporting database to the primary database server specified earlier. Clear the check box to deploy the Reporting database to a different database server, and specify the instance of SQL Server that you want to use in the Reporting database server box. The name of the Project Server Reporting database for this instance of PWA.

Quota for SharePoint content in this site Quota Warning for SharePoint content in this site The maximum site storage, in megabytes, for the PWA site. The site storage level, in megabytes, at which a warning e-mail message will be sent to the site administrator. 5. Click OK. Project Server starts the PWA site creation process. This may take some time. When the site creation process is complete, the status shown on the PWA site list is Provisioned. Once the PWA site has been provisioned, verify that it was created in the content database that you created. Use the Get-SPSite Windows PowerShell command, passing the new content database as a parameter: To verify the PWA site location 1. Verify that you meet the following minimum requirements: See Add-SPShellAdmin. 2. On the Start menu, click All Programs. 3. Click Microsoft SharePoint 2010 Products. 4. Click SharePoint 2010 Management Shell. 5. From the Windows PowerShell command prompt (that is, PS C:\>), type the following command and then press ENTER: Get-SPSite -ContentDatabase <ContentDatabaseName> The command should return the URL for your PWA site and no other URLs. Note: If additional URLs beyond that of the PWA site are listed in the content database, delete the PWA site and restart the procedure with a new content database. Once the PWA site is in the desired content database, you must lock down the database to prevent SharePoint Server 2010 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 1. In SharePoint Central Administration, in the Application Management section, click Manage content databases. 2. In the Database Name column, click the link for the content database that you created. 3. In the Database Capacity Settings section: 1. In the Number of sites before a Warning event is generated box, type 0. 2. In the Maximum number of sites that can be created in this database box, type 1. 4. Click OK. Once you have locked down your PWA content database, you can return any other content databases to their original values for Maximum number of sites that can be created in this database and Number of sites before a Warning event is generated. You can now access the new PWA site. Note: The first invocation of the Internet Information Services (IIS) application pool that contains the Project Web App application can be slow because the.net Framework application is being compiled and loaded. Configure time reporting periods Configuring time reporting periods is required for Team Member use of Time Tracking and Task Statusing within Project Server 2010. We recommend that you create at least a year of time reporting periods. Use the following procedure to create time reporting periods. To create time reporting periods 1. In PWA, click Server Settings. 2. In the Time and Task Management section, click Time Reporting Periods. 3. On the Time Reporting Periods page: 1. Click the calendar button next to Date the first period starts and select a start date for the first time reporting period. Important: If you choose a length of seven days for a standard reporting period, all periods will begin on the day of the week you select for the first period start date. Choose a day of the week that conforms with the needs of your organization.

Important: If you want to create variable-length periods, for example when you use a period per calendar month, you must do these individually on the Time Reporting Periods page or programmatically through custom code. 2. Click Create Bulk. 3. Click Save. Configure the workflow proxy account The final step before you start to use the PWA site is to set the workflow proxy user account. By default, this account is set to the account that you used to create the PWA site. Although you can keep the default, we recommend that you create an Active Directory account for this purpose. Important: You must change the account before you start any workflows or else in-progress workflows will break. There are two steps that you must follow to set up the workflow proxy account: Create a Project Server 2010 user account for the workflow proxy Active Directory account. Configure this account as the workflow proxy user. Perform the following procedure to create a Project Server 2010 for the workflow proxy account. To create a user 1. In Project Web App, click Server Settings. 2. In the Security section, click Manage Users. 3. On the Manage Users page, click New User. 4. On the New User page: 1. Clear the User can be assigned as a resource check box. 2. In the Display Name box, type the name that you want to use for the user account (for example, Workflow Proxy User). 3. In the User Authentication section, type the Active Directory account that you created for the workflow proxy user in the User logon account box. 4. Select the Prevent Active Directory synchronization for this user check box.

5. In the Security Categories area, select My Organization in Available Categories, and then click Add. 6. Under Permissions for My Organization, select Allow for the following permissions: Open Project Save Project to Project Server View Enterprise Resource Data 7. Under Global Permissions, select Allow for the following permissions: Log On Manage Users and Groups Manage Workflow and Project Detail Pages 5. Click Save. Once the user account is created, you can set the workflow proxy user account. Perform the following procedure to configure the workflow proxy user account. To set the workflow proxy user account 1. In PWA, click Server Settings. 2. On the Server Settings page, in the Workflow and Project Detail Pages section, click Project Workflow Settings. 3. On the Project Workflow Settings page, in the Workflow Proxy User account box, type the Active Directory account that you created for the workflow proxy user, and then click Save. You are now ready to start using the Project Web App site. Creating a Project Web APP, ProJect Configuration and Plan in Project Server 2010 Please follow the screen display to create a project site web application and to provision a site plan. Click on the project server service application

Click on Create Project Web App Site Create the project site with different content DB as it takes lots of resources.

It takes minimum 5-10 minutes to provision the project web app site: Once the process is completed your screen will look like this. Your default Project site: From the left hand menu select Server Settings and click on Project site provisioning to allocate the site creation location.

In this example I am restricting all projects sites to be created under the main Project Web App.

User Profile Synchronisation From the left hand menu select Server Settings and click on Active Directory Resource Pool Synchronisation. AD setup:

Select the group you have created to synchronise with AD. In this example I have created an AD group named PWA_User. Just by clicking on Find Group button to synchronise the AD group and schedule the process accordingly. Once it is completed click Save to apply the configuration.

Go to the server settings and select Manage Users After user profile synchronisation your screen will like: Go back to Server Settings and select Manage Groups and allocate users.

For example: Select Project Manager s group Work-Flow provision Settings From the Server Settings menu select Project Workflow Settings

Select the appropriate user to provide this facility for the entire project sites. Activate the Project Proposal workflow Now we are ready to create a project site and a plan associated with the Project Server Web App. Project Site creation Go to site settings and create a new project site (BA Demo). You can see that all sites you create will be placed under the main project application. Your new project site will look like:

Here you can enter all relating the upcoming project.. Deliverables will look like this after the configuration: Synchronising Project Professional with SharePoint

A Project Manager (PM) can use all the advanced scheduling capabilities that exist in Project Professional with all the collaborative capabilities that exist in SharePoint. Users can now publish a project plan from Project to SharePoint and vice versa. Any changes made in Project / SharePoint can be easily updated into SharePoint / Project with the click of a button. So how does this work? Let s assume a PM creates a simple project plan in Project Professional, as shown below. The PM would like to share the plan with his/her team members via SharePoint. To do this, the PM clicks on the File tab and drills on to Save & Send > Sync with Tasks List (see image below). After filling out the required fields, the user clicks on Sync, and in a matter of seconds the project plan has been published to SharePoint. The SharePoint list will look as follows:

Now the team members can view and modify the data in SharePoint, and the PM can synchronize the updates by clicking on the Sync button. Tip: After the first sync, the Sync button also appears in the Info tab shown below. If the same data is modified both in SharePoint and Project, the PM will be prompted with a conflict resolution dialog next time there is a Sync operation.

A few important things to notice are: Summary tasks are supported in the synchronization Most custom fields can be synchronized, and can be added via the Manage Fields dialog (click on Manage Fields button shown on the image above in the Info tab) This feature only works with SharePoint Foundation and SharePoint Server 2010