Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ PI Server Installation and Configuration (PI Server 2018)

List of port requirements for PI Notifications Service

List of port requirements for PI Notifications Service

  • Last UpdatedFeb 12, 2025
  • 1 minute read

Functionality

Remote application

Protocol

Port

Direction (1)

Local application

Email delivery channel (required if using email notifications)

SMTP server

TCP

25 (2)

Outbound

PI Notifications Service

Client to PI Notifications service (base functionality)

PI AF SDK clients (for example, PI System Explorer or PI Vision)

TCP

5468

Inbound

PI Notifications Service

Web service delivery channel (required if using SOAP or REST services)

Web service

TCP

User configured

Outbound

PI Notifications Service

1 Direction is in relation to the computer where PI Notifications Service is running. For example, Outbound means that firewall rules must allow traffic to leave the PI Notifications Service node and be directed towards the remote node; Inbound means that firewall rules for the PI Notifications Service node must accept incoming connections from the remote node.

2 Default port can be changed during configuration.

TitleResults for “How to create a CRG?”Also Available in