Search Maker Pro – Automatically Updating the Search Engine
Knowledge Base Article: kb02
Introduction
Whilst maintaining the pages that you are using Search Maker Pro to index, you may find that you need to recreate the search.html file when pages are updated, added or removed.
This can be done by running Search Maker Pro again to recreate the search.html file.
This is a one step process if you save a configuration file after indexing.
However the entire search recreation process can be automated for solutions that require a reindex at frequent or specified intervals.
For instance you may be using the software to create a search for the contact information on your intranet.
The search would need to be refreshed on a daily basis to reflect ever changing contact information stored within the web pages.
Command Line Options
You can achieve this automation by using Command Line Options.
These are parameters that are passed to the application when it starts.
will open the saved configuration file c:mywebdefault.rhm, index the website, reduce the amount indexed to 5000 characters per page, and save the search engine to z:intranetpublishcontactsearch.html
Command Line Reference
/o <rhm configuration file>
Open a previously saved Search Maker Pro configuration file.
/s <full filename>
Save the generated search.html file. The full filename must be provided, such as C:My DocumentsWebrootsearch.html. If this switch is not used then the file is saved to C:search.html
/m1
Minimize the size of the generated file using option 1, "Remove all body text".
/m2 <number of chars>
Minimize the size of the generated file using option 2, "Specify maximum number of characters to index for each page".
/m3 <max file size (KB)>
Minimize the size of the generated file using option 3, "Specify maximum size of search.html file".
Automating the Script
The final step needed in our example is to automate running the command.
This can be done using your operating systems "Scheduled Tasks" option.
Note that it is required that the scheduled task is run under the user account that installed and registered the application on the system.