Installation Guide

You can also download the installation guide here (disabled now, the latest version is in HTML below)

Table of Contents

Installation of Internet Information Services (IIS)

Before installation of IIS, please install the following:

  1. Microsoft Visual Studio .Net 2005
  2. Microsoft SQL Server 2005 with Management Studio installed (Management Studio is located on the 2nd installation disk).
  3. Microsoft .Net Framework 2.0 Download

If you already have IIS installed, please skip this section and go onto the installation of APOGEE.

Windows XP

Step 1

Open the Control Panel, from the Start Menu, and open Add/Remove Programs.

Step 2

On the left sidebar, click Add/Remove Windows Components, scroll down, and check off the checkbox next to Internet Information Services (IIS).

IIS

Step 3

Follow the prompts and insert your XP Disk when asked to. Follow the remaining prompts to continue the installation.

You will need your Windows XP Pro installation disk. Go to the Control Panel, from the Start Menu, and open Add/Remove Programs. On the left sidebar, click Add/Remove Windows Components, scroll down and check off the checkbox next to Internet Information Services (IIS). Insert your XP Pro disk and follow the prompts to continue the installation.

Windows Server 2003

Open the server manager in Start->Programs->Administrative Tools->Manage Your Server.

Step 2

Click Add or Remove a role, and select Application Server.

Step 3

Check the Enable ASP.NET checkbox.

Step 4

Follow the prompts, inserting the Windows Server 2003 Disk when asked to. The setup will copy files, and will complete the installation.

Installation of APOGEE

Step 1

Download the files from here.

Step 2

Extract a copy onto somewhere on C drive (e.g., on desktop). Do not remove this folder after installation! APOGEE needs this local copy for writing temporary files.

Step 3 (Updated!)

Locate the WatiN folder in APOGEE project folder, and double click on WatiN-1.2.1.4000-net-2.0 installer. Follow the instructions and have WatiN for ASP.Net 2.0 installed.

Step 4 (Updated!)

We need to modify two sections of the configuration file. In Web.Config in the main ProtoAPOGEE folder, modify: (1) key "APOGEEDB" so that "Data Source=GSW475\SQLEXPRESS;" is "Data Source=server\SQLEXPRESS;" (if you're using SQL Express) or "Data Source=server;" (if you're using SQL Server Standard) where "server" is the name of your computer (To look for the name of your computer: Start Menu --> Right Click on My Computer --> Select "Properties" --> Click the "Computer Name" tab). (2) key "ProjFolder" so that it contains the actual installation path of APOGEE in step 3.

In your web.config file locate the line about "identity impersonate" and set it as the following. The "username" should be the administrator account that you plan to run the application as.

<identity impersonate="true" username="server\username" password="yourpassword" />

Enter the "genProjRpt" folder, and open the file "App.config". Modify the "APOGEEDB" entry correspondingly. Set the value of "ProjFolder" to the actual path of "genProjRpt" (e.g., "C:\Xiang\Research\Projects\ProtoAPOGEE\Latest\ProtoAPOGEE3\genProjRpt").

Step 5

You may have to precompile the application. To do this, first open the .sln in Visual Studio 2005.

Step 6

Next select Build->Clean Solution; Build->Rebuild Solution. Press "F5" to run the project, you should be able to see the log-in page of APOGEE. (However, you won't be able to log in as the database has not be restored yet.)

Configuration of APOGEE and IIS

Step 1

Open the IIS manager by going to Start->Run, type 'inetmgr' in the box execute.

Step 2

Expand the items until you get to "Default Web Site." Right click it and click New->Virtual Directory.

IIS

Step 3

Enter "APOGEE" as the name for your virtual directory.

Step 4

When IIS asks you for the location of "APOGEE", create a sub-folder named "APOGEE" under "c:\inetpub\wwwroot".

Step 5

Select Read and Run scripts (such as ASP) as the only two access permissions for the virtual directory.

IIS

Step 6

Open Visual Studio command prompt (located at Start->Microsoft Visual Studio 200x->Visual Studio->Visual Studio 200x Command Prompt). In this prompt, issue the following command: "aspnet_regiis -i". Please notice that this step is very important -- this is to tell windows xp/2003 server to use asp.net v2.0 as the main platform.

Note: if you are running 64-bit system you have to specify the path of the aspnet_regiis so that the right version is used . You should be able to find the right version of the aspnet_regiis file of the 64-bit system in "c:\windows\Microsoft.Net\Framework\version...".

IISReg

Step 7 (updated!)

Now open the ProtoAPOGEE (extracted on desktop) again. Click "Build->Publish Website". Click the "..." button, then select "local IIS" on the left, finally select the "APOGEE" virtual directory to publish. Note that you do NOT have to update the web.config and app.config files for the copy published to IIS. This is because the running APOGEE instance in IIS will access the extracted APOGEE copy for writing temporary files (instead of accessing the copy in c:\inetpub\wwwroot). This increases the security of APOGEE). After this, the website should be accessible from http://localhost/APOGEE/Default.aspx (APOGEE won't be working just yet, since we need to configure the database).

