Dependent objects are assets that are required by other assets.
For example, a saved query that a mapping depends on is a dependent object. The connection and runtime environment that the mapping uses are also dependent objects.
When you set up an export, you have the option to include or exclude dependent objects in the export file. The dependent objects must exist either in the export file or in the target organization, else the import fails.
You might want to include dependent objects if they do not exist in the target organization. Or, you might want to include dependent objects if you want to replace the dependent objects in the target organization with updated versions from the source organization. If you choose to include dependent objects, the export file includes dependent objects for all of the assets that you include in the export. When you configure the import, you can choose which dependent assets to import.
You might want to exclude an asset's dependent objects if the objects exist in the target organization and you do not want to replace them.
Note: Schedules are not dependent objects and are not included when you export assets that use them.
Runtime environments and connections
Runtime environments and connections are dependent objects.
If you configure an export to include dependent objects, you can use the source connections and runtime environments in the export file, or you can select connections and runtime environments in the target organization.
If you configure an export to exclude dependent objects, be sure that a suitable connection and runtime environment for the assets exists in the target organization. If a dependent connection or runtime environment does not exist in the target organization, during the import operation you must select a connection or runtime environment in the target organization.
When you select a connection or runtime environment in the target organization during the import, the connector type and version must be the same as the connector type and version that the asset used in the source organization.
If the target organization has connections or runtime environments with the same name as those in the export file, Informatica Intelligent Cloud Services uses the connections or runtime environments that exist in the target organization. Informatica Intelligent Cloud Services does not overwrite the connections or runtime environments in the target organization.
Note: An export or import cannot include a Cloud Hosted Agent or shared agent. If an asset uses a Cloud Hosted Agent or a shared agent, you can select a runtime environment to use for the asset during import.
Dependent objects example
You want to migrate a mapping task. The mapping task depends on the following objects:
•The connection to the source object and the runtime environment used for the connection.
•The connection to the target object and the runtime environment used for the connection.
•The mapping on which the mapping task is based.
The connections, the runtime environment, and the mapping exist in the target organization. The mapping in the source organization is an updated version of the mapping in the target organization. You configure an export that includes dependent objects so that the source organization and target organization have the same version of the mapping.
When you configure the import, you specify that you want to overwrite existing assets. For connections and runtime environments, you accept the default.
During import, Informatica Intelligent Cloud Services overwrites the mapping in the target organization with the mapping from the source organization. The imported assets use the connections and runtime environments that exist in the target.