Reloading the database
The (re)loading of the search the search database is handled by a job which periodically checks for changes and triggers the reload if necessary. If the first search request (after a server start) arrives prior to the wirst execution of the reload job, this search will trigger the reload.
A database reload can also be triggered manually. In this case, FACT-Finder checks for changes made to the search database and, if necessary, performs an immediate reload.
Search and suggest databases can be reloaded separately or together.
REST Interface
FACT-Finder 7.3 adds a REST-API. The search application contains the technical documentation and can be accessed via this URL:
$stringEscapeUtils.escapeHtml($body)The interface offers not only the parameter documentation, but also the option to test a query and review the result. The documentation was created with Swagger, you can use Swagger Codegen to generate a client for it and use it for your code.
Methods are documented under refreshdatabases.
HTTP Interface
The interface acts differently depending on which parameters and values are passed on to it. For example, the basic URL is:
$stringEscapeUtils.escapeHtml($body)The parameter do defines which database should be reloaded. Possible values are refreshDatabases to reload the search database, refreshSuggestDatabases for the suggest database, refreshRecommenderDatabases to reload the recommendation database and refreshAllDatabases for all three. In addition, with refreshDatabasesOnNextRequest it is possible to reload both databases when the next query is received and with flushPersonalization you can empty the Personalization data (the latter requires admin rights).
In all variants, except for refreshDatabasesOnNextRequest and flushPersonalization, it is also possible, via the channel parameter, to arrange for the database to only be reloaded for a specific channel. If it should apply to several channels, the channel names must be entered, separated by a comma.
If the call was successful, the response will be a blank page. An error page is returned if an error has occurred.
Webservice/SOAP-Interface
End of Life
Please note: the SOAP interface will no longer be updated or upgraded. We recommend the REST-API for new customers. If you have been using the SOAP interface so far, you can go on using it. We do however recommend changing your integration interface to improve performance.
The WSDL of this interface can be reached at:
$stringEscapeUtils.escapeHtml($body)The available methods accept the user data as well as the desired channel names or a list of these.