Data Source Files - Ironstream_Hub - 1.3.1

Data source configuration files are defined in the source subdirectory of the Configuration Directory. Each Source Connection needs a separate file in this folder.

The filename should have a .json extension. The filename should be the Id of the Data Source. For example, 12345678-1234-1234-1234-123456789012.json.

These items can be defined in each file:

Fields Description Valid Values Default Value Name Name of the Source Connection. Must be unique Id UUID of the Source Connection. Must be unique ConnectorType Type of Connection: currently there is only one. TcpIpServer TcpIpServerConfiguration: Port The port that Hub will listen on. 1024 - 49151 None TcpIpServerConfiguration: Delimiter The delimiter that Hub will use to split incoming records into individual records. Note that a delimiter will be a character that does not appear within the individual records, only between those records. For Ironstream for IBM Z, the delimiter should be set to "\n" (see Configuration of the Ironstream for IBM Z Agent). None TcpIpServerConfiguration: AnnotateWithClientHostName Obtains the host name from each connected client using a reverse DNS lookup. If available, then the host name will be used by a File Destination as a part of the file name. If the lookup of the host name fails, then the IP address will be used instead. true or false false TcpIpServerConfiguration: BufferSizeInKiloBytes The size of the buffer at the source. Once this volume of data has been accumulated within the buffer the data will be sent through the pipeline. If the network buffer becomes empty, then the data will be immediately sent regardless of whether the buffer’s threshold has been reached. This is more likely in low throughput scenarios. 0 or positive integer 2560 KB (2.5 MB) TcpIpServerConfiguration: TlsConfiguration : On If set to true, then TLS will be turned on for all inbound connections on this port. true or false false TcpIpServerConfiguration: TlsConfiguration : AutoGenerateCertificate If set to true, then Hub will use an autogenerated self-signed certificate. The PathToCertificateFile and PathToKeyFile fields will be ignored. true or false false TcpIpServerConfiguration: TlsConfiguration : PathToCertificateFile File system path to the certificate file to use when TLS is turned on. Valid file system path Mandatory if On is true and AutoGenerate Certificate is false TcpIpServerConfiguration: TlsConfiguration : PathToKeyFile File system path to the file containing the private key when TLS is turned on. Valid file system path Mandatory if On is true and AutoGenerateCertificate is false MonitorPipelineWaitMS If no data is received for this amount of time, then the pipeline monitor will take a performance measurement. Null or positive integer Null