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 Service Pack 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 idp Command Reference
  16. infacmd edp 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

Import Control File Parameters for Model Repository Objects

Import Control File Parameters for Model Repository Objects

Use the import control file parameters to configure the objects that you want to import from an XML file into the Model repository.
An import control file for Model repository objects can contain the following elements:
  • importParams. Can contain a single folderMaps element and a single connectionInfo element.
  • folderMaps. Can contain multiple folderMap elements.
  • folderMap. Contains attributes to filter objects in a specific folder. Can contain multiple objectList elements.
  • objectList. Contains attributes to filter objects by type. Can contain multiple object elements.
  • object. Contains attributes to filter objects by name.
  • connectionInfo. Can contain a single rebindMap element.
  • rebindMap. Can contain multiple rebind elements.
  • rebind. Contains attributes to map connections in the source repository to connections in the target repository.
The following table describes the configurable attributes for the folderMap element in the import control file:
Attribute Name
Attribute Description
sourceProject
Required. Name of the source project in the export file that contains the objects you want to import. The value is not case sensitive.
sourceFolderPath
Optional. Path of the source folder in the export file that contains the objects you want to import. Use the following format:
"/<folder_name>/<folder_name>"
For example, if a project contains a folder named F1, then the folder path of F1 is "/F1." To consider importing all objects in the project, specify "/." The value is not case sensitive. Default is "/."
targetProject
Required. Name of the project in the target repository into which you want to import objects. The project must exist in the repository before you import the objects. The value is not case sensitive.
targetFolderPath
Optional. Path of the folder in the target repository into which you want to import objects. Use the following format:
"/<folder_name>/<folder_name>"
For example, if a project contains a folder named F1, then the folder path of F1 is "/F1." To import all objects into the target project, specify "/." The folder must exist in the repository before you import the objects. The value is not case sensitive. Default is "/."
recursive
Optional. Indicates whether to import objects from subfolders of the specified folder. Set to true to import from subfolders. Valid values are true and false. The value is case sensitive. Default is true.
select
Optional. Indicates whether infacmd imports all remaining objects in the specified project when you define an objectList element for the folderMap. Set to all to import all remaining objects. For example, the following lines import mappings with a Reuse resolution strategy. The lines import all remaining objects with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2" select="all" resolution="replace">   
   <objectList type="Mapping" resolution="reuse" /> 
</folderMap>
If you define an objectList element and do not use the select attribute, then infacmd imports objects that satisfy the attributes defined in objectList. For example, the following lines import mappings with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2" resolution="replace">   
   <objectList type="Mapping" /> 
</folderMap>
If you do not define an objectList element for the folderMap, then the default value is all. For example, the following line imports all objects with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2" resolution="replace" />
Valid value is all.
resolution
Optional. Resolution strategy when a name conflict occurs. Applies to all objects in this folder. Specify one of the following values:
  • Rename. Rename source object using a generated name, and then import it.
  • Replace. Replace target object with the source object.
  • Reuse. Reuse object in the target Model repository.
  • None.
The values are not case sensitive. Default is none.
The following table describes the configurable attributes for the objectList element in the import control file:
Attribute Name
Attribute Description
type
Required. Type of Model repository object to import to the specified folder path. Valid values include all object types present in the Model repository. You can view the type of the object in the Properties view in the Developer tool. For example, you can enter "Relational Data Object" or "Profile." The value is not case sensitive.
select
Optional. Indicates whether infacmd imports all remaining objects of the specified type when you define an object element for the objectList. Set to all to import all remaining objects. For example, the following lines import MyMapping with a Reuse resolution strategy. The lines import all remaining mappings with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2">
  <objectList type="Mapping" select="all" resolution="replace">
    <object name="MyMapping" resolution="reuse" />
  </objectList>
</folderMap>
If you define an object element and do not use the select attribute, then infacmd imports objects that satisfy the attributes defined in the object element. For example, the following lines import the mapping named MyMapping with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2">
  <objectList type="Mapping" resolution="replace">
    <object name="MyMapping"/>
  </objectList>
</folderMap>
If you do not define an object element for the objectList, then the default value is all. For example, the following lines import all mappings with a Replace resolution strategy: 
<folderMap sourceProject="p1" targetProject="p2">
  <objectList type="Mapping" resolution="replace" />
</folderMap>
Valid value is all.
resolution
Optional. Resolution strategy when a name conflict occurs. Applies to all objects of the specified type. Specify one of the following values:
  • Rename. Rename source object using a generated name, and then import it.
  • Replace. Replace target object with the source object.
  • Reuse. Reuse object in the target Model repository.
  • None.
The values are not case sensitive. Default is none.
The following table describes the configurable attributes for the object element in the import control file:
Attribute Name
Attribute Description
name
Required. Name of a specific object to import of the specified object type. The value is not case sensitive.
resolution
Optional. Resolution strategy when a name conflict occurs for this object. Specify one of the following values:
  • Rename. Rename source object, and then import it.
  • Replace. Replace target object with the source object.
  • Reuse. Reuse object in the target Model repository.
  • None.
The values are not case sensitive. Default is none.
renameTo
Optional. Name to use when the conflict resolution strategy is Rename. If you do not specify a name, then infacmd generates a name by appending a number to the end of the name. Infacmd ignores the value if there are no conflicts or if the conflict resolution strategy is not Rename.
renameIdTo
Optional. ID string to use when you import a connection object and the conflict resolution strategy is Rename. If you do not specify a connection ID, then infacmd generates an ID by appending a number to the end of the connection ID. Infacmd ignores the value if there are no conflicts or if the conflict resolution strategy is not Rename.
The following table describes the configurable attributes for the rebind element in the import control file:
Attribute Name
Attribute Description
source
Required. Name of a source connection in the file that you are importing. The value is not case sensitive.
target
Required. Name of a connection in the target Model repository to map to the source connection. By default, the connection must exist in the target repository before you import the objects. If the connection does not exist, the import fails. When you run infacmd, you can choose to skip target connection validation during the import. When you skip target connection validation, the import succeeds if a connection does not exist in the target repository. The value is not case sensitive.
0 COMMENTS
We’d like to hear from you!