Shared Content for Data Engineering 10.2
- All Products
ExportToPC <-Release|-rel> release_number [<-SourceFile|-sf> source_file] [<-SourceRepository|-sr> source_repository] [<-SourceFolders|-f> folder1 folder2|<-SourceObjects|-so> object1 object2] [<-Recursive|-r>] [<-TargetLocation|-tl> target_location] [<-TargetFolder|-tf> target_folder_name] [<-CodePage|-cp> target_code_page] [<-Check|-c>] [<-ReferenceDataLocation|-rdl> reference_data_output_location] [<-ConvertMappletTargets|-cmt>] [<-ConvertMappingsToMapplets|-cmm>] [<-NoValidation|-nv>] [<-DSTErrorFormat|-def>]
Required. The PowerCenter release number.
Optional. The full path to an XML file containing source objects that you exported with the Developer tool.
Optional. The Model repository that contains the objects to export to PowerCenter.
To specify the gateway host and port to connect to the Model Repository Service, use the following command syntax in a non-Kerberos domain:
To specify the domain name when you have multiple gateway nodes, use the following command syntax to establish a resilient connection to the Model Repository Service in a non-Kerberos domain:
To specify the domain name with the logged-in credentials, use the following command syntax to run the command with single sign on:
To specify the gateway host and port with the logged-in credentials, use the following command syntax to run the command with single sign on:
To specify the gateway host and port with the user credentials you specify instead of the logged-in credentials, use the following command syntax in a Kerberos domain:
To specify the domain name with the user credentials you specify instead of the logged-in credentials, use the following command syntax in a Kerberos domain:
The port parameter is the HTTP port. The &namespace parameter is optional. The default namespace is native.
If you use -sr, you must use -f or -so.
List of source folders that you want to export from the Model repository. You can export mapplets, mappings, and logical data object models from the source folders to PowerCenter. If you export more than one object, you must separate each object in the list with a space.
If you use -sr, you must use -f or -so.
List of source objects that you want to export from the Model repository. You can export mapplets, mappings, and logical data object models to PowerCenter. You can describe the object as a name.
Use the following syntax:
You must include the full path of the object. If you export more than one object, you must separate each object in the list with a space.
You can enter the following types:
Optional. Exports all mappings and logical data object models from the source folders. Exports each subfolder below the objects, and any subfolders below that.
Optional. The full path to the target XML file.
Optional. The PowerCenter folder to export the objects to. The ExportToPC command places the folder name in the target XML file. If you do not configure a folder name, the ExportToPC command creates a folder name.
Optional. Code page of the PowerCenter repository. Default is UTF-8.
Optional. Tests the conversion without creating a target file.
Optional. Location where you want to save reference table data. The ExportToPC command saves the reference table data as one or more dictionary .dic files.
Optional. Converts targets in mapplets to output transformations in the PowerCenter mapplet.
PowerCenter mapplets cannot contain targets. If the export includes a mapplet that contains a target and you do not select this option, the export fails.
Optional. Converts Developer tool mappings to PowerCenter mapplets. The Developer tool converts sources and targets in the mappings to Input and Output transformations in a PowerCenter mapplet.
Optional. The ExportToPC command does not validate source objects before converting them.
Optional. The error messages appear in a format that the Developer tool can parse. The full path of each object displays in the error messages. Default is to display errors in a user-friendly format.
Updated April 22, 2019