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

collectAppLogs

collectAppLogs

Collects log files for YARN applications that run to enable the Catalog Service.
The infacmd ldm collectAppLogs command uses the following syntax:
The collectAppLogs command is not supported if you have deployed Enterprise Data Catalog on a Cloudera cluster. This command works only for the Hortonworks Data Platform (HDP) clusters and Enterprise Data Catalog deployed on HDP embedded clusters. 
collectAppLogs 

        <-DomainName|-dn> domain_name

        <-UserName|-un> user_name

        <-Password|-pd> password

        <-ServiceName|-sn> service_name

        <-OutputZipFileName|-of> output zip file name 

        [<-ApplicationStartDate|-ad>

        [<-LdmApplicationTypes|-at>
        
        [<-SecurityDomain|-sdn> security_domain]

        [<-ResilienceTimeout|-re> timeout_period_in_seconds]

        [<-CustomClientUserPrincipal|-ccup> custom_client_user_principal 
        
        [<-CustomKeytabFile|-ckf> custom_keytab_file_location
The following table describes infacmd ldm collectAppLogs 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.
-UserName
-un
user_name
Required if the domain uses Native or LDAP authentication. User name to connect to the domain. You can set the user name with the -un option or the environment variable INFA_DEFAULT_DOMAIN_USER. If you set a user name with both methods, the -un option takes precedence.
Optional if the domain uses Kerberos authentication. To run the command with single sign-on, do not set the user name. If you set the user name, the command runs without single sign-on.
-Password
-pd
password
Required if you specify the user name. Password for the user name. The password is case sensitive. You can set a password with the -pd option or the environment variable INFA_DEFAULT_DOMAIN_PASSWORD. If you set a password with both methods, the password set with the -pd option takes precedence.
-ServiceName
-sn
service_name
Required. Catalog Service name.
-OutputZipFileName
-of
output zip file name
Required. Absolute path of the ZIP file on local machine to which the logs will be collected. The zip file will be created if it doesn't already exist, overwritten otherwise.
-ApplicationStartDate
-ad
Application Start Date
Optional. The start date of applications to be fetched in the format
MM/dd/yyyy
. Logs for all applications with start date after this will be fetched. If you do not provide the date, the latest YARN log file is fetched.
-LdmApplicationTypes
-at
ApplicationTypes
Comma separated values of the Ldm application types that you want to fetch. Accepted types are hbase/solr/ingestion. Example value: 'hbase,solr,ingestion' or simply 'ingestion'). By default, it would collect logs for all 3 types.
-SecurityDomain
-sdn
security_domain
Required if the domain uses LDAP authentication. Optional if the domain uses native authentication or Kerberos authentication. Name of the security domain to which the domain user belongs. You can set a security domain with the -sdn option or the environment variable INFA_DEFAULT_SECURITY_DOMAIN. If you set a security domain name with both methods, the -sdn option takes precedence. The security domain name is case sensitive.
-ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or reestablish a connection to the domain. You can set the resilience timeout period with the -re option or the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If you set the resilience timeout period with both methods, the -re option takes precedence.
-CustomClientUserPrincipal|
-ccup
custom_client_user_principal
Optional. User with required permissions on the specified directory for backup and restore in a Kerberos-enabled cluster. The default user is the Catalog Administrator user. Use format:<serviceClusterName>@<kerberosDomain>)
-CustomKeytabFile
-ckf
custom_keytab_file_location
Optional. Location of the custom keytab file. The default location for the file is the location where the Catalog Administrator keytab file exists.
0 COMMENTS
We’d like to hear from you!