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

MIMB Bridge Documentation

MIMB Import Bridge from SAS Library

Bridge Specifications

Vendor SAS
Tool Name Library
Tool Version 9.3
Tool Web Site
Supported Methodology [Relational Database] Data Store (Physical Data Model) via SPK File

Tool: SAS / Library version 9.3 via SPK File
Metadata: [Relational Database] Data Store (Physical Data Model)
Component: SasDb version 11.0.0

This bridge imports SAS Database metadata.

The bridge reads the definition of Libraries and Tables from an SPK package file.
The file may contain multiple libraries of different engine types, implemented on multiple servers.
Thus you must specify the Library Engine to use and which server you wish to import from.

Please work with your SAS administrator to generate the required SPK file which must contain the proper Libraries, Servers, and Tables you wish to import.


Refer to the current general known limitations at or bundled in Documentation/ReadMe/MIMBKnownLimitations.html

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)

Bridge Parameters

Parameter Name Description Type Values Default Scope
File The SPK file to import from.

To create a SAS Package file in SAS Management Console:
1. Connect to the metadata server.
2. Select the Folders tab.
3. Right-click the SAS Folders node, and click 'Export SAS Package'.
4. Enable the option 'Include dependent objects when retrieving initial collection of objects'.
5. Follow the wizard screens to select folders and objects of interest and create the SPK file.

To create .SPK file with physical tables, etc. you may check "Include dependent objects when retrieving initial collection of objects" option while exporting the SAS package.

Make sure to include the following objects required by your selection:
- Libraries
- Servers
- Connections

You can also use the ExportPackage command line utility to generate the SPK file.
See this page for details:
FILE *.spk   Mandatory
Library Engine Specify the library engine to import.

The supported engine types are:
BASE engine

Analytic engine (SASIOLA in-memory engine for input-output with LASR)

For other types of engines (ORACLE, TERADATA), connecting to the source database directly is recommended.
Server The SPK package file may contain multiple libraries of different engine types, implemented on multiple servers.
Specify the server where the libraries you wish to import from are deployed.
The value should match a 'ServerContext' or 'SASClientConnection' in the SPK file.
You can browse this parameter to select a server available in the SPK file.


Bridge Mapping

Mapping information is not available

Last updated on Mon, 12 Apr 2021 17:37:38

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