System and Setup Requirements to Support Integration of Team Foundation Server and Project Server
You can synchronize data between Visual Studio Team Foundation Server 2012 (TFS) and Microsoft Project Server by installing Team Foundation Server Extensions for Project Server. You can install the extensions of the following versions of Project Server: Project Server 2007 with Service Pack 2 (SP2), Project Server 2007 with SP3, Project Server 2010 with SP1, or Project Server 2013. You must install Visual Studio 2012 on those machines that will participate in configuring the integration and managing projects by using Project Professional.
In this topic
To ask a question of the community, see the following forum post on the Microsoft website: Team Foundation Server and Project Server Integration.
You must have the following software installed before you configure the integration between Team Foundation Server and Project Server:
For administrators of Team Foundation Server:
Visual Studio Team Foundation Server 2012
A version of Visual Studio 2012 or Team Explorer 2012 must be installed on the same machine that will be used to configure the integration of the two server products.
For administrators of Project Server: One of the following versions of Project Server:
Project Server 2007 with SP2. Project Server must be supported by SQL Server 2005 or SQL Server 2008. Also, to enhance performance, you should install the update that the following page on the Microsoft website describes: Description of the Project Server 2007 hotfix package: August 25, 2009.
Project Server 2007 with SP3.
Project Server 2010 with SP1.
Project Server 2013.
For Project Server 2007 and Project Server 2010, the he SharePoint web application for the instance of PWA must be set to Classic Mode Authentication. You will not be able to register it if the authentication is set to Claims Based Authentication.
For Project Server 2013, both Classic Mode and Claims Based authentication are supported.
For project managers: Visual Studio 2012 and one of the following versions of Microsoft Project must be installed on the same machine that will be used to manage enterprise project plans that will participate in data synchronization with team projects:
Project Professional 2007 with SP2 and the update that you can download from the following page on the Microsoft website: Description of the Office Project 2007 hotfix package (Project-x-none.msp): February 23, 2010.
Project Professional 2007 with SP3.
Project Professional 2010.
Project Professional 2013.
Active Directory is not required, but it is highly recommended that you deploy Active Directory in your network to synchronize the accounts of users, groups, and services that are valid within Team Foundation Server and Project Server.
The following table summarizes the software that you must install to support the data synchronization between the two server products. To install software, you must have administrative permissions on the machine where the software is installed.
Visual Studio 2012 or Team Explorer 2012
Each machine on which Project Professional is used to synchronize data between enterprise project plans and team projects and each machine that is used to administer the configuration of the two server products.
Visual Studio Team Foundation Server 2012
Each application-tier server that hosts Team Foundation Server and that will participate in synchronizing data with Project Server. For more information, see Installing Team Foundation Server and Visual Studio ALM.
Team Foundation Server Extensions for Project Server
Each application-tier server that hosts Project Server 2007 and that will participate in synchronizing data with Team Foundation Server.
Each web-tier and application-tier server that hosts Project Server 2010 and that will participate in synchronizing data with Team Foundation Server.
For more information, see How to: Add Project Server to Team Foundation Server.
Before you can synchronize data between the two server products, you must first configure several points of integration between them. The following sequence describes the main configuration elements that are required:
Project Server must be configured. Before you configure the integration of Team Foundation Server and Project Server, you must have configured Project Server to support your enterprise project plans. You must have defined at least once instance of Project Web Access or Project Web App (PWA) that will participate in data synchronization.
At least one enterprise project plan must be defined. Before you can map the project plan with a team project, you must have created the plan and published it to Project Server.
At least one team project collection must be defined. Before you can map a collection to an instance of PWA, you must define that collection.
The team project that you want to synchronize must be defined. You must have a team project that you will map to an enterprise project plan. You can synchronize data with any team project. Also, before you upload field mappings to a team project collection, you must have defined a team project for that collection.
Configure the integration. As the following illustration shows, you must perform six main steps when you configure the integration of the two server products.
For more information, see Configure the Integration of Team Foundation Server and Project Server.
Customize the field mappings. You will have to customize the default field mappings if you are mapping a project plan to a team project that was created from the Visual Studio Scrum process template.
You may have to customize the field mappings if the team project was not created from a Microsoft process template, either Agile Software Development or Capability Maturity Model Integration (CMMI) Process Improvement. Also, if you have customized the types of work items in your team project, you may have to further customize the field mappings to support data synchronization.
For more information, see Customize the Field Mapping Between Project Server and Team Foundation Server.
To understand how components map to one another and the synchronization process, see the following topics: