How to setup an offline or unconnected WATS Client or Test Station

In rare cases the WATS Client or Test Station is located in an isolated or disconnected environment that is unable to access the WATS Server. We call these Unconnected WATS Clients or Test Stations.

There are still ways to produce files that can be submitted or further processed by another online WATS Client or the Rest API. 

There are 3 main approaches to get data from an Unconnected station:

1. Without installing the WATS Client
   Move (copy or manually) the result files (UUT/UUR) to another computer with a connected WATS Client with a proper converter installed (e.g. ATML, WSXF, WSJF, etc.)
   Optionally, POST WSJF or WSXF from any computer using the rest API 
    
2. Install the WATS Client, but not connect once to the WATS server, using TestStand add-on
   1. Configure the WATS Client without connecting to the WATS server as described below on the Unconnected station. 
   2. Configure TestStand to use the "XML Document" Report Format
   3. Optionally, disable the "WATS Logging" result processing option.
   4. Install the TestStand XML converter on the connected WATS Client to upload the UUT reports (and maintain all the TestStand properties). 
       
3. Install the WATS Client and connect once to the WATS server
   This method will use the Submit-ready WRML (*.Queued) files located in the Reports folder in the WATS data folder - located at C:\ProgramData\Virinco\WATS
   These files have to be copied from the Reports folder on the unconnected WATS client to the Reports folder on a connected WATS Client.
   
   The advantage with this approach is to preserve Client/Level functionality in System Manager and User Settings, including access restrictions.
   
   NOTE: Following option 3, Unconnected WATS Clients have to be connected to WATS once before they can be utilized.
   
   WATS Client API
   You can use the WATS Client API directly on an Unconnected WATS Client to produce submit-ready files. Using SubmitOnline or Submit with SubmitMethod.Online will throw error on the unconnected WATS Client.
   
   WATS Client Converter
   Built-in and custom converters can run on an unconnected WATS Client. They will produce submit-ready files in the reports folder. 
   Using SubmitOnline or Submit with SubmitMethod.Online will cause the converter to fail on the unconnected WATS Client.
   
   TestStand add-on or LabVIEW toolkit
   Use the TestStand or LabVIEW add-on and produce submit-ready files in the reports folder

Configure a WATS Client without connecting to the server

NOTE: Each time a change is made to processes in WATS you need to copy Processes.json from the WATS data folder of an online WATS Client to the WATS data folder of the unconnected WATS Client.

(6.x or newer)

To configure an unconnected WATS Client, you can bypass the Setup (connect) page:

1. Open WATS Client Configuration and enter a URL in Account/Server and a username and password.
   • The URL must be to something the machine cannot reach, ex. http://offline-client. 
2. You should get the warning "Specified server could not be reached. Configure anyway?". Click Yes.
3. Install TestStand or LabView add-on normally.
4. Install and configure converters normally.

(5.1)

To configure an unconnected WATS Client, you can bypass the Setup (connect) page:

1. Open WATS Client Configuration and enter a URL in Account/Server and a username and password.
   • The URL must be to something the machine cannot reach, ex. http://offline-client. 
2. You should get the warning "Specified server could not be reached. Configure anyway?". Click Yes.
3. Install TestStand or LabView add-on normally.
4. Edit settings.json in the WATS data folder and change "ClientState":"NotConfigured" to "ClientState":"Active"