Configuration

The Connector Service retrieves all its configuration from the Core Service managing it, with the exception of the initial listening port after installation. The listening port needs to be set on installation first, so the Core Service can communicate to the Connector service and send its configuration data over the network. The default listening port is 6510. All configuration required for a Connector Service to operate can be done in DataStudio after installation.

Changing the Listener Port

Be aware, that changing the listening port of the Connector Service will interrupt the communication to the Core Service once the command was passed to the Connector. Any data fetched by the Connector in the meanwhile will be buffered, until the Core can re-instantiate the communication.

Remotely

The port on which the Connector service listens for incoming connection requests can be changed in the Object Properties Panel in DataStudio. To do this, create a Connector in the Core representing the Connector service. Then, in the Object Properties Panel for the object, navigate to the 'Communication' section and change the Listener Port. Then, click Apply to implement the change.

Before applying the configuration change in DataStudio, make sure that:

  • Firewall configurations allow TCP communication using the new port

  • The new port is not used by any other process on the Connector host

When a change listening port command is issued, and this port cannot be used when trying to start a TCP communication between Connector and Core, e.g. due to firewall rules blocking this port, a Connector Service can become unreachable remotely. In this case, the configuration can only be changed locally on the Connector service host.

Locally

To change the listening port of the Connector Service locally, the new port needs to be specified as a startup parameter in the Windows Service Control Manager.

Local Configuration Storage

All configuration of the Connector Service will be intermediately stored on the local host. This is done to ensure that the Connector Service can be restarted without having a connection to Core Service. The configuration will be stored in binary format in the inmation.root\img directory. During normal operation, when connected to a Core Service, all configuration changes sent to the Connector will be effective immediately, while the intermediate configuration dump is written lazily, means when no other higher prioritized actions need to be executed. Configuration synchronization between the Core and the Connector service happens automatically in a timely manner, without any administrative action involved.