Normally SNF is installed so that the workspace and rulebase directories are the same. The getRulebase scripts provided assume that this is the case and that they will be living in the workspace directory along with the rulebase file. If your installation uses different paths then you will need to modify the scripts accordingly. Assuming everything is "normal" you should be able to get automated updates running following these steps:

1. Verify that wget and gzip are available. If you are installing on a *nix system then it is very likely they are already present and available. If you are installing SNF on a Win* system then the distribution file will include the wget and gzip utilities as a convenience. These are open source utilities. The distribution file will also tell you where the included copies came from.
   
2. Open your getRulebase script with your favorite text editor.
   
3. Edit the variable assignments at the top of the script:
   • Put in the correct path.
   • Put in the correct license id.
   • Put in the correct authentication string.
     
4. Save the file.
   
5. Create an UpdateReady.txt file. It doesn't matter what is in the file or even if the file is empty. It simply must exist so that the getRulebase script can find it.
   
6. Run the script. It should detect the UpdateReady.txt file and download the new rulebase from our servers. This is a good first step when setting up a new installation since the SNF engine will refuse to start if it doesn't find its rulebase file. A successful test-run of your getRulebase script not only verifies that your automated update script is working correctly but also gets you your rulebase file so you are ready run SNF.
   
7. Open your configuration file (snf_engine.xml or snfmdplugin.xml) with your favorite editor.
   • Locate the <update-script...> tag
     
     

     <update-script on-off='off' call='getRulebase' guard-time='180'/>

   • Modify the tag so that the update-script feature is turned on and the full path to your getRulebase script is configured. For example, if you are installing SNF on a Win* system and your SNF workspace and rulebase paths are C:\SNF\ then you should edit this line to look like this:
     
     

     <update-script on-off='on' call='C:\SNF\getRulebase.cmd' guard-time='180'/>

8. Save your configuration file. Now when the SNF engine is running it will automatically launch your update script within a minute or so of when a new rulebase file is ready. This is the best way to get new rulebase files without any time-lag or extra downloads.

Please email support@armresearch.com with any questions.