Administering the Integration of Team Foundation Server and Project Server
Updated: June 2011
As an administrator for the integration of Visual Studio Team Foundation Server 2010 and Microsoft Project Server 2007 with Service Pack 2 (SP2) or Project Server 2010, you must configure the integration of the two server products. When you configure this integration, you define what components participate in data synchronization and what data flows from team projects to enterprise project plans. The initial configuration requires that you install software, grant permissions, register instances of Project Web Access or Project Web App (PWA), and map Project Server components to Team Foundation components. You may also need to customize the types of work items and how fields are mapped to participate in data synchronization. After you configure the integration, you may need to monitor and troubleshoot it.
In this topic
You can download a virtual machine that demonstrates how you can integrate Team Foundation Server and Project Server 2010 so that teams can share data between the two server products. This virtual machine includes enterprise project plans in Project Server that are mapped to team projects in Team Foundation Server, along with sample data to highlight key integration scenarios. The walkthrough documents illustrate four scenarios that simulate the interactions between the project manager, who is working in Project Server, and members of the software development team, who are working in Team Foundation Server. For more information, see the following page on the Microsoft website: Microsoft Team Foundation Server 2010 and Microsoft Project Server 2010 Integration Hyper-V Virtual Machine.
Plan the integration of the two server products. To synchronize data between Team Foundation Server 2010 and Project Server, you must install service packs and feature packs on those machines that will participate in configuring the integration and managing projects by using Project Professional. To understand how you will configure the integration of the two server products, you should understand how Project Server components map to Team Foundation components.
Configure the integration to support a test or evaluation environment. You can use this topic as a quick reference to install software, assign permissions, configure integration, and verify data synchronization.
Configure the integration to support a production environment. You can use this topic to collect the information that is required for configuration, permissions that you must grant, and configuration tasks that you must perform to support a customized integration of the two server products.
Grant permissions to support configuration and data synchronization. You must grant permissions to administrators, service accounts, and team members. You must also make sure that specific service accounts have access as Shared Services Provider (SSP) for the server that hosts SharePoint Products for Project Server.
Map and unmap enterprise project plans to team projects. You define which project plans synchronize data with Team Foundation by defining the association or mappings between project plans and team projects. You can map multiple plans to a team project, but you can map each plan to only one team project.
Manage which work item types participate in data synchronization. To support synchronization of data between an enterprise project plan and a team project, you must specify the types of work items that you want to participate in synchronization. You can define the types when you associate a project plan to a team project, and then you can add or remove types later.
Manage which fields participate in data synchronization. To synchronize data between an enterprise project plan and a team project, you must associate the work-item fields in Team Foundation with the fields in Project Server. You can add fields and specify how they synchronize by customizing the field mapping file.
You can map fields that are associated with pick lists in Team Foundation. However, you must create lookup tables in Project Server to match the pick lists. You cannot automatically synchronize pick lists and lookup tables.
Manage and modify the integration of synchronized components. You can change how components are mapped or list the current mappings by using the TfsAdmin ProjectServer command-line tool. You can review the options and parameters that are provided with this tool and learn about the operations that specific options perform.
Understand the three types of synchronization that occur. The synchronization engine performs three types of synchronization: publishing, status, and approval. This process captures and maintains task-related and resource-related data in both Team Foundation Server and Project Server while respecting the ownership of data by the project manager in the project plan.
Change the configuration or shut down synchronization. You can remove components that you have configured to participate in data synchronization, or you can permanently shut down synchronization. You should always follow the recommended reconfiguration sequence when you remove components from participating in synchronization.
Re-map or re-configure the integration. After you have configured the two server products to support data synchronization, you may need to reconfigure a component before or after you move or delete a team project, project collection, or an application-tier server.
Retrieve the latest synchronization error messages. To help troubleshoot the integration of the two server products, you can display a list of recent synchronization errors. You can display the most recent errors that were logged for a team project collection if you use the /GetSyncMessages option of the TfsAdmin ProjectServer command-line tool.
Troubleshoot synchronization and configuration issues. You can use these topics to resolve problems that can occur during configuration of the two server products or during the synchronization process.