You can create a profile on multiple data sources under multiple connections. The Developer tool creates individual profile tasks for each source.
1. In the Object Explorer view, select multiple data objects you want to run a profile on.
2. Click File > New > Profile to open the profile wizard.
3. Select Enterprise Discovery Profile and click Next.
4. Enter a name for the profile and verify the project location. If required, browse to a new location.
5. Verify that the name of the data objects you selected appears within the Data Objects section. Click Choose to select more data objects, if required.
6. Click Next.
The Add Resources to Profile Definition pane appears. You can select multiple, external relational connections and data sources from this pane.
7. Click Choose to open the Select Resources dialog box.
The Resources pane lists all the internal and external connections and data objects under the Informatica domain.
8. Click OK to close the dialog box.
9. Click Next.
10. Configure the profile types that you want to run. You can configure the following profile types:
- - Data domain discovery
- - Column profile
- - Primary key profile
- - Foreign key profile
Note: Select Enabled as part of "Run Enterprise Discovery Profile" action for the profile types that you want to run as part of the enterprise discovery profile. Column profiling is enabled by default.
11. Review the options for the profile.
You can edit the sampling options for column profiles. You can also edit the inference options for data domain, primary key, and foreign key profiles.
12. Select Create profiles.
The Developer tool creates profiles for each individual data source.
13. Select Run enterprise discovery profile on finish to run the profile when you complete the profile configuration. If you enabled all the profiling operations, the Developer tool runs column, data domain, and primary key profiles on all selected data sources. Then, the Developer tool runs a foreign key profile across all the data sources.
14. Click Finish.
After you run an enterprise discovery profile, you need to refresh the Model Repository Service before viewing the results. This step is required as the import of metadata for external connections happens in the Model repository. You need to refresh the Model Repository Service so that the Developer tool reflects the changes to the Model repository.