Note: This guide does not apply to customers running 2.7 with SolrCloud. Please contact Professional Services to upgrade to 2.8.
...
On the Primary ViaWorks server, if using Microsoft SQL Server, run the installer normally, entering the database user credentials when prompted then skip to the Secondary Server section. If using PostgreSQL, follow these steps:
Perform a full PostgreSQL backup by executing a command similar to this:
"%ProgramFiles%\Virtual Works\ViaWorks\PostgreSQL\bin\pg_dump.exe" -i -h localhost -p 5432 -U postgres -F c -f "F:\Backups\viaworks.bak" ViaWorks
(where "F:\Backups\viaworks.bak" is the path to the backup file)Backup the custom configuration files (although they should not be overwritten by the upgrade):
copy “%ProgramData%\Virtual Works\ViaWorks\Database\pg_hba.conf” F:\Backups
copy %ProgramData%\Virtual Works\ViaWorks\Database\postgresql.conf F:\BackupsProceed to upgrade. During the upgrade, the ViaWorksIndexBuilder 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.
Add a new rule to the Windows firewall allowing all traffic inbound on TCP port 8983 for Solr. Run the following from an elevated command prompt. This command will work on Windows Server 2008 R2 or later: Note: this rule was added during the initial configuration, however upgrading to 2.8 could remove it.
netsh advfirewall firewall add rule name="ViaWorks Solr (TPC-In)" protocol=TCP localport=8983 action=allow dir=IN
From an elevated command prompt, edit the file %ProgramData%\Virtual Works\ViaWorks\Database\postgresql.conf
(Note: If you customized where ProgramData was set during installation, you must enter that full path instead of using the system variable "%ProgramData%")
Search for “#listen_addresses = 'localhost'” and add the following line before it:listen_addresses='*'
- Restart the the ViaWorks Database Service
...