Troubleshooting Integrator

Owned by Jonathan Reis
Nov 23, 2015
Components

Integrator has several components, please take a minute to review the general architecture. This will help you understand the various troubleshooting tasks.

In addition to Connexion with advanced services, the integrator application has four components:

  1. Channel Runner - this service loads and runs channels. It runs with limited privileges.
  2. Remote Agent - this service is responsible for creating a communications channel to the datacenter Connexion, as well as brokering communications between the channel runner and the datacenter.
  3. Updater - Not currently used.
  4. MongoDb - the database used for message persistence.
Communications

For an integrator instance to connect to Connexion, the following must be true:

  • A port (default 8085) must be opened at the datacenter to allow inbound traffic from remote integrators.
  • The integrator host computer must allow outgoing connections. Firewalls which block outbound traffic will need an exception added for port 8085 (or whatever port is configured).
  • The 'hub', the datacenter-side component which receives connections from remote instances, must be configured with a FQDN if you are connecting across networks.

Connexion

Connexion must be running with advanced services enabled. Please see the sprint 2 document for details.

If you cannot connect the remote agent management UI to connexion, please ensure that the connection details are correct. The target port should be the same as what the Connexion client app uses - typically 8081 or 8082.

If you cannot connect after verifying the port, you will need to check the Connexion log files to ensure the advanced services endpoints are running and that there aren't any silent errors occurring. Please see here for opening the log files. You should find the following lines in your Connexion.txt log file:

'External Remote Integrator Service' Started on 'net.tcp://0.0.0.0:8085/ConnexionV14/RemoteAgentRegistrationService.svc' with compression type NONE 
'Remote Integrator Hub Service' Started on 'net.tcp://0.0.0.0:8082/ConnexionV14/RemoteAgentHubService.svc' with compression type NONE

If you do not find these, your advanced services have not been correctly configured or are failing to start. You will need to check the log file for errors and confirm you've correctly configured advanced services.

Integrator

If you are able to connect to Connexion with both the standard connexion UI as well as the integrator management UI, and you have configured your HUB endpoint and your remote integrator instances still cannot connect, we will need to inspect the log files of the integrator instance (on the machine with integrator installed).

The log files are located in the c:\programdata\connexion.integrator\logs folder. There are two files of interest: ChannelRunner.txt and RemoteAgent.txt. You will need to inspect these files for signs of errors, and contact Inner Harbor if there are no errors logs or they do not point to a solution.