Skip to content

Connection Manager

Connection Manager is a tool used to manage your connection to MMTE Server.

To open Connection Manager:

The Connection Manager window opens:

Connection Manager

When you open Connection Manager, it auto-detects MMTE Servers in your local area network by sending broadcast requests via all network interfaces of your computer on most typical TCP ports used by MMTE (see Network Configuration).

You can also force MMTE Client to re-scan your LAN by pressing the Refresh Refresh button.

MMTE Client collects responses of MMTE Servers in your network, it takes some time:

Connection Manager

When auto-detecting finishes, the list of auto-detected MMTE Server instances is displayed at the top the Connection Manager window, if there are any. Otherwise, a warning about firewalls is displayed:

Connection Manager

To choose your MMTE Server:

  1. Choose MetaMiner Server Host from the list of auto-detected instances, or specify the host manually. For this, you can enter its host name or FQDN, or IP address. Examples:

        infolytikserver

    myserver.company.com

    74.189.15.169

  2. Specify MetaMiner Server Port for the connection, if it differs from the default or auto-detected value. Note that you must specify the same value that was previously entered in MMTE Administrator (see Server Section Settings).

  3. Click the Connect button.

    If User Defined Security is enabled, the Login Required dialog box will appear:

    Connection Manager - Login Required

  4. Click OK.

    The Validating connection... dialog window opens.

  5. Wait for the end of validation process. Results are displayed in the Connection Manager window.

    If connection to MMTE Server was successful, then the Host and Port fields are displayed with green marks Mark Complete:

    Connection Manager - Success

    But if connection to MMTE Server failed, its name is displayed with a red icon:

    Connection Manager - Failure

  6. Make sure connection to your MMTE Server is validated. The list of Tableau environments, available on the selected server, is now displayed at the bottom part of the Connection Manager window.

  7. You may want to skip loading of some environments by clearing the appropriate Enable checkboxes in the list to minimize the resources required by MMTE Client.
  8. If you want to connect to the same server and the same environments each time you start MMTE Client, and save your choice of environments, check the Reconnect on startup checkbox.
  9. Click Apply. Connection to the MMTE Server is established, and your configuration is saved.

  10. The Enter Tableau SSO Credentials dialog box opens:

    Connection Manager - Tableau SSO

  11. Specify login & password for each Tableau environment you are going to connect. Note that generally speaking these credentials are different from those specified on the previous step.

  12. Click OK. MMTE Client starts to load your BI data from the selected environments.
  13. Wait for the BI data to be loaded from MMTE Server to MMTE Client. When you connect MMTE Server to your environment for the first time, this initial pull from Tableau may take much time, and MMTE Client will not finish loading until this initial pull is finished. See also Connecting MMTE to your Tableau Software.

Finally, the main MMTE Client screen is displayed.

Monitoring Connection to MMTE Server

During your work with MMTE Client, you can constantly monitor status of your connection to MetaMiner Server. For this, look at the left bottom corner of the MMTE Client window, in Status Bar:

Connection Status

If connection to MMTE Server works fine, the server icon has a green label, as shown above.

Otherwise, the icon has a yellow warning label:

Connection Lost

To fix problems with the connection, open Connection Manager again by clicking the server icon.

Connecting over SSL

There are absolutely no manoeuvres for the customers for achieving this as the MMTE Client is configured to handle this implicitly.

Here is the detailed explanation of MMTE Client SSL connection workflow.

  1. MMTE Client tries to connect MMTE Server over SSL.

  2. If the server is SSL enabled, then it connects successfully.

  3. If the server is not SSL enabled, then it connects with MMTE Server without SSL.

So, either way SSL/Non SSL connections to MMTE Server are handled by MMTE Client effortlessly.

See also

What is the MMTE Server?

What is MMA?

Back to top