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

enableMappingValidationEnvironment

enableMappingValidationEnvironment

Enables a mapping validation environment for mappings that you run from the Developer tool. The mapping validation environment properties indicate the engines that the mapping will be validated to run in.
Use the ValidationEnvironment parameter to specify a validation environment to enable on a mapping. Repeat the command and specify a different validation environment to enable an additional validation environment for the mapping.
Use filters to update one or more mappings in a project. If you do not include filters, the command updates all mappings that are not deployed to the Data Integration Service. A mapping must match all specified filters to be modified.
The infacmd mrs enableMappingValidationEnvironment uses the following syntax: 
enableMappingValidationEnvironment
<-DomainName|-dn> domain_name
[<-SecurityDomain|-sdn> security_domain]
<-UserName|-un> user_name
<-Password|-pd> password
<-ServiceName|-sn> service_name
[<-ProjectName|-pn> project_name]
[<-ConnectionName|-cn> connection_name]
[<-MappingNamesFilter|-mnf> mapping_names]
[<-ExecutionEnvironmentFilter|-eef> execution_environment_name]
[<-ExecutionEnvironmentParameterNameFilter|-pnf> parameter name]
[<-ExecutionEnvironmentParameterDefaultValueFilter|-pdvf> parameter default value]
<-ValidationEnvironment|-ve> validation_environment_name
[<-ResilienceTimeout|-re> timeout_period_in_seconds]
The following table describes the enableMappingValidationEnvironment 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.
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 LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
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. Name of the Model Repository Service.
ProjectName
-pn
project_name
Optional. Name of the project that contains the mapping. If you do not specify a project name, the command updates all projects in the Model repository.
You can specify only one project at a time.
ConnectionName
-cn
connection_name
Name of the connection for the mapping validation environment to use. The connection overwrites an existing connection or connection parameter that was set for the environment.
Required to enable the native or non-native environment if no connection is present in the specified mapping. Optional to enable the native environment or if a connection is already present.
MappingNamesFilter
-mnf
mapping_names
Optional. The names of mappings that you want to enable the validation environment for. Separate mapping names with commas.
Default is all mappings in the Model repository.
ExecutionEnvironmentFilter
-eef
execution_environment_name
Optional. Specify the execution environment to filter on. You can enter either Native, Hadoop, or Databricks.
By default, the validation environment is changed for all engines based on other filter criteria.
ValidationEnvironment
-ve
validation_environment_name
Required. Name of the validation environment to enable on a mapping. You can enter one of the following values:
  • native
  • blaze
  • spark
  • spark-databricks
Run the command for each validation environment to enable.
ExecutionEnvironmentParameterNameFilter
-pnf
name_of_parameter
Optional. Selects only mappings whose parameter name matches this value.
Example:
infacmd.sh mrs enableValidationEnvironment -pnf MyParam -ve Databricks
ExecutionEnvironmentParameterDefaultValueFilter
-pdvf
parameter_default_value
Optional. Selects only mappings whose default parameter name matches this value.
Example:
infacmd.sh mrs enableValidationEnvironment -pdvf Hadoop -ve Databricks
ResilienceTimeout
-re
timeout_period_in_seconds
Optional. Amount of time in seconds that infacmd attempts to establish or re-establish 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.
0 COMMENTS
We’d like to hear from you!