|
 |
 |
Test Pilot |  |
||||||||
|
Test Pilot Classic Manual |
||||||||||||
Java Installation of Test Pilot's web server component requires that the server, and the server alone, first have a Java Virtual Machine installed. Java 1.1.8 or better running is required. Java is available free from Sun at: Java Servlet Runner Test Pilot for Windows comes in two distributions.
Once Sun's Java VM is installed on the Windows server, the web service software must support running Java programs under the server's control. The software for performing this task is called a Java servlet runner. This is typically implemented using a third party plug-in for the web service software. Apache and Microsoft's servers require a plug-in. We recommend the use of New Atlanta ServletExec as Java servlet runner. It is quite easy to install and the company's technical support is first rate. A trial version downloaded from New Atlanta's web site can be simply upgraded to the full version with the purchase of a serial number. ServletExec is available for the following Windows web servers:
We recommend that you carefully read and follow the installation procedures as outlined in ServletExec's manual. To verify that you have installed Java and the servlet runner properly, attempt to access one of the bundled servlets that are typically included. ServletExec includes a servlet called DateServlet. Access the following URL replacing server.edu with your server's name: http://server.edu/servlet/DateServlet/ You should receive a web page with the current date and time on it. The Distribution There are a number of files and folders included with this distribution. Here is a short description of them: License.TXT - Our software license agreement. You must agree to the terms of the agreement or return the software unused. servlets - This is a directory containing Java program libraries used by Test Pilot. Included are libraries for Test Pilot. Updating Test Pilot as newer versions are released is as simple as replacing the single TestPilot3.jar file located in this directory. Configuring Test Pilot Java servlet runners have a number of options that allow you to specify configuration information. Configuring ServletExec with parameters is accomplished as follows. If you are using another Java servlet runner, consult their manual to see how they accomplish these steps.
Initialization Parameters Setting Information There are parameters to be associated with your TestPilot3 configuration. Here is a list of all supported initialization parameters:
The following arguments are optional and need not be specified if the default values are acceptable.
Servlet Aliases To ensure that your server will direct URL's accessing Test Pilot documents to the Test Pilot servlet, you must create servlet aliases for the extensions used by Test Pilot. That is, if a user accesses a file ending in .tp3, you want the Test Pilot servlet to handle that request. To have the server do so, you need to specify that all requests for files ending in .tp3 should be handled by Test Pilot. An important side effect of using aliases is to secure the files from prying eyes. Any attempt to access the files will be handed off to Test Pilot which protects the files according to your security selections. Create servlet aliases with ServletExec as follows. If you are using another Java servlet runner, consult their manual to see how they accomplish these steps.
Aliases must be created for ALL permutations of character case. As the .tp3 and .tpj aliases are defined above, aliases must be created for the following extensions:
To verify that you have it installed properly, access the following URL replacing server.edu with your server's name: http://server.edu/servlet/TestPilot3/ You should receive a Test Pilot login screen. Security Issues When running under IIS, Test Pilot must be permitted to read and write files and directories on the web server. The user account that Test Pilot uses for access is the Internet Guest Account, typically IUSR_XXXX, where XXXX is your server's NT domain name. Thus, in order for Test Pilot to be able to create assessments and update scores and results, the web server directories must have their file security permissions set to allow the IUSR_XXXX account to read, write, delete and create files in the directory. You would typically accomplish this by right-clicking on a directory icon, selecting Properties and choosing the Security tab. You would then add an entry for the IUSR_XXXX account with read/write/create/delete permission. You can also use these settings to limit where Test Pilot can create assessments on your server. Note that the correct permissions settings to change are file system permissions. Microsoft complicates NT management by maintaining a completely separate security system under the Microsoft Server Management Console. You do NOT want to grant the IUSR_XXXX account any special access under the Server Management Console or you may compromise your server's security. If you limit your permissions modifications to those outlined in the paragraph above, your server's security should remain as secure as IIS servers can be. Installing with Tomcat Under Windows There are a number of files and folders included with this distribution. Here is a short description of them:
License - Test Pilot 3 - Our software license agreement. You must agree to the terms of the agreement or return the software unused. License - Tomcat 3.2.4 - Test Pilot requires a web server to operate. Included in this distribution is a fully configured copy of the Apache organization's Tomcat software for web services. It is an open source freely distributable 100% Java web server. Its license information is in this file. bin\STARTUP.BAT and bin\SHUTDOWN.BAT - These are batch files to start and stop, respectively Tomcat and Test Pilot together.Startup times will vary - do not be surprised if it takes up to two minutes to start Tomcat and Test Pilot. Windows may not properly start these files. If you receive an "out of environment space" message, you need to create shortcuts for these file. The process is as follows: Once you have the shortcuts created, use those icons to start and stop Tomcat and Test Pilot. lib - This is a folder containing Java programming libraries used by Tomcat and Test Pilot. Additions to the standard Tomcat distribution have been the inclusion of Test Pilot. Updating Test Pilot as newer versions are released is as simple as replacing the single TestPilot3.jar file located in this directory. conf - This is a folder containing the configuration files used by Tomcat. The only modifications from the standard Tomcat distribution have been made to the server.xml file for the purposes of running Test Pilot. logs - This is a folder containing the log files generated by Tomcat. Errors, if they occur, will appear in the tomcat.log file in this folder. work - This is a folder containing temporary files and directories generated by Tomcat. webapps - This is the Tomcat web server's home directory. This is where files and folder which will be accessible to the outside world should be stores. It is in this folder or its subfolders that Test Pilot will store its tests and results files. Care should be taken with the WEB-INF subdirectory of the webapps folder. It is in that directory that configuration for the Test Pilot program is stored. Specifically: webapps/WEB-INF/web.xml - This is a file that instructs Tomcat how to configure and run Test Pilot. This file must be edited during installation to set up some important Test Pilot settings. Configuring Test Pilot As noted before, you must edit the webapps/WEB-INF/web.xml configuration file to use Test Pilot. Specifically you must make some substitutions: SERIAL_NUMBER_GOES_HERE - should be changed to the Test Pilot serial number you receive when you purchase Test Pilot. Without a serial number, Test Pilot will periodically cease to function. ADMIN_PASSWORD_GOES_HERE - should be changed to the password you wish to use when creating new assessments. On Windows servers, this is not used. SMTP_SERVER_NAME_GOES_HERE - should be changed to a valid Internet SMTP mail server should you wish to use Test Pilot's built-in e-mailing functions. Web services from Tomcat are by default set up to use port 8080 to prevent conflict with other web servers like personal web services and commercial web server software such as IIS. To access the Tomcat home page with a browser on the same computer as Tomcat, use the following URL: http://localhost:8080/ To access a Test Pilot login screen with a browser on the same computer as Tomcat, use: http://localhost:8080/servlet/TestPilot3/ To access the Tomcat/Test Pilot services from an outside computer, it will be necessary for you to know your computer's IP address or Internet name (usually found on the TCP/IP Control Panel). For example, if your IP address was 128.210.86.32, then you would access the server as: http://128.210.86.32:8080/ If you knew that the Internet name of your computer was bogus.server.edu then you could use a URL as follows: http://bogus.server.edu:8080/ If you are not running any other web services on the Tomcat/Test Pilot server, you can eliminate the need to type ":8080" by setting Tomcat's service port to 80. You accomplish this by editing the conf/server.xml file. Look for the following lines: <Parameter name="port" change them to: <Parameter name="port" Other Initialization Argument Setting Information There are other parameters in the webapps/WEB-INF/web.xml configuration file. Here is a list of all supported initialization parameters:
The following arguments are optional and need not be specified if the default values are acceptable.
To verify that you have it installed properly, access the following URL replacing server.edu with your server's name http://server.edu:8080/servlet/TestPilot3/ You should receive a Test Pilot login screen. |
|
||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||
