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
Interactive Data Preparation Service . The description cannot exceed 765 characters.
|
Location
| Location of the
Interactive Data Preparation Service in the Informatica domain. You can create the service within a folder in the domain.
|
License
| License object with the data lake option that allows the use of the
Interactive Data Preparation Service .
|
Node Assignment
| 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.
|
Node
| Name of the node on which the
Interactive Data Preparation Service runs.
|
Backup Nodes
| If your license includes high availability, nodes on which the service can run if the primary node is unavailable.
Select each backup node on which the service runs.
|
Grid
| Select the grid that you want to use for the
Interactive Data Preparation Service .
|
Property
| Description
|
---|---|
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.
|
Data Integration Service Name
| Name of the Data Integration Service.
|
Property
| Description
|
---|---|
HTTP Port
| Port number for the HTTP connection to the
Interactive Data Preparation Service .
|
Enable Secure Communication
| 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.
|
HTTPS Port
| Port number for the HTTPS connection to the
Interactive Data Preparation Service .
|
Keystore File
| Path and the file name of keystore file that contains key and certificates required for HTTPS communication.
|
Keystore Password
| Password for the keystore file.
|
Truststore File
| Path and the file name of truststore file that contains authentication certificates for the HTTPS connection.
|
Truststore Password
| Password for the truststore file.
|
Property
| Description
|
---|---|
Database Type
| Type of database to use for the Data Preparation repository.
|
Host Name
| Host name of the database machine.
|
Port Number
| Port number for the database.
|
Connection String
| 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:
verifyServerCertificate=true&useSSL=true&requireSSL=true |
Secure JDBC Parameters
| 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> |
Database User Name
| Database user account to use to connect to the database.
|
Database User Password
| Password for the database user account.
|
Schema Name
| Schema or database name for a MySQL database.
|
Property
| Description
|
---|---|
Rules Server Port
| 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.
|
Property
| Description
|
---|---|
Local Storage Location
| Directory for data preparation file storage on the node where the service runs.
|
HDFS Connection
| HDFS connection for data preparation file storage.
|
HDFS Storage Location
| HDFS location for data preparation file storage. If the connection to the local storage fails, the
Interactive Data Preparation Service recovers data preparation files from the HDFS location.
|
Property
| Description
|
---|---|
Hadoop Authentication Mode
| 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.
|
HDFS Service Principal Name
| Service Principal Name (SPN) for the data preparation Hadoop cluster.
|
Hadoop Impersonation User Name
| User name to use in Hadoop impersonation as set in the Hadoop connection properties. Use the Administrator tool to view Hadoop connection properties.
|
SPN Keytab File for User Impersonation
| Path and file name of the SPN keytab file for the user account to impersonate when connecting to the Hadoop cluster. The keytab file must be in a directory on the machine where the
Interactive Data Preparation Service runs.
|
Property
| Description
|
---|---|
Log Severity
| Severity of messages to include in the logs. Select from the following values:
Default value is INFO.
|