Import command for InfoSphere FastTrack assets

Use the istool import command with the -fasttrack parameter to import an archive file that contains IBM® InfoSphere® FastTrack assets.

Purpose

You import assets from an exported archive file into a different instance of InfoSphere Information Server. For example, you can transfer assets from a development environment to a production or test environment. You can also migrate assets to a newer version of InfoSphere Information Server.

You can use a single istool import command with the -all parameter to import most types of metadata assets from an archive file. See Moving all assets from one metadata repository to another.

Prerequisites

You must have the FastTrack Administrator role.

You must run the command on a computer on the client tier where InfoSphere FastTrack is installed.

The preferred way to run this command is in the istool command-line window. If you run this command in your operating system command-line window or in scripts, you must add istool before the command name.

Command syntax

Optional parameters and values in the syntax are enclosed in brackets, [ ].

import 
authentication parameters
[generic parameters] 
-abortAfter number_of_errors	
-archive file_name_and_path
[-preview |-replace]
[-responseFile "file_name_and_path"]
-fasttrack 
   '
    [-dsNamespace  server[/project]
    [-onNameConflict  [ignore | replace | rename]  ] |
    [-renameSuffix suffix]
   '

Parameters

authentication parameters

Required. All asset interchange commands use authentication parameters to connect to a specific installation of InfoSphere Information Server.

generic parameters

The generic parameters are available to all asset interchange commands. Use the generic parameters to request help on command syntax, to specify silent or verbose operation, and to use a script to run commands.

-abortAfter | -abort number_of_errors

Specifies that the import stops if more than the specified number of errors occur.

-archive | -ar file_name_and_path

Required. Specifies the .isx file to import assets from.

-preview | -pre

Previews the import. The preview lists the assets that will be imported when the import runs. The assets are not imported when you run a command with the -preview parameter.

-replace

Replaces existing common metadata assets with imported assets. If you specify the -replace parameter, and an asset with the same identity exists in the target metadata repository, the imported asset is merged with the existing asset.

-responseFile | -rf "file_name_and_path"

Specifies the name and path of a response file that contains assets that failed to import during a run of a previous istool import -ft command. Not supported with the -preview parameter. For more information, see Using a response file for istool export and istool import commands.

-fasttrack | -ft '[import-options]'

Required. Specifies that InfoSphere FastTrack assets are imported. You can use the following import options within the single quotation marks (' ').

-dsNamespace | -dsns server [/project]

Required only when mapping components are present in the archive file to be imported. Specifies the name of the InfoSphere DataStage® and QualityStage® server and optionally the project into which to import mapping components.

-onNameConflict | -nameConf [ignore | replace | rename]

Specifies an action that you want to take when a name conflict is detected for an InfoSphere Information Analyzer project.

ignore: The default option. If a project with the same name exists on the target, do not import.

replace: If a project with the same name exists on the target, replace the project with the imported asset.

rename: If a project with the same name exists on the target, then rename the new asset that is being imported. By default, _New is added to the end of the project name. You can use the -renameSuffix option to specify your own suffix.

-renameSuffix | -renSuf suffix

Specifies the suffix that would be used if there was a name conflict. By default the suffix is _New, but you can specify different text. For example, if a project named Customer_Data is being imported, and a project that is named Customer_Data exists on the target system, you can specify _Updated as the value for -renameSuffix. Then the project imported is renamed to Customer_Data_Updated.

Examples

The following command imports all InfoSphere FastTrack assets from the file ft_archive1.isx.

import -dom EVEREST -u admin -p admin100 -ar C:\ft_archive1.isx -ft ''

The following command imports all InfoSphere FastTrack assets. When a project of the same name exists on the target computer, the target project is replaced with the project in the archive file.

import -dom EVEREST -u admin -p admin100 -ar C:\ft_archive1.isx -ft '-nameconf replace'

The following command imports all InfoSphere FastTrack assets, including mapping components. When a project of the same name exists on the target computer, the project in the archive file is renamed on import by adding the suffix _imported to the project name.

import -dom EVEREST -u admin -p admin100 -ar C:\ft_archive1.isx -ft '-dsNamespace=EVEREST/dstage1 -nameconf rename -rensuf _imported'

Importing multiple types of assets

If the archive file includes multiple types of assets, you must specify each type of included metadata on the command line when you import the archive file, otherwise only InfoSphere FastTrack assets are imported.

Note: You must use the -replace option when you import report assets from an archive. If you do not want to use the -replace option for other types of assets in the archive, you must use a separate command to import the reports. If you import InfoSphere FastTrack assets without the -replace option and import their related reports with the -replace option, some of the reports might not be accurate for the unreplaced assets in the target environment. Check the reports and run them again in the new environment if necessary.

Archive files can contain assets from multiple exports of multiple tools. For best performance, when you import from an archive file, or when you migrate assets of varying types in multiple archive files, run separate commands to import the following types of assets in the following order:

Users and groups
Common metadata
InfoSphere DataStage and QualityStage assets.
Reports.
InfoSphere Information Analyzer assets.
InfoSphere FastTrack assets.
InfoSphere Information Governance Catalog extended data sources.
InfoSphere Information Governance Catalog extension mapping documents.
InfoSphere Information Governance Catalog business glossary assets. In versions earlier than 11.3, these assets are created in InfoSphere Business Glossary.
Custom attributes for InfoSphere Information Governance Catalog extended data sources and extension mappings. In versions earlier than 11.3, these assets are created in InfoSphere Metadata Workbench.

Asset types not listed can be imported in any order.

In the following example, the exported assets from the file ft_archive1.isx are imported in the correct order for best performance. The common metadata assets, InfoSphere DataStage and QualityStage assets, and InfoSphere FastTrack assets are imported without using the -replace option. The reporting assets are imported with the required -replace option.

import -u admin -p admin100 -dom EVEREST -ar ft_archive1.isx -cm ''
import -u admin -p admin100 -dom EVEREST -ar ft_archive1.isx 
   -ds '<import-options>' 
import -u admin -p admin100 -dom EVEREST -ar ft_archive1.isx 
  -replace -rep 
import -u admin -p admin100 -dom EVEREST -ar ft_archive1.isx 
  -fasttrack '<import options>'

If mapping components are to be imported, the import options for the InfoSphere FastTrack assets must include the -dsNamespace option, which specifies the server and project that the InfoSphere DataStage and QualityStage assets were imported to.

Exit status

The command returns the following exit values:

Exit status = 0: The package was built successfully.
Values greater than 0: An error occurred.

A summary report is printed upon completion.