Asset Management > Asset migration > Asset import

Asset import

You can import all of the assets in an export file or select the assets that you want to import.

When you import assets, you specify the following information:

•The assets in the export file that you want to import and the projects in which to import them.
•Whether to overwrite assets in the target project with assets in the export file when there is a name conflict.
•Whether to merge tags when you overwrite assets in the target project.
•The connections and runtime environments to use for the imported assets.
•Whether to publish taskflows when you import them.

To import an asset, you need the following privileges and permissions:

•Your user role must have privileges to import assets.
•If you import an asset into the target project as a new asset, you must have create, update, and read permissions on the asset.
•If you overwrite an asset in the target project, you must have update and read permissions on the asset.

Note: To overwrite a source-controlled asset in the target project, the asset must be checked out.

The target organization must have all of the required licenses for the assets being imported. For example, to import a mapping task, the target organization must have all of the licenses required for the mapping task. This includes the licenses required for the mapping on which the mapping task is based.

The Import Assets page lists the assets that are in the export file. You can select which assets you want to import, and then specify which project to import the assets to. You can accept the default project, which is the same project name as the source project, or you can select a different project. If the project does not exist in the target organization, Informatica Intelligent Cloud Services creates it.

You can publish taskflows when you import them.

Asset name conflicts

You can specify how Informatica Intelligent Cloud Services handles asset name conflicts when the export file contains assets with the same name as assets in the target project. You can choose whether to overwrite the assets in the target project or use the existing assets in the target project.

To see how the import handles any asset name conflicts before you start the import job, you can test the import on the Import Assets page before you import the assets. The import action displays in the Status column for each asset. You can filter the list of assets by asset name, asset type, or status.

The following image shows a list of assets and the import action to be performed when overwriting existing assets is enabled:

The image of the Import Asset page shows nine assets and the projects in which the assets are to be located. The Status column shows that during the import, Informatica Intelligent Cloud Services creates one of the assets because it does not exist in the target location. Informatica Intelligent Cloud Services overwrites the other assets because assets with the same name exist in the target location.

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.

Runtime environment and connection selection

If the export file contains dependent objects, the target connection and runtime environment fields show the connection and runtime environments from the export file as the default. You can accept the default or select a different connection or runtime environment.

If the export file doesn't include dependent objects and the connections or runtime environments that are used by the assets in the export file don't exist in the target organization, you must select a target connection or runtime environment.

If a suitable connection or runtime environment doesn't exist in the target organization, create it in the target organization before you import the file. For example, if you want to use a connection that uses a different end point in the target organization, create the connection that uses the end point in the target organization before you import the file. When you import the file, you can select the target connection that you created.

When you select a connection or runtime environment that exists in the target organization, the connector type and version must be the same as the connector type and version that the asset used in the source organization.

The following image shows the source connections and runtime environment and the selected target connections and runtime environment:

Importing asset tags

Asset tags are included in the export file and imported with the asset to the target project. When you overwrite existing assets, you can choose to merge tags in the target project with tags in the export file or keep only the tags in the export file.

When you import a new asset, its tags are also imported to the target project. When you overwrite existing assets in the target project, you can choose to merge tags. When you merge tags, after import, both export and target project tags are assigned to the asset.

You can choose to merge tags for all assets or for some assets in the export file. You can only merge tags when you overwrite existing assets in the target project.

If you choose to merge tags and the asset in the export file does not have tags but the asset in the target project does, after import, the asset will retain tags from the target project. To remove the target project tags, navigate to the asset on the Explore page and remove the tags.

The following table shows how Informatica Intelligent Cloud Services merges tags when you overwrite existing assets on import:

Asset name	Export file tags	Target project tags	Merge tags	Tags after import
Asset_1	Tag_1, Tag_2	Tag_3	Yes	Tag_1, Tag_2, Tag_3
Asset_2	Tag_1, Tag_2	Tag_4, Tag_5	No	Tag_1, Tag_2
Asset_3	Tag_1, Tag_2	-	Yes	Tag_1, Tag_2
Asset_4	-	Tag_5, Tag_6	Yes	Tag_5, Tag_6
Asset_5	-	Tag_5, Tag_6	No	Tag_5, Tag_6

Importing assets with persisted values

When you import a shared sequence or a mapping task that contains in-out parameters or sequences, you can choose to retain, reset, or overwrite persisted values.

The actions you can take for persisted values depends on whether or not the asset exists in the target project and if you choose to overwrite existing assets.

The following table describes the actions you can take when you import new assets or choose not to overwrite existing assets:

Setting	Description
Reset to default values	Default. Informatica Intelligent Cloud Services creates a new asset in the target location with default in-out parameter values and initial sequence values.
Retain persisted values	Informatica Intelligent Cloud Services creates a new asset with the persisted in-out parameter and sequence values .

The following table describes the actions you can take when you overwrite existing assets:

Setting	Description
Retain persisted values in the target	Default. Informatica Intelligent Cloud Services ignores values coming from the export file and retains the values persisted in the target project.
Reset persisted values to default values	Informatica Intelligent Cloud Services resets persisted values to the default in-out parameter value and initial sequence value.
Overwrite persisted values in the target with source values	Informatica Intelligent Cloud Services overwrites values in the target with persisted values in the export file.

Importing assets

Import assets from an Informatica Intelligent Cloud Services export file.

1 Log in to the target organization.

2On the Explore page, navigate to All Projects and click Import.

3On the Import Assets page, navigate to the export file and click Open, or drag the zip file from the Downloads folder in Windows.

The Import Assets page lists the assets in the file.

4Optionally, change the import job name.

5Choose whether to overwrite existing assets with the assets in the import.

- If you choose to overwrite existing assets, when an asset has the same name as an asset in the target project, the asset replaces the existing asset in the target project.
- If you do not choose this option, if an asset with the same name exists in the target project, the asset is not imported.

6Select the assets to import.

If the export file contains a project and you want to import the entire project, select all of the assets. Informatica Intelligent Cloud Services creates the project in the target organization.

7Select the target project or accept the default.

8For each source connection, select the target connection or accept the default.

9For each source runtime environment, select the target runtime environment or accept the default.

10If you want to publish taskflows when you import them, select Publish Taskflows after import.

11Click Test to see the potential results of the import.

In the Select Assets area, the status for each asset shows the action that the service performs when you import the files.

12If necessary, revise your selections to resolve any issues in the test results.

13Click Import.

You can see the progress of the import on the Import tab of the My Import/Export Logs page. When the import process is complete, a message appears in Notifications. Click the link in the message to open the log details page and see the results of the import.