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

DeployFolder

DeployFolder

Deploys a folder. You can use this command to copy a folder within a repository or to a different repository.
To use this command, you must create a control file with all the specifications that the Copy Wizard requires. The control file is an XML file defined by the depcntl.dtd file.
If
pmrep
 cannot immediately acquire object locks in the target repository, by default it waits indefinitely to acquire the locks.
You can use the deployment control file parameters to specify a deployment timeout. The deployment timeout is the period of time (in seconds) that
pmrep
 waits to acquire locks. A value of 0 fails the deployment if
pmrep
 cannot immediately acquire locks. The default value is -1, which instructs
pmrep
 to wait indefinitely to acquire the locks.
Press Ctrl+C to cancel the deployment during the deployment operation or while
pmrep
 is waiting to acquire object locks.
The DeployFolder command uses the following syntax:
deployfolder 

-f <folder_name>

-c <control_file_name>

-r <target_repository_name>

[-n <target_repository_user_name>

[-s <target_repository_user_security_domain>]

 [-x <target_repository_password> | 

  -X <target_repository_password_environment_variable>]

 [-d <target_domain_name> |

   {-h <target_portal_host_name>

    -o <target_portal_port_number>}]] (only if target is in a different domain)

[-l <log_file_name>]
The following table describes
pmrep
 DeployFolder options and arguments:
Option
Argument
Description
-f
folder_name
Required. Name of the folder to deploy.
-c
control_file_name
Required. Name of the XML file containing the Copy Wizard specifications.
-r
target_repository_name
Required. Name of the target repository you are copying the folder to.
-n
target_repository_user_name
Required if you copy the folder to another repository. Login user name for the target repository.
-s
target_repository_user_
security_domain
Required if you use LDAP authentication. Name of the security domain that the user belongs to. Default is Native.
-x
target_repository_user_
password
Optional. Login password for the target repository. Use the -x or -X option, but not both. If you copy the folder to a different repository and you do not use the -x or -X option,
pmrep
 prompt you for the password.
-X
target_repository_password_
environment_variable
Optional. Login password environment variable for the target repository. Use the -x or -X option, but not both. If you copy the folder to a different repository and you do not use the -x or -X option,
pmrep
 prompt you for the password.
-d
target_domain_name
Required if you copy the folder to a different repository and you do not use the -h and -o options. Name of the domain for the repository.
-h
target_portal_host_name
Required if you copy the folder to a different repository and you do not use the -d option. Machine name for the node that hosts the domain of the target repository.
-o
target_portal_port_number
Required if you copy the folder to a different repository and you do not use the -d option. Port number for the node that hosts the domain of the target repository.
-l
log_file_name
Optional. Log file that records each deployment step. If you omit this option,
pmrep
 outputs the deployment steps to the command line window.
0 COMMENTS
We’d like to hear from you!