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.5.3
  • 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 dis Queries
  16. infacmd dp Command Reference
  17. infacmd idp Command Reference
  18. infacmd edp Command Reference
  19. Infacmd es Command Reference
  20. infacmd ics Command Reference
  21. infacmd ipc Command Reference
  22. infacmd isp Command Reference
  23. infacmd ldm Command Reference
  24. infacmd mas Command Reference
  25. infacmd mi Command Reference
  26. infacmd mrs Command Reference
  27. infacmd ms Command Reference
  28. infacmd oie Command Reference
  29. infacmd ps Command Reference
  30. infacmd pwx Command Reference
  31. infacmd roh Command Reference
  32. infacmd rms Command Reference
  33. infacmd rtm Command Reference
  34. infacmd sch Command Reference
  35. infacmd search Command Reference
  36. infacmd sql Command Reference
  37. infacmd tdm Command Reference
  38. infacmd tools Command Reference
  39. infacmd wfs Command Reference
  40. infacmd ws Command Reference
  41. infacmd xrf Command Reference
  42. infacmd Control Files
  43. infasetup Command Reference
  44. pmcmd Command Reference
  45. pmrep Command Reference
  46. Working with filemanager
  47. Working with pmrep Files

Command Reference

Command Reference

Back Next

importObjects

importObjects

Imports objects from an XML file into an existing project in the Model repository.
If you do not want to import all objects in the file, use an infacmd import control file to filter the Model repository objects that you want to import.
If the file being imported contains reference tables, you must run the command from the Informatica services installation directory. The command imports the reference table metadata from the XML file into the Model repository. The command imports the reference table data from a zip file. When you run the command, specify the path and file name of both the XML and zip files to be imported.
If the command fails with a Java memory error, increase the system memory available for infacmd. To increase the system memory, set the -Xmx value in the ICMD_JAVA_OPTS environment variable.
The infacmd tools importObjects command uses the following syntax: 
importObjects

<-DomainName|-dn> Domain name

<-UserName|-un> User name

<-Password|-pd> Password

[<-SecurityDomain|-sdn> Security domain]

[<-TargetProject|-tp> Target project name <ignored if control file is specified>]

<-RepositoryService|-rs> Model Repository Service name

<-ImportFilePath|-fp> import_file_path

[<-SourceProject|-sp> Source project name in import file <ignored if control file is specified>]

[<-TargetFolder|-tf> Target folder to import to <omit for root, ignored if control file is specified>]

[<-SkipCRC|-sc> Set to "true" to skip CRC check on imported file.]

[<-ConflictResolution|-cr> Resolution type]

[<-ControlFilePath|-cp> Path of import control file]

[<-SkipCnxValidation|-scv> Set to "true" to skip connection validation.]

[<-OtherOptions|-oo>]
The following table describes infacmd tools importObjects options and arguments:
Option
Argument
Description
-DomainName
-dn
Domain name
Required. Name of the Informatica domain. You can set the domain name with the -dn option or the environment variable INFA_DEFAULT_DOMAIN. If you set a domain name with both methods, the -dn option takes precedence.
-UserName
-un
User name
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
-Password
-pd
Password
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
-SecurityDomain
-sdn
Security domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
-TargetProject
-tp
Target Project name <ignored if control file is specified>
Optional. Name of the project into which you want to import the objects. The project must exist in the repository before you import the objects. The option is ignored if you use an import control file.
-RepositoryService
- rs
Model Repository Service name
Required. Model Repository Service name.
-ImportFilePath
-fp
import_file_path
Required. Path and file name of the XML file to import the objects from. You can specify an absolute path or a relative path to the file name.
-SourceProject
-sp
Source project name in import file <ignored if control file is specified>
Optional. Source project name in the file to import. The option is ignored if you use an import control file.
-TargetFolder
-tf
Target folder to import to <omit for root, ignored if control file is specified>
Optional. Target folder into which you want to import the objects. If you do not specify a target folder, the objects are imported into the target project. The folder must exist in the repository before you import the objects. The option is ignored if you use an import control file.
-SkipCRC
-sc
Set to "true" to skip CRC check on imported file.
Indicates whether to skip the cyclic redundancy check (CRC) that detects whether the file to import was modified. Set to true to skip the check. Default is false.
-ConflictResolution
-cr
Resolution type specified
Optional. Conflict resolution strategy. You can specify one of the following options for all objects being imported:
  • rename
  • replace
  • reuse
  • none
The option is ignored if you use an import control file. If the conflict resolution strategy is set to none and a conflict occurs, the import fails. Default is none.
-ControlFilePath
-cp
Path of import control file
Optional. Path and file name of the import control file that filters the objects that are imported. You can specify an absolute path or a relative path.
-SkipCnxValidation
-scv
Set to "true" to skip connection validation.
Optional. Indicates whether to skip target connection validation during the import. By default, the import process verifies that connections used by the imported objects exist in the target repository. If the connections do not exist, the import fails.
To skip target connection validation and continue with the import, set this option to true. If the imported objects use connections that do not exist in the target repository, the import process imports the objects with an "Unspecified" connection. Use the Developer tool to select the correct connection after the import process has completed.
Default is false.
If an import control file specifies a source connection that does not exist in the file that you are importing, the import process fails regardless of the value for this option. To correct the error, verify that the connection rebind element in the import control file includes source connections that exist in the file that you are importing.
-OtherOptions
-oo
-
Required if the import file contains reference tables. Additional options to import reference table data from a zip file. Enter options using the following format: 
rtm:<option_name>=<value>,<option_name>=<value>
Required option names include:
  • disName. Name of the Data Integration Service.
  • codePage. Code page of the reference data.
  • refDataFile. Path and file name of the zip file from where you want to import the reference table data.
For example: 
rtm:disName=ds,codePage=UTF-8,refDataFile=/folder1/data.zip
0 COMMENTS
We’d like to hear from you!