Meta Integration® Support

Table of Contents

STEP 1 - Documentation, Tooltips, Specifications, News

• MIMB Supported Tools
• MIMB Known Limitations
• MIMB README Versions
• MIMB Third Party LICENSES
• MIMM README Versions

STEP 2 - MIMB Log Analysis

In case of claims of regression with a newer version of a bridge (new patch and major release) such as the bridge is slower or has new warnings or consistency errors, etc., it is important that 1st level support makes sure the customer is not "comparing apples and oranges" with the following 7 classic 1st level support obligations based on MIMB log analysis.

We now provide an MIMB-LogAnalyzer (,bat or .sh) utility in your install home directory

• Copy the latest cumulative patch of either (or both) 10.1.0 and 11.0.0:
  • MIMB-OEM-CumulativePatch-1010-20220505-1633.zip
  • MIMB-OEM-CumulativePatch-1100-20220505-1633.zip
• copy your MIMB log file:
  • log.txt
• Run the MIMB log analyzer utility (do -help for command line options):
  • MIMB-LogAnalyzer.bat
• Analyze the produced summary file (note any new version of libraries at the end, and any other classic issues like clear cache missing as expressed below):
  • summary.csv

1 - Different Bridge Import Scope with Full vs Incremental harvesting

Different bridge import scope with full vs incremental harvesting especially for multi-model (see below). The fair way to start is to compare both full harvesting understanding that it happens only once and does not reflect the daily incremental harvesting which is dramatically faster if there are little changes. Now comparing incremental harvesting is hard as it depends on changes of the metadata sources.

Action: Compare the Miscellaneous parameters between logs.

2 - Different Bridge Import Mode with Single vs Multi-Model

Different bridge import mode with Single vs Multi-Model especially for databases, this is related to the incremental harvesting capabilities.

Action: Compare the Miscellaneous parameters between logs.

3 - Different Bridge Import Parameters

Different bridge import parameters which will affect the imported metadata.

Action: Compare all bridge parameters between logs such as URL (dev vs prod), schema, include and exclude filters, etc.

4 - Different Bridge Resources

Different bridge resources such as CPU, memory, OS user, and network connectivity to the source metadata

Action: Compare the Miscellaneous parameters and java environment between logs. For the record, the only fair comparison is by running the new version of the harvesting agent on the same machine but a different port.

5 - Different Source Metadata Dates

Different source metadata comparing an old import of the previous version version of the bridge, with a brand new import with the new version of the bridge while the source metadata has changed a lot (e.g. new schema, tables, etc.).

Action: Compare the import date in the logs and require customers to run a fresh new import of the previous bridge version (just before or after) running the new import bridge version

6 - Different Bridge Patch Level Dates

Different bridge patch levels not having applied the current patch level on both the old version (e.g. 10.1) import and the new version import (11.0).

Action: Compare the dates of the libraries (.jar or .dll) in the logs vs the latest cumulative patch (zip)

7 - Different Bridge Specifications

Different bridge specifications / capabilities as with any new version (or even patch) the bridge are on continuous improvements extracting more metadata, parsing more expressions, etc. which can lead to more warnings or consistency check feedback.

Action: Check these new warnings, errors or consistency check results to analyze if they are actually valid.

STEP 3 - Customer Support Knowledge Base (CSKB)

• Google Shared Drive

STEP 4 - Customer Issue Tracking System (CITS)

• NEW Cloud JIRA Dashboard See Google login instructions.

Meta Integration 2nd Level Support - Rules of Engagement Per OEM agreement

1 - Customer's First Level Support Access

OEM partners must request their customers to contact their 1st level support rather than contacting MITI directly.

2 - Partner's Centralized Second Level Support

