AceProject
Intranet Package
Installation Procedure

Welcome to the AceProject installation procedure for your corporate Intranet

This document outlines the detailed procedure required to install AceProject's Intranet package. Click any section below to get redirected accordingly. This way, you can skip the steps you already know or did. Do not hesitate to contact us should you require additional information or technical support.

You received or downloaded a file called yourcompany.zip. It contains all the files you need to install AceProject on your corporate Intranet. Here are the steps for installing AceProject's Intranet package.

Prerequisites

Database Support:

Software Requirements:

Minimum Server Hardware Requirements:

Step 1 - Decompress the .zip file

  1. 1. Créez le dossier suivant : C:\Inetpub\wwwroot\aceproject-intranet\
  2. 2. Unzip the file in the aceproject-intranet folder. The following hierarchy should be created in the aceproject-intranet folder:

Step 2 - Configure Internet Information Services (IIS)

A - IIS 6

  1. 1. Make sure Internet Information Services (IIS) is running.
  2. 2. Right click on "Application Pools", go to "New", "Applicaiton Pool...".
  1. 3. Type in "aceproject" as the "Application pool ID" value and choose "Use default settings for new application pool".
  1. 4. Right-click on the default Web Site (in the tree).
  2. 5. Select "New > Virtual Directory".
  1. 6. You get to the Virtual Directory Creation Wizard.
  2. 7. Click Next >.
  1. 8. Type "aceproject" as the alias for your Virtual Directory.
  2. 9. Click Next >.
  1. 10. Type in the path to the "app" directory.
  2. 11. Click Next >.
  1. 12. Check the Read and Run scripts boxes.
  2. 13. Click Next >.
  1. 14. You have successfully created your virtual directory.
  2. 15. Click Finish.
  1. 16. Right click on "aceproject" and select "Properties"
  1. 17. On "Virtual Directory" tab, go to "Application pool" and chose "aceproject". Click on "OK".
  1. 18. Under the "ASP.NET" tab, select "2.0.XXXXX" as the ASP.NET version number.
  2. 19. Click on "Apply".
  1. 20. Right-click the "aceproject" virtual directory in IIS' left-panel tree and click Properties.
  2. 21. Under the Virtual Directory tab, click on "Configuration".
  3. 22. Under the "Options" tab, check "Enable parent paths".
  4. 23. Click on "OK".
  1. 24. Under the "Documents" tab, check "Enable default content page", remove all pages indicated in this area and then add "login.asp".
  2. 25. Click on "OK".
  1. 26. Repeat steps 4 through 19 (parameter settings included). This time, create a virtual directory called "aceproject-api" which points to C:\inetpub\wwwroot\aceproject-intranet\api . The application name associated with this virtual directory will be called "aceproject-api" and it will be associated to the "aceproject" application pool. 

B - IIS 7

  1. 1. Make sure Internet Information Services (IIS) is running.
  2. 2. Right clik on "Application Pools".
  3. 3. Choose “Add Application Pool...”.
  4. 4. Type in “aceproject” as the name and make sure the other settings are identical to those in the screenshot.
  5. 5. Click on "Ok".
  1. 6. Select "Application Pools".
  2. 7. Select "aceproject".
  3. 8. Click on "Advanced Settings...".
  4. 9. Click on the "..." button for the “Identity" parameter (under "Process Model").
  5. 10. Select "NetworkService" under “Built-in account”.
  6. 11. Click on "OK".
  1. 12. Right-click on the Default Web Site (in the tree).
  2. 13. Select "Add Application".
  1. 14. Type "aceproject" as the alias for your application.
  2. 15. Type in the path to the "app" folder (c:\inetpub\wwwroot\aceproject-intranet\app).
  3. 16. Click on "Select..." and under "Application pool" choose "aceproject".
  4. 17. Click on "OK".
  1. 18. Repeat steps 12 through 17 to create another application called "aceproject-api". This application will point on C:\inetpub\wwwroot\aceproject-intranet\api and will also be associated to application pool "aceproject".
  1. 19. Click on  the "aceproject" application in the left tree and double click on the "ASP" item in the main pane.
  1. 20. Make sure the "Enable Parent Paths" and "Send Errors to Browser" parameters are set to "True", and the "Maximum Requesting Entity Body Limit" parameter to "2147483647" (i.e. 2 GB), then click Apply.
  1. 21. In order to receive detailled error messages in your browser, you must also perform the following configuration. Double-clique on the "Error Pages item for the "aceproject" virtual directory. Right-click on status code 500. Select "Edit Feature Settings". Choose "Detailed errors" and click on "OK".
  1. 22. Select application "AceProject" in the left pane and choose "Authentication" in the main pane.
  1. 23. Select “Anonymous Authentication” and click on “Edit...”
  2. 24. Choose “Application pool identity” and click “OK”
  1. 25. Repeat steps 22 through 24, this time for the “aceproject-api” application.
  1. 26. In the left tree, click on "Application Pools", then "aceproject" in the main pane and "Advanced Settings" in the right pane.
  1. 27. In the "Process Model" section, set  "Identity" to "NetworkService".
  2. 28. Make sure option "Enable 32-Bit Applications" is set to "True" (only required if you have a 64-bit version of Windows Server). This setting allows you to export AceProject data to Excel or CSV format.
  3. 29. Click on "OK".

