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

Command Reference

Command Reference

Back Next

RegisterPlugin

RegisterPlugin

Registers an external plug-in to a repository. Registering a plug-in adds its functionality to the repository. Use the RegisterPlugin command to update existing plug-ins.
When you use this command, the Repository Service must be running 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 RegisterPlugin command uses the following syntax: 
registerplugin 

-i <input_registration_file_name_or_path>

[-e (update plug-in)]

[-l <NIS_login> 

  {-w <NIS_password> | 

  -W <NIS_password_environment_variable>} 

  [-k (CRC check on security library)]]

[-N (is native plug-in)]
The following table describes
pmrep
 RegisterPlugin options and arguments:
Option
Argument
Description
-i
input_registration_file_name_or_
path
Required. Name or path of the registration file for the plug-in.
-e
-
Optional. Update an existing plug-in. Not applicable for authentication modules.
-l
NIS login
Optional. Registers security module components. Provide the NIS login of the user registering an external security module. If the plug-in contains an authentication module, you must supply the external login name, or the registration fails. This login becomes the administrator user name in the repository. Do not use this option for other plug-ins.
-w
NIS password
Optional. Use to register authentication module components.
External directory password of the user registering the module. If the plug-in contains an authentication module, you must supply the user password from the external directory or the registration fails. Do not use this option for other plug-ins.
Use the -w or -W option, but not both. If you do not supply a password or password environment variable,
pmrep
 prompts you for a password.
-W
NIS_password_environment_
variable
Optional. Use to register authentication module components.
External directory password environment variable of the user registering the module. If the plug-in contains an authentication module you must supply the user password from the external directory or the registration fails. Do not use this option for other plug-ins.
Use the -w or -W option, but not both. If you do not supply a password or password environment variable,
pmrep
 prompts you for a password.
-k
-
Optional. Stores the CRC of the plug-in library in the repository. When the Repository Service loads the module, it checks the library against the CRC.
-N
-
Registers a plug-in. Required when the following conditions are true:
  • You upgrade PowerCenter.
  • The PowerCenter upgrade does not have a new repository version.
  • The plug-in contains updated functionality.
  • The plug-in is registered by default with a new PowerCenter installation.
For information about plug-ins that you need to register when you upgrade, see the
PowerCenter Release Guide
.
0 COMMENTS
We’d like to hear from you!