erwin Data Intelligence Implementation Guide: Deployment and Advanced Configuration 

Estructura tridimensional de metadatos y linaje para la guía de erwin Data Intelligence en Bidatia.
Do you manage complex infrastructures and regulated environments? Discover our guide to erwin Data Intelligence. We analyze the optimization of Apache Tomcat, the automation of complex lineage through scripts, and the extension of the metamodel we apply at Bidatia.

For large organizations operating in highly regulated environments, Data Governance is a legal compliance requirement. When faced with complex infrastructures with thousands of legacy tables (legacy), generic solutions fall short. For this reason, having a guide to erwin Data Intelligence (erwin DI) by Quest is fundamental. This leading platform unifies the catalog and business processes in local and multicloud.

Unlike catalogs based on superficial scans, erwin DI unifies the Data Catalog and the Data Literacy in a robust suite that connects physical data modeling with business processes. 

At Bidatia we tackle these projects from a purely technical perspective. In this guide, we detail the critical aspects of your deployment, metadata configuration e advanced integration via APIs. 

1. Architecture and Deployment in the erwin Data Intelligence Guide

The Erwin DI suite is based on a three-tier architecture.3-tier) which requires precise sizing to support millions of metadata assets: 

  • Presentation Cover Browser-accessible user interface (UI) via HTTPS. 
  • Application Layer Apache Tomcat-based application server that processes governance logic. 
  • Repository Layer Relational database (SQL Server, Oracle, or PostgreSQL) that hosts the governance graph. 
Diagrama de arquitectura de tres capas y flujo de metadatos en erwin Data Intelligence.

At Bidatia We optimized the deployment on the application layer by configuring Tomcat on Linux instances. We adjusted the Java Virtual Machine (JVM) parameters, allocating a minimum of Xms8g -Xmx16g, and enabled the G1 Garbage Collector (-XX:+UseG1GC) to prevent interface latencies during massive data scans. 

2. Automation of metadata ingestion and complex lineage 

The true heart of erwin DI is its module Metadata Manager. The approach of Bidatia consists of structuring intake through standard (SDCs) and advanced connectorsSmart Data Connectors). 

Environment Scan Configuration 

To connect repositories like Snowflake, Databricks, or traditional systems, we execute two critical steps: 

  1. JDBC Drivers: We uploaded the JAR files to Tomcat and encrypted the credentials in the Credential Manager by AES with 256 bits. 
  1. Intake Filters We inject regular expressions (Regex) to ignore temporary tables (TMP_*) or test environments, strictly capturing production structures. 

Automatic extraction of data lineage 

erwin DI is notable for its ability to analyze SQL statements and stored procedures.Stored Procedures) to map the data flow. We configure its computing engine (Parsing Engine) to read specific dialects (PL/SQL, T-SQL) and handle dynamic transformations using structured configuration files (XML/JSON). 

3. Advanced Customization in the erwin Data Intelligence Guide

Erwin DI presents a robust REST API that allows it to be integrated into development workflows (CI/CD) and customize the platform to adapt it to business needs. 

Metamodel Modification (Extended Properties) 

In Bidatia, we extend the native metamodel by adding User-Defined Properties (UDPs) at the table and column level. If your organization needs to audit criticality under regulations like GDPR or the DORA operational resilience law, we inject these fields and dropdown lists directly into the interface. 

Workflow automation 

To avoid manual documentation, we developed scripts in Python or Java that consume the erwin DI API for key tasks: 

  • Glossary Synchronization: High volume, automated upload of new business terms approved by the data committee. 
  • External Lineage Injection Connection with proprietary development tools, transforming your dependencies into JSON structures to send them to the erwin API, ensuring full traceability. 

Critical Factors in erwin DI Projects: Bidatia's Experience 

The robustness of erwin DI requires strict governance of the system itself. In our implementations, we define two essential best practices: 

  • Metadata Lifecycle Management We set up environment versioning (Environment VersioningWhen production changes, we freeze the previous version in the catalog to maintain historical lineage auditing. 
  • Search Optimization We adjusted the overnight indexing parameters to ensure that business queries in the module Data Literacy they take less than a second. 

Conclusion to the erwin Data Intelligence Guide: Engineering and Business

This platform cannot be deployed by clicking «next.». On the contrary, requires a team with deep knowledge of systems administration, database optimization, and API development. Therefore, only then will its true corporate potential be unleashed.

At Bidatia We are specialists in mastering the most complex aspects of erwin DI to protect your data assets and accelerate your regulatory compliance. 

Share news in:
You may be interested in
en_US