Step 3 - Set permissions on the "files" folder

When files are attached to a project or task and when AceProject's import function is used, the selected local file is uploaded to the "files" folder on the server, so both IIS applications must have write access to this folder.

  1. 1. Through Windows Explorer, locate the "files" folder on the host machine. It should be located as follows: c:\inetpub\wwwroot\aceproject-intranet\files
  2. 2. Right-click on the "files" folder.
  3. 3. Click on the "Security" tab.
  4. 4. Add the "Everyone" user, and grant it "modify" user rights.
  5. 5. Click on "OK".

The procedure layed out here allows you to perform the recommended installation in which the "files" folder is located on the same server as IIS. For tips on how to install the "files" folder on a server other than the IIS server, you may refer to section "Configuration Procedure for Files Hosted on Server Other than the IIS Server" in the Troubleshooting section, after completing the recommended installation.

Step 4 - Register ADODB.DLL

If you performed a default Windows Server installation, odds are the "ADODB" .Net component was not installed. You may look for the ADODB component in the "c:\windows\assembly" folder. If you do not see it, run the \install\AdodbInstall.bat file included in the .zip of your Intranet package.

You must have disabled the UAC for this part to work fine if you are not logged as "Administrator".

Step 5 - Install your SQL Server Database

In order to use the SQL Server database, SQL Server 2008 or 2008 Express Edition must be installed on your intranet.

  1. 1. Enable CLR by following these steps:

    1. SQL server 2008:

      1. Start "SQL Server Management Studio" and connect to your SQL server.
      2. Right click on your server and select "Facets".
      3. Select the "Surface Area Configuration" facet.
      4. Set "ClrIntegrationEnabled" to "True" and click on OK.
  1. 2. Right-click on your server's name and click Properties.
  1. 3. Click Security on the left panel and make sure "SQL Server and Windows Authentication mode" is selected.
  1. 4. Right-click the "sa" user and click Properties.
  1. 5a. In the "General" page, you can change the "sa" user's password. Please note this password as you will need to insert it in connection strings, later on in the installation procedure.
  1. 5b. Click on "Status" in the left pane and make sure the options are set like this.
  1. 6. Right-click the "Databases" folder and click "Restore Database..."
  1. 7. Click General on the left panel.
  2. 8. Type "aceproject" in the "To database:".
  3. 9. Select the "From device:" option and browse to the blank database "aceproject-blank.bak" file (or to the "aceproject-data.bak" file if you are migrating from an online account) provided in your Intranet package.
  4. 10. Check the Restore box in the table at the bottom.
  1. 11. Click OK to restore the database.
  2. 12. DO NOT FORGET THIS LAST STEP. Run script \ScriptUpdate.sql against your database.
  1. 12.a Choose the DB "aceproject"
  1. 12.b Click on "Execute"

You are now done with setting up the database.

Step 6 - Configure AceProject

To ensure AceProject operates smoothly, you must configure a few things.

All items to configure, except the last item in this section, are located in the app\configuration.asp file.

In certain cases, you might not need to change the default values already set.

You must have disabled the UAC for this part to work fineif you are not logged as "Administrator".

Constant constConnectionString (for ASP file connections to the database)

The connection string tells AceProject where your database is located and how to connect to it.

You will need to modify the connection string by changing a few parameters, such as the server name, the database name, the user ID and the password.

SQL Server

Connection string format:

