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

createConfigurationWithParams

createConfigurationWithParams

Creates a cluster configuration through cluster parameters that you specify in the command line.
The cluster configuration is an object in the domain that contains configuration information about the compute cluster.
The infacmd cluster
createConfigurationWithParams
command uses the following syntax:
createConfigurationWithParams <-DomainName|-dn> domain_name <-UserName|-un> user_name <-Password|-pd> password [<-SecurityDomain|-sdn> security_domain] [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ConfigurationName|-cn> configuration_name <-DistributionType|-dt> CDH|EMR|HDI|HDP|MAPR|DATAPROC|DATABRICKS [<-DistributionVersion|-dv> distribution_version] <-Parameters|-params> parameters, separated by space in the form of name=value. Use single quote to escape any equal sign or space in the value.
The following table describes infacmd cluster
createConfigurationWithParams
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 or if you import properties directly from the cluster. 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.
-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.
-ConfigurationName
-cn
Name of the cluster configuration
Required. The cluster configuration name must meet the following requirements:
  • Unique within the domain
  • Cannot exceed 128 characters
  • Cannot contain white spaces or the following special characters:
    • ~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? /
Values are not case sensitive.
-DistributionType
-distType
Distribution
Required. One of the following distribution types:
  • CDH. Cloudera CDH or Cloudera CDP.
  • EMR. Amazon EMR.
  • HDI. Azure HDInsight.
  • HDP. Hortonworks HDP.
  • MAPR
  • DATAPROC
  • DATABRICKS
Values are not case sensitive.
-DistributionVersion
-dv
Distribution version
Optional. Specify a distribution version other than the default version.
Each distribution has a default version. Use the -dv option to specify a different supported version to apply to the cluster configuration.
Default is the most recent distribution version that Big Data Management supports.
-Parameters
-params
Parameters
Separated by space in the form of name=value. Use single quote to escape any equal sign or space in the value.
You can use the following parameters for each distribution :
  • Databricks:

      url

      accesstoken

      clusterid

  • All other distribution types:

      host

      port

      username

      password

      clustername


0 COMMENTS

We’d like to hear from you!