Initial Configuration Integration for Team Foundation Server 2012 and Project Server 2010

by GaryG 14. October 2013 20:47

Initial integration configuration (Should know)

These are the minimal steps you'll need to complete 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 the 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 directory to C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE, or add it to your path. Open a command prompt from the Start menu. Using the following steps:

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

    Tool Used: TfsAdmin

    1. Open a Command Prompt from the Start Menu.
    2. Run the following command (without the <> brackets):

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

    that is,

    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 command prompt from the Start menu.
    2. Run the following command (without the <> brackets):

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

    that is,

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

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

  3. Upload default field mappings.

    Tool: TfsAdmin

    1. Open command prompt from the Start menu.
    2. Run the following command (without the <> brackets):

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

    that is,

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

    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: 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>

    that is,

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

    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 Project Server tasks that are mapped to work items in Team Foundation Server not to be assigned to the Fixed Work task type.

  5. Add team members to the enterprise resource pool.

    Tool: 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.

    Please refer to detailed instructions at the following 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 synchronization.

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

 

 

About this Except:

Portions of this excerpt were re-published by the author (me).  The full book is available for purchase here http://www.amazon.com/dp/1849688540/?tag=packtpubli-20.  Note that some content may be different (pictures, charts, etc.) as I'm trying to format this post for the web.

Tags:

ALM | TFS

About the author

   
Gary Gauvin is a 20+ year Information Technologies industry leader, currently working as the Director of Application Lifecycle Management for CD-Adapco, a leading developer of CFD/CAE solutions. Working in both enterprise environments and small businesses, Gary enjoys bringing ROI to the organizations he works with through strategic management and getting hands-on wherever practical. Among other qualifications, Gary holds a Bachelor of Science in Information Technologies, an MBA, a PMP (Project Management Professional) certification, and PSM (Professional Scrum Master) certification.  Gary has also been recognized as a Microsoft Most Valuable Professional.

LinkedIn Profile: http://www.linkedin.com/in/garypgauvin

(Note: Comments on this blog are moderated for content and relevancy)


 

Month List

Page List