Book Image

Instant Team Foundation Server 2012 and Project Server 2010 Integration How-to

By : Gary P Gauvin
Book Image

Instant Team Foundation Server 2012 and Project Server 2010 Integration How-to

By: Gary P Gauvin

Overview of this book

Developers and project managers managing large software development projects often find themselves at odds during the course of a project. This usually ends with the developers feeling they are wasting time sending status updates, and the project managers feeling that they aren't getting all the information they need to satisfy stakeholders. It doesn't have to be that way! Instant Team Foundation Server 2012 and Project Server 2010 Integration How-to, is a practical format that walks you through what you need to know to get two of Microsoft's most popular products for managing team productivity integrated. We boil down the complex parts to deliver just what you need to know to get started today.The book takes you through the planning, setup, and configuration of Team Foundation Server Extensions for Project Server. Step-by-step instructions are provided with enough detail to get you started without burdening you with a ton of background information. Learn the basics of how to manage the integration as well as a few helpful tips on establishing a test environment, and the basics of how to integrate these server-based technologies. You will learn everything you need to know to get started with planning, installing, and managing the integration.
Table of Contents (7 chapters)

Initial integration configuration (Should know)


These are the minimal steps you'll need to perform in order to complete the initial configuration of Team Foundation Server and Project Server. You may need more steps depending on specific site requirements. Please complete them in the order listed for predictable results.

Getting ready

In order to run the TfsAdmin command-line tool indicated in some of these steps, you will need to run it in an elevated command prompt (right-click on the command prompt in the Start menu and select Run as administrator).

How to do it...

We'll lay the steps out here by subject to make it easy to follow and refer back to later.

Integration

You'll also need to change the directory to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE, or add it to your path. Open the Command Prompt console from the Start menu. Using the following steps you can perform integration:

  1. Register an instance of PWA. Each instance must be registered.

    Tool used: TfsAdmin

    1. Open the Command Prompt console from the Start menu.

    2. Run the following command:

      TfsAdmin ProjectServer /RegisterPWA /pwa:<pwaUrl> /tfs:<tfsUrl>
      

      Replace the <> brackets with the URL, as shown in the following code:

      TfsAdmin ProjectServer /RegisterPWA /pwa:http://tfspsdemo/PWA /tfs:http://tfspsdemo:8080/tfs/
  2. Map the PWA instance with a team project collection.

    Tool used: TfsAdmin

    1. Open the command prompt from the Start menu.

    2. Run the following command (without the <> brackets):

      TfsAdmin ProjectServer /MapPWAtoCollection /pwa:<pwaUrl> /collection:<tpcUrl>

      Replace the <> brackets with the URL, as shown in the following code:

      TfsAdmin ProjectServer /MapPWAToCollection /pwa:http://tfspsdemo/PWA /collection:http://tfspsdemo:8080/tfs/DefaultCollection

    Note

    Map each instance of PWA that supports an enterprise project plan.

  3. Upload default field mappings.

    Tool used: TfsAdmin

    1. Open the command prompt from the Start menu.

    2. Run the following command (without the <> brackets):

      TfsAdmin ProjectServer /UploadFieldMappings /collection:<tpcUrl> /useDefaultFieldMappings

      Replace the <> brackets with the URL, as shown in the following code:

      TfsAdmin ProjectServer /UploadFieldMappings /collection:http://tfspsdemo:8080/tfs/DefaultCollection /useDefaultFieldMappings

    Note

    We must define the field mappings for each project collection that we have mapped to an instance of PWA. You can use the default field mappings to begin with and customize if you need to (many organizations use this right out of the box).

  4. Associate an enterprise project plan with a team project.

    Tool used: TfsAdmin

    1. Open Command Prompt from the Start menu.

    2. Run the following command (without the <> brackets):

      TfsAdmin ProjectServer /MapPlanToTeamProject /collection:tpcUrl /enterpriseproject:<ProjectServerPlanName> /teamproject:<TfsProjectName> /workitemtypes:<ListOfTypes>

      Replace the <> brackets with the URL, as shown in the following code:

      TfsAdmin ProjectServer /MapPlanToTeamProject /collection:http://tfspsdemo:8080/tfs/DefaultCollection/ enterpriseproject:MyEnterpriseProject /teamproject:MyTfsTeamProject /workitemtypes:"User Story,Task"

    Note

    Do not include a space after the comma for the workitemtypes parameter. If you mapped a plan while it was open, re-open it to register the changes. Look for the Publish to Team Project and Work Item Type columns to indicate that the mapping has been completed.

    The /nofixedwork flag is optional. Use this only if you want the Project Server tasks that are mapped to the work items in Team Foundation Server to not be assigned to the Fixed Work task type.

  5. Add team members to the enterprise resource pool.

    Tool used: Project Web App

    On each task that is published to the team project, you need to assign a valid member of the team project as a resource. You also need to identify any team member who submits work items that are synchronized with Project Server. To identify valid contributors, you must add team members from the enterprise resource pool to the resources for the enterprise project plan.

    Note

    Please refer to the detailed instructions at the location Add Team Foundation members to the Team Members group in the recipe Managing Project Server. Also, please refer to details on this function at http://office.microsoft.com/en-us/project-help/add-resources-to-the-enterprise-resource-pool-HA010377760.aspx.

  6. Verify the synchronization.

    The last step in setting up the initial integration is to verify the synchronization. Please refer to Verifying Synchronization in the recipe Managing Project Server.