Informatica Data Quality
- Informatica Data Quality 10.2
- All Products
Level
| Description
|
|---|---|
Process Level
| Configures the domain to use a unique service principal name (SPN) and keytab file for each node and each application service on a node.
The number of SPNs and keytab files required for each node depends on the number of application service processes that run on the node. Use the process level option for domains that require a high level of security, such as productions domains.
|
Node Level
| Configures the domain to share SPNs and keytab files on a node.
This option requires one SPN and keytab file for the node and all application services that run on the node. It also requires a separate SPN and keytab file for all HTTP processes on the node.
Use the node level option for domains that do not require a high level of security, such as test and development domains.
|
Property
| Description
|
|---|---|
Domain name
| Name of the domain. The name must not exceed 128 characters and must be 7-bit ASCII only. The name cannot contain a space or any of the following characters: ` % * + ; " ? , < > \ /
|
Node name
| Name of the Informatica node.
|
Node host name
| Fully qualified host name or the IP address of the machine on which to create the node. The node host name cannot contain the underscore (_) character.
Do not use
localhost . The host name must explicitly identify the machine.
|
Service realm name
| Name of the Kerberos realm to which the Informatica domain services belong. The realm name must be in uppercase.
The service realm name and the user realm name must be the same.
|
User realm name
| Name of the Kerberos realm to which the Informatica domain users belong. The realm name must be in uppercase.
The service realm name and the user realm name must be the same.
|
Keytab directory
| Directory where all keytab files for the Informatica domain are stored. The name of a keytab file in the Informatica domain must follow a format set by Informatica.
|
Kerberos configuration file
| Path and file name of the Kerberos configuration file. Informatica requires the following name for the Kerberos configuration file:
krb5.conf |
Option
| Description
|
|---|---|
Enable HTTPS for Informatica Administrator
| Set up a secure connection to Informatica Administrator.
|
Disable HTTPS
| Do not set up a secure connection to Informatica Administrator.
|
Option
| Description
|
|---|---|
Port
| Port number for the HTTPS connection.
|
Keystore file
| Select whether to use a keystore file generated by the installer or a keystore file you create. You can use a keystore file with a self-signed certificate or a certificate signed by a certification authority.
1 - Use a keystore generated by the installer
2 - Specify a keystore file and password
If you select to use a keystore file generated by the installer, the installer creates a self-signed keystore file named Default.keystore in the following location:
<Informatica installation directory>/tomcat/conf/
|
Prompt
| Description
|
|---|---|
Enable SAML Authentication
| Select whether to enable SAML Authentication:
1 - No
2 - Yes
|
Option
| Description
|
|---|---|
Use the default Informatica SSL certificate file.
| Select to use the default Informatica truststore file for SAML authentication.
|
Enter the location of the SSL certificate file.
| Select to use a custom truststore file for SAML authentication. Specify the directory containing the custom truststore file on gateway nodes within the domain. Specify the directory only, not the full path to the file.
|
Property
| Description
|
|---|---|
Truststore Directory
| Specify the directory containing the custom truststore file on gateway nodes within the domain. Specify the directory only, not the full path to the file.
|
Truststore Password
| The password for the custom truststore file.
|
Option
| Description
|
|---|---|
Use the default Informatica SSL certificate files
| Use the default SSL certificates provided by Informatica.
If you do not provide an SSL certificate, Informatica uses the same default private key for all Informatica installations. If you use the default Informatica keystore and truststore files, the security of your domain could be compromised. To ensure a high level of security for the domain, select the option to specify the location of the SSL certificate files.
|
Specify the location of the SSL certificate files
| Use SSL certificates that you provide. You must specify the location of the keystore and truststore files.
You can provide a self-signed certificate or a certificate issued by a certificate authority (CA). You must provide SSL certificates in PEM format and in Java Keystore (JKS) files. Informatica requires specific names for the SSL certificate files for the Informatica domain. You must use the same SSL certificates for all nodes in the domain. Store the truststore and keystore files in a directory accessible to all the nodes in the domain and specify the same keystore file directory and truststore file directory for all nodes in the same domain.
|
Property
| Description
|
|---|---|
Keystore file directory
| Directory that contains the keystore files. The directory must contain files named infa_keystore.jks and infa_keystore.pem.
|
Keystore password
| Password for the keystore infa_keystore.jks.
|
Truststore file directory
| Directory that contains the truststore files. The directory must contain files named infa_truststore.jks and infa_truststore.pem.
|
Truststore password
| Password for the infa_truststore.jks file.
|
Prompt
| Description
|
|---|---|
Database type
| Type of database for the domain configuration repository. Select from the following options:
1 - Oracle
2 - Microsoft SQL Server
3 - IBM DB2
4 - Sybase ASE
|
Property
| Description
|
|---|---|
Database user ID
| Name for the domain configuration database user account.
|
User password
| Password for the domain configuration database user account.
|
Property
| Description
|
|---|---|
Configure tablespace
| Select whether to specify a tablespace:
1 - No
2 - Yes
In a single-partition database, if you select No, the installer creates the tables in the default tablespace. In a multi-partition database, you must select Yes.
|
Tablespace
| Name of the tablespace in which to create the tables. Specify a tablespace that meets the pageSize requirement of 32768 bytes.
In a single-partition database, if you select Yes to configure the tablespace, enter the name of the tablespace in which to create the tables.
In a multi-partition database, specify the name of the tablespace that resides in the catalog partition of the database.
|
Property
| Description
|
|---|---|
Schema name
| Name of the schema that will contain domain configuration tables. If this parameter is blank, the installer creates the tables in the default schema.
|
Prompt
| Description
|
|---|---|
Database host name
| Host name for the database.
|
Database port number
| Port number for the database.
|
Database service name
| Service or database name :
|
Configure JDBC Parameters
| Select whether to add additional JDBC parameters to the connection string:
1 - Yes
2 - No
If you select Yes, enter the parameters or press Enter to accept the default. If you select No, the installer creates the JDBC connection string without parameters.
|
Property
| Description
|
|---|---|
Database truststore file
| Path and file name of the truststore file for the secure database.
|
Database truststore password
| Password for the truststore file.
|
Custom JDBC Connection String
| JDBC connection string to connect to the secure database, including the host name and port number and the security parameters for the database.
|
Option
| Description
|
|---|---|
1 - OK
| Enter the connection information for a new database.
|
2 - Continue
| The installer overwrites the data in the database with new domain configuration.
|
Property
| Description
|
|---|---|
Keyword
| Keyword to use to create a custom encryption key to secure sensitive data in the domain. The keyword must meet the following criteria:
|
Encryption key directory
| Directory in which to store the encryption key for the domain. By default, the encryption key is created in the following directory:
<Informatica installation directory>/isp/config/keys .
|
Property
| Description
|
|---|---|
Domain name
| Name of the Informatica domain to create. The default domain name is Domain_<MachineName>.
The name must not exceed 128 characters and must be 7-bit ASCII only. The name cannot contain a space or any of the following characters:
` % * + ; " ? , < > \ /
|
Node name
| Name of the node to create.
|
Node host name
| Host name or IP address of the machine on which to create the node.
If the machine has a single network name, use the default host name. If the a machine has multiple network names, you can modify the default host name to use an alternate network name.
The node host name cannot contain the underscore (_) character. Do not use localhost. The host name must explicitly identify the machine.
|
Node port number
| Port number for the node. The default port number for the node is 6005. If the port number is not available on the machine, the installer displays the next available port number.
|
Domain user name
| User name for the domain administrator. You can use this user name to initially log in to Informatica Administrator. Use the following guidelines:
|
Domain password
| Password for the domain administrator. The password must be more than 2 characters and must not exceed 16 characters.
Not available if you configure the Informatica domain to run on a network with Kerberos authentication.
|
Confirm password
| Enter the password again to confirm.
Not available if you configure the Informatica domain to run on a network with Kerberos authentication.
|
Prompt
| Description
|
|---|---|
Display advanced port configuration page
| Select whether to display the port numbers for the domain and node components assigned by the installer:
1 - No
2 - Yes
If you select Yes, the installer displays the default port numbers assigned to the domain components. You can specify the port numbers to use for the domain and node components. You can also specify a range of port numbers to use for the service process that will run on the node. You can use the default port numbers or specify new port numbers. Verify that the port numbers you enter are not used by other applications.
|
Port
| Description
|
|---|---|
Service Manager port
| Port number used by the Service Manager on the node. The Service Manager listens for incoming connection requests on this port. Client applications use this port to communicate with the services in the domain. The Informatica command line programs use this port to communicate to the domain. This is also the port for the SQL data service JDBC/ODBC driver. Default is 6006.
|
Service Manager Shutdown port
| Port number that controls server shutdown for the domain Service Manager. The Service Manager listens for shutdown commands on this port. Default is 6007.
|
Informatica Administrator port
| Port number used by Informatica Administrator. Default is 6008.
|
Informatica Administrator shutdown port
| Port number that controls server shutdown for Informatica Administrator. Informatica Administrator listens for shutdown commands on this port. Default is 6009.
|
Minimum port number
| Lowest port number in the range of dynamic port numbers that can be assigned to the application service processes that run on this node. Default is 6014.
|
Maximum port number
| Highest port number in the range of dynamic port numbers that can be assigned to the application service processes that run on this node. Default is 6114.
|