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

MIMB Bridge Documentation

MIMB Import Bridge from SAP HANA Database (via JDBC)

Bridge Specifications

Vendor SAP
Tool Name SAP HANA Database
Tool Version 15
Tool Web Site http://www.sap.com/pc/tech/database/software/adaptive-server-enterprise/index.html
Supported Methodology [Database] Data Store (Physical Data Model, Stored Procedure Expression Parsing) via JDBC API

Import tool: SAP SAP HANA Database 15 (http://www.sap.com/pc/tech/database/software/adaptive-server-enterprise/index.html)
Import interface: [Database] Data Store (Physical Data Model, Stored Procedure Expression Parsing) via JDBC API from SAP HANA Database (via JDBC)
Import bridge: 'JdbcSAPHana' 10.0.1

IMPORTING FROM A SAP HANA DATABASE USING JDBC.

This bridge establishes a JDBC connection with a physical SAP Hana database in order to extract the physical metadata. It is critical that the parameters are filled correctly in order to satisfy the local connection requirements on the client workstation that runs the bridge. Please refer to the individual parameter's tool tips for more detailed examples.

Note about permissions:
The username specified must have the permission to select metadata of schemas imported.
CREATE USER user1 PASSWORD password1 NO FORCE_FIRST_PASSWORD_CHANGE;
GRANT SELECT METADATA ON SCHEMA schema1 TO user1;
GRANT SELECT METADATA ON SCHEMA schema2 TO user1;
Also the username specified must have the permission to select on system table _SYS_REPO.ACTIVE_OBJECT and on system schemas _SYS_BI and _SYS_BIC.
GRANT SELECT ON _SYS_REPO.ACTIVE_OBJECT TO user1;
GRANT SELECT ON SCHEMA _SYS_BI TO user1;
GRANT SELECT ON SCHEMA _SYS_BIC TO user1;


This bridge will connect to the sys tables which exists in SAP Hana environment when importing metadata.

Driver details:
- driver name: SAP (com.sap.db.jdbc.Driver)
- driver version 2.2.33.1510080117
- file: ngdbc.jar (788,596 bytes)
- file location: ${MODEL_BRIDGE_HOME}/java/Jdbc/SapHana


Bridge Parameters

Parameter Name Description Type Values Default Scope
Driver location
This parameter is optional.

By default, all necessary JARs will be loaded from:
'${MODEL_BRIDGE_HOME}/java/Jdbc/SapHana'

However, you may use this parameter to specify a different location. All JARs found in the specified folder will be added to the CLASSPATH.

The 'com.sap.db.jdbc.Driver' JDBC driver with the 'SAP' name is required.
DIRECTORY      
Host Host name or IP address where SAP Hana server is running.
STRING   localhost Mandatory
Port SAP Hana server port number. Default value is 39013.
NUMERIC   39013  
Database Database instance name.
STRING     Mandatory
User The database user name on whose behalf the connection is being made.

Important note about permissions:
This bridge reads the metadata for a database, rather than the data. Hence, permission assignments need to be quite different than for a standard database user. The bridge requires access to the system tables, not the actual data tables, thus it is highly recommended that one engages their DB Admin staff to ensure proper permissions for the username entered here.

We do not have any specific instructions as to what are the minimal set of permissions required as it varies from database type to database type, as well as from version to version. In order to ensure that the bridge is working properly, one must first import using the bridge with a FULL Sys Admin type user name (all permissions), i.e., the same type of user name that is used to create and maintain the DB. Once the bridge is working properly against a give DB, then the DB Admin staff may create a user with lesser privileges that still produce a successful result.

Note, this parameter is not required. In the case of Oracle and SQL Server one can specify user credentials in the cHost bridge parameter. In addtion, many Microsoft Access databases allow one to connect without specifying user credentials.
Also, for the Microsoft SQL Server specific bridge, if this parameter is empty, then it is assumed that integrated security is being used (see http://msdn.microsoft.com/en-us/library/ms378428.aspx#Connectingintegrated). In this case, the bridge will attempt to connect with this type of signature:

jdbc:sqlserver://; integratedSecurity=true
instead of

jdbc:sqlserver://; user=userid;password=userpassword

However, in order for this to work, the user must the sqljdbc_auth.dll available on the PATH environment variable. Also the version of the library must match the version of the sqljdbc4.jar that they are using.

STRING      
Password The database user's password on whose behalf the connection is being made PASSWORD      
Schema Description: you can specify a list of database schemas to import.
When the list is empty all available schemas are imported.
The list can have one or more schema names separated by semicolons (e.g. schema1; schema2).
You can specify schema name patterns using SAP HANA SQL LIKE expressions syntax.
Patterns support inclusions and exclusions.
Here is an example of inclusion syntax, "A%; %B; %C%; D" that tries to get schema names that:
- start with A or
- end with B or
- contain C or
- equal D

Note: when a pattern has special characters, like spaces enclose it in single quote marks (e.g. "'two wo%'; onewo%;").

To exclude a pattern prefix it with NOT. Here is an example of exclusion syntax, "A%; %B; NOT %SYS; NOT 'SYS%'"
that contributes to the following SQL filter: "where (name like A% or name like %B) and (name not like %SYS) and (name not like 'SYS%')"

System schemas (that start with SYS) and all objects they have are ignored by default. To import them specify '-s' option in Miscellaneous parameter.
REPOSITORY_SUBSET      
Package Description: you can specify a list of database packages to import.
When the list is empty all available packages are imported.
The list can have one or more package names separated by semicolons (e.g. package1; package2).
You can specify subpackages using dot (e.g. package1.subpackage1_2.subsubpackage1_2_2).
If you specify a package then you import the package as well as all children subpackages.
REPOSITORY_SUBSET      
Tables, Views Description: you can specify a list of database tables to import.
When the list is empty all available tables are imported.
The list can have one or more table names separated by semicolons (e.g. table1; table2).
You can specify table name patterns using SQL LIKE expressions syntax.
Patterns support inclusions and exclusions.
Here is an example of inclusion syntax, "A%; %B; %C%; D" that tries to get table names that: - start with A or
- end with B or
- contain C or
- equal D

Note: when a pattern has special characters, like spaces enclose it in single quote marks (e.g. "'two wo%'; onewo%;").

To exclude a pattern prefix it with NOT. Here is an example of exclusion syntax, "A%; %B; NOT %SYS; NOT 'SYS%'" that
contributes to the following SQL filter: "where (name like A% or name like %B) and (name not like %SYS) and (name not like 'SYS%')"

STRING      
Stored procedure details Specify what stored procedure details you would like to include

- 'Signature' - name and parameters of stored procedures (default)
- 'Code, signature' - above plus code
- 'Lineage, code, signature' - above plus data lineage derived from the code
- 'None' - stored procedures are not included
ENUMERATED
None
Signature
Code, signature
Lineage, code, signature
Signature  
Import indexes Specifies if the Indexes should be imported or not.

- 'False' : Indexes are not imported(default)
- 'True' : Indexes are imported
BOOLEAN
False
True
False  
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -m 4G -f 100 -j -Dname=value -Xms1G

-f the database driver fetch size in number of rows (e.g. -f 100)

-zip exportFile to store DDL create tables statements (e.g -zip c:/temp/ddl/export.zip)

-m the maximum Java memory size whole number (e.g. -m 4G or -m 2500M ).
-s import system objects that are skipped by default (e.g. -s)
-v set environment variable(s) (e.g. -v var1=value -v var2="value with spaces").
-j the last option that is followed by Java command line options (e.g. -j -Dname=value -Xms1G).

-diff difference detection level (e.g. -diff ikm for disabling checking indexes, keys, classifier and feature maps)

-synonyms disable import of all synonyms

STRING      

 

Bridge Mapping

Meta Integration Repository (MIR)
Metamodel
(based on the OMG CWM standard)
"SAP HANA Database (via JDBC)"
Metamodel
Jdbc
Mapping Comments
     
Name Name  
Attribute Table Column  
Comment Comments on the column If JDBC driver supports
InitialValue Default value  
Name Name  
Optional Based on the nullable property For Access databases, set to false only if the attribute is in a Unique Index
PhysicalName Name  
Position Position If position is not provided, the order in which the attributes are retrieved is used.
BaseType Types  
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Maximum scale  
Class Table of type "TABLE"
Comment Comments on the table If JDBC driver supports
CppClassType   Set to ENTITY
CppPersistent   Set to True
Name Name  
PhysicalName Name  
ClassDiagram Schema A class diagram is created for each package and contains all the elements of the package
DerivedType Column Table column, stored procedure column SQL View column or type
DataType Data Type See datatype conversion array
Length Size  
Name   The name is computed from the datatype
PhysicalName Name  
Scale Decimal digits  
UserDefined   True for Type
DesignPackage Schema A Package is created for each retrieved schema. If there is no schema a default package is created.
Name Name Set to "Schema" if there is no schema or the schema has no name.
SQLViewAttribute View Column  
Comment Comments on the column If JDBC driver supports
Name Name  
PhysicalName Name  
Position Ordinal position  
SQLViewEntity Table of type "VIEW"
Comment Comments on the table If JDBC driver supports
Name Name  
PhysicalName Name  
StoreModel Catalog The model is built using the elements contained in the catalog (e.g. the database for MS SQL server)
Name Name Set to "Catalog" if the catalog has no name.
Synonym Table Synonym If JDBC driver supports
Name Name  

Last updated on Fri, 21 Sep 2018 16:15:06

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