...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Introduction
ICD-001 is a network communication protocol based on XML. The protocol is used over standard TCP/IP client-server connections.
...
This section covers the configuration of the plugin within Witness. The configuration controls the network settings as well as enabling how and what data is transmitted through the plugin.
Contents
...
Table of Contents | ||||||
---|---|---|---|---|---|---|
|
...
Overview
When Witness generates events, such as alarms, or processes targets, it passes all this information to the Integration Manager. The Integration Manager is then able to use loaded plugins such as ICD-001 to convert this information into a suitable data format to send to external systems. In this case the plugin converts the data to XML message which are transmitted over a TCP/IP connection.
...
The data is transmitted as the events occur, leading to real time reporting.
Installing the ICD-001 Plugin
Witness supports integration with many different types of external systems through the use of plugins. These are stand-alone software libraries which are dynamically loaded by the Integration Manager and contain code which knows how to convert the Witness data into the required format for the external system. Navtech Radar can easily develop bespoke plugins to interface with a specific type of equipment or application, however ICD-001 has been developed to provide a comprehensive communication protocol which is based on open standards in order to make it as easy as possible to integrate with a large number of different systems.
Tip |
---|
The plugin can be selected during setup and will automatically be installed in the correct location. |
When installing Witness, in the Choose Components page of the Witness Setup wizard, open Integration Plugin options and select ICD001:
...
Configuring the ICD-001 Plugin
When the plugin is installed and licensed, a plugin configuration with default settings is automatically generated.The settings can be viewed and edited by enabling the Config Function, then selecting the plugin in Integration Configurations, within the Configuration Tree. Configuration settings will then be available in the Configuration Panel.
...
Info |
---|
Once you have made changes to the plugin configuration and committed the changes by saving, the plugin will automatically restart itself based on the new configuration. Note that any connections to 3rd party systems will be dropped during this restart. |
...
Authentication Type: the authentication method to use for the TLS connection:
a. None - no authentication is used however the link is still encrypted using TLS with a self-signed certificate created by Witness.
b. Fingerprint - this option can be used with self-signed certificates. This will look for client certificates with matching thumbprints on the server’s Windows certificate store. You can store more than one thumbprint in order to support a different certificate per client.
c. Certificate - this option uses a certificate with a fully verifiable certificate chain and Certificate Authority (CA). Typically this will need the full certificate chain including the CA root certificate available in the Windows certificate store or verifiable through a network connection.
Fingerprint Authentication
This is a simple way to authenticate clients when using self-signed certificates that can’t be verified using a Certificate Authority (CA).
...
Certificate Thumbprint: the thumbprint of the server certificate to use for the TLS connection.
Current User Store: indicates if the certificate should be fetched from the current user store, if not it will be fetched from the local computer store.
Client Thumbprints: this is the list of client thumbprints. These are used to authenticate client connections. Each of these certificates must be installed in the certificate store on the server. Each entry can added with name for easy identification of the certificate.
Certificate Authentication
This is the standard way of authenticating a certificate using a Certificate Authority (CA) typically through a CA root certificate.
...
Certificate Thumbprint: the thumbprint of the server certificate to use for the TLS connection.
Current User Store: indicates if the certificate should be fetched from the current user store, if not it will be fetched from the local computer store.
Product Specific Settings
ClearWay™
Send Size Classification Report: when enabled ClearWay™ Size & Classification Reports will sent if Traffic Analysis is enabled.
...
Related Information
Filter by label (Content by label) | ||||||
---|---|---|---|---|---|---|
|