Property | Description |
|---|---|
Name | Name of the Interactive Data Preparation Service. 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: ` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [ |
Description | Description of the service. The description cannot exceed 765 characters. |
License | License object with the data lake option that allows use of the service. |
Node | Name of the node on which the service runs. |
Node Assignment | Type of node in the Informatica domain on which the service runs. Select Single Node if a single service process runs on the node or Primary and Backup Nodes if a service process is enabled on each node for high availability. However, only a single process runs at any given time, and the other processes maintain standby status. The Primary and Backup Nodes option will be available for selection based on the license configuration. Default is Single Node. |
Backup Nodes | If your license includes high availability, nodes on which the service can run if the primary node is unavailable. |
Grid | If you selected Grid for node assignment, select the grid that you want to use for the Interactive Data Preparation Service. A grid ensures horizontal scalability. Improved scalability supports high performance, interactive data preparation during increased data volumes and number of users. Each user is assigned a node in the grid using round-robin method to distribute the load across the nodes. |
Property | Description |
|---|---|
Database User Name | Database user account to use to connect to the Data Preparation repository. |
Database User Password | Password for the Data Preparation repository database user account. |
Connection String | JDBC connection string to connect to the database. Format the string as follows: jdbc:informatica:oracle://<database host name>:<port>;ServiceName=<service name> |
Secure JDBC Parameters | List of secure database parameters to connect to the database. Format the parameters as follows: EncryptionMethod=SSL;HostNameInCertificate=<secure database host name>;ValidateServerCertificate=true |
Property | Description |
|---|---|
Database User Name | Database user account to use to connect to the database. |
Database User Password | Password for the Data Preparation repository database user account. |
Database Host Name | Host name of the machine that hosts the database. |
Database Port Number | Port number for the database. |
Schema Name | Schema or database name of the Data Preparation repository database. |
Connection String | Connection string to connect to the database. To connect to a non-secure database, format the string as follows: jdbc:mysql://<database host name>:<port> The connection string is optional if you connect to a non-secure database. To connect to an SSL-enabled database, format the string as follows: verifyServerCertificate=true&useSSL=true&requireSSL=true |
Secure JDBC Parameters | String containing the path and file name for the database truststore file, and the truststore password. Format the string as follows: trustCertificateKeyStoreUrl=file://<truststore path/truststore file name>&trustCertificatekeyStorePassword=<truststore password> |
Property | Description |
|---|---|
Local Storage Location | Directory for data preparation file storage on the node where the service runs. |
Durable Storage Type | Storage type for the data preparation file. |
Durable Storage Connection | Connection for the data preparation file storage. |
Durable Storage Location | Location for the data preparation file storage. If the connection to the local storage fails, the service recovers data preparation files from the location. If the Hadoop cluster uses Kerberos authentication, the impersonation user name must have read, write and execute permission on the HDFS storage location directory. The default location is: /datalake/dps_durable_storage. |
Hadoop Authentication Mode | Security mode of the Hadoop cluster for data preparation storage. If the Hadoop cluster uses Kerberos authentication, you must set the required Hadoop security properties for the cluster. |
Property | Description |
|---|---|
Log Severity | Severity of messages to include in the logs. Select from one of the following values:
|
Log Directory | Location of the directory of log files. |
Property | Description |
|---|---|
Enable Rule Execution | Set to true for enabling the rule execution. |
Model Repository Service Name | Name of the Model Repository Service. 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: ` ~ % ^ * + = { } \ ; : ' " / ? . , < > | ! ( ) ] [You cannot change the name of the service after you create it. |
Model Repository Service User Name | User name to access the Model Repository Service. |
Model Repository Service Password | Password to access the Model Repository Service. |
Security Domain | Select the security domain to access the Model Repository Service. |
Data Integration Service Name | Name of the Data Integration Service. |