Skip to main content
Skip table of contents

Relocating the Shinydocs Search Engine Data Folder

For disk management purposes sometimes an implementation might require the relocation of the Search Engine’s data to an alternate drive, i.e. from C: drive to E: drive. This article outlines the process.

To relocate the OpenSearch data folder, use the following steps:

  1. Create a new folder in the desired location, i.e. E:\SearchIndexes

  2. Ensure the service account for the Shinydocs Search Engine has full access to this folder.

  3. Confirm that all crawling has been stopped within Shinydocs Pro by inspecting the available data sources:

    image-20240229-154927.png

    Click on the “hamburger” menu in the top-right corner.

  4. Ensure that all actions are complete and the Status bar is all green.

    image-20240229-155116.png


  5. Open the Services App (services.mcs) from the Windows Start menu.

  6. Locate the Shinydocs Search Engine, right-click on the service:

    image-20240229-155208.png


  7. Stop the service.

  8. Using Windows Explorer, locate the folder C:\Program Files\Shinydocs Professional\SearchEngine

  9. Open the config folder and locate the opensearch.yaml file.

  10. Create a backup of this file (i.e. opensearch.yaml.bak) then open the original in Notepad++ or Notepad.

  11. Locate the remarked-out entry for #path.data:

  12. Add a new entry below the original example for your new location:

    image-20240229-155356.png

  13. Save this file.

  14. Return the folder C:\Program Files\Shinydocs Professional\SearchEngine and locate the data folder.

  15. Cut this folder, then move to the new location (E:\SearchIndexes) and paste the data folder into that location.

  16. Return to the Services App and start the Shinydocs Search Engine.

  17. Wait for 2 to 3 minutes then access http://localhost:9200 from the browser.

    image-20240229-155458.png

  18. You may then connect to the Shinydocs Professional Overview (https://localhost:5001/overview)

    image-20240229-155556.png



JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.