Prerequisites for destination types
- Last UpdatedMay 15, 2026
- 2 minute read
- PI System
- PI System Connector 3 3.0
- Connectors
Ensure the following prerequisites are met before configuring the AVEVA PI System Connector 3 (PSC3) to send data to either a PI System or a Broker.
Certificates and security requirements
PSC3 uses certificate-based authentication to secure communication between the connector and broker or a broker and broker.
-
Create and install all required certificates on the appropriate machines.
-
Confirm that each certificate is trusted by the local system and appears in the correct certificate store.
-
Ensure both the connector and broker hosts have the corresponding certificates installed and trusted if you are configuring communication with a Broker. See Certificate requirements for Brokers for additional information.
Network and port accessibility
PSC3 must be able to reach its destination, whether a PI System or a Broker, over the network paths you intend to use.
-
Ensure firewalls permit inbound and outbound traffic on all required ports.
-
Verify that the destination hostname and port are reachable from the connector machine.
-
When using a Broker, confirm that the broker’s listener port matches the port entered on the connector’s Destination tab.
Destination system readiness
The destination must be prepared to receive data before PSC3 begins sending it.
-
For PI System destinations, confirm that the AF Server and Data Archive are online, accessible, and properly licensed.
-
For Broker destinations, confirm that the Broker service is running and its forwarding configuration (to a PI System or another Broker) is complete.
Connector application access and service status
To configure destination settings, you must be able to access PSC3’s user interface.
-
Ensure the connector service is installed and running on the machine.
-
Verify that you can open the Connector UI locally, as configuration tasks must be performed on the host system.
Data source and shared data source options
PSC3 applies several shared settings across all data sources.
-
Review and update shared data source parameters, such as scan rates and history recovery settings. See Shared Data Source Options for additional information.
-
Confirm these values meet the deployment needs to ensure consistent behavior across all data sources.