Page Comparison

...

...

...

On the Primary Locator server:

If using Microsoft SQL Server, run complete the installer normally, entering the database user credentials when prompted then skip then proceed to the Secondary Server section.

If using PostgreSQL, follow these steps:

1. Perform a full PostgreSQL backup by executing a command similar to this:
   
   "%ProgramFiles%\Virtual Worksayfie\ViaWorksLocator \PostgreSQL\bin\pg_dump.exe" -i -h localhost -p 5432 -U postgres -F c -f "F:\Backups\viaworksLocator.bak" ViaWorks Locator 
   
   (where "F:\Backups\viaworksLocator.bak" is the path to the backup file)

   
   

2. Backup the custom configuration files (although they should not be overwritten by the upgrade):
   
   copy “%ProgramData%\Virtual Worksayfie\ViaWorksLocator\Database\pg_hba.conf” F:\Backups
   copy %ProgramData%\Virtual Worksayfie\ViaWorksLocator\Database\postgresql.conf F:\Backups

   
   

3. Proceed to upgrade. During the upgrade, the ViaWorksIndexBuilder Locator IndexBuilder service will be stopped, upgraded and re-started. If there many pending conversions the system may be CPU bound, slowing down the upgrade process. It’s safe to temporarily stop the Index Builder service until the system is completely upgraded.
   
   

4. Verify that the custom configuration in “%ProgramData%\ayfie\Locator\Database\pg_hba.conf” and %ProgramData%\ayfie\Locator\Database\postgresql.conf are still there. These configurations were originally set in Installing/configuring a Primary Server in a multi-server environment

On the Secondary

...

Locator server:

Note: If the secondary server is a SolrCloud node and part ot the ViaWorksCloud collection, make sure your schema_overrides.xml and solrconfig_overrides.xml in %ProgramData%\ayfie\Locator\Solr\configsets\ViaWorksCloud\conf are identical to these files on the primary node. Also make sure schema.xml and solrconfig.xml exists. There is a bug in Locator 2.11 SR2 where these files aren't created on install.

If using Microsoft SQL Server, run complete the installer normally, entering the database user credentials when prompted then continue with step 3.1. .

If using Postgres, follow these steps:

1. From an elevated command prompt, first make a backup copy and then edit the file %ProgramFiles%\Virtual Worksayfie\ViaWorksLocator\Config\DataAccess.config
   Essentially we will revert the changes back to default settings:
   
   

   1. Change the value of the “ViaDatabaseServer” key to 127.0.0.1. Save the current value as you need it for a later step.
      
      

   2. Remove this line before the </appSettings> line:
      
      <add key="LicensingServiceServer" value="<IPv4_addr>" />
      

      
      

2. Start the ViaWorksLocator.Database.ServiceThere are two methods to upgrading the secondary server: 1) .
   
   

3. In the installer, click "Run Again"
   

   Proceed with the ViaWorks upgrade and follow the steps below to manually configure it as a secondary server or 2) uninstall ViaWorks and reinstall using the Custom install option to automate some of these steps. If using method 2, continue with the steps in the original Install/Configuration guide starting at the Secondary Server steps.

   NOTE WHEN UPGRADING TO 2.8 SR3 OR OLDER: The upgrade can fail trying to create the ViaWorksDocumentation Solr collection. When the error occurs, leave the installer window open and follow these steps to correct the issue:
4. Stop the index service
5. In Program Files\VirtualWorks\ViaWorks\SOLR\bin\Solr.in.cmd replace line "REM set ZK_HOST=" with "set ZK_HOST=<<PrimaryIP>>:9983"
6. Start the index service
7. In ProgramData\VirtualWorks\ViaWorks\SOLR, delete the ViaWorksDocumentation folder
8. In a browser, enter this URL: http://localhost:8983/solr/admin/collections?action=DELETE&name=ViaWorksDocumentation
9. That will delete the ViaWorksDocumentation collection and allow the installer to complete successfully

Locator upgrade.



10. The upgrade will enable and start all of the services. Some of the services below might not exist, depending on which component was selected during install. Stop all ViaWorks Locator services again in this order if exist:
    1. All Fetch Services, in any order (e.g. ViaWorks ayfie/Locator FileServer Fetch Service, ViaWorks ayfie/Locator Exchange Fetch Service, etc.)
    2. ViaWorks Locator Index Service
    3. ViaWorks Locator IndexBuilder ServiceService 
    4. ViaWorks Locator Licensing Service
    5. ViaWorks Locator Database Service
       
       

11. Postgres only: From an elevated command prompt, first make a backup copy and then edit the file %ProgramFiles%\Virtual Worksayfie\ViaWorksLocator\Config\DataAccess.config
    

    1. Change the value of the “ViaDatabaseServer” key back to reflect the IPv4 address of the Primary ViaWorks Locator server as opposed to the default value of 127.0.0.1.
       

    2. Edit the ZookeeperHost value from "localhost:9983" to be the host name of the primary server, eg: "hostname:9983"

    3. Edit the LicensingServiceServer value from "localhost" to the host name of the primary server.
       
       
12. Edit the Rest Service web.config: "[Drive]:\Program Files\VirtualWorksayfie\ViaWorksLocator\RestService\web.config": change <add key="LicenseHostName" value="localhost" /> to <add key="LicenseHostName value="FQDN_of_primary_server" />
    
    
13. Disable
all non-fetch ViaWorks services except the ViaWorks Index Service by executing the command in an elevated PowerShell session:$fetchServices= Get-Service | Where {$_.DisplayName -like "*ViaWorks*" -and $_.DisplayName -notlike "*ViaWorks*Fetch*" -and $_.DisplayName -notlike "*Index Service*"}
$fetchServices| Set-Service -StartupType Disabled -Verbose


14. Start all of the ViaWorks fetch services by executing the command in an elevated PowerShell session:
    

    Get-Service| Where {$_.DisplayName -like "*ViaWorks*Fetch*" -or $_.DisplayName -like "*Index Service*"} | ForEach-Object {
    Start-Service -Name $_.Name -Verbose
    Start-Sleep -Seconds 10
    }  

...

1. the appropriate services by selecting the appropriate option for your setup below:
   1. If on a search server: Disable all ayfie/Locator services except Locator Index Service.
   2. If on a fetch server: Disable all ayfie/Locator services except ayfie/Locator Fetch Services.
   3. If on a search and fetch server: Disable all ayfie/Locator services except Locator Index Service and ayfie/Locator Fetch Services.
2. Start all of the ayfie/Locator services that were not set as disabled in previous step.