workbench extension mapping export command

Use the istool command workbench extension mapping export to export extension mapping documents from the metadata repository to a file in a comma-separated value (CSV) format.

Purpose

Use this command to export extension mapping documents or when you want to schedule an export.

Requirements

You must have the Information Governance Catalog Information Asset Administrator role.

Information Governance Catalog must be installed on the same IBM® WebSphere® Application Server.

The version of istool command framework must be the same version as InfoSphere® Information Governance Catalog.

Run the command from the client tier, or from the engine tier if InfoSphere Information Governance Catalog was installed there.

Command syntax

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.

istool> workbench extension mapping export
authentication parameters
-directory directory_for export_file
-pattern string_to_match 
-output log_file_name
[generic parameters]

Parameters

These parameters are specific to the workbench extension mapping export command. For authentication parameters and generic parameters, see Common commands and parameters.

-directory | -dir directory_for export_file: Specifies the name of the directory that contains the export file. The export file can be a single file in a CSV format. Alternatively, the export file can contain multiple files in a CSV format that are combined into a single file in a compressed format.
-pattern | -pt string_to_match: Specifies the text pattern to match in the name of the extension mapping documents. Use the percent sign (%) as a wildcard character. If string_to_match is a single percent sign, all mapping documents in the -directory directory are exported.
-output | -o log_file_name: Specifies the name of the log file that contains the output, including errors, of the command that was run. Include the directory path in log_file_name.; If the directory does not exist, the command fails.; The log file is created if it does not exist. If the log file does exists, the output is appended to the file. If the command is automated to run at different times, the log file displays the ongoing output of each command that was run.

Output

A return value of 0 indicates successful completion; any other value indicates failure. The reason for the failure is displayed in a screen message.

For more information, see the system log file in either of the following directories:

For Microsoft Windows operating system environment: C:\Documents and Settings\username\istool_workspace\.metadata\.log; where username is the name of the operating system account of the user who runs this command.
For UNIX or Linux operating system environment: user_home/username/istool_workspace/.metadata/.log; where user_home is the root directory of all user accounts, and username is the name of the operating system account of the user who runs this command.

Example

You can export extension mapping documents whose file name begins with the string "myMap". All CSV files in directory E:\CLI\files\a are searched. The log file is C:\IBM\InformationServer\logs\amount_due_export.log:

istool> workbench extension mapping export 
-dom mysys
-u myid 
-p mypassword
-dir E:\CLI\files\a 
-pt myMap%
-o C:\IBM\InformationServer\logs\amount_due_export.log

You can export all extension mapping documents in a specified directory, such as E:\CLI\map_files. The log file is C:\IBM\InformationServer\logs\all_ext_map_docs_export.log:

istool> workbench extension mapping export 
-dom mysys
-u myid 
-p mypassword
-dir E:\CLI\map_files 
-pt %
-o C:\IBM\InformationServer\logs\all_ext_map_docs_export.log