LAS Command Line Testing Utility
The configuration process completes, the LAS command line testing utility is ready to be used. Here are the command line options available with the script $LAS_HOME/bin/lasTest.sh.
usage: lasTest [-a] [-c] [-D] [-d <DATASET STRING>] [-e] [-f] [-h] -l <THE LAS URL> [-r] [-v <VIEW>] [-V]
-a,--all Test all products
-c,--connection Test the data set connections via the file or OPeNDAP URL.
-D,--DDS used with -c to print each DDS.
-d,--dataset <DATASET STRING> Test only data sets that contain this string
-e,--exit Exit on first error.
-f,--ftds Test F-TDS URLs.
-h,--help Print help message.
-l,--LAS <THE LAS URL> The base URL of the LAS to test (http://server.org/las)
-r,--responses Test product responses.
-v,--view <VIEW> Test only the specified view, one of x,y,z,t,xy,xz,xt,yz,yt,zt
-V,--verbose Verbose output.
Each option is explained in detail below.
usage: lasTest [-a] [-c] [-D] [-d <DATASET STRING>] [-e] [-f] [-h] -l <THE LAS URL> [-r] [-v <VIEW>] [-V]
-a,--all Test all products
The --all option will read the operations file and test every 1D and 2D plot appropriate for each data set. This is a very extensive test and might not be the best option for monitoring the health of you LAS.
-c,--connection Test the data set connections via the file or OPeNDAP URL.
-D,--DDS used with -c to print each DDS.
-d,--dataset <DATASET STRING> Test only data sets that contain this string
One of the issues we face running an LAS installation is making sure that the remote OPeNDAP data upon which our site depends is available. Often data that is interesting to our users is generoulsy made available via OPeNDAP by other institutions, but those servers can go down or get moved with any notification. So if you have configured remote OPeNDAP servers into your LAS, you can run the test utility which wil read your configuration and test the availability of the remote data.
These three options (-c, -D and -d <string>) control how that testing is done and how much information gets reported by the utility.
-e,--exit Exit on first error.
I you are running the test utility in a script, especially in a script being run by cron, you might like the utility to keep testing even though it encounters an error with one of the data sets or products. On the other hand you might like it to exit immediately when running on the command line.
-f,--ftds Test F-TDS URLs.
Part of the magic of LAS is that it takes any data configured into LAS and re-serves it via OPeNDAP through the F-TDS that is installed along side every LAS. This does two things, it makes the data avaiable to remote desktop clients and it allows the LAS machinery to define new variables using the server-side analysis capabilities of F-TDS. Unfortunately, there is no automated way to setup the F-TDS so once you think you've got it setup it's nice to be able to test it.
-h,--help Print help message.
Just print the options message an exit.
-l,--LAS <THE LAS URL> The base URL of the LAS to test (http://server.org/las)
This is a required parameter. You must the utility the URL of the LAS you want to test. While it is slightly inconvenient to have to specify this parameter, it has the advantage of enabling the utility to test remote LAS installations.
-r,--responses Test product responses.
-v,--view <VIEW> Test only the specified view, one of x,y,z,t,xy,xz,xt,yz,yt,zt
This option will attempt to create a product for each view and will examine the result to verify the product was created.
-V,--verbose Verbose output.
Writes out as much information as possible for the LAS test.