Instant search - just wait a week

Jake Brown

August 06, 2015 23:09

Just ran across this little gem in the admin guide.  

If you delete a map service from the index, and then you want to start using Instant Search again for that map

service, you must re-scan the service to add it back to the index. It may be more than a week before your features

 

are available again in Instant Search.

 

 

How can this be true?  There is a workaround?  Have some unhappy users in my production environment and I'm not sure I have the courage to tell them to "wait a week or more"  

-Jake

0

• 

  Permanently deleted user

  August 14, 2015 04:26

  I agree. It's extremely frustrating! I'm in the same boat. Waiting a week when the initial index is generated in a few hours is riduculous to me. Perhaps it'll be addressed in an upcoming release.

  0
• 

  Stefan Schweigert

  August 15, 2015 00:00

  Hello Jake and Rebecca,

  This is a configurable setting actually. You will need to stop CORE, change the setting, then start CORE back up.

  Edit the role.config for the Instant Search Scanner Manager here: (C:\Program Files\Latitude Geographics\Geocortex Core\NSRoot\Geocortex\Core\Roles\InstantSearch\ScannerManager\2.3.0).

  Uncomment the following line and change the schedule to fit your needs: <!--<StartupSetting Key="IndexSchedule" Value="{'Interval':'Monthly', 'DayOfMonth':28 'Hour':12, 'Minute':0}" />-->

  Thanks,

   

  Stefan

  0
• 

  Permanently deleted user

  August 19, 2015 00:53

  Thanks for that, Stefan. Tech support wasn't able to tell me this. I was told I had no other option than to wait a week. Perhaps sharing it with the tech support team would be useful to alleviate users' frustration.

  A few questions: I'm assuming stopping CORE affects all sites and should be done during non-peak usage times? Does changing this setting affect all sites? Which version of Essentials is this relevant for?

  0
• 

  Stefan Schweigert

  August 19, 2015 01:25

  I would advise to stopping Core outside of peak hours as you are correct; the downtime will affect all sites.   That line in the file only applies to Core 2.1.  You can manually go into Manager and force an immediate re-index as of Core 2.2.   In order for the settings in the role.config file to take effect, you will also need to manually restart indexing for any of the services that it should be applied to.  After that index completes, the scheduling settings will be applied.

  0

Please sign in to leave a comment.