How to install SocialTFS Proxy Server

Before starting note that if you want to update SocialTFS Proxy Server without losing stored data you must follow the guide How to update SocialTFS Proxy Server.
To install the SocialTFS Proxy Server, download the last version of SocialTFS from http://socialtfs.codeplex.com/releases and unzip the package.
The Proxy Server is in the file SocialTFSProxyServer.zip.

First of all you must run SQL Server Management Studio (if you don't have it already installed on your system, check this guide or this one), login via Windows Authentication with an administrator account and open the Server Properties from the context menu of the connection in the Object Explorer pane on the left.

ip0.1.png


Then you need to open the Security page from the left menu and switch from "Windows Authentication mode" to "SQL Server and Windows Authentication mode" in the Server authentication section.

ip0.2.png

Now you must restart the server from the context menu of the connection in the object explorer pane on the left and then you can close the SQL Server Management Studio.

ip0.3.png


Now it's time to configure the IIS 7.* web server.
Now you need to run IIS Manager. If you don't find IIS Manager application, then IIS is not installed. To install it, click Start, and then click Control Panel. In Control Panel, click Programs, and then click Turn Windows features on or off.

controlpanel.png


In the Windows Features dialog box, click Internet Information Services to install the default features, and then select the following additional features:
  • ASP.NET
  • .NET Extensibility
  • Request Filtering
  • ISAPI
  • ISAPI Extensions
  • Server Side Includes

In case of further doubts, this is a screenshot of one our IIS setup for a typical SocialTFS installation.

IISsetup.png


Click OK to close the Windows Features dialog box. To verify that IIS installed successfully, type the following into a Web browser: http://localhost and you should see the default IIS Welcome page.
For more information about setting up IIS adn ASP.NET application, refert to this guide.

Now that IIS is installed, try to run IIS Manager again, then select the sites folder on the left and add a new web site from the menu on the right.

ip1.png


Choose site name (SocialTFS), physical location and let the IIS Manager creates a new application pool (SocialTFS). If you want, change the other settings as you wish.

ip2.png


Now select the application pools folder on the left, select the application pool you just created (SocialTFS) from the central view; double-click on it and check or change the option Managed Pipeline mode from Integrated to Classic.
Then, and open the advanced settings from the menu on the right.

ip3.png


In the advanced settings window select the version 4.0 for the. NET Framework, LocalSystem for Identity and confirm.

ip4.png


Now select the site you just created (SocialTFS) from the sites folder on the left and start the application import procedure from the menu on the right. If you don't see any Import entry in the menu, then you need to install the Web Deploy package from here.

ip4.5.png


On the first page of the wizard enter the path to the file SocialTfsProxyServer.zip just unzipped and go to the next page.

ip5.png


The second page of the wizard shows the contents of the package. Make sure that everything is selected except UpdateScript.sql and go to the next page.

new_ip6.png


On the third page of the wizard enter the path to the application (it is preferable to leave it blank). Please, do not change the database connection strings: the first will be used to create a database (SocialTFS) and a SQL Server user (SocialTFS) owner of that database; the second will be used by the Proxy Server to connect to the database. We strongly recommend to change the database connection password by following the guide How to change connection password after SocialTFS Proxy Server installation.

Should the content of the two fields be diffent from what shown in the figure below, try to copy and paste the following values:
  • data source=.\SQLEXPRESS;Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;User Instance=true
  • Data Source=SERVERNAME;Initial Catalog=SocialTFS;User ID=SocialTFS;Password=●●●●●●●●●●●●●●●●●●●●●●●●●●●●●

ip7.png


The fourth page of the wizard shows the results of the application import procedure.

ip8.png


Now select the folder AdminPanel from the site you just created (SocialTFS) on the left and double click on the Directory Browsing item from the central view.
ip9.png

Finally enable directory browsing from the menu on the right. This allows access from any browser to the admin panel.

ip10.png


The installation is complete.
Now you can access the admin panel at http://<socialtfs_proxyserver_host_address>/adminpanel. You can login by setting to admin both username and password. It's suggested to change this credentials as soon as possible.

If browsing the web site gives you a HTTP Error 404.17, then you have to enable .Net Framework4.0 on your IIS server. If you have installed .Net Framework4.0 on your IIS server, please run "aspnet_regiis -i" in C:\Windows\Microsoft.NET\Framework\v4.0.{your version}.

If browsing the web site gives you a HTTP Error 404.2 – Not Found, then you have to go to IIS Manager and properly set the ISAPI and CGI Restrictions for .NET 4.0 applications. To do this, follow these steps:
  • Click Start, type Inetmgr in the Start Search box, and then click Inetmgr in the Programs list.
If you are prompted for an administrator password or for confirmation, type the password, or click Continue.
  • Select the server name in the Connections tree view.
  • In Features view, double-click ISAPI and CGI Restrictions.
  • Right-click the restriction that restricts the requested ISAPI resource or the requested CGI resource, and then click Allow (.NET 4 application in our case).

Note: If you want to uninstall the proxy server you need to delete the site, the application pool and the database. The first two operations are performed via the IIS Manager, while the third should be done using a tool such as SQL Server Management Studio.

Last edited Apr 24, 2013 at 5:07 PM by nsanitate, version 26