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
  • 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

Register

Register

Registers a local repository with a connected global repository. You must connect to the global repository before you register the local repository.
Also, you must run the Repository Service for the local repository in exclusive mode. You can configure the Repository Service to run in exclusive mode in the Administrator tool or you can use the
infacmd
 UpdateRepositoryService command.
The command returns “register successfully completed” or returns “failed to execute register” message. The registration might fail for the following reasons:
  • You failed to connect to the Repository Service.
  • The local repository is not running in exclusive mode.
  • The Repository Service failed to initialize information about the global repository.
  • The Repository Service failed to register the local repository with the global repository.
The Register command uses the following syntax: 
register 

-r <local_repository_name> 

-n <local_repository_user_name> 

[-s <local_repository_user_security_domain>]

[-x <local_repository_password> |

-X <local_repository_password_environment_variable>]

[-d <local_repository_domain_name> | 

{-h <local_repository_portal_host_name> 

-o <local_repository_portal_port_number>}] (if local repository is in a different domain)
The following table describes
pmrep
 Register options and arguments:
Option
Argument
Description
-r
local_repository_name
Required. Name of the local repository to register.
-n
local_repository_user_name
Required. Local user name.
-s
local_repository_user_security_
domain
Required if you use LDAP authentication. Name of the security domain that the user belongs to. Default is Native.
-x
local_repository_password
Optional. Login password for the local target repository. You use the -x or -X option, but not both. If you do not use the -x or -X option,
pmrep
 prompts you for the password.
-X
repository_password_
environment_variable
Optional. Login password environment variable for the local target repository. You use the -x or -X option, but not both. If you do not use the -x or -X option,
pmrep
 prompts you for the password.
-d
local_repository_domain_name
Required if the local repository is in a different domain and you do not use the -h and -o options. Name of the Informatica domain for the repository.
-h
local_repository_portal_host_
name
Required if the local repository is in a different domain and you do not use -d. Machine name of the domain where the local repository is located. If you use this option, you must also use the -o option.
-o
local_repository_portal_port_
number
Required if the local repository is in a different domain and you do not use -d. Port number for the domain where the local repository is located. If you use this option, you must also use the -h option.
0 COMMENTS
We’d like to hear from you!