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

CreateService

CreateService

Creates a Catalog Service. Before you create a Catalog Service, you need to ensure that you import the Hadoop cluster certificates to the domain trust store for a Hadoop cluster that uses SSL protocol.
The infacmd ldm CreateService command uses the following syntax:
CreateService <-DomainName|-dn> domain_name <-NodeName|-nn> node_name [<-SecurityDomain|-sdn> security_domain] <-UserName|-un> user_name <-Password|-pd> password <-ServiceName|-sn> service_name [<-ResilienceTimeout|-re> timeout_period_in_seconds] <-ModelRepositoryService|-mrs> model_repository_service_name <-MRSUserName|-mrsun> model_repository_service_user_name <-MRSPassword|-mrspd> model_repository_service_user_password [<-MRSSecurityDomain|-mrssdn> model_repository_service_user_security_domain] [<-HttpPort|-p> port_name] [<-HttpsPort|-sp> https_port_name] [<-EnableTls|-tls> enable_tls true|false] [<-KeystoreFile|-kf> keystore_file_location] [<-KeystorePassword|-kp> keystore_password] [<-SSLProtocol|-sslp> ssl_protocol] [<-IsExternalCluster|-ise> is_external_cluster true|false] [<-ClusterHadoopDistributionType|-chdt> Cluster_Hadoop_Distribution_Type ClouderaManager|HortonWorks|HDInsight|Others (default Others)] [<-ClusterHadoopDistributionURL|-chdu> Cluster_Hadoop_Distribution_URL] [<-ClusterHadoopDistributionURLUser|-chduu> Cluster_Hadoop_Distribution_URL_User] [<-ClusterHadoopDistributionURLPwd|-chdup> Cluster_Hadoop_Distribution_URL_Pwd] [<-ClusterNameHadoopDistribution|-cnhd> Cluster_Name_Hadoop_Distribution] [<-InfaHadoopServiceName|-ihsn> infa_hadoop_service_name] [<-ZookeeperURI(s)|-zk> zk_uris] [<-HDFSNameNodeURI(s)|-hnnu> hdfs_namenode_uri] [<-YarnRMUri(s)|-yrmu> yarn_resource_manager_uri] [<-YarnRMHttpUri(s)|-yrmhu> yarn_resource_manager_http_uri] [<-HistoryServerHttpUri|-hshu> history_server_http_uri] [<-YarnRMSchedulerUri(s)|-yrmsu> yarn_resource_manager_scheduler_uri] [<-ServiceClusterName|-scn> service_cluster_name] [<-HdfsServiceNameHA|-hsn> hdfs_service_name] [<-IsClusterSecure|-isc> is_cluster_secure true|false] [<-HdfsServicePrincipal|-hspn> hdfs_service_principal] [<-YarnServicePrincipal|-yspn> yarn_service_principal] [<-KdcDomain|-kdn> kdc_domain_name] [<-KeytabLocation|-kl> keytab_location] [<-ClusterSslEnabled|-cssl> cluster_ssl_enabled true|false] [<-SolrKeyStoreFile|-skf> solr keystore file path on cluster] [<-loadType|-lt> Load Type, demo|low|medium|high (default 'low')] [<-SolrKeyStorePassword|-skp> solr keystore password] [<-isEmailEnabled|-iee> is_email_enabled true:false] [<-OtherOptions|-oo> other options] [<-BackupNodes|-bn> node_name1,node_name2,...] [<-isNotifyChangeEmailEnabled|-cne> is_notify_change_email_enabled true:false (default false)] <-EnableDataAssetAnalytics|-ed> Enable Data Asset Analytics(true, false). If you enable this option, make sure that you configure the following parameters: DataAssetAnalyticsDBSelect, DataAssetAnalyticsDBUsername, DataAssetAnalyticsDBPassword, DataAssetAnalyticsDBURL [<-DataAssetAnalyticsDBSelect|-ddt> Select the database for Data Asset Analytics (ORACLE, SQLSERVER or POSTGRESQL)] [<-DataAssetAnalyticsDBUsername|-ddu> Username to access the database] [<-DataAssetAnalyticsDBPassword|-ddp> Password configured for the username] [<-DataAssetAnalyticsDBURL|-ddl> Database connection string. Make sure that the connection string starts with 'jdbc:informatica:'] [<-DataAssetAnalyticsDBSchema|-dds> Database schema name (applicable if you had selected SQL Server or PostgreSQL as the database type.)] [<-DataAssetAnalyticsSecureJDBCParameters|-dsjdbcp> Secure JDBC connection parameters]
The following table describes infacmd ldm CreateService 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.
-NodeName
-nn
node_name
Required. Node where you want to run the Catalog Service to run.
-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. Catalog Service name.
-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.
-ModelRepositoryService
-mrs
model_repository_service_name
Required. Model Repository Service name to associate with the Catalog Service.
-MRSUserName
-mrsun
model_repository_service_user_name
Required if you specify a Model Repository Service. User name to connect to the Model repository.
If you enter a user name that contains a space or other non-alphanumeric character, enclose the name in quotation marks.
-MRSPassword
-mrspd
model_repository_service_user_password
Required if you specify a Model Repository Service.
User password for the Model Repository Service.
-MRSSecurityDomain
-mrssdn
model_repository_service_user_security_domain
Required if you use LDAP authentication. Name of the security domain to which the Administrator user belongs.
-HttpPort
-p
port_name
Required. A unique HTTP port number used for each Catalog Service process. The default port number is 9085.
-HttpsPort
-sp
https_port_name
Required if you enable Transport Layer Security. Port number for the HTTPS connection.
-EnableTls
-tls
enable_tls
Select this option to enable Transport Layer Security.
-KeystoreFile
-kf
keystore_file_location
Required if you select Enable Transport layer Security. Path and file name of the keystore file. The keystore file contains the keys and certificates required if you use the SSL security protocol with Catalog Administrator.
-KeystorePassword
-kp
keystore_password
Required if you select Enable Transport layer Security. The password for the keystore file.
-SSLProtocol
-sslp
ssl_protocol
Optional. Secure Sockets Layer protocol to use.
-IsExternalCluster
-ise
is_external_cluster
Indicates the deployment type for Enterprise Information Catalog. You can choose to deploy in an internal Hadoop cluster or an external Hadoop cluster.
-InfaHadoopServiceName
-ihsn
infa_hadoop_service_name
Required. Name of the Hadoop service for the embedded cluster.
-ClusterHadoopDistributionType
-chdt
Cluster_Hadoop_Distribution_Type
Required for external clusters. The type of the Cluster Hadoop Distribution.
-ClusterHadoopDistributionURL
-chdu
Cluster_Hadoop_Distribution_URL
Required for external clusters. The URL for the Cluster Hadoop Distribution.
ClusterHadoopDistributionURLUser
-chduu
Cluster_Hadoop_Distribution_URL_User
Required for external clusters. The username for the Cluster Hadoop Distribution.
ClusterHadoopDistributionURLPwd
-chdup
Cluster_Hadoop_Distribution_URL_Pwd
Required for external clusters. The password for the Cluster Hadoop Distribution.
ClusterNameHadoopDistribution
-cnhd
Cluster_Name_Hadoop_Distribution
Required for external clusters. The name of the Cluster Hadoop Distribution. If Enterprise Data Catalog is deployed on a Cloudera Hadoop Distribution then it has multiple cluster environment.
-ZookeeperURI
-zk
zk_uris
Required only if you choose the option Others for the cluster type. The URI for the Zookeeper service, which is a high-performance coordination service for distributed applications.
Multiple Zookeeper URI values are separated by commas.
-HDFSNameNodeURI
-hnnu
hdfs_namenode_uri
Required only if you choose the option Others for the cluster type. The URI to access HDFS.
Use the following format to specify the NameNode URI in the Cloudera distribution:
hdfs://<namenode>:<port>
Where
- <namenode> is the host name or IP address of the NameNode.•
- <port> is the port that the NameNode listens for Remote Procedure Calls (RPC).
For high availability enabled cluster, enter all the Hadoop namenode URI values separated by commas.
-YarnRMUri
-yrmu
yarn_resource_manager_uri
Required only if you choose the option Others for the cluster type. The service within Hadoop that submits the MapReduce tasks to specific nodes in the cluster.
Use the following format:
<hostname>:<port>
Where-
- Hostname is the name or IP address of the Yarn resource manager.-
- Port is the port number on which Yarn resource manager listens for Remote Procedure Calls (RPC).
For high availability enabled cluster, enter all the resource manager URI values separated by commas.
-YarnRMHttpUri
-yrmhu
yarn_resource_manager_http_uri
Required only if you choose the option Others for the cluster type. http URI value for the Yarn resource manager.
For high availability enabled cluster, enter all the resource manager URI values separated by commas.
-HistoryServerHttpUri
-hshu
history_server_http_uri
Required only if you choose the option Others for the cluster type. Enter a value to generate the Yarn allocation log for scanners. When you Provide the value, the Catalog Administrator displays the log URL as part of task monitoring.
-YarnRMSchedulerUri
-yrmsu
yarn_resource_manager_scheduler_uri
Required only if you choose the option Others for the cluster type. Scheduler URI value for the Yarn resource manager.
For high availability enabled cluster, enter all the resource manager URI values separated by commas.
-ServiceClusterName
-scn
service_cluster_name
Optional. Name of the service cluster.
-HdfsServiceNameHA
-hsn
hdfs_service_name
Optional. Required for high availability enabled cluster. Name of the HDFS service. Applicable if you select Others as the Cluster type.
-IsClusterSecure
-isc
is_cluster_secure
Applies to external cluster. Choose to enable cluster authentication.
-HdfsServicePrincipal
-hspn
hdfs_service_principal
Required when the cluster type is others. Principal name for the HDFS service. Applicable only if isClusterSecure is set to true.
-YarnServicePrincipal
-yspn
yarn_service_principal
Required when the cluster type is others. Principal name for the Yarn service. Applicable only if isClusterSecure is set to true.
-KdcDomain
-kdn
kdc_domain_name
Required. Kerberos domain name. Applicable only if isClusterSecure is set to true.
-KeytabLocation
-kl
keytab_location
Required. Path to the keytab file. A keytab file contains all the users in LDAP. Applicable only if isClusterSecure is set to true.
-ClusterSslEnabled
-cssl
cluster_ssl_enabled
Optional. Select the option to enable cluster SSL.
-SolrKeyStoreFile
-skf
Solr_KeyStore_File
Required if you set ClusterSSl Enabled to true. Solr keystore file path in cluster.
-SolrKeyStorePassword
-skp
Solr_KeyStore_Password
Required if you set ClusterSSl Enabled to true. Password for Solr keystore .
-loadType
-lt
Load Type
Optional. Specify one of the following load type values:
  • Demo
  • Low
  • Medium
  • High