OEM partners must centralize their first level support for MITI products to a small team of MITI software experts (known as the OEM partner's centralized MITI second level support), rather than having anyone worldwide in first level support, pre-sales, or professional services creating second level technical support tickets to MITI. In fact, even the OEM partner's development and QA team should also go through the OEM partner's centralized second level support expert in MITI products, rather than filling tickets directly.

3 -First Level Support Obligations

OEM partners must:

1. Check the errors or warnings messages in the log in debug mode for details (e.g. missing client/SDK, missing ETL/DI runtime parameters, etc.)
2. Check the bridge documentation (tooltip) for the overall bridge (including FAQ and requirements such as SDK), and for each parameter of the bridge
3. Apply the current cumulative patch (bug fixes and enhancements are delivered at least once a week)
4. Check access rights as many issues in database, DI and BI harvesting are due to insufficient security privileges (if test fails, try a full import to get more details)
5. Perform a full harvest (instead of incremental harvesting), especially after installing a new version (or cumulative patch)
6. Request all input files (e.g. many DI/ETL bridges require additional run time parameter files)
7. Request proof of valid input (e.g. operational running DI jobs, BI reports, SQL script, etc.)
8. Request native formats (e.g. in case of Erwin, require the original .erwin in addition to the exported XML)
9. Try to restore the database backup in house (DM/DI/BI repository backup sometimes passwords are required)
10. Try to reproduce in house as many import bridges do not require access to the original tool/SDK client such as XML based bridges for Erwin or Informatica, or for bridges on common databases and open source software like Apache.

4 - Second Level Support New Ticket Creation

OEM partners must:

1. Project: OEM.Vendor.Tool (VENDORTOOL)
2. Type: Defect, New Feature, Improvement, Task, Usage, License Request
         Defect - A problem which impairs of prevents the functions of the product
         New Feature - A new feature of the produce which has yet to be developed
         Improvement - An improvement of enhancement to an existing feature or process
         Task - A task which needs to be done that is not one of the other Types
         Usage - Questions related to regular usage of the product
         License Request - Request for a license
3. Priority: Blocker, Critical, Major, Minor, Trivial
4. Summary: MIMM or MIMB topic / details @ Customer Name / Prospect name as follows:
          - explain unknown acronyms. e.g. Advanced Boring Company (ABC)
          - add country name after dash if necessary, e.g. ABC - Afghanistan
          - specify if it is a PoC instead of a customer by appending (PoC)
          @ Advanced Boring Company (ABC) - Afghanistan (PoC)
         
         MIMM metadata management issues:
               "MM / Glossary / Term Editing @ ABC"
               "MM / Manage / Users / Authentication / oAuth / fails to connect @ ABC"
               "MM / REST API / Repository / Browse @ ABC"
         
         MIMB metadata harvesting issues:
               "Erwin DM import / COM API @ ABC"
               "Talend DI import / Run time parameters @ ABC"
         
               UI / Fix...
               Literals / Updates for typos
               SDK / MIR Profiler /
               SDK / MIMB OEM /
               Third Party Software / Download from Maven /
               Third Party Software / Apache Log4J / Security Vulnerability / Upgraded to the latest to fix CVE...
               Security Vulnerability / Static Application Security Testing (SAST) /
               Any import / Miscellaneous parameter / Model Import Options /
               Any import / Miscellaneous parameter / Data Connection Options /
               Any Java bridge / Miscellaneous parameter / Java Environment Options /
               
               Any Database JDBC import / Miscellaneous parameter /
               Any Database JDBC import / Data Profiling /
               Any Database JDBC import / Data Sampling /
               Any Database SQL DDL import/
               Any Database SQL DML Script import /
               Any File System import / Miscellaneous parameter /
               Any File System import / Data Profiling /
               Any File System import / Data Sampling /
               Amazon S3 import /
               Amazon RedShift JDBC import /
               Amazon Aurora / Oracle MySQL import /
               Amazon Athena / Database JDBC import /
               Amazon Glue ETL / Apache Spark import /
               Apache Atlas import /
               Apache Avro import /
               Apache Cassandra Database import /
               Apache Kafka import /
               Apache Parquet import /
               Cloudera Navigator import /
               Confluent Kafka import /
               Data Integration (DI/ETL) import /
               Database DDL import /
               Database JDBC import / Specific database /
               Databricks import /
               Erwin DM export /
               Erwin DM import /
               Erwin DM import / Mart /
               File System import /
               Google BigQuery import /
               Greenplum JDBC import / Error 'Data profiling samples loading failed...'
               Hadoop HDFS import /
               Hadoop Hive DDL import /
               Hadoop Hive DML import /
               Hadoop Hive JDBC import /
               Hadoop Hive JDBC import / Amazon EMR /
               Hadoop Hive JDBC import / Cloudera /
               Hadoop Hive JDBC import / Hortonworks /
               HP Vertica / Database JDBC import /
               IBM Cognos Framework Manager (FM) import /
               IBM Cognos import / Content Manager /
               IBM DataStage import /
               IBM DB2 UDB DML import /
               IBM DB2 UDB JDBC import /
               IBM DB2 iSeries (AS/400) / Database JDBC import /
               IBM DB2 for z/OS (mainframe) / Database JDBC import /
               IBM IGC (via IIS) export /
               IBM IGC (via Open IGC) export /
               IBM Informix JDBC import /
               IBM InfoSphere Data Architect (IDA) import /
               IDERA ER/Studio import /
               Informatica PowerCenter export /
               Informatica PowerCenter import /
               Informatica PowerCenter import / Repository /
               JSON import /
               Metadata Excel Format import /
               Microsoft Azure Blob Storage import /
               Microsoft Azure Cosmos DB NoSQL import /
               Microsoft Azure Data Lake Storage import /
               Microsoft Azure Data Factory import /
               Microsoft Azure Purview import /
               Microsoft Azure Synapse Analytics import /
               Microsoft Azure SQL Database import /
               Microsoft Excel File import /
               Microsoft Power BI File import /
               Microsoft Power BI Repository Server import /
               Microsoft Azure Power BI Service import /
               Microsoft SQL Server DDL import /
               Microsoft SQL Server DML import /
               Microsoft SQL Server JDBC import /
               Microsoft SSAS import /
               Microsoft SSAS/SSRS import /
               Microsoft SSIS import /
               Microsoft SSRS import /
               MicroStrategy import / should fetch all Project Connections (not only Default Connection)
               NoMagic MagicDraw (via UML 2.x XMI) import /
               OMG CWM XMI import /
               Oracle DML import /
               Oracle JDBC import /
               Oracle MySQL JDBC import /
               Oracle OBIEE import /
               Oracle ODI import /
               Positional File import /
               PostgreSQL DML import /
               QlikSense import /
               QlikView import /
               SAP BusinessObjects import /
               SAP BW import /
               SAP S/4HANA / ECC import /
               SAP HANA import /
               SAP PowerDesigner PDM import /
               SAP Sybase ASE Database JDBC import /
               SAS DI import /
               Snowflake JDBC import /
               Tableau import /
               Talend Data Prep import /
               Talend DI export /
               Talend DI import /
               Teradata DDL import /
               Teradata DML import / BTEQ /
               Teradata DML import / TPT /
               Teradata JDBC import /
               ThoughtSpot import /
               TIBCO Spotfire import / DXP Format /
               TIBCO Spotfire import / Repository /
               W3C WSDL import /
               W3C XML import /
               W3C XSD import /
         
         Popular MIMM Ticket Summary prefix topics are:
               MM / Security Vulnerability /
               MM / Third Party Software / Apache Tomcat / Security Vulnerability / Upgraded to the latest to fix CVE./..
               MM / Third Party Software / PostgreSQL / Upgraded to the latest to improve performance
               MM/ Security Vulnerability / Static Application Security Testing (SAST) /
               
               MM / Deployment / Setup /
               MM / Deployment / Restart/
               MM / Deployment / Upgrade /
               MM / Server / Repository / Oracle /
               MM / Server / Repository / PostgreSQL /
               MM / Server / Repository / SQL Server /
               
               MM / Manage / Users / Authentication / LDAP /
               MM / Manage / Users / Authentication / OAuth /
               MM / Manage / Users / Authentication / SAML /
               MM / Manage / Users / Authentication / LDAP /
               MM / Manage / Groups /
               MM / Manage / Global Roles /
               MM / Manage / Object Roles /
               MM / Manage / Operations /
               MM / Manage / Schedules /
               MM / Manage / Servers
               MM / Manage / Secret Vaults /
               MM / Manage / Email
               MM / Manage / Metamodel
               MM / Manage / Labels /
               MM / Manage / Conditional Labels /
               MM / Manage / Sensitivity Labels /
               MM / Manage / Data Classes /
               MM / Manage / Global Roles /
               MM / Manage / License /
               MM / Manage / System /
               
               MM / Manage / Repository / Backup /
               
               MM / Manage / Configuration / Stitching / Model Management /
               MM / Manage / Configuration / Stitching / Report /
               MM / Manage / Configuration / Build /
               MM / Manage / Configuration / Architecture Diagram /
               
               MM / Manage / Model / Import / Remote Server /
               MM / Manage / Model / Import / Setup
               MM / Manage / Model / Documentation / Bulk Update via CSV Export/Re-Import
               
               MM / Object / Search /
               MM / Object / Explore /
               MM / Object / Overview /
               MM / MQL /
               MM / REST API /
               MM / Collections /
               MM / Worksheets /
               MM / Dashboards /
               
               MM / Glossary / Import/Export /
               MM / Glossary / Relationships /
               MM / Glossary / Workflow /
               MM / Custom Model /
               MM / Data Mapping /
               MM / Semantic Mapping
               MM / Physical Data Model /
               
               MM / Semantic Flow / Definition /
               MM / Data Flow / Lineage / Overview /
               MM / Data Model / Diagram /
               MM / Data Sampling /
               MM / Data Profiling /
               MM / Curation / Endorsement /
               MM / Security / Access Rights /
               
               MM / UI / Login /
               MM / UI / Configuration Selector /
               MM / UI / Header /
5. Import Bridge: Erwin 9.x Mart, and Tool Version 8.1.2
6. Export Bridge: Vendor X Tool Y, and Tool Version 10.11.12
7. Attachments: must include the full log (with debug messages), the source metadata to reproduce (e.g. model.erwin), full browser snapshots (no cropping), short step by step videos (no full meeting video), documents describing how to reproduce step by step.
8. Description: must include step by step details to reproduce, and proper references to attachments.
9. Affects Version: 10.0.0
10. Fix Version: 10.0.1 and 10.0.0
11. Partner Issue ID: 12345678
12. Issue Context: Customer Production, Customer PoC, Partner QA or Partner Development.
13. Customer: Company Name (only if a real customer issue)
14. Reporter: Full Name (mandatory), Email (mandatory), phone is optional

5 - Second Level Support Existing Ticket Follow Up

OEM partners must:

1. Sign any posting (with your first and last Name at the end of any posting) as multiple people are involved and contributing on any ticket from a given OEM partner account (login).
2. Click on "Submit Information" after providing any new information (comments or uploaded files) on "Investigating" or "Resolving" tickets, so that this ticket goes back to MITI's second level support queue. This happens when further details from the customer become available that would help the investigation or the resolution.
3. Click on "Submit Response" after providing the requested information (comments or uploaded files) on "Waiting for Information" tickets, so that this ticket goes back to MITI's second level support queue.
4. Click on "Verify" to acknowledge reception of MITI's provided solution, work around or cumulative patch. A Comment is required to explain if the solution was actually tested and verified in house, or just passed to the customer for further verification. Remember that "Verify" does not necessarily means that the customer confirmed that the solution worked (Note that customers usually only get back when it does not work, in such case you can re-open the ticket as explained below).
5. Click on "Open" for any other status so that this ticket goes back to MITI's second level support queue, including while MITI is investigating or resolving to request a status update / ETA, or provide more input to resolve the issue. You can also re-open the ticket if MITI's provided solution, work around or cumulative patch did not fix the ORIGINAL issue, which can happen immediately upon your in house testing of "Resolved" tickets, or much later on "Closed" tickets after the customer's testing/feedback. In all cases, a new updated full log showing proper application of the cumulative is required, as well as all details of the problems. WARNING, do NOT re-open the ticket if the problem does not exactly match the original ticket, even if this is the same customer and the same bridge, instead confirm the original is fixed by marking the ticket as "Verified" and open a new related ticket for the follow up issue (e.g. different syntax error, or different access right issues).

Meta Integration 2nd Level Support - Patches

WARNING: Important disclaimer about patches:

1. PATCHES CANNOT BE USED FOR VERSION UPGRADE:
   Patches can only be used within a given version (e.g. 10.1.0), but cannot be used for a version upgrade (e.g. from 10.0.1 to 10.1). Fore more information about the latest version, read the MIMB release changes, and MIMM release changes. Therefore, the deployment of any new version must start from a full clean install of that version, and then apply the latest cumulative patch of that version. In case of MIMM, read the Server Upgrade instructions.
2. ALL PATCHES ARE CUMULATIVE:
   No individual patch fixing an individual issue is released, instead only fully integrated cumulative patches are released.
3. PATCHES DO NOT COVER TOMCAT OR POSGRESQL:
   The MIMM Cumulative patches do not include any update (even for security vulnerabilities) to the Apache Tomcat Web application server and PostgreSQL database server. Such updates (and new versions) are only available in the full build)
