Table of Contents


  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



Deploys an application patch using a .piar file to a Data Integration Service. The Data Integration Service applies the patch to the corresponding incremental application. The incremental application must be deployed on the same Data Integration Service where you want to deploy the patch.
If you created the patch based on a previous version of the incremental application, the patch might not be valid. A patch is not valid if the application objects in the patch have been updated by other application patches since the patch that you currently want to deploy was created. To proceed, you can force the Data Integration Service to apply the patch.
You can also choose to retain or discard state information. State information refers to mapping properties and the properties of run-time objects such as mapping outputs or the Sequence Generator transformation.
For more information about state information, see the "Application Deployment" chapter in the
Informatica Developer Tool Guide
If you deploy a previous version of a patch, the Data Integration Service does not roll back the incremental application to the time that the patch was created. The Data Integration Service updates the application based on the application objects in the patch.
The infacmd tools patchApplication command uses the following syntax:
patchApplication <-DomainName|-dn> Domain name <-UserName|-un> User name <-Password|-pd> Password [<-SecurityDomain|-sdn> Security domain] <-DataIntegrationService|-dis> Data Integration Service name <-FilePath|-fp> Patch file path [<-force|-f> True | False] [<-RetainStateInformation|-rsi> True | False]
The following table describes infacmd tools patchApplication options and arguments:
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.
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.
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.
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.
Data Integration Service name
Required. The name of the Data Integration Service where the incremental application is deployed.
Patch file path
Required. Path and .piar file name of the patch to deploy. You can specify an absolute path or a relative path to the file name.
True | False
Optional. Use
to ignore the validity of the patch and force the Data Integration Service to apply the patch to the application. Default is
True | False
Optional. Indicates whether state information is retained or discarded.
This option overrides the setting to retain or discard state information in the application patch archive file.


We’d like to hear from you!