This document describes how to install the Data Set View software contained in the ds-view package. The following topics can be found in this section:
This section details the system requirements for installing and operating the Product Query software.
The Data Set View software was developed using Java and will run on any platform with a supported Java Runtime Environment (JRE). The software was specifically developed under Java version 1.6 and has only been tested with this version. The following commands test the local Java installation in a UNIX-based environment:
% which java
/usr/bin/java
% java -version
java version "1.6.0_26"
Java(TM) SE Runtime Environment (build 1.6.0_26-b03-384-10M3425)
Java HotSpot(TM) 64-Bit Server VM (build 20.1-b02-384, mixed mode)
The first command above checks whether the java executable is in the environment's path and the second command reports the version. If Java is not installed or the version is not at least 1.6, Java will need to be downloaded and installed in the current environment. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, the Java software can be downloaded from the Oracle Java Download page. The software package of choice is the Java Standard Edition (SE) 6, either the JDK or the JRE package. The JDK package is not necessary to run the software but could be useful if development and compilation of Java software will also occur in the current environment.
The Data Set View software requires a Java application server for hosting the web application. The suggested application server for this release is Apache Tomcat with a minimal version of 6.0.20 through version 7.0.X. Consult the local system administrator for installation of this software. For the do-it-yourself crowd, see the Tomcat Deployment document for installation and configuration details. If viewing this document from the ds-view package, view the Tomcat Deployment document from the Engineering Node site.
Download the ds-view package from the PDS FTP site. The binary distribution is available in identical zip or tar/gzip packages. The installation directory may vary from environment to environment but in UNIX-based environments it is typical to install software packages in the /usr/local directory and in Windows-based environments it is typical to install software packages in the C:\Program Files directory. Unpack the selected binary distribution file with one of the following commands:
% unzip ds-view-2.4.0-bin.zip
or
% tar -xzvf ds-view-2.4.0-bin.tar.gz
Note: Depending on the platform, the native version of tar may produce an error when attempting to unpack the distribution file because many of the file paths are greater than 100 characters. If available, the GNU version of tar will resolve this problem. If that is not available or cannot be installed, the zipped package will work just fine in a UNIX environment.
The commands above result in the creation of the ds-view-2.4.0 directory with the following directory structure:
A README file directing the user to the available documentation for the project.
The copyright notice from the California Institute of Technology detailing the restrictions regarding the use and distribution of this software. Although the license is strictly worded, the software has been classified as Technology and Software Publicly Available (TSPA) and is available for anyone to download and use.
This is the Web ARchive (WAR) file containing the Data Set View software including all dependent JAR files.
This directory contains a local web site with the Data Set View documentation and other configuration management related information. Just point the desired web browser to the index.html file in this directory.
The Data Set View web application is packaged as a WAR file and is intended for installation under a standard Java Application Server. There are two options for deploying the WAR file:
<?xml version="1.0" encoding="utf-8" ?>
<Context crossContext="true">
</Context>
Assuming Data Set View WAR and accompanying directories are located at /usr/local/ds-view (if not, substitute the directory location as needed), we need to set the application to allow for cross-context so it can use the various server-side includes. We can do this by creating $TOMCAT_HOME/conf/Catalina/localhost/ds-view.xml containing the following text:
<?xml version="1.0" encoding="utf-8" ?>
<Context docBase="/usr/local/ds-view/ds-view.war" crossContext="true">
</Context>
The Data Set View web application also depends on several other directories from the PDS Website that include images and server-side include files that are in the extras directory in Search UI package (i.e. /usr/local/search-ui/extras). This contains the following directories:
The current Data Set View is intended for deployment on both the PDS Engineering website, as well as external users. The remaining installation procedures can be ignored for PDS EN deployment because these directories are already included in the PDS EN website.
If the directories above are not in the $TOMCAT_HOME/webapps directory already, create the following Tomcat context files in $TOMCAT_HOME/conf/Catalina/localhost to include these directories:
<?xml version="1.0" encoding="utf-8" ?>
<Context docBase="/usr/local/search-ui/extras/images" ></Context>
<?xml version="1.0" encoding="utf-8" ?>
<Context docBase="/usr/local/search-ui/extras/include" ></Context>
An alternative solution is to move all of the directories into the $TOMCAT_HOME/webapps directory: (assumes Search UI software and directories are at /usr/local/search-ui)
Unix Environment
$ mv extras/include $TOMCAT_HOME/webapps
$ mv extras/images $TOMCAT_HOME/webapps
Restart Tomcat to ensure the changes take effect.
The Data Set View web application provides the following parameters for configuration:
| Parameter | Description |
|---|---|
| pdshome.url | The URL for the PDS web site. |
| registry.url | The base URL for the PDS3 Registry Service. |
| proxy.registry.url | The base URL for the ADS Registry Service. |
| search.url | The base URL for the Search Service. |
To modify the configuration, edit the web.xml file located in the $TOMCAT_HOME/webapps/ds-view/WEB-INF directory. The following block contains the parameters:
<!-- PDS Web Site -->
<context-param>
<param-name>pdshome.url</param-name>
<param-value>http://pds.jpl.nasa.gov/</param-value>
</context-param>
<!-- Registry Service base URL -->
<context-param>
<param-name>registry.url</param-name>
<param-value>http://localhost:8080/registry-pds3</param-value>
</context-param>
<context-param>
<param-name>proxy.registry.url</param-name>
<param-value>http://localhost:8080/registry-ads</param-value>
</context-param>
<!-- Search Service base URL -->
<context-param>
<param-name>search.url</param-name>
<param-value>http://localhost:8080/search-service</param-value>
</context-param>
The above values should be modified for the target environment.