Success
Manage your Success Plans and Engagements, gain key insights into your implementation journey, and collaborate with your CSMs
Customer Experience Accelerators
Accelerate your Purchase to Value by engaging with Informatica for Customer Success
My Engagements
All your Engagements at one place
 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
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Experience Lounge
Self-guided, intuitive experience platform for outcome-focused product capabilities and use cases
 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
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
SupportFlash
Monthly support newsletter
Product Availability Matrix
Product Availability Matrix statements of Informatica products
Product Lifecycle
End of Life statements of Informatica products
Pulse
Monitor the status of your Informatica services across regions
Events
Change Request Tracking
Marketplace
Trust Platform
Deutsch
  • Data Engineering Integration 10.2.1
  • Alle Produkte

Inhaltsverzeichnis

Search

  1. Vorwort
  2. Befehlszeilenprogramme und Dienstprogramme
  3. Installieren und Konfigurieren von Befehlszeilendienstprogrammen
  4. Verwenden der Befehlszeilenprogramme
  5. Umgebungsvariablen für Befehlszeilenprogramme
  6. Verwenden von infacmd
  7. infacmd as-Befehlsreferenz
  8. infacmd aud-Befehlsreferenz
  9. infacmd autotune-Befehlsreferenz
  10. Infacmd bg-Befehlsreferenz
  11. infacmd ccps-Befehlsreferenz
  12. infacmd cluster-Befehlsreferenz
  13. infacmd cms-Befehlsreferenz
  14. infacmd dis-Befehlsreferenz
  15. infacmd dps-Befehlsreferenz
  16. infacmd edl-Befehlsreferenz
  17. Infacmd es-Befehlsreferenz
  18. infacmd ihs-Befehlsreferenz
  19. infacmd ipc-Befehlsreferenz
  20. infacmd isp Command Reference
  21. infacmd ldm-Befehlsreferenz
  22. infacmd mas-Befehlsreferenz
  23. infacmd mi-Befehlsreferenz
  24. infacmd mrs-Befehlsreferenz
  25. infacmd ms-Befehlsreferenz
  26. Infacmd oie-Befehlsreferenz
  27. infacmd ps-Befehlsreferenz
  28. infacmd pwx-Befehlsreferenz
  29. infacmd rms-Befehlsreferenz
  30. infacmd rtm-Befehlsreferenz
  31. infacmd sch-Befehlsreferenz
  32. infacmd search-Befehlsreferenz
  33. infacmd sql-Befehlsreferenz
  34. infacmd tdm-Befehlsreferenz
  35. infacmd wfs-Befehlsreferenz
  36. infacmd ws-Befehlsreferenz
  37. infacmd xrf-Befehlsreferenz
  38. infacmd-Steuerdateien
  39. infasetup-Befehlsreferenz
  40. Pmcmd-Befehlsreferenz
  41. pmrep-Befehlsreferenz
  42. Arbeiten mit pmrep-Dateien

Command Reference

Command Reference

Zurück Weiter

createService

createService

Creates a Data Preparation Service.
The infacmd dps createService command uses the following syntax: 
createService

<-DomainName|-dn> domain_name

<-UserName|-un> user_name

<-Password|-pd> password

[<-SecurityDomain|-sdn> security_domain]

[<-ResilienceTimeout|-re> timeout_period_in_seconds]

<-ServiceName|-sn> service_name

<-NodeName|-nn> node_name | <-GridName|-gn> grid_name

[<-BackupNodes|-bn> node_name1,node_name2,...]

