Shared Content for Data Engineering 10.5.2
- All Products
CreateService <-DomainName|-dn> DomainName <-NodeName|-nn> NodeName <-UserName|-un> Username <-Password|-pd> Password <-ServiceName|-sn> ServiceName <-HTTPProtocolType|-hp> HTTPProtocolType [<-HTTPPort|-pt> HTTPPort] [<-HTTPSPort|-spt> HTTPSPort] [<-HadoopServicePrincipalName|-hpn> HadoopServicePrincipalName] [<-HadoopKeyTab|-hkt> HadoopKeyTab] [<-ServiceDescription|-sd> ServiceDescription] [<-ResilienceTimeout|-re> ResilienceTimeout] [<-FolderPath|-fp> FolderPath] [<-BackupNodes|-bn> BackupNodes] [<-KeyStoreFile|-kf> KeyStoreFile] [<-KeystorePassword|-kp> KeystorePassword] [<-TruststoreFile|-tf> TruststoreFile] [<-TruststorePassword|-tp> TruststorePassword] [<-SecurityDomain|-sdn> SecurityDomain] [<-SSLProtocol|-sp> SSLProtocol] [<-loggedInUserAsImpersonationUser|-uiu> UseLoggedInUserAsImpersonationUser] [<-enableOSProfile|-osp> EnableOSProfile]
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.
Node where the Metadata Access Service runs. You can run the Data Integration Service only on a node.
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.
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.
Required. Name of the Metadata Access Service.
The name is not case sensitive and must be unique within the domain. The characters must be compatible with the code page of the associated repository. The name cannot exceed 230 characters, have leading or trailing spaces, or contain carriage returns, tabs, or the following characters:
Security protocol that the Metadata Access Service uses. Enter one of the following values:
When you set the HTTP protocol type to HTTPS, you enable Transport Layer Security (TLS) for the service.
Default is HTTP.
Required if you do not specify an HTTPS port. Unique HTTP port number used for each Metadata Access Service process. After you create the service, you can define different port numbers for each Metadata Access Service process.
Default is 7080. The Metadata Access Service uses consecutive port numbers to connect to multiple Hadoop distributions.
Required if you do not specify an HTTP port. Unique HTTPS port number used for each Metadata Access Service process. After you create the service, you can define different port numbers for each Metadata Access Service process.
The Metadata Access Service uses consecutive port numbers to connect to multiple Hadoop distributions.
Service Principal Name (SPN) of the Metadata Access Service to connect to a Hadoop cluster that uses Kerberos authentication.
Not applicable for the MapR distribution.
The file path to the Kerberos keytab file on the machine on which the Metadata Access Service runs.
Not applicable for the MapR distribution.
Optional. Service description.
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 the resilience timeout period with both methods, the -re option takes precedence.
Optional. Full path, excluding the domain name, to the folder in which you want to create the Metadata Access Service. Must be in the following format:
Default is “/” (the domain).
Optional. Nodes on which the service can run if the primary node is unavailable. You can configure backup nodes if you have high availability.
Path and file name of the keystore file that contains the keys and certificates required if you use the HTTPS protocol for the Metadata Access Service. You can create a keystore file with a keytool. keytool is a utility that generates and stores private or public key pairs and associated certificates in a keystore file. You can use the self-signed certificate or use a certificate signed by a certificate authority.
Password for the keystore file.
Required when the domain is SSL- enabled. Domain truststore file location in the cluster.
Required when the domain is SSL- enabled. Truststore domain password.
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.
Optional. Secure Sockets Layer protocol to use.
Optional. Enter a user name for the Metadata Access Service to impersonate when it connects to a Hadoop environment.
Required if the Hadoop cluster uses Kerberos authentication. Hadoop impersonation user. The user name that the Metadata Access Service impersonates to import metadata from the Hadoop environment at design time.
Indicates that the Metadata Access Service can use operating system profiles for metadata preview.
Default is false.
Updated June 17, 2022