Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica Data Quality 10.4.1
  • All Products

Table of Contents

Search

  1. Preface
  2. Command Line Programs and Utilities
  3. Installing and Configuring Command Line Utilities
  4. Using the Command Line Programs
  5. Environment Variables for Command Line Programs
  6. Using infacmd
  7. infacmd as Command Reference
  8. infacmd aud Command Reference
  9. infacmd autotune Command Reference
  10. Infacmd bg Command Reference
  11. infacmd ccps Command Reference
  12. infacmd cluster Command Reference
  13. infacmd cms Command Reference
  14. infacmd dis Command Reference
  15. infacmd dp Command Reference
  16. infacmd idp Command Reference
  17. infacmd edp Command Reference
  18. Infacmd es Command Reference
  19. infacmd ihs Command Reference
  20. infacmd ipc Command Reference
  21. infacmd isp Command Reference
  22. infacmd ldm Command Reference
  23. infacmd mas Command Reference
  24. infacmd mi Command Reference
  25. infacmd mrs Command Reference
  26. infacmd ms Command Reference
  27. infacmd oie Command Reference
  28. infacmd ps Command Reference
  29. infacmd pwx Command Reference
  30. infacmd roh Command Reference
  31. infacmd rms Command Reference
  32. infacmd rtm Command Reference
  33. infacmd sch Command Reference
  34. infacmd search Command Reference
  35. infacmd sql Command Reference
  36. infacmd tdm Command Reference
  37. infacmd tools Command Reference
  38. infacmd wfs Command Reference
  39. infacmd ws Command Reference
  40. infacmd xrf Command Reference
  41. infacmd Control Files
  42. infasetup Command Reference
  43. pmcmd Command Reference
  44. pmrep Command Reference
  45. Working with pmrep Files

Command Reference

Command Reference

Back Next

ExportToPC

ExportToPC

Exports objects from the Model repository or an export file and converts them to PowerCenter objects.
The ExportToPC command converts objects from the Model repository or from an XML file that you exported from the Model repository. You must choose either a Model repository or a source file for export. If you choose both options, the source file option takes precedence. Run ExportToPC command to create an XML file that you can import into PowerCenter with the pmrep program.
The infacmd ipc ExportToPC command uses the following syntax: 
ExportToPC

<-Release|-rel> release_number

[<-SourceFile|-sf> source_file]

[<-SourceRepository|-sr> source_repository]

[<-SourceFolders|-f> folder1 folder2|<-SourceObjects|-so> source_objects]

[<-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>]

[<-OptimizationLevel|- O optimization_level 1 or Optimization_level 2]
The following table describes infacmd ipc ExportToPC command options and arguments:
Option
Argument
Description
-Release
-rel
release_number
Required. The PowerCenter release number.
-SourceFile
-sf
source_file
Optional. The full path to an XML file containing source objects that you exported with the Developer tool.
-SourceRepository
-sr
source_repository
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: 
<Model repository name>@<host>:<port>#<projectname>
?user=<username>[&namespace=<namespace>]&password=<password>
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: 
<Model repository name>@<domainname>#<projectname>
?user=<username>[&namespace=<namespace>]&password=<password>
To specify the domain name with the logged-in credentials, use the following command syntax to run the command with single sign on: 
<Model repository name>@<domainname>#<projectname>
?isloggedinuser=true[&namespace=<namespace>]
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: 
<Model repository name>@<host>:<port>#<projectname>
?isloggedinuser=true[&namespace=<namespace>]
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: 
<Model repository name>@<host>:<port>#<projectname>
?iskerberos=true&user=<username>[&namespace=<namespace>]&password=<password> &Kerberosrealm=<kerberosrealm>
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: 
<Model repository name>@<domainname>#<projectname>
?iskerberos=true&user=<username>[&namespace=<namespace>]&password=<password> &Kerberosrealm=<kerberosrealm>
The port parameter is the HTTP port. The &namespace parameter is optional. The default namespace is native.
-SourceFolders
-f
source_folders
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.
SourceObjects
-so
source_objects
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: 
name=/<path>/<objectname>[&type=<typename>]
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:
  • Mapping. Use to export mapping and mapplets.
  • DataObjectModel. Use to export logical data object models.
The type is not case sensitive. Default is Mapping.
-Recursive
-r
-
Optional. Exports all mappings and logical data object models from the source folders. Exports each subfolder below the objects, and any subfolders below that.
Default is false.
-TargetLocation
-tl
target_location
Optional. The full path to the target XML file.
-TargetFolder
-tf
target_folder_name
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.
-CodePage
-cp
target_code_page
Optional. Code page of the PowerCenter repository. Default is UTF-8.
-Check
-c
-
Optional. Tests the conversion without creating a target file.
Default is false.
-ReferenceDataLocation
-rdl
reference_data_output_location
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.
-ConvertMappletTargets
-cmt
-
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.
Default is false.
-ConvertMappingstoMapplets
-cmm
-
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.
Default is false.
-NoValidation
-nv
-
Optional. The ExportToPC command does not validate source objects before converting them.
Default is false.
-DSTErrorFormat
-def
-
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.
OptimizationLevel
- O
optimization_level
Optional. Controls the optimization methods that the Data Integration Service applies to the mapping. Enter the numeric value that is associated with the optimization level that you want to configure. Enter one of the following numeric values:
  • 0 (None). The Data Integration Service does not apply any optimization.
  • 1 (Minimal). The Data Integration Service applies the early projection optimization method.
  • 2 (Normal). The Data Integration Service applies the early projection, early selection, branch pruning, push-into, pushdown, and predicate optimization methods. Normal is the default optimization level.
  • 3 (Full). The Data Integration Service applies the cost-based, early projection, early selection, branch pruning, predicate, push-into, pushdown, and semi-join optimization methods.
If you do not use this option, the Data Integration Service applies the optimization level configured in the mapping properties for the deployed application in the Administrator tool.
0 COMMENTS
We’d like to hear from you!