<-ServiceOptions|-so> option_name=value ...(HDFSConnection*,HiveConnection*,HadoopConnection*,HDFSSystemDirectory*,HiveTableStorageFormat(DefaultFormat|Parquet|ORC (default DefaultFormat)),LogLevel(FATAL|ERROR|WARNING|INFO|TRACE|DEBUG (default INFO)),customLogDirectory,SecurityMode(nonsecure|kerberos (default nonsecure)),IDLKerberosPrincipal(Principal Name for User Impersonation),IDLKerberosKeyTabFileName(SPN Keytab File for User Impersonation), LogAuditEvents(true|false (default false)),JDBCPort,ZeppelinURL,MaxFileUploadSize(default=512MB),DownloadRowsSize(default=1000000),MaxRecommendations(default=10),MaxSampleSize(default=50000),SampleSize(default=50000),hiveExecutionEngine(MR|Spark|Tez|Cluster-Default (default=Cluster-Default),LocalSystemDirectory*,SolrJVMOptions,IndexDir)

[<-LicenseName|-ln> license_name]

<-RepositoryServiceName |-rs> repository_service_name

<-RepositoryUser|-rsun> repository_user

[<-RepositoryPassword|-rspd> repository_password]

[<-RepositorySecurityDomain|-rssdn> model_repository_security_domain]

<-DISServiceName|-dsn> dis_service_name

<<-HttpPort|-hp> http_port|<-HttpsPort|-hsp> https_port>

[<-KeystoreFile|-kf> keystore_file_location]

[<-KeystorePassword|-kp> keystore_password]

[<-TruststoreFile|-tsf> truststore_file_location]

[<-TruststorePassword|-tsp> truststore_password]

[<-RulesServerPort|-rpo> RulesServerPort]

[<-SolrPort|-spo> SolrPort]

<-maxHeapSize|-mxhs> maxHeapSize]

[<-FolderPath|-fp> full_folder_path]
The following table describes infacmd dps 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.
-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 the resilience timeout period with both methods, the -re option takes precedence.
-ServiceName
-sn
service_name
Required. Name of the Data Preparation Service.
You cannot change the name of the service after you create it. The name is not case sensitive and must be unique within the domain. It cannot exceed 128 characters or begin with @. It also cannot contain spaces or the following special characters:
` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [
-NodeName
-nn
node_name
Required if you do not specify grid name. Node where the service runs.
-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.
-ServiceOptions
-so
option_name=value ...
Optional. Service properties that define how the Data Preparation Service runs.
-LicenseName
-ln
license_name
Optional. License object that allows the use of the service.
-RepositoryServiceName
-rs
repository_service_name
Optional. Name of the Model Repository Service that manages the Model repository that contains rule objects and metadata. Set this property if rules are used during data preparation.
-RepositoryUser
-rsun
-repository_username
Optional. User account to use to log in to the Model Repository Service.
-RepositoryPassword
-rspd
-repository_password
Optional. Password for the Model Repository Service user account.
-RepositorySecurityDomain
-rssdn
model_repository_security_domain
Optional. Security domain to which the Model Repository Service user account belongs.
-DISServiceName
-dsn
dis_service_name
Optional. Name of the Data Integration Service that runs rules during data preparation. Set this property if rules are used during data preparation.
-HttpPort
-hp
http_port
Required if you do not specify an HTTPS port. Unique HTTP port number used for each Data Integration Service process. After you create the service, you can define different port numbers for each service process.
-HttpsPort
-hsp
https_port
Required if you do not specify an HTTP port. Unique HTTPS port number used for each Data Integration Service process. After you create the service, you can define different port numbers for each service process.
-KeystoreFile
-kf
keystore_file_location
Optional. Path and file name of the keystore file that contains the keys and certificates required if you use the HTTPS protocol for the 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
Optional. Password for the keystore file.
-TruststoreFile
-tsf
truststore_file_location
Optional. Path and the file name of the truststore file that contains authentication certificates for the HTTPS connection.
-TruststorePassword
-tsp
truststore_password
Optional. Password for the truststore file.
-RulesServerPort
-rpo
RulesServerPort
Optional. Port used by the rules server managed by the Data Preparation Service. Set the value to an available port on the node where the Data Preparation Service runs.
-SolrPort
-spo
SolrPort
Optional. Port number for the Apache Solr server used to provide data preparation recommendations.
-maxHeapSize
-mxhs
maxHeapSize
Optional. Heap size to allocate to the service.
-FolderPath
-fp
full_folder_path
Optional. Full path, excluding the domain name, to the folder in which you want to create the service. Must be in the following format: 
/
parent_folder
/
child_folder