4. PATCHES FOR OLDER VERSIONS ARE LIMITED:
   It is our plan to go on releasing cumulative patches and full builds of MIMM as needed on regular basis for 10.1.0. However when 11.0 is GA, we will only release MIMB cumulative patches (upon automated regression testing certification) on weekly basis (as needed). The MIMM cumulative patches and full builds will be released only on monthly basis as they require a lot more manual regression testing certification. Nevertheless, in case of a critical bug, MIMM cumulative patch and builds may be released if needed.

The following cumulative patches contain all changes since the last GA 1001-20200131 are available on the Google drive at:

• Shared with me > MIMB > MIMB-OEM > 10.1.0 > MIMB-OEM-CumulativePatch-1010-YYYYMMDD.zip
  contains only bridges (and their profiles)
  for all MIMB and MIMM OEM partners.
• Shared with me > MIMM > Software > 10.1.0 > MIMM-CumulativePatch-1010-YYYYMMDD.zip
  contains only the MM application server / UI (no bridges)
  for all MIMM OEM partners.
• Shared with me > MIMB > MIMB > 10.1.0 > MIMB-CumulativePatch-1010-YYYYMMDD.zip
  contains only the MIMB application server / UI (no bridges)
  for all OEM partners, but only when needed for support.

Note that these cumulative patches are Meta Integration partner neutral and therefore do NOT contain any partner customization or documentation including:

