This tool enables you to transfer existing archive full-text data from the JobRouter database to Elasticsearch. This way, the new indexing of the documents gets superfluous and the changeover of the full-text engine is accelerated.
The tool can be found in the download section of the Support portal.
Requirements
Elasticsearch was already configured. The documents in the archive are indexed in the Full text engine database already.
Preparation and configuration
Unzip the Zip file into an empty directory. Before doing so, please press Allow in the file settings, if needed.
Copy the instance.key file from the config subfolder of the JobRouter web application into the program directory.
Then you have to configure the program. To do so, please open the Configuration.json file and adapt it as follows: Copy all values up to archiveTable from the config.php file. You can find the value for the archiveTable setting in the form of a Table name in the Archive configuration. Below you can find an example for the Configuration.json file.
{
"host": "jobrouter_dbhost",
"port": "",
"schema": "jobrouter_test",
"type": 0,
"username": "admin",
"password": ":V/7yf2cL7U/z7W/ExampleZ0eNg==",
"archiveTable": "TESTARCHIV"
}
Execution
Please start the FulltextImporterDbToElasticsearch.exe application. After the start, the program creates a new index in Elasticsearch and transfers the archive full-text data from the JobRouter database. Depending on the size of the archive, this can take just some minutes or even several hours. The revision ID of the most recently transferred document is saved in a file called last_processed_revision_id. If the transfer is interrupted for any reason, it will be automatically continued as soon as the program is started again.
