Overview
Once a catalog source is created and capabilities are enabled/configured, users can start a scan (outside of Metadata Command Center) on a catalog source via API call specifying the required capabilities.
Pre-Requisites
- Knowledge on: Metadata Command Center, Catalog source capability configuration, API client like Postman
- The catalog source should already be created, and the required capabilities must be enabled in Metadata Command Center
Self-Service Resources
Goals
- To run a scan (outside of Metadata Command Center) on a catalog source with required capabilities via API using an API client.
Outcome
- Start the scan for required capabilities on a catalog source and get the ‘Job ID’ and ‘Tracking URI’ as response.
Required Roles/Personas
- Governance Administrator
- By default, a user with this role will have ‘Create’, ‘Read’, ‘Update’, ‘Delete’, ‘Run’ and ‘Set Permission’ on ‘Catalog Source Configuration’ asset for ‘Metadata Command Center’ service.
- By default, a user with this role will have ‘Create’, ‘Read’, ‘Update’, ‘Delete’, ‘Run’ and ‘Set Permission’ on ‘Catalog Source Configuration’ asset for ‘Metadata Command Center’ service.
- ‘Read’ and ‘Run’ permission on the catalog source.
- Users can customize the permission on a catalog source. Hence, make sure there are not any permission restriction on the catalog source on which you are going to run a scan.
- Users can customize the permission on a catalog source. Hence, make sure there are not any permission restriction on the catalog source on which you are going to run a scan.
Engagement Details
Catalog Type
Ask An Expert
Engagement Category
Feature Clarity
Products
Cloud Data Governance and Catalog
Engagement Type
Ask An Expert
Adoption Stage
Configure
Implement
Optimize
Focus Area
Adoption - Technical
Functional
Engagement ID
AAE-CDGC-005
Disclaimer
- All the topics covered in the Success Accelerators/Ask An Expert sessions are intended for guidance and advisory only. This is implicit and it will not be called out under the scope of each engagement.
- Customers need to include their relevant technical/business team members highlighted in each engagement topic to derive the best out of each engagement.
- Customers need to perform any hands-on work by themselves leveraging the guidance from these engagements.
- Customers need to work with Informatica Global Customer Support for any product bugs/issues and troubleshooting.