Network Ports and Firewall¶
The connections MetaMiner opens and accepts, so you can request firewall rules before you install.
Inbound to the MetaMiner server host¶
| Port | Protocol | From | Used for | Change it in |
|---|---|---|---|---|
| 49714 | TCP (HTTP/WebSocket, optional TLS) | Client workstations, browsers, the MetaMiner Administrator | MetaMiner Client connections, Web Console, configuration saves | MMA Preferences > Settings... > General, Server Port (port in config.json) |
| 49614 | TCP (PostgreSQL) | Only hosts that query the MetaMiner Database directly (reporting tools, ODBC) | Embedded MetaMiner Database | MMA Configure MMDB |
All other MetaMiner ports listen on the local host only and need no firewall rule:
| Port | Process | Note |
|---|---|---|
| 49717 | MetaMiner Web Apps | Reached by browsers through port 49714 |
Keep the database port closed unless you need it
Clients and browsers never connect to the MetaMiner Database. Open 49614 only for the hosts in Direct MMDB Access, and see Network Exposure.
Port reservation during installation
The installer asks Windows to exclude the MetaMiner default ports from the range it hands out to other programs, so another process cannot take them. The result is logged in server\logs\mm-port-protection.log.
Client auto-detection of servers (UDP multicast)
The Connection Manager in the client can find MetaMiner Servers on the local network by UDP multicast to group 228.5.6.7. The server answers on UDP ports 49352, 54215, 58632 or 63759; the client listens on 49752, 55447, 59429 or 64186. Firewalls often block this. If auto-detection finds nothing, type the server host and port instead; no multicast rule is required.
Outbound from the MetaMiner server host¶
| Destination | Port | Used for | Required |
|---|---|---|---|
| BusinessObjects CMS | CMS name server port (BusinessObjects default 6400) plus the CMS request port | All pulls and actions through the BusinessObjects SDK | Yes |
| BusinessObjects web tier (RESTful Web Service) | As configured in your BI platform | Web Intelligence document processing on BI 4.x | Yes, for Web Intelligence deep processing |
| BusinessObjects audit database | Database listener port | Audit history | Optional |
| BusinessObjects CMS database | Database listener port | Faster change detection on large systems | Optional |
| External PostgreSQL (if not embedded) | Database listener port (PostgreSQL default 5432) | MetaMiner Database | Only with an external MMDB |
| SMTP server | 25, 587 or your relay port | Notification and diagnostic e-mail | Optional |
Default database ports offered in the MetaMiner Administrator when you configure an audit or CMS database:
| Database type | Default port |
|---|---|
| SQL Server | 1433 |
| Oracle | 1521 |
| SAP HANA | 30015 |
| DB2 | 50000 |
| MySQL | 3306 |
| PostgreSQL | 5432 |
| SQL Anywhere | 2638 |
TODO: list the BusinessObjects server ports each MetaMiner feature needs
Confirm, per feature, which BusinessObjects servers the SDK contacts beyond the CMS (for example Input/Output File Repository Servers for backup and promotion, Report Application Server for Crystal processing, Adaptive Processing Server for universes) and whether customers with fixed request ports must open them.
Client workstations¶
| Destination | Port | Used for |
|---|---|---|
| MetaMiner Server | 49714 TCP | All client functions |
| BI launch pad | As configured | Open in Browser and report validation |