A.: AQdevTeam Web Interface is a server-side component. It uses AQdevTeam Server to generate Web pages that provide access to the AQdevTeam database. The Web Interface lets end-users access the database without installing special client software. All they need is their Internet browsers: Microsoft Internet Explorer 5.0 or higher, Netscape Navigator 6.0 or higher or Mozilla 1.0 or higher.

The Web Interface provides a number of basic features that let users view items in a convenient manner and lets administrators perform some tasks. Like AQdevTeam Client, the Web Interface uses the password-controlled login and employs an excellent security system with privileges that allows you to control users' access to each project and item. However, the Web Interface has fewer features than AQdevTeam Client. For instance, it does not let you create or delete projects and item types. You can use it as a database editor with minimum requirements on the client side.

Some Web Interface benefits:

A.: On the server side AQdevTeam Web Interface requires Internet Information Services ver. 4.0 or later.

To access Web pages provided by the Web Interface, you can use any modern Internet browser that supports cascade style sheets. We recommend that you use Microsoft Internet Explorer 5.0 or higher, Netscape Navigator 6.0 or higher or Mozilla 1.0 or higher.

A.: Yes, you can. To specify the computer with the AQdevTeam Server, use the Machine setting in the server.url file that is located in the <AQdevTeam Web Interface>\<Web> folder (that is, the folder that corresponds to the <AQdevTeam Web Interface> virtual directory).

For example:

Machine=MyAQdevTeamServerComp
Machine=192.168.1.100

A.: AQdevTeam Web Interface is a server component. It provides access to the information stored in the AQdevTeam database via Web pages. Since it was designed mostly as a database viewer, it has fewer options when compared with AQdevTeam Client. The Web Interface does not support the features and operations listed below. To use them, employ AQdevTeam Client:

With the Web Interface you can —

Also, the Web Interface does not support events that are handled by client macros and it does not support macros that run when an action is executed. Such functionality is supported by AQdevTeam Client, not by the Web Interface. Server macros and jobs are supported, because they are run by AQdevTeam Server and do not depend on the Web Interface.

A.: In many cases, incorporating AQdevTeam Web Interface into the Web site of your company is a good idea. For instance, instead of writing messages to your support team, your customers may open a page of your site and post a bug report or a suggestion directly to the AQdevTeam database. The reported bug can then be assigned to a developer by a support team member or by AQdevTeam. AQdevTeam can automatically notify developers and support persons every time a new bug report appears.

Without the Web Interface, users will have to write messages to your support team, which, in its turn, should process each message, notify the developers about issues, (possibly) post an issue message to the database, etc. This way is less effective and prone to errors: for instance, a support team member may forget to add a bug report to the database and notify a developer; a developer may forget to fix the issue on time, etc. Using AQdevTeam Web Interface helps you organize the user feedback in a more obvious and solid manner.

The Web Interfaces help system includes a number of topics that explains how you can add Web Interface pages to your Web site. Just search for Incorporating Web Interface into your site in the index.

If you are going to include Web Interface pages in your Web site, you may need to change the visual style of these pages. You can do this by modifying the cascade style sheet that the Web Interface uses. The AQdevTeam Web Interface help system holds a complete description of this CSS.