Manage system calls, drivers, and plugins

Under System Management > Data Source Management, calls record system relationships, drivers connect databases, and plugins provide integration, reverse engineering, and parsing. Plugins are direct harvesting prerequisites.

Register system calls

1. Open System Calls > New.
2. Enter caller, callee, and relationship information.
3. Verify source/database, resource, reference method, and function description.
4. Save, search, and check direction.

Search by source/database, resource, and description; lists show caller/callee and recording users. Manual relationships do not replace SQL/ETL lineage. Edit/delete after verification. For bulk registration, download the template, Import Calls, and sample direction afterward.

Add drivers

1. Select the database type in Driver Management.
2. Upload an approved compatible driver.
3. Verify it appears under the correct type.
4. Set the default driver.
5. Create/test a source and verify initialization.

Defaults initialize new sources; existing sources do not necessarily switch.

Replace or delete

Referenced drivers cannot be deleted. Migrate dependent sources and test first. Use approved packages and Compatibility; supported types do not validate every driver combination.

Understand plugin types

Type	Responsibility
Source	Source types, forms, connections
Reverse engineering	Convert structures into tables, columns, views, routines, or metamodel objects
Lineage parser	Extract SQL/ETL/BI processing relationships

JDBC drivers do not add source types or complete reverse engineering/parsing.

Upload and validate

1. Open Plugin Management and choose type.
2. Upload the matching file.
3. Verify name/type/state.
4. Test source creation/connections for source plugins.
5. Test limited harvesting and properties for reverse engineering plugins.
6. Test known parsing, node matching, and dependencies for parsers.

Source packages may contain multiple components, but source/reverse engineering types remain separate. Reupload can replace a plugin; installed plugins normally cannot be deleted directly. Have delivery/development teams retain previous versions, dependency lists, and verification records.

Troubleshoot

Symptom	Check
Driver exists, type missing	Source plugin
Connected, objects missing	Reverse engineering compatibility, rights, schemas, logs
Metadata exists, parsing fails	Parser, format, engine, namespace
Driver deletion blocked	Source references
Calls differ from lineage	Separate manual relationship and parsed evidence/history