constConnectionString="Provider=SQLNCLI10;Server=[PUT SERVER HERE];
User Id=[PUT SQL USER ID HERE];Password=[PUT SQL USER PASSWORD HERE];Database=ACEPROJECT"

Example:

constConnectionString="Provider=SQLNCLI10;Server=localhost;User Id=sa;Password=sa$%;Database=ACEPROJECT"
SQL Server Express Edition (with SQLEXPRESS instance)

Connection string format:

constConnectionString="Provider=SQLNCLI10;Server=[PUT SERVER HERE]\sqlexpress;
User Id=[PUT SQL USER ID HERE];Password=[PUT SQL USER PASSWORD HERE];Database=ACEPROJECT"

Example:

constConnectionString="Provider=SQLNCLI10;Server=localhost\sqlexpress;User Id=sa;Password=sa$%;Database=ACEPROJECT"

Four URL constants

You must set the actual URL that will be used to access files located in the "app" folder (using the "aceproject" virtual directory you created). If you installed a SSL certificate, you may define the optional constSecureURL constant.

To force all users to connect in secure mode (https), set the constAlwaysHTTPS constant to True. If that constant is set to True, a value must be indicated for the constSecureURL constant.

Those constants are useful to switch from Secure to Non-Secure connection on the login page. It's also useful to set the clickable links included in each email notification.

Example #1:

Const constNonSecureURL = "http://yourintranet/aceproject/"
Const constSecureURL = "https://yourintranet/aceproject/"
Const constAlwaysHTTPS = True

Example #2:

Const constNonSecureURL = "http://yourintranet/aceproject/"
Const constSecureURL = ""
Const constAlwaysHTTPS = False

The value of constApiURL must indicate the actual URL that will be used to accessthe \api\api.aspx file (using the "aceproject-api" virtual directory you created)

Example:

constApiURL = "http://yourintranet/aceproject-api/api.aspx"

API configurations (file \api\web.config)

In section 6A, you configured the connection string used by some .asp files to connect to the database. The API uses a separate connection. In this section, you must configure how the API connects to the database and set other parameters in regard to the API. These parameters are set in \api\web.config keys located near the bottom of the file, at the end of the <appSettings> section.

1. Open file \api\web.config with your favorite text editor.

2. Locate the following database connection keys:

<add key="SQLServer" value ="localhost"/>
<add key="DatabaseAPI" value ="aceproject"/>
<add key="UserId" value ="sa"/>
<add key="Password" value ="sa"/>

3. Adjust the values of these 4 keys, where necessary, as per the instructions below.

  1. - The SQLServer key represents the machine where SQL Server is located. "Localhost" is the default value and is to be used if SQL Server is on the same machine as IIS. If SQL Server Express or an instance is used on the same machine as IIS, the value should be "localhost\sqlexpress" or "localhost\instancename" . If SQL Server is not installed on the same machine as IIS, the value will need to be specified using one of the following formats: "machinename", "IPaddress", "machinename\instancename" or "machinename,port#".
  2. - The DatabaseAPI key represents the database name. The value should be "aceproject".
  3. - The UserId key represents the SQL login that the AceProject API is to connect to the database with.
  4. - The Password key indicates the password associated with user UserId. The UserId and Password combination specified in these keys must match a login/password combination set in SQL Server.

4. Locate the following key: 

key="AceprojectURL"

5. Replace "yourintranet" in this key by the same value you indicated for "constSecureURL" or "constNonSecureURL" in file configuration.asp, depending on your decision to force HTTPS or not.

6. Locate the following key: 

key="PathToFiles"

                
7. Adjust the 'files" folder location only if you are not using the default
                    location already indicated.

                
8. Save your changes.

Step 7 - Login to AceProject


Congratulations! You are now ready to start using AceProject.

To facilitate the configuration process, we have created a default account in the aceproject-blank.bak database. If you have restored your online account database using file aceproject-data.bak, you may login using your online account username and password.

Here's the procedure to login to AceProject.

  1. 1. Open your favorite web browser to the login page: 
    1. Example: http://yourintranet/aceproject/
  2. 2. Enter the credentials below to connect to the default account (database restored from aceproject-blank.bak) or use your online account username and password (database restored from aceproject-data.bak):
    1. Username: admin
    2. Password: admin
  3. 3. Then, click the "Login" button.
  4. 4. Go to "Admin -> Configuration -> Account Info", and set your account parameters (if working on the default account).

Configure the Custom SMTP Server Options

