Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Published by Scroll Versions from space DEV and version r0641

D toc
 

The following users may be required for installation of the 

D s platform
rtrue
 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.

Info

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

Info

NOTE: The software must be installed on the node using the root account.

Running Services

After installation, you can run the platform as the 

D s defaultuser
Typegeneric
Valuetrue
 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

D s platform

  • Required configuration: No
  • Defaults:
    • User: 
      D s defaultuser
      Typeldap
      Valuetrue
    • Group: 
      D s defaultuser
      Typeldap.group
      Valuetrue
  • Documentation reference: 
    • User: 
      D s defaultuser
      Typeldap
    • Group: 
      D s defaultuser
      Typeldap.group
  • Documentation link: Configure SSO for AD-LDAP

Databases

The 

D s platform
 installs and maintains two databases.

Main database

The Main database is used for managing 

D s item
itemmetadata
.

  • Required configuration: Yes
  • Default user: 
    D s defaultuser
    Typedb.main
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.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
    Typedb.jobs
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.jobs
  • Documentation link: Manual Database Install

Scheduling database

Storage of schedules, including datasets to execute.

  • Required configuration: Yes
  • Default user: 
    D s defaultuser
    Typedb.scheduling
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.scheduling
  • Documentation link: Manual Database Install

Time-based Trigger database

Storage of triggering information.

  • Required configuration: Yes
  • Default user: 
    D s defaultuser
    Typedb.tbts
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.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
    Typedb.configuration
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.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
    Typedb.artifact
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.artifact
  • Documentation link: Manual Database Install

Job Metadata Service database

Storage of metadata on job execution.

  • Required configuration: Yes
  • Default user: 
    D s defaultuser
    Typedb.metadata
    Valuetrue
  • Documentation reference: 
    D s defaultuser
    Typedb.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.

Info

NOTE: This user account is specified and used in multiple configurations for integration with the Hadoop cluster.

  • Required configuration: Yes
  • Defaults:
    • User:
      D s defaultuser
      Typehadoop
      Valuetrue
    • Group:
      D s defaultuser
      Typehadoop.group
      Valuetrue
  • Documentation references:
    • User: 
      D s defaultuser
      Typehadoop
    • Group: 
      D s defaultuser
      Typehadoop.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 

D s platform
. Depending on the other components available in the cluster, you may need to specify other Kerberos principals.

Hive

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

  • Required configuration: No
  • Defaults:
    • User: 
      D s defaultuser
      TypeHive
      Valuetrue
    • Group: 
      D s defaultuser
      Typehive.group
      Valuetrue
  • Documentation references: 
    • User: 
      D s defaultuser
      Typehive
    • Group: 
      D s defaultuser
      Typehive.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
      Typehdi
      Valuetrue
    • Group: 
      D s defaultuser
      Typehdi.group
      Valuetrue
  • Documentation references: 
    • User: 
      D s defaultuser
      Typehdi
    • Group: 
      D s defaultuser
      Typehdi.group
  • Documentation link: Configure for HDInsight