Reloading the LAS Configuration

This page explains how you can apply configuration changes to a running server. Reloading the configuration for the user interface only works for the V7+ user interface.

Configuring your server to allow reloads

When LAS starts it reads in its configuration from a collection of files in $LAS_HOME/conf/server. It is now possible to have LAS re-initialize itself after you make changes to these files without the need to stop and restart your Tomcat server. Follow these instructions to set up your server to use the administrator user interface. 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 at http://yourserver/las/ReInit.do. When you load this page and provide the proper credentials to the server you will see a page telling you if the re-initialization was successful.

If you see a message explaining that the server was not restarted because there were active product requests you can either wait until these requests finish or you can force the server to re-initialize by appending ?reinit=force to the ReInit.do URL.

Server Locking and the V7 User Interface

If you load the re-initialization page and the server initiates the process of reading the new configuration will temporarily "lock" itself and not accept new product requests. The server will return a simple page to the requesting client explaining that that server is temporarily down for maintenance. Once the new configuration has been read, the server will "unlock" itself and accept product requests again. However, a user's session will not be invalidated to if the changes to the configuration were extensive it is possible that they will receive an error for subsequent product requests (like in the case were the new configuration has completely removed a data set from the server).