Topology 3: Overview & diagram

Keep these points in mind when building Topology 3:

1. The hard drive sizes shown in the diagram are what the virtual machines in the test lab used; the sizes needed may vary, especially for the Data Archive servers and shared, external storage devices used for proxy drives.

2. You can assume that versions the same as or newer than those used in testing provide the same level of performance. When a new version of a PI product is released that changes performance, topology information will be updated.

The following diagram shows Topology 3’s achievable performance envelope when built using the prescribed servers, hardware resources, software, and data flows.

PI Data Flows: Topology 3

The following list corresponds to the numbered data flow lines in the diagram.

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

4. PI Data Archive Collective Node Traffic

5. PI AF, SQL DAS to PI Data Archive - TCP port 5450 (PINET-Data Archive)

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

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

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

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

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

11. PI Vision and Web API Requests Flowing to PI Asset Framework - TCP ports 5457 (PINET-AF)

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

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

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

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