Here we talk about typical installation of MetaMiner in corporate landscape.

This study covers:

The following diagram shows MetaMiner components, your corporate infrastructure linked with MetaMiner, their connections, and users:

MetaMiner Server is the center of your installation

SAP BusinessObjects CMS Server and Audit Database provide MetaMiner with your corporate data

MetaMiner Database stores all data retrieved by MMS

MetaMiner Administrator allows system administrator(s) to configure and monitor MetaMiner Server. MMA always runs on the same computer as MMS.

MetaMiner Client should be installed on a computer of any user who intend to use MetaMiner benefits

 

Data Exchange

Connections between MetaMiner components and modules are shown on a diagram above.

MetaMiner Server connects most of the components, servers, and databases together, providing a complete solution to users via MetaMiner Client.

Communication between Client and Server components is achieved via the proprietary MetaMiner protocol running in one of 2 modes: normal and secure (SSL-enabled), on TCP/IP port 49714 by default. You use Connection Manager in MetaMiner Client to configure and start connection to MetaMiner Server. MMC does NOT pull changes automatically. To refresh local data at the client side, users use the icon on Client status bar.

MetaMiner Server retrieves the information from your corporate SAP datasources every 7 minutes, by default. After retrieving the updated data snapshot, it stores it in the MetaMiner Database. These periods can be customized to be faster.

However, for some actions data is retrieved from SAP datasources (mostly, from the Audit Database) directly.

Connection Manager is used to connect to MMS. Once it fetches info from MMS to MMC, it does not pull it anymore... then you need to press Refresh in MMC. At this moment, the updated snapshot is sent.

 

 
See also

Network Requirements and Permissions

MetaMiner Server

Business Objects

About Initial and Incremental Pull