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.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 dps Command Reference
  16. infacmd edl 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 rms Command Reference
  30. infacmd rtm Command Reference
  31. infacmd sch Command Reference
  32. infacmd search Command Reference
  33. infacmd sql Command Reference
  34. infacmd tdm Command Reference
  35. infacmd wfs Command Reference
  36. infacmd ws Command Reference
  37. infacmd xrf Command Reference
  38. infacmd Control Files
  39. infasetup Command Reference
  40. pmcmd Command Reference
  41. pmrep Command Reference
  42. Working with pmrep Files

Command Reference

Command Reference

Back Next

PrintSPNAndKeytabNames

PrintSPNAndKeytabNames

Generates the list of SPN and keytab file names for the nodes and services in the domain. The Informatica domain requires a keytab file for each SPN. You might need to ask the Kerberos administrator to add the SPNs to the principal database and create the keytab files. The SPN and keytab file names are case sensitive.
The infacmd isp PrintSPNAndKeytabNames command uses the following syntax: 
PrintSPNAndKeytabNames

<-DomainName|-dn> domain_name

<-ServiceRealmName|-srn> realm_name_of_node_spn

[<-Format|-fm> format_TEXT_CSV]

[<-OutputFile|-of> output_file_name]

[<-DomainNodes|-dns> Node1:HostName1 Node2:HostName2 ...]

[<-ServiceProcesses|-sps> ServiceName1:NodeName1 ServiceName2:NodeName2...]

[<-SPNShareLevel|-spnSL> SPNShareLevel PROCESS|NODE]
The following table describes infacmd isp PrintSPNAndKeytabNames options and arguments:
Option
Argument
Description
-DomainName
-dn
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.
-ServiceRealmName
-srn
realm_name_of_node_spn
Required. Name of the Kerberos realm to which the Informatica domain services belong. The realm name must be in uppercase and is case sensitive.
-Format
-fm
format_TEXT_CSV
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
-of
output_file_name
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.
-DomainNodes
-dns
NodeName:HostName
[NodeName:Hostname]
Name of the node and the fully qualified host name of the machine that hosts the node. Use the following format: NodeName:HostName
You can generate SPNs and keytab file names for multiple nodes. Separate each node name and host name pair with a space.
-ServiceProcesses
-sps
ServiceName:Nodename
[ServiceName:Nodename]
Optional. Name of the service that you want to create in the Informatica domain and the name of the node on which the service will run. Use the following format: ServiceName:NodeName
You can generate SPNs and keytab file names for multiple services. Separate each service name and node name pair with a space.
Note:
 The keytab files for application services in the domain do not have to be available when you configure the domain to use Kerberos authentication. You can add the service SPN to the principal database and create the keytab after you change the Informatica domain authentication but before you enable the service.
SPNShareLevel
-spnSL
SPNShareLevel
PROCESS|NODE]
Optional. Indicates the service principal level for the domain. Set the property to one of the following levels:
  • Process. The domain requires a unique service principal name (SPN) and keytab file for each node and each service on a node. The number of SPNs and keytab files required for each node depends on the number of service processes that run on the node. Recommended for production domains.
  • Node. The domain uses one SPN and keytab file for the node and all services that run on the node. It also requires a separate SPN and keytab file for all HTTP processes on the node. Recommended for test and development domains. Recommended for test and development domains.
Default is process.
0 COMMENTS
We’d like to hear from you!