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

GetWorkflowLog

GetWorkflowLog

Gets log events for the most recent run of a workflow. The PowerCenter Repository Service must be running when you run this command.
The infacmd isp GetWorkflowLog command uses the following syntax: 
GetWorkflowLog

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

[<-Format|-fm> format_TEXT_XML_BIN]

[<-OutputFile|-lo> output_file_name]

<-IntegrationService|-is> integration_service_name

<-RepositoryService|-rs> repository_service_name

[<-RepositoryDomain|-rd> domain_of_repository]

<-RepositoryUser|-ru> repository_user

<-RepositoryPassword|-rp> repository_password

[<-RepositoryUserSecurityDomain|-rsdn> repository_user_security_domain]

<-FolderName|-fn> repository_folder_name

<-Workflow|-wf> workflow_name

[<-RunInstance|-in> run_instance_name] | <-RunId|-id> workflow_run_id]
If you do not specify -un, -pd, and -sdn options, the infacmd isp GetWorkflowLog command uses the corresponding values from the -ru, -rp, and the -rsdn options.
The following table describes infacmd isp GetWorkflowLog 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.
-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.
If the domain uses native or LDAP authentication, the default is Native. If the domain uses Kerberos authentication, the default is the user realm specified during installation.
-Gateway
-hp
gateway_host1:port gateway_host2:port
...
Required if the gateway connectivity information in the domains.infa file is out of date. The host names and port numbers for the gateway nodes in the domain.
‑ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or reestablish a connection to the domain. If you omit this option, infacmd uses the timeout value specified in the INFA_CLIENT_RESILIENCE_TIMEOUT environment variable. If no value is specified in the environment variable, the default of 180 seconds is used.
-Format
-fm
format
Optional. Format for the session log. Valid types include:
  • Text
  • XML
  • Bin (binary)
If you choose binary, then you must specify a file name using the OutputFile option.
If you do not specify a format,
infacmd
 uses text format with lines wrapped at 80 characters.
-OutputFile
-lo
output_file_name
Name and file path for the workflow log file. By default, the Service Manager uses the server\infa_shared\log directory on the master gateway node. Omit this option to display the log events on the screen. If you choose binary as the output file type, you must specify a file name using this option.
‑IntegrationService
-is
integration_service_name
Required. Name of the Integration Service that runs the workflow. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-RepositoryService
-rs
repository_service_name
Required. Name of the Repository Service that contains the workflow. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-RepositoryDomain
-rd
domain_of_repository
Required if the repository is in a domain other than the local domain. Domain of the Repository Service. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-RepositoryUser
-ru
user
Required for native or LDAP authentication. Optional if the domain uses Kerberos authentication. User name used to connect to the repository. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-RepositoryPassword
-rp
password
Required for native or LDAP authentication. Optional if the domain uses Kerberos authentication. User password. You can set a password with the -rp option or the environment variable INFA_REPOSITORY_PASSWORD. If you set a password with both methods, the password set with the -rp option takes precedence.
-RepositoryUserSecurityDomain
-rsdn
repository_user_security_domain
Required for LDAP or Kerberos authentication. Optional if the domain uses native authentication. Name of the security domain to which the PowerCenter repository user belongs.
The security domain name is case sensitive. If you do not specify this option, the command sets the repository user security domain to native.
-FolderName
-fn
repository_folder_name
Required. Name of the folder containing the workflow. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-Workflow
-wf
workflow_name
Required. Name of the workflow. To enter a name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-RunInstance
-in
run_instance_name
Name of the workflow run instance. Use this option if you are running concurrent workflows. Use the -in or the -id option, not both.
-RunId
-id
workflow_run_id
Run identifier number (Run ID) of the workflow run instance. Use this option if you are running concurrent workflows. Use the -in or the -id option, not both.
Use this option if the workflow does not have a unique run instance name.
0 COMMENTS
We’d like to hear from you!