Configuration of the APOGEE Database

Preliminary Note:

As before, depending on your version of SQL Server, you may have to replace "server" with server\SQLEXPRESS (for SQL Express) or leave it as is (for SQL Server Standard) where "server" is your computer name.

Step 1

Open the Windows command prompt and enter "osql -S server -E". Then issue the following commands: (note the "$projectpath" is the path to the project folder. If necessary append "WITH REPLACE" to the restore command.)

1> restore database APOGEEDB from disk='$projectpath\DBBackup\APOGEEDB2.bak'
2> go
3> EXEC sp_dboption 'APOGEEDB', 'recursive triggers', 'true'
4> go
5> quit

DBRestore

Step 2

In order to set up the proper permissions for the database, we need to launch SQL Server Management Studio (or SQL Server Management Studio Express). If you do not have the management studio installed, SQL Server Management Studio Express can be downloaded from http://www.microsoft.com/downloadS/details.aspx?familyid=C243A5AE-4BD1-4E3D-94B8-5A0F62BF7796&displaylang=en.

Step 3

We must create a user called 'server/ASPNET' for SQL Server. To do that, click the top-level database server (note: NOT FOR APOGEEDB, it's the security tab of the root node!) , and in the window that appears on the right, double click Security, right click Logins, and click New Login. Create a login "server\ASPNET" where server is the name of your computer, or the server that SQL Server is running on.

Please repeat the above procedure for "server\administrator" (the "administrator" refers to the name of the admin user account you use) and "NT Authority\System" (i.e., the "local system". Click the "search" button, type "System" in the dialog, and click "check name" to search for the complete name).

Step 4

Then, we must create a user specific for the APOGEE database. Drill down Databases until you get to APOGEEDB. Double click Security, right click Users and click New User. For login name, you need to put server\ASPNET. For both Schema owned by this user, and Database role membership, select db_datareader, db_datawriter, and db_owner. That should be it for the permissions.

Please repeat the above procedure for "server\administrator" and "NT Authority\System".

SQL

SQL

Configuration of Permissions

Windows XP

Step 1

To make sure that we have the correct permissions to launch Internet Explorer, we need to start up the DCOM configuration manager. Start->Run->'dcomcnfg'

Step 2

Double click Component Services, then Computers, then My Computer, then DCOM Config (if you get a warning, just press yes).

Step 3

Find the "Internet Explorer (Version 1.0)" and right click, and select properties.

Step 4

Go to the location tab and make sure the following are selected: "Run application on the computer where the data is located" and "Run application on this computer."

Step 5

Go to the security tab, and for both Launch and Activation Permissions and Access Permissions, select customize, and edit as follows:

Add an ASPNET user, as well as another admin user that will be logged on while the application is running (must have administrative access), and check off all the boxes under allow.

Step 6

Then, go to Control Panel->Administrative Tools->Local Security Policy.

Step 7

Trickle down through Local Policies to User Rights Assignment and right click "Act as part of the operating system" and select properties.

Step 8

Add the two users that you added before (ASPNET and your admin user account).

Step 9

Now to set up permissions so that screenshots will be allowed, go to C:\WINDOWS\Microsoft.Net\FrameWork\\CONFIG and make a backup of 'machine.config,' 'machine.config.comments,' and 'machine.config.default.'

Step 10

In machine.config, replace the line "<processModel autoconfig="true" />" with "<processModel enable="true" userName="System" />"

Step 11: Make Service Available

SQL

Go to control panel -> admin tools -> services and right click on "IIS Admin", click on the "Log On" tab and select "Log on as: Local System". In addition check "Allow service to interact with Desktop".

Repeat the above for the "World Wide Web Publishing Service"

After the above setting, start an IE browser from local host to access and run a testing instance of APOGEE first. Minimize the local instance and keep it in desktop taskbar. Then you can test APOGEE from a remote browser. The screen shot should be working. You should keep the account logged on for screen shot function of the application to work.

Step 12

We may get a dialog that pops up every time a project is submitted telling you about a security warning when attempting to run the report generator. You can disable this by going into the Group Policy Manager. You can do this by going to Start->run and inputting gpedit.msc. Then, go to Local Computer Policy->User Configuration->Administrative Templates->Windows Components->Attachment Manager. In the Attachment Manager, find "Inclusion list for low file types," right click, and click properties. Make sure it is enabled, and in the box below, add ".exe" to the list. Restart you computer.

Windows Server 2003

Step 1

To make sure that we have the correct permissions to launch Internet Explorer, we need to start up the DCOM configuration manager. Start->Run->'dcomcnfg'

Step 2

Double click Component Services, then Computers, then My Computer, then DCOM Config (if you get a warning, just press yes).

Step 3

Find Internet Explorer and right click, and select properties.

Step 4

Go to the location tab and make sure the following are selected: "Run application on the computer where the data is located" and "Run application on this computer."

Step 5

Go to the security tab, and for both Launch and Activation Permissions and Access Permissions, select customize, and edit as follows:

Add the "System" user, the "IIS_WPG" as well as an administrator user that will be logged on while the application is running (must have administrative access), and check off all the boxes under allow.

Step 6

Then, go to Control Panel->Administrative Tools->Local Security Settings.

Step 7

Trickle down through Local Policies to User Rights Assignment and right click "Act as part of the operating system" and select properties.

Step 8

Add the three users that you added before (System, IIS_WPG, and your admin user account). Note that for IIS_WPG, click the "Object Types" button of the "Select Users or Groups" dialog (when you check the name of the user) and check "groups". Then system will search for the complete name of the IIS_WPG group).

