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

runMapping

runMapping

Runs a mapping that is deployed to a Data Integration Service. You can run the mapping with a parameter set or a parameter file.
To create a parameter file for a mapping, run infacmd ms listMappingParams.
Before you run infacmd ms listMappingParams, run the infacmd dis startApplication command for the application.
To view the parameters and values for a parameter set, run the command infacmd dis listParameterSetEntries.
The infacmd ms runMapping command uses the following syntax: 
runMapping

<-DomainName|-dn> domain_name

<-ServiceName|-sn> service_name

<-UserName|-un> user_name

<-Password|-pd> password

[<-SecurityDomain|-sdn> security_domain]

[<-ResilienceTimeout|-re> timeout_period_in_seconds]

<-Application|-a> application_name

<-Mapping|-m> mapping_name

[<-Wait|-w> true|false]

[<-ParameterFile|-pf> parameter_file_path]

[<-ParameterSet|-ps> parameter_set_name]

[<-OperatingSystemProfile|-osp> operating_system_profile_name]

[<-NodeName|-nn> node_name]

[<-OptimizationLevel|-ol> optimization_level]

[<-PushdownType|-pt> pushdown_type]

[<-CustomProperties|-cp> custom_properties]

[<-RuntimeInstanceName|-rin> runtime_instance_name]
The command returns the job ID for the mapping run.
You must enable monitoring to store the run-time instance name. If you purge monitoring statistics, run-time instance names are deleted and will not be returned by infacmd ms getMappingStatus. The mapping log might still contain the run-time instance name and the persisted mapping outputs associated with the run-time instance name can still be used.
The following table describes infacmd ms runMapping 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.
-ServiceName
-sn
service_name
Required. Name of the Data Integration Service to run the mapping. The application that contains the mapping must be deployed to a Data Integration Service.
-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 LDAP security domain created during installation. The name of the security domain is the same as the user realm specified during installation.
-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. You can set the resilience timeout period with the -re option or the environment variable INFA_CLIENT_RESILIENCE_TIMEOUT. If you set a the resilience timeout perioud with both methods, the -re option takes precedence.
-Application
-a
application_name
Required. Name of the application that contains the mapping.
-Mapping
-m
mapping_name
Required. Name of the mapping to run.
-Wait
-w
true|false
Optional. Indicates whether infacmd waits for the mapping to complete before returning to the shell or command prompt. If true, infacmd returns to the shell or command prompt after the mapping completes. You cannot run subsequent commands until the mapping completes. If false, infacmd returns to the shell or command prompt immediately. You do not have to wait for the mapping to complete before running the next command. Default is false.
-ParameterFile
-pf
parameter_file_path
Optional. Name and path of the parameter file. Do not enter a parameter file and a parameter set.
-ParameterSet
-ps
parameter_set_name
Optional. Name of a parameter set to use at run time. The parameter set option overrides any parameter set deployed with the application. Do not enter a parameter set and a parameter file.
-OperatingSystemProfile
-osp
operating_system_profile_name
Optional. Name of the operating system profile to run the mapping.
If you do not use this option when the Data Integration Service is enabled to use operating system profiles, the Data Integration Service runs the mapping with the default profile.
-NodeName
-nn
node_name
Optional. Name of the node in a Data Integration Service grid to dispatch the mapping job to. A Data Integration Service process must be running on the node.
If you do not use this option, the mapping job is dispatched to the node where the master Data Integration Service process runs.
-OptimizationLevel
-ol
optimization_level
Optional. Controls the optimization methods that the Data Integration Service applies to the mapping. Enter the numeric value that is associated with the optimization level that you want to configure. Enter one of the following values:
-1 (Auto)
The Data Integration Service applies optimizations based on the execution mode and mapping contents.
0 (None)
The Data Integration Service does not apply any optimization.
1 (Minimal)
The Data Integration Service applies the early projection optimization method.
2 (Normal)
The Data Integration Service applies the early projection, early selection, branch pruning, push-into, global predicate optimization, and predicate optimization methods.
3 (Full)
The Data Integration Service applies the cost-based, early projection, early selection, branch pruning, predicate, push-into, semi-join, and dataship-join optimization methods.
Default is -1 (Auto).
-PushdownType
-pt
pushdown_type
Optional. Controls the pushdown type that the Data Integration Service applies to a mapping. Enter one of the following values:
  • None. Select no pushdown type for the mapping.
  • Source. The Data Integration Service tries to push down as much transformation logic as it can to the source database.
  • Full. The Data Integration Service pushes the full transformation logic to the source database.
This option overrides the pushdown type set in the mapping run-time properties or in a parameter file or parameter set.
If you do not use this option, the Data Integration Service applies the pushdown type set in the mapping run-time properties or in a parameter file or parameter set.
-CustomProperties
-cp
custom_properties
Optional. Define custom properties for a mapping at the request of Informatica Global Customer Support.
Enter custom properties as name-value pairs separated by semicolons. For example: 
... -cp custom_property_name=value
To enter a value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
-RuntimeInstanceName
-rin
runtime_instance_name
Optional. Name of the run-time instance of the mapping. The name must be unique.
The run-time instance name cannot contain slash characters.
You must specify a run-time instance name in runMapping to persist mapping outputs and run the commands listMappingPersistedOutputs and deleteMappingPersistedOutputs.
You can set the value as follows to standardize run-time instance names:

    If all the mappings in an application use the same persisted mapping outputs, use the application name.

    If the mappings use different persisted mapping outputs, use a combination of the application name, mapping name, and parameter set or file name.

0 COMMENTS
We’d like to hear from you!