Security for Production Management Network
- Last UpdatedJul 25, 2024
- 1 minute read
Securing the Network
-
Network Communication
-
Ports
-
Security for integrations and Web services
Connecting to Server through firewall ports
We recommend only opening the specific firewall ports required by AVEVA™ Production Management.
For clients to connect to Server through a firewall, Server requires the following ports on the server to be open for incoming traffic. This includes Studio clients, Production Analyst clients (web and desktop), and custom clients that use AVEVA™ Production Management web services.
This is the list of ports required to be open for incoming traffic.
Note: Other applications or components you use with the AVEVA Production Management, if any, may have specific port requirements. For more information, see their documentation.
|
Port |
Traffic |
|---|---|
|
1235* |
Production Analyst |
|
1240 |
Health Monitoring (if enabled) |
|
7001 |
Downtime REST Web API |
|
7002 |
Configuration REST Web API |
|
7003 |
Authorization REST Web API |
|
7004 |
Shift log REST Web API |
|
7100 |
Data curation REST Web API (HTTPS) |
|
7101 |
Data curation REST Web API (HTTP) |
|
7321 |
Notification client |
|
8001* |
Studio |
|
808 |
WCF services (TCP Binding) |
|
8889* |
WCF services (HTTP Binding) |
|
8890* |
Real-Time communications |
|
9003* |
Production Management REST Web API |
*These are default ports used within AVEVA Production Management and are configurable. For information on how to configure these ports, see AmplaUtil, Modify the ServerRemoting config file, and Modify the SE.SPO.AmplaStudio.exe config file.
Communication Protocol for Web services
When using the AVEVA™ Production Management Web services, we recommend using NetTcp bindings – instead of HTTP bindings – because Net TCP implements transport layer security.