https://docs.splunk.com/Documentation/Splunk/8.0.5/Admin/Inputsconf
[tcp://<remote server>:<port>]
*Configures the input to listen on a specific TCP network port.
*If a <remote server> makes a connection to this instance, the input uses this stanza to configure itself.
*If you do not specify <remote server>, this stanza matches all connections on the specified port.
*Generates events with source set to "tcp:<port>", for example: tcp:514
*If you do not specify a sourcetype, generates events with sourcetype set to "tcp-raw"

The indexing pipeline and the parsing pipeline are the two pipelines that are responsible for transforming the raw data into events and preparing them for indexing. The indexing pipeline applies index-time settings, such as timestamp extraction, line breaking, host extraction, and source type recognition. The parsing pipeline applies parsing settings, such as field extraction, event segmentation, and event annotation.

Reference:
Updateconfigurations#2._Reload_the_deployment_server
https://docs.splunk.com/Documentation/Splunk/8.0.5/Updating/Useserverclass.conf
"Use serverclass.conf to define server classes" "The most important settings define the set of deployment clients and the set of apps for each server class."

https://docs.splunk.com/Documentation/Splunk/8.0.3/Data/Monitornetworkports