Last modified: Mon, 04/03/2017 - 17:29
Sometimes it is helpful to be able to run from the command the exact same Ferret script that was used by the the LAS Ferret backend service.
You can use this technique to see exactly where it failed and to test modifications by changing the values of some of the symbols before running the script.
- Add the LAS Ferret Backend Services script directory to you Ferret path. For example:
setenv FER_GO "$FER_GO $TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/scripts"
- Your $TOMCAT_HOME environment variable might not be defined in your shell show you'll have to use the full path to this directory instead.
- Go to the temporary diretory used by the service and find the script that defines the symbols for the product request you're trying to debug.
- This directory is typically $TOMCAT_HOME/webapps/las/WEB-INF/classes/resources/ferret/temp
- It will contain script with names like: ferret_operation_1175028078373.jnl.
- You can look for the symbol operation_service_action which is set to the name of the operation that was run.
- You can look for data_0_url which contains the data access url for the data set being use in this operation.
- Once you found the script you're looking for you can run it from the command line by starting Ferret in this directory and running the operation script (provided "." is in your FER_GO path).
- You need to start Ferret in "gif" mode.
[rhs@porter ~]$ cd /home/porter/rhs/tomcat/webapps/testbed/WEB-INF/classes/resources/ferret/temp
[rhs@porter temp]$ setenv FER_GO "$FER_GO /home/porter/rhs/tomcat/webapps/testbed/WEB-INF/classes/resources/ferret/scripts"
[rhs@porter temp]$ ferret -gif
Linux(g77) 2.6.9-22. - 03/22/07
yes? go ferret_operation_1175027947211.jnl