...
There is an option to use TLS which can be selected during install. This provides secure communications between all servers.
Once this is enabled during installation, any clients that accesses the system must have TLS enabled on the login screen:
Conversely, if it wasn't enabled during install it must not be enabled during login.
...
The solution is to manually manipulate the replica set configuration after software installation. Please navigate here ReplicaSet Database Replica Set Administration to find out how to do this.
...
You will need to uninstall, and then reinstall Witness.
During the reinstallation of Witness there will be the option of Integration Plugins:
You can click the ➕ icon to view the dropdown list:
Or you can select them all or select / deselect individual plugins and then continue with the rest of the installation.
The plugin(s) should then be visible under Integration Configurations.
Repeat this process on each UI and Management Server for them to work on these platforms.
...
Hover your mouse over the Save button:
The system will display a tooltip with the reason why there is a problem with your configuration.
...
Check to see the position of the Map Transparency Slider. In the example below it is highlighted in pink and is switched off. It is located above the Picture Transparency Slider highlighted in turquoise.
If the transparency slider is on the left, move it to the right:
No Transparency Slider
...
Check the settings in the User Details:
Navigate to the Background Display settings and check to see if there is a background image option selected. If there is not then you can check to see if there is a background or static image which would normally be applied.
If the Background Map Type is set to None, then click Edit:
Then select either Google Map or Open Street Map from the Background Map Type drop-down list:
If you select Google Maps, there are additional options:
Make a selection and click Save.
Return to the Live screen and adjust the transparency slider if required to see the background image.
For more information about background images please see the following pages: Displaying a Map Adding a Background Image Adding a Background Image in ClearWay™.
...
Click Save to save the layout:
For more info please refer to https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/2291499117/Layout#Update-Current-Layout.
...
Navigate to Settings > Camera Settings.
Click on the Edit button and select the Camera System Enabled check box.
Click Save.
Camera not assigned to Controller
Check that the camera has been assigned to the Camera Controller:
VLC Media Player has not been installed
...
Witness has been designed to not show any radar data when this occurs:
Simply zoom back in, and the radar data will reappear:
Radar not Allocated to Track Engine
...
Navigate to the Topology page and ensure that the radar has been allocated to a Track Engine like this example:
If the radar has not been allocated, drag and drop the radar into the Track Engine:
Distribution Address Not Configured
...
Select the site name on the Configuration Tree, which is the master folder of the Entity Tree (e.g. the site, Navtech Demo, as illustrated below):
The site settings will then be displayed in the Configuration Panel:
Click Edit and select the IP address from the drop-down list (the list is auto populated by examining the IP addresses on the system running the UI application).
Add the IP Address and then click Save.
...
Check to see the Track Recording Mode:
If it has been set to None then there will be no track recording.
To enable this feature, click on Edit to open the drop-down menu:
Then select Incident or Save All and click Save:
Unable to Store Track Data
...
Check that the Track Recording setting has been enabled:
It must be set to either Incident or Save All.
In ClearWay™ you will need to enable Distribute Tracks on all of your radars:
To enable the Distribute Tracks feature for an individual radar, select the desired Radar to enable the Radar Mini Controller and click the Distribute Tracks toggle on, turning the button colour from black to blue:
...
Check to see if “localhost” or ”127.0.0.1” has been used by checking the Management Server address setting when logging in:
If it has then the solution to this is to uninstall then reinstall the system software with the database accessed via its outward facing IP address:
Log back in to Witness and amend the Server IP address:
There are additional tasks to ensure that your system runs smoothly:
...
Check Windows Services and ensure that the Management Server has started correctly:
If it has not started then Restart the service.
...
To resolve this please check that you have enabled SSO:
Next, check that the SSO Group Name has been configured:
If this hasn’t been configured then select Edit to add an SSO Group Name. This name must match the exact name as it appears in the AD, as illustrated below.
Finally, check that when logging into Witness, the Enable SSO option has been selected:
Incorrect IP Address
...
Check the server address entered in the UI login dialogue…
…matches the IP address of the Management Server:
Management Server Won’t Start
...
Check that the Service Account (normally “Witness”) is in the local Windows admin group:
Check that the passwords for the Windows user account and the password used on the service match. If necessary re-enter both.
...
Attempt to identify the invalid XML in the configuration file and correct it.
Alternatively, rename the current configuration file and allow the Management Server to create a default config file when it starts.
...
Remove the radar from its assigned Track Engine by either clicking the Unassign All Items button or by Drag+Dropping it out:
Then put radar back into the Track Engine:
If the problem still exists, reboot the Track Engine in Vertex.
...
To enable Plot Merging, select Merge Plots:
Do not set the Merge Range too aggressively. For example, several targets which are close to each other could be merged into a single track and be classified as a vehicle. Please refer to https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/2342486437/Channels+Tracker+Settings#Plot-Merging for more information.
...
This could be due to your Extra Sample Increment or Minimum Probability Required settings being too high. This may also have a knock-on effect for other parts of the system, for example, your rules. If you rely on classification in your rule configuration, then you need to consider how to handle tracks which may be unclassified for a number of sightings.
Enable the option in the rule configuration to handle unclassified tracks.
...
The IP address of the radar is found in Witness>Topology>Track Engine>Radar:
Next, go to Windows search and open a 'command prompt' (cmd).
In the command prompt type ping + radar IP address; e.g. ping 10.77.2.210
Press Enter. If the command prompt replies 4 times as in the picture below, then the network connection is good.
...
The IP address of the camera is found in Witness>Topology>Track Engine>Camera>Connection Details:
Next, go to Windows search and open a 'command prompt' (cmd).
In the command prompt type ping + camera IP address; e.g. ping 10.77.3.11
Press Enter. If the command prompt replies 4 times as in the picture below, then the network connection is good.
...