Recommended firewall settings for an on-premise installation of Data Virtuality

Recommended firewall settings for ports used by Data Virtuality Server.

Name in dvserver-standalone.xmlPortPrivate networkPublic networkDescriptionUsed by Data Virtuality StudioNecessary for DV to start
jboss.socket.binding.port-offsetN/AN/AN/APort offsetN/AN/A
management-http9990ClosedClosedWildFly management interface.NoNo
management-https9993ClosedClosed
ajp8009ClosedClosedApache JServ Protocol. Used for HTTP clustering and load balancing.NoNo
http8080OpenClosedDefault Data Virtuality Server portal and Rest API server.NoNo
https8443OpenOpenNoNo
txn-recovery-environment4712OpenClosedThe JTA transaction recovery manager.NoYes
txn-status-manager4713OpenClosedThe JTA / JTS transaction manager.NoYes
dv-jdbc31000OpenClosed YesNo
dv-jdbc-ssl31001OpenOpen YesNo
dv-odbc35432OpenClosed NoNo
dv-odbc-ssl35433OpenOpen NoNo
postgresql DB54322OpenClosedInternal Postgres DBNoYes

Additional information can be found here: https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform/6/html/installation_guide/network_ports_used_by_jboss_enterprise_application_platform_62

Port offset

Already documented. CData Virtuality Documentation

management-http and management-https

This is a web-based management console for WildFly.

For more information, please refer to this documentation: Management Clients - WildFly 10

Ajp (Apache JServ Protocol)

The Apache JServ Protocol (AJP) is a binary protocol that can proxy inbound requests from a web server through to an application server that sits behind the web server. AJP is a highly trusted protocol and should never be exposed to untrusted clients, which could use it to gain access to sensitive information or execute code on the application server.[1]

For more information, please refer to this documentation: Apache JServ Protocol - Wikipedia

http and https

Default ports for a web-based interface to Data Virtuality. This portal include links to binaries, management, and documentation. These are also the ports used by the Rest API server inside of Data Virtuality Server.

txn-recovery-environment and txn-status-manager

Internal transaction manager and transaction crash recovery system for WildFly. Used by Data Virtuality Server.

See https://access.redhat.com/documentation/en-us/jboss_enterprise_application_platform/5/html/transactions_development_guide/chap-transactions_jta_programmers_guide-transaction_recovery

dv-jdbc

Port used by client connections using the Data Virtuality JDBC connector. This port does not encrypt traffic between the client and the server.

dv-jdbc-ssl

Port used by client connections using the Data Virtuality JDBC connector. This port uses SSL to encrypt the traffic between the client and the server.

dv-odbc

Port used by client connections using the Data Virtuality ODBC driver. This port does not encrypt traffic between the client and the server.

dv-odbc-ssl

Port used by client connections using the Data Virtuality ODBC driver. This port uses SSL to encrypt the traffic between the client and the server.

References

“AJP File Read/Inclusion in Apache Tomcat (CVE-2020-1938) and Undertow (CVE-2020-1745)”. Red Hat Customer Portal*. Retrieved* 1 March 2020.

1 Like