Set the destination

Before configuring the connector to send data to a broker, ensure the connector and broker are able to communicate on the configured ports. This may include configuring firewall rules to ensure proper routing of data.

Select Broker to forward data to another broker. This is recommended when data must cross one or more network DMZs or when multiple handoffs are required. In this configuration, the connector sends data to the broker over a secure connection, and the broker is responsible for routing the data to its final destination.

Brokered destinations require additional configuration, including certificates, port alignment, and firewall rules, and support chaining up to three brokers to accommodate complex network topologies. The broker acts as an intermediary that manages secure, controlled data transfer between systems.

If you are using a broker to send data to another broker, this configuration only requires a communication certificate, the host name of the destination Broker machine in the Broker Address field, and a valid AMQP port number.

The port number on the destination tab for the broker must correspond to the port on the broker machine where the broker is listening. For example, if the broker is configured to listen on port 5460, then the connector destination configuration should have the same port number.

After configuring the connector to send data to a broker, the broker must be set up to forward that data to the next system in the transfer path. This may be a destination PI System or another broker in a multi-hop configuration. See Configure the broker to forward data for additional information.