Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from Looker Server - New Beta Bridge

Bridge Specifications

Vendor Looker
Tool Name Looker
Tool Version 7.2
Tool Web Site https://www.looker.com/
Supported Methodology [Business Intelligence] Multi-Model, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Report Structure) via REST API

BRIDGE INFORMATION
Import tool: Looker Looker 7.2 (https://www.looker.com/)
Import interface: [Business Intelligence] Multi-Model, BI Design (RDBMS Source, Dimensional Target, Transformation Lineage, Expression Parsing), BI Report (Relational Source, Dimensional Source, Report Structure) via REST API from Looker Server - New Beta Bridge
Import bridge: 'Looker' 11.0.0

BRIDGE DOCUMENTATION
This bridge imports metadata from a Looker server, including database connections, LookML Models, and associated reports (Looks and Dashboards).

A Looker API3 key is required in order to login and use the Looker Restful API.
Please use the Looker Admin console to configure an API3 key on a user account.
The API3 key consists in a public client_id and a private client_secret (OAuth2 authentication pattern).
* Select a user in the 'Users' section of the 'Admin' panel
* In the section 'API3 Keys' choose 'Edit Keys'
The 'Client ID' and 'Client Secret' values are displayed https://docs.looker.com/reference/api-and-integration/api-auth
https://docs.looker.com/admin-options/settings/users#api3_keys
You can test that the API key is configured correctly by performing a login on this page:
https://server:19999/api-docs/index.html
Looker versions 3.4+ expose the Restful API on default port is 19999.
Please use the Looker Admin console to check your API port.
https://docs.looker.com/reference/api-and-integration/api-troubleshooting

You may use this URL in a web browser, to check the API availability and version(s) number(s):
https://server:19999/versions

SUPPORT

Q: How do I provide metadata to the support team to reproduce an issue?
A: Configure the bridge parameter 'Incremental import=False' and configure the bridge 'Miscellaneous' parameter to save metadata as files into a local directory.
Compress the resulting files in a ZIP archive and send to the support team.


Bridge Parameters

Parameter Name Description Type Values Default Scope
Server API URL Enter the Looker API URL here.
The default port for API requests is port 19999.
All Looker API endpoints require an HTTPS connection.
STRING   https://localhost:19999/ Mandatory
Login User Enter the username which the bridge will use to log in. Be sure this user name has necessary permissions to access the objects you wish to import.
This corresponds to the Client ID for an OAuth authentication method.
STRING     Mandatory
Login Password Enter the password associated with the username which the bridge will use to log in.
This corresponds to the Client secret for an OAuth authentication method.
PASSWORD     Mandatory
Project filter This option is used to select looks and dashboards by their parent project.

You can specify here multiple projects, separated by semicolon (;) character.
REPOSITORY_SUBSET      
Incremental import Specifies whether to import only the changes made in the source or to re-import everything (as specified in other parameters).

True - import only the changes made in the source.
False - import everything (as specified in other parameters).

An internal cache is maintained for each metadata source, which contains previously imported models. If this is the first import or if the internal cache has been deleted or corrupted, the bridge will behave as if this parameter is set to 'False'.
BOOLEAN
False
True
True  
Multiple threads Number of worker threads to harvest metadata asynchronously.
Leave the parameter blank to have the bridge compute the value, between 1 and 6, based on JVM architecture and number of available CPU cores.
Specify a numeric value greater or equal to 1 to provide the actual number of threads.
If the value specified is invalid, a warning will be issued and 1 will be used instead.
If you experience out of memory conditions when harvesting metadata asynchronously, experiment with smaller numbers.
If your machine has a lot of available memory (e.g. 10 Gb or more), you can try larger numbers when harvesting many documents at once.
Note that setting the number too high can actually decrease the performance due to resource contention.
NUMERIC      
Offline metadata directory In order to facilitate testing and reproducing Looker metadata environment, when that environment is not installed locally, this parameter allows importing metadata from files previously downloaded from the Looker server. Specify in this parameter the directory path where the downloaded files are located. No connection to the Looker server is needed in this case, the usual connection parameters are ignored. DIRECTORY      
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -m 4G

-v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces").
-jre {path to java executable} to specify a custom Java Runtime Environment. It could be an absolute path to javaw.exe on Windows or a link/script path on Linux.
for example: -jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"
-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G).
-f specify path to store metadata locally (for subsequent use with Offline metadata directory parameter). Incremental import should be set to false in this case.
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Mon, 23 Mar 2020 17:37:49

Copyright © Meta Integration Technology, Inc. 1997-2019 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.