Cycle for Autoloaded Data

This demonstration is applicable if you have configured and started autoload.
  1. In SAS Visual Analytics Administrator, set up the suggested display.
  2. If the Public LASR Analytic Server is running, right-click on it, and select Stop.
    CAUTION:
    Stopping the server unloads all tables.
    Stop the server only at a time when other users will not be disrupted.
  3. On the computer where SAS Visual Analytics is installed, copy the data set cars.sas7bdat from your equivalent of the following directory:
    C:\Program Files\SASHome\SASFoundation\9.4\core\sashelp
    to your equivalent of the following directory:
    C:\SAS\Config\Lev1\AppData\SASVisualAnalytics\VisualAnalyticsAdministrator\AutoLoad
  4. After 15 minutes, review the results.
    Note: This demonstration assumes a task interval of 15 minutes. If the interval is shorter or if there is a delay between your unload action and your get status action, autoload might load the table in the interim, leading to a different sequence of results.
    1. On the LASR Servers tab, select Public LASR Analytic Server, right-click, and select Get Status. Notice that the server is running. Autoload triggers the server to start if it is not already running.
    2. On the LASR Tables tab, click the refresh icon. Notice that the new table CARS is listed. The Description column indicates that the table was autoloaded.
    3. On the LASR Tables tab, get the statuses of all of the listed tables. Notice that tables that use reload-on-start are now loaded.
      Tip
      If autoload starts the server, it also triggers reload-on-start.
  5. Examine reload behavior.
    1. On the LASR Tables tab, right-click CARS, and select Unload.
    2. Right-click CARS again. Notice that you cannot reload the table manually.
    3. On the LASR Servers tab, stop, and then start the Public LASR Analytic Server.
    4. On the LASR Tables tab, right-click CARS, and select Get Status. Notice that the table did not reload after you restarted the server.
    5. After the scheduled task interval has elapsed, get the status of the CARS table again. Notice that the table is now loaded. The most recent run of autoload identified that autoload’s drop zone copy of CARS was not loaded, so it loaded that table again.