Sharing your corporate SharePoint Server with multiple TFS servers
In my previous posts around TFS and Windows SharePoint Services I explained how you could use WSS3.0 or WSS2.0 with TFS. In many companies you already have a corporate SharePoint Farm. You may want to use that with TFS so you don't have to maintain 2 different sets of portals. This post tries to explain how you could achieve this.
TFS requires
- SQL Reporting services to be present on TFS AT machine
- WSS can be installed on any machine on the network.
Relationship:
There is a circular relationship between TFS, WSS and Reporting. What do I mean?
- TFS uses WSS as the Team Portal. All the documents and process guidance is hosted within WSS.
- When users access their team portal they also want to have access to their reports on the portal so we have links to the reports on the portal. This requires us to know the reporting server URL to redirect the requests made by users.
- TFS also needs to keep track of Reporting and SharePoint URLs for various tasks.
In short:
- TFS needs to know where WSS and Reporting are located
- WSS needs to know where Reporting server is located for a TFS Instance.
Sharing same SharePoint Farm for multiple TFS Instances:
To achieve this we require every TFS instance to have its own Managed path. You can create managed paths using the WSS admin site. As shown in the diagram below TFS_001 TFS Instance should have its unique managed path for e.g. TFS001. Similarly for TFS_002 you should have TFS002.
Following are steps you can use to setup this environment
Note: You can run this tool again for 2nd TFS server by running <TFSInstallDirectory>\tools\TFSWSSConfig
