Configuring environment properties - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
Latest
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Help
Copyright
2024
First publish date
2016
ft:lastEdition
2024-07-09
ft:lastPublication
2024-07-09T15:09:58.774265

You can use the Properties tab to parameterize values that might change across your system's environments.

  1. From the menu at the top of the screen, select Admin > Environments.
  2. To edit an existing environment, select the environment that you want to edit from the list on the left of the screen.
  3. Select the Properties tab.
  4. Click New to add a new property.
  5. When you have finished adding properties, click Save Changes.

Example

In this example, you want the URL, username, and password of a database-based data store to differ per environment. Rather than manually changing these values within the data store definition each time you move the data store across environments, you can create environment properties.

You would need to create the properties in each environment where the data store will reside. Environment properties are name:value pairs. In each environment, the properties could have the same names but different values, for example:

Environment 1 has the following properties:

Name

Value

URL

jdbc:teradata://123.45.678.910/DATABASE=test

USERNAME

databaseTestUser

PASSWORD

passwordTest

 

Environment 2 has the following properties:

Name

Value

URL

jdbc:teradata://123.45.678.910/DATABASE=prod

USERNAME

databaseProdUser

PASSWORD

passwordProd

 

Within the data store, you could then reference the environment properties by using the following syntax: ${propertyName}. For example, ${URL}, ${USERNAME}, and ${PASSWORD}. The system would then substitute the parameterized property names with their values, per environment.

Fields that support substitution

The fields that support substitution include:

Data Store

  • S3 Channel:
    • Bucket Name.
    • Folder.
  • HDFS Channel:
    • Path.
  • Filesystem Channel:
    • Path.
  • Database Channel:
    • JDBC Driver Name.
    • URL.
    • Username.
    • Password.
    • Principal Name.
    • Keytab File Name.
    • SQL.
    • Count SQL.
    • Sample SQL.
  • Kafka Channel:
    • Server.
    • Topic.
    • Value for each Additional Connection Property.
    • Registry URL.
    • Schema ID.
    • Topic.
    • Schema Naming Strategy.

Analysis

  • Output Path in Excel Output node.

Process Model

  • Message in Settings screen.
  • Message Details in Settings screen.