Inbound Connections
The host where MMTE Server and MMTE Administrator are installed must be configured to accept the following inbound connections:
| Protocol | Port | Accessible from | Features | Notes |
|---|---|---|---|---|
| MetaMiner Protocol | 49714 TCP (default value, can be changed) | All Tableau Servers and hosts where MMTE Client is installed | SSL (optional) WebSocket (required) |
Required. A proprietary protocol for communication between the MMTE Server and its client software (MMTE Client and remote monitoring agents). You can specify any TCP port, but it is your responsibility to avoid possible conflicts and enable communication through your firewalls, proxy servers, and other network infrastructure. Note that network connections from the Tableau Server hosts to MMTE Server on this port must be open as well, because MetaMiner Remote Tableau Metrics Agent uses it. |
| Pulse/Grafana HTTP | 3000 TCP (default value, can be changed) | All hosts from which Pulse/Grafana should be accessed | SSL (optional) | Optional. This port should be open on the MMTE Server host to client workstations to access web-based dashboards for monitoring. |
| Remote Desktop Protocol | 3389 TCP 3389 UDP |
All hosts from which system administrator will use MMA | RDP is used for MMS/MMA maintenance | |
| RAS | 6499 TCP (default value, can be changed) | All hosts used for RAS SDK | Optional, disabled by default. See VMARG System Variables | |
| JMX remote connection | 8085 TCP (default value, can be changed) | All hosts used for remote debug | Optional, disabled by default. See VMARG System Variables |
See Configuring MMTE Server Settings about how to change the default port for MetaMiner Protocol to a custom value.
See Metaminer Client's connection to Metaminer server about enabling/disabling to run connections between MMC and MMS over SSL cryptographic protocol (recommended).
The hosts on which MMTE Client is installed should not accept inbound connections.
See also