Default is low.
-isEmailEnabled
-iee
is_email_enabled
Optional. Specify True if you want to enable email notification. Default is False.
-OtherOptions
-oo
other options
Optional. Enter name-value pair separated by spaces. To enter an option value that contains a space or other non-alphanumeric character, enclose the value in quotation marks.
-BackupNodes
-bn
node_name1,node_name2,...
Optional. Nodes on which the service can run if the primary node is unavailable. You can configure backup nodes if you have high availability.
-isNotifyChangeEmailEnabled
-cne
is_notify_change_email_enabled
Optional. Specify True if you want to enable asset change notifications. Default is False.
-EnableDataAssetAnalytics
-ed
Enable Data Asset Analytics(true, false)
Required. Specify True if you want to enable Data Asset Analytics with Enterprise Data Catalog. If you enable this option, make sure that you configure the following parameters:
  • DataAssetAnalyticsDBSelect
  • DataAssetAnalyticsDBUsername
  • DataAssetAnalyticsDBPassword
  • DataAssetAnalyticsDBURL
-DataAssetAnalyticsDBSelect
-ddt
Select the database for Data Asset Analytics (ORACLE, SQLSERVER or POSTGRESQL)
Required if the
EnableDataAssetAnalytics
option value is set to true.
Applies to the following databases:
  • Oracle
  • SQL Server
  • PostgreSQL
-DataAssetAnalyticsDBUsername
-ddu
Username to access the database
Required if the
EnableDataAssetAnalytics
option value is set to true. Specify the username to access the database for Data Asset Analytics.
DataAssetAnalyticsDBPassword
-ddp
Password configured for the username
Required if the
EnableDataAssetAnalytics
option value is set to true. Specify the password to access the database for Data Asset Analytics.
DataAssetAnalyticsDBURL
-ddl
Database connection string
Required if the
EnableDataAssetAnalytics
option value is set to true. Specify the database connection string. Make sure that the connection string starts with
'jdbc:informatica:'
DataAssetAnalyticsDBSchema
-dds
Database schema name
Optional. Specify the database schema name. Applicable if you had selected SQL Server or PostgreSQL as the database type.
DataAssetAnalyticsSecureJDBCParameters
-dsjdbcp
Secure JDBC connection parameters
Optional. If the database for Data Asset Analytics is secured with the SSL protocol, you must enter the secure database parameters. Enter the parameters in the form of key-value pairs separated by a semi-colon. For example:
param1=value1;param2=value2

0 COMMENTS

We’d like to hear from you!