You must define a SMTP server for sending email notifications. This can be done under "Admin -> Account Info -> Edit Account", under "Custom SMTP Server Options".

The Server Name field is used to enter the custom server's name. This field is mandatory.

Example 1: smtp.yourdomain.com

Example 2 : youservername

The Port Number field is used to enter the custom server's SMTP port. This field is mandatory.

By default, the SMTP port is 25.

The Username field is used to enter the custom server's username required for authentication.

The Password field is used to enter the custom server's password required for authentication.

The SSL Connection Required box lets you choose whether to send emails using a secure or a non-secure connection.

The Send Test Email button lets you test your SMTP server settings by sending a test email.

Installing the mobile version (Not included in the 20 user license)

The following instructions will allow you to install AceProject's mobile version. Do not begin installing the mobile version until the "regular" application is fully installed and functional.

Also note that the mobile version will only be accessible from a mobile device if AceProject is setup as a public facing website and its pages are called by IP address or by domain name.

  1. 1. Right-click on the "aceproject" application in IIS and choose "Add Application".
  2. 2. In the "Add Application" window, call the application "m", associate it to the DefaultAppPool and make the application point to the C:\inetpub\wwwroot\aceproject-intranet\mobile folder.
  1. 3. Open file C:\inetpub\wwwroot\aceproject-intranet\mobile\web.config.
  2. 4. Locate the following keys: 
    key="ApiURL"
    and 
    key="SubDomain"
  3. 5. Replace "yourintranet" in this key by the same value you indicated for "constApiURL" in file configuration.asp.
  4. 6. Replace "aceproject" in this key by the same value you indicated for "Database" in file configuration.asp.

You are now set to use the mobile version. You may call the login page of the mobile version through one of the following URLs: http://yourintranet/aceproject/m or https://yourintranet/aceproject/m

Troubleshooting

Here are the most frequent issues our users encounter when installing and using AceProject. These procedures will help you solve these issues and benefit from AceProject's functionalities at full potential.

Installing Internet Information Services (IIS)

Start IIS Installation through "Server Management - Add Role".

To install IIS 6 on Windows Server 2003, set configurations as illustrated in the screenshots below. Scroll further down for instructions on an IIS 7/7.5 on Windows Server 2008/2008R2 install.





To install IIS7/7.5 on Windows Server 2008/2008R2, set configurations as illustrated in the screenshots below.

When you select the ASP.NET and ASP items, most other role services are automatically selected.





You installed .NET Framework 3.5 before installing IIS

Execute the appropriate command below to integrate the Framework with IIS. Framework 3.5 is an update of Framework 2.0; thus the reference to version 2.0 you see in the folder name.

32 bits: 
C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
64 bits: 
C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i

Installing SQL Server 2008 R2 Express Edition

Download "Microsoft SQL Server 2008 R2 Express with Management Tools", 32 or 64 bits, through the following link:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=967225eb-207b-4950-91df-eeb5f35a80ee

Note: Installing SQL Server on Windows Server 2003 requires you install both Windows Installer 4.5 (which you may download here), and PowerShell (available through Windows Update).

1. Run the SQLEXPRWT_x[86-64]_ENU.EXE (32 or 64 bits) setup file.

2. Select "New installation or add features to an existing installation".

3. On the "Feature Selection" page, select only "Database Engine Services" and "Management Tools - Basic". Then, click "Next".

4. On the "Instance Configuration" page, select "Default instance", and then click "Next".

5. On the "Server Configuration" page, click on the "Collation" tab and on the "Customize" button. In the "Windows collation designator and sort order" area, choose "Latin1_General" and do not check any of the boxes. Click "OK". You should see "Latin1_Genral_CI_AI". If so, click "Next". With Windows Server 2003, you might get an error on the service account tab. If so, select "NT AUTHORITY\NETWORKSERVICE" as the account name for the "SQL Server Database Engine" service and then click "Next".

6. On the "Database Engine Configuration" page, select "Mixed Mode" and enter your password. Click "Add Current User". You can also add other users if you want. Click "Next".

7. Complete the installation.

Installing SQL Server Native Client

If SQL Server is not installed on the same machine as your web server, odds are the "SQL Server Native Client" component is not installed on the web server machine.

Another possible issue lies in the fact the SQL Server 2005 "SQLNCLI" is not identical to the one associated with SQL Server 2008 or 2008 R2.  Since AceProject uses the latest SQLNCLI, you must install the appropriate "SQL Native Client" component.

