| Java Device Test Suite Tester’s Guide |    
|
| C H A P T E R 3 |
|
Updating the Tester Harness |
This chapter describes how to how to update the tester harness. The Central Installation must be updated before you update the tester harnesses. Check with your administrator to find out if the Central Installation has been updated.
The chapter contains these sections:
Download the Java Device Test Suite updaters from the Java Device Test Suite licensee web site at https://javapartner.sun.com. Download one or both sets of updater files:
jdts_tester-version-update-build_solaris-date.bin (tester harness updater)
jdts_tester-version-update-build_windows-date.exe (tester harness updater)
The value of version is the version of the Java Device Test Suite that running the updater creates. The value of build and date depend on when the software was built.
The updaters have the same resource requirements as the installers, described in Installation Requirements.
You can update a tester harness installation interactively with a graphical user interface or with a command line script.
|
1. Ensure that the central installation is updated before you begin the tester harness update.
Check with your administrator to be sure the central installation is updated.
2. Ensure that the Relay is running.
Verify by entering this URL in a web browser: http://relayHost:relayPort/appContext
For example: http://localhost:8080/JdtsServer. An administrator can give you the values for relayHost, relayPort, and appContext.
The Relay displays a page similar to FIGURE 2-1 if it is running.
3. Ensure that no tester harness is running.
You must arrange for all harnesses to be shut down while the tester updater runs.
Double click jdts_tester-version-update-build_windows-date.exe.
Enter the following command at the prompt:
% sh jdts_tester-version-update-build_solaris-date.bin
Depending on processor, disk, and network speed, the updater can take a few minutes to initialize before it displays its first screen.
5. Accept the license agreement and click Next to continue.
6. Specify the current installation location for the tester harness, and click Next to continue.
Click Choose to navigate to the installation directory.
7. Specify a directory containing a Java Runtime Environment software version.
You can choose a JRE software version that is newer than the version you have been using. Installation Requirements describes the supported versions.
8. Review the Update Summary information and click Install.
9. Click Finish when the update process completes.
|
You can automate the update of a tester harness by writing a script that invokes the updater. Invocation examples (ignore line breaks):
> jdts_tester-version-update-build_windows-date.exe -f tester.properties
% sh jdts_tester-version-update-build_solaris-date.bin -f tester.properties
The value of version depends on the version of the updater. The values of build and date depend on when the updater was built.
tester.properties is a text file you create. It can be named anything.properties. However, the full path name of the .properties file must not contain a space.
The .properties file must contain the following lines:
INSTALLER_UI=silent CONSOLE_DIR=pathToInstallDir CHOSEN_INSTALL_FEATURE_NUM=1 CHOSEN_INSTALL_FEATURE_LIST=Update CHOSEN_INSTALL_SET=Update CHOSEN_INSTALL_BUNDLE_LIST=Update CHOSEN_INSTALL_FEATURE_1=Update MY_JAVA_HOME2=pathToJRE
pathToInstallDir is the absolute path to the directory containing the tester harness that is to be updated.
pathToJRE is the absolute path to a directory containing a Java Runtime Environment version described in Installation Requirements. You can specify a JRE software version that is newer than the version you specified when you installed the tester harness.
CONSOLE_DIR=c\:\\JDTS_Tester
Notice that the path characters “:” and “\” must be preceded by “\”.
CONSOLE_DIR=/home/userName/JDTS_Tester
Before updating, verify that the Relay is running by entering this URL in a web browser: http://relayHost:relayPort/appContext
For example: http://localhost:8080/JdtsServer. An administrator can give you the values for relayHost, relayPort, and appContext.
A command line update does not provide visual feedback, console messages, or an error code. You can monitor its progress with an operating system tool that shows the status of processes.
The update is complete when the file CONSOLE_DIR/JDTSversion_ConsoleInstallLog.log has been created. Open this file with a text editor and search for messages containing the string “FATAL”. If there are no such messages, installation was successful. The “FATAL” messages describe the details of the problems encountered, if any.
You can verify the update by launching the tester harness and choosing Help > About the Java Device Test Suite. The display shows Version version RR, where version is equivalent to the version in the updater file name (see Obtaining the Software). For example (your version number might be different):
Running the Graphical Updater