Provide the license key and installation directory path
Provide the license key and installation directory path
Specify the installation directory and the path to the license key file.
Enter the absolute path to the installation directory.
The directory names in the path can't contain spaces or the following special characters:
` % * + ; \ / " ? , < > @ # ! % ) ( } { ] [ ' | &
Default is the user home directory for the user that runs the installation.
Informatica recommends using alphanumeric characters in the installation directory path. If you use a special character such as á or €, unexpected results might occur at run time.
Enter the absolute path to the license key and press
Enter
.
You can enter the license key of any version.
Choose
1
to enable Kerberos network authentication, otherwise choose
2
and press
Enter
.
Default is 1.
You can enable either Kerberos authentication or Security Assertion Markup Language (SAML) authentication in the domain. You cannot enable both authentication modes.
If you enabled Kerberos network authentication, the
Network Security - Service Principal Level
section appears.
If you did not enable Kerberos network authentication, the
Select the level at which to set the Kerberos service principals for the domain.
All nodes in a
CDI-PC domain
must use the same service principal level. When you join a node to a domain, select the same service principal level used by the gateway node in the domain.
Choose one of the following levels:
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.
The
Network Security - Kerberos Authentication
section appears.
Enter the parameters required for Kerberos authentication.
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 CDI-PC 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
CDI-PC 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
CDI-PC 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
CDI-PC domain
are stored. The name of a keytab file in the
CDI-PC domain
must follow a format set by
Cloud Data Integration for PowerCenter (CDI-PC)
.
Fully Qualified Path to the Kerberos Configuration File
. Path and file name of the Kerberos configuration file.
Cloud Data Integration for PowerCenter (CDI-PC)
requires the following name for the Kerberos configuration file:
krb5.conf
If you configure the domain to run with Kerberos authentication, the domain and node name and the node host name must match the names you specified when you ran the
Cloud Data Integration for PowerCenter (CDI-PC)
Kerberos SPN Format Generator to generate SPN and keytab file names. If you use a different domain, node, or host name, generate the SPN and keytab file names again and ask the Kerberos administrator to add the new SPN to the Kerberos principal database and create the keytab files.
The
Pre-Installation Summary
section appears.
Review the installation information and press
Enter
to continue.
The installer copies the
CDI-PC
files to the installation directory. After the installer copies the files, the
ASK INFAPreview
