There are 5 short steps in installing FogBugzPd
  • Set up web application in IIS
  • Connect to Database
  • Test installation
  • Configure FogBugzPd to use your FogBugz
  • Change Local Login settings

Prerequisites

  • .NET 4.5
  • Free Sql Server Express 2008/2012 or Sql Server Professional/Enterprise/Developer 2008/2012
  • IIS 7+

Step 1: Set up web application on iis

Download and unzip files from latest FogBugzPd Stable Release:
https://fogbugzpd.codeplex.com/releases


Use the following instructions to set FogBugzPd as a separate web-site
http://www.codeproject.com/Articles/280137/How-To-Deploy-a-Web-App-in-IIS


You can aslo setup FogBugzPd as a web application under already existing website like:
http://fogbugz.acme-corp.com/FogBugzPd


Here is an example of setting up web-app under Default Web Site
http://msdn.microsoft.com/en-us/library/ha2y9493(v=vs.100).aspx

In both cases, web site or web application, make sure that Application Pool targets .NET 4.

Step 2: Connect to Database

Connection string to database is stored in Web.Config located in root direction of FogBugzPd web application.

Sql Server Express

By default connection string is:

  <connectionStrings>
    <add name="ConnString" providerName="System.Data.SqlClient" connectionString="Data Source=.\SQLEXPRESS;AttachDbFileName=|DataDirectory|FogBugzPd.mdf;Integrated Security=True;User Instance=True" />
  </connectionStrings>


This uses Sql Server Express and points to Database in /<FogBugzPd Web>/App_Data?FogBugzPd.mdf

The file doesn't exist, but gets created the first time you open the web application. For the file to get created correctly you need to add Modify Permissions to /AppData directory for IUSR<Name of the Machine>

Set_Modify_Permissions_To_App_Data.png

Sql Server Developer/Professional Enterprise

If you already have Sql Server installed and would like to use it instead of Express:

1. Create new empty DB on the Sql Server. Call it "FogBugzPd"

Create_FogBugzPd_Database.png

2. Create user "fogbugzpd" and map it to FogBugzPd DB as owner

Create_Db_User_Step1.png

Create_Db_User_Step2.png


3. Update connection string in Web.Config to point to the empty database. Connection string will look like this:

  <connectionStrings>
     <add name="ConnString"
		   providerName="System.Data.SqlClient"
		   connectionString="Data Source=YourDbServerName; Initial Catalog=FogBugzPd; User Id=fogbugzpd; Password=PasswordYouUsedFor_fogbugzpd_user"/>
  </connectionStrings>

Step 3: Test installation

At this point Web Application should be fully functional. Go ahead and open it in your favorite web browser.

If everything was installed correctly you should see:
Login_Screen.png

Use "admin/admin" and click "Login" to login. It will log you in into our Demo FogBugz account and all the pages should be functional.

If you are getting errors. Please go through the first two steps again to make sure you didn't miss anything. If you are still having issues please contact using our support Form:
ur:http://www.entechsolutions.com/contact

and we will get back to you shortly.

Step 4: Configure FogBugzPd to use your FogBugz

Now that you made sure that FogBugzPd works with demo account you can point it to your own FogBugz account. To do that, update the following lines in Web.Config:

    <add key="FogBugz_Url" value="https://fogbugzpm-demo.fogbugz.com" />
    <add key="FogBugz_Username" value="igor@entechsolutions.com" />
    <add key="FogBugz_Password" value="igor12" />



FogBugz_Url Where u installed FogBugz, like "http://fogbugz.acme-corp.com"
FogBugz_Username Username of a fogbugz users that will be used to pull information out of FogBugz. Preferrably this user should have administrative privileges and only used for FogBugzPd. So creating a user "fogbugz" would make the most sense. But you can use any already existing user also.
FogBugz_Password Password used for user from row above


After saving web.config, open FogBugzPd in browser and make sure your List Project/Milestones page lists the projects from your fogbugz account.

Step 5: Change Local Login settings

By default all FogBugzPd users will use admin/admin to login. That can be easily changed using the following entries in Web.Config:

    <add key="LocalLogin_Enabled" value="true" />
    <add key="LocalLogin_Username" value="admin" />
    <add key="LocalLogin_Password" value="admin" />



LocalLogin_Enabled Allows you to enable/disable LocalLogin. If you are installing FogBugzPd behind firewall not accessible externally, you can disable LocalLogin, so users will bypass login screen
LocalLogin_Username Local username used for FogBugzPd login
LocalLogin_Password Password used for FogBugzPd login


After saving web.config, open FogBugzPd in browser and make sure your Local Login settings are working.

Extra Credit : FogBugzPd Settings in GUI

When you login the first time, in top right corner you will notice a Settings button.
Gui_Settings.png

These settings are used to enable/disable various options for accessing and processing your FogBugz information. You can hover over each option to see what it does. I will be providing more advanced info for these options in my blog: http://www.entechsolutions.com/blog so please check it regularly or through RSS.

This Settings screen is accessible to all users using FogBugzPd so after you configured the settings it is good idea to prevent users from messing with them in the future. To do that you need to open Web.Config and add new entry to AppSettings section:

 </appSettings>

  <add key="HideSettings" value="1>
 <appSettings>

This will hide "Settings" from all logins. If you need to modify Settings again in the future open Web.Config again and temporarily set value of "HideSettings" to "0"


===============================================
That is the end of the installation guide.

If you have Feedback about it please use: DISCUSSIONS and FEEDBACK sections for this project in CODEPLEX.

Or you can contact our support directly (if urgent):
ur:http://www.entechsolutions.com/contact

Last edited Jul 29, 2013 at 8:42 AM by ericpopivker, version 7

Comments

No comments yet.