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 of the

Interactive Data Preparation Service

. The description cannot exceed 765 characters.

Location of the

Interactive Data Preparation Service

in the Informatica domain. You can create the service within a folder in the domain.

License object with the data lake option that allows the use of the

Interactive Data Preparation Service

.

Type of node in the Informatica domain on which the

Interactive Data Preparation 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.

Select the

Grid

option to ensure horizontal scalability by using a grid with multiple

Interactive Data Preparation Service

nodes. 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.

Default is Single Node.

Name of the node on which the

Interactive Data Preparation Service

runs.

Type of database to use for the Data Preparation repository.

Database user account to use to connect to the database.

Password for the database user account.

Host name of the database machine.

Port number for the database.

Schema or database name of the Data Preparation repository database.

Connection string used to connect to the database.

To connect to an Oracle database, format the string as follows:

jdbc:informatica:oracle://<database host name>:<port>;ServiceName=<service name>

To connect to a non-secure MySQL or MariaDB 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 MySQL or MariaDB database, format the string as follows:

Secure JDBC parameters required to access a secure database.

To connect to a secure Oracle database, format the string as follows:

EncryptionMethod=SSL;HostNameInCertificate=<secure database host name>;ValidateServerCertificate=true

To connect to as secure MySQL or MariaDB database, format the string as follows:

trustCertificateKeyStoreUrl=file://<truststore path/truststore file name>&trustCertificatekeyStorePassword=<truststore password>

Directory for data preparation file storage on the node where the service runs.

Storage type for the data preparation file.

Connection for the data preparation file storage.

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.

Security mode enabled for 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.

Port number for the HTTP connection to the

Interactive Data Preparation Service

.

Use a secure connection to connect to the

Interactive Data Preparation Service

. If you enable secure communication, you must set all required HTTPS properties, including the keystore and truststore properties.

Port number for the HTTPS connection to the

Interactive Data Preparation Service

.

Path and the file name of keystore file that contains key and certificates required for HTTPS communication.

Password for the keystore file.

Path and the file name of truststore file that contains authentication certificates for the HTTPS connection.

Password for the truststore file.

Port used by the rules server managed by the

Interactive Data Preparation Service

. Set the value to an available port on the node where the service runs.