When you configure the erwin Data Modeler File catalog source, you define the settings for the metadata extraction capability.
The metadata extraction capability extracts source metadata from external source systems.
You can save the catalog source configuration at any point after you enter the connection information. After you save the catalog source, you can choose to run the catalog source job. To run the job once, click Run. To run metadata extraction and other capabilities on a recurring schedule, configure schedules on the Schedule tab.
Configure metadata extraction
When you configure the erwin Data Modeler File catalog source, you choose a runtime environment and enter configuration parameters for metadata extraction.
Before you configure metadata extraction, install the Secure Agent on the same Windows machine where you installed the erwin Data Modeler File software.
1In the Connection and Runtime area, choose a serverless runtime environment or the Secure Agent group where you want to run catalog source jobs.
Note:
Serverless runtime environment options are available if the catalog source works with a serverless runtime environment.
2Choose to retain, delete, or deprecate objects that are deleted from the source system in the catalog with the Metadata Change Option.
- Retain. Retains objects that are deleted from the source system in the catalog. If you update or add a filter, the catalog retains objects extracted from the previous job and extracts additional objects that match the current filter. Objects deleted from the source system are not deleted from the catalog. Enrichments added on deleted objects and relationships are retained.
- Delete. Deletes metadata from the catalog based on objects deleted from the source system and changes you make to the filter. Enrichments added on deleted objects and relationships are also permanently lost. Objects renamed in the source system are removed and recreated in the catalog.
- Deprecate. The lifecycle of objects imported into the catalog moves to Obsolete based on objects deleted from the source system and changes you make to the filter. This does not impact enrichments added on deprecated objects and relationships. Objects renamed in the source system are removed and recreated in the catalog. When you run the catalog source job again for other capabilities such as data classification, relationship discovery, or glossary association, the job doesn't consider obsolete objects. Obsolete objects remain in the catalog until they are purged when you run a Purge Obsolete Objects job on the Explore page.
Note:
You can also change the configured metadata change option when you run a catalog source.
3In the Configuration Parameters area, enter configuration parameters.
The following table describes the properties that you need to enter:
Property
Description
Import UDPs
Specify how to import property definitions and values. A user-defined property (UDP) is usually defined with a property definition object that has a default value.
Import Relationship Name
Specifies how to import relationship names from erwin Data Modeler. Choose one of the following options:
- From relationship name
- From derived name
Import Column Order From
Specifies how to import the position of columns in tables. Choose one of the following options:
- Physical order
- Column order
Import Owner Schemas
Determines whether to import owner schemas. Import owner schemas to preserve the original ownership information from the source database in the data analysis. Select 'True' to import owner schemas. Select 'False' if you don't want to import owner schemas.
Move Entities to Subject Areas
Select 'True' if you want subject areas to be used as conventional UML design packages with corresponding namespaces. If entities belong to a single subject area, they are placed in the corresponding package. Other entities are placed in the model. Select 'False' if you don't want to move the entities to the subject areas .
Miscellaneous Options
Enter a value for additional extraction runtime options. For example:
- To allocate 4 GB of memory to the metadata extraction process, enter: -java.memory 4G
- To clear the cache before metadata extraction, enter: -cache.clear