A "Provider cannot be found. It may not be properly installed." error typically occurs if the proper SQLNCLI component is not installed.

You will then need to install SQLNCLI on the web server, using the appropriate link from the two below, so that the AceProject application may connect to SQL Server.

Windows Server 32-bit system:

Windows Server 64-bit system

Launch and perform a default installation.

Disabling the UAC (User Account Control)

If you are installing AceProject on a Windows 2008 or 2008 R2 system, you will need to disable the UAC if you are not logged in under the "Administrator" account. Having administrator rights on an account other than the "Administrator" account is not sufficient.

1. Launch msconfig (Start - Run - type msconfig). Select "Tools" tab.

2a. Windows 2008: Select "Disable UAC". Click "Launch". Reboot.

2b. Windows 2008 R2: Select "Change UAC Settings". Click "Launch". Set it to minimum value. Click OK. Reboot.

Help menu not displayed (page cannot be found)

If the Help Section is not working, this means that IIS is not configured properly. Here is how this issue can be fixed:

1. Open IIS and right-click the corresponding web site, usually aceproject.

2. Select "Properties -> Home Directory".

3. Click the "Configuration" button.

4. Click the "Options" tab and check the "Enable Parent Paths" box.

Activate JavaScript in Internet Explorer (for users)

If you find that AceProject's left menus are displayed poorly or do not work at all, it is likely that your web browser has disabled JavaScript. In order to display AceProject's menus properly, JavaScript must be enabled.

1. Go to "Tools -> Internet Options".

2. Click the Security tab.

3. Click Internet in the Web content zone

4. Set the sliding bar to Medium.

5. Click the "Custom Level…" button.

6. In the new window, scroll down to Scripting

7. In the sub-section Active scripting, click enable.

8. Click the OK button.

9. Click OK to close the options window.

If you only want to activate JavaScript for certain sites, choose Trusted sites instead of Internet in the web content zone, then activate JavaScript as described above. All you have to do is click on the Sites… button to add trusted websites.

Browser Refresh Problem

AceProject being a dynamic site, your Internet browser needs to be set to automatically download every page, instead of using the one stored in your browser cache. If you notice strange behaviour in AceProject (for example tabs that do no refresh or recent changes that are not displayed), you may need to set your refresh settings correctly.

How to set automatic refresh in Internet Explorer:

1. Go to "Tools -> Internet options".

2. Click the General tab.

3. In the middle of the window, click the "Settings…" button.

4. Click "Automatically" in the "Check for newer versions" of stored pages section.

5. Click OK to close the window.

6. Click OK to close the Internet Options window.

Windows 2003 File Upload Size Problem

When users upload file attachments to AceProject tasks, they may encounter problems with larger files. If you use Windows Server 2003, IIS 6.0 prevents the upload of files more than 200 Kb. You need to change this parameter to a higher value to allow larger files.

For IIS 6.0 users, the AspMaxRequestEntityAllowed property specifies the maximum number of bytes allowed in the entity body of an ASP request. If a Content-Length header is present and specifies an amount of data greater than the value of AspMaxRequestEntityAllowed, IIS returns a 403 error response.

This property is related in function to MaxRequestEntityAllowed, but is specific to ASP request. Whereas you might set the MaxRequestEntity Allowed property to 1 MB at the general World Wide Web Publishing Service (WWW Service) level, you may choose to set AspMaxRequest EntityAllowed to a lower value, if you know that your specific ASP applications handle a smaller amount of data.

How to set the maximum file size allowed for upload in IIS 6.0

1. Stop the IIS service before making changes.

2. Open your metabase.XML which is located in c:\Windows\System32\Inetsrv

3. Find the line AspMaxRequestEntityAllowed and change it to 1073741824. This is 1GB - of course you can enter another value to suit your needs.

NOTE: Before you edit the file, be sure to stop the IIS service first or else you won't be able to save the file.

Date Issue with Non-English Servers

You may have a date issue if you install AceProject on a non-English Windows Web server, or when using a non-English SQL Server. Since AceProject saves dates in US format, default non-English server installation may not save dates in US format. This issue only occurs with SQL databases. It can be fixed with minor modifications.

The user specified in the connection string of the "configuration.asp" file must be set as an English user. For example, if the user is named "aceproject", you should run the following SQL query to fix the issue:

