Starview2-VTT Integration Team Meeting Minutes

June 06, 2000

Next Meeting: June 21, 2000

Attendees:

Discussion:

A preliminary discussion of the scope of this project was already defined. The general requirements of this project are located at:

http://ra.stsci.edu/apst/apt/apt-sv2-vtt/sv2-vtt-4-11-req.html

The primary focus of today's meeting was to go over an outline that Niall created. The outline explains some of the initial requirements of the changes to both software packages. The outline is available here for more information.

Some discussion was also done regarding the delivery of the software packages. Currently, Install Anywhere sets the environment variables (e.g. CLASSPATH and PATH) for the installed packages. If a user installs one software package and then later installs the other software package, the CLASSPATH would not be set-up properly to invoke the subsequently installed software package within the same JVM. For example:

Install Starview - sets CLASSPATH = /usr/local/lib/Starview within the "starview" script
One Month Later - Install VTT - sets CLASSPATH = /usr/local/lib/VTT within the "VTT"script.
The "starview" execution script will not know anything about the VTT and therefore will not be able to instantiate a TargetTunerModule class (since GOV.nasa.gsfc.sea.targettuner.TargetTunerModule or its associated package is not in the "starview" CLASSPATH).

Several solutions were suggested such as:

Detect the software packages at install time and modify the CLASSPATH accordingly if one or the other is found
Detect the software at execution time and modify the CLASSPATH accordingly if one or the other is found
Have different installation packages available that set the CLASSPATH differently

No solution was agreed upon at this time. The members of the team will think about alternatives and solicit input from their respective development groups regarding possible solutions.

Actions:

Fred will begin working on an API that will link together the two software packages.