Topology 3A diagram

The following diagram shows the achievable performance envelope for Topology 3A when built with the prescribed servers, hardware resources, software, and data flows.

Note: Only small amounts of PI to CONNECT transfer data are acceptable when the PI to CONNECT Agent is loaded on the Data Archive node.

Topology 3A: PI data flows

1. Inbound Data Flowing to PI Data Archive - TCP port 5450 (Clients)

2. PI AF, SQLDAS to PI Data Archive - TCP port 5450 (PINET-Data Archive)

3. PI AF, SQLDAS to MS SQL Server - TCP port 1433 (SQL), UDP port 1434 (SQL)

4. PI Analysis Service, Notifications Flowing to Asset Framework - TCP port 5457 (PINET-AF)

5. PI Analysis Service, Notifications Flowing to PI Data Archive - TCP port 5450 (PINET-Data Archive)

6. PI Vision Requests Flowing to MS SQL Server - TCP port 1433 (SQL), UDP port 1434 (SQL)

7. PI Vision and WebAPI Requests Flowing to PI Data Archive - TCP ports 5450 (PINET-Data Archive)

8. PI Vision and WebAPI Requests Flowing to PI Asset Framework - TCP ports 5457 (PINET-AF)

9. PI Client Requests Flowing to PI Data Archive - TCP ports 5450 (PINET-Data Archive)

10. PI Client Requests Flowing to PI Asset Framework and SQL DAS - TCP ports 5457 (PINET-AF), 5464 (SQLDAS-HTTP/SOAP), 5465 (SQLDAS-net.tcp)

11. PI Client Requests Flowing to PI Analysis Service and PI Notifications - TCP port 5463 (PINET-Analysis), 5468 (PINET-Notifications)

12. PI Web Clients Requests Flowing to PI Vision Server - TCP ports 80 (HTTP), 443 (HTTPS)

13. PI to CONNECT data transferred to CONNECT data services - TCP port 443 (HTTPS) outbound to PI to Data Hub gateway. Data Hub gateway URL varies based on Data Hub namespace region

14. Adapter OMF Requests Flowing to WebAPI - TCP ports 80 (HTTP), 443 (HTTPS)