EXEC sp_defaultlanguage 'aceproject', 'english'
DBCC useroptions

PS: We recommend that you do not use the 'sa' user. We recommend you create another user to connect to the database.

Issue with "Plain Text" mode

You might encounter errors when switching to "Plain Text" mode in fields where this option is supported (Details and Comment fields at the task level and Message field in the Discussion forum). You will need to enable CLR integration in SQL Server for this function to operate correctly. Here's how:

SQL server 2008:

1. Start "SQL Server Management Studio" and connect to your SQL server.

2. Right click on your server and select "Facets".

3. Select the "Surface Area Configuration" facet.

4. Set "ClrIntegrationEnabled" to "True" and click on OK.

"Page Cannot be Displayed" Error

If the Intranet package installation is not installed properly on a first try, your Web browser may not be able to tell you what the problem is exactly. In such a case, you would get a "Page Cannot be Displayed" error message.

However, in order to fix the issue, you need to know what the issue is exactly. Your browser can be set to display "HTTP Non-Friendly Error Messages" in which you can see all details related to the error. Here's how you can activate this option:

1. Open Internet Explorer

2. Tools -> Internet Options

3. Advanced tab

4. Uncheck Show friendly HTTP error messages

5. Apply.

6. Try to generate your error again and you should get a more detailed error message.

Session Timeout Issue

The "Timeout" value is set in file "configuration.asp". Even If the value is set in accordance with your needs, it may not work properly. You may have to set the timeout value elsewhere on your web server if you think it doesn't work. There are several places where you can set the timeout value, here are a few of them:

at the IIS level;

at the Application Pool level;

at the Virtual Directory level;

You may have to change the timeout value at all above-mentioned levels.

NOTE: According to our tests, the "session.timeout" value prevails over all above-mentioned parameters. The value of session.timeout is in minutes.

Example (recommended):

session.timeout = 480

Active Server Pages Not Allowed (Windows Server 2003)

This issue occurs when .asp pages cannot be displayed in Windows Server 2003. By default, Windows Server 2003 doesn't allow .asp pages to be executed. As a result, the "login.html" page will be working but "login.asp" won't.

Here's the procedure to fix this issue (see screenshot):

  1. 1. Open IIS and locate "Web Service Extensions" on the left tree.
  2. 2. Click "Active Server Pages" on the right list.
  3. 3. Click the "Allow" button to allow ASP pages to be executed.

Number of Task Details kept in the History Table (in file configuration.asp)

This is the number of task detail changes kept in the history table in the database. Increasing this number will increase the task history table size. Accepted values are integers equal or above zero (0) Set this value to zero (0) to keep no task detail change in the history table.

Example:

Const constTaskDetailsMaxHistory = 3

Configuration Procedure for Files Hosted on Server Other than the IIS Server

To be able to locate files on a Server different than the IIS Server, a shared folder setup on the file Server is necessary. A UNC path to the shared folder must be used rather than a drive letter mapping because there is no guarantee that the drive letter would be available to the user under which the Aceproject web site would be executed at runtime.

You should therefore create a network domain user specifically for AceProject and assign this user to all applications and application pools used by AceProject. Define a shared folder on the file server and setup Read/Write access on it for the new domain user. Finally, adjust the "PathToFiles" entry in \api\web.config file to make it point to the shared folder using a UNC path syntax, along the following lines…

<add key="PathToFiles" value="\\YourFileServer\files" />

Here is a step-by-step:

  1. 1. Create a user specifically for AceProject on your network domain.
  2. 2. Assign the user created in step 1 to the website application pool. The application pool may be found as illustrated below.
  1. Please note that if the application pool is different for the AceProject and AceProject-Api websites, changes should be applied on each application pool.

  1. 3. Assign the user created in step 1 to the AceProject and AceProject-Api websites.

Customize AceProject

The standard Intranet package contains a compiled API. Therefore, customizations are more or less limited to the look and feel of AceProject. You may modify the .html pages in the /app folder which are the interface template pages called by the corresponding .asp file.

Be careful not to remove or alter the special tags that ensure proper data display. Field and button labels are usually defined near the top of the .asp files. Menu items are defined in xml files located in /app/menu/XML/. Before modifying any AceProject file, you must agree to the License Agreement included in your package.


Note:

If your changes hinder AceProject's ability to operate, you will need to make the repairs yourself or contract Websystems Inc. to do it at the regular hourly rate.