Locator supports the deployment of multiple Locator servers, configured to work together to index documents from the various data sources within the customer environment. In a multi-server scenario, the primary Locator server will be used to establish connections, "crawl" and discover documents to be indexed from each connection, and perform the conversion and indexing, while the secondary servers are used strictly to assist in the conversion process. This document describes the process of deploying a secondary Locator server to enable the additional server to fetch and convert documents.
...
- In the Locator Installer choose Custom Install
- On the Server Address page, replace localhost with the primary server hostname for the Licensing service address field
- For the Zookeeper address, replace localhost with the primary server IPV4 address and keep the port :9983
- If using PostgreSQL, on the Database Information page, leave the drop down as PostgreSQL and the database name as Locator.
- If using Microsoft SQL, on the Database Information page, change the drop down as Microsoft SQL Server and fill in the database server hostname, database name and database user account credentials. Click Verify Connection
- Choose the following components
- Finish the installer and wait for the installation to complete.
...
Verify Configuration and Assign Fetch Server
- On the Primary Locator server:
- (Optional for PostgreSQL installations) From an elevated command prompt, run %ProgramFiles%\ayfie\Locator\PostgreSQL\bin\pgAdmin3.exe
- Select the Locator database
Select the SQL button and paste the following text into the window:
Code Block language sql SELECT * FROM config.via_works_server;
- Run the query
- Verify there is a second row showing the secondary Locator server (see the ADDITIONAL_COMPUTERNAME and ADDITIONAL_COMPUTER_FQHN columns).
- Close pgAdmin
- Start the Locator Management Console and on the "Scheduling" page under Connections, assign the secondary server to each of the connections in each of the connectors from which the secondary server will be used to fetch documents.
- The secondary server should have the “Perform Discovery” option disabled and the “Perform Fetch” option enabled.
- Remember to click "Save" after assigning the server to each connection.
- Note that the secondary server’s schedule must be set and is independent of the primary server’s schedule.
See also
Child pages (Children Display) page Installing the ayfie Locator Server