Modifying Default Search Service Settings

Search Service Settings are meant for the administrator of the Web Search server and are intended to give him global control over all virtual search servers, including the ability to completely disable searching by turning it off.

They also allow the administrator to control the overall performance of the Web Search Server.


General Services Settings

General Services Settings affect error log and server settings for all virtual search servers.

To modify general services settings, do the following:

  1. From the Web Search Manager home page, click General under Services Settings.

  2. Select where you want log results displayed by choosing one of the following options from the Log Errors To drop-down list:

    • File: When this option is selected, you can click View next to the Log Errors To drop-down list and the log results are displayed in your browser.
    • Console: You can also view log results at the NetWare system console by selecting Console, pressing Ctrl+Esc on your server's keyboard, and then pressing the number corresponding to the Tomcat servlet engine.
    • Both: Displays results in both your browser and at the system console.

    HINT:  You can access the log file directly by going to volume:\searchroot\errors.log.

  3. To start a new log file each time you restart the Web Search server, click Yes next to New Log When Services Load.

    HINT:  You can also delete the log file at the path specified above. The log file will be recreated on the first instance of a new error, statistics, etc.

  4. To limit the size of the log file, enter a file size (in bytes) in the Maximum Log Size field.

  5. To limit the number of indexing jobs that can run at the same time, specify a number in the Maximum Number of Active Index Jobs field.

  6. In the Default Location of Virtual Search Servers field, specify the path to where you want all virtual search server files to be stored, including index and configuration files.

    HINT:  Changing this setting won't move existing sites to the new default location. But all new virtual search servers will be placed here.

  7. To direct Web Search to reload configuration files modified manually, outside of Web Search Manager, click Yes next to the Detect Manual Search Server Changes field.

    If you make changes outside of Web Search Manager, such as modifying a configuration or properties file, Web Search will re-read those files as often as you indicate in the Seconds Between Checking for Changes field.

  8. In the Seconds Between Checking for Changes field, specify how often Web Search should check for manual changes (changes made outside of Web Search Manager) to the configuration files.

  9. To direct Web Search to reload Web Search templates that have been modified, click Yes next to the Detect Template Changes field.

    After making a change to a template from within your HTML editing tool and saving it on your server, Web Search will re-read the template as often as you specify in the Seconds Between Template Updates field. That way you can test your changes almost immediately.

  10. In the Seconds Between Checking for Template Changes field, specify how often Web Search should reload search, print, results, and error templates.

  11. Click Apply Settings.


Search Services Settings

Search Services Settings let you turn search capabilities on or off and manage debugging and statistics settings.

To modify search services settings, do the following:

  1. From the Web Search Manager home page, click Search under Services Settings.

  2. To enable search services for all virtual search servers on your Web Search server, click Yes next to Enable Search Service.

  3. Under Debug Settings, click Yes next to Enable Search Debugging if you want to keep a log of all searches and query results going to all virtual search servers.

    IMPORTANT:  We recommend that you use this features only while setting up or troubleshooting your search services because depending on search activity, the log file can grow in size very quickly. While you can limit it's size (see Step 6) it can become ineffective when the limit is reached and no more activities are added to the log file.

  4. Select where you want log results displayed by choosing one of the following options from the Log Debug Messages To drop-down list:

    • File: When this option is selected, you can click View next to the Log Debug Messages To drop-down list and the log results are displayed in your browser.
    • Console: You can also view log results at the NetWare system console by selecting Console, pressing Ctrl+Esc on your server's keyboard, and then pressing the number corresponding to the Tomcat servlet engine.
    • Both: Displays results in both your browser and at the system console.

  5. To start a new log file each time you restart the Web Search server, click Yes next to New Log When Services Load.

  6. To limit the size of the log file, enter a file size (in bytes) in the Maximum Log Size field.

  7. Under Statistics Settings, click Yes next to Enable Search Statistics Logging if you want an updated log file containing statistics about searches performed against all virtual search servers on your Web Search server.

  8. In the Seconds Between Statistics Updates field, enter a number (in seconds) that should elapse between updates of the statistics log file.

  9. For the next three fields, follow Step 4, Step 5, and Step 6 above.

  10. In the Log Error If Search Time Exceeds field, enter a number (in seconds) before Web Search should record the current search as exceeding the specified time limit on the statistics display. This appears as the Limit portion of the statistics display.

  11. Click Apply Settings.


Print Services Settings

To modify print services settings, do the following:

  1. From the Web Search Manager home page, click Print under Services Settings.

  2. To enable print services for all virtual search servers on your Web Search server, click Yes next to Enable Print Service.

  3. Under Debug Settings, click Yes next to Enable Print Debugging if you want print debugging turned on.

    IMPORTANT:  We recommend that you use this features only while setting up or troubleshooting your search services because depending on search activity, the log file can grow in size very quickly. While you can limit it's size (see Step 6) it can become ineffective when the limit is reached and no more activities are added to the log file.

  4. Select where you want log results displayed by choosing one of the following options from the Log Debug Messages To drop-down list:

    • File: When this option is selected, you can click View next to the Log Debug Messages To drop-down list and the log results are displayed in your browser.
    • Console: You can also view log results at the NetWare system console by selecting Console, pressing Ctrl+Esc on your server's keyboard, and then pressing the number corresponding to the Tomcat servlet engine.
    • Both: Displays results in both your browser and at the system console.

  5. To start a new log file each time you restart the Web Search server, click Yes next to New Log When Services Load.

  6. To limit the size of the log file, enter a file size (in bytes) in the Maximum Log Size field.

  7. Under Statistics Settings, click Yes next to Enable Print Statistics Logging if you want to an updated log file containing statistics about print requests performed on your Web Search server.

  8. In the Seconds between Statistics Updates field, enter a number (in seconds) that should elapse between updates of the statistics log file.

  9. For the next three fields, follow Step 4, Step 5, and Step 6 above.

  10. In the Log Error If Print Time Exceeds field, enter a number (in seconds) before Web Search should record the current print job as exceeding the specified time limit on the statistics display. This appears as the Limit portion of the statistics display.

  11. Click Apply Settings.



Previous | Next