Configuring your server to allow access to the Admin Page
When LAS starts it reads in its configuration from a collection offiles in $LAS_HOME/conf/server. It is now possible to manage the LAS cache and have LASre-initialize itself after you make changes to the configuration files files without the need to stop and restart your Tomcat server. When LAS is installed,the Web server configuration includes entries which give an administrator access to the admin page, the cache manager and the re-initialization page using the same certificate, user name and password that is used for the THREDDS DataServer. These pages will be available only if you have followed the instructions for setting up access to TDS via SSL using a certificate.
Once you have finished the configuration and tested it by loading your TDS "debug" page you can use the same login and password to access the LAS re-initialization page. The page is found athttp://yourserver/las/admindo. When you load this page and provide the proper credentials to the server you will see a page with links to the cache manager and the re-initialization page. You can also access them directly. To re-initialize the server use: http://yourserver/las/ReInit.od and to manage the cache use: http://yourserver/las/CacheManager.do.
Re-initializing Development Servers
If you have a private server (such as one deployed behind a firewall) which is being used to test configurations or develop new products you can configure the server to allow open access to the admin page. Comment out or remove the security configuration section of the $LAS_HOME/WebContent/WEB-INF/web.xml file and redeploy the server. This will allow you to test your new configurations simply by loading the ReInit.do page without needing to create a certificate or configure a role, user and password. You can also manage the cache from the CacheManager.do page without creating a certificate or configuring a role, user and password. When you access the admin, re-init or cache manager pages no login challenge will be issued. Obviously, this is not recommended for production servers.