The following users may be required for installation of the 

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

• Documentation link: Install on CentOS and RHEL

Running Services

After installation, you can run the platform as the 

• 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

• Required configuration: No
• Defaults:
  • User: 

    D s defaultuser
    Type ldap Value true

  • Group: 

    D s defaultuser
    Type ldap.group Value true

• Documentation reference: 
  • User: 

    D s defaultuser
    Type ldap

  • Group: 

    D s defaultuser
    Type ldap.group

• Documentation link: Configure SSO for AD-LDAP

Databases

The 

Main database

The Main database is used for managing 

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.main Value true

• Documentation reference: 

  D s defaultuser
  Type db.main

• Documentation link: Manual Database Install

Jobs database

The Jobs database is used for tracking batch execution jobs initiated by the platform. 

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.jobs Value true

• Documentation reference: 

  D s defaultuser
  Type db.jobs

• Documentation link: Manual Database Install

Scheduling database

Storage of schedules, including datasets to execute.

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.scheduling Value true

• Documentation reference: 

  D s defaultuser
  Type db.scheduling

• Documentation link: Manual Database Install

Time-based Trigger database

Storage of triggering information.

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.tbts Value true

• Documentation reference: 

  D s defaultuser
  Type db.tbts

• Documentation link: Manual Database Install

Configuration Service database

Storage of parameter settings at the workspace level.

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.configuration Value true

• Documentation reference: 

  D s defaultuser
  Type db.configuration

• Documentation link: Manual Database Install

Artifact Storage Service database

Storage for feature-specific usage data such value mappings.

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.artifact Value true

• Documentation reference: 

  D s defaultuser
  Type db.artifact

• Documentation link: Manual Database Install

Job Metadata Service database

Storage of metadata on job execution.

• Required configuration: Yes
• Default user: 

  D s defaultuser
  Type db.metadata Value true

• Documentation reference: 

  D s defaultuser
  Type db.metadata

• Documentation link: Manual Database Install

Hadoop

Hadoop User

When the platform interacts with the Hadoop cluster, all actions are brokered through the use of a single Hadoop user account.

• Required configuration: Yes
• Defaults:
  
  • User:

    D s defaultuser
    Type hadoop Value true

  • Group:

    D s defaultuser
    Type hadoop.group Value true

• Documentation references:
  
  • User: 

    D s defaultuser
    Type hadoop

  • Group: 

    D s defaultuser
    Type hadoop.group

• Documentation link: Configure for Hadoop

Kerberos

If Kerberos is enabled on your cluster, you must specify the principal of the Hadoop user for the 

• Required configuration: No
• Default user: 

  D s defaultuser
  Type principal Value true

• Documentation reference: 

  D s defaultuser
  Type principal

• Documentation links:
  • Kerberos:  Configure for Kerberos Integration
  • Secure impersonation: Configure for Secure Impersonation

Hive

You must specify a user that Hive uses to connect to HDFS. 

• Required configuration: No
• Defaults:
  
  • User: 

    D s defaultuser
    Type Hive Value true

  • Group: 

    D s defaultuser
    Type hive.group Value true

• Documentation references: 
  • User: 

    D s defaultuser
    Type hive

  • Group: 

    D s defaultuser
    Type hive.group

• 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: 

    D s defaultuser
    Type hdi Value true

  • Group: 

    D s defaultuser
    Type hdi.group Value true

• Documentation references: 
  
  • User: 

    D s defaultuser
    Type hdi

  • Group: 

    D s defaultuser
    Type hdi.group

• Documentation link: Configure for HDInsight