OT Connect System Architecture

The following image shows how these machines should be incorporated into the basic APM system architecture:

The Conductor requires access to the APM Datasource(s), so it should be installed on the APM Server with the other services.

Each OT Connect Adapter Service can connect a single Process Historian or OPC Server to a single APM Datasource, so your solution may require multiple OT Connect Adapter Services, installed on the same or different servers.

Important: Do not configure more than one Adapter with the same OT Source Name.

The OT Connect Adapter Service does not require any inbound connections, only outbound connections to the Message Broker and Cache services, allowing the OT Connect Process Data Server to be deployed within a DMZ or OT Network without compromising security.

Required Server Ports

To ensure successful communications between APM and OT Connect, make sure the listed ports are open.


Feature	Firewall Port	From	To
Tag and Subscription Synchronization	Configurable; 1433 for a default SQL Server. Additional ports as required by the chosen Authentication scheme	OT Connect Conductor	APM Database
Tag and Subscription Synchronization	Configurable; 6379 by default	OT Connect Conductor	Redis Server
Tag and Subscription Synchronization	Configurable; 61616 by default	OT Connect Conductor	ActiveMQ Server
All connectivity for that OT Source	Configurable; 6379 by default	OT Connect Adapter	Redis Server
All connectivity for that OT Source	Configurable; 61616 by default	OT Connect Adapter	ActiveMQ Server

Note: For the network requirements for each protocol, refer to About the Protocol Adapters.