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

CreateService

CreateService

Creates a Metadata Access Service. The Metadata Access Service is an application service that allows the Developer tool to access Hadoop connection information to import and preview metadata.
The infacmd mas CreateService command uses the following syntax: 
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]
The following table describes infacmd mas 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
Node where the Metadata Access Service runs. You can run the Data Integration Service only on a node.
-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 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: 
/ * ? < > " |
-HTTPProtocolType
-hp
http_protocol_type
Security protocol that the Metadata Access Service uses. Enter one of the following values:
  • HTTP. Requests to the service must use an HTTP URL.
  • HTTPS. Requests to the service must use an HTTPS URL.
When you set the HTTP protocol type to HTTPS, you enable Transport Layer Security (TLS) for the service.
Default is HTTP.
-HTTPPort
-pt
http_port
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.
-HTTPSPort
-spt
https_port
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.
-HadoopServicePrincipalName
-hpn
hadoop_spn
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.
-HadoopKeyTab
-hkt
keytab_file_path
The file path to the Kerberos keytab file on the machine on which the Metadata Access Service runs.
Not applicable for the MapR distribution.
-ServiceDescription
-sd
service_description
Optional. Service description.
-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 the resilience timeout period with both methods, the -re option takes precedence.
-FolderPath
-fp
full_folder_path
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:
/parent_folder/child_folder
Default is “/” (the domain).
-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.
-KeystoreFile
-kf
keystore_file_location
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.
-KeystorePassword
-kp
keystore_password
Password for the keystore file.
-TruststoreFile
-tf
trust_store_file
Required when the domain is SSL- enabled. Domain truststore file location in the cluster.
-TruststorePassword
-tp
trust_store_password
Required when the domain is SSL- enabled. Truststore domain password.
-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.
-SSLProtocol
-sp
ssl_protocol
Optional. Secure Sockets Layer protocol to use.
-HadoopImpersonationUser
-hu
hadoop_impersonation_user
Optional. Enter a user name for the Metadata Access Service to impersonate when it connects to a Hadoop environment.
-loggedInUserAsImpersonationUser
-uiu
use_logged_in_user_as_proxy
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.
-enableOSProfile
-osp
enable_OS_profile
Indicates that the Metadata Access Service can use operating system profiles for metadata preview.
Default is false.
0 COMMENTS
We’d like to hear from you!