Network Considerations
Protocols
By default, the Nintex RPA Platform utilizes the Net.TCP and HTTP protocols. The platform includes the option to secure communications using SSL/TLS , in which case the primary protocols are Secured Net.TCP and HTTPS.
When deployed with SSL/TLS , one of Kryon's Windows services utilizes the HTTP protocol. The communication for this service uses a secured channel, with security implemented at the message level rather than at the transport level.
- When installing with SSL/TLS , the customer must provide the required certificate.
- Note that encrypting communications at the transport level may influence communication speed between theNintexServer and clients.
- TLS v1.2 is supported.
Ports
Nintex's default port configuration is as follows. Server-side ports are fully and easily configurable.
For standard deployments (those not using SSL/TLS ):
| Friendly name | Protocol | Server-side inbound port (configurable) |
Client-side outbound port |
|---|---|---|---|
| NGNIX port | HTTP | 80 | N/A |
For SSL/TLS deployments:
| Friendly name | Protocol | Server-side inbound port (configurable) | Client-side outbound port |
|---|---|---|---|
| NGNIX port | HTTPS | 443 | N/A |
| Discovery port | HTTP | 80 | N/A |
Port 8090 is used when installing more than oneNintex RPA Server (for unattended only).
Traffic
Downloading wizards from the Nintex Server to robots has minimal impact on overall network traffic.
Load Balancing (for attended only)
Nintex supports active-active redundancy for attended automation deployments with multiple servers. Customers can choose to implement this capability either: (i) through Nintex's internal load balancing mechanism; or (ii) by utilizing an external load balancer.
See Appendix A for an illustration of external load balancer architecture.