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

getDomainObjectPermissions

getDomainObjectPermissions

Gets the list of domain objects to which the specified users or groups have permission. You can generate reports for the specified users or groups.
Users with the administrator role can run this command.
The infacmd aud getDomainObjectPermissions command uses the following syntax: 
getDomainObjectPermissions

<-DomainName|-dn> domain_name
<-UserName|-un> user_name
<-Password|-pd> password
[<-SecurityDomain|-sdn> security_domain]
[<-Gateway|-hp> gateway_host1:port gateway_host2:port...]
[<-ResilienceTimeout|-re> timeout_period_in_seconds]
<<-ExistingUserNames|-eu> existing_user_names|
<-ExistingGroupNames|-eg> existing_group_names>
[<-ExistingSecurityDomain|-esd> existing_security_domain] 
[<-Format|-fm> format_TEXT_CSV]
[<-OutputFile|-lo> output_file_name]
The infacmd program uses the following common options to connect to the domain: domain name, user name, password, security domain, and resilience timeout. The table of options has brief descriptions. To see detailed descriptions, refer to Connecting to the Domain.
The following table describes infacmd aud getDomainObjectPermissions options and arguments:
Option
Description
-DomainName
-dn
Name of the Informatica domain.
-UserName
-un
User name to connect to the domain.
-Password
-pd
Password for the user name.
-SecurityDomain
-sdn
Name of the security domain that you want to create to which the domain user belongs.
-
Gateway
-
hp
Required if the gateway connectivity information in the domains.infa file is out of date. Specify the host names and port numbers for the gateway nodes in the domain.
-ResilienceTimeout
-re
Amount of time in seconds that infacmd attempts to establish or re-establish a connection to the domain.
-ExistingUserNames
-eu
Required if you do not use ‑ExistingGroupNames (-eg). Name of the user or a list of users to run the reports. For multiple users, separate each user by a comma at the command line.
-ExistingGroupNames
-eg
Required if you do not use ‑ExistingUserName (-eu). Name of the group or a list of groups to run the reports. For multiple groups, separate each group by a comma at the command line.
-ExistingSecurityDomain
-esd
Required if you use LDAP authentication. Security domain to which the user or group belongs. Default is Native.
-Format
-fm
Optional. Output file format. Valid types include:
  • Text
  • CSV
If you do not specify a format, infacmd uses text format with lines wrapped at 80 characters.
-OutputFile
-lo
Optional. Name and file path for the output file.
If you do not specify an output file name, infacmd displays the log events on the screen.
0 COMMENTS
We’d like to hear from you!