• For MIMB OEM partner's tools:
  • conf\ModelBridgeList.xml for custom list of supported bridges can be downloaded from on the Google drive at:
    Shared with me > MIMB-conf-VendorNameToolName > MIMB-Version \ conf > ModelBridgeList.xml and ModelBridgeR-EADME.txt which explains how to integrate a new MIMB OEM
• For MIMM OEM partner's tools:
  • conf\ModelBridgeList.xml (and conf\Template\ModelBridgeList.xml) - for custom list of supported bridges
  • conf\literals\ - for custom literals in different languages
  • conf\resources\ (and conf\Template\resources\) - for custom UI look & feel, and home pages, etc.
  • conf\resources\help - for online help / user guide
  • Documentation\ReadMe\ - for installation and setup instructions
  • Documentation\License\ - for third party software disclaimers
  • tomcat\conf\tomcat.properties - for custom default ports
  • Metadata Management URL start shortcut - for custom default ports

If a fix needs any of these above files, the necessary files can easily be extracted from the following full builds on the Google drive at:

• Shared with me > MIMM > Software > 10.1.0 > MIMM-1010-YYYYMMDD.zip (and .tbz2)
• Shared with me > xMM > Software > xMMy.z.-10.1.0 > xMMy.z-YYYYMMDD.zip (and .tbz2)

Meta Integration 2nd Level Support - Customer Environment Information

• Sign in to MIMM as a user with the Administrator security role:
• Go to MANAGE > System
  • Take a snapshot, or click Download (top right) to obtain a TXT file of the application and database server Information)
  • Click Scripts (top left) > Get repository content statistics (run script and save log)
  • Click Scripts (top left) > Get repository configuration statistics (run script and save log)
  • Click Scripts (top left) > Test performance (run script and save log)
• Go to MANAGE > Servers
  • Take a snapshot
• Go to the MANAGE > Schedule
  • Select the script (top panel) Run Database Maintenance
  • Select the latest execution in the History (bottom panel) and click View Log (on the right)
  • In the Log Messages dialog, click on show All (bottom), and Save
• Go to the Metadata Explorer UI and for each large configuration, go to BROWSE > Statistics in the banner and Download (top left) the CSV file of the configuration statistics.