Swagger API Sources > Create catalog sources in Metadata Command Center > Step 2. Configure capabilities

Step 2. Configure capabilities

When you configure the Swagger API 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 Swagger API catalog source, you choose a runtime environment, define filters, and enter configuration parameters for metadata extraction.

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 Filters area, define one or more filters for metadata extraction:

aSelect Yes to view filter options.
bFrom the Include/Exclude list, choose to include or exclude metadata based on the filter parameters.
cIn the value field, enter the title attribute value.

Filter values can contain wildcards. Use a question mark to represent a single character and an asterisk to represent multiple characters.

For example: *Data includes or excludes metadata from all JSON files with title attribute values that end with 'Data.'

The following image shows the filter condition options with a sample filter value entered: The Filters area for the Swagger API catalog source includes a text field to enter attribute values.

The Filters area for the Swagger API catalog source includes a text field to enter attribute values.

To include or exclude multiple objects, click the Add icon to add filters with the OR condition.

4Optional. In the Configuration Parameters area, enter expert parameters.

Click Show Advanced to view expert parameters.

Note:

Use expert parameters when it is recommended by Informatica Global Customer Support.

5Click Next.

The Associations page appears.