In a typical installation scenario, where separate instances are running for the Managing Node, SQL Server, and the numerous Worker Nodes, it is essential to configure the firewall rules to enable proper communication. Let's explore the necessary ports for each service:
Managing Node
Inbound Rules:
- TCP port 14711: Used for SOAP requests from clients when using HTTP.
- TCP port 14713: Used for SOAP requests from clients when using HTTPS.
- TCP port 14714: Used for REST requests from clients (an alternative port for REST requests can be defined in the <ManagingNodeConfig.user.xml> file).
- TCP port 14712: Used for communication with the Worker Node.
Outbound Rules:
- Remote TCP port 14721: Required for communication with the Worker Node.
Worker Node
Inbound Rules:
- TCP port 14721: Necessary for communication with the Managing Node.
Outbound Rules:
- Remote TCP port 14712: Required for communication with the Managing Node.
Database
To ensure seamless communication between the Rendition Server services and the SQL Server, it is advisable to open the following ports on the database machine using inbound rules:
- TCP port 1433: Used for general communication.
- UDP port 1434: Used for SQL Server browser service.
By configuring the firewall to allow traffic through these specific ports, you can establish smooth communication between the Managing Node, Worker Nodes, and the SQL Server, facilitating the efficient operation of the Rendition Server.
Remember to adjust the firewall settings accordingly, and consult your organization's security policies and network administrators for any additional requirements or considerations.
By following these guidelines, you can ensure secure and uninterrupted communication between the various components of your Rendition Server deployment.
