While this section assumes that you use the Tomcat server, you can use other application servers.
The JSP reference implementation depends on several paths related to the Tomcat Web server and Java SDK. This section assumes the following path names:
The location of the Tomcat installation |
|
The location of the Java SDK installation |
|
Note
The Java SDK installation must consist of the entire JDK, and not just the location of a copied or linked Java binary.
To set up the JSP reference implementation:
Copy the reference implementation from
$ENDECA_REFERENCE_DIR/endeca_jspref
to the Tomcat/webapps
directory (for example,/usr/local/tomcat-
).version
/webappsThe
$ENDECA_REFERENCE_DIR
variable is set as part of the Platform Services installation.(Optional.) Go to the
/usr/local/tomcat-
directory and open theversion
/confserver.xml
file in a text editor. You can modify the file as follows:Set the appropriate Tomcat environment variables.
For
csh
and similar shells, set:setenv JAVA_HOME /usr/local/j2sdk-
version
setenv CATALINA_BASE /usr/local/tomcat-version
export JAVA_HOME=/usr/local/j2sdk-
version
export CATALINA_BASE=/usr/local/tomcat-version
Generally these commands should be placed in a script run at the startup of the shell so that the variables are set for future use.
Copy the following file from the
PresentationAPI/<version>/java/lib
directory to/usr/local/tomcat-
:version
/webapps/endeca_jspref/WEB-INF/libCopy the following file from the
$ENDECA_ROOT/lib/java/
directory to/usr/local/tomcat-
:version
/webapps/endeca_jspref/WEB-INF/libCopy the following Report Generator file from the
$ENDECA_ROOT/lib/java
directory to/usr/local/tomcat-
:version
/webapps/endeca_jspref/WEB-INF/lib
The JSP reference implementation is set up and you can now test your Guided Search installation with it.