The following users may be required for installation of the 
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.
Installation node
Install
NOTE: The software must be installed on the node using the root account. |
Running Services
After installation, you can run the platform as the 
user.
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 
.
- Required configuration: No
- Defaults:
- User:
- Group:
- Documentation reference:
- User:
- Group:
Databases
The installs and maintains two databases.
Main database
The Main database is used for managing 
.
- Required configuration: Yes
- Default user:
- Documentation reference:
Jobs database
The Jobs database is used for tracking batch execution jobs initiated by the platform.
- Required configuration: Yes
- Default user:
- Documentation reference:
Scheduling database
Storage of schedules, including datasets to execute.
- Required configuration: Yes
- Default user:
- Documentation reference:
Time-based Trigger database
Storage of triggering information.
- Required configuration: Yes
- Default user:
- Documentation reference:
Configuration Service database
Storage of parameter settings at the workspace level.
- Required configuration: Yes
- Default user:
- Documentation reference:
Artifact Storage Service database
Storage for feature-specific usage data such value mappings.
- Required configuration: Yes
- Default user:
- Documentation reference:
Job Metadata Service database
Storage of metadata on job execution.
- Required configuration: Yes
- Default user:
- Documentation reference:
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:
- Group:
- Documentation references:
- User:
- Group:
Kerberos
If Kerberos is enabled on your cluster, you must specify the principal of the Hadoop user for the . Depending on the other components available in the cluster, you may need to specify other Kerberos principals.
- Required configuration: No
- Default user:
- Documentation reference:
Hive
You must specify a user that Hive uses to connect to HDFS.
- Required configuration: No
- Defaults:
- User:
- Group:
- Documentation references:
- User:
- Group:
