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

MIMB Bridge Documentation

MIMB Import Bridge from Salesforce (SFDC) Database

Bridge Specifications

Vendor Salesforce
Tool Name Database
Tool Version Summer '17
Tool Web Site
Supported Methodology [Relational Database] Data Store (Physical Data Model) via REST API

Tool: Salesforce / Database version Summer '17 via REST API
Metadata: [Relational Database] Data Store (Physical Data Model)
Component: SalesForceObjects version 11.0.0

This bridge authenticates the consumer and retrieves available physical metadata (e.g., Tables). Utilizing the username-password authentication flow that assumes the consumer already has the user's credentials.

In the event that users will be submitting Salesforce Documents, certain security settings must be configured to allow this access on Standard Objects and Custom Objects.
To configure permissions:
- Within Salesforce, click on Setup and then click on Manage Users
- Under the Manage Users tree click on Profiles
- Once the Profiles appear on the right, select which Profile you want to edit and click on the Edit link next to the corresponding profile

Standard Objects: Ensure that the "Documents" section has the Read permissions selected.
Custom Objects: Ensure that the Read permissions selected for each custom objects.


Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html
Field called "Description" in third column is ommitted by Salesforce API, consequently will not appear under any of the Profiles.

Provide a trouble shooting package with:
- the debug log (can be set in the UI or in conf/ with MIR_LOG_LEVEL=6)
- the metadata backup if available (can be set in the Miscellaneous parameter with option -backup)

When you do not have username-password authentication parameter values but have an access token and your Salesforce instance URL you can specify them using the Miscellaneous parameter (see its description for details). In this case, you still need to fill all mandatory parameters with some text that will be ignored.

Bridge Parameters

Parameter Name Description Type Values Default Scope
Instance/My Domain URL The Salesforce login endpoint URL.
By default (when the value is empty) it is
You can use your company' instance URL (such as or My Domain URL (such as
User The username of the user that the connected app is imitating. STRING     Mandatory
Password The password of the user that the connected app is imitating.
The security token is an automatically generated key that must be added to the end of the password to log in to Salesforce from an untrusted network.Concatenate the password and token when passing the request for authentication.;type=5
PASSWORD     Mandatory
Consumer Key The Consumer Key from the connected app definition.
The connected app's consumer key, which you can find on the connected app's Manage Connected Apps page or from the connected app's definition.;type=5
STRING     Mandatory
Consumer Secret The Consumer Secret from the connected app definition.
The connected app's consumer secret, which you can find on the connected app's Manage Connected Apps page or from the connected app's definition.;type=5
PASSWORD     Mandatory
Objects List of object names, like 'object1, object2'.
An empty list means that all available objects.
You can specify object names as a wieldcard pattern, e.g.


Miscellaneous Specify miscellaneous options starting with a dash and optionally followed by parameters, e.g.
-connection.cast MyDatabase1="SQL Server"
Some options can be used multiple times if applicable, e.g.
-connection.rename NewConnection1=OldConnection1 -connection.rename NewConnection2=OldConnection2;
As the list of options can become a long string, it is possible to load it from a file which must be located in ${MODEL_BRIDGE_HOME}\data\MIMB\parameters and have the extension .txt. In such case, all options must be defined within that file as the only value of this parameter, e.g.

-m <Java Memory's maximum size>
1G by default on 64bits JRE or as set in conf/, e.g.
-m 8G
-m 8000M

-j <Java Runtime Environment command line options>
This option must be the last one in the Miscellaneous parameter as all the text after -j is passed "as is" to the JRE, e.g.
-j -Dname=value -Xms1G
The following option must be set when a proxy is used to access internet (this is critical to access (and exceptionally a few other tool sites) in order to download the necessary third party software libraries.
-j -Dhttp.proxyHost= -Dhttp.proxyPort=3128 -Dhttps.proxyHost= -Dhttps.proxyPort=3128 -Dhttp.proxyUser=user -Dhttp.proxyPassword=pass -Dhttps.proxyUser=user -Dhttps.proxyPassword=pass

-jre <Java Runtime Environment full path name>
It can be an absolute path to javaw.exe on Windows or a link/script path on Linux, e.g.
-jre "c:\Program Files\Java\jre1.8.0_211\bin\javaw.exe"

-v <Environment variable value>
None by default, e.g.
-v var1=value1 -v var2="value2 with spaces" <model name>
Override the model name, e.g. "My Model Name"

-prescript <script name>
The script must be located in the bin directory, and have .bat or .sh extension.
The script path must not include any parent directory symbol (..).
The script should return exit code 0 to indicate success, or another value to indicate failure.
For example:
-prescript "script.bat arg1 arg2"

Clears the cache before the import, and therefore will run a full import without incremental harvesting.
Warning: this is a system option managed by the application calling the bridge and should not be set by users.

the Salesforce access token. It is a 'long' case-sensitive alphanumeric key that is used FOR temporary (minutes or hours) access Salesforce. When an access token expires, attempts to use it fail. In Salesforce terms, the access token is a session ID (SID), much like a session cookie on other systems. It must be protected against misuse.
-instance_url your Salesforce insatance URL (e.g. -instance_url


Bridge Mapping

Mapping information is not available

Last updated on Fri, 25 Sep 2020 17:37:51

Copyright © Meta Integration Technology, Inc. 1997-2020 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.