This setup is no longer required with new Resultviewers!

Preparation

• Prepare two computers
  - a "Production" with go2MONITOR (LT1) and
  - a "Client" with the standalone ResultViewer (LT0)

Data Storage Location

On the "Production" computer with go2MONITOR (LT1)

• Usually I set up a special directory because we need to share this directory and it needs some space (maybe a disk array)
• Modify SystemConfiguration.xml
  (c:\Program Files (x86)\go2signals\go2MONITOR\sysconfig\)
  If you like to have your data in d:\go2mresults

Replace:
<VARIABLE>ifserverpath</VARIABLE>
<VALUE>$_USER_PATH_NO_VERSION_$results</VALUE>
with:
<VARIABLE>ifserverpath</VARIABLE>
<VALUE>d:\go2mresults </VALUE>

• Start go2MONITOR and do some decoding.
• Check if files are written to the new directory
• Check if the go2MONITOR ResultViewer is still working

Standalone ResultViewer Setup

On the "Production" computer with go2MONITOR (LT1)

• Share the directory with the results (d:\go2mresults) and define the user(s) to have access to this directory.
• Disable the firewall (only for the tests/setup) or open port 39115 for PostgreSQL
• Specify the TCP/IP address(es) on which the server is listening
  In c:\Users\xxxxx\go2signals\go2MONITOR\database\postgresql.conf

Add the line:
#listen_addresses = 'localhost' # what IP address(es) to listen on;
listen_addresses = '*' # listen on all IP address(es);

If setup is complete assign correct values to avoid any security problems!

• Setup user user authentication
  In c:\Users\xxxxx\go2signals\go2MONITOR\database\pg_hba.conf

Add the line:
# host all all 127.0.0.1/32 trust
host   all all 0.0.0.0/0    trust

If setup is finished assign correct values to avoid any security problems!

On the "Client" computer with Remote ResultViewer (LT0)

• Check on the client computer if you have access to the results (\\LT1\go2mresults)
• On the client computer setup a database management tool (like DBeaver)
  - Host: computer name or IP address
  - Port: 39115
  - Database: cmas
  - Username: cmas
  - Password: ******

• 

• Check on the client computer if you have access to the database

• 
  If you can not connect, then check if go2MONITOR on LT1 is running (as it starts PostgreSQL) and if the firewall(s), routers vpn etc. allows traffic to port 39115. Instead of the computer name, you can also try with the IP address.

• Now setup the Remote ResultViewer on the client computer (LT0)
  In c:\Users\xxxxx\go2signals\go2MONITOR xx.x\resultviewerapp.conf

Add

<?xml version="1.0" encoding="utf-8"?>
<configuration>

<appSettings>

<add key="LogLevel" value="2" />
<add key="LogToFile" value="1" />
<add key="LogToConsole" value="1" />
<add key="LogPerRun" value="1" />
<add key="LogUseXML" value="0" />
<add key="LogDirectory" value="log" />
<add key="LogMaxFileNumber" value="5" />
<add key="LogMilliSeconds" value="1" />

<!--add key="CMAS_IP" value="127.0.0.1" /-->
<add key="ResultRootPath" value="\\LT1\go2Mresults\" />
<add key="ResultDatabaseName" value="QPSQL|cmas:procitec@192.168.222.75:39115/cmas" />

</appSettings>

</configuration>

192.168.222.75 is the IP-address of LT1

• Start the Remote ResultViewer on LT0.
  Now, you should be able to browse in your data

Additional Remarks

• I also recommend to install the pgAdmin tool. It allows you to monitor the SQL server.
• Additional VPN setup may be required if the two computers are connected via the Internet.
  With such a setup, the database queries are usually very fast, but downloading files (IQ data from narrowband/wideband recordings or audio) takes some time depending on the actual network speed..
• Instead of sharing the data directory, it is also possible to set it up with a synchronization tool. Then all files are downloaded as soon as some network bandwidth is available.