Step 9

Now launch "Internet Information Services" admin module from control panel -> admin tools. Drill down to "Application Pools" and create a new application pool named "APOGEEAdmin". Right click on "APOGEEAdmin", choose "properties" in the popup menu, and then click the "identity" tab, and select "Local System" as the identity of "APOGEEAdmin". Then drill down to "Website" and find the "APOGEE" application. Right click on "APOGEE" and set its application pool to "APOGEEAdmin". Thus, when the web application is running, its identity is "Local System". When necessary, its impersonation identity is escalated to "Administrator" for taking screen shots (this is needed when windows GDI32 API is invoked for taking screen shots).

Step 10: Make Service Available

SQL

Go to control panel -> admin tools -> services and right click on "IIS Admin", click on the "Log On" tab and select "Log on as: Local System". In addition check "Allow service to interact with Desktop".

Repeat the above for the "World Wide Web Publishing Service"

After the above setting, start a browser from local host to access and run a testing instance of APOGEE first. Minimize the local instance and keep it in desktop taskbar. Then you can test APOGEE from a remote browser. The screen shot should be working. You should keep the account logged on for screen shot function of the application to work.

If the IIS does not interpret the default.aspx at all, you should go to Control Panel --> Admin Tools --> Internet Information Services (IIS) Manager --> "Web Service Extensions" and enable the Active Server Pages (ASP).

Step 11

We may get a dialog that pops up every time a project is submitted telling you about a security warning when attempting to run the report generator. You can disable this by going into the Group Policy Manager. You can do this by going to Start->run and inputting gpedit.msc. Then, go to Local Computer Policy->User Configuration->Administrative Templates->Windows Components->Attachment Manager. In the Attachment Manager, find "Inclusion list for low file types," right click, and click properties. Make sure it is enabled, and in the box below, add ".exe" to the list. Restart you computer.