Contents:
Depending on your Alteryx® deployment, the following users may be required for installation of the platform and integration with other components in the environment. In some cases, you must also designate a group in which the user or users must belong.
NOTE: Except as noted, you may substitute your own usernames for the default usernames. These substitutions are identified in the documentation references.
In this sections below, you can review the user requirements for various aspects of platform installation and integration.
Legend:
- Required configuration: If Yes, then the configuration and the relevant user are required for all installations of the platform.
- Default user: Default or expected username for the user.
- Documentation reference: How the user is referenced in the documentation.
- Documentation link: For more information on configuring for the listed component, please visit the listed link, where application of these values is described in greater detail.
Installation node
Install
NOTE: The software must be installed on the node using the root account. After installation, this account is not used.
- Documentation link: Installation Steps
Running Services
After installation, you can run the platform as the trifacta user.
- Documentation link: Start and Stop the Platform
Active Directory/LDAP
When enabling Single Sign-On, you must specify an Active Directory user to serve as the admin for provisioning users within the Designer Cloud Powered by Trifacta platform.
- Required configuration: No
- Defaults:
- User:
trifacta - Group:
trifactausers
- User:
- Documentation reference:
- User:
[ldap.user] - Group:
[ldap.group]
- User:
- Documentation link: Configure SSO for AD-LDAP
Databases
The Designer Cloud Powered by Trifacta platform installs and maintains two databases.
Main database
The Main database is used for managing Alteryx metadata.
- Required configuration: Yes
- Default user:
trifacta - Documentation reference:
[db.main.user] - Documentation link: Set up the Databases
Jobs database
The Jobs database is used for tracking batch execution jobs initiated by the platform.
- Required configuration: Yes
- Default user:
trifactaactiviti - Documentation reference:
[db.jobs.user] - Documentation link: Set up the Databases
Hadoop
Hadoop User
When the platform interacts with the Hadoop cluster, all actions are brokered through the use of a single Hadoop user account.
NOTE: This user account is specified and used in multiple configurations for integration with the Hadoop cluster.
- Required configuration: Yes
- Defaults:
- User:
trifacta - Group:
trifactausers
- User:
- Documentation references:
- User:
[hadoop.user] - Group:
[hadoop.group]
- User:
- Documentation link: Configure for Hadoop
Kerberos
If Kerberos is enabled on your cluster, you must specify the principal of the Hadoop user for the Designer Cloud Powered by Trifacta platform. Depending on the other components available in the cluster, you may need to specify other Kerberos principals.
- Required configuration: No
- Default user:
trifacta - Documentation reference:
[hadoop.user.principal] - Documentation links:
- Kerberos: Set up for a Kerberos-enabled Hadoop cluster
- Secure impersonation: Configure for secure impersonation
Hive
You must specify a user that Hive uses to connect to HDFS.
- Required configuration: No
- Defaults:
- User:
hive - Group:
trifactausers
- User:
- Documentation references:
- User:
[hive.user] - Group:
[hive.group]
- User:
- Documentation link:Configure for Hive
HDInsight
Cluster
When integrating with HDInsight, you must specify a user for the platform to use with its connections to HDI.
- Required configuration: No
- Defaults:
- User:
trifacta - Group:
trifactausers
- User:
- Documentation references:
- User:
[hdi.user] - Group:
[hdi.group]
- User:
- Documentation link: Configure for HDInsight
This page has no comments.