Windows Services¶

The Windows services and child processes that make up a MetaMiner Server installation for Power BI, and how they depend on each other.

Services¶

Service name	Display name	Program	Role
`metaminer`	MetaMiner Service	`server\MetaMinerServer.exe`	The MetaMiner Server (MMS): Power BI collection, client connections, API, MMDB updates, backup jobs, retention jobs
`InfolytikPostgres`	Infolytik Postgres DB	PostgreSQL in `server\pgsql-win-16.3.2\`	Embedded MetaMiner Database (MMDB); not present with an external database
`MetaMinerWebApps`	MetaMiner Web Apps Service	`server\MetaMinerWebApps.exe`	Web apps under `/web/`, including the Power BI usage dashboards, reached through the MMS port
`MetaMinerFSS`	MetaMiner Flow Scheduler Service	`server\MetaMinerFSS.exe`	Tableau Prep flow scheduling; off unless enabled, not used with Power BI

flowchart LR
  MMA[MMA Start Server] --> MMS[metaminer]
  MMS -->|starts, waits for| PG[(InfolytikPostgres)]
  MMA --> WA[MetaMinerWebApps]
  MMA -.->|only if enabled| FSS[MetaMinerFSS]
  WA -->|data| MMS
  MMS -->|HTTPS| MS[Microsoft APIs]

Dependencies and order¶

MMA Start Server starts metaminer, waits for the embedded database, then starts MetaMinerWebApps and, if enabled, MetaMinerFSS. Stop Server stops them in reverse and leaves InfolytikPostgres running. See Start and Stop the Server.
MMS starts InfolytikPostgres when it is not running. Windows restarts the database service automatically up to three times after a failure.
net start metaminer starts only MMS; start MetaMinerWebApps separately.
Microsoft API calls for collection and backups come from the metaminer service. Environment validation runs in the MMA process on the same machine.

Child processes¶

MMS starts these processes itself. They stop with MMS.

Process	Purpose
`MetaMinerQueryAgent.exe`	Runs MetaQuery SQL against the MMDB; memory set on the Meta Query page
InfluxDB (`influxd.exe`)	Metrics storage, when InfluxDB Enabled is on
Grafana (`grafana.exe`)	SAP BusinessObjects Pulse dashboards, when Pulse Enabled is on and licensed
Metadata engines	Separate Java processes that build lineage and SQL metadata

Ports¶

Port	Used by
49714	MMS (MetaMiner Client, MMA, web apps, API)
49614	Embedded MMDB
49717	`MetaMinerWebApps`, local to the server
49716	`MetaMinerFSS`, local to the server

The installer reserves these ports in Windows so other programs are not assigned them dynamically. Outbound, MMS needs HTTPS (443) to the Microsoft endpoints of your cloud. See Ports and Endpoints and Network and Microsoft Endpoints.

Service account¶

The services run under the account chosen at installation. That account needs write access to the installation folder and to the backup archive path if it is a UNC share. If your network uses an outbound proxy, the account must be able to reach the Microsoft endpoints through it. See Service Accounts.

TODO: document the default service account and startup type of each service

Source to check: installer service registration. Fill in the account (LocalSystem or other) and startup type (Automatic, Manual) per service.