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
  • Common Content for Data Engineering 10.2.2
  • 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 dps Command Reference
  16. infacmd edl Command Reference
  17. Infacmd es Command Reference
  18. infacmd ihs Command Reference
  19. infacmd ipc Command Reference
  20. infacmd isp Command Reference
  21. infacmd ldm Command Reference
  22. infacmd mas Command Reference
  23. infacmd mi Command Reference
  24. infacmd mrs Command Reference
  25. infacmd ms Command Reference
  26. infacmd oie Command Reference
  27. infacmd ps Command Reference
  28. infacmd pwx Command Reference
  29. infacmd roh Command Reference
  30. infacmd rms Command Reference
  31. infacmd rtm Command Reference
  32. infacmd sch Command Reference
  33. infacmd search Command Reference
  34. infacmd sql Command Reference
  35. infacmd tdm Command Reference
  36. infacmd tools Command Reference
  37. infacmd wfs Command Reference
  38. infacmd ws Command Reference
  39. infacmd xrf Command Reference
  40. infacmd Control Files
  41. infasetup Command Reference
  42. pmcmd Command Reference
  43. pmrep Command Reference
  44. Working with pmrep Files

Command Reference

Command Reference

Back Next

ObjectExport

ObjectExport

Exports objects to an XML file defined by the powrmart.dtd file. You export an object by name. If you enter an object, you must enter the name of the folder that contains it. If you do not enter a version number, you export the latest version of the object.
Use a persistent input file to specify different objects to export at one time. You can create this file by using the ExecuteQuery, Validate, or ListObjectDependencies
pmrep
 commands. If you use the persistent input file, do not use the other parameters to specify objects.
If you export a mapping, by default PowerCenter exports the mapping and its instances. If you want to include dependent objects, you must add the appropriate
pmrep
 options. You can optionally include reusable and non-reusable dependent objects, objects referenced by shortcuts, and related objects in a primary key-foreign key relationship.
To export mapping dependencies, you must use the -b and -r options.
The ObjectExport command uses the following syntax: 
objectexport 

{{-n <object_name> 

 -o <object_type> 

 [-t <object_subtype>] 

 [-v <version_number>] 

 [-f <folder_name>]} |

 -i <persistent_input_file>}

[-m (export pk-fk dependency)]

[-s (export objects referred by shortcut)]

[-b (export non-reusable dependents)]

[-r (export reusable dependents)]

-u <xml_output_file_name>

[-l <log_file_name>]

[-e dbd_separator]
The following table describes
pmrep
 ObjectExport options and arguments:
Option
Argument
Description
-n
object_name
Required if you do not use the -i option. Name of a specific object to export. If you do not enter this option,
pmrep
 exports all the latest or checked out objects in the folder. Use the -n option or the -i option, but not both.
-o
object_type
Object type of the object name. You can specify source, target, transformation, mapping, mapplet, session, worklet, workflow, scheduler, session config, or task. If you use this option, you cannot use the -i option.
-t
object_subtype
Type of transformation or task. This argument is ignored for other object types. For more information about valid subtypes, see Listing Object Types.
-v
version_number
Optional. Exports the version of the object that you enter.
-f
folder_name
Name of the folder containing the object to export. If you do not enter an object name,
pmrep
 exports all the objects in this folder. If you use this option, you cannot use the -i option.
-i
persistent_input_file
Required if you do not use the -n option. Text file list of objects generated from ExecuteQuery, Validate, or ListObjectDependencies. It contains object records with encoded IDs. If you use this parameter, you cannot use the -n, -o, or -f options.
-m
-
Required to export dependent objects. Exports primary key table definitions when you export sources or targets with foreign keys.
-s
-
Required to export dependent objects. Exports the original object referenced by the shortcut.
-b
-
Required to export dependent objects. Exports non-reusable objects used by the object.
-r
-
Required to export dependent objects. Exports reusable objects used by the object.
-u
xml_output_file_name
Required. Name of the XML file to contain the object information.
-l
log_file_name
Optional. Log file that records each export step. If you omit this option, status messages output to the window.
-e
dbd_separator
Optional. If an ODBC source has a period (.) in the name, define a different separator character when you define the source object. For example, instead of database_name.source_name, define the source object as database_name\source_name, and define the dbd_separator as backslash (\).
0 COMMENTS
We’d like to hear from you!