Import command for InfoSphere Streams assets

Use the istool import command with the -streamsEndpoint parameter to import an archive file that contains endpoints from InfoSphere Streams.

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.

Any custom attributes that were created for InfoSphere Streams endpoints and exported into the archive file are imported with the endpoints.

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 Common Metadata Importer role to import InfoSphere Streams assets.

You must run the command on a client tier computer.

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 to 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]
[-responseFile "file_name_and_path"]
-streamsEndpoint '-onNameConflict [ignore | replace]'

Command options

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.

-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 -igc command. Not supported with the -preview parameter. For more information, see Using a response file for istool export and istool import commands.

-streamsEndpoint | -streams

Required. Specifies that InfoSphere Streams endpoints are imported. Requires the following option:

'-onNameConflict | -nameconf [ignore | replace]'

Specifies the action that you want to perform when a name conflict is detected for an endpoint:

ignore: The default. If an endpoint with the same name and application scope already exists on the target computer, then the endpoint is not imported.
replace: If an endpoint with the same name and application scope already exists on the target computer, then the existing endpoint is replaced with the imported endpoint.

Importing multiple types of assets

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.

Exit status

A return value of 0 indicates successful completion. Any other value indicates failure.

Example

The following example imports endpoints from the archive file ep.isx. When an endpoint of the same name and application scope already exists in the metadata repository, the imported endpoint replaces the existing endpoint.

istool> import -domain ISDOMAIN:9443 -archive c:\temp\ep.isx 
-username dsadm -password **** -